REQUIREMENTS MANAGEMENT PLAN – [Project Name]
[Project name]
Approved
Name / Approved/Not Approved / Signature / Title / Date /Author: / [Name], Business Analyst, ITS
Version:
Date: / 22 October 2013
PAGE 6 OF 6
THE AUSTRALIAN NATIONAL UNIVERSITY
REQUIREMENTS MANAGEMENT PLAN – [Project Name]
Contents
1 Introduction 3
1.1 Purpose 3
2 Requirements Management Overview 3
2.1 Organisation, Responsibilities and Interfaces 3
2.2 Tools, Environment and Infrastructure 3
3 Requirements Management 3
3.1 Assumptions/Constraints 3
3.2 Requirements Definition 3
3.3 Requirements Artefacts 3
3.4 Stakeholder Analysis 4
3.5 Requirements Elicitation Planning 4
3.6 Requirements Traceability 5
3.7 Workflows and Activities 5
3.8 Change Management 5
Appendix A: Key Terms 6
Appendix B: Requirements Specification 6
Appendix C: Requirements Traceability 6
1 Introduction
1.1 Purpose
[Provide the purpose of the Requirements Management Plan. This document should be tailored to fit a particular project’s needs.]
2 Requirements Management Overview
2.1 Organisation, Responsibilities and Interfaces
[Describe here who is going to be responsible for performing the various activities described in the requirements workflows defined later in this document.]
2.2 Tools, Environment and Infrastructure
[Describe the environment and software tools to be used in fulfilling the Requirements Management functions throughout the project or product lifecycle. Describe the tools and procedures that will be used to control the versioning of the Requirements items generated throughout the project or product lifecycle.]
3 Requirements Management
3.1 Assumptions/Constraints
[Define any assumptions and/or constraints taken into account when defining requirement for this section of this document.]
3.2 Requirements Definition
[Describe the approach and tools that the project will use to define the specifications of the project requirements. Explicitly describing project requirements promotes the correct and efficient development and delivery of that requirement.]
3.3 Requirements Artefacts
[Provide the list of requirements artifacts that will be produced.]
Artefact / Requirements Typee.g. Solution Requirement Specification (SRS) / e.g. Use Case (UC)
e.g. As Is Process / e.g. BPMN process map
PAGE 6 OF 6
THE AUSTRALIAN NATIONAL UNIVERSITY
REQUIREMENTS MANAGEMENT PLAN – [Project Name]
3.4 Stakeholder Analysis
For details on stakeholder involvement, please refer to the document <Document Name>.
3.5 Requirements Elicitation Planning
[Describe the elicitation activities and techniques that will be used.]
ID / Activity Description / Dependency / Stakeholders Participating / Time Required / Challenges / TechniquePAGE 6 OF 6
THE AUSTRALIAN NATIONAL UNIVERSITY
REQUIREMENTS MANAGEMENT PLAN – [Project Name]
3.6 Requirements Traceability
[Describe the approach and tools that the project will use to trace the project requirements throughout the systems life cycle. The approach that is followed should enable the project team to ensure that the project delivers the project requirements exactly as specified and that they fulfill the project requirements. Appendix C is for a Requirements Traceability Matrix that can be adapted and populated for this purpose.]
3.7 Workflows and Activities
[Describe the workflows and activities that apply to managing requirements. Describe review activities, including review objectives, responsibilities, timing, and procedures.]
3.8 Change Management
[Describe the process by which problems and changes are submitted, reviewed, and resolved. This should include the process for negotiating requirements changes with customers, and any contractual processes, activities, and constraints. Describe who will be authorized to approve changes and procedures for processing change requests.]
PAGE 6 OF 6
THE AUSTRALIAN NATIONAL UNIVERSITY
REQUIREMENTS MANAGEMENT PLAN – [Project Name]
Appendix A: Key Terms
[Insert terms and definitions used in this document.]
Term / Definition/DescriptionAppendix B: Requirements Specification
[Insert a link to the Requirements Specification.]
Appendix C: Requirements Traceability
[Insert a link to the Requirements Traceability.]
PAGE 6 OF 6
THE AUSTRALIAN NATIONAL UNIVERSITY