Sunday, May 13, 2012

Chapter 7 – Software Development


VIGNETTE “Boeing Dreamliner Faces A Few Bumps in the Road”



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?


Yes, somehow there's a software who's in operable condition while others are in defect process, thou major evaluating the products it help to develop and ease major problems that might cause a effect to the customers.   




2. What can organization do to reduce the negative consequences of software development problems in the production of their products and operation of their business processes and facilities.



Thou examines and following standards which may cause a good quality products, developing process may conducting several testing and reviewing in part of documents, to secure the products that is reliable to the customers and free from defect to avoid risky problems during manufacturing until supplying.







Case Study 1 – Computer Problems at WellPoint Have Serious Impact


1.  “The computer system did it” is an easy excuse for a multitude problem. Clearly WellPoint’s system consolidation effort went poorly but it is fair to say that this incident raises other more fundamental areas of concern about the management of WellPoint?

These issues are cause to improper management of each data and unprofessionalism of the people who’s handling the data and information of each client that may lead to multitude problems and might cause the failure of each and anyone. 





2.  What can be done to improve the quality of information technology projects at healthcare organizations? Should such system efforts be classified as safety-critical systems and be subjected to more rigorous implementation standards and processes? Should there be oversight of such efforts by either the government or the industry organization?

Proper organized of the data of each client and must have an integrate database which is reliable always to the user to avoid unwanted problems might happen. Yes, it should be classified as safety-critical systems it is a risky part not just to their client but also for the user, WellPoint must undergo to a lot of process and follow standardization to produce a system that is reliable and operable. Yes, there must be oversight in industry organization, when certain thing happened like what issues given all are totally affected. 



3. Implementation of electronic healthcare records is a national priority, and much emphasis is being place in the importance of adopting new information technology. Meanwhile, the fundamental processing systems are falling into disappear. How should healthcare organizations such as WellPoint prioritize their scarce resources?   

Before implementation, first must go to planning, by this part WellPoint knew the way to handle insufficient resources and evaluate which they prioritize first to be able to secure and inter-connected to every client they have.





Case Study 2 – Prius Plagued by Programming Error


1. Do you agree with NHTSA’s assessment that problem with Prius was not a safety-critical issue? In such case, who should decide whether a software bug creates a safety-critical issue-the manufacturer, consumers, government agencies, or some group?

No, it is a safety-critical issue, all system that have been produced and implement must be free from any error it is harmful to use defect system or product and it must undergo to different process and testing to be reliable to the user to avoid risky things. The manufacturer must be liable for the software they produce and they the one who is responsible if there are even single defect that will encountered.



2.  How would the issue have been handled differently if it had been safety-critical matter? Would it have been handled differently if the costs involved hadn’t been so great?

As much concern to the prior of the user, possible test and reviewing safety-critical software matter must be prioritize. Possible problems or risk may encounter manufacturer especially developer will shoulder the issues. It’s better to be sure than to avoid huge amount of costs will expend, safety first life is priceless.



3. As the amount of hardware and software embedded in the average car continues to grow, what steps can automakers take to minimize warranty claims and ensure customer safety?  
  
Is better to produced a reliable and undergo to certain process to assure the product are in good condition and it is better to produced product with a certified standardization license approval to ensure the customer safety.







Case Study 3 – Patriot Missile Failure


1. With the benefits of hindsight, what steps could have been taken during development of the Patriot software to avoid the problems that lead to the loss of life? Do you think that these steps would have improved the Patriot’s effectiveness enough to make it obvious that the missile was a strong deterrent against the Scud? Why or why not?

It must be reliable to the person who use, certified and pass to every Quality Assurance testing and it is undergo to ISO standardization. Yes by this part of overall effective testing and totally sealed to be as standard as compare top other missile.



2.  What ethical decisions do you think the U.S. military made in choosing to deploy the Patriot missile to Israel and Saudi Arabia and reporting the effectiveness of the Patriot system?

God bless America they love war; I think ethically they do process and testing to avoid another incident happened that will kill another U.S armies. Thru deploying missile is much effective as what as the radar and the missile are liable to communicate in certain action.



3. What key lessons from this example of safety-critical software development could be applied to the development of business information system software?

Safety-critical software must test and review as possible as could be. By this part it is necessary to evaluate the software and to know the better result, each progress must be recorded and examine to assure that there is no defect on software to release.

No comments:

Post a Comment