• Architecture

Here are some examples for representing the architecture. Architecture can be represented in a variety of ways, according to the needs of the project team. See Architecture for more information.

Feel free to use one or more of these examples or create your own.

The Architect should decide what views are useful for describing the system under consideration. 

Consider one or more relevant views of the architecture and document each one using the provided template for the architectural view. If needed, document information that applies to more than one view using the template provided for the Software Architecture Document to get an integrated representation of the architecture instead of just snapshots taken from different angles.

The structuring of the documents must support the needs of the intended audience. For example, instead of a document for the implementation view developers may find more useful alternative forms for the project directory structure like the template provided for the project startup kit.

Keep documentation up-to-date but to an essential minimum. During elaboration decisions are reconsidered frequently so constant revision of the documentation is an unnecessary expense.  Determine points in the development process when documentation should be updated.

• sw_architecture_doc_tpl.dot
• project_startup_kit.zip
• sw_architecture_view_tpl.dot
• software_arch_document.dot