Template 11: Requirement Analysis Report

<Project/Initiative Name>

Requirements Specifications

Recommendation

[Insert a new signature line for each additional stakeholder providing approval. The signature of each stakeholder confirms that all impacted business lines are informed and consulted. Approval of this requirement’s specification document provides agreement by stakeholders for shared responsibility of the business and technical requirements. Delete this comment once completed.]

We recommend approval of this business case for <Project Name> initiative.

Image

I / We concur:

Image

Document History

Image

Table of Contents

1.      Introduction

1.1      Purpose

1.2      Scope

1.2.1      Out-of-Scope

2.      Business Need

2.1      Benefits

2.2      Audience

2.3      Stakeholders

3.      Impact and Constraints

3.1      Risks

3.2      Assumptions

3.3      Constraints

3.4      Dependencies

4.      Timing/Schedules

4.1      Milestones

5.      Assessment Methodology

5.1      Reference Materials

5.2      Assessment Techniques

6.      Requirements Analysis

6.1      Functional Requirements

6.2      Operational Requirements

6.3      Technical Requirements

6.4      Transactional Requirements

6.5      Out-of-Scope Requirements

1.   Introduction

1.1.   Purpose

This requirement specifications report documents and tracks the activities performed to determine the needs and/or desires for the architectural design of <Specify the system name>.

This document also includes an overview of the assessment methodology used and details the findings of the requirement analysis so stakeholders have necessary information to build system architectural designs.

1.2.   Scope

[This section explains what business strategies will drive the results of this assessment. Delete this comment once completed.]

The following are considered in-scope deliverables as part of this project:

•  <Insert in-scope strategy>

•  <Insert in-scope strategy>

1.2.1.   Out-of-Scope

[This section explains what business strategies will not drive the results of this assessment. Delete this comment once completed.]

The following are considered out-of-scope deliverables as part of this project:

•  <Insert out-of-scope strategy>

•  <Insert out-of-scope strategy>

2.   Business Need

2.1.   Benefits

[This section describes the benefit(s) to be achieved and the justification(s) for completing the assessment. Delete this comment once completed.]

2.2.   Audience

[Modify the table in this section based on the individuals who have a vested interest in the outcome of this assessment, such as Executive Management, Subject Matter Experts, IT Support, or Sales. Delete this comment once completed.]

The intended audience of this requirements specification document includes the following:

•  <Insert the business lines or organizational role>

•  <Insert the business lines or organizational role>

2.3.   Stakeholders

[This section lists the specific individuals and/or business lines who will participate either directly or indirectly in the completion of this assessment. The stakeholders listed in the table below are provided as examples and should be modified to match those individuals and/or groups specific to the organization. Delete this comment once completed.]

Image

3.   Impact and Constraints

3.1.   Risks

[Describe the significant events or conditions that, if they occur, will affect this assessment. Delete this comment once completed.]

Image

3.2   Assumptions

The following circumstances and outcomes, taken for granted in the absence of concrete information, have affected this assessment:

•  <Assumption description>

•  <Assumption description>

3.3   Constraints

The following limitations and restrictions have been taken into consideration prior to the execution of this assessment:

•  <Constraint description>

•  <Constraint description>

3.4.   Dependencies

The following preceding elements were performed prior to the execution of this assessment:

•  <Dependency description>

•  <Dependency description>

4.   Timing/Schedules

[Include an implementation date for the project and use multiple rows if the project is being implemented in several phases. Include a high-level schedule of the projected implementation plan; critical dates, including additional funding checkpoints; and any interdependencies with other initiatives. Delete this comment once completed.]

images

4.1.   Milestones

[Describe the key deliverables that will be used for measuring the project’s success or failure. Delete this comment once completed.]

images

5.   Assessment Methodology

The section outlines the methodology followed to gather and validate the requirements in support of the business strategies described in Section 1.2.

5.1.   Reference Materials

In support of this assessment, the reference materials specified in the table below were used to gather the baseline set of requirements.

[In the table below, specify the documentation, roadmaps, best practices, etc. used to gather the baseline set of requirements. Delete this comment once completed.]

images

5.2.   Assessment Techniques

In support of this assessment, the baseline set of requirements were validated with stakeholders identified in Section 2.3 using the approaches listed in the table below.

[In the table below, specify the interviews, surveys, workshops, etc. used to validate the baseline set of requirements with stakeholders. Delete this comment once completed.]

images

6.   Requirements Analysis

The section outlines the finalized set of requirements in support of the business strategies described in Section 1.2.

6.1.      Functional Requirements

This section describes the features of the deliverable(s) that will specifically meet a business need or desire.

images

6.2.   Operational Requirements

This section describes the “behind the scenes” functions needed to keep the deliverable(s) working overtime.

images

6.3.   Technical Requirements

This section describes the conditions under which the deliverable(s) must function.

images

6.4.   Transactional Requirements

This section describes the aspects of the deliverable(s) that must be met to hand over support responsibilities.

images

6.5.   Out-of-Scope Requirements

This section describes the requirements that have been identified as out of scope.

images

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.143.239.1