1). Is this example of software problems holding up the introduction of a major new product and impacting a firm’s customers and suppliers unusual, or is it a common occurrence?
High quality software systems are easy to learn and use because they perform quickly and efficiently; they meet their users' needs; and they operate safely and reliably so that system downtime is kept to a minimum. Such software has long been required to support the fields air traffic control, nuclear power, automobile safety, healthcare, military and defense, and space exploration.
2.) What can organizations do to reduce the negative consequences of software development problems in the production of their products and the operation of their business processes and facilities?
The primary goal of software developers is the production of quality systems that meet the needs of the user. Software quality is defined in terms of customer satisfaction. "Risk" is understood as any potential threat to the delivery of a quality product. To meet the goal of quality software, developers focus on particular risks including: project and schedule slips, cost increases, technical and quality risks, the timeliness of the product, risks that the final product will not fit the business for which it was designed. Projects are managed focusing on these risks. Tools used to help identify and manage these risks include: risk tables, and lists of risks categorized by type, probability and impact. The checklist process is reminiscent of the process pilots go through before take off. As airline passenger we are made more comfortable by the fact that they go through this procedure. But unlike pilots, developers choose to ignore some risks. Risks levels are determined based on the anticipated impact of the risk and its probability of occurring. Only risks above limited specified levels are addressed.
http://dl.acs.org.au/index.php/ajis/article/viewFile/202/176
No comments:
Post a Comment