Chapter 11 Software Development Horror Stories. Sampling of Software Problems = Faye Starman gets an electric bill for $6.3 million instead of $63 due.

Slides:



Advertisements
Similar presentations
Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
Advertisements

A Gift of Fire, 2edChapter 4: Can We Trust the Computer?1 PowerPoint ® Slides to Accompany A Gift of Fire : Social, Legal, and Ethical Issues for Computers.
The Crippled Team The Story of CONFIRM CS 524 – Software Engineering Dr. Sheldon X. Liang 18 Sept 2007 Darryl Nakata.
Systems Analysis and Design 9th Edition
Project Management.
Effective Project Management: Traditional, Agile, Extreme
Chapter 15 Design, Coding, and Testing. Copyright © 2005 Pearson Addison-Wesley. All rights reserved Design Document The next step in the Software.
Slides prepared by Cyndi Chie and Sarah Frye (and Liam Keliher) A Gift of Fire Third edition Sara Baase Chapter 9: Professional Ethics and Responsibilities.
1 14. Project closure n An information system project must be administratively closed once its product is successfully delivered to the customer. n A failed.
Centers for IBM e-Business Innovation :: Chicago © 2005 IBM Corporation IBM Project October 2005.
SE is not like other projects. l The project is intangible. l There is no standardized solution process. l New projects may have little or no relationship.
The Analyst as a Project Manager
Development Processes and Product Planning
Reaching Goals and Objectives Goal Setting The Bullfight.
Accountability, Data, Improvement Plans.  Data loaded in tables on the web portal for performance  Language says “Current year” ( )
Don Cole Risk Assessment and Mitigation Project Management for ARA Engineers and Scientists.
Vendor Risk: Effective Management is Essential
Chapter 11 Application for Present-Use Value 1. Application for PUV The present-use value program is a voluntary program that provides the owner with.
Initiating and Planning Systems Development projects
Chapter 15 Systems Development. 2 Learning Objectives When you finish this chapter, you will  Understand the systems development life cycle.  Be able.
Database Planning, Design, and Administration Transparencies
Ch 1: The Scope of Software Engineering
Employment and Personnel Matters. District employees  As public officials, you may hire employees to carry out the day to day responsibilities of the.
Chapter 11 Management Skills
12/02/04www.cis.ksu.edu/~meiyappa Enterprise Resource Planning Meiyappan Thandayuthapani CIS 764.
Chapter 13: Developing and Implementing Effective Accounting Information Systems
Performance Improvement. 2 Steps to Performance Improvement 1. Define the Problem 2. Define Duties or Behaviors to be Improved 3. Establish Priorities.
1 Can We Trust the Computer? What Can Go Wrong? Case Study: The Therac-25 Increasing Reliability and Safety Perspectives on Failures, Dependence, Risk,
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
Project Management Methodology Project Closing. Project closing stage Must be performed for all projects, successfully completed or shut off by management.
Software Development Process and Management (or how to be officious and unpopular)
Monica Pantea, MANETPCC meeting in Groningen 2006 Time Schedule of the EURONS Annual Report End of reporting period Deadline of submission.
By: Heather Smith LDR 609. On January 15, 2009, the Department of Health and Human Services (HHS) released the final regulation to move from the current.
University of Virginia Software Development Processes (CS340 John Knight 2005) 1 Software Development Processes.
Interim Executive Director June  Financial Management Practices Audit Results Fiscal Year Audit Results Fiscal Year Internal.
Software Engineering Saeed Akhtar The University of Lahore Lecture 8 Originally shared for: mashhoood.webs.com.
J. G. Weisend II Deputy Head of Accelerator Projects April 2, 2014 Actions at ACCSYS Resulting from the Recommendations of the Annual Review.
1 Establishing A Horticulture Business. Next Generation Science / Common Core Standards Addressed! RST.11 ‐ 12.7Integrate and evaluate multiple sources.
Computers Are Your Future Tenth Edition Chapter 13: Systems Analysis & Design Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall1.
3 1 Project Success Factors u Project management important for success of system development project u 2000 Standish Group Study l Only 28% of system development.
1 14. Project closure n An information system project must be administratively closed once its product is successfully delivered to the customer. n A failed.
Advisor: Dr. Edwin Jones 1 Client: Paul Jewell ISU Engineering Distance Learning Facility May01-13 Design Team: David DouglasCprE Matt EngelbartEE Hank.
STEP 4 Manage Delivery. Role of Project Manager At this stage, you as a project manager should clearly understand why you are doing this project. Also.
McGraw-Hill/Irwin © 2003 The McGraw-Hill Companies, Inc., All Rights Reserved. 6-1 Chapter 6 CHAPTER 6 INTERNAL CONTROL IN A FINANCIAL STATEMENT AUDIT.
Introducing Project Management Update December 2011.
14-1 CHAPTER 14 McGraw-Hill/Irwin © 2008 The McGraw-Hill Companies, Inc., All Rights Reserved. Cost Analysis for Planning.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
COSTING AND THE VALUE CHAIN CHAPTER 18 PAGE# 794 Faisal
Project Management. Introduction  Project management process goes alongside the system development process Process management process made up of three.
IS2210: Systems Analysis and Systems Design and Change Twitter:
Software Requirements Specification Document (SRS)
Grid Operations Report To ERCOT Board Of Directors December 16, 2003 Sam Jones, COO.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 2 Managing the Information Systems Project 2.1.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Finish Ethics Next Week Research Topics in HCI CS 321 Human-Computer Interaction.
October 25,  Benefit Year Earnings (BYE): Root Causes Identified:  Agency Causes  Staff fails to follow-up with claimant at the time continued.
Project Management Methodology Project Closing. Project closing stage Must be performed for all projects, successfully completed or shut off by management.
INTRODUCTION CSE 470 : Software Engineering. Goals of Software Engineering To produce software that is absolutely correct. To produce software with minimum.
A six-pack of major RFP problems
Managing the Project Lifecycle
Systems Analysis and Design in a Changing World, 4th Edition
Personal Financial Planning
MANAGEMENT ACCOUNTING
د. حنان الداقيز خريف /28/2016 Software Quality Assurance ضمان جودة البرمجيات ITSE421 5 – The components of the SQA.
Financial Merchandise Management
Financial Merchandise Management
Accounting, Fifth Edition
2011 POPULATION AND HOUSING CENSUS PREPARATORY WORKS
Chapter 22, Part
Completing and Presenting the Class Project
Overview Headlines RSP – Progress Overview General progress report
Presentation transcript:

Chapter 11 Software Development Horror Stories

Sampling of Software Problems = Faye Starman gets an electric bill for $6.3 million instead of $63 due to a data entry error = Someone is denied a new credit card because her Mother’s credit history is merged with her own = Six people die due to excessive radiation from a therapeutic linear accelerator

More Sample Software Problems = The Mars Climate Orbiter spacecraft crashes into the surface of Mars due to a simple unit-of-measure conversion error = Several Blackhawk helicopters crash killing several people due to radio signals interfering with on board computer systems

More Sample Software Problems = $125 million is squandered on a hotel reservation system, in which proper project management should have revealed that this project was hopelessly out-of-control = Software development projects frequently produce systems that are not used because users deem them unusable

Preventing Horror Stories through Software Engineering = Software engineering can address a significant number of the previously discussed software failures = Certain failures cannot be addressed by software engineering and proper system design, such as ensuring that users are adequately trained, but it can mitigate the effects of such problems

Preventing Horror Stories through Software Engineering = Proper software engineering can address the following issues: = Adequate testing = Proper project management = Improved algorithm design = Improved data design

CONFIRM Development Objectives = Design, develop, operate, and maintain a new state-of-the-art reservation processing system to be used world- wide. = Design and develop interfaces with airline reservation systems so consumers could make airline, hotel, and car rental reservations through a single computerized system.

CONFIRM Development Objectives = Market the reservation system and other communications services to customers for profit. = Convert each of the partners' (Hilton, Marriot, and Budget Rent-A-Car) current reservation systems to the new integrated system. = Integrate the reservation systems with decision support systems.

CONFIRM Case Study: = In October 1987 Marriott, Hilton, Budget Rent-a-car, and AMRIS form a consortium to develop and run CONFIRM, with AMRIS managing the development. = The project is to be developed in two phases and be completed by June 1992.

CONFIRM Case Study: = On May 24, 1988, AMRIS announces the beginning of the CONFIRM design phase through a press release. = On December 30, 1988, AMRIS presents the base design of the system to to the members of the consortium. Marriott objects that the functional specifications are not sufficiently detailed to convey user needs to the developers.

CONFIRM Case Study: = In March 1989, AMRIS presents a development plan which is found to be unacceptable by the consortium members. = In August 1989, AMRIS releases project financial estimates to consortium members. Based on these estimates, the other consortium members decide to remain involved in the project.

CONFIRM Case Study: = The statements regarding the financial estimates are later found to severely underestimate personnel and operating costs. = In September 1989, AMRIS finally completes the design phase to the consortium members' satisfaction. The cost estimate for the project increases to $72.6 million from $55 million.

CONFIRM Case Study: = In January 1990, AMRIS misses its first contractual deadline for completion of the terminal-screen design. = In February 1990, a second project milestone concerning analysis of the business area for the system is missed. AMRIS admits to being 13 weeks behind schedule, but claims that the original deadline can still be achieved.

CONFIRM Case Study: = In February 1991, AMRIS presents the consortium members with a revised development plan that provides Marriott with its full functionality by March Marriott later claims that AMRIS knew it could not meet the new deadline and forced employees to artificially inflate their timetables or face firing or reassignment.

CONFIRM Case Study: = In the revised development plan, AMRIS raises the price of the project to $92 million. = In October 1991, the president of AMRIS and about 20 additional employees resign.

CONFIRM Case Study: = On May 1, 1992 the new president of AMRIS acknowledges that the "system interfaces and databases are insufficient to providing the necessary performance and reliability". He also attributes the situation to AMRIS's misrepresentation of the status of the project.

CONFIRM Case Study: = Finally, in July 1992 after spending $125 million on the effort, the consortium disbands.

Questions for Discussion on the CONFIRM Case Study = If you were a partner in the consortium developing CONFIRM, when would you have terminated your involvement and why? = Which SE deliverables should have been tell-tale indicators that the project was off-track? = Be specific. How would you evaluate a deliverable as being inadequate?

Questions for Discussion on the CONFIRM Case Study = What violations of professional ethics occurred in the CONFIRM chronology? = If you were a developers on the CONFIRM project, would you have altered the time table as directed by management or face firing? What if you were economically dependent on this job?

Questions for Discussion on the CONFIRM Case Study = No risk analysis was carried out on the project. What potential stumbling blocks might a thorough risk analysis have highlighted? = What suggestions to reduce the risk level of this development project might have been made? = As manager what would you have done differently?

Questions for Discussion on the CONFIRM Case Study = The development plan scheduled meetings between the developers and user representatives only once a month? What problems might this cause? What sort of developer-user relationship would you establish for this project?

Questions for Discussion on the CONFIRM Case Study = If you were interviewing with a company that appeared to have an excessive number of openings, what questions might you ask as a result of being familiar with the CONFIRM case study? = What questions would you ask a potential employer, If you were considering being hired as a developer for a large-scale project?