OpenUP/OpenUP_PT/library/openup_basic/workproducts/architecture_notebook.xmi

<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ArtifactDescription 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" epf:version="1.0.0" xmi:id="_H4gOYKYTEdmvhNXG0Oc2uA" name="architecture_notebook,_0XAf0MlgEdmt3adZL5Dmdw" guid="_H4gOYKYTEdmvhNXG0Oc2uA" changeDate="2007-03-03T10:34:06.078+0000" version="1.0.0">
  <mainDescription>&lt;p&gt;
    This artifact&amp;nbsp;is a communication vehicle that tells Developers what pieces to build, as well as how those pieces
    behave and interact with each other. It determines the project structure so that managers can plan the project. It also
    gives whoever must maintain and change the architecture later their first glimpse of the system; and an understanding
    of the motivation behind the important technical decisions.
&lt;/p&gt;
&lt;p&gt;
    This artifact focuses on specific aspects of the design, concentrating on structure, essential elements, key scenarios
    and those aspects that have a lasting impact on system qualities such as performance, reliability, adaptability and
    cost. It defines the set of mechanisms, patterns and styles that will guide the rest of the design, assuring its
    integrity.
&lt;/p&gt;
&lt;p&gt;
    Architectural elements make excellent units of implementation, unit testing, integration, configuration management
    and&amp;nbsp;documentation. The organisation of the architecture can also help the &lt;a class=&quot;elementLink&quot;
    href=&quot;./../../openup_basic/roles/project_manager,_0a0o0MlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0a0o0MlgEdmt3adZL5Dmdw&quot;&gt;Project
    Manager&lt;/a&gt; decide on the organisation of the team.
&lt;/p&gt;</mainDescription>
  <purpose>&lt;p&gt;
    To describe the essential part of the design of the system so the integrity and understandability of the system is
    assured.
&lt;/p&gt;</purpose>
  <representationOptions>&lt;p&gt;
    The he architecture can be represented in many forms and from many viewpoints, depending on the needs of the project
    and the preferences of the project team. The architecture can be expressed as a simple metaphor or as a comparison to a
    predefined architectural style or set of styles. It may be a precise set of models or documents that describe the
    various aspects of the system's key elements. Expressing it as skeletal build is another option - although this build
    may need to be baselined and preserved to ensure that the essence of the system can be understood as the system grows.
&lt;/p&gt;
&lt;p&gt;
    It is frequently a design artifact that must be represented in a readable and accessible way. It can reference models
    that describe &lt;a class=&quot;elementLink&quot;
    href=&quot;./../../openup_basic/guidances/guidelines/architectural_view,_T9nygClEEduLGM8dfVsrKg.html&quot;
    guid=&quot;_T9nygClEEduLGM8dfVsrKg&quot;&gt;Architectural View&lt;/a&gt;s for communicating the architecture. A view is a representation
    of a system from the perspective of a related set of concerns.&amp;nbsp;To choose the appropriate set of
    views,&amp;nbsp;identify the Stakeholders who depend on software architecture documentation and the information that they
    need.
&lt;/p&gt;
&lt;p&gt;
    It need not be a formal document. The essence of the architecture can often be communicated through a series of simple
    diagrams on a whiteboard; or as a list of decisions. Choose the medium that best meets the needs of the project.
&lt;/p&gt;</representationOptions>
</org.eclipse.epf.uma:ArtifactDescription>