Artifact:  Supplementary Specifications

Supplementary Specifications	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 operating systems and environments, compatibility requirements, and design constraints
Role:	Analyst
Enclosed in:	Software Requirements Specification
More Information:	Checkpoints:Supplementary Specifications Concepts: Requirements Guidelines: SRS/Non-Functional Requirements
Templates, Case-Study, Report.. Purpose Timing Responsibility Tailoring

Input to Activities: Architectural Analysis Class Design Design Test Detail a Use Case Implement Component Perform Unit Tests Plan Test Review Requirements Review the Architecture Review the Design Structure the Use-Case Model Use-Case Analysis Use-Case Design

Output from Activities: Develop Vision Find Actors and Use Cases Elicit Stakeholders Requests Detail a Use Case

Templates, Case-Study, Report..

The Word template can be bought through a template package. Case studies and reports are freely available in the table below.

Word Template	Case Study	Report
		---

Purpose

The following roles and role sets use the Supplementary Specifications:

• Analysts create and maintain the Supplementary Specifications, which serve as a communication medium between the analyst, the customer, and developers.
• Designers use the Supplementary Specifications as a reference when defining responsibilities, operations, and attributes on classes, and when adjusting classes to the implementation environment.
• Implementers refer to the Supplementary Specifications for input when implementing classes.
• Project managers refer to the Supplementary Specifications for input when planning iterations.
• Testers use the Supplementary Specifications to verify system compliance.

Timing

Supplementary Specifications go hand-in-hand with the use-case model, implying that:

• they are initially considered in the Inception phase, as a complement to defining the scope of the system
• they are refined in an incremental fashion during the Elaboration and Construction phases

Responsibility

A analyst is responsible for producing the Supplementary Specifications, which is an important complement to the use-case model. The Supplementary Specifications and the use-case model together should capture a complete set of requirements on the system.

Tailoring

The kinds of supplementary requirements vary widely between projects, so tailoring should be applied to define sections applicable to your project.  Decide which information (attributes) to include in the Vision, and which to manage using requirements management tools.