Business Requirements for [Project

Name]
Version 1.0

Prepared By: [Author’s Name Goes Here]

Date: [Date of First Draft Completion goes here]
Table of Contents
Revision History
Business Process Flow / Overview
Dependencies..............................................................................................................................5
Current Business Flow Diagram.................................................................................................5
Proposed Business Flow Diagram...............................................................................................5
Information Flow
Current System Context Diagram...............................................................................................5
Proposed System Context Diagram.............................................................................................6
Business Requirements
Security Requirements................................................................................................................6
Performance Requirements.........................................................................................................6
Availability Requirements...........................................................................................................6
System Requirements and Processing Rules
Technical Services Impact Statement..........................................................................................7
System Environment Needs................................................................................................7
Questions............................................................................................................................7
Network Needs....................................................................................................................8
Backup and Recovery Needs...............................................................................................8
Storage Capacity Needs.......................................................................................................8
Telecommunications Load...................................................................................................8
Solution Alternatives/ Preliminary architecture diagram
Solution #1: [Enter the name of the solution here]..............................................................9
Solution #2: [Enter the name of the solution here]..............................................................9
Budget and Resource Estimates
Glossary
Approvals
Inspection Checklist for Software Requirements
Organization and Completeness................................................................................................12
Correctness...............................................................................................................................12
Quality Attributes......................................................................................................................12
Traceability...............................................................................................................................12
Special Issues............................................................................................................................12
Revision History
This section records the change history of this document.

Name Date Reason For Changes Version

 Business Process Flow / Overview
This section shows the current and proposed business process diagrams. The current business
process flow diagram describes the current process accurately, including any flaws that exist in
today's process that will be repaired by the proposed process. The proposed business flow
diagram describes the proposed process accurately.

Dependencies

Certain business dependencies exist that may affect the project team's ability to implement the
project. These dependencies are listed below so that they can be communicated and addressed.
The items listed here can affect the success of the project so they should be addressed as quickly
as possible.
 [Add a dependency here.]

Current Business Flow Diagram

[Insert diagram here]

[Add any comments about the diagram here]

Proposed Business Flow Diagram

[Insert diagram here]

[Add any comments about the diagram here]

Information Flow
The information in the current business system flows from one place to another with a certain
context. The context of the information flow is defined by the following diagrams. The first
diagram displays the context of the current system. The second diagram displays the context of
the proposed system. These diagrams are a representation of how information flows from external
entities to the current and proposed system.

Current System Context Diagram

[Insert diagram here]

[Add any comments about the diagram here]
Proposed System Context Diagram

[Insert diagram here]

[Add any comments about the diagram here]

Business Requirements
The business requirements describe the needs of the business. The following types of
requirements must be defined fully here:
 Security Requirements — Define the security measures that must apply to this product as
defined by the business unit and the Security Policies and Procedures Guide.
 Performance Requirements — Define the performance necessary in the product from a
business perspective.
 Availability Requirements — Define the timeframes during which the product must be
available to meet the needs of the business.
 User Requirements – Define exactly what the business wants the finished product to look
and function like.

Security Requirements

The following security requirements must be present in the final product:

 [Insert security requirement here.]

Performance Requirements

The following general performance requirements must be present in the final product. More
stringent performance requirements may be placed upon the product in the Functional Design
Specification or in the Technical Design Specifications. These documents may not reduce the
performance requirements:
 [Insert performance requirement here.]

Availability Requirements

The final product must be available to the users during [Enter availability requirement here]. Any
time the system must be brought down during these times, users will be notified with [number of
hours] of advanced notice. If a problem occurs that brings down the system without warning, the
users will be notified as soon as possible. Whenever availability is interrupted, a notice will be
sent when the system is again available.
 [Insert availability requirement here.]

User Requirements
The requirements must be defined as traceable throughout the development Life Cycle. Technical
solutions should be avoided here; solutions do not come into play until the Design Phase of the
project. In the attached Requirements Traceability Matrix, the language should be written at the
level that the User would understand.

"ATCRequirements
Tracability Matrix.xls"

Requirements Tracability Matrix

Use this embedded document to begin tracking your requirements.

System Requirements and Processing Rules

Each system has a set of system requirements and processing rules that define the needs of the
business and the rules that define how the system should work. This section defines those
requirements.

Technical Services Impact Statement

This section describes the needs of this new system and the impact it will have on the technical
infrastructure of ATC. The following infrastructure needs are addressed:
 System environment
 Network
 Backup and recovery
 Storage capacity
 Telecommunications bandwidth

System Environment Needs

This new system needs a specific hardware and software environment. The following
environment is required to support this system: This will assist to establish the preliminary
architecture based on general questions about the customer needs. This preliminary information
will be converted into accurate dollar figures.
[Enter the system environment hardware, software, memory needs for all appropriate tiers here.]

Questions
Is this a new system or an upgrade of an existing system? [new system or upgrade]
How many users does the business expect for the proposed system? [number or range]
How many do you expect to be on the system concurrently? [number or range]
How many are in Domestic Field Offices? [number or range]
 How many are in International Field Offices? [number or range]

Do you expect the system to require feeds from outside of the ATC Network? [yes or no]
Do you expect the system to require feeds from inside of the ATC Network? [yes or no]
Do ATC Partners need to access the system? [yes or no]
Do you need a new server for development? [yes or no]
Do you need a new server for testing or staging? [yes or no]
Does the system have an E-mail dependency? [yes or no]
Is this system's server replacing an existing server? [yes or no]
Server being replaced: [If yes, name the existing server.]
If no, are you acquiring a new server? [yes or no]
Does this system require a dedicated server for Production? [yes or no]
[If yes, describe any situations that require this system to have a dedicated server]

Network Needs
This new system has specific needs in terms of network connections, bandwidth, and general
network environment. The following network attributes are required to support this system:
[Enter the network needs for all appropriate tiers here.]

Backup and Recovery Needs

Backup and recovery services are provided by the Data Center staff. This section describes the
backup needs for this system.
What level of backups does the system need?
[Describe the backup frequency (daily, weekly, etc) type (full or incremental) and storage]

Storage Capacity Needs

This system has certain storage needs in order to continue to function. These needs are outlined in
the section below:

Device Name or Type Initial Storage Estimate Growth Rate Estimate

[Device Name goes here] [Initial storage size goes here] [Growth rate goes here]
[Device Name goes here] [Initial storage size goes here] [Growth rate goes here]
… … …
Telecommunications Load
This system will place a certain load on the telecommunication systems at ATC. This section
describes the parameters that contribute to the telecommunications load:

Department/Location Est. No. of Users Est. Rate of Use Online?

[Department Name goes here] [# of users] [Heavy, medium, light] [Yes/No]
[Department Name goes here] [# of users] [Heavy, medium, light] [Yes/No]
… … … …

Solution Alternatives/ Preliminary architecture

diagram
This section describes each of the solutions that are under consideration for this system. These
solutions each have benefits and drawbacks outlined here:

Solution #1: [Enter the name of the solution here]

[Enter a description of this solution, including the benefits and drawbacks here.]

Solution #2: [Enter the name of the solution here]

[Enter a description of this solution, including the benefits and drawbacks here.]

Budget and Resource Estimates

The appropriate estimates for project costs and project planning are listed below:
Information Systems Business

Software Exp $ Cap $ Hours Exp $ Cap $ Hours

Hardware 0.00 0.00 — 0.00 0.00 —
Personnel Resources 0.00 0.00 — 0.00 0.00 —
Consultants/Contractors 0.00 0.00 0 0.00 0.00 0
Support Resources 0.00 0.00 0 0.00 0.00 0
Maintenance Contracts 0.00 0.00 0 0.00 0.00 0
Miscellaneous 0.00 — — 0.00 — —
Total 0.00 — — 0.00 — —
0.00 0.00 0 0.00 0.00 0
Dollar figures in thousands of dollars for estimated life of product.
Glossary
The terms in this glossary are business or project-specific terms that might cause confusion. If
you have difficulty with any term in the project documentation, consult this glossary for
clarification:

Approvals

______________________________________________
Sponsor –

______________________________________________
Business Analyst –

_______________________________________________
Project Manager –
Inspection Checklist for Software Requirements
The following checklist should be completed after the initial requirements document is completed
but before it is presented to the developers:

Organization and Completeness

 Are all internal cross-references to other requirements correct?

 Are all requirements written at a consistent and appropriate level of detail?
 Do the requirements provide an adequate basis for design?
 Is the implementation priority of each requirement included?
 Are all external hardware, software, and communication interfaces defined?
 Have algorithms intrinsic to the functional requirements been defined?
 Does the SRS include all of the known customer or system needs?
 Is any necessary information missing from a requirement? If so, is it identified as TBD?
 Is the expected behavior documented for all anticipated error conditions?

Correctness

 Do any requirements conflict with or duplicate other requirements?

 Is each requirement written in clear, concise, unambiguous language?
 Is each requirement verifiable by testing, demonstration, review, or analysis?
 Is each requirement in scope for the project?
 Is each requirement free from content and grammatical errors?
 Can all of the requirements be implemented within known constraints?
 Are any specified error messages unique and meaningful?

Quality Attributes

 Are all performance objectives properly specified?

 Are all security and safety considerations properly specified?
 Are other pertinent quality attribute goals explicitly documented and quantified, with the
acceptable tradeoffs specified?

Traceability

 Is each requirement uniquely and correctly identified?

 Is each software functional requirement traceable to a higher-level requirement (e.g., system
requirement, use case)?

Special Issues
 Are all requirements actually requirements, not design or implementation solutions?
 Are the time-critical functions identified, and timing criteria specified for them?
 Have internationalization issues been adequately addressed?