Process Area : Requirement Management (REQM) By: Amna Rehmat Maria Habib Sana Ahmed

Agenda: Purpose Related Process Areas Goals Practices Practical Implementation Issues Tools Questions

Why Focus on Requirement? According to the SEI National Software Capacity Study [SEI 90], the top 2 factors that contribute to the failure of system development :  1. Inadequate requirements specification (4.5)  2. Changes in requirements (4.3) According to the SEI [Christel 92], problems of requirements elicitation can be grouped into 3 categories:  1. Problems of Scope  2. Problems of Understanding  3. Problems of Volatility

Purpose: The purpose of requirements Management (REQM) is to manage the requirements of the project’s products and product components and to identify inconsistencies between those requirements and the project’s plans and work products

Related Process Areas:

Related Process Areas (contd.): Configuration Management: Project Planning Project Monitoring And Control Risk Management Change in Requirements Revise Plan according To change (if required) Revised Project Plan History of CR Work product Activities Monitor and control Corrective Actions (CA) (if needed) History of CA Requirements Identify Risk and Critical Areas Adaptive Measures Track Change Requests Assignment of Change Requests to Baselines Cr assigned to baseline History of CR

Specific and Generic Goals & Practices

SubPractices: 1.Establish Criteria for Distinguishing Req.provider 2.Establish objective criteria for Evaluation and Acceptance of Reqst Subpractices: 1.Assess the impact of requirements on existing commitments. 2. Negotiate and record commitments. Sub practices 1.Document all requirements and requirements 2. Maintain the requirements change 3. Evaluate the impact of requirement changes 4. Make the requirements and change data available to the project. Sub practices: 1.Review the project’s plans, activities, and work products 2. Identify the source of the inconsistency 3. Identify changes that need to be made. 4. Initiate corrective actions.

GG 1 Achieve Specific Goals GG 2 Institutionalize a Managed Process GG 3 Institutionalize a Defined Process GG 4 Institutionalize a Quantitatively Managed Process GG 5 Institutionalize an Optimizing Process GP 1.1 Perform Specific Practices GP 2.1 Establish an Organizational Policy GP 2.2 Plan the Process GP 2.3 Provide Resources GP 2.5 Train People GP 2.10 Review status with higher Level Management GP 2.7 Identify & Involve relevant Stakeholders GP 2.9 Objectively evaluate adherence GP 2.4 Assign Responsibility GP 2.8 Monitor & Control the Process GP 2.6 Manage Configurations GP 3.2 Collect Improvement Information GP 3.1 Establish a Defined Process GP 4.2 Stabilize Subprocess Performance GP 4.1 Establish Quantitative Objectives for the Process GP 5.2 Correct Root Causes of Problems GP 5.1 Ensure Continuous Process Improvement

REQM: Work Products Requirements Collection Checklist: Volere Volere Volere Checklist Checklist Checklist Requirements Specification Review Checklist: Review Checklist Review Checklist Review Checklist Review Checklist Peer Review: Peer Review Peer Review Peer Review Peer Review Change Request: Change Request Change Request Change Request Change Request

REQM: Work Products (contd.) Traceability Matrix: Forward/Backward Forward/Backward Forward/Backward Horizontal and Vertical Horizontal and Vertical Horizontal and Vertical Horizontal and Vertical Traceability Matrix Traceability Matrix Traceability Matrix Traceability Matrix REQM Plan: REQM Plan Template REQM Plan Template REQM Plan Template REQM Plan Template

Issues: According to SEPG Conference March 10, 2004 REQM, PP and SAM received the most issues. Some strong redundancies with configuration management. REQM looks like some kind of “specialization” of CM. Bi-directional traceability requires clarification (could be explained through examples) Horizontal and Vertical traceability is also ambiguous. Breaking out REQM and RD leads to confusion for practicing engineers. Most often these processes for the organization are defined as one. This makes it a little more difficult to evaluate on a SCAMPI.

Tools: Rational RequisitePro:  Powerful requirements engine.  Traceability.  Change analysis and notification.  Baseline creation and comparison.  Integrated requirements management. Telelogic DOORS :  A collaborative Requirements Management environment  The ability to manage changing requirements  Powerful Traceability created easily  Scalability to address all your Requirements Management needs