1. Requirements Management It’s a Team Sport Gerard van der Pol Borland Software Corporation

2. Have you ever… …misunderstood a customer request? …ended up delivering a lot more functionality than you originally estimated? …missed a deadline because the customer changed the specifications at the last minute? …found a software defect caused by an incomplete change? …forgotten to notify someone when a change was made? Requirements Management Problems

3. The Source of Software Defects Requirements Errors (56%) Other Errors (10%)Coding Errors (7%) Design Errors (27%) Source: James Martin, An Information Systems Manifesto

4. The Cost to Fix Software Defects Source: James Martin, An Information Systems Manifesto RequirementsErrors(82%)RequirementsErrors(82%) Design Errors (13%) (13%) Other Errors (4%) Coding Errors (1%)

5. Relative Cost of Fixing a Defect Source: Boehm, Barry W. Software Engineering Economics. Englewood Cliffs, NJ: Prentice-Hall, 1981 0 10 20 30 40 50 60 70 RequirementsDesignCodeDevelopment Testing Acceptance Testing Operation Relative Cost to Correct a Defect

6. Requirements = Blueprints

7. Even small errors can lead to big problems.

8. How Are Req’s Managed Today? Most organizations use manual and document-based methods –“Sticky” notes –Telephone calls –Email –White boards –Word processors –Spreadsheets –Desktop databases Software Requirements Specification

9. Requirements Development vs Management Analyze, Document, Review, Negotiate MARKETING, CUSTOMERS, MANAGEMENT Baselined Requirements Reqs. Development Reqs. Management Requirements Change Process revised requirements MARKETING CUSTOMERS MANAGEMENT PROJECT CHANGES 1-9

10. Requirements User Documentation Changes can come from many different sources. Help Desk CCB (Approval Process) Customer/ User Design Code Test New Feature New Reqmt Business Area Coder/ Tester Defect A Change Management Process

11. Time/change Ver 1.0  Ver 1.1  Ver 2  Ver 2.0  Ver 1.1  Ver 1.1  Ver 1.0  Ver 1.0  Ver 1.0  Ver 1.0  Ver 1.2  Ver 2.1  Ver 3.0  Ver 1.2  Ver 1.2  Ver 2.2  Ver 1.3  Ver 2.0  Ver 1.4  Ver 1.5  Ver 1.6  = Project Scope 1/1/2001 BASELINE Requirements = Current Version “Snapshot in time” of Requirements Project Baseline

12. WhyWhatHowWhenWhere Link Customers to Reps WHY 1012 ZIP code Capability WHAT 1013 Client_Info Table HOW 1014 Postal Code View & Create HOW 1016 ZIP Code Lookup HOW 1015 Analysis Procedures WHEN1022 DB Design WHEN1017 Create Procedures WHEN1018 GUI Design WHEN1019 Implementation WHEN1020 Interface Design Task WHEN1021 Check Zoom Button TD: Test (Manual) TestDirector_Demo Starvm.app StarTeam StarDraw\SourceCode\ checkInBoxes State TD:Test (WR-AUTOMATED) TestDirector_Demo StarDraw.h StarTeam StarDraw\SourceCode\ Initial State TD:Test (MANUAL) TestDirector_Demo Stardoc.h StarTeam StarDraw\SourceCode\ Requirements Management in Practice

13. Configuration, Change, and Project Management It’s a Team Sport Quality Assurance / Testing Requirements Management AnalyzeAnalyzeDesignDesignDevelopDevelopDeliverDeliver Object-Oriented Analysis and Design Together VS.NET Configuration and Change Management Requirements ManagementCaliberRM Project Management and Estimation Microsoft Project, EstimatePro Unit TestingTest AutomationTest Management Integrated Development Environment Visual Studio.NET

15. Software Delivery Optimization DesignDevelop Manage Test Deliver Define

16. DesignDevelop Manage Test Deliver Define Business Analytics Resource Optimization Asset Utilization Portfolio Planning & Management Doing the RIGHT SOFTWARE Financiers and Business Sponsors WHAT?WHO? Process Automation Audits & Metrics for Compliance Dashboards & Production Analytics Project & Requirements Management Decision Makers and Managers Doing SOFTWARE RIGHT Software Creation and Management Artifact Repository Doing Software Software Creators Software Delivery Optimization Role Optimized

17. Thank You Borland Software Corporation