| <?xml version="1.0" encoding="UTF-8"?> |
| <xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.4/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0"> |
| <org.eclipse.epf.uma:ProcessDescription xmi:id="-E-d4Jcu297rxUq8lte8qnw" name="CP1 with all elements,_4sCtsTzgEdq5ysFONr1BGQ" guid="-E-d4Jcu297rxUq8lte8qnw"> |
| <mainDescription><p> |
| The subcategories of process are delivery process and capability pattern.&nbsp; A delivery process defines a complete |
| or end-to-end process.&nbsp; A capability pattern is a process fragment used to compose a delivery process. |
| </p> |
| <p> |
| &nbsp; |
| </p></mainDescription> |
| <keyConsiderations>This capability pattern can be used to quickly construct an Inception phase iteration in a delivery process.&nbsp; Copy or |
| extend the pattern&nbsp;repeatedly to create as many iterations as necessary for the particular delivery process.</keyConsiderations> |
| <purpose>This capability pattern can be used to quickly construct an Inception phase iteration in a delivery process.&nbsp; Copy or |
| extend the pattern&nbsp;repeatedly to create as many iterations as necessary for the particular delivery process. <br /> |
| <br /></purpose> |
| <alternatives><p> |
| To explain the work involved in the Analysis and Design discipline, the activities and work products are organized into |
| a capability pattern for the discipline. |
| </p> |
| <p> |
| In the Inception Phase, analysis and design is concerned with establishing whether the system as envisioned is |
| feasible, and with assessing potential technologies for the solution (in <a href="resources/wfs_archsyn.htm"><font |
| color="#0000ff">Perform Architectural Synthesis</font></a>). If it is felt that little risk attaches to the development |
| (because, for example, the domain is well understood, the system is not novel, and so on) then this workflow detail may |
| be omitted. |
| </p> |
| <p> |
| The early Elaboration Phase focuses on creating an initial architecture for the system ( <a |
| href="resources/wfs_and1.htm"><font color="#0000ff">Define a Candidate Architecture</font></a>) to provide a starting |
| point for the main analysis work. If the architecture already exists (either because it was produced in previous |
| iterations, in previous projects, or is obtained from an application framework), the focus of the work changes to |
| refining the architecture ( <a href="resources/wfs_and2.htm"><font color="#0000ff">Refine the Architecture</font></a>) |
| and analyzing behavior and creating an initial set of elements which provide the appropriate behavior ( <a |
| href="resources/wfs_and3.htm"><font color="#0000ff">Analyze Behavior</font></a>). |
| </p> |
| <p> |
| After the initial elements are identified, they are further refined. <a href="resources/wfs_and4.htm"><font |
| color="#0000ff">Design Components</font></a> produce a set of components which provide the appropriate behavior to |
| satisfy the requirements on the system. If the system includes a database, then <a href="resources/wfs_and7.htm"><font |
| color="#0000ff">Design the Database</font></a> occurs in parallel. The result is an initial set of components which are |
| further refined in <a href="resources/wfd_imp.htm"><font color="#0000ff">Implementation</font></a>.<br /> |
| </p>&nbsp;<br /> |
| <br /></alternatives> |
| <howtoStaff><p> |
| To explain the work involved in the Analysis and Design discipline, the activities and work products are organized into |
| a capability pattern for the discipline. |
| </p> |
| <p> |
| In the Inception Phase, analysis and design is concerned with establishing whether the system as envisioned is |
| feasible, and with assessing potential technologies for the solution (in <a href="resources/wfs_archsyn.htm"><font |
| color="#0000ff">Perform Architectural Synthesis</font></a>). If it is felt that little risk attaches to the development |
| (because, for example, the domain is well understood, the system is not novel, and so on) then this workflow detail may |
| be omitted. |
| </p> |
| <p> |
| The early Elaboration Phase focuses on creating an initial architecture for the system ( <a |
| href="resources/wfs_and1.htm"><font color="#0000ff">Define a Candidate Architecture</font></a>) to provide a starting |
| point for the main analysis work. If the architecture already exists (either because it was produced in previous |
| iterations, in previous projects, or is obtained from an application framework), the focus of the work changes to |
| refining the architecture ( <a href="resources/wfs_and2.htm"><font color="#0000ff">Refine the Architecture</font></a>) |
| and analyzing behavior and creating an initial set of elements which provide the appropriate behavior ( <a |
| href="resources/wfs_and3.htm"><font color="#0000ff">Analyze Behavior</font></a>). |
| </p> |
| <p> |
| After the initial elements are identified, they are further refined. <a href="resources/wfs_and4.htm"><font |
| color="#0000ff">Design Components</font></a> produce a set of components which provide the appropriate behavior to |
| satisfy the requirements on the system. If the system includes a database, then <a href="resources/wfs_and7.htm"><font |
| color="#0000ff">Design the Database</font></a> occurs in parallel. The result is an initial set of components which are |
| further refined in <a href="resources/wfd_imp.htm"><font color="#0000ff">Implementation</font></a>.<br /> |
| </p> |
| &nbsp;<br /> |
| <br /></howtoStaff> |
| <externalId>EXternal ID:CP1 with all elements</externalId> |
| <scope><p> |
| To explain the work involved in the Analysis and Design discipline, the activities and work products are organized into |
| a capability pattern for the discipline. |
| </p> |
| <p> |
| In the Inception Phase, analysis and design is concerned with establishing whether the system as envisioned is |
| feasible, and with assessing potential technologies for the solution (in <a href="resources/wfs_archsyn.htm"><font |
| color="#0000ff">Perform Architectural Synthesis</font></a>). If it is felt that little risk attaches to the development |
| (because, for example, the domain is well understood, the system is not novel, and so on) then this workflow detail may |
| be omitted. |
| </p> |
| <p> |
| The early Elaboration Phase focuses on creating an initial architecture for the system ( <a |
| href="resources/wfs_and1.htm"><font color="#0000ff">Define a Candidate Architecture</font></a>) to provide a starting |
| point for the main analysis work. If the architecture already exists (either because it was produced in previous |
| iterations, in previous projects, or is obtained from an application framework), the focus of the work changes to |
| refining the architecture ( <a href="resources/wfs_and2.htm"><font color="#0000ff">Refine the Architecture</font></a>) |
| and analyzing behavior and creating an initial set of elements which provide the appropriate behavior ( <a |
| href="resources/wfs_and3.htm"><font color="#0000ff">Analyze Behavior</font></a>). |
| </p> |
| <p> |
| After the initial elements are identified, they are further refined. <a href="resources/wfs_and4.htm"><font |
| color="#0000ff">Design Components</font></a> produce a set of components which provide the appropriate behavior to |
| satisfy the requirements on the system. If the system includes a database, then <a href="resources/wfs_and7.htm"><font |
| color="#0000ff">Design the Database</font></a> occurs in parallel. The result is an initial set of components which are |
| further refined in <a href="resources/wfd_imp.htm"><font color="#0000ff">Implementation</font></a>.<br /> |
| </p>&nbsp;<br /> |
| <br /></scope> |
| <usageNotes><p> |
| The subcategories of process are delivery process and capability pattern.&nbsp; A delivery process defines a complete |
| or end-to-end process.&nbsp; A capability pattern is a process fragment used to compose a delivery process. |
| </p></usageNotes> |
| </org.eclipse.epf.uma:ProcessDescription> |
| <org.eclipse.epf.uma:ActivityDescription xmi:id="-YVTZRE5oy5oGcue1XXh3dQ" name="Activity1,_E73rITziEdq5ysFONr1BGQ" guid="-YVTZRE5oy5oGcue1XXh3dQ"> |
| <mainDescription><p> |
| This Workflow Detail: |
| </p> |
| <ul> |
| <li> |
| Provides the natural <b>transition from analysis</b> activities <b>to design</b> activities, identifying: |
| <ul> |
| <li> |
| appropriate design elements from analysis elements |
| </li> |
| <li> |
| appropriate design mechanisms from related analysis mechanisms |
| </li> |
| </ul> |
| </li> |
| <li> |
| <b>Describes</b> the organization of the system's <b>run-time and deployment architecture</b> |
| </li> |
| <li> |
| <b>Organizes the implementation model</b> so as to make the transition between design and implementation seamless |
| </li> |
| <li> |
| <b>Maintains the consistency and integrity of the architecture</b>, ensuring that: |
| <ul> |
| <li> |
| new design elements identified for the current iteration are integrated with pre-existing design elements. |
| </li> |
| <li> |
| maximal re-use of available components and design elements is achieved as early as possible in the design |
| effort. |
| </li> |
| </ul> |
| </li> |
| </ul></mainDescription> |
| <keyConsiderations><p> |
| Key considerations: |
| </p> |
| <ul> |
| <li> |
| key1 |
| </li> |
| <li> |
| key2 |
| </li> |
| <li> |
| key3 |
| </li> |
| <li> |
| key4 |
| </li> |
| <li> |
| key5 |
| </li> |
| <li> |
| key6 |
| </li> |
| <li> |
| key7 |
| </li> |
| </ul></keyConsiderations> |
| <usageGuidance><p> |
| The work is best done in several sessions, perhaps performed over a few days (or weeks and months for very large |
| systems). The initial focus will be on the activities <a class="elementLink" |
| href="resources/identify_design_mechanisms,{C7A26BD7-3820-48D9-830F-684C3AF155F9}.html" |
| guid="{C7A26BD7-3820-48D9-830F-684C3AF155F9}">Identify Design Mechanisms</a> and <a class="elementLink" |
| href="resources/identify_design_elements_real-time_design,{586963D0-607D-4EC2-8D53-292DAFAB9C92}.html" |
| guid="{586963D0-607D-4EC2-8D53-292DAFAB9C92}">identify_design_elements_real-time_design</a>, with a great deal of |
| iteration with the <a class="elementLink" |
| href="resources/incorporate_design_elements,{5C647173-4E32-4594-96A9-2548B47722FA}.html" |
| guid="{5C647173-4E32-4594-96A9-2548B47722FA}">Incorporate Existing Design Elements</a> activity to make sure that new |
| elements do not duplicate functionality of existing elements. |
| </p> |
| <p> |
| As the design emerges, concurrency and distribution issues are introduced in the activities <a class="elementLink" |
| href="resources/describe_runtime_architecture,{4D35C038-A2D0-48B8-9ECD-52717FEAE33A}.html" |
| guid="{4D35C038-A2D0-48B8-9ECD-52717FEAE33A}">Describe the Run-time Architecture</a> and <a class="elementLink" |
| href="resources/describe_distribution,{6A112808-0A90-427A-BAB9-E14F3FBF72B5}.html" |
| guid="{6A112808-0A90-427A-BAB9-E14F3FBF72B5}">Describe Distribution</a>, respectively. As these issues are considered, |
| changes to design elements may be required to split behavior across processes, threads or nodes. |
| </p> |
| <p> |
| As the individual models are refined to incorporate the architectural decisions, the results are documented in |
| respective view sections in the Software Architecture Document (e.g., as the Design Model is refined, the Logical View |
| of the Software Architecture Document is refined, as well). The resulting architecture is reviewed. |
| </p> |
| <br /> |
| <br /></usageGuidance> |
| <purpose><p> |
| Purpose of this activity is to have tasks that are associated to other tasks. |
| </p> |
| <p> |
| &nbsp;<img height="71" alt="" src="resources/rup.jpg" width="176" /> |
| </p></purpose> |
| <alternatives><p> |
| Alterantives: |
| </p> |
| <ol> |
| <li> |
| Alter1 |
| </li> |
| <li> |
| Alter2 |
| </li> |
| <li> |
| Alter3 |
| </li> |
| </ol></alternatives> |
| <howtoStaff><p> |
| These activities are best carried out by a small team staffed by cross-functional team members. Issues that are |
| typically architecturally significant include usability, performance, scaling, process and thread synchronization, and |
| distribution. The team should also include members with domain experience who can identify key abstractions. The team |
| should also have experience with model organization and layering. The team will need to be able to pull all these |
| disparate threads into a cohesive, coherent (albeit preliminary) architecture. |
| </p> |
| <p> |
| Because the focus of the architecture effort is shifting toward implementation issues, greater attention needs to be |
| paid to specific technology issues. This will force the architecture team to shift members or expand to include people |
| with distribution and deployment expertise (if those issues are architecturally significant). In order to understand |
| the potential impact of the structure on the implementation model on the ease of integration, expertise in the software |
| build management process is useful to have. |
| </p> |
| <p> |
| At the same time, it is essential that the architecture team not be composed of a large extended team. A strategy for |
| countering this trend is to retain a relatively small core team with a satellite group of extended team members that |
| are brought in as "consultants" on key issues<b>.</b> This structure also works well for smaller projects where |
| specific expertise may be borrowed or contracted from other organizations; they can be brought in as specific issues |
| need to be addressed. |
| </p></howtoStaff> |
| </org.eclipse.epf.uma:ActivityDescription> |
| <org.eclipse.epf.uma:ActivityDescription xmi:id="-VRUCShAvXrsLgs7PZzHgUw" name="Iteration1,_EFVrwTziEdq5ysFONr1BGQ" guid="-VRUCShAvXrsLgs7PZzHgUw"> |
| <mainDescription><p> |
| This workflow detail has the following goals: |
| </p> |
| <ul> |
| <li> |
| Create an initial sketch of the architecture of the system |
| <ul> |
| <li> |
| Define an initial set of architecturally significant elements to use as the basis for analysis |
| </li> |
| <li> |
| Define an initial set of analysis mechanisms |
| </li> |
| <li> |
| Define the initial layering and organization of the system |
| </li> |
| <li> |
| Define the use-case realizations to be addressed in the current iteration |
| </li> |
| </ul> |
| </li> |
| <li> |
| Identify analysis classes from the architecturally significant use cases |
| </li> |
| <li> |
| Update the use-case realizations with analysis class interactions |
| </li> |
| </ul></mainDescription> |
| <keyConsiderations><p> |
| Key considerations: |
| </p> |
| <ul> |
| <li> |
| key11 |
| </li> |
| <li> |
| key22 |
| </li> |
| <li> |
| key33 |
| </li> |
| </ul></keyConsiderations> |
| <usageGuidance><p> |
| The work is best done in several sessions, perhaps performed over a few days (or weeks and months for very large |
| systems), with iteration between <a class="elementLink" |
| href="resources/architectural_analysis,{8CB48402-D4C5-4E17-BB33-507315CB1BBF}.html" |
| guid="{8CB48402-D4C5-4E17-BB33-507315CB1BBF}">Architectural Analysis</a> and <a class="elementLink" |
| href="resources/use_case_analysis,{28014615-A62F-452D-B821-30C7CAB0EC44}.html" |
| guid="{28014615-A62F-452D-B821-30C7CAB0EC44}">Use-Case Analysis</a>. Perform an initial pass at the architecture in <a |
| class="elementLink" href="resources/architectural_analysis,{8CB48402-D4C5-4E17-BB33-507315CB1BBF}.html" |
| guid="{8CB48402-D4C5-4E17-BB33-507315CB1BBF}">Architectural Analysis</a>, then choose architecturally significant use |
| cases, performing <a class="elementLink" href="resources/use_case_analysis,{28014615-A62F-452D-B821-30C7CAB0EC44}.html" |
| guid="{28014615-A62F-452D-B821-30C7CAB0EC44}">Use-Case Analysis</a> on each one. After (or as) each use case is |
| analyzed, update the architecture as needed to reflect adaptations required to accommodate new behavior of the system |
| and to address potential architectural problems which are identified. |
| </p> |
| <p> |
| Where the architecture already exists (either from a prior project or iteration), change requests may need to be |
| created to change the architecture to account for the new behavior the system must support. These changes may be to any |
| artifact in the process, depending on the scope of the change. |
| </p> |
| <br /> |
| <br /></usageGuidance> |
| <purpose><p> |
| Purpose: This itertaion is created for two activities. |
| </p> |
| <p> |
| &nbsp;<img height="474" alt="" src="resources/rup_platform.jpg" width="504" /> |
| </p></purpose> |
| <alternatives><p> |
| Alternatives: |
| </p> |
| <ol> |
| <li> |
| <a href="../roles/role_A1.xmi" target="_blank">role_A1.xmi</a> |
| </li> |
| <li> |
| <a href="../tasks/task_A2.xmi" target="_blank">task_A2.xmi</a> |
| </li> |
| </ol></alternatives> |
| <howtoStaff><p> |
| These activities are best carried out by a small team staffed by cross-functional team members. Issues that are |
| typically architecturally significant include performance, scaling, process and thread synchronization, and |
| distribution. The team should also include members with domain experience who can identify key abstractions. The team |
| should also have experience with model organization and layering. The team will need to be able to pull all these |
| disparate threads into a cohesive, coherent (albeit preliminary) architecture. |
| </p></howtoStaff> |
| </org.eclipse.epf.uma:ActivityDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-nUH0voD7RoKQgPT0rbOwQQ" name="task_B2,_McYH0DzlEdq5ysFONr1BGQ" guid="-nUH0voD7RoKQgPT0rbOwQQ"> |
| <keyConsiderations><p> |
| key considerations: |
| </p> |
| <ol> |
| <li> |
| k1 |
| </li> |
| <li> |
| k2 |
| </li> |
| <li> |
| k3 |
| </li> |
| </ol></keyConsiderations> |
| <usageGuidance><p> |
| usage guidance for task_B2 |
| </p> |
| <table cellspacing="2" cellpadding="2" width="180" border="1"> |
| <tbody> |
| <tr> |
| <td> |
| </td> |
| </tr> |
| </tbody> |
| </table> |
| <table cellspacing="2" cellpadding="2" width="180" border="1"> |
| <tbody> |
| <tr> |
| <th scope="col"> |
| r1 |
| </th> |
| <th scope="col"> |
| c2 |
| </th> |
| <th scope="col"> |
| c3 |
| </th> |
| <th scope="col"> |
| c4 |
| </th> |
| </tr> |
| <tr> |
| <th scope="row"> |
| r2 |
| </th> |
| <td> |
| asd |
| </td> |
| <td> |
| dsf |
| </td> |
| <td> |
| dsf |
| </td> |
| </tr> |
| <tr> |
| <th scope="row"> |
| r3 |
| </th> |
| <td> |
| <img height="28" alt="" src="resources/buttons.jpg" width="337" /> |
| </td> |
| <td> |
| dsf |
| </td> |
| <td> |
| </td> |
| </tr> |
| <tr> |
| <th scope="row"> |
| r4 |
| </th> |
| <td> |
| </td> |
| <td> |
| </td> |
| <td> |
| sdf |
| </td> |
| </tr> |
| <tr> |
| <th scope="row"> |
| r5 |
| </th> |
| <td> |
| daf |
| </td> |
| <td> |
| sdf |
| </td> |
| <td> |
| <img height="12" alt="" src="resources/bullet1.gif" width="12" /> |
| </td> |
| </tr> |
| </tbody> |
| </table> |
| <br /> |
| <br /> |
| <br /> |
| <br /></usageGuidance> |
| <refinedDescription><p> |
| <a href="resources/papers.htm" target="_blank">papers.htm</a> |
| </p> |
| <p> |
| refined description: |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-aDE4yFzE_m_n2PIzcOt4rA" name="task_A2,_JCrBEDzlEdq5ysFONr1BGQ" guid="-aDE4yFzE_m_n2PIzcOt4rA"> |
| <keyConsiderations><p> |
| keys: |
| </p> |
| <ol> |
| <li> |
| kk1 |
| </li> |
| <li> |
| kk2 |
| </li> |
| <li> |
| kk3 |
| </li> |
| </ol></keyConsiderations> |
| <usageGuidance><p> |
| usage guidance for task_B2 |
| </p> |
| <table cellspacing="2" cellpadding="2" width="180" border="1"> |
| <tbody> |
| <tr> |
| <th scope="col"> |
| r1 |
| </th> |
| <th scope="col"> |
| c2 |
| </th> |
| <th scope="col"> |
| c3 |
| </th> |
| <th scope="col"> |
| c4 |
| </th> |
| </tr> |
| <tr> |
| <th scope="row"> |
| r2 |
| </th> |
| <td> |
| asd |
| </td> |
| <td> |
| dsf |
| </td> |
| <td> |
| dsf |
| </td> |
| </tr> |
| <tr> |
| <th scope="row"> |
| r3 |
| </th> |
| <td> |
| <img height="28" alt="" src="resources/buttons.jpg" width="337" /> |
| </td> |
| <td> |
| dsf |
| </td> |
| <td> |
| </td> |
| </tr> |
| <tr> |
| <th scope="row"> |
| r4 |
| </th> |
| <td> |
| </td> |
| <td> |
| </td> |
| <td> |
| sdf |
| </td> |
| </tr> |
| <tr> |
| <th scope="row"> |
| r5 |
| </th> |
| <td> |
| daf |
| </td> |
| <td> |
| sdf |
| </td> |
| <td> |
| <img height="12" alt="" src="resources/bullet1.gif" width="12" /> |
| </td> |
| </tr> |
| </tbody> |
| </table> |
| <br /> |
| <br /> |
| <br /> |
| <br /></usageGuidance> |
| <refinedDescription>Task A2's refined description</refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-5t8GtoL4IBoxfazBI_0crA" name="wpDesc1,_SUGQgDziEdq5ysFONr1BGQ" guid="-5t8GtoL4IBoxfazBI_0crA"> |
| <keyConsiderations>key:wpDesc1</keyConsiderations> |
| <usageGuidance>usage:wpDesc1</usageGuidance> |
| <refinedDescription><p> |
| refined: wpDesc1 |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-ifmQNB5y1RZKF1Hrm3CdRA" name="task associated to taskA1,_FrtMoDziEdq5ysFONr1BGQ" guid="-ifmQNB5y1RZKF1Hrm3CdRA"> |
| <keyConsiderations><p> |
| keys: |
| </p> |
| <p> |
| key1,key2 |
| </p></keyConsiderations> |
| <usageGuidance><p> |
| usage: |
| </p> |
| <p> |
| The work is best done in several sessions, perhaps performed over a few days (or weeks and months for very large |
| systems). The initial focus will be on the activities <a class="elementLink" |
| href="resources/identify_design_mechanisms,{C7A26BD7-3820-48D9-830F-684C3AF155F9}.html" |
| guid="{C7A26BD7-3820-48D9-830F-684C3AF155F9}">Identify Design Mechanisms</a> and <a class="elementLink" |
| href="resources/identify_design_elements_real-time_design,{586963D0-607D-4EC2-8D53-292DAFAB9C92}.html" |
| guid="{586963D0-607D-4EC2-8D53-292DAFAB9C92}">identify_design_elements_real-time_design</a>, with a great deal of |
| iteration with the <a class="elementLink" |
| href="resources/incorporate_design_elements,{5C647173-4E32-4594-96A9-2548B47722FA}.html" |
| guid="{5C647173-4E32-4594-96A9-2548B47722FA}">Incorporate Existing Design Elements</a> activity to make sure that new |
| elements do not duplicate functionality of existing elements. |
| </p> |
| <p> |
| As the design emerges, concurrency and distribution issues are introduced in the activities <a class="elementLink" |
| href="resources/describe_runtime_architecture,{4D35C038-A2D0-48B8-9ECD-52717FEAE33A}.html" |
| guid="{4D35C038-A2D0-48B8-9ECD-52717FEAE33A}">Describe the Run-time Architecture</a> and <a class="elementLink" |
| href="resources/describe_distribution,{6A112808-0A90-427A-BAB9-E14F3FBF72B5}.html" |
| guid="{6A112808-0A90-427A-BAB9-E14F3FBF72B5}">Describe Distribution</a>, respectively. As these issues are considered, |
| changes to design elements may be required to split behavior across processes, threads or nodes. |
| </p> |
| <p> |
| As the individual models are refined to incorporate the architectural decisions, the results are documented in |
| respective view sections in the Software Architecture Document (e.g., as the Design Model is refined, the Logical View |
| of the Software Architecture Document is refined, as well). The resulting architecture is reviewed. |
| </p> |
| <p> |
| <br /> |
| <br /> |
| &nbsp; |
| </p></usageGuidance> |
| <refinedDescription><p> |
| refined description |
| </p> |
| <p> |
| <img height="16" alt="" src="resources/helpbook.gif" width="16" /> |
| </p> |
| <p> |
| <a href="resources/papers.htm" target="_blank">papers.htm</a> |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-pO8LeceGXjKeapuLoFfkxA" name="roleDesc1,_P1sUYDziEdq5ysFONr1BGQ" guid="-pO8LeceGXjKeapuLoFfkxA"> |
| <keyConsiderations><p> |
| key considerations: |
| </p> |
| <p> |
| key1 |
| </p> |
| <p> |
| key2 |
| </p></keyConsiderations> |
| <usageGuidance><p> |
| <img height="474" alt="" src="resources/rup_platform.jpg" width="504" />usage for roleA1&nbsp; |
| </p></usageGuidance> |
| <refinedDescription>refined description for roleDesc1</refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-_Th-jv5jm0h0f0mFhKtqgQ" name="roleDesc2,_Q99kADziEdq5ysFONr1BGQ" guid="-_Th-jv5jm0h0f0mFhKtqgQ"> |
| <keyConsiderations>key consideration for roleA2</keyConsiderations> |
| <usageGuidance><p> |
| <img height="12" alt="" src="resources/bullet1.gif" width="12" /> |
| </p> |
| <p> |
| usage guidance for roleA2 |
| </p></usageGuidance> |
| <refinedDescription><p> |
| refined description for roleA2 |
| </p> |
| <p> |
| </p> |
| <p> |
| refined description for roleA2 |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-Bkv6VTdMpg4bD0YkfHZ4dg" name="task associated to taskA2,_LwLQgDziEdq5ysFONr1BGQ" guid="-Bkv6VTdMpg4bD0YkfHZ4dg"> |
| <keyConsiderations>keys: task associated to taskA2</keyConsiderations> |
| <usageGuidance>usage:task associated to taskA2</usageGuidance> |
| <refinedDescription><p> |
| refined:task associated to taskA2 |
| </p> |
| <table cellspacing="2" cellpadding="2" width="180" border="1"> |
| <tbody> |
| <tr> |
| <th scope="col"> |
| 1 |
| </th> |
| <th scope="col"> |
| z |
| </th> |
| <th scope="col"> |
| z |
| </th> |
| <th scope="col"> |
| z |
| </th> |
| <th scope="col"> |
| z |
| </th> |
| <th scope="col"> |
| z |
| </th> |
| </tr> |
| <tr> |
| <td> |
| z |
| </td> |
| <td> |
| 2 |
| </td> |
| <td> |
| </td> |
| <td> |
| </td> |
| <td> |
| </td> |
| <td> |
| </td> |
| </tr> |
| <tr> |
| <td> |
| z |
| </td> |
| <td> |
| </td> |
| <td> |
| 3 |
| </td> |
| <td> |
| </td> |
| <td> |
| </td> |
| <td> |
| </td> |
| </tr> |
| <tr> |
| <td> |
| z |
| </td> |
| <td> |
| </td> |
| <td> |
| </td> |
| <td> |
| 4 |
| </td> |
| <td> |
| </td> |
| <td> |
| </td> |
| </tr> |
| <tr> |
| <td> |
| z |
| </td> |
| <td> |
| </td> |
| <td> |
| </td> |
| <td> |
| </td> |
| <td> |
| 5 |
| </td> |
| <td> |
| </td> |
| </tr> |
| </tbody> |
| </table></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-TRxhxAs1xOKNRrFCEPpAlw" name="task with no links,_5jJYADzkEdq5ysFONr1BGQ" guid="-TRxhxAs1xOKNRrFCEPpAlw"> |
| <keyConsiderations>key:task with no links</keyConsiderations> |
| <usageGuidance>usage:task with no links</usageGuidance> |
| <refinedDescription><p> |
| refined:task with no links |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:ActivityDescription xmi:id="-AdwAjn5vRCnEQQLUaYJ1dw" name="Activity2,_BS6gETzlEdq5ysFONr1BGQ" guid="-AdwAjn5vRCnEQQLUaYJ1dw"> |
| <mainDescription><p> |
| This Workflow Detail: |
| </p> |
| <ul> |
| <li> |
| Provides the natural <b>transition from analysis</b> activities <b>to design</b> activities, identifying: |
| <ul> |
| <li> |
| appropriate design elements from analysis elements |
| </li> |
| <li> |
| appropriate design mechanisms from related analysis mechanisms |
| </li> |
| </ul> |
| </li> |
| <li> |
| <b>Describes</b> the organization of the system's <b>run-time and deployment architecture</b> |
| </li> |
| <li> |
| <b>Organizes the implementation model</b> so as to make the transition between design and implementation seamless |
| </li> |
| <li> |
| <b>Maintains the consistency and integrity of the architecture</b>, ensuring that: |
| <ul> |
| <li> |
| new design elements identified for the current iteration are integrated with pre-existing design elements. |
| </li> |
| <li> |
| maximal re-use of available components and design elements is achieved as early as possible in the design |
| effort. |
| </li> |
| </ul> |
| </li> |
| </ul></mainDescription> |
| <keyConsiderations><p> |
| Key considerations: |
| </p> |
| <ul> |
| <li> |
| key1 |
| </li> |
| <li> |
| key2 |
| </li> |
| <li> |
| key3 |
| </li> |
| <li> |
| key4 |
| </li> |
| <li> |
| key5 |
| </li> |
| <li> |
| key6 |
| </li> |
| <li> |
| key7 |
| </li> |
| </ul></keyConsiderations> |
| <usageGuidance><p> |
| The work is best done in several sessions, perhaps performed over a few days (or weeks and months for very large |
| systems). The initial focus will be on the activities <a class="elementLink" |
| href="resources/identify_design_mechanisms,{C7A26BD7-3820-48D9-830F-684C3AF155F9}.html" |
| guid="{C7A26BD7-3820-48D9-830F-684C3AF155F9}">Identify Design Mechanisms</a> and <a class="elementLink" |
| href="resources/identify_design_elements_real-time_design,{586963D0-607D-4EC2-8D53-292DAFAB9C92}.html" |
| guid="{586963D0-607D-4EC2-8D53-292DAFAB9C92}">identify_design_elements_real-time_design</a>, with a great deal of |
| iteration with the <a class="elementLink" |
| href="resources/incorporate_design_elements,{5C647173-4E32-4594-96A9-2548B47722FA}.html" |
| guid="{5C647173-4E32-4594-96A9-2548B47722FA}">Incorporate Existing Design Elements</a> activity to make sure that new |
| elements do not duplicate functionality of existing elements. |
| </p> |
| <p> |
| As the design emerges, concurrency and distribution issues are introduced in the activities <a class="elementLink" |
| href="resources/describe_runtime_architecture,{4D35C038-A2D0-48B8-9ECD-52717FEAE33A}.html" |
| guid="{4D35C038-A2D0-48B8-9ECD-52717FEAE33A}">Describe the Run-time Architecture</a> and <a class="elementLink" |
| href="resources/describe_distribution,{6A112808-0A90-427A-BAB9-E14F3FBF72B5}.html" |
| guid="{6A112808-0A90-427A-BAB9-E14F3FBF72B5}">Describe Distribution</a>, respectively. As these issues are considered, |
| changes to design elements may be required to split behavior across processes, threads or nodes. |
| </p> |
| <p> |
| As the individual models are refined to incorporate the architectural decisions, the results are documented in |
| respective view sections in the Software Architecture Document (e.g., as the Design Model is refined, the Logical View |
| of the Software Architecture Document is refined, as well). The resulting architecture is reviewed. |
| </p> |
| <br /> |
| <br /></usageGuidance> |
| <purpose><p> |
| Purpose of this activity is to have tasks that are associated to other tasks. |
| </p> |
| <p> |
| &nbsp;<img height="71" alt="" src="resources/rup.jpg" width="176" /> |
| </p></purpose> |
| <alternatives><p> |
| Alterantives: |
| </p> |
| <ol> |
| <li> |
| Alter1 |
| </li> |
| <li> |
| Alter2 |
| </li> |
| <li> |
| Alter3 |
| </li> |
| </ol></alternatives> |
| <howtoStaff><p> |
| These activities are best carried out by a small team staffed by cross-functional team members. Issues that are |
| typically architecturally significant include usability, performance, scaling, process and thread synchronization, and |
| distribution. The team should also include members with domain experience who can identify key abstractions. The team |
| should also have experience with model organization and layering. The team will need to be able to pull all these |
| disparate threads into a cohesive, coherent (albeit preliminary) architecture. |
| </p> |
| <p> |
| Because the focus of the architecture effort is shifting toward implementation issues, greater attention needs to be |
| paid to specific technology issues. This will force the architecture team to shift members or expand to include people |
| with distribution and deployment expertise (if those issues are architecturally significant). In order to understand |
| the potential impact of the structure on the implementation model on the ease of integration, expertise in the software |
| build management process is useful to have. |
| </p> |
| <p> |
| At the same time, it is essential that the architecture team not be composed of a large extended team. A strategy for |
| countering this trend is to retain a relatively small core team with a satellite group of extended team members that |
| are brought in as "consultants" on key issues<b>.</b> This structure also works well for smaller projects where |
| specific expertise may be borrowed or contracted from other organizations; they can be brought in as specific issues |
| need to be addressed. |
| </p></howtoStaff> |
| </org.eclipse.epf.uma:ActivityDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-BY__tijwRrV41YUrXItU0w" name="role_A2,_JC98ADzlEdq5ysFONr1BGQ" guid="-BY__tijwRrV41YUrXItU0w"> |
| <keyConsiderations>keys consideration:Role A2</keyConsiderations> |
| <usageGuidance>usage:Role A2</usageGuidance> |
| <refinedDescription><p> |
| refined description : Role A2 |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-DOZrR_sZwwpcUtcou-jIyQ" name="role_A1,_JC98ATzlEdq5ysFONr1BGQ" guid="-DOZrR_sZwwpcUtcou-jIyQ"> |
| <keyConsiderations>Role A1:key consideration</keyConsiderations> |
| <usageGuidance>Role A1:usage</usageGuidance> |
| <refinedDescription>Role A1:Refined description</refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-arFrJisByP90YCrMb-iyjg" name="roleDesc with no links,_3_UNwDzkEdq5ysFONr1BGQ" guid="-arFrJisByP90YCrMb-iyjg"> |
| <keyConsiderations>key consideration:roleDesc with no links</keyConsiderations> |
| <usageGuidance>usage:roleDesc with no links</usageGuidance> |
| <refinedDescription>refined description : roleDesc with no links</refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-5OeGPH8JRzSRAFPzBgHnJA" name="role_B2,_Mc0zwDzlEdq5ysFONr1BGQ" guid="-5OeGPH8JRzSRAFPzBgHnJA"> |
| <keyConsiderations>key:Role B2</keyConsiderations> |
| <usageGuidance>usage:Role B2</usageGuidance> |
| <refinedDescription>refined:Role B2</refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-YerIjDrIlewd8iDhISMg1g" name="role_B1,_Mc0zwTzlEdq5ysFONr1BGQ" guid="-YerIjDrIlewd8iDhISMg1g"> |
| <keyConsiderations>key:Role B1</keyConsiderations> |
| <usageGuidance>usage:Role B1</usageGuidance> |
| <refinedDescription>refined: Role B1</refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-ncLhU4vhg6dhoEKTTkKkDQ" name="wpDesc2,_TCu4IDziEdq5ysFONr1BGQ" guid="-ncLhU4vhg6dhoEKTTkKkDQ"> |
| <keyConsiderations>key:wpdesc2</keyConsiderations> |
| <usageGuidance>usage:wpdesc2</usageGuidance> |
| <refinedDescription>refined: wpdesc2</refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-rDXoW6bWZ_7mkL_E9Wcyhg" name="wpDesc3 with no links,_1x57ADzkEdq5ysFONr1BGQ" guid="-rDXoW6bWZ_7mkL_E9Wcyhg"> |
| <keyConsiderations>key: wpDesc3 with no links</keyConsiderations> |
| <usageGuidance>usage: wpDesc3 with no links</usageGuidance> |
| <refinedDescription>refined: wpDesc3 with no links</refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-hmCCr-DKZ6zr8S6DXdqfSA" name="artifact_A2,_JC98AjzlEdq5ysFONr1BGQ" guid="-hmCCr-DKZ6zr8S6DXdqfSA"> |
| <keyConsiderations>key : Artifact A2</keyConsiderations> |
| <usageGuidance>usage: Artifact A2</usageGuidance> |
| <refinedDescription>refined: Artifact A2</refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-CDJo_oYCdDi5vp8I69v9Ow" name="deliverable_A2,_JC98AzzlEdq5ysFONr1BGQ" guid="-CDJo_oYCdDi5vp8I69v9Ow"> |
| <keyConsiderations>keys: Deliverable A2</keyConsiderations> |
| <usageGuidance>usage: Deliverable A2</usageGuidance> |
| <refinedDescription>refined:Deliverable A2</refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-QN9RGL5cn0SlbUwnGV2G_A" name="artifact_A2,_JDHtADzlEdq5ysFONr1BGQ" guid="-QN9RGL5cn0SlbUwnGV2G_A"> |
| <keyConsiderations>keys:Artifact A2</keyConsiderations> |
| <usageGuidance>usage:Artifact A2</usageGuidance> |
| <refinedDescription>refined:Artifact A2</refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-1jTDqS4Rv_PAEHYFpeojmA" name="outcome_A2,_JDHtATzlEdq5ysFONr1BGQ" guid="-1jTDqS4Rv_PAEHYFpeojmA"> |
| <keyConsiderations>key:Outcome A2</keyConsiderations> |
| <usageGuidance>usage:Outcome A2</usageGuidance> |
| <refinedDescription>refined:Outcome A2</refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-DakzmvA-qhwGESCfZK11sQ" name="artifact_B2,_MdRfsDzlEdq5ysFONr1BGQ" guid="-DakzmvA-qhwGESCfZK11sQ"> |
| <keyConsiderations>key:Artifact B2</keyConsiderations> |
| <usageGuidance>usage:Artifact B2</usageGuidance> |
| <refinedDescription>refined:Artifact B2</refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-LaDyAujxBkPThr28t2Xdwg" name="deliverable_B2,_MdRfsTzlEdq5ysFONr1BGQ" guid="-LaDyAujxBkPThr28t2Xdwg"> |
| <keyConsiderations>key:Deliverable B2</keyConsiderations> |
| <usageGuidance>usage:Deliverable B2</usageGuidance> |
| <refinedDescription>refined:Deliverable B2</refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-nTt6H3rXytUsOqpJLEQjdw" name="outcome_B2,_MdkaoTzlEdq5ysFONr1BGQ" guid="-nTt6H3rXytUsOqpJLEQjdw"> |
| <usageGuidance>&nbsp;&nbsp;&nbsp;</usageGuidance> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-zBAs11RgLg_YSbs7BdkSuQ" name="task_A1,_0DR_QEDEEdqO9M3fukYA_A" guid="-zBAs11RgLg_YSbs7BdkSuQ"> |
| <keyConsiderations>Task A1&nbsp; key</keyConsiderations> |
| <usageGuidance><p> |
| Task A1&nbsp; guidance |
| </p> |
| <p> |
| <img height="16" alt="" |
| src="file:///C:/Documents%20and%20Settings/Administrator/IBM/MethodLibraries/Paris/Paris/Plug%20A/capabilitypatterns/resources/synced.gif" |
| width="16" /> |
| </p> |
| <p> |
| <img height="16" alt="" |
| src="file:///C:/Documents%20and%20Settings/Administrator/IBM/MethodLibraries/Paris/Paris/Plug%20A/capabilitypatterns/resources/helpbook.gif" |
| width="16" /> |
| </p></usageGuidance> |
| <refinedDescription>Task A1&nbsp; refined description</refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-yb-LGikcA5MPeR8L3YW2CA" name="task_A2,_2887EEDEEdqO9M3fukYA_A" guid="-yb-LGikcA5MPeR8L3YW2CA"> |
| <keyConsiderations>Task A2 key</keyConsiderations> |
| <usageGuidance>Task A2 guidance</usageGuidance> |
| <refinedDescription>Task A2 refined description</refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-wBVwnKNA7vxPZpY5h0njBQ" name="role_A1,_0Dk6MEDEEdqO9M3fukYA_A" guid="-wBVwnKNA7vxPZpY5h0njBQ"> |
| <keyConsiderations>Role A1 key</keyConsiderations> |
| <usageGuidance>Role A1 guidance</usageGuidance> |
| <refinedDescription><p> |
| Role A1 refined desc |
| </p> |
| <p> |
| <img height="71" alt="" |
| src="file:///C:/Documents%20and%20Settings/Administrator/IBM/MethodLibraries/Paris/Paris/Plug%20A/capabilitypatterns/resources/rup.jpg" |
| width="176" /> |
| </p></refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| <org.eclipse.epf.uma:DescriptorDescription xmi:id="-_j3f8djwKxsKaCHDnJIqVA" name="role_A2,_0Dk6MUDEEdqO9M3fukYA_A" guid="-_j3f8djwKxsKaCHDnJIqVA"> |
| <keyConsiderations><p> |
| Role A2 key |
| </p> |
| <p> |
| <img height="167" alt="" |
| src="file:///C:/Documents%20and%20Settings/Administrator/IBM/MethodLibraries/Paris/Paris/Plug%20A/capabilitypatterns/resources/rup1_a.gif" |
| width="26" /> |
| </p></keyConsiderations> |
| <usageGuidance>Role A2 usage</usageGuidance> |
| <refinedDescription>Role A2 refined desc</refinedDescription> |
| </org.eclipse.epf.uma:DescriptorDescription> |
| </xmi:XMI> |
