IN4MATX 43 Lecture Notes - Lecture 4: Requirements Engineering, Waterfall Model, Requirements Analysis
Document Summary
The task was too large and complex. Payroll system: 160 state departments, 40+ medical/dental plans, State/city gov"t is less efficient than the private sector. State/city rules require inadequate programming languages to be used. The contractor, sap public services/pricewaterhousecoopers, has a flawed management structure. Software must conform to the reality of payroll contracts, laws, billing policies. Part of the goal is to update systems in place since the 1970s. Doesn"t matter how we get there, as long as we get there. The companyis still trying to figure out what product to build. No one knows inside the company what they are building. Requirements = what the software should do (without saying how to do it) [we] have grown to care about requirements because we have seen more projects stumble or fail as a result of poor requirements than for any other reason . Studies show that many of the key contributors to project failures originate or relate to requirements.
