<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title>Software Engineering Code Of Ethics And  Professional Practice by Aiman Faris97</title>
      <link>https://padlet.com/aimanfaris97/yw5wq31fnu1u</link>
      <description>Software Engineering FOC Assignment</description>
      <language>en-us</language>
      <pubDate>2019-02-26 23:10:23 UTC</pubDate>
      <lastBuildDate>2019-03-06 15:45:18 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url>https://padlet-assets.s3.amazonaws.com/icons/Removelove.png</url>
      </image>
      <item>
         <title>Summary Of Software Engineering Code of Ethics And Professional Practice</title>
         <author>aimanfaris97</author>
         <link>https://padlet.com/aimanfaris97/yw5wq31fnu1u/wish/335693182</link>
         <description><![CDATA[<h1>Software Engineering Code Of Ethics And Professional Practice</h1><div>Software Engineering FOC Assignment is a code</div><div>or a list of principles which software engineers should well stick in order to achieve a good software applications, in which are beneficial. This code to prevent any harm to be made due to immoral or irrelevant practices that can cause problems in world of full of technology.<br><br>The Code contains 8 principles related to the behaviors and decisions made by anyone in the software engineering field. The Principles identify the ethically responsible relationships in which individuals,groups, and organizations participate and the primary obligations within these relationships. The Code set as an obligations of anyone wanting to become a software engineer. The 8 principles listed are Public,Client And Employer,Product,Judgement,Management,Profession,Collegues and SELF, which all adhere how a software engineer should be.</div>]]></description>
         <enclosure url="" />
         <pubDate>2019-02-27 00:05:12 UTC</pubDate>
         <guid>https://padlet.com/aimanfaris97/yw5wq31fnu1u/wish/335693182</guid>
      </item>
      <item>
         <title>Problem background
</title>
         <author>congjc9797</author>
         <link>https://padlet.com/aimanfaris97/yw5wq31fnu1u/wish/335738939</link>
         <description><![CDATA[<div>The background problem for this article is a little error by software can cause a fatal disaster to all community. From the article, sensor for vehicle is good to managing the object that we cannot see because of blind spot. But these sensor not only detect cars, pedestrians, and large rocks in its path and stop or swerve to avoid them, its also detect other objects—like a plastic bag in the road or a trash can on the sidewalk—that a car can safely ignore. But the article shows the sensor is ignoring the "real object" which is human and an accident is happen.<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2019-02-27 03:56:17 UTC</pubDate>
         <guid>https://padlet.com/aimanfaris97/yw5wq31fnu1u/wish/335738939</guid>
      </item>
      <item>
         <title>Summary of the automotive software bug</title>
         <author></author>
         <link>https://padlet.com/aimanfaris97/yw5wq31fnu1u/wish/337862698</link>
         <description><![CDATA[<div>In this article, it has been reported that the fatal crash killed a pedestrian in Tempe, Arizona in March occurred because of a software bug in Uber's self-driving car technology. Uber’s sensor did detect the pedestrian but the software classified the pedestrian as a "false positive" and decided it didn't need to stop for the pedestrian.<br><br></div><div>Distinguishing between real objects and illusory ones is one of the most basic challenges of developing self-driving car software. If the software is programmed to be too cautious, the ride will be slow and jerky, as the car constantly slows down for objects that pose no threat to the car or aren't there at all. Tuning the software in the opposite direction will produce a smooth ride most of the time—but at the risk that the software will occasionally ignore a real object.  The more cautiously a car's software is programmed, the more often it will slam on its brakes unnecessarily. That will produce a safer ride but also one that's not as comfortable for passengers.<br><br></div><div>This provides some useful context for Efrati's March report that cars from Cruise, GM's self-driving car subsidiary, "frequently swerve and hesitate.Getting fully self-driving cars on the road is a worthwhile goal. But making sure that's done safely is more important.</div>]]></description>
         <enclosure url="" />
         <pubDate>2019-03-05 12:26:45 UTC</pubDate>
         <guid>https://padlet.com/aimanfaris97/yw5wq31fnu1u/wish/337862698</guid>
      </item>
      <item>
         <title>Highlighted and how the reading on the given article can be related and solve the issues</title>
         <author></author>
         <link>https://padlet.com/aimanfaris97/yw5wq31fnu1u/wish/338200946</link>
         <description><![CDATA[<div>From the first article given, software engineers should adhere those eight principles in order to take care of health, safety and welfare of the publlic. Those eight principles are public, client and employer, product, judgment, management, profession, colleageues and self. <br>From the second article , a fatal crash that killed pedestrain in Tempe, Arizona occurred due to a software bug in Uber's self-driving car technology. In this incident, software enginners should have the principle of Public. Software engineers should approve software only if the have a well-founded belief that the software is safe enough and does not diminish quality of life. Principle Client and Employer is also important because they shall act in a manner that is in the best interests of their client and employer, consistent with the public to provide the professional knowledge to the authority and public. Software engineers ensure that any document upon which they rely has been approved, when required by some authorized such as government, If the software has been checked ,tested and approved by the authorized, the safety of the software might increase and it definitely will increase the safety of the public and also the user. Next, principle Product is also important in this incident because software engineers shall ensure that their product and related modifications meet the highest professional standards. Some of the product of the software engineers can harm the users or the public indirectly. The incident occur in the second article is the best example to carry out how important is the product and also the safety of the product of the software engineers. In conclusion, not only these three principles of the eight should contained by the engineers, every of the eight principles are important to make the product of the software engineers become higher quality and also will increase the professional of them.</div>]]></description>
         <enclosure url="" />
         <pubDate>2019-03-06 01:19:57 UTC</pubDate>
         <guid>https://padlet.com/aimanfaris97/yw5wq31fnu1u/wish/338200946</guid>
      </item>
      <item>
         <title>Issue in Software Engineering</title>
         <author></author>
         <link>https://padlet.com/aimanfaris97/yw5wq31fnu1u/wish/338430878</link>
         <description><![CDATA[<div>In article, the issue that have is a fatal disaster that killed pedestrian Elaine Herzberg,distinguishing between real objects and illusory ones is one of the most basic challenges. The software not detect the things that not recorded at walk side.<br>The more cautiously a car's software is programmed, the more often it will slam on its brakes unnecessarily. It will not safe if the programmer not record or program it detail, it will dangerous to the user.<br>This issue make the company can not continue their project, if they success in the safety record and program it, the accident will not happen and they can continue the project</div>]]></description>
         <enclosure url="" />
         <pubDate>2019-03-06 15:33:48 UTC</pubDate>
         <guid>https://padlet.com/aimanfaris97/yw5wq31fnu1u/wish/338430878</guid>
      </item>
   </channel>
</rss>
