July 2, 1997
System Development
Life Cycle Outline
System Requirements Specification
March 2009
Health and Human Services Agency, Office of Systems IntegrationPrinted at 10/05/18 4:01 AM / DRAFT
Project Management Office
Office of Systems Integration / System Requirements Specification
March 2009
Revision History
Revision HistoryRevision/WorkSite # / Date of Release / Owner / Summary of Changes
SDLC Outlines - #5358 / August 29, 2008 / OSI - PMO / Initial Release
OSI Admin 5358v2 / 03/26/09 / OSI-PMO / Updated document to reference that this outline should be used when developing RFP requirements. Updated the roles to reflect responsibilities associated with System Requirements Specification.
OSIAdmin #53581
Project Management OfficeOffice of Systems Integration / System Requirements Specification
March 2009
Table of Contents
1.Purpose
2.Scope
3.Responsibilities
3.1Contractor
3.2Project Manager
3.3Contract Manager
3.4Systems Engineer
3.5Project Team
4.System Requirements Specification Outline
4.1Cover Page
4.2Revision History
4.3Table of Contents
4.4Introduction
4.4.1System Purpose
4.4.2Business Content
4.4.3Scope
4.4.4User Characteristics
4.5General System Description
4.5.1System Context
4.5.2System Modes and States
4.5.3Major System Capabilities
4.5.4Major System Conditions
4.5.5Major System Constraints
4.5.6Assumptions
4.5.7Dependencies
4.5.8Operational Scenarios
4.6System Capabilities, Conditions and Constraints
4.6.1Business Requirements
4.6.2Functional Requirements
4.6.3Physical Requirements
4.6.4Logical Data Requirements
4.6.5Performance Requirements
4.6.6Operations Requirements
4.6.7Security Requirements
4.6.8Policy and Regulations Requirements
4.7Reference Documents
4.8Glossary
4.9Appendices
OSIAdmin #53581
Project Management OfficeOffice of Systems Integration / System Requirements Specification
March 2009
1.Purpose
This document should be used by the Office of Systems Integration (OSI) projects to assist in defining RFP requirements. This document provides guidance in the uniform development of the System Requirements Specification (SyRS) document, which is a structured collection of information that embodies the requirements of the system. The purpose of the system requirements specification is to communicate stakeholder requirements to the technical resources that will specify and build the system. This document was based on the following Institute of Electrical and Electronics Engineers (IEEE) Standards: IEEE Standard (STD) 1233-1998.
2.Scope
The SyRS is a product that is produced during the System Development Life Cycle (SDLC). The SDLC is a conceptual model used for project management that describes a series of phases involved in a system development project. The OSI has defined the following phases as part of the SDLC model: Requirements Analysis, Design, Development, Test, Implementation, and Transition to Maintenance and Operations (M&O).
The SyRS is constructed during the analysis phase of the SDLC and is a deliverable of this phase. The SyRS serves as a blueprint for completing the project. It is the reference document for the project and all subsequent SDLC phase documents, such as, the detailed design specification, testing documents, and system documentation.
3.Responsibilities
3.1Contractor
The Contractor is responsible for developing, updating, and obtaining approval for the SyRS, if it is included as a requirement in the contract.
3.2Project Manager
The Project Manager is responsible for coordinating the efforts of those involved in the SyRS development, review, and approval.
3.3Contract Manager
The Contract Manager verifies that the SyRS is developed, reviewed, and approved.
3.4Systems Engineer
The Systems Engineer may provide input in developing the SyRS.
3.5Project Team
The project team member(s) is responsible for assisting in the development and review of the SyRS.
4.System Requirements Specification Outline
This outline specifies the minimum content elements for the SyRS. Document formatting is not defined; all formats are acceptable, if the content elements are complete.
4.1Cover Page
Provide a cover page with the necessary content, such as the name of the document, date, and the Office of Systems Integration logo and footer.
4.2Revision History
Provide a revision history table with column titles: Revision Number, Date of Release, Owner, and Summary of Changes.
4.3Table of Contents
Provide a table of contents with a list of the document sections and the pages on which they begin.
4.4Introduction
4.4.1System Purpose
Specify the purpose of the SyRS and its intended audience.
4.4.2Business Content
Provide an overview of the business organization sponsoring the development of the system, and any related business content.
4.4.3Scope
Describe the scope of the system to be developed.
4.4.4User Characteristics
Identify each type of user of the system by function, location, and type of device. Specify the number of users in each group and the nature of their use of the system.
4.5General System Description
4.5.1System Context
Provide appropriate diagrams and accompanying narratives to provide an overview of the context of the system, defining all significant interfaces crossing the system’s boundaries.
4.5.2System Modes and States
Describe the various modes of operation for the system and the conditions that determine the modes of operation.
4.5.3Major System Capabilities
Provide diagrams and narratives to depict major capability groupings of the requirements.
4.5.4Major System Conditions
Specify major conditions and their associated capabilities.
4.5.5Major System Constraints
Describe major constraints of the system.
4.5.6Assumptions
Describe the assumptions that can affect the requirements specified in this SyRS.Assumptions are factors that are believe to be true during the life cycle of the project, that if changed may affect the outcome of the project.Dependencies are outside of the scope and control of the project and must remain true for the project to succeed.
4.5.7Dependencies
Describe the dependencies that can affect the requirements specified in this SyRS.
4.5.8Operational Scenarios
Provide descriptive operational scenarios for the system.
4.6System Capabilities, Conditions and Constraints
In the requirements subsections, specify all requirements to a level of detail sufficient to enable development of the system.
Each requirement documented in the requirements sections must have a unique identifier for requirements traceability and should be ranked for importance and/or stability.
4.6.1Business Requirements
Describe all business requirements for the system.
4.6.2Functional Requirements
Provide the functional requirements necessary to comprehensively define the fundamental actions that must take place within the system to accept and process the inputs and to process and generate the outputs.
4.6.3Physical Requirements
6.6.3.1Construction
Specify the environmental characteristics of where the system will be installed.
6.6.3.2Durability
Specify the durability characteristics of the system.
6.6.3.3Adaptability
Specify the growth, expansion, capability, and contraction characteristics of the system.
6.6.3.4Environmental Conditions
Detail the environmental conditions to be encountered by the system.
4.6.4Logical Data Requirements
Describe the logical data requirements for the system.
4.6.5Performance Requirements
Describe the critical system performance requirements, such as response time or system capacity.
4.6.6Operations Requirements
6.6.6.1 System Maintainability
Describe any maintainability requirements that apply to maintaining the system in the support environment.
6.6.6.2 System Reliability
Describe any reliability requirements and define the conditions under with these requirements will be met.
4.6.7Security Requirements
Define any security requirements for the system.
4.6.8Policy and Regulations Requirements
Define any policy or regulations requirements that are necessary for the system.
4.7Reference Documents
Provide any references used in the creation of the document.
4.8Glossary
Provide an alphabetized list of definitions for special terms and acronyms used in the document.
4.9Appendices
The appendices should contain material that is too detailed or large to be included in the main body of the document. Refer to each appendix in the main body of the text where the information applies.
OSIAdmin #53581