| first draft of architectural model | to communicate with customers | a particular audience | several different views such as-  The logical breakdown into subsystems, often shown using package diagrams
 -  The dynamics of the interaction among components at run time, expressed using interaction or activity diagrams
 -  The data that will be shared among the subsystems, expressed using class diagrams
 -  The components that will exist at run time, and the machines or devices on which they will be located, expressed using component and deployment diagrams 
 
  |  | the terms that people use when they communicate with each other about lower-level details | generic to ensure reusability | use case modellers guidance about the steps the user will need to perform | the same time as the central use cases | information about the interfaces and dynamic interactions among the subsystems | 9.4 - Software Architecture | - integrating the work of individual people to form the final system
 - planning and co-ordination of the work of developing a complex software system which is distributed among a large number of people
 - planning the evolution of the system, such as subsystems that are envisioned to be part of a future release
 
  | each system component, encouraging reuse | architectural model |