MAJOR SOFTWARE FAILURES, WHY THEY FAILED AND LESSONS LEARNED BY AKPABIO UWANA.

Slides:



Advertisements
Similar presentations
Test process essentials Riitta Viitamäki,
Advertisements

Lecture 8: Testing, Verification and Validation
McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 20 Systems Operations and Support.
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
Project What is a project A temporary endeavor undertaken to create a unique product, service or result.
OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 What is software? Software errors, faults and failures Classification.
Software Development Problems Range of Intervention Theory Prevention, Treatment and Maintenance Planning, Development and Use Cost of Intervention.
OHT 14.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software quality infrastructure components The need for procedures and.
Factors to be taken into account when designing ICT Security Policies
Oracle Database Administration. Rana Almurshed 2 course objective After completing this course you should be able to: install, create and administrate.
Software Quality Assurance
High Level: Generic Test Process (from chapter 6 of your text and earlier lesson) Test Planning & Preparation Test Execution Goals met? Analysis & Follow-up.
Planning and Tracking Software Quality Yordan Dimitrov Telerik Corporation
 Software Software  Program vs Software Products Program vs Software Products  Software Characteristics Software Characteristics  Software Crisis.
1 Implementing Computer Applications in Counseling James P. Sampson, Jr. Florida State University Copyright 2003 by James P. Sampson, Jr. All rights reserved.
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
Cmpe 589 Spring Software Quality Metrics Product  product attributes –Size, complexity, design features, performance, quality level Process  Used.
Why use RequisitePro RequisitePro is a comprehensive tool that supports any of today's requirements management processes. The predominant requirements.
PROJECT MILESTONES Group Presentations: ~ 5 mins presentations.
Networking Basics Lesson 1 Introduction to Networks.
Software Project Failure Software Project Failure Night Two, Part One CSCI 521 Software Project Management.
Chapter 3: Software Maintenance Process Omar Meqdadi SE 3860 Lecture 3 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Software Software is omnipresent in the lives of billions of human beings. Software is an important component of the emerging knowledge based service.
ITIL and the Help Desk Craig Bennion University of Utah
The Software Quality Assurance System By Jonathon Gibbs Jonathon Gibbs (jxg16u) 26 th November 2009.
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
FCS - AAO - DM COMPE/SE/ISE 492 Senior Project 2 System/Software Test Documentation (STD) System/Software Test Documentation (STD)
Software Evaluation Catherine McKeveney Medical Informatics 1st March 2000.
CH10: Delivering the System help users to understand and feel comfortable with our product * Training * Documentation TECH Computer Science.
Software Metrics and Reliability. Definitions According to ANSI, “ Software Reliability is defined as the probability of failure – free software operation.
Appendix C: Designing an Operations Framework to Manage Security.
Advantage of File-oriented system: it provides useful historical information about how data are managed earlier. File-oriented systems create many problems.
Tutorial 1: Date: 19/09/2012 Instructor: Hanif Ullah
A Gift of Fire, 2edChapter 4: Can We Trust the Computer?1 Can We Trust the Computer?
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 24 Delivering the System.
COMPUTER SOFTWARE Management Information Systems.
Communication at Work – Following Directions Business Information Management I.
Software Requirements and Design Khalid Ishaq
Data Gathering Techniques 27 th February Data Gathering Techniques System requirements specify what the system must do or what property or quality.
1 EE29B Feisal Mohammed EE29B: Introduction to Software Engineering Feisal Mohammed Ph: x3156.
CHAPTER 2 TYPES OF BUSINESS INFORMATION SYSTEM. INTRODUCTION Information System support business operations by processing data related to business operation.
Defect Classes and the defect repository
Introduction to Testing. Topics Who are we? Who are we? Software Testing Definition and Goals Software Testing Definition and Goals Facts and Numbers.
CISB113 Fundamentals of Information Systems IS Development.
GCSE ICT Systems Analysis. Systems analysis Systems analysis is the application of analytical processes to the planning, design and implementation of.
Chapter 9: Design Guidance and Design Rationale Kevin Juang David Bate Will Rodes.
Objectives Understand Corrective, Perfective and Preventive maintenance Discuss the general concepts of software configuration management.
Project Management. Projects and Project Managers Project – a [temporary] sequence of unique, complex, and connected activities having one goal or purpose.
TESTING FUNDAMENTALS BY K.KARTHIKEYAN.
Project Management Overview U08784Software Project Management Rosemary Phillimore.
Why Cryptosystems Fail R. Anderson, Proceedings of the 1st ACM Conference on Computer and Communications Security, 1993 Reviewed by Yunkyu Sung
Workshop 1 – Implementation of the new CAP Michael Cooper Director – UK Co-ordinating Body 12 September 2012.
Observing the Current System Benefits Can see how the system actually works in practice Can ask people to explain what they are doing – to gain a clear.
Text INTERNAL February 11, 2011 Problem Solving. INTERNAL Tech Republic’s railway department wants a solution Tech Republic’s railway department.
Project Planning Goal 1 - Estimates are documented for use in tracking and planning project. Goal 2 - Project Activities and commitments planned and documented.
Standardized Fault Reporting in Electronic Commerce Software University of St. Thomas MBIF 705 – Foundations of Electronic Commerce Jeff D. Conrad December.
Software Maintenance1 Software Maintenance.
CS 310 Ch 4: Software Processes Software process: a set of activities that lead to a software system specification design and implementation validation.
Project Failure RYAN BIBBY – PROJECT 5 ASSIGNMENT 2 TASK 1.4.
Mary Grace Satoya III-BLIS. The difficulties appear to involve 3 group of people Computer center and systems personnel Suppliers of hardware and software.
Verification and Testing
Software Project Planning and Tracking
IEEE Std 1074: Standard for Software Lifecycle
Quickbooks training in Chandigarh. Quickbooks Customer Service,s Features.
Fail Fail Poor Communication Lack of Documentation Poor Execution.
What is software quality?
Quality Measurable characteristic Cyclomatic complexity Cohesion
Welcome to Corporate Training -1
What is software quality?
Presentation transcript:

MAJOR SOFTWARE FAILURES, WHY THEY FAILED AND LESSONS LEARNED BY AKPABIO UWANA

What is a software? A software is general term used to describe a collection of computer programs, procedures and documentation that perform some tasks on a computer system; they are designed according to user specifications.

What is software failure? Can be generally defined as “a failure of the delivered system to comply with the specifications agreed”. –Suits hardware failure better –Changing specs in software –Fault tolerance systems We need a clearer definition of software failure.

What is software failure (2)? Failure is determined by customer satisfaction Can be defined as “failure of delivered system to meet users expectation and inability of the system to aid the user do any useful work”.

Causes of Software failures The general causes of software failures are: –Lack of communication –Incorrect documentation –Software complexity –Programming errors –Frequent changes in requirements –Time pressure

Causes of software failures (2) –Individual egos –Software development codes –Lack of resources –Commercial pressures –Poor project management –Administrative Bottlenecks

Software system failures U.S. bank account holders –Programming error –Error fixed Lesson learned here is: –Employ professional programmer –Have good idea of what to do

Software system failures (2) Heathrow terminal 5 luggage system –Prevented passengers from checking in their luggage –Delay in completion of building programme due to time –Rushed testing –Lack of training given to staff on use of software –Impact on operations Here we learn that: – software failures do not only occur due to programming errors but also lack of training, communication and time constraints.

Conclusion