<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title>SPECIMEN by guzitgs</title>
      <link>https://padlet.com/guzitgs/ITGSSPEC</link>
      <description>SPECIMEN</description>
      <language>en-us</language>
      <pubDate>2016-10-31 04:09:26 UTC</pubDate>
      <lastBuildDate>2026-01-03 23:45:57 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url></url>
      </image>
      <item>
         <title></title>
         <author>guzitgs</author>
         <link>https://padlet.com/guzitgs/ITGSSPEC/wish/134135567</link>
         <description><![CDATA[]]></description>
         <enclosure url="https://padletuploads.blob.core.windows.net/aws/109649051/51fca3ab15d0f0a7a1b5465b4c281008/Specimen_papers_1__2_and_3.pdf" />
         <pubDate>2016-10-31 04:11:14 UTC</pubDate>
         <guid>https://padlet.com/guzitgs/ITGSSPEC/wish/134135567</guid>
      </item>
      <item>
         <title>Health S16C (Girls)</title>
         <author>afifah_zaki98</author>
         <link>https://padlet.com/guzitgs/ITGSSPEC/wish/135657114</link>
         <description><![CDATA[<blockquote> <strong>Criterion B</strong></blockquote><div><br></div><pre>Step by step</pre><div>- Blood is taken and glucose levels are measured by the meter<br><strong>- The computer is connected to a secured wireless connection<br>- Patient has to log in their profile, username, password and keyword (special keyword in order to help medical staffs do research about their data easier)</strong><br>- The results are uploaded and stored on the patient’s computer. <br><strong>- The data is saved in database</strong><br>- Results are sent to the LivingWithDiabetes website. <br><strong>- Staffs need to log in into the website using their own username and password <br>- Staffs should key in the patient's keyword in order to search about patient's data in order to make them able to access the data </strong><br>- Results can be viewed by medical staff <br><br></div><pre><strong>Relationship</strong></pre><div>- Security of patients' data will be jeopardized if there is lacked in security system in the website. hacker can hack the data. <br>hackers hack the database.<br><br><br><br></div><blockquote><strong>Criterion C</strong></blockquote><div><br>1. Reliability and Integrity<br>Stakeholder : Living With Diabetes Company<br>Situation : As the website is being used in a wide range, so it is possible for it to get hang and the data might also lost and being changed. too much request.<br>New dimension : the web crashed<br><br>2. Security<br>Stakeholder : Diabetics<br>Situation : Less security of the website might lead the hackers to manipulate the data and steal their personal profiles<br>New dimension : Wrong dose of medicine gives by the doctor because of the wrong information about the data of the patient<br><br>3. Privacy and anonymity<br>Stakeholder : Diabetics<br>Situation : when data is not secured Hackers who have access the data might spread the information <br>New dimension : if the hacker sent the to the insurance company diabetics personal data like address, id number got stolen, the possibilities the hacker target the same person to get more info like bank account number that lead to worser issue<br><br>4. Authenticity<br>Stakeholder : Diabetics<br>Situation : Hackers that able to hijacked the staffs username and password might manipulate and change the data<br>New dimension :<br><br>5. people and machine<br>Stakeholder : Diabetics<br>Situation : Diabetics who key in their data by themselves without being monitored by medical staffs might cheat<br>New dimension : The patients' health might be affected and getting worse</div>]]></description>
         <enclosure url="" />
         <pubDate>2016-11-07 01:29:11 UTC</pubDate>
         <guid>https://padlet.com/guzitgs/ITGSSPEC/wish/135657114</guid>
      </item>
      <item>
         <title>Health SC (Boys Power)</title>
         <author>salmanfaris</author>
         <link>https://padlet.com/guzitgs/ITGSSPEC/wish/135657611</link>
         <description><![CDATA[<div>Describe, step by step, how the IT system works:</div><div><br></div><div>Patients take their blood and use a blood glucose meter to measure the levels of blood glucose. <strong>The blood glucose meter is equipped with a sensor, and thus after filtering, a result is produced.</strong></div><div><br></div><div>The patients upload the result by attaching the meter to the computer via wi-fi. <strong>Encryption of the data occurs and it is then instantaneously securely stored into a software in the computer via driver that is given prior to when purchasing the blood glucose meter itself.</strong></div><div><br></div><div><strong>Patients connect his or her computer to a computer-network either LAN or an open Wi-Fi given by the hospital which is probably unsecured or even his own personal network that may be protected by WEP, WPA or WPA2, that all, </strong><strong><em>may be compromised and exploited by hackers.</em></strong></div><div><br></div><div><strong>The patients log in to the system of </strong><strong><em>LivingWithDiabetes</em></strong><strong> website using a registered username and password</strong> <strong>that have a captcha to ensure a human user instead of a bot </strong>and access to the uploading screen to upload the result.</div><div><br></div><div><strong>The results are then stored in a secured database, protected by a 10 alphanumeric pin code to prevent brute-force attacks by hackers or potentially unethical medical staffs,  on the </strong><strong><em>LivingWithDiabetes</em></strong><strong> website where it may be accessible by a certified medical staff</strong>, either the nurse or the doctors.</div><div><br></div><div>The<strong> doctors </strong>access to the information online up on the net and <strong>evaluate the result, and thus think of the action that should be reflected upon the patient.<br><br>Relationship<br> The unsecured connection might open doors to hackers to intercept data from the user during uploads. This leads to the issue of security....<br><br></strong><strong><em>Le Criterion C:</em></strong><strong><br></strong>1. Issue: Privacy and anonymity of the Diabetes patient himself. The information of the diabetes patient is open to access up on the net and it  therefore may be compromised by hackers where the data may be used to blackmail the patient or sold up on the Dark Web. <em>New dimension: Patients might find themselves in a position where their Identification number, health records and even live home addresses exposed and may be used for negative purposes.</em><br>.<br>2. Issue: Reliability and integrity of the LivingWithDiabetes company. The company held responsible for the data that it enholds, this includes providing a strong firewall and enough server space to accomodate the data that it serves, might as well the more the better to prevent any possible DoS or DDoS attacks by hackers. <em>New dimension: With a strong firewall, hackers using less exploitable codes and weak softwares would not be able to jeopardize the system and thus with a bigger server space, crashing and freezing of system can be prevented.</em></div><div> </div><div><br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2016-11-07 01:35:01 UTC</pubDate>
         <guid>https://padlet.com/guzitgs/ITGSSPEC/wish/135657611</guid>
      </item>
      <item>
         <title>Diabetes (Auni &amp; Syakirah - S16B)</title>
         <author>husna212</author>
         <link>https://padlet.com/guzitgs/ITGSSPEC/wish/135983226</link>
         <description><![CDATA[<div>Criterion B — The IT concepts and processes                                                                            [6 marks]</div><div>Describe, step by step, how the IT system works.<br><br></div><div>1.            Patients diagnosed with diabetes will have an account made for them at a website called <em>LivingWithDiabetes</em> to monitor and record their blood glucose level.<br><br></div><div>2.            Diabetic patients drew out their blood on a daily basis.<br><br></div><div>3.            The blood was put in a blood glucose meter to be measured<br><br></div><div>4.            The level of blood glucose levels will be measured using a software and showed on the meter.<br> </div><div>5.            Patients will update their blood glucose level in a computer.<br><br></div><div>6.            Patient will log in to their own account at <em>LivingWithDiabetes</em> website<br><br></div><div>7.            Then, the result will be updated to the <em>LivingWithDiabetes</em> website for doctor’s reference<br><br></div><div>8.            Medical staff will receives the information and review it.<br><br></div><div>9.            The staff will report to the doctor if the blood glucose level reach an unhealthy level. If not, the record will be kept as future reference.<br><br></div><div>10.          The doctor can immediately access the information online.<br><br></div><div><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2016-11-08 02:28:33 UTC</pubDate>
         <guid>https://padlet.com/guzitgs/ITGSSPEC/wish/135983226</guid>
      </item>
      <item>
         <title>(Alister, Hafizah, Anis)- S16B</title>
         <author>alster_dude</author>
         <link>https://padlet.com/guzitgs/ITGSSPEC/wish/135983521</link>
         <description><![CDATA[<div>Describe, step by step, how the IT system works <br>- Blood is taken and glucose levels are measured by the meter <br>-The embedded computer in the meter records the results<br>-The meter is connected to the patient's computer  and the results are uploaded and stored on the patient’s computer <br>-The patient's computer is connected to the Internet through wireless connection or broadband or LAN connection <br>-Patient logs in to  LivingWithDiabetes website account with a username and a password<br>- Results are sent to the LivingWithDiabetes website <br>- Results are saved in website database<br>- Medical staff who has the hospital account password to LivingWithDiabetes website access the results<br>-  Results are viewed by the medical staff immediately</div>]]></description>
         <enclosure url="" />
         <pubDate>2016-11-08 02:31:29 UTC</pubDate>
         <guid>https://padlet.com/guzitgs/ITGSSPEC/wish/135983521</guid>
      </item>
      <item>
         <title>Criterion C (Anis, Hafizah, Alister)</title>
         <author></author>
         <link>https://padlet.com/guzitgs/ITGSSPEC/wish/135994374</link>
         <description><![CDATA[<div>1. Issue: Privacy and anonymity of the Diabetes patient himself. The information of the diabetes patient is shared and open to access up on the net and it  therefore may be compromised. <em>New dimension: Patients might find themselves in a position where their Identification number, health records and even live home addresses exposed and may be used for negative purposes.</em><br><em><br>2</em>. Issue: Security <br>Stakeholder: LivingWithDiabetes company<br>Situation: The company has to come up with measures to overcome unauthorized access and restricts access to the administration of the database and website to certain employees.<em><br>New dimension: With a strong firewall, hackers using less exploitable codes and weak softwares would not be able to jeopardize the system and thus with a bigger server space, crashing and freezing of system can be prevented.<br><br></em>3. Issue: Policies<br>Stakeholder: Patients(Diabetics)<br>Situation: Technologically illiterate patients or users enter unnecessary personal information in the process of making a LivingWithDiabetes account without realising that not every personal detail is crucial for website identification and this leads to important details being uploaded unnecessarily.<br><em>New dimension</em> : <em>the users unknowingly upload essential info of themselves that can be maliciously used by unknown criminals over many years.<br><br></em>4. Issue : Equality of access <br>Stakeholder :  Patients(diabetics)<br>Situation : Language and geographical barrier can make it difficult for some patients(diabetics) to use the system.<em><br>New dimension : The system can only be apply to one particular and homogeneous group of patients.<br><br>5. issue:  </em><br><em><br><br></em><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2016-11-08 04:35:27 UTC</pubDate>
         <guid>https://padlet.com/guzitgs/ITGSSPEC/wish/135994374</guid>
      </item>
      <item>
         <title>Auni and Syakirah (Criterion C - Diabetic) </title>
         <author>nurauni1203</author>
         <link>https://padlet.com/guzitgs/ITGSSPEC/wish/136005068</link>
         <description><![CDATA[]]></description>
         <enclosure url="https://padletuploads.blob.core.windows.net/aws/122543221/21f169643df7be672a9b56a31a5f2702/Diabetic_Patients__Criterion_C_.docx" />
         <pubDate>2016-11-08 07:20:41 UTC</pubDate>
         <guid>https://padlet.com/guzitgs/ITGSSPEC/wish/136005068</guid>
      </item>
      <item>
         <title>Auni and  Syakirah (Criterion D)</title>
         <author>nurauni1203</author>
         <link>https://padlet.com/guzitgs/ITGSSPEC/wish/137944688</link>
         <description><![CDATA[<div>Solution for security:<br>- Make an encryption to the database of the patients. Only certain people can access the data. <br><br> Step-by-Step :<br>1. User (Patients, Medical staffs and Doctors) will set up a password with a security word / picture when they register at <em>"LivingWithDiabetes"</em> website.<br>2. When the users want to log in, they have to make sure that the security word / picture matches with their profile. If not, they have to report to the administrator in case of their account might get hacked.<br>3. Every edit or search made by the user will be tracked and recorded for further reference.<br>4. Medical staffs and doctors access towards patient's information will be limited. They are only permitted to access information for certain accounts.<br>5. If there is a report on an account being hacked, access to the account will be blocked immediately.<br>6. Any edit or search made by users will be reviewed once a month to detect any suspicious movement.<br><br>Evaluation: <br>Positive:<br>-The data will be more secure<br>-Can discourage the hackers to hack the data.<br>Negative:<br>-The Hackers might still able to access to the data if they knew someone that know about the detail of the encryption. <br><br>Future Development:<br>- The account can be accessed using the user's fingerprint in the future.<br><br>Conclusion and judgement:  <br>-Government and other people that involve should take serious about the security of the database as it keep the personal information of the patients.  </div>]]></description>
         <enclosure url="" />
         <pubDate>2016-11-16 00:15:36 UTC</pubDate>
         <guid>https://padlet.com/guzitgs/ITGSSPEC/wish/137944688</guid>
      </item>
      <item>
         <title></title>
         <author>dibahmaster98</author>
         <link>https://padlet.com/guzitgs/ITGSSPEC/wish/137944857</link>
         <description><![CDATA[]]></description>
         <enclosure url="" />
         <pubDate>2016-11-16 00:17:35 UTC</pubDate>
         <guid>https://padlet.com/guzitgs/ITGSSPEC/wish/137944857</guid>
      </item>
      <item>
         <title></title>
         <author>dibahmaster98</author>
         <link>https://padlet.com/guzitgs/ITGSSPEC/wish/137944893</link>
         <description><![CDATA[]]></description>
         <enclosure url="" />
         <pubDate>2016-11-16 00:17:52 UTC</pubDate>
         <guid>https://padlet.com/guzitgs/ITGSSPEC/wish/137944893</guid>
      </item>
      <item>
         <title>Criterion D</title>
         <author>izad981004</author>
         <link>https://padlet.com/guzitgs/ITGSSPEC/wish/137949145</link>
         <description><![CDATA[<div>Solution for Privacy <br>- Encryption of Data in the database of <em>LivingWithDiabetes</em> website where data would be encrypted by AES encryption by certified cryptographers.<br><br>Pros:<br>1. Data will not be able to be penetrated by hackers since it is encrypted and need more highly sophisticated software and revolutionary new codes to overcome the encryption.<br>2. Thus, data would not be able to be intercepted with end-to-end encryption being applied.<br><br>Cons:<br>1. High cost in hiring a cryptographer or purchasing available software in encrypting data.<br>2. Data of patients may load slowly in order to decrypt it everytime the doctors/patients want to access it.<br>3. Patients have to pay more since the cost of hiring a cryptographer or purchasing an encryption service is quite high.</div>]]></description>
         <enclosure url="" />
         <pubDate>2016-11-16 01:02:51 UTC</pubDate>
         <guid>https://padlet.com/guzitgs/ITGSSPEC/wish/137949145</guid>
      </item>
      <item>
         <title>AHA CRITERION D :0</title>
         <author>dibahmaster98</author>
         <link>https://padlet.com/guzitgs/ITGSSPEC/wish/137950709</link>
         <description><![CDATA[<div>Issue: the users unknowingly upload essential info of themselves that can be maliciously used by unknown criminals over many years.<br><br></div><div>Solution: the company designs a user- friendly website.<br><br></div><div>Characteristic: 1) the website has opt in and opt out functions<br><br></div><div>2) data validation is applied to warn users if they enter their data incorrectly<br><br></div><div>3) website policies and agreements are made visible in user account all the time<br><br></div><div>4) demo videos are available <br><br></div><div>Step-by-step:<br><br></div><div>1.      A user- friendly website offer an opt in and opt out function that enable user to sign in only when it is necessary. </div><div>2.      The website has demo videos to guide users in signing up for LivingWithDiabetes website account.</div><div>3.      When user keys in their personal information, data validation on the website will warn users if they enter their data incorrectly.</div><div>4.      Users will be able to view the website’s policies and agreements when they are signed in to their accounts to remind users to be cautious in sharing their personal information. </div><div>5.      Connection verification is applied to warn users if their network is not private to avoid any third parties that can access patients’ personal information.</div><div>6.      The company should make a simplified but clear terms and policies so that users are aware of the agreements made and they understand them before making an agreement.<br><br></div><div> <br><br></div><div>Evaluation: <br><br></div><div>By creating a website with user- friendly interface, users will be reminded or warned when creating an account to be careful in sharing their personal information for their own safety, ensuring that they will not make any mistake in sharing important data while signing up.  however, </div>]]></description>
         <enclosure url="" />
         <pubDate>2016-11-16 01:14:12 UTC</pubDate>
         <guid>https://padlet.com/guzitgs/ITGSSPEC/wish/137950709</guid>
      </item>
      <item>
         <title>CRITERION D ( Girls S16C)</title>
         <author>hohohoho</author>
         <link>https://padlet.com/guzitgs/ITGSSPEC/wish/137959092</link>
         <description><![CDATA[<div>Problem : Security of data that might be corrupted and hacked<br><br>Solution : The company should build firewall for their website<br><br>Characteristics <br><br>1) Block malicious software and corrupt files from entering your computer. Firewalls block malicious items that come from your internet connection along with all other computers connected on a shared network<br><br>2) Block unauthorized access while permitting outward communication. It is a device or set of devices configured to permit, deny, encrypt, decrypt, or proxy all computer traffic between different security domains based upon a set of rules and other criteria. <br><br>3) Prevent unauthorized Internet users from accessing the data in the website connected to the Internet, especially intranets. All messages entering or leaving the intranet pass through the firewall, which examines each message and blocks those that do not meet the specified security criteria. <br><br>Weakness :<br><br>Faulty firewall protection - Caused by the free firewall software downloads instead use a product that is widely acclaimed and has been proven stable and trustworthy.</div>]]></description>
         <enclosure url="" />
         <pubDate>2016-11-16 02:31:58 UTC</pubDate>
         <guid>https://padlet.com/guzitgs/ITGSSPEC/wish/137959092</guid>
      </item>
      <item>
         <title></title>
         <author></author>
         <link>https://padlet.com/guzitgs/ITGSSPEC/wish/138986085</link>
         <description><![CDATA[]]></description>
         <enclosure url="" />
         <pubDate>2016-11-21 02:16:45 UTC</pubDate>
         <guid>https://padlet.com/guzitgs/ITGSSPEC/wish/138986085</guid>
      </item>
   </channel>
</rss>
