Requirement Determination Process (RDP)

By: Sourabh Arya

21 December 2009

Agenda• Overview Of RDP• Main Steps• Sub Steps• Questions

Overview Of RDP• RPD: It enables you to, obtain, verify & communicate effective

requirements that brings value to you, HP & client• RDP is a proactive, value- added approach to determining

requirements developed by EDS in 1992.• RDP is a set of guidelines to effectively listen to information provided

by client’s and translate the same into a set of system specific feasible requirements

• Benefits of RDP:o Increased business Value through better solution offeringo Reduced cost of correcting defects & failure due to ill stated

requirements

Steps to Determine Requirements• Plan/ Manage: to prepare for & manage the requirements

• Obtain: Collect information from various source

• Understand: Analyze the obtained information

• Validate: Confirm mutual understanding of the requirements

• Evaluate: Asses the process

Step 1: Planning/Manage

• Allocate HP Resource• Identify the client resource• Determine RDP techniques & standards• Determine Evaluation parameters

o Identify Key Success Parameters (KSF) Within Budget On Schedule

o Identify causes of concern Enlarged scope Additional needs

• Build the plan• Review plan with the client of RDP team

Continued • Manage the plan

o Continuous monitoring of project scopeo Identify potential risk and timely resolution of the same

Step 2: Obtain• Determine requirement sources• Determine/ Confirm Obtain Techniques• Execute Obtain Techniques

o Document Research: Client literature etco Facilitation: Joint Application Design (JAD) Sessionso Observationo Prototyping: computer aided software engineering (CASE) tool to build

prototypes for process understandingo Surveyo Interviewing

• Stored the obtained information

Step 3: Understand

• Extract requirements• Link to source document• Perform root cause analysis• Verify consistency and completeness• Add verification criteria• Determine appropriateness of requirements• Determine requirements to be validated

ContinuedTechniques to understand requirements• Facilitation: group meetings to obtain consensus• Data Modeling & Process Modeling: Technique to verify & understand

the completeness of the requirement• N fold Structured walkthroughs: application of multiple structured

walkthroughs to increase Understanding & Validity of requirements• Analytic Hierarchy Process: To determine relative value of each

requirement in listo Forced pair Matrix

• Ambiguity Analysis: To test the ambiguity & conflicting expectation or requirements during requirement determination

• Expectation Limitation: a technique to expose un realistic expectation

Step 4: Validate• Determine validation participation• Determine levels of detail• Determine confirm validation techniques:

o Facilitationo Data Modeling & Process Modelingo N fold Structured Walkthroughso Analytic hierarchy Process

Forced Pairso Ambiguity Pollo Expectation Limitation

Continued• Execute validation techniques• Close down RDP

Step 5: Evaluate• Evaluate Techniques: Analyze effectiveness of techniques used• Evaluate Requirement Statements: Analyze any potential gaps

between clients requirements and the product to be delivered• Evaluate RDP: refer next slide• Evaluate Total Effectiveness: refer next slide

Continued

Questions??