Requirements Document

For
Name of system
Submitted To:
Client Name of Organization

Submitted By:
Applied Research and Technology Services

Date document is submitted
2 of 7
Requirements Template


Table of Contents
1. EXECUTIVE SUMMARY ................................................................................................. 3
2. BACKGROUND ................................................................................................................. 3
3. PURPOSE/ PRODUCT DESCRIPTION ............................................................................ 4
4. METHODOLOGY .............................................................................................................. 4
5. BUSINESS RULES ............................................................................................................. 4
6. GENERAL FUNCTIONAL REQUIREMENTS ................................................................ 4
7. CLIENT RESPONSIBILITIES ........................................................................................... 5
8. ASSUMPTIONS .................................................................................................................. 5
9. DOCUMENT REFERENCES ............................................................................................. 6
10. GLOSSARY ..................................................................................................................... 6
11. POINTS OF CONTACT .................................................................................................. 6
12. APPROVAL ..................................................................................................................... 7



3 of 7
Requirements Template


INSTRUCTIONS
The following template contains instructions (blue italicized) under each of its 12 sections
describing, what type of data and information to be included in the full requirements document.
Under each section beginning with the word insert, you will read and replace the blue
italicized instructions with relevant information, pertaining to the new product or system ARTS is
developing.
See example below in blue box of the deleted instructions in blue, replaced with the real purpose
in black font.
PURPOSE/PRODUCT DESCRIPTION
Insert: What is the purpose of the new system, its intended audience? Describe the business
objectives and business processes, and the applications the new system supports.
This document will be written by ARTS to define a product they are making or, the requirements
for one or more new features for an existing product. This document is designed to help people
within the company to understand what a product should and, how it works. It will identify and
define the problems that, the product must solve. This template is most commonly used for
software products but, can be used for other types of products.

1. EXECUTIVE SUMMARY
Insert: A summary of the entire document highlighting the key features and components of the
report and, its intended use, the audience and the improvements.

2. BACKGROUND
Insert: Description of the Client organization, the system currently being used and, the systems
functions. Also include the reason the Client organization contacted ARTS, and the desired outcome if
ARTS develops a new system for the Client Organization.
See example below:
Client currently utilizes an old system (name) which no longer meets their needs. The Tracker
System allows for information on individual cases to be entered into a database and acts as a
simplified workflow System.
Client contacted Applied Research and Technology Services (ARTS) to develop a new case
tracking System (the System) to meet their daily workflow and database needs.
4 of 7
Requirements Template


The following Requirements have been defined:

3. PURPOSE/ PRODUCT DESCRIPTION
Insert: What is the purpose of the new system, its intended audience? Describe the business objectives
and business processes, and, the applications the new system supports.
See example below:
This document will be written by ARTS to define a product they are making or, the requirements
for one or more new features for an existing product. This document is designed to help people
within the company to understand what a product should and, how it works. It will identify and
define the problems that, the product must solve. This template is most commonly used for
software products but, can be used for other types of products.
4. METHODOLOGY
Insert: Describe the overall approach used in the determination of the requirements document contents.
Describe the modeling method(s) so non-technical readers can understand what is being conveyed.

5. BUSINESS RULES
Insert: Anything that captures or implements business policy and practices. A rule can enforce business
policy, make a decision, or infer new data from existing data. Business rules are intended to assert
business structure or, to control or influence the behavior of the business.
6. GENERAL FUNCTIONAL REQUIREMENTS
Insert: Organized bullet points and numberings containing the specifications of the new system,
including:
The desired operating system requirements
How the new system will save data
How employees and staff of the client organization will retrieve saved data on the system
How the new system will integrate operations with the existing system
Security features
Computer hardware components e. g, number of computer screens
Software out put options
Description of inputs such as data and outputs such as documents /reports generated
See examples below:
6.1 Functional Requirements:- See examples below
6.1.1 All data and source code shall be submitted and belong to Client after System
acceptance.
5 of 7
Requirements Template


6.1.2 The System shall save data entered on each screen separately.
6.1.3 The System shall enable Client staff to retrieve Case records.

6.2 Development Requirements:- See examples below
6.2.1 The System shall use Windows Server 2008 R2.
6.2.2 The System shall use SQL for the backend System (database).

6.3 Hardware Requirements:- See examples below
6.3.1 The system shall utilize computer monitors and processors for easier data entry,
and, generation.

6.4 Software Requirements:- See examples below
6.4.1 The system shall run internal computers on Microsofts operating system

6.5 Security Requirements:- See examples below
6.5.1 The system shall utilize controlled access software requiring authorized users
authentication.

6.6 Interface Requirements: See examples below
6.6.1 The System shall be capable of interfacing the Clients HR Software.

7. CLIENT RESPONSIBILITIES
Insert: Client Organizations responsibilities and limitations in regards to the new system and its
component level compatibility. For example, if a Client provides report layout and data requirements.
See example below:
7.1 Client will ensure that any and all of their support does not compromise System or
component level compatibility.
7.2 Client will Provide report layout and data requirements.

8. ASSUMPTIONS
Insert: A list of potential Assumptions that may be included for example (see below)
Software ARTS will use to build the new system
How ARTS will integrate previous system with the new system?
The Client organizations purchases in relation to maintenance of new system
How ARTS and the Client organization will work together?
8.1 ARTS will build the System using Visual Studio 2008 or 2010.
8.2 Client will purchase reporting software (e.g., Crystal Reports).

6 of 7
Requirements Template


9. DOCUMENT REFERENCES
Insert: - All documents, websites or related materials used in in supporting this requirements
template and full document.
Identify all documents by title, report number and publishing organization.
Include additional sources as needed such as meeting summaries, white paper analysis.
Specify the sources from which references can be obtained. This information may be provided by
reference to an appendix or to another document.
10. GLOSSARY
Insert: - Business terms peculiar to application.
See example below:
Term Definition
<Term> <Provide definition of term and acronyms used in this document.>



11. POINTS OF CONTACT
Insert: - Names and titles of major participants in the project. At the minimum, list the Project
Manager, Development Project Leader and user contacts and, a Clients employee whose
signature constitutes the acceptance of the requirements document/report. The persons listed will
be those individuals responsible for the administrative implementation of the product for the
Client and ARTS.
See example:
Administrator/ Admin officer- ARTS Contact information
Administrator/ Admin Officer -Client Contact information

7 of 7
Requirements Template


12. APPROVAL
Insert: List the individuals whose signatures are desired and, represent the approval and
acceptance of the project by both client and ARTS. Examples of such individuals are Business
Owner, Project Manager (if identified), and any appropriate stakeholders. Add additional lines
for signature as necessary.

Signature:
Date:
Print Name:

Title:

Role:


Signature:
Date:
Print Name:

Title:

Role:


Signature:
Date:
Print Name:

Title:

Role: