Workflow > Detail > Artifact

Artifact: Supplementary Specifications

The Supplementary Specification captures the application's or website's quality attributes, architectural requirements, and design constraints that do not belong in the use cases.

More detail: Purpose - Audience - Template

Click the icons for definition

Business Strategist
End User
Situational AssessmentBusiness Concept
Business Process AnalystFind Business Actors and Use CasesDefine Business OperationsStructure the Business Use Case Model
GlossaryBusiness Use Case RealizationBusiness Use CaseBusiness Use Case ModelBusiness Ops PlanBusiness Object ModelUse Case Model (Sketch)
Business DesignerDetail a Business Use Case
Business Modeling Guidelines (from Environment)
Software Architect
Business Process Analyst
Business Strategist
Software Architecture Document (Sketch)
Requirements AnalystExplore Software Support
Analysis Model (Sketch)


Requirements applicable to the whole website or application such as security, conformance with standards, or availability are inappropriate to capture in use cases. However, they must be kept somewhere so the project team has an agreed to definition of the requirements, quality goals, and design constraints. The Supplementary Specification documents those requirements and goals. Quality attributes include reliability, performance, usability and other characteristics that span multiple use cases. It is also important to identify constraints on the system such as pre-chosen platforms, interoperability with existing systems, etc. The Supplementary Specification and the Use Case specifications define the application's requirements.


The following roles use the Supplementary Specification:

  • The Role: Requirements Analyst uses it to capture requirements and goals for the application being built.
  • Stakeholders and other requirements reviewers assess it to ensure the project team understands the requirements and expectations.
  • The Role: Software Architect uses the Supplementary Specification as a primary source for designing the software architecture.
  • The Role: Software Designer and Role: Implementer use it to understand the requirements that the software architecture satisfies.
  • The Role: Tester uses it as input to designing tests.
  • The Role: Project Manager uses it to identify risks and establish iteration objectives.