Examples Of Software Failure

Table Of Content

Description

Page Number

Front Cover Page 1,2

Table of Content 3

1.0 What is Software and Software Failure 4

2.0 Reason for Software Project Failure

2.1 Failing to Plan 5

2.2 The Triple Constrains 6

2.3 No User Involvement

2.4 Testing

2.5 Poor User Interface 7

3.0 Examples of Software Failures

3.1 Amazon Christmas Software Glitch

3.2 Airports in UK Grounded

3.3 Toyota Recalled Toyota Prius 8

3.4 Emergency Numbers Went Offline

3.5 Apple Forced to Pull iOS 8 Update 9

4.0 Conclusion 10

5.0 Reference 11

1.0 What is Software and Software Failures?

Software is everywhere. Software is set of machine readable instructions also known as “machine code” that direct the computer on how and what to execute. Software is usually written

A project plan and a professional project team are needed. One reason for failure is working backwards from a set finish date. “If you fail to plan you plan to fail”. Project management team should understand customer’s requirement and what to do in order to solve their problem. Project management should also have a “bigger picture” of the system to know what is the software project is going to be in the future. Failure to establish upper-management commitment to the project will also lead the software project to fail. Project plan will always evolves during the development process, therefore, the schedule, cost estimate and risk will have to be revised from time to time. In the planning phase, the project management team should be planning for a “Big Picture” for the software

From this report, I feel that I have shown numerous examples of system failure. The project can run with the Software Development Life Cycle. The project management team should properly understand the problem that the client is facing and their requirement before the development stage starts. After understanding what the client needs and requirement, the project team should start designing. Choosing the methodology for the project is subjected. The project team may use Waterfall Model, Spiral Model, Rapid Prototyping and more. Waterfall Model is the safest among all due to each phase have to be completed and processed one at a time. Waterfall model works well for smaller project where requirements are very well understood. After the planning stage, design stage takes place, the desired features and detailed operations are described to the client. After planning, the development team would start taking the development stage. In development stage, the real coding is written based on the plan. Integration and testing is the next stage. The team brings all the pieces together into a testing environment, then checks for errors and bugs. If the testing stage passes, the team would start the final stage that is implementation. The software and hardware are put together into production in the client’s organization and runs the business to solve their problem. Maintenance is