Purpose
  • To verify that the analysis objects meet the functional requirements made on the system
  • To verify that the analysis objects and collaborations are consistent

Conduct a review informally at the end of the workshop, as a synchronization point, as well as the conclusion to the Activity: Use-Case Analysis.

Check-points for Analysis Classes

  • Are the classes reasonable?
  • Does the name of each class clearly reflect the role it plays?
  • Does the class represent a single well-defined abstraction? If not, consider splitting it.
  • Does a class define any attributes and responsibilities that are not functionally coupled to the other attributes or responsibilities defined by that class?
  • Do the classes offer the behavior the use-case realizations and other classes require?
  • Are all specific requirements on the class in the requirement specification addressed?

Check-points for Use-Case Realizations

See Checkpoints for Use Case Realizations

Display Rational Unified Process using frames

 

© Rational Software Corporation 1998 Rational Unified Process 5.1 (build 43)