1. REQUIREMENTS - WHY WHAT AND HOW? Steve Chenoweth & Chandan Rupakheti CSSE 371 Chapters 1 - 4 Requirements Text. Question 6

2. WHY REQUIREMENTS “Why not just ask them what they want, they tell you, and you build it?”

3. Some facts 3  250 billion dollar industry  31% projects cancelled(money lost 81 billion dollars)  52.7% cost 189% of their original estimates

4. Biggest Reasons for Project Success and Failure

5. Project Failure  Lack of user input (13%)  Incomplete requirements (12%)  Changing requirements (12%) Question 1

6. Project Success  User involvement (16%)  Executive management support (14%)  Clear statement of requirements (12%)

7. 7

8. Defects by Development Phase  Requirements – 31%  Design – 25%  Coding – 12%  Documentation – 16%  Bad fixes – 16%

9. Cost to Fix Errors 9 Requirements Design Coding Unit Test Acceptance Test Maintenance 1 5 25 50 125 500

10. Why ? 10  Requirements errors are likely to be the most common class of error  Requirements errors are likely to be the most expensive to fix

11. WHAT IS A SOFTWARE REQUIREMENT? “I’d like to see the web pages in green…”

12. What is a Software Requirement? 12 1. A software capability needed by the user to solve a problem to achieve an objective 2. A software capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification or other formally imposed documentation Question 2

13. What is Software Requirements Management? 13  The process of systematically, eliciting, organizing and documenting requirements for the software system, and a process that establishes and maintains agreement between the customer and the project team on the changing requirements of the system. Question 3

14. 14

15. What does it involve? 15  Understand the need - the problem to be solved  Propose features - how the need will be resolved  Requirements are the specific conditions that are imposed on the solution

16. 16 Needs Features Requirements Problem Domain Solution Domain Question 4

17. SOFTWARE LIFECYCLE PROCESS MODELS

18. Waterfall Model  Manufacturing life cycle model  Assumes  multi-stage development cycle  completely separate stages  output of one stage is input for next  each stage complete before next is begun

19. Waterfall Stages Requirements DesignCodingTestingMaintenance

20. Advantages  Much better than chaos!  Clearly defined stages help with  planning, scheduling  management, organization  accountability, control

21. Disadvantages  Not very practical (do not know requirements in the beginning)  Customer sees nothing until last step  Change is Anathema

22. Spiral Model 22  Incremental  more feedback from customer  Risk analysis  more rigorous analysis of risk at each stage

23. Spiral Model

24. Iterative (or Incremental) Approach  Four phases  Inception  Elaboration  Construction  Transition 24

25. Iterative(or Incremental) Approach 25  An iteration is a sequence of activities with an established plan and evaluation criteria, resulting in an executable of some type  Each phase goes under a # of iterations

26. Management Environment Business Modeling Implementation Test Analysis & Design Preliminary Iteration(s) Iter. #1 Phases Iterations Iter. #2 Iter. #n Iter. #n+1 Iter. #n+2 Iter. #m Iter. #m+1 Deployment Configuration Mgmt Requirements ElaborationTransitionInceptionConstruction Workflows group activities logically In an iteration, you walk through all activities Process Workflow Support Workflow Rational Unified Process Model Question 5

27. Software Development 27  Is this a team activity? Why?

28. Requirements Team Skills 1. Analyzing the Problem 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 5. Refining the System Definition 6. Building the Right System