DEV475 Mastering Object-Oriented Analysis and Design with UML ...

Module 3 - Requirements OverviewSupplementary SpecificationSupplementary Specification• Functionality• Usability• Reliability• Performance• Supportability• Design constraintsSupplementarySpecificationMastering Object Oriented Analysis and Design with UMLCopyright © 2003 Rational Software, all rights reserved 23The nonfunctional requirements and functional requirements not captured by the usecases are included in the Supplementary Specifications. The SupplementarySpecifications include constraints on the implementation.Functionality: List of the functional requirements that are general to many use cases.Usability: Requirements that relate to, or affect, the usability of the system. Examplesinclude ease-of-use requirements or training requirements that specify how readilythe system can be used by its actors.Reliability: Any requirements concerning the reliability of the system. Quantitativemeasures such as mean time between failure or defects per thousand lines of codeshould be stated.Performance: The performance characteristics of the system. Include specificresponse times. Reference related use cases by name.Supportability: Any requirements that will enhance the supportability ormaintainability of the system being built.Design Constraints: Any design constraints on the system being built.Supplementary Specifications go hand-in-hand with the Use-Case Model, implyingthat:• They are initially considered in the Inception phase as a complement to definingthe scope of the system.• They are refined in an incremental fashion during the Elaboration andConstruction phases.3 - 23