Service Life Cycle Management
Project requirements for project
Note: This is a very detailed requirements template, with many sections that may be
unnecessary for a given project. Because this is a template, you should feel free to adapt
it to the needs of your project.
Abstract: [Provide a very brief summary of the document’s contents.]
Contents
Version notice................................................................................................................................................. 1
Trademarks ..................................................................................................................................................... 2
Security checklist ........................................................................................................................................... 2
1. Introduction ................................................................................................................................................ 3
2. General information.................................................................................................................................... 3
3. Processing flows ......................................................................................................................................... 4
4. System architecture .................................................................................................................................... 4
5. Detailed requirements ................................................................................................................................. 4
6. System Interfaces/Impacts .......................................................................................................................... 6
7. Global requirements ................................................................................................................................... 6
8. Testing considerations ................................................................................................................................ 8
9. Summary .................................................................................................................................................... 8
Version notice
All revisions of this document are listed in chronological order. There is no relationship between the
document number and the software release number.
Document release Date Description Software release
Draft 1 mm/dd/yyyy [This information is optional. If you wish to
do so, give a brief description of this and
subsequent drafts.]
Draft 2 mm/dd/yyyy
Release 1 mm/dd/yyyy First release.
This document was created by within COMPANY NAME. COMPANY has made
every effort to ensure that this document is accurate at the time of printing. Obtain additional copies of this
document, as well as updated releases, from the following organization:
Rev. 11/21/2011 1 c4080580-ece5-4fcb-b57b-59cce7bec03d.doc
Service Life Cycle Management
Trademarks
The trademarks contained in this document are the property of their respective owners.
Security checklist
If the answer to any of the following questions is "yes", then the IT Security Office should review
additional details of the proposed implementation.
Will sensitive data be stored on, or transmitted through, the system (for example, Social Security
Numbers, employee or student records, health information)?
Does the application require authentication?
Will the vendor be providing and maintaining the hardware or software?
Would abuse or compromise of the system potentially damage the university’s image or brand, or
adversely affect public relations?
Rev. 11/21/2011 2 c4080580-ece5-4fcb-b57b-59cce7bec03d.doc
Service Life Cycle Management
1. Introduction
Purpose/Scope
[Briefly explain the purpose and goal of the project. Summarize the problem clients experience with
the present system, if one exists, or the need clients have for a system solution. Identify goals that
would be achieved with the proposed system and the assumptions and dependencies that these
statements are based on. Define the scope of this system requirements document. What releases does it
include? What does it exclude?]
Summary of changes
Target audience
Review/Concurrence information
Structure and use
Traceability
Disclaimer
2. General information
Challenge/Opportunity
Feature/Project description
Benefit/Value
Assumptions, Dependencies, Constraints
Security risk assessment
3. Processing flows
4. System architecture
Hardware requirements
Software requirements
5. Detailed requirements
Common requirements
Data modeling requirements
Rev. 11/21/2011 4 c4080580-ece5-4fcb-b57b-59cce7bec03d.doc
Service Life Cycle Management
Functional requirements
Client (User) interface requirements
Database requirements
Building block requirements
Contract requirements
Data communications requirements
Rev. 11/21/2011 5 c4080580-ece5-4fcb-b57b-59cce7bec03d.doc
Service Life Cycle Management
Other
6. System Interfaces/Impacts
Project interfaces
7. Global requirements
Availability/Reliability requirements
Performance requirements
Security requirements
Environmental constraints
Client or site-specific requirements
System administration requirements
Information development requirements
Usability requirements
Rev. 11/21/2011 7 c4080580-ece5-4fcb-b57b-59cce7bec03d.doc
Service Life Cycle Management
8. Testing considerations
9. Summary
Open issues
Acknowledgements
References
Glossary
Attachments
Rev. 11/21/2011 8 c4080580-ece5-4fcb-b57b-59cce7bec03d.doc