Requirements Development Approach

<Project>
Requirements Development Approach / <version>

Requirements Development Approach

Version: <version #>

Date: <version date>

Publication Record

Version / Date / Primary Author / Description

Table of Contents

1Introduction

1.1Purpose

1.2Document Scope

1.3References

1.4Acronyms, Abbreviations, and Terms

1.4.1Acronyms and Abbreviations

1.4.2Terms

2Planning Phase

2.1Scope

2.1.1In Scope Items

2.1.2Out of Scope Items

2.2Assumptions, Dependencies and Risks

2.3Standards

2.4Methodology

2.5Requirements Development Team

2.6Requirements Development Communication Plan

2.7Requirements Development Project Plan

2.8Requirements Change Management

3Eliciting Phase

3.1Methods and Techniques

3.2Tools

3.3Principles

4Documenting Phase

4.1Methods and Techniques

4.2Tools

4.3Requirements Package

4.4Requirements Reviews

4.5Traceability

4.6Standards

5Approving Phase

5.1Interim Approvals

5.2Final Approval

6Approvals

6.1Reviewers

1Introduction

1.1Purpose

1.2Document Scope

1.3References

Reference Identification / Description / Source / Location

1.4Acronyms, Abbreviations, and Terms

The following tables list the acronyms, abbreviations, and terms used in this document.

1.4.1Acronyms and Abbreviations

Acronym / Term

1.4.2Terms

Term / Definition

2Planning Phase

2.1Scope

2.1.1In Scope Items

2.1.2Out of Scope Items

2.2Assumptions, Dependencies and Risks

# / Date / Description

2.3Standards

The requirements will be developed in alignment with the following standards:

2.4Methodology

The methodology planned for this initiative is:

Methodology
(Select ONE)
Iterative
Waterfall
Agile/Scrum
Spiral
RUP
Other (specify)

2.5Requirements Development Team

The Requirements Development team consists ofmany people with varying roles. The roles involved are:

Role / Description / Expected Time Commitment

These roles will be filled by the following individuals:

Person / Primary Role / Perspective/Specialty

2.6Requirements Development Communication Plan

The following communications will be sent regarding requirements development for this initiative:

Communication / Owner / Participants/Recipients / Vehicle / Frequency

2.7Requirements Development Project Plan

2.8Requirements Change Management

3Eliciting Phase

3.1Methods and Techniques

The methods and techniques used during the Eliciting Phase are:

Methods/Techniques / Select all that apply
Activity Diagram / Operational Walkthrough
Brainstorming / Prototyping
Business Process Map / Requirements Workshop
Class Model / Reverse Engineering
Context Diagram / Sequence Diagram
CRUD Matrix / SIPOC
Data Flow Diagram / State Diagram
Data Transformation and Mapping / Storyboard
Decision Table / Survey
Decision Tree / Technology Demonstrations
Document Analysis / Use Cases
Event-Response Table / User Stories
Fishbone Diagram / User Task Analysis
Flowchart / Workflow Models
Focus Group / Other (specify)
Interface Analysis
Interview
Observation

3.2Tools

The tools used during the Eliciting Phase are:

Requirements Elicitation/
Management Tools / Comments
QualityCenter
BluePrint
RavenFlow
Tibco Business Studio
Doors
Microsoft Office (Word, Excel)
Other (specify)

3.3Principles

4Documenting Phase

4.1Methods and Techniques

The methods and techniques used during the Documentation Phase are:

4.2Tools

The tools used during the Documentation Phase are:

Requirements Elicitation/
Management Tools / Comments
QualityCenter
BluePrint
RavenFlow
Tibco Business Studio
Doors
Microsoft Office (Word, Excel)
Other (specify)

4.3Requirements Package

4.4Requirements Reviews

4.5Traceability

Deliverable
(Higher Level) / Deliverable
(Lower Level) / Rationale/Comments

4.6Standards

5Approving Phase

5.1Interim Approvals

5.2Final Approval

6Approvals

6.1Reviewers

Page 1 of 10