Artifact: Subsystem Use-Case Model
This is essentially the Use-Case Model artifact at one level down. It is separate artifact because it has a different responsible role (at this level). Otherwise, it has the same purpose and almost the same content: it becomes the Use-Case Model for the application of RUP to the development of the subsystem.
Domain:  Systems Engineering
Work Product Kinds:  Model
Purpose

The following people use the Use-Case Model:

  • The customer approves the Use-Case Model. When you have that approval, you know the system is what the customer wants. You can also use the model to discuss the system with the customer during development.
  • Potential users use the Use-Case Model to better understand the system.
  • When doing software development, the Software Architect uses the Use-Case Model to identify architecturally significant functionality.
  • When doing systems engineering, the System Architect uses the Use-Case Model in the identification of subsystems, and the System Designer elaborates the use-case flow of events into "white-box" form, produces system use-case realizations and subsystem use-case models, as part of use-case flowdown (see Concept: Use-Case Flowdown).
  • Designers use the Use-Case Model to get a system overview. When you refine the system, for example, you need documentation on the Use-Case Model to aid that work.
  • The Project Manager uses the Use-Case Model to plan and follow up the Use-Case Modeling and also the subsequent design.
  • People outside the project but within the organization, executives, and steering committees, use the Use-Case Model to gain insight into what has been done.
  • People review the Use-Case Model to give appropriate feedback to developers on a regular basis.
  • Designers use the Use-Case Model as a basis for their work.
  • Testers use the Use-Case Model to plan testing activities (use-case and integration testing) as early as possible.
  • Those who develop the next version of the system use the Use-Case Model to understand how the existing version works.
  • Documentation writers use the use cases as a basis for writing the system's user guides.
Relationships
Tailoring
Representation OptionsUML Representation:

Model, stereotyped as "Use-Case Model."

Tailor to support project needs. This might mean including only a subset of the sub-artifacts (properties), tailoring the level of formality in which the sub-artifacts are created and managed, and tailoring of the individual sub-artifacts. Document tailoring decisions in the  Work Product: Project-Specific Guidelines.