<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-7Psn_E5lP1tzfaBc7sV-gA" name="epilogue_outline_the_architecture,_y_WSULn4Ee2ItPaV9bHRfA" guid="-7Psn_E5lP1tzfaBc7sV-gA" changeDate="2023-03-05T21:34:16.686+0330">
  <mainDescription>This task focuses on envisioning the initial architecture and outlining the&amp;nbsp;architectural decisions that will guide&#xD;
development and testing. It relies on gathering experience gained in similar systems or problem domains to constrain and&#xD;
focus the architecture so that effort is not wasted in re-inventing architecture. &#xD;
&lt;p>&#xD;
    The results are captured for future reference and are communicated across the team. It is important that the team has&#xD;
    enough information to understand the technical approach being taken.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    The architecture evolves organically over time by outlining and refining portions of it. A few people get together in a&#xD;
    room and sketch out what they think the architecture will be. This envisioning effort sets the foundation for&#xD;
    prototyping. If the solution is similar to a previously produced solution (or is a well-known solution domain), then it&#xD;
    will probably be good enough to reference that example as evidence of the feasibility of the approach. In some cases,&#xD;
    it may be necessary to develop one or more prototypes to validate some of the decisions or clarify some of the&#xD;
    requirements.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    The work done here does not seek to produce a detailed and comprehensive technical specification for the system.&#xD;
    Rather, the approach should be to decide the overall technical approach at a high level. The conclusion of this work&#xD;
    should produce just enough information to communicate the architecture to the team, and to demonstrate its viability to&#xD;
    the customer. This allows the project to move forward, enabling you to refine and baseline the architecture&#xD;
&lt;/p></mainDescription>
  <keyConsiderations>It&amp;nbsp;is important to reduce the complexity of the&amp;nbsp;solution by raising the levels of abstraction. &#xD;
&lt;p>&#xD;
    It is critical that this task be performed collaboratively with active involvement of other team members and project&#xD;
    stakeholders so that consensus and common understanding is reached. It is particularly vital to involve the&#xD;
    developer(s) throughout this task. The architecture effort&amp;nbsp;is about providing leadership and coordination of the&#xD;
    technical work rather than putting in a solo performance.&#xD;
&lt;/p></keyConsiderations>
  <sections xmi:id="_KhSvALuAEe29CKVnbOLlJg" name="Identify architectural goals  " guid="_KhSvALuAEe29CKVnbOLlJg"/>
  <sections xmi:id="_Ls7bsLuAEe29CKVnbOLlJg" name="Identify architecturally significant requirements  " guid="_Ls7bsLuAEe29CKVnbOLlJg"/>
  <sections xmi:id="_NGf2sLuAEe29CKVnbOLlJg" name="Identify constraints on the architecture  " guid="_NGf2sLuAEe29CKVnbOLlJg"/>
  <sections xmi:id="_OD3d4LuAEe29CKVnbOLlJg" name="Identify key abstractions  " guid="_OD3d4LuAEe29CKVnbOLlJg"/>
  <sections xmi:id="_PJ88MLuAEe29CKVnbOLlJg" name="Identify reuse opportunities  " guid="_PJ88MLuAEe29CKVnbOLlJg"/>
  <sections xmi:id="_QJJvYLuAEe29CKVnbOLlJg" name="Define approach for partitioning the system  " guid="_QJJvYLuAEe29CKVnbOLlJg"/>
  <sections xmi:id="_RJzUELuAEe29CKVnbOLlJg" name="Define approach for deploying the system  " guid="_RJzUELuAEe29CKVnbOLlJg"/>
  <sections xmi:id="_SCB8kLuAEe29CKVnbOLlJg" name="Identify architectural mechanisms  " guid="_SCB8kLuAEe29CKVnbOLlJg"/>
  <sections xmi:id="_TN8WELuAEe29CKVnbOLlJg" name="Identify interfaces to external systems  " guid="_TN8WELuAEe29CKVnbOLlJg"/>
  <sections xmi:id="_UIX-ALuAEe29CKVnbOLlJg" name="Verify architectural consistency  " guid="_UIX-ALuAEe29CKVnbOLlJg"/>
  <sections xmi:id="_VGxf8LuAEe29CKVnbOLlJg" name="Capture and communicate architectural decisions  " guid="_VGxf8LuAEe29CKVnbOLlJg"/>
  <purpose>Outline the Architecture</purpose>
</org.eclipse.epf.uma:TaskDescription>
