Requirements Template

April 2003
[Purpose of Template
This template should be used to document the requirements associated with the products and/or services your
project will provide. This generic template is suitable for all types of large to medium size projects. If a section
does not apply to your project, type not applicable under the section heading.

The template consists of 3 major sections:

• User requirements – used to document the requested business uses for the project’s products or
services.
• Functional requirements- used to document what the products or services must do in order to
fulfill the user requirements.
• Non-functional requirements – used to document the product’s behavioral properties and
qualities.
This template should be completed by the person(s) that elicit requirements from the project stakeholders. This
role may be fulfilled by the project manager, a business analyst, a systems analyst, or by some other person in
your organization.

The audiences for and their uses of this document are listed below.

• Project stakeholders. The designated stakeholders should thoroughly review and approve the user and
functional requirements prior to the design stage.

• Testing team. This team will use the requirements for the creation of test plans and to ensure that all
documented and approved requirements are satisfied by the end products.

• Developers. For software application projects, this document serves as input to the technical design.]

[To Complete This Document

Information to guide you in completing this template is enclosed in square brackets and is displayed in blue-
gray italicized text. You should delete this instructional text when your document is completed.]
[Revision History Table
Each time changes are made to this document, the author of the changes must:
• Indicate the date the change was made
• Indicate the document version where the change was made
• Describe the change
• Enter the author’s name]

Revision History
Date Document Description Author
Revision
Number
 Contents
1. Introduction...................................................................................................................................................6
1.1 Statement of Scope.............................................................................................................................6
1.2 Target Markets...................................................................................................................................6
2. Abbreviations, Acronyms, and Terms .........................................................................................................6
2.1 External Links, Supporting Documentation.......................................................................................6
3. User Requirements/Business Workflow.......................................................................................................6
3.1 Business Workflow............................................................................................................................6
3.2 User Requirements.............................................................................................................................7
3.3 Assumptions.......................................................................................................................................8
3.4 Dependencies.....................................................................................................................................8
4. Functional Requirements..............................................................................................................................8
4.1 Functional Requirements – ITS Scorecard (Homepage) ..................................................................9
4.2 Functional Requirements – ITS Scorecard (Financial & People) ...................................................10
4.3 Functional Requirements – ITS Scorecard (End User Support) .....................................................11
4.4 Functional Requirements – ITS Scorecard (Project Performance) .................................................11
5. Nonfunctional Requirements......................................................................................................................13
5.1 Usability/Quality..............................................................................................................................13
5.2 Availability, Reliability, and Performance Requirements...............................................................13
5.3 Look and Feel Requirements...........................................................................................................13
5.4 Interfaces..........................................................................................................................................14
5.4.1 External Interfaces............................................................................................................................14
5.4.2 Hardware Interfaces.........................................................................................................................14
5.5 Constraints.......................................................................................................................................14
5.6 User Documentation and Help System Requirements.....................................................................14
5.7 Training and Documentation...........................................................................................................14
5.8 Data Migration (Existing Content, Content Conversion)................................................................14
5.9 Security............................................................................................................................................14
5.9.1 General Security Requirements........................................................................................................14
5.9.2 Authentication/ Access.....................................................................................................................14
5.10 Licensing Requirements.................................................................................................................15
5.11 Cultural and Political Requirements..............................................................................................15
5.12 Legal, Copyright, and Other Notices.............................................................................................15
6. Supporting Information..............................................................................................................................16
6.1 Future Release Feature List (Not in Current Scope)........................................................................16
 Requirements
1. Introduction
[This section provides an overview of the products and/or services being created by this project.]

1.1 Statement of Scope

[Use this subsection to fully describe the scope of the project. The scope statement should clearly define what
deliverables (products and/or services) will be created and delivered to the customers when the project work is
completed. Include any products/services that will not be delivered and are considered to be “out-of-scope” for this
specific project. You may copy previously documented scope statements from the project charter or Vision, Scope, and
Impact document if applicable.]

1.2 Target Markets

[Specify the audience who will be using the products/services.]

2. Abbreviations, Acronyms, and Terms

[Provide definitions of all abbreviations, acronyms, and terms required to properly interpret this document.]
Abbreviation/Acronym/Term Definition

2.1 External Links, Supporting Documentation

[Provide a complete list of all materials referenced in this document. Identify each referenced material by title,
date, and author or department. Specify where the materials and external links can be found or provide a link
within the table below.]

Document Title Date Author/CSIT Group Source

3. User Requirements/Business Workflow

[This section is used to document the requirements from a user’s perspective. List the user requested features and
functions that the products/services must provide. Do not focus on how the products/services will be developed or
designed.]

3.1 Business Workflow

[Include a basic diagram depicting any new or changed business processes that result from the new product or
service.]
3.2 User Requirements
[Using the Word table below, summarize what the user community has requested in terms of the major
features/functions the products/services must perform or allow the user to perform upon completion of the project
work.]
• User Req. ID – begin each ID with the abbreviation UR followed by an ascending number such as UR01,
UR02, etc.
• Requirement – describe the user requirement.
• Priority – enter High, Medium, or Low as the priority values. High = feature/function must be in product.
Medium = nice to have in the project’s products but stakeholders do not want to extend delivery date or
increase cost. Low = feature can be included in a future product or can be fulfilled via other alternatives.
• Originator (optional) – enter the name of the user who submitted the requirement.
User Requirement Priority Originator
Req. ID
 3.3 Assumptions
[Document any assumed factors that if proven to be invalid could impact the project. May copy previously
documented assumptions from the project charter or Vision, Scope, and Impact document if applicable.]

3.4 Dependencies
[Document any dependencies on external factors that could impact the fulfillment of the user requirements. May
copy previously documented dependencies from the project charter or the Vision, Scope, and Impact document if
applicable.]

4. Functional Requirements
[Functional requirements more fully describe the features and/or functions that the product must perform or allow the
users to perform. They describe the capabilities that must be present in order for the user to carry out the services
provided by each feature and/or function. For software application products, include how the product should respond to
unexpected conditions such as invalid data entry or to any anticipated error conditions.
Functional requirements must satisfy all user requirements. Document all requirements with enough detail so that
product designers (i.e. developers for software applications) can design a system that satisfies those requirements and
testers can create and execute test plans that ensure the developed products/services satisfy the requirements.
Use the Word table below to document the functional requirements. Please group the functional requirements by type of
feature, function, module, etc, in separate tables. For example, if the product has a print and edit function, group all of
the functional requirements related to the edit function in one table and then group all of the requirements related to the
print function in another table. See example tables below.
• Funct. Req. ID – enter an ID for each functional requirement using a short textual description followed
by a unique number.
• Requirement – enter a detailed description of the requirement.
• UR ID Satisfied – enter the ID for the user requirement that is satisfied by this requirement.]
4.1 Functional Requirements – ITS Scorecard (Homepage)

The ITS Scorecard will serve as a dashboard for key ITS enterprise-wide metrics. The scorecard itself is
categorized by five major areas: (1) Systems Availability; (2) Financial; (3) People; (4) End User Support; (5)
Project Performance. Defined metrics have been identified for each area with user-specific views according to
assigned privileges. The ITS homepage is viewable by all of ITS. User will initially view the ITS scorecard at a
high-level. This view briefly summarizes all major categories with selected metrics for each area into a packaged
window pane/table. *Note: Reference http://usteams/sites/ITS_OPS/ITS_Scorecard/scorecard.htm for mock
concept look & feel.
Funct. Requirement UR ID Satisfied
Req. ID
SC01SA User shall be able to view the following metrics from the Systems Enter the ID(s) for
(Scorecard Availability pane area, detailing entire FY MTD% and YTD% data the user
Homepage – for the following: Enterprise Systems, Financial & Human requirement(s) that
Systems Resources, Messaging, Tax & Audit, Telecom, and Network. Each this functional
Availability) metric will contain an active-hyperlink to its source application requirement is
Clearpath. Each metric will accompany a color status according to fulfilling.
its defined percentage threshold.
SC01F User shall be able to view the following metrics from the Financial Enter the ID(s) for
(Scorecard pane area, detailing period and YTD data for the following: Net the user
Homepage – Costs – Actual vs Plan %, Net Cost - % of Net Revenue, Net Costs - requirement(s) that
Financial) $ per person served, and Capital Spend: Actual vs Plan %. Each this functional
metric will contain an active hyperlink to the combined Financial & requirement is
People page as defined in Funct. Req. ID SC02F. Each metric will fulfilling
accompany a color status according to defined thresholds.
SC01P User shall be able to view the following metrics from the People Enter the ID(s) for
(Scorecard pane area, detailing period and YTD data for the following: ITS the user
Hompage – Headcount – Actual vs Plan %, Turnover – Actual vs Expected %, requirement(s) that
People) and Average CED hours per person. Each metric will contain an this functional
active hyperlink to the combined Financial & People page as defined requirement is
in Funct. Req. ID SC02P. Each metric will accompany a color status fulfilling
according to defined thresholds.
SC01EUS User shall be able to view the following metrics from the End User Enter the ID(s) for
(Scorecard Support pane area, detailing a count, rating, or percentage of the the user
Homepage – following: Headcount of US firms, Laptops in Service, Laptop requirement(s) that
End User Failure %, Laptop Compliance %, Backup %, Service Desk this functional
support) Incidents (ITS), Service Desk Incidents in SLA, SD Survey Results requirement is
(scale 1-5), Unique Visits to DeloitteNet, and Unique Visits to My fulfilling
Technology. Each metric will contain an active hyperlink to the End
User Support page as defined in Funct. Req. ID SC02EUS.
SC01PP User shall be able to view the following metrics from the Project Enter the ID(s) for
(Scorecard Performance pane area, detailing a count, rating, or percentage of the user
Homepage – the following: Active Projects, # of Top Projects at Risk, Completed requirement(s) that
Project Projects, Initiated Projects, Customer Satisfaction (scale 1-5), and this functional
Performance) Compliance Status. Each metric will contain an active hyperlink to requirement is
the Project Performance page as defined in Funct. Req. ID SC02PP. fulfilling
4.2 Functional Requirements – ITS Scorecard (Financial & People)
The Financial & People page will house all Financial and People metrics with the ability to view data from a firm-
wide or departmental (CIO, EAG, INFRA, or TSS) perspective. The firm-wide view will be accessible by all of
ITS. Departmental views on the other hand will be restricted to leaders and direct reports of each respective
department. The CIO will have unrestricted access.
Funct. Req. Requirement UR ID Satisfied
ID
SC02F User shall be able to view the following metrics from the Financial Enter the ID(s) for
pane area, detailing period and YTD data for the following: Net the user
(Scorecard –
Costs – Actual vs Plan % as a makeup of Salaries, Computers, requirement(s) that
Financial)
Outside Professional Services, Telecom, Travel and Other; Net this functional
Costs - % of Net Revenue; Net Costs - $ per person served; Capital requirement is
Spend – Actual vs Plan % as a makeup of Leased and Purchased. fulfilling
Each metric will contain an active hyperlink to its graphical view as
defined in SC03FP. Each metric will also accompany a color status
according to defined thresholds. The same metrics, if applicable, will
appear for each department once view is filtered by the user.
SC02P User shall be able to view the following metrics from the People Enter the ID(s) for
(Scorecard – pane area, detailing period and YTD data for the following three (3) the user
People) People areas: Staffing – inclusive of Headcount Plan vs Actual, requirement(s) that
Headcount Leverage, and Turnover Rate; Training – inclusive of this functional
SSL Credits per Quarter, Average CED per Staff, and # of Staff requirement is
charging CED (%); Recruiting – inclusive of Open Positions, fulfilling
Average days open, Average days to fill and number of hires. Each
metric will contain an active hyperlink to its graphical view as
defined in SC03FP. The same metrics, if applicable, will appear for
each department once view is filtered by the user.
SC02CIO CIO shall be able to view all of the metrics and areas as defined in Enter the ID(s) for
(Scorecard – Funct. Req. ID SC02F, SC02P, and SC03FP. In addition to the latter, the user
CIO Financial & People Diversity and WINS will be restricted solely to requirement(s) that
restricted) the CIO. Separately, Diversity and WINS data is inclusive of the this functional
following: Total Representation, Career Lever 5 & above, Turnover requirement is
Gap, and % of New Hires. Each metric will contain an active fulfilling
hyperlink to its graphical view as defined in SC03FP. The same
metrics, if applicable, will appear for each department once view is
filtered by the user.
SC03FP User shall be able to view a graphical representation of all Financial Enter the ID(s) for
(Scorecard – & People metrics. Graphs will show historical data and trending for the user
Graphs) the entire fiscal year. This area is only accessible by departmental requirement(s) that
leaders for their own departments and CIO for full access. this functional
requirement is
fulfilling
4.3 Functional Requirements – ITS Scorecard (End User Support)

Funct. Req. Requirement UR ID Satisfied

ID
SC02EUS User shall be able to view the following metrics from the End User Enter the ID(s) for
Support pane area, detailing count, rating or percentage of the the user
(Scorecard –
following eight categories: Hardware Performance – inclusive of requirement(s) that
End User
Laptop Failure Rate, Desktop Failure Rate, Printer Failure Rate, this functional
Support)
PDA Failure Rate, Non-Warranty Repair Costs, and Laptop requirement is
Performance by class; Laptop Compliance – inclusive of SMS, fulfilling
EPO, DFE, Connected, Firewall, and Patches; Service Desk
Incident Management – inclusive of First Contact Resolution
(STP), % of incidents met by SLT; Data Management – inclusive of
Connected; Asset Management – Inclusive of Computers
Reimaged, LAM Data Accuracy, and % of delinquent EOL;
Customer Satisfaction – inclusive of Service Desk (1 Lo – 5 Hi)
ratings and New-Hire Orientation Training; Practitioner
Communications – inclusive of Visits to My Technology by unique
user and Laptop self-schedule statistics; Engagement Support –
inclusive of # of supported engagements per region, # of tech hours
devoted to support, and # of Service Desk incidents created for
support. Each metric will contain an active hyperlink to its graphical
view as defined in SC03EUS. Each metric will also accompany a
color status according to defined thresholds.
SC03EUS User shall be able to view a graphical representation of all End User Enter the ID(s) for
Support metrics. Graphs will show historical data and trending for the user
(Scorecard –
the entire fiscal year. This area is only accessible by CIO requirement(s) that
Graphs)
Leadership. this functional
requirement is
fulfilling

4.4 Functional Requirements – ITS Scorecard (Project Performance)

Funct. Req. Requirement UR ID Satisfied

ID
SC02PP User shall be able to view the following metrics from the Project Enter the ID(s) for
Performance pane area, detailing count, rating or percentage of the the user
(Scorecard –
following five categories: Active Projects – inclusive of Total requirement(s) that
Project
Active Projects, Totals Active Projects Overdue and % of Active this functional
Performance)
Projects Overdue; Completed Projects – inclusive of Projects requirement is
completed within the current month and Fiscal YTD Completions; fulfilling
Pipeline Status – inclusive of Projects Cancelled within current
month, Projects Cancelled YTD, Proposed Projects and Initiated
Projects; Customer Satisfaction – inclusive of ITS Project
Satisfaction Rating, Customer Satisfaction Rating, and End-User
Satisfaction Rating; Top Project Tracker – Inclusive of Top
Projects color statuses as defined by the PMO group. Each metric
 will also contain an active hyperlink to its graphical view as defined
in SC03PP.
SC03PP User shall be able to view a graphical representation of all Project Enter the ID(s) for
Performance metrics. Graphs will show historical data and trending the user
(Scorecard –
for the entire fiscal year. This area will be accessible to all of ITS. requirement(s) that
Graphs)
this functional
requirement is
fulfilling
5. Nonfunctional Requirements
[Nonfunctional requirements document how well the product works. Requirements pertaining to
interfaces should be included in this section along with requirements related to quality and performance
attributes such as availability, efficiency, and reliability].

5.1 Usability/Quality
[Include requirements that impact how well the user will interact with the new products/services. These include
requirements around ease of use, ease of learning, and the ability to be used by certain user types.
• Use of existing style standard
Example: The page layout will provide a 3 inch margin of white space for user’s notes.
• Use of existing navigation standards
Example: The user must be able to drill down to needed information in less than 3 clicks.
• Ease of use
Example: The user must be able to complete and submit his/her enrollment data within 10 minutes.
Example: The menu system must have less than 4 choices.
• Consistency with other existing products and/or services
Example: The new application must use the same font and style as all other existing reports]]

5.2 Availability, Reliability, and Performance Requirements

[Specify the users expectations regarding the product’s availability, reliability, and performance
requirements. Consider the following:
Availability—Specify the percentage of time available ( xx percent), hours of use, maintenance access,
etc.
Accuracy—Specify precision (resolution) and accuracy (by some known standard) that is required in the
product.
Response time for a transaction (average, maximum)
Number of concurrent users or operations to be supported
Examples: The response time should be less than 2 seconds for 90% of responses and no more than 3
seconds for the reminder of responses.
Example: The system must be available for 95% of the time between 6:00 am and 8:00 pm EST.]

5.3 Look and Feel Requirements

[Document standard styles or standard interface elements that should exist throughout the entire product.
Examples include standard fonts, styles, colors, buttons, links, short cut keys, error message formats. For
software applications, do not document details of the user interface design here.
Example: The dimensions of the firm directory will be 4 x 7 inches and will use Arial 9 point font.]
5.4 Interfaces
[Define and describe any external, 3rd party, or hardware interfaces that must be supported by the product.]

5.4.1 External Interfaces

[Define any needed interactions between the product and other external products and/or data sources
such as SAP, 3rd party software, news feeds, etc.]

5.4.2 Hardware Interfaces

[Define any peripheral hardware that must be supported by the products such as OCR scanners, bar code
readers, special use printers, etc.]

5.5 Constraints
[Indicate any constraints that place restrictions on the types of solutions that may be evaluated and on the way the
products/services can be designed/developed. You may copy constraints that may have been previously
documented in the project charter and/ or Vision, Scope, and Impact document. Examples of constraints include:
• Budget constraints
• Time constraints (when product can be delivered, how long a training course can take due to out of
office impact)
• Resource constraints
• Software languages/versions/service packs
• Developmental tools
• Architectural and design constraints
• Purchased components

5.6 User Documentation and Help System Requirements

[Describe the requirements, if any, for user documentation and help systems, etc.]

5.7 Training and Documentation

[Describe the requirements for any training materials.]

5.8 Data Migration (Existing Content, Content Conversion)

[Describe how existing data will be migrated or converted to meet data requirements and data structure for the
new application. Include data conversion tables and conversion rules if applicable.]

5.9 Security
[Specify any requirements regarding security or privacy issues surrounding the use of the product or protection of
the data.]

5.9.1 General Security Requirements

[Explain who and under what circumstances users can access and use what parts of the product.]

5.9.2 Authentication/ Access

[Explain how users will access the product and if needed, be authenticated to use the product.]

5.9.2.1Roles and IDs

[Describe user roles and needed IDs that may be different from the generic authentication
 scheme.]

5.9.2.2Test Roles and IDs

[Describe any special user IDs that need to be created for testing purposes.]

5.9.2.3User Account Maintenance

[Describe how authentication groups, if applicable, will be maintained.]

5.9.2.4Data Encryption
[Describe any requirements that will be used in the application such as encryption of credit
card numbers, social security numbers, or other confidential information.]

5.10 Licensing Requirements

[Define any licensing enforcement requirements or other usage restriction requirements that will be required for
the product.]

5.11 Cultural and Political Requirements

[Describe any requirements that constrain the design or functions of the product based on global or political
needs. Include internationalization requirements related to items such as language choices. Include other
requirements such as logos for branding purposes and exclusion of certain words, colors, phrases, and symbols
that may be inappropriate for global applications.]

5.12 Legal, Copyright, and Other Notices

[Describe any necessary legal disclaimers, warranties, copyright notices, patent notices, trademarks, or logo
compliance issues for the product.]
 6. Supporting Information
[Include additional information that more fully explains or supports both user and functional requirements. Items that
may be included in this section include an index, appendices, storyboards or user interface (UI) prototypes.
[Use the Data Table to further define each functional requirement as needed. The Data Table provides a place to enter
specific information regarding data attributes.
• Funct. Req. ID – enter the ID for the functional requirement that contains the data element being described.
• Label – The data label is the name of the element (field) that will appear on the user interface such as
Ending Date, Social Security Number, Function, Award Date.
• Type - describe the type of interface requirement (checkbox, drop-down lists, radio button, text entry, etc.)
• Required – indicate if this data element is required.
• Possible Values – list any values for the field as dictated by the user. If actual values are not provided
include a definition of the possible values such as numeric, alpha, or alphanumeric.
• Default Values – define the default value for the element if applicable
• Comments – enter any other needed information concerning the data element such as minimum/maximum
field lengths, calculations/formulas, or other necessary descriptive information.]
Funct. Req. Label Type Required Possible Default Comments
ID (Y/N) Values Values

PRINT02 Select Radio Y Report A None

Report Button
Report B
Report C

Funct. Req. Label Type Required Possible Default Comments

ID (Y/N) Values Values

6.1 Future Release Feature List (Not in Current Scope)

[Include any features or functions that will not be delivered in the current project’s work but will be included in
future projects. You may create a bulleted list of these out-of-scope features/functions or use the sample table
below.]
Req. ID Requirement Description Priority for future Originator Target Release
release