Minor text corrections.
diff --git a/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/tasks/outline_the_arch.xmi b/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/tasks/outline_the_arch.xmi
index ba9cd04..d5f5a79 100644
--- a/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/tasks/outline_the_arch.xmi
+++ b/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/tasks/outline_the_arch.xmi
@@ -4,7 +4,7 @@
xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf"
epf:version="1.5.0" xmi:id="_qDRSULBKEdm7Eph_l9Cn9w"
name="outline_the_arch,_0f-1oMlgEdmt3adZL5Dmdw" guid="_qDRSULBKEdm7Eph_l9Cn9w"
- changeDate="2008-07-23T17:19:55.475-0700" version="1.0.0">
+ changeDate="2008-08-08T11:26:46.696-0700" version="1.0.0">
<mainDescription><p>
This task focuses on outlining the initial architectural decisions that will guide development and testing. It relies
on gathering experience gained in similar systems or problem domains to constrain and focus the architecture so that
@@ -29,8 +29,8 @@
the customer. This allows the project to move forward, enabling you to refine and baseline the architecture.
</p></mainDescription>
<keyConsiderations><p>
- When envisioning the architecture, it is important to reduce the complexity of the&nbsp;solution by raising the levels
- of abstraction.&nbsp; For more information, see <a class="elementLinkWithType"
+ It&nbsp;is important to reduce the complexity of the&nbsp;solution by raising the levels of abstraction.&nbsp; For more
+ information, see <a class="elementLinkWithType"
href="./../../core.tech.common.base/guidances/guidelines/abstract_away_complexity_DBF13AE6.html"
guid="_we3F4ACpEdu8m4dIntu6jA">Guideline: Abstract Away Complexity</a>.
</p>
@@ -48,8 +48,8 @@
guide the approach to important technical decisions.<br />
</p>
<p>
- It will be important to regularly review the status of these goals throughout the project to make sure that they are
- still valid and that the system is on track to deliver them.<br />
+ It's important to regularly review the status of these goals throughout the project to make sure that they are still
+ valid and that the system is on track to deliver them.
</p>
<p>
For more information, see <a class="elementLinkWithType"
@@ -103,7 +103,7 @@
<sectionDescription><p>
Survey, assess, and select available assets.&nbsp; Identify assets from other areas that may be reused in the current
architecture. For more information, see <a class="elementLinkWithType"
- href="./../../practice.tech.evolutionary_design.base/guidances/guidelines/software_reuse_B6B04C26.html"
+ href="./../../core.tech.common.base/guidances/guidelines/software_reuse_B6B04C26.html"
guid="_vO2uoO0OEduUpsu85bVhiQ">Guideline: Software Reuse</a>.
</p></sectionDescription>
</sections>
@@ -184,13 +184,15 @@
</sections>
<sections xmi:id="_Q2PRIFHSEd2zrOgIte8oWg" name="Verify architectural consistency"
guid="_Q2PRIFHSEd2zrOgIte8oWg">
- <sectionDescription>Work with the team&nbsp;to verify that the architecture is consistent with the requirements; and that the descriptions of
+ <sectionDescription>Work with the team&nbsp;to verify that the architecture is consistent with the requirements and that the descriptions of
the architecture are complete, meaningful, and clear.</sectionDescription>
</sections>
<sections xmi:id="_Xia1QFHSEd2zrOgIte8oWg" name="Capture and communicate architectural decisions "
guid="_Xia1QFHSEd2zrOgIte8oWg">
- <sectionDescription>Capture important decisions about the architecture for future reference. Make sure that&nbsp;the team understand the
-architecture&nbsp;and can deliver it.</sectionDescription>
+ <sectionDescription>Capture important decisions about the architecture in the <a class="elementLink"
+href="./../../practice.tech.evolutionary_arch.base/workproducts/architecture_notebook_9BB92433.html"
+guid="_0XAf0MlgEdmt3adZL5Dmdw">Architecture Notebook</a>&nbsp;for future reference. Make sure that&nbsp;the team
+understands the architecture&nbsp;and can deliver it.</sectionDescription>
</sections>
<purpose><p>
To outline a technical approach to the system that supports the project requirements, within the constraints placed on
diff --git a/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/tasks/refine_the_arch.xmi b/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/tasks/refine_the_arch.xmi
index 24a773d..5fd717b 100644
--- a/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/tasks/refine_the_arch.xmi
+++ b/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/tasks/refine_the_arch.xmi
@@ -1,9 +1,10 @@
<?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.5/uma.ecore"
- xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="_rUis8LBKEdm7Eph_l9Cn9w"
+ xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf"
+ epf:version="1.5.0" xmi:id="_rUis8LBKEdm7Eph_l9Cn9w"
name="refine_the_arch,_0gRJgMlgEdmt3adZL5Dmdw" guid="_rUis8LBKEdm7Eph_l9Cn9w"
- changeDate="2008-02-15T18:49:15.750+0000" version="1.0.0">
+ changeDate="2008-08-08T11:29:21.559-0700" version="1.0.0">
<mainDescription><p>
This task&nbsp;builds upon the outlined architecture and makes concrete and unambiguous architectural decisions to
support development.&nbsp; It takes into&nbsp;account any design and implementation work products that have been
@@ -18,16 +19,16 @@
The results are captured for future reference and are communicated across the team.
</p></mainDescription>
<keyConsiderations><p>
- When evolving the architecture, it is important to continue to reduce the complexity of the&nbsp;solution by raising
- the levels of abstraction.&nbsp; For more information, see <a class="elementLinkWithType"
+ It is important to continue to reduce the complexity of the&nbsp;solution by raising the levels of abstraction.&nbsp;
+ For more information, see <a class="elementLinkWithType"
href="./../../core.tech.common.base/guidances/guidelines/abstract_away_complexity_DBF13AE6.html"
guid="_we3F4ACpEdu8m4dIntu6jA">Guideline: Abstract Away Complexity</a>.
</p>
<p>
- You should also continue the collaboration with the whole&nbsp;team on the refining of the architecture in order to
- promote consensus and a common understanding of the overall solution. You should be working to coordinate and guide the
- technical activities of the team, rather than seeking to do all the work alone.&nbsp;Place special emphasis&nbsp;on
- involving&nbsp;the developer(s) throughout this task since its the developed solution that will prove out the
+ Continue the collaboration with the whole&nbsp;team on the refining of the architecture in order to promote consensus
+ and a common understanding of the overall solution. The architect should be working to coordinate and guide the
+ technical activities of the team rather than doing all the work alone.&nbsp;Place special emphasis&nbsp;on
+ involving&nbsp;the developer(s) throughout this task since it's the developed solution that will prove out the
architecture and may result in refinements to the architecture documentation.
</p>
<p>
@@ -63,9 +64,13 @@
class="elementLink" href="./../../core.tech.common.base/guidances/concepts/arch_goals_CB41D8AE.html"
guid="_HlRqANpbEdyP58ppo1Ieaw">Architectural Goals</a>&nbsp;and <a class="elementLink"
href="./../../core.tech.common.base/guidances/concepts/arch_significant_requirements_1EE5D757.html"
- guid="_HrZGIA4MEduibvKwrGxWxA">Architecturally Significant Requirements</a>&nbsp;and refine, as needed. It may be that
- some new architecturally-significant requirements have been introduced or your architectural goals and priorities may
- have changed.
+ guid="_HrZGIA4MEduibvKwrGxWxA">Architecturally Significant Requirements</a>&nbsp;and refine them as needed. It may be
+ that some new architecturally-significant requirements have been introduced or your architectural goals and priorities
+ may have changed.
+</p>
+<p>
+ The development work performed so far will also inform the decisions and goals you've identified. Use information from
+ designing and implementing the system so far to adjust and refined those decisions and goals.
</p></sectionDescription>
</sections>
<sections xmi:id="_G_k1kBaqEduSTJywppIxVQ" name="Identify architecturally significant design elements"
@@ -112,7 +117,7 @@
<li>
Components that implement the <a class="elementLink"
href="./../../core.tech.common.base/guidances/concepts/arch_mechanism_2932DFB6.html"
- guid="_mzxI0A4LEduibvKwrGxWxA">Architectural Mechanism</a>s
+ guid="_mzxI0A4LEduibvKwrGxWxA">Architectural Mechanisms</a>s
</li>
<li>
Architectural and key design <a class="elementLink"
@@ -161,7 +166,7 @@
<sectionDescription><p>
Refine&nbsp;the applicable <a class="elementLink"
href="./../../core.tech.common.base/guidances/concepts/arch_mechanism_2932DFB6.html"
- guid="_mzxI0A4LEduibvKwrGxWxA">Architectural Mechanism</a>s, as needed to support the design.&nbsp; For example,
+ guid="_mzxI0A4LEduibvKwrGxWxA">Architectural Mechanisms</a>s, as needed to support the design.&nbsp; For example,
refining an analysis mechanism into a design mechanism and/or refining a design mechanism into an implementation
mecahanism.&nbsp;<br />
</p></sectionDescription>
