Artifact: Supplementary Specifications










var backPath = './../../';
var imgPath = './../../images/';
var nodeInfo=[{view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_gpYSoAILEdq-_NKqZM1EhA", "_kus_YN7DEdmsEI4YDGX2ag", "{F1F206DF-3AA0-4AC0-92EF-8E4A01B6C5B5}", "{B16C2941-791C-44E6-B353-354109B5C9DE}"]}, {view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_gpYSoAILEdq-_NKqZM1EhA", "_N13eYAINEdq-_NKqZM1EhA", "_KVkLoN7HEdm8G6yT7-Wdqw", "{B16C2941-791C-44E6-B353-354109B5C9DE}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_f6_YwN7DEdmsEI4YDGX2ag", "_kus_YN7DEdmsEI4YDGX2ag", "{F1F206DF-3AA0-4AC0-92EF-8E4A01B6C5B5}", "{B16C2941-791C-44E6-B353-354109B5C9DE}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_EOvXUN7HEdm8G6yT7-Wdqw", "_KVkLoN7HEdm8G6yT7-Wdqw", "{B16C2941-791C-44E6-B353-354109B5C9DE}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_jijhYAIaEdqEutyfYo0quQ", "_3aJCcN7REdmjRZts2c4ZjQ", "{B16C2941-791C-44E6-B353-354109B5C9DE}"]}];
contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);










Artifact: Supplementary Specifications















This artifact captures system requirements that are not readily captured in behavioral requirements artifacts such as use-case specifications.


Domains: Requirements
Work Product Kinds: Specification






Purpose



The Supplementary Specifications capture the system requirements that are not readily captured in the use cases of the use-case model. Such requirements include: Legal and regulatory requirements, and application standards Quality attributes of the system to be built, including usability, reliability, performance, and supportability requirements Other requirements such as those for operating systems and environments, compatibility with other software, and design constraints



Relationships



RolesResponsible:



System Analyst


Modified By:



System Analyst





TasksInput To:



Architectural Analysis


Assess Viability of Architectural Proof-of-Concept


Capture a Common Vocabulary


Class Design


Database Design


Describe Distribution


Describe the Run-time Architecture


Design the User Interface


Detail a Use Case


Identify Design Elements


Identify Design Mechanisms


Implement Design Elements


Prototype the User-Interface


Review Requirements


Review the Architecture


Review the Design


Structure the Implementation Model


Use-Case Analysis


Use-Case Design


Output From:



Develop Supplementary Specifications


Structure the Use-Case Model





Process Usage


Analysis & Design
 > 
Define a Candidate Architecture
 > 
Supplementary Specifications


Analysis & Design
 > 
Perform Architectural Synthesis
 > 
Supplementary Specifications


Analysis & Design
 > 
Refine the Architecture
 > 
Supplementary Specifications


Analysis & Design
 > 
Design the Database
 > 
Supplementary Specifications


Analysis & Design
 > 
Analyze Behavior
 > 
Supplementary Specifications


Analysis & Design
 > 
Design Components
 > 
Supplementary Specifications


Implementation
 > 
Implement Components
 > 
Supplementary Specifications


Implementation
 > 
Structure the Implementation Model
 > 
Supplementary Specifications


Requirements
 > 
Analyze the Problem
 > 
Supplementary Specifications


Requirements
 > 
Understand Stakeholder Needs
 > 
Supplementary Specifications


Requirements
 > 
Define the System
 > 
Supplementary Specifications


Requirements
 > 
Refine the System Definition
 > 
Supplementary Specifications


Requirements
 > 
Manage Changing Requirements
 > 
Supplementary Specifications


Test
 > 
Validate Build Stability
 > 
Supplementary Specifications


Test
 > 
Verify Test Approach
 > 
Supplementary Specifications


Test
 > 
Improve Test Assets
 > 
Supplementary Specifications


Test
 > 
Test and Evaluate
 > 
Supplementary Specifications






Description



Main Description The Supplementary Specifications are an important complement to the Use-Case Model, because together they capture all software requirements (functional and nonfunctional) that need to be described to serve as a complete Software Requirements Specification.


Brief Outline It is recommended that the Supplementary Specification be organized according the requirement categories.  For a description of a categorization approach using the "FURPS+" acronym, see Concept: Requirements.



Illustrations



Examples


CSPS Supplementary Specification - Elaboration Phase


CSPS Supplementary Specification - Inception Phase






Key Considerations



The Supplementary Specification captures all system-wide requirements, not just the non-functional ones.  A common misconception is that all functional requirements reside in the Use Case work products and all non-functional requirements reside in the Supplemental Specification work product. This is inaccurate as some functional requirements apply to the system as a whole (such as a requirement for online help). Similarly, some non-functional requirements only apply to a particular use case (or flow within a use case), in which case the requirement should be attached to the use case, otherwise the system will be over-engineered.



Tailoring



Representation Options The kinds of supplementary requirements vary widely between projects, so tailoring should be applied to define sections applicable to your project.



More Information



Checklists


Supplementary Specifications





Concepts


Requirements





Guidelines


Software Requirements Specification


Supplementary Specifications â€" Informal Representation








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







contentPage.onload();