Artifact: System Analysis Model
This is the Analysis Model at the system level. The system context is shown as the top level collaboration in this model.
Domain:  Systems Engineering
Work Product Kinds:  Model
Purpose

The System Analysis Model contains the top-level collaboration (system and actors showing the system context), design subsystems, and Process Model elements (active classes), and any associated artifacts. The System Analysis Model might be a temporary artifact, as is the case where it evolves into a system design model, or it might continue to live on through some or all of the project, and perhaps beyond, serving as a conceptual overview of the system.

Relationships
Illustrations
Tailoring
Representation OptionsUML Representation:

Model, stereotyped as "system analysis model."

The System Analysis Model is pitched at a higher level of abstraction than the System Design Model, and it might be permissible to allow the System Analysis Model to simply evolve into the System Design Model (at which time the System Analysis Model ceases to exist). There might be good reasons to continue to maintain a separate System Analysis Model:

  • When the development is of a family of systems, with differing realizations and deployments, for which the System Analysis Model remains a good overall description.
  • When the design is elaborate and the System Analysis Model remains a useful teaching instrument.

It needs to be understood that the System Analysis Model, if retained, does need to be kept in synch with the System Design Model to be useful. This might require more work (to be done properly) than the project is willing to devote to it. The Project Manager and System Architect need to consider this carefully.