Roles and Activities > Developer Role Set > Software Architect > Prioritize Use Cases

Purpose
  • To define input to the selection of the set of scenarios and use cases that are to be analyzed in the current iteration.
  • To define the set of scenarios and use cases that represent some significant, central functionality.
  • To define the set of scenarios and use cases that have a substantial architectural coverage (that exercise many architectural elements) or that stress or illustrate a specific, delicate point of the architecture.
Steps
Input Artifacts: Resulting Artifacts:
Role: Software Architect

Workflow Details:

Prioritize Use Cases and Scenarios To top of page

A software architect proposes the technical contents and the order of successive iterations by selecting a certain number of scenarios and use cases to be analyzed and designed. This technical proposal is completed and refined by the various development teams, based on personnel availability, customer requirements in terms of deliverables, availability of tools and COTS products, and the needs of other projects.

The selection of scenarios and use cases that constitute the use-case view is driven by the following:

In general the impact on architecture is correlated to the criticality. However, it should be noted that there may be critical use cases that have little or no impact, and vice versa, some ancillary use case may have a big impact on the architecture, which makes it questionable from a business perspective.

Document the Use-Case View To top of page

The use-case view is documented in the use-case view section of the Software Architecture Document. This section contains a listing of the significant use cases and scenarios within each package in the use-case model, together with significant properties such as descriptions of the flow of events, relationships, use-case diagrams, and special requirements related to each use case. Note that if the use-case view is developed early in the iteration, some of these properties may not yet exist.

Evaluate Your Results To top of page

The use-case view should be checked at this stage to verify that the work is on track, but not to review the use-case view in detail. See especially checkpoints for use-case view in Activity: Review the Architecture.

Copyright  1987 - 2001 Rational Software Corporation


Display Rational Unified Process using frames

Rational Unified Process