| <?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.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmlns:rmc="http://www.ibm.com/rmc" |
| rmc:version="7.5.0" xmi:id="_17Ve8Nd6EdmIm-bsRSNCgw" |
| name="architecture,_17PYUNd6EdmIm-bsRSNCgw" guid="_17Ve8Nd6EdmIm-bsRSNCgw" authors="Chris Doyle, Mark Dickson" |
| changeDate="2008-08-11T10:07:36.984-0700" changeDescription="(Mark Dickson) formatted & applied changes from Chris Doyle " |
| version="1.2"> |
| <sections xmi:id="_MN7hMNjcEdydTt3eL7YyCQ" name="Is the architecture understandable?" |
| guid="_MN7hMNjcEdydTt3eL7YyCQ"> |
| <sectionDescription><ul>
 |
| <li>
 |
| Is the description of the architecture complete, meaningful, and clear?
 |
| </li>
 |
| <li>
 |
| Is the&nbsp;architecture&nbsp;at an appropriate level of detail, given the objectives?
 |
| </li>
 |
| <li>
 |
| Are concepts&nbsp;handled in the simplest way possible?
 |
| </li>
 |
| <li>
 |
| Does&nbsp;the architecture clearly convey not only the solution but also the motivation and objectives related to
 |
| the&nbsp;decisions that have been made in shaping the architecture?
 |
| </li>
 |
| <li>
 |
| Are the key assumptions and decisions that the&nbsp;architecture is based on documented and visible to reviewers
 |
| and those who will use the architecture?
 |
| </li>
 |
| <li>
 |
| Is the architecture description current?
 |
| </li>
 |
| <li>
 |
| Have the design guidelines been followed?
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| <sections xmi:id="_U-wp8NvXEdyrWIQpneun6w" name="Have the architectural goals, constraints and requirements been adequately described and handled?" |
| guid="_U-wp8NvXEdyrWIQpneun6w"> |
| <sectionDescription><ul>
 |
| <li>
 |
| Have the <a class="elementLink"
 |
| href="./../../../core.tech.common.extend_supp/guidances/concepts/arch_goals_CB41D8AE.html"
 |
| guid="_HlRqANpbEdyP58ppo1Ieaw">Architectural Goals</a>&nbsp;been clearly described?
 |
| </li>
 |
| <li>
 |
| Have any <a class="elementLink"
 |
| href="./../../../core.tech.common.extend_supp/guidances/concepts/arch_constraints_AE56B662.html"
 |
| guid="_jdKSsNpiEdyP58ppo1Ieaw">Architectural Constraints</a>&nbsp;been identified and documented?
 |
| </li>
 |
| <li>
 |
| Have the <a class="elementLink"
 |
| href="./../../../core.tech.common.extend_supp/guidances/concepts/arch_significant_requirements_1EE5D757.html"
 |
| guid="_HrZGIA4MEduibvKwrGxWxA">Architecturally Significant Requirements</a>&nbsp;been identified and are they
 |
| clearly described.
 |
| </li>
 |
| <li>
 |
| Is the architecture is consistent with the architectural goals, constraints and requirements?
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| <sections xmi:id="_UCJbQNvYEdyrWIQpneun6w" name="Have necessary architectural mechanisms been identified and described?" |
| guid="_UCJbQNvYEdyrWIQpneun6w"> |
| <sectionDescription><ul>
 |
| <li>
 |
| Is it clear when&nbsp;each <a class="elementLink"
 |
| href="./../../../core.tech.common.extend_supp/guidances/concepts/arch_mechanism_2932DFB6.html"
 |
| guid="_mzxI0A4LEduibvKwrGxWxA">Architectural Mechanism</a>&nbsp;should be applied?
 |
| </li>
 |
| <li>
 |
| Is there a clearly defined design pattern in place to support&nbsp;each mechanism?
 |
| </li>
 |
| <li>
 |
| Does each mechanism adequately address the requirements it is intended to meet?
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| <sections xmi:id="_hKAz8NvZEdyrWIQpneun6w" name="Have the system partitions been adequately defined?" |
| guid="_hKAz8NvZEdyrWIQpneun6w"> |
| <sectionDescription><ul class="noindent">
 |
| <li>
 |
| Is partitioning approach clearly described and applied consistently?
 |
| </li>
 |
| <li>
 |
| Does the partitioning approach reduce complexity and improve understanding?
 |
| </li>
 |
| <li>
 |
| Have the partitions been defined to be highly cohesive within the partition, while the partitions themselves are
 |
| loosely coupled?
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| <sections xmi:id="_eYXBINvYEdyrWIQpneun6w" name="Have the key elements been adequately defined?" |
| guid="_eYXBINvYEdyrWIQpneun6w"> |
| <sectionDescription><ul>
 |
| <li>
 |
| Have the <a class="elementLink"
 |
| href="./../../../core.tech.common.extend_supp/guidances/concepts/key_abstractions_1474DBF2.html"
 |
| guid="_pLEGUNqGEdy88NBoQgfGyg">Key Abstractions</a>&nbsp;adequately defined?
 |
| </li>
 |
| <li>
 |
| Have the the key design elements (i.e., <a class="elementLink"
 |
| href="./../../../core.tech.common.extend_supp/guidances/concepts/component_CB167D48.html"
 |
| guid="_0YP18MlgEdmt3adZL5Dmdw">Component</a>s) adequately defined?
 |
| </li>
 |
| <li style="LIST-STYLE-TYPE: none">
 |
| <ul>
 |
| <li>
 |
| Do the components have well-defined interfaces?
 |
| </li>
 |
| <li>
 |
| Have the system's responsibilities been allocated to the components?
 |
| </li>
 |
| <li>
 |
| Are the number and types of components reasonable?
 |
| </li>
 |
| </ul>
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| <sections xmi:id="_KU3WQNvbEdyrWIQpneun6w" name="Have interfaces to external systems been adequately represented?" |
| guid="_KU3WQNvbEdyrWIQpneun6w"> |
| <sectionDescription><p>
 |
| See <a class="elementLinkWithType"
 |
| href="./../../../core.tech.common.extend_supp/guidances/guidelines/repres_interfaces_to_ext_systems_51A34F6E.html"
 |
| guid="_0gjdYMlgEdmt3adZL5Dmdw">Guideline: Representing Interfaces to External Systems</a>
 |
| </p></sectionDescription> |
| </sections> |
| <sections xmi:id="_bQB24NvbEdyrWIQpneun6w" name="Has all reuse been identified?" |
| guid="_bQB24NvbEdyrWIQpneun6w"> |
| <sectionDescription>Have all reusable assets been identified -- either those reused by the system, or those elements within the system that
 |
| have been built to be reused.&nbsp; For more information, see <a class="elementLinkWithType"
 |
| href="./../../../core.tech.common.extend_supp/guidances/guidelines/software_reuse_B6B04C26.html"
 |
| guid="_vO2uoO0OEduUpsu85bVhiQ">Guideline: Software Reuse</a>.</sectionDescription> |
| </sections> |
| <sections xmi:id="_pgGfsNvaEdyrWIQpneun6w" name="Has the architecture been built to evolve?" |
| guid="_pgGfsNvaEdyrWIQpneun6w"> |
| <sectionDescription><ul class="noindent">
 |
| <li>
 |
| Can the&nbsp;architecture easily evolve,&nbsp;so that&nbsp;expected changes can be easily accommodated?
 |
| </li>
 |
| <li>
 |
| Are all technical risks either mitigated or addressed in a contingency plan?
 |
| </li>
 |
| <li>
 |
| Has the&nbsp;architecture been overly structured to handle unlikely change at the expense of simplicity and
 |
| comprehensibility? (Hint: "Yes" to this question is not good.)
 |
| </li>
 |
| </ul><br />
 |
| <br /></sectionDescription> |
| </sections> |
| <sections xmi:id="_aWun4NjcEdydTt3eL7YyCQ" name="Can the architecture be delivered by the team?" |
| guid="_aWun4NjcEdydTt3eL7YyCQ"> |
| <sectionDescription><ul>
 |
| <li>
 |
| Does the architecture provide a suitable basis for organizing the development teams?
 |
| </li>
 |
| <li>
 |
| Does each team have the skills required to implement their allocated components?
 |
| </li>
 |
| <li>
 |
| Are responsibilities divided well between teams?
 |
| </li>
 |
| <li>
 |
| Do all team members share the same understanding of the architecture as the one presented by the architect?
 |
| </li>
 |
| <li>
 |
| Can team members understand enough from the architecture to successfully design and code their allocated
 |
| components?
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| <sections xmi:id="_9LIDYNvbEdyrWIQpneun6w" name="Has the software been adequately mapped to the hardware?" |
| guid="_9LIDYNvbEdyrWIQpneun6w"> |
| <sectionDescription><ul class="noindent">
 |
| <li>
 |
| Have the deployable software components been mapped to physical nodes?
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| </org.eclipse.epf.uma:ContentDescription> |
