| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" rmc:version="7.1.0" epf:version="1.0.0" xmi:id="-cnGBBA4NXmhTIjHjlHx4Mw" name=",_T9nygClEEduLGM8dfVsrKg" guid="-cnGBBA4NXmhTIjHjlHx4Mw" changeDate="2006-08-22T11:29:43.831-0700" version="1.0.0"> |
| <mainDescription><p> As an Architect, 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</strong> [<a class="elementLinkWithUserText" href="./../../../openup_basic/guidances/supportingmaterials/references,_9ToeIB83Edqsvps02rpOOg.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> Use-case view:</strong> Describes functionality of the system, |
| its external interfaces, and its principal users. The use-case view&nbsp;contains |
| the <a class="elementLink" href="./../../../openup_basic/workproducts/uc_model,_0UCrZclgEdmt3adZL5Dmdw.html" guid="_0UCrZclgEdmt3adZL5Dmdw">Use-Case |
| Model</a>. 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> 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: </strong>This |
| view is mandatory when using the 4+1 Views of Software Architecture. </p> |
| </li> |
| <li> |
| <p>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>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&#8482; |
| (EJB&#8482;), 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 </strong>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> Deployment views: </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> 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> |
| <p><br /></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |