1. Requirements Management Plan - Documents Author: Oldřich Vašut Course: SAN 2008

2. Outline • Introduction • What is RM Plan? • RM Plan description, relationships to other plans • Documents

3. Introduction to Requirements Management • Requirements management involves establishing and maintaining agreement between customer and developer on both technical and non-technical requirements. This agreement forms the basis for estimating, planning, performing, and tracking project activities throughout the project and for maintaining and enhancing developed software.

4. Introduction to RM - Key activities • planning the requirements phase • establishing the requirements process • controlling requirements changes • minimizing the addition of new requirements (scope creep) • tracking progress • resolving issues with customers and developers • holding requirements reviews

5. Requirements Management Plan • A requirements management plan is a component of the project management plan. Generally, the purpose of RM is to ensure customer and developer have a common understanding of what the requirements for an undertaking are. Several subordinate goals must be met for this to take place: in particular, requirements must be of good quality and change must be controlled. The plan documents how these goals will be achieved. Depending on your project standards, a variety of sections might be included in your RM plan.

6. Sections of RM Plan • introduction to RM and document overview • document scope • issues affecting implementation of the plan, such as training on the RM tool • applicable documents, such as policies and standards • terms and definitions used in the plan - if your use of the term “requirement” includes several requirement categories, define it here • methods and tools that will be used for the RM process (or the requirements for selecting a tool if one is not selected) • the RM process, including any diagrams of the process • authorities and responsiblities of participants • strategy for achieving requirement quality, including traceability and change control

7. Relationship to other plans The following is a mapping of Requirements Management Plan sections to artifacts that may contain complementary information:

8. Document based Requirement Artifacts and Types • Vision (VIS) – Stakeholder Need (NEED), Product Feature (FEAT) • Glossary (GLS) – Term (TERM) • Business Rule Reference (BR) – Business Rule (BR) • Use-Case Model Survey • Use-Case Specification (UC) – Use-Case Detail Requirement (UCDR) • Supplementary Specification (SS) – Supplementary Requirement (SUPP) • Test Plan (TPL) – Test Plan Requirement (TPR) • Test Case (TC) – Test Requirement (TR) • Issues (ISU) – Issue (ISS) • Assumptions (ASM) – Assumption (ASM)

9. Traceability Criteria

10. RM Plan Template • 1. Introduction1.1 Purpose1.2 Scope1.3 Definitions, Acronyms, and Abbreviations 1.4 References 1.5 Overview • 2. Requirements Management • 2.1 Organization, Responsibilities, and Interfaces • 2.2 Tools, Environment, and Infrastructure • 3. The Requirements Management Program • 3.1 Requirements Identification • 3.2 Traceability 3.2.1 Criteria for <traceability item> • 3.3 Attributes 3.3.1 Attributes for <traceability item> • 3.4 Reports and Measures • 3.5 Requirements Change Management 3.5.1 Change Request Processing and Approval 3.5.2 Change Control Board (CCB) 3.5.3 Project Baselines • 3.6 Workflows and Activities • 4. Milestones • 5. Training and Resources

11. References • Requirements Management Plan Example http://www.ibm.com/developerworks/rational/library/4421.html • REQUIREMENTS MANAGEMENT PLANhttp://www.baz.com/kjordan/swse625/htm/rm_plan3.htm • REQUIREMENTS MANAGEMENT http://www.jiludwig.com/Requirements_Management.html • Requirements Management – SRM http://www.akamonitor.cz/2007/08/sprva-poadavk-v-studijnm-plnu-manaersk.htm • Requirements Management Plan Templatehttps://cabig.nci.nih.gov/workspaces/TBPT/Templates/caBIG_Reqts_%20Mgt_Plan.doc

12. End • Thanks for favour.