Artifact: Software Requirements Specification










var backPath = './../../';
var imgPath = './../../images/';
var nodeInfo=[{view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_gpYSoAILEdq-_NKqZM1EhA", "_kus_YN7DEdmsEI4YDGX2ag", "{7264A534-7509-4B4B-AF73-CAECC0178898}", "{BE8165DC-BAF2-4237-B27D-F2A037023364}"]}, {view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_gpYSoAILEdq-_NKqZM1EhA", "_N13eYAINEdq-_NKqZM1EhA", "_KVkLoN7HEdm8G6yT7-Wdqw", "{BE8165DC-BAF2-4237-B27D-F2A037023364}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_f6_YwN7DEdmsEI4YDGX2ag", "_kus_YN7DEdmsEI4YDGX2ag", "{7264A534-7509-4B4B-AF73-CAECC0178898}", "{BE8165DC-BAF2-4237-B27D-F2A037023364}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_EOvXUN7HEdm8G6yT7-Wdqw", "_KVkLoN7HEdm8G6yT7-Wdqw", "{BE8165DC-BAF2-4237-B27D-F2A037023364}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_jijhYAIaEdqEutyfYo0quQ", "_3aJCcN7REdmjRZts2c4ZjQ", "{BE8165DC-BAF2-4237-B27D-F2A037023364}"]}];
contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);










Artifact: Software Requirements Specification















This artifact captures the software requirements for the complete system, or a portion of that system.


Domains: Requirements
Work Product Kinds: Specification






Purpose



The Software Requirements Specification (SRS) focuses on the collection and organization of all requirements surrounding your project. It is useful for collecting your project software requirements in a formal, IEEE830-style document. Since you might find yourself with several different tools for collecting these requirements, it is important to realize that the collection of requirements may be found in several different artifacts and tools. For this reason, we will collect the requirements for our SRS in a package which may be a single document or a collection of various artifacts that describe the requirements. (See the More Information section for additional guidelines). The SRS package controls the evolution of the system throughout the development phase of the project, as new features are added or modified to the Vision document, they are elaborated within the SRS Package. The following people use the Software Requirements Specification: Designers use the SRS Package as a reference when defining responsibilities, operations, and attributes on classes, and when adjusting classes to the implementation environment. Implementers refer to the SRS Package for input when implementing classes. The Project Manager refers to the SRS Package for input when planning iterations. Testers use the SRS Package as an input to considering what tests will be required.



Relationships



RolesResponsible:



Requirements Specifier


Modified By:



Requirements Specifier





TasksInput To:



Capture a Common Vocabulary


Define Test Approach


Identify Test Ideas


Review Requirements


Output From:



Detail the Software Requirements





Process Usage


Project Management
 > 
Plan the Project
 > 
Software Requirements Specification


Project Management
 > 
Refine the Development Plan
 > 
Software Requirements Specification


Requirements
 > 
Analyze the Problem
 > 
Software Requirements Specification


Requirements
 > 
Understand Stakeholder Needs
 > 
Software Requirements Specification


Requirements
 > 
Define the System
 > 
Software Requirements Specification


Requirements
 > 
Refine the System Definition
 > 
Software Requirements Specification


Requirements
 > 
Manage Changing Requirements
 > 
Software Requirements Specification


Test
 > 
Improve Test Assets
 > 
Software Requirements Specification


Test
 > 
Define Evaluation Mission
 > 
Software Requirements Specification


Test
 > 
Test and Evaluate
 > 
Software Requirements Specification






Description



Brief Outline The Software Requirements Specification (SRS) captures the complete software requirements for the system, or a portion of the system. Many different arrangements of an SRS are possible. Review the tailoring section for additional guidance.



Tailoring



Representation Options Many different arrangements of an SRS are possible. Review the templates and examples section in the header table of this page for arrangements relevant in your project context. Refer to [IE830] for further elaboration of this artifact, including other options for SRS organization. The Software Requirements Specification should provide a complete definition of the software requirements, both functional and non-functional. However, use-case specific requirements, both functional and non-functional, should be documented in  the Use Cases, and system-wide requirements, both functional and non-functional, should be documented in the Supplementary Specifications. These separate work products may be packaged together to define the Software Requirements Specification (SRS).



More Information



Checklists


Software Requirements Specification





Concepts


Requirements





Guidelines


Software Requirements Specification








©  Copyright IBM Corp. 1987, 2006.  All Rights Reserved.







contentPage.onload();