Checklist: Supplementary Specifications
This checklist helps make sure that all necessary Supplementary specifications are identified.
Expand All SectionsExpand All Sections    Collapse All SectionsCollapse All Sections
CollapseRelationships  
Related Elements
Back to topBack to top
CollapseMain Description  

The included basic issues should be addressed to detail all requirements that are not specified within the use-case model.
Back to topBack to top
CollapseCheck Items  
Expand All Check ItemsExpand All Check Items Collapse All Check ItemsCollapse All Check Items
ExpandFunctionality  
What is the software supposed to do? This should include the following:
  • Validity checks on the inputs
  • General responses to abnormal situations, including: overflow, communication facilities, error handling and recovery
  • Effects of parameters
  • Relationship of outputs to inputs, including input/output sequences and formulas for input to output conversion
Expand External interfaces   
How does the software interact with people, the system's hardware, other hardware, and other software?
Expand Performance   
What is the speed, availability, response time, recovery time of various software functions, etc.? Are both static and dynamic requirements included?
Expand Logical database requirements   
Have all logical requirements been specified for any information that is to be placed into a database? This may include the following:
  • Types of information used by various functions
  • Frequency of use
  • Accessing capabilities
  • Data entities and their relationships
  • Integrity constraints
  • Data retention requirements
Expand Standards Compliance   
Have all requirements derived from existing standard and regulations been specified? How will this be traced?
Expand Attributes   
What are the reliability, availability, portability, correctness, maintainability, security, etc. considerations?
Expand Design constraints imposed on an implementation   
Are there any required standards in effect, implementation language, policies for database integrity, resource limits, operating environment(s), etc.?
Back to topBack to top

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