OpenUP/OpenUP_PT/library/openup_basic/guidances/guidelines/architectural_view.xmi

<?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>&lt;p&gt; 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&lt;/strong&gt; [&lt;a class=&quot;elementLinkWithUserText&quot; href=&quot;./../../../openup_basic/guidances/supportingmaterials/references,_9ToeIB83Edqsvps02rpOOg.html&quot; guid=&quot;_9ToeIB83Edqsvps02rpOOg&quot;&gt;KRU95&lt;/a&gt;].. 
&lt;/p&gt;
&lt;p&gt;
    &lt;img height=&quot;254&quot; alt=&quot;4+1 Views of Software Architecture&quot; src=&quot;./resources/4plus1_2.jpg&quot; width=&quot;405&quot; /&gt;
&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt; 
    &lt;p&gt; Use-case view:&lt;/strong&gt; Describes functionality of the system, 
      its external interfaces, and its principal users. The use-case view&amp;nbsp;contains 
      the &lt;a class=&quot;elementLink&quot; href=&quot;./../../../openup_basic/workproducts/uc_model,_0UCrZclgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0UCrZclgEdmt3adZL5Dmdw&quot;&gt;Use-Case 
      Model&lt;/a&gt;. This view is mandatory when using the 4+1 Views, because all 
      elements of the architecture should be derived from requirements. &lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt; 
    &lt;p&gt; Logical view: &lt;/strong&gt;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: &lt;/strong&gt;This 
      view is mandatory when using the 4+1 Views of Software Architecture. &lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt; 
    &lt;p&gt;Implementation view: &lt;/strong&gt;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. &lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt; 
    &lt;p&gt;Process view: &lt;/strong&gt;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&amp;#8482; 
      (EJB&amp;#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 &lt;/strong&gt;about 
      run-time system quality attributes, such as performance and reliability. 
      This view is optional when using the 4+1 Views. &lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt; 
    &lt;p&gt; Deployment views: &lt;/strong&gt;Describe how the system is mapped to 
      the hardware. This view is optional when using the 4+1 Views. &lt;/p&gt;
  &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In addition, you may wish to represent the following, &lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
    &lt;p&gt; Data view:&lt;/strong&gt; 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. &lt;/p&gt;
  &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;br /&gt;</mainDescription>
</org.eclipse.epf.uma:ContentDescription>