Use Case

Use case describes the context or process wherein a product or product component, subpart, is used within. Hence the use case specifies the function or operation of each deliverable product or component. Use case is specified in a procedural outline with logical branches and sub-cases to describe various conditions in the operation of a product or component. UML, pseudocode or a procedural language can be used to document the use case. Actors or user roles in the use case demonstrate interactions of the product or component with external entities. Use case is derived from the actor and process lists of the requirements. Architects and designers act on the use case to develop detailed artifacts such as interaction, sequence, class and component interface diagrams. Each artifact specified is preferred with UML.

As a specification of the input and output parameters of each deliverable product component the Use case provides a basis to develop a test and validation artifact for each component. The complete test and validation artifact parameterized the limits of each component input and output. The test and validation artifacts are used to assure the satisfaction of each component requirement prior to integration in a deliverable product. Ultimately test and validation assure the satisfaction of requirements for each deliverable to customers.