1. 8/28/2005ECEN5543 Req Elicitation1 Targets of Requirements Engineering ECEN 5543 SW Engineering of Standalone Programs University of Colorado, Boulder

2. 8/28/2005ECEN5543 Req Elicitation2 Vision Document Should not be long Should not describe firm requirements in detail Output of requirements elicitation techniques, workshops in particular –Not created in the order of the outline –Information gathered, then structured

3. 8/28/2005ECEN5543 Req Elicitation3 Vision Template 1.Introduction –1.1Purpose –1.2Scope –1.3Definitions, Acronyms, and Abbreviations –1.4References –1.5Overview

4. 8/28/2005ECEN5543 Req Elicitation4 Vision Template Section 2 2.Positioning –2.1Business Opportunity –2.2Problem Statement –2.3Product Position Statement

5. 8/28/2005ECEN5543 Req Elicitation5 Vision Template Section 3.1 – 3.6 3.Stakeholder and User Descriptions –3.1Market Demographics –3.2Stakeholder Summary –3.3User Summary –3.4User Environment –3.5Stakeholder Profiles 3.5.1 –3.6User Profiles 3.6.1

6. 8/28/2005ECEN5543 Req Elicitation6 Vision Template Section 3.7 - 3.8 3.Stakeholder and User Descriptions 3.7 Key Stakeholder or User Needs 3.8 Alternatives and Competition –3.8.1 –3.8.2

7. 8/28/2005ECEN5543 Req Elicitation7 Vision Template Section 4 4.Product Overview 4.1Product Perspective 4.2Summary of Capabilities 4.3Assumptions and Dependencies 4.4Cost and Pricing 4.5Licensing and Installation

8. 8/28/2005ECEN5543 Req Elicitation8 Vision Template Section 5, 6, 7 5.Product Features –5.1 –5.2 6.Constraints 7.Quality Ranges

9. 8/28/2005ECEN5543 Req Elicitation9 Vision Template Section 8, 9 8.Precedence and Priority 9.Other Product Requirements –9.1Applicable Standards –9.2System Requirements –9.3Performance Requirements –9.4Environmental Requirements

10. 8/28/2005ECEN5543 Req Elicitation10 Vision Template Section 10 10.Documentation Requirements –10.1User Manual –10.2Online Help –10.3Installation Guides, Configuration, and Read Me File –10.4Labeling and Packaging

11. 8/28/2005ECEN5543 Req Elicitation11 Vision Template Appendix A Feature Attributes A.1 Status A.2 Benefit A.3 Effort A.4 Risk A.5 Stability A.6 Target Release A.7 Assigned To A.8 Reason

12. 8/28/2005ECEN5543 Req Elicitation12 IEEE 830 Software Requirements Specification (SRS) This is not created all at once Some parts come straight from Vision Doc However, all of this must be understood and specified eventually May be maintained in a Requirements DB Should be accessible to team on the web Should be baselined and managed

13. 8/28/2005ECEN5543 Req Elicitation13 IEEE Std 830 SRS Table of Contents

14. 8/28/2005ECEN5543 Req Elicitation14 Overall description Product perspective Product functions User characteristics Constraints Assumptions and dependencies

15. 8/28/2005ECEN5543 Req Elicitation15 Specific requirements External interfaces Functions Performance Logical database Design constraints –Standards compliance

16. 8/28/2005ECEN5543 Req Elicitation16 Specific requirements – cont. Software system attributes –Reliability –Availability –Security –Maintainability –Portability –Accessibility

17. 8/28/2005ECEN5543 Req Elicitation17 Organizing the detailed requirements System mode User class Objects Feature Stimulus Response Functional hierarchy