Scribd
Upload
115 views4 pages

Requirements Analysis Template

The document provides information on the requirements analysis for a project including the project name, agency, sponsor, and manager. It defines the scope as identifying requirements for the solution to the XYZ project. It summarizes requirements gathered from JAD sessions with ABC and DEF business units. The business need briefly describes the problem driving the project and identifies customers and consumers. In scope requirements include functional, technical, operational, and transitional requirements with type, business function, and priority. Out of scope requirements provide reasons for being out of scope.

Uploaded by

Hussain Rahib
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
115 views4 pages

Requirements Analysis Template

The document provides information on the requirements analysis for a project including the project name, agency, sponsor, and manager. It defines the scope as identifying requirements for the solution to the XYZ project. It summarizes requirements gathered from JAD sessions with ABC and DEF business units. The business need briefly describes the problem driving the project and identifies customers and consumers. In scope requirements include functional, technical, operational, and transitional requirements with type, business function, and priority. Out of scope requirements provide reasons for being out of scope.

Uploaded by

Hussain Rahib
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
You are on page 1/ 4

REQUIREMENTS ANALYSIS: PROJECT INFORMATION

Project Name:
Agency:
Project Sponsor:
Project Manager:
Last Revision Date:
Document Status:
Prepared By:

Draft or Final
Enter the names of the project team members by whom the document was prepared.

Document Scope:

To define a consistent set of requirements for the solution to the <XYZ> project and to identify what is in
and out of scope.
This document summarizes the requirements gathered in a series of <LMN (e.g. Joint Application
Development)> sessions that were conducted by members of the project team with <ABC> and <DEF>
business units between <date> and <date>.

Business Need:

Briefly describe the need or problem driving the proposed project and the identification of the Customers
and anticipated Consumers of the projects product.
Describe how the project is consistent with the agencys mission and/or strategic plan. Provide rationale
if it is not.

288357131.xls

IN SCOPE REQUIREMENTS

Type
(Functional,
Technical,
Operational,
Transitional)

Business
Function /
Category
(for
Functional
Type only)

Requirement

Priority
(Core,
Essential,
Desired)

Page 2 of 4

288357131.xls

Requirement

OUT OF SCOPE REQUIREMENTS


Reason Requirement is 'Out of Scope'

Page 3 of 4

Term
Functional

Technical

Definition of 'Type'
Definition
Impacts the Business Process Requirements that define
those features of the product that will specifically satisfy a
Consumer need, or with which the Consumer will directly
interact.

Impacts the Product Infrastructure Requirements that


identify the technical constraints or define conditions under
which the product must perform.

Operational Impacts Operations and Support Requirements that define


those "behind the scenes" functions that are needed to keep
the product operational over time.

Example Considerations
-Common Functions
-GUI Functions
-Reporting Functions
-Interface Functions
-Batch Functions
-Security Functions
-Accessibility
-Encryption
-Hosting
-Environment
-Disaster Recovery
-System Performance
-Data Archival
-Audit and Controls
-System Administration
-System Quality Assurance
-Business Continuity

Transitional Impacts Implementation Requirements that define those


aspects of the product that must be addressed in order for the -Data Conversion
product to be successfully implemented and to relegate support -Release Validation
responsibilities to the Performing Organization.
-Documentation
-Training
-Deployment

Term
Business
Function /
Category

Definition of 'Business Function / Category'


Definition
The business function column is used for Functional types of requirements. The purpose for the column is
to categorize the requirements, which in turn helps the team ensure that they have captured all of the
requirements for a given business function.
Example: An insurance program may have business functions of: benefits, appeals, adjudications, etc.
Each of these business functions may have requirements specific to itself.

Core

Definition of 'Priority'
Definition
Requirements without which the product may as well not be developed at all; it will be of no use to most
Customers without these.

Essential

Requirements for which a short-term work-around could be developed (or for which an old process can be
used for a little while longer), but over the long run, the requirements have to be there.

Desired

Requirements that are the "bells and whistles" which may be precious to certain constituencies, but without
which the product will function just fine.

Term

A product must be delivered with all Core and a good portion of Essential requirements represented, and
with a plan to implement the remaining Essential requirements in the subsequent phase.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy