[Project Name]

Release X.X: [Release Short Name]

DETAILED REQUIREMENTS (v X.X)

Detail Description
Detail Description
Detail Description
Business Requirements - Document Info
Project Name, Release X.X, [Short Name]

Document

Title of Document Detailed Requirements & Traceability Matrix

Detailed Requirements record the Quality, Data, Security, Content, Architecture,

Environment, Service Introduction, and all other project needs and constraints that
define project scope and provide the foundation for design and subsequently,
development.

The Requirements Traceability Matrix provides the means to demonstrate a

Purpose requirement has been designed, developed, and tested.

Location [Sharepoint location]

PMO ID No. [PMO ID No.]

Owner/ Author

Name John Smith

Title Business Analyst

Department DoITT PMO

Email jsmith@doitt.nyc.gov

Phone 212-232-0000

Reviewers/ Approver

Reviewer Signature/ Initials

Jane Doe

Jane Doe

Peter Jones (Final Approver)

x

Data, Security, Content, Architecture,

other project needs and constraints that
ation for design and subsequently,

des the means to demonstrate a

d, and tested.

Date

mm/dd/yy

mm/dd/yy

mm/dd/yy
Business Requirements - Revision History
Project Name, Release X.X, [Short Name]

Version Change Highlights Author Date

1 First draft John Smith mm/dd/yy

Incorporated feedback from Steering

2 Committee meeting John Smith mm/dd/yy

Incorporated feedback from internal team

3 meetings John Smith mm/dd/yy
Comments
Business Requirements - Instructions

1.

2.

3.

4.

5.

6.

7.

8.
Business Requirements - Instructions

This template must be used by all ETD projects until such time as the automated requirements tool is
implemented.

Tab Components
The following components must be including in the requirements:
a. Business Requirements
b. Actors (samples included)
c. Assumptions (samples included)
d. Glossary (samples included)
e. Version History (samples included)
f. Additional components may be included at the option of the team as useful for your particular project.

Columns
The Business Requirements must include the required columns on that sheet.
The optional columns are provided for your convenience but are not required.
You may want to include additional optional columns as useful for your particular project.

Column List Values

Your team should use values relevant to your particular project. The values provided are samples.

Printing
All the columns will not fit on paper. For meetings where you need printed copies, hide columns irrelevant to
the meeting so it will fit on the desired paper size and then print.

Formatting
Colors and look and feel is optional. We recommend keeping the existing structure because it facilitates
organization, management and maintenance of the requirements.

Security
To avoid unintentional/unauthorized changes, we recommend you secure the file as read only with a password
required to open the file for editing.

Additional Questions
If you have any questions on this template or the excel features, contact one of the following people:
- Nina Ong - nong@doitt.nyc.gov
- Susan Robertson - srobertson@doitt.nyc.gov
- Chris Zic - czic@doitt.nyc.gov
Business Requirements - Actors
Project Name, Release X.X, [Short Name]

Actor

Agency Admin

DoITT SysAdmin Role

ments - Actors
[Short Name]

Permissions

The Agency Admin's role is to manage the application users.

The DoITT SysAdmin role is to maintain the functionality of the system being
developed.
Business Requirements - Assumptions
Project Name, Release X.X, [Short Name]

Assumptions

There will be no additional integration with any Agency's legacy systems in the current Pilot Phase.

Agencies are responsible for providing software to enable them to view video assets.
Business Requirements - Current
Project Name, Release X.X, [Short Name]

REQ # PRIMARY FUNCTIONAL AREA (opt) MODULE (opt)

00.00.00 Calendar of Events (Template Example)

00.01.00 Calendar of Events (Template Example) Calendar View

00.01.01 Calendar of Events (Template Example) Calendar View

00.01.02 Calendar of Events (Template Example) Calendar View

00.02.00 Calendar of Events - Template Example Event

01.00.00 Functional Area 1

01.01.00

01.02.00

01.03.00

01.04.00

01.05.00

02.00.00 Functional Area 2

02.01.00

02.02.00

02.03.00

02.04.00
02.05.00

03.00.00 Functional Area 3

03.01.00

03.02.00

03.03.00

03.04.00

03.05.00

04.00.00 Functional Area 4

04.01.00

04.02.00

04.03.00

04.04.00

04.05.00
ACTOR SHORT NAME ENVIRONMENT (opt)

Internet User Calendar View Internet

Internet User Block Format Internet

Internet User List Format Internet

Registered User Event Details Internet

REQUIREMENT TYPE REQUIREMENT DESCRIPTION

Users will be able to view all Calendar Events for an individual

UI/ Navigation month

Users will be able to view all Calendar Events for an individual

UI/ Navigation month in a block format

Users will be able to view all Calendar Events for an individual

UI/ Navigation month in a list format

Users will be able to select an individual Event to view the

following corresponding details:
- Event name
- Event location/ venue
- Event address
- Event date and time
- Event description
UI/ Navigation - Event contact info
RATIONALE X-REF PRIORITY

[Why is the requirement needed? What is the benefit of the

feature/functionality? What is the impact if the
feature/functionality is missing? Supply quality/quantity
(metrics) to support/demonstrate rationale.] 1 - High

1 - High

2 - Medium

00.01.00 1 - High
RELEASE/ SCOPE (opt) SIEBEL SRF RELATED? (opt)

In Scope No

In Scope No

In Scope No

In Scope No
QUESTIONS/ ISSUES (opt) COMMENTS
Req Traceability Matrix -->
(click + above to expand)
Business Requirements - Deleted
Project Name, Release X.X, [Short Name]

REQ # PRIMARY FUNCTIONAL AREA (opt) MODULE (opt)

00.02.04 Calendar of Events (Template Example) Event

00.02.05 Calendar of Events (Template Example) Event

ACTOR SHORT NAME REQUIREMENT TYPE

Internet Users Event Map Database

Internet Users Event Reminder Database

REQUIREMENT DESCRIPTION

Users will be able to view a map of the Event location.

System will automatically email an event reminder to the User

RATIONALE X-REF PRIORITY

[Why is the requirement needed? What is the benefit of the

feature/functionality? What is the impact if the
feature/functionality is missing? Supply quality/quantity
(metrics) to support/demonstrate rationale.] 1 - High

1 - High
RELEASE/ SCOPE (opt) SIEBEL SRF RELATED? (opt)

Out of Scope No

Out of Scope No
QUESTIONS/ ISSUES (opt) COMMENTS
Business Requirements - Glossary
Project Name, Release X.X, [Short Name]

Term

Form

Media
s Requirements - Glossary
e, Release X.X, [Short Name]

Definition

An agency fillable form online that allows users to submit information to the agency.

Electronic Video, Audio and or Pictures.

Business Requirements - Other Related Deliverables
Project Name, Release X.X, [Short Name]

Document Name Version Number Document Description

Documents all possible functional scenario

Use Cases 1.0 flows (written in list/ text format)

Documents all static text content (field labels,

instructional text, etc.) for the application;
cross-referenced with the Functional
Content Inventory 1.0 Specifications document

Documents User Interface (UI) Flows,

wireframes and corresponding specification
Functional Specifications 1.0 details for all screens in the application
Author Location

[Business Analyst] [location]

[Information Architect] [location]

[Information Architect] [location]