The implementation view is one of five architectural views of a system. The other architectural views are the logical view, use-case view, process view, and deployment view.

The purpose of the implementation view is to capture the architectural decisions made for the implementation. Typically, the implementation view contains:

  • an enumeration of all subsystems in the implementation model
  • component diagrams illustrating how subsystems are organized in layers and hierarchies
  • illustrations of import dependencies between subsystems

The implementation view is useful for:

  • assigning implementation work to individuals and teams, or subcontractors
  • assessing the amount of code to be developed, modified, or deleted
  • reasoning large-scale reuse
  • considering release strategies

The implementation view and the other architectural views are documented in the Software Architecture Document.



Rational Unified Process  

2003.06.13