SDLC_ System Requirements Specification Outline

System Development Life Cycle Outline

System Requirements Specification

March 2009

Use File/Properties/Custom to insert title

July 2, 1997

Health and Human Services Agency, Office of Systems Integration

Printed at 04/08/23 6:27 AM

DRAFT

Project Management Office

Office of Systems Integration

System Requirements SpecificationMarch 2009

Revision History

REVISION HISTORY

REVISION/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 #5358 i




Table of Contents

1. PURPOSE...................................................................................................................................... 1

2. SCOPE........................................................................................................................................... 1

3. RESPONSIBILITIES....................................................................................................................... 13.1 CONTRACTOR......................................................................................................................... 13.2 PROJECT MANAGER...............................................................................................................13.3 CONTRACT MANAGER.............................................................................................................13.4 SYSTEMS ENGINEER...............................................................................................................13.5 PROJECT TEAM...................................................................................................................... 1

4. SYSTEM REQUIREMENTS SPECIFICATION OUTLINE..............................................................24.1 COVER PAGE......................................................................................................................... 24.2 REVISION HISTORY.................................................................................................................24.3 TABLE OF CONTENTS.............................................................................................................24.4 INTRODUCTION....................................................................................................................... 2

4.4.1 System Purpose.............................................................................................................2

4.4.2 Business Content..........................................................................................................2

4.4.3 Scope.............................................................................................................................. 2

4.4.4 User Characteristics......................................................................................................2

4.5 GENERAL SYSTEM DESCRIPTION.............................................................................................24.5.1 System Context..............................................................................................................2

4.5.2 System Modes and States.............................................................................................2

4.5.3 Major System Capabilities.............................................................................................2

4.5.4 Major System Conditions..............................................................................................3

4.5.5 Major System Constraints.............................................................................................3

4.5.6 Assumptions.................................................................................................................. 3

4.5.7 Dependencies.................................................................................................................3

4.5.8 Operational Scenarios...................................................................................................3

4.6 SYSTEM CAPABILITIES, CONDITIONS AND CONSTRAINTS..........................................................34.6.1 Business Requirements................................................................................................3

4.6.2 Functional Requirements..............................................................................................3

4.6.3 Physical Requirements..................................................................................................3

4.6.4 Logical Data Requirements...........................................................................................4

4.6.5 Performance Requirements..........................................................................................4

4.6.6 Operations Requirements.............................................................................................4

4.6.7 Security Requirements..................................................................................................4

4.6.8 Policy and Regulations Requirements.........................................................................4

4.7 REFERENCE DOCUMENTS.......................................................................................................44.8 GLOSSARY............................................................................................................................. 44.9 APPENDICES.......................................................................................................................... 4

OSIAdmin #5358 i




OSIAdmin #5358 ii




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.1ContractorThe Contractor is responsible for developing, updating, and obtaining approval for the SyRS, if it is included as a requirement in the contract.

3.2Project ManagerThe Project Manager is responsible for coordinating the efforts of those involved in the SyRS development, review, and approval.

3.3Contract ManagerThe Contract Manager verifies that the SyRS is developed, reviewed, and approved.

3.4Systems EngineerThe Systems Engineer may provide input in developing the SyRS.

3.5Project TeamThe project team member(s) is responsible for assisting in the development and review of the SyRS.

OSIAdmin #5358 1




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 PageProvide 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 HistoryProvide a revision history table with column titles: Revision Number, Date of Release, Owner, and Summary of Changes.

4.3Table of ContentsProvide a table of contents with a list of the document sections and the pages on which they begin.

4.4Introduction

4.4.1 System Purpose

Specify the purpose of the SyRS and its intended audience.

4.4.2 Business Content

Provide an overview of the business organization sponsoring the development of the system, and any related business content.

4.4.3 Scope

Describe the scope of the system to be developed.

4.4.4 User 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.1 System 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.2 System Modes and States

Describe the various modes of operation for the system and the conditions that determine the modes of operation.

4.5.3 Major System Capabilities

Provide diagrams and narratives to depict major capability groupings of the requirements.

OSIAdmin #5358 2




4.5.4 Major System Conditions

Specify major conditions and their associated capabilities.

4.5.5 Major System Constraints

Describe major constraints of the system.

4.5.6 Assumptions

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.7 Dependencies

Describe the dependencies that can affect the requirements specified in this SyRS.

4.5.8 Operational Scenarios

Provide descriptive operational scenarios for the system.

4.6System Capabilities, Conditions and ConstraintsIn 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.1 Business Requirements

Describe all business requirements for the system.

4.6.2 Functional 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.3 Physical Requirements

6.6.3.1 ConstructionSpecify the environmental characteristics of where the system will be installed.

6.6.3.2 DurabilitySpecify the durability characteristics of the system.

6.6.3.3 AdaptabilitySpecify the growth, expansion, capability, and contraction characteristics of the system.

OSIAdmin #5358 3




6.6.3.4 Environmental ConditionsDetail the environmental conditions to be encountered by the system.

4.6.4 Logical Data Requirements

Describe the logical data requirements for the system.

4.6.5 Performance Requirements

Describe the critical system performance requirements, such as response time or system capacity.

4.6.6 Operations Requirements

6.6.6.1 System MaintainabilityDescribe any maintainability requirements that apply to maintaining the system in the support environment.

6.6.6.2 System ReliabilityDescribe any reliability requirements and define the conditions under with these requirements will be met.

4.6.7 Security Requirements

Define any security requirements for the system.

4.6.8 Policy and Regulations Requirements

Define any policy or regulations requirements that are necessary for the system.

4.7Reference DocumentsProvide any references used in the creation of the document.

4.8GlossaryProvide an alphabetized list of definitions for special terms and acronyms used in the document.

4.9AppendicesThe 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 #5358 4

SDLC_ System Requirements Specification Outline

Documents

Transcript of SDLC_ System Requirements Specification Outline