IN4MATX 43 Lecture Notes - Lecture 2: Requirements Analysis, Software Development Process, Failure Cause
Document Summary
Top software failure causes: requirement issues, lack of user input/involvement. Incomplete requirements and specifications: changing requirements and specifications. Lack of rigor/formality: lack of discipline in the development process, lack of methodical usage of metrics. Lack of resources: requirements: what the software should do without saying how it should do it. So many projects stumble or fail because of poor requirements than any other reason. Studies have shown have that many of the key contributors to project failures originate or relate to requirements. 31% of projects cancelled before they were even completed: billions of dollars wasted on cancelled, unused, or unusable projects. 52. 7% of projects were more than 189% over budget on delivery. Requirement defects are expensive too: represent more than 70% of rework costs, rework consumes about 30-50% of total project budget. Lack of user input/involvement is listed as the most frequent problem: maintenance costs are the highest in the software life cycle.
