| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:GuidanceDescription xmi:version="2.0" |
| xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.5/uma.ecore" |
| xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf" |
| epf:version="1.5.0" xmi:id="-sKBCb98PYCcliL0zVljcyQ" |
| name="new_example,_4bC4cNs_EdyEW4klSH3vRA" guid="-sKBCb98PYCcliL0zVljcyQ" changeDate="2008-02-15T06:14:05.812-0800" |
| version="7.2.0"> |
| <mainDescription><p>
 |
| You may want to consider the following views (not all views are relevant to all systems or all the stakeholders). This
 |
| set of views is known as the 4+1 Views of Software Architecture [<a class="elementLinkWithUserText" href="./../../../core.tech.common.base/guidances/supportingmaterials/references.tech_6CCF393.html" guid="_9ToeIB83Edqsvps02rpOOg">KRU95</a>].
 |
| </p>
 |
| <p>
 |
| <img height="254" alt="4+1 Views of Software Architecture" src="./resources/4plus1_2.jpg" width="405" />
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <p>
 |
| <strong>Use-case view</strong>: Describes functionality of the system, its external interfaces, and its
 |
| principal users. This view is mandatory when using the 4+1 Views, because all elements of the architecture
 |
| should be derived from requirements.
 |
| </p>
 |
| </li>
 |
| <li>
 |
| <p>
 |
| <strong>Logical view</strong>: Describes how the system is structured in terms of units of implementation. The
 |
| elements are packages, classes, and interfaces. The relationship between elements shows dependencies, interface
 |
| realizations, part-whole relationships, and so forth. Note: This view is mandatory when using the 4+1 Views of
 |
| Software Architecture.
 |
| </p>
 |
| </li>
 |
| <li>
 |
| <p>
 |
| <strong>Implementation view</strong>: Describes how development artifacts are organized in the file system. The
 |
| elements are files and directories (any configuration items). This includes development artifacts and
 |
| deployment artifacts. This view is optional when using the 4+1 Views.
 |
| </p>
 |
| </li>
 |
| <li>
 |
| <p>
 |
| <strong>Process view</strong>: Describes how the run-time system is structured as a set of elements that have
 |
| run-time behavior and interactions. Run-time structure often bears little resemblance to the code structure. It
 |
| consists of rapidly changing networks of communication objects. The elements are components that have run-time
 |
| presence (processes, threads, Enterprise JavaBeans&trade; (EJB&trade;), servlets, DLLs, and so on), data stores, and
 |
| complex connectors, such as queues. Interaction between elements varies, based on technology. This view is
 |
| useful for thinking about run-time system quality attributes, such as performance and reliability. This view is
 |
| optional when using the 4+1 Views.
 |
| </p>
 |
| </li>
 |
| <li>
 |
| <p>
 |
| <strong>Deployment view</strong>: Describe how the system is mapped to the hardware. This view is optional when
 |
| using the 4+1 Views.
 |
| </p>
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| In addition, you may wish to represent the following,
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <p>
 |
| <strong>Data view</strong>: A specialization of the logical view. Use this view if persistence is a significant
 |
| aspect of the system, and the translation from the design model to the data model is not done automatically by
 |
| the persistence mechanism.
 |
| </p>
 |
| </li>
 |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:GuidanceDescription> |
