OpenUP/OpenUP_baseline_EN/exported_HTML_1_0/openup/guidances/guidelines/architectural_view.html - epf/org.eclipse.epf.nl-libraries - Git at Google

 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
 <!-- VERSION rmc:7.1.0 -->
 <html xmlns="http://www.w3.org/1999/xhtml">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
 <!-- START NON-TRANSLATABLE -->
 <title>openup&amp;#92;guidances&amp;#92;guidelines&amp;#92;&amp;#92;architectural_view.xmi</title>
 </head>
 <!-- WARNING: do not modify the generated comments in this file below this line.  They are used as markers for the import process. -->
 <body>
 Element Name: architectural_view.xmi<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: presentationName<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:presentationName,_T9nygClEEduLGM8dfVsrKg CRC: 2033001342 -->Architectural View<!-- END:presentationName,_T9nygClEEduLGM8dfVsrKg -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: briefDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:briefDescription,_T9nygClEEduLGM8dfVsrKg CRC: 3932502239 -->Architecture can be represented from a variety of viewpoints, all of which can be combined to create a holistic view of the system.<!-- END:briefDescription,_T9nygClEEduLGM8dfVsrKg -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: mainDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:mainDescription,-cnGBBA4NXmhTIjHjlHx4Mw CRC: 2124966115 --><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 [<a class="elementLinkWithUserText" href="./../../../openup/guidances/supportingmaterials/references_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>
             Use-case view: Describes functionality of the system, its external interfaces, and its principal users. The
             use-case view&nbsp;contains the <a class="elementLink" href="./../../../openup/workproducts/use_case_model_intent_req_ucm_17B6B2A6.html" guid="_0UCrZclgEdmt3adZL5Dmdw">use_case_model_intent_req_ucm</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: 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>
             Implementation view: 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: 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>
             Deployment views: 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: 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 />
 </p><!-- END:mainDescription,-cnGBBA4NXmhTIjHjlHx4Mw -->
 </body>
 </html>
	<?xml version="1.0" encoding="UTF-8"?>
	<!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
	<!-- VERSION rmc:7.1.0 -->
	<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
	<!-- START NON-TRANSLATABLE -->
	<title>openup&#92;guidances&#92;guidelines&#92;&#92;architectural_view.xmi</title>
	</head>
	<!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. -->
	<body>
	Element Name: architectural_view.xmi<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: presentationName<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:presentationName,_T9nygClEEduLGM8dfVsrKg CRC: 2033001342 -->Architectural View<!-- END:presentationName,_T9nygClEEduLGM8dfVsrKg -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: briefDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:briefDescription,_T9nygClEEduLGM8dfVsrKg CRC: 3932502239 -->Architecture can be represented from a variety of viewpoints, all of which can be combined to create a holistic view of the system.<!-- END:briefDescription,_T9nygClEEduLGM8dfVsrKg -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: mainDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:mainDescription,-cnGBBA4NXmhTIjHjlHx4Mw CRC: 2124966115 --><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 [<a class="elementLinkWithUserText" href="./../../../openup/guidances/supportingmaterials/references_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>
	Use-case view: Describes functionality of the system, its external interfaces, and its principal users. The
	use-case view contains the <a class="elementLink" href="./../../../openup/workproducts/use_case_model_intent_req_ucm_17B6B2A6.html" guid="_0UCrZclgEdmt3adZL5Dmdw">use_case_model_intent_req_ucm</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: 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>
	Implementation view: 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: 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™ (EJB™), 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>
	Deployment views: 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: 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 />
	</p><!-- END:mainDescription,-cnGBBA4NXmhTIjHjlHx4Mw -->
	</body>
	</html>