https://bugs.eclipse.org/bugs/show_bug.cgi?id=224225
diff --git a/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/guidances/practices/evolutionary_arch.xmi b/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/guidances/practices/evolutionary_arch.xmi
index 9966b92..a005929 100644
--- a/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/guidances/practices/evolutionary_arch.xmi
+++ b/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/guidances/practices/evolutionary_arch.xmi
@@ -1,8 +1,9 @@
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:PracticeDescription 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="-TleqHW_wvIYc0qLQgZUchA"
- name="new_practice,_uVnpQB4qEd2bS8fFOQ7WWA" guid="-TleqHW_wvIYc0qLQgZUchA" changeDate="2008-08-04T13:49:37.468-0700"
+ 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="-TleqHW_wvIYc0qLQgZUchA"
+ name="new_practice,_uVnpQB4qEd2bS8fFOQ7WWA" guid="-TleqHW_wvIYc0qLQgZUchA" changeDate="2008-08-07T12:34:06.418-0700"
version="7.5.0">
<additionalInfo><h3>
Additional Resources
@@ -23,47 +24,56 @@
<a href="http://www.agiledata.org/essays/enterpriseArchitecture.html" target="_blank">Agile Enterprise
Architecture</a>
</li>
- <li>
- [*** Add more, as needed ***]<br />
- </li>
-</ul></additionalInfo>
- <problem><h3>
+</ul><br /></additionalInfo>
+ <problem><p>
+ <span class="c1">This practice improves quality and productivity by reducing the need to make time consuming error
+ prone fixes to late detected problems that result from architectural flaws.</span>&nbsp; This is possible because you
+ validate the architecture early and correct any key architectural problems before the majority of development is
+ done.<span class="c1">&nbsp;</span>
+</p>
+<p>
+ <span class="c1">This practice reduces time to market by focusing on reuse.</span>&nbsp; It improves the consistency
+ and maintainability of the system by incorporating lessons learned from development back into the architecture and
+ applying those lessons to the rest of development.<span class="c1">&nbsp;</span>
+</p>
+<p class="MsoNormal c2">
+ <span class="c1">This practice improves predictability by identifying and implementing the highest risk technical areas
+ first.</span>&nbsp; It improves your team’s responsiveness to change by shortening the architecture cycle and
+ minimizing time wasted in architecture scrap and rework when changes arise.
+</p>
+<h3>
The Essence of Evolutionary Architecture
</h3>
<p>
- The following capture the key principles of the Evolutionary Architecture practice:
+ In the Evolutionary Architecture practice, you analyze the major technical concerns that affect the solution and
+ document architectural decisions to ensure that you have assessed and communicated those decisions.
</p>
-<ul>
- <li>
- <strong>Architecture work is prioritized with all other work (architect "just in time" and evolve the architecture
- over time).</strong> Architectural issues are explicitly identified, discussed by the team, and prioritized with
- any other work within the context of iteration planning. Prioritization is based on need for technical risk
- mitigation versus value creation.&nbsp; Assigning architectural issues to an iteration drives 'just-in-time'
- architecture work and the architecture <em>evolves over time</em>.
- </li>
- <li>
- <strong>Document key architectural decisions and outstanding issues</strong>.&nbsp; The <a class="elementLink"
- href="./../../../practice.tech.evolutionary_arch.base/workproducts/architecture_notebook_9BB92433.html"
- guid="_0XAf0MlgEdmt3adZL5Dmdw">Architecture Notebook</a>&nbsp;provides a place to maintain a list of the
- architectural issues, along with any supporting materials documented at the appropriate level to make it easy to
- understand what architectural decisions have been made, and are still left to be made.
- </li>
- <li>
- <strong>Implement and test key capabilities as a means to address architectural issues</strong>.&nbsp; Resolving an
- architectural issues typically requires not only architectural brainstorming, but also associated
- prototyping.&nbsp; In other words, implement enough code (hopefully code that becomes production code, minus what
- had to be thrown away because proven invalid) to validate the assumptions behind the architecture.
- </li>
-</ul>
<h3>
- <br />
- Why Adopt this Practice?
+ The key principles of the Evolutionary Architecture practice are:
</h3>
-<p>
- [*** Include some content here that describes the business value of this practice -- what do you get when you adopt
- it?&nbsp; This section is essentially the value proposition for the practice.&nbsp; You may want to describe some
- common problems and how this practice solves those problems.&nbsp; &nbsp;***]&nbsp;&nbsp;&nbsp;
-</p></problem>
+<ul type="disc">
+ <li class="MsoNormal c3">
+ <strong><span class="c1">Perform architecture work "just in time" with all other work.</span></strong><span
+ class="c1">&nbsp;&nbsp; When planning your project, identify and discuss architectural issues with your team, then
+ prioritize architecture work with any other work.</span> &nbsp;Base your priorities on mitigating technical risk
+ rather than creating value.&nbsp; Deferring architectural issues to handle “just in time” causes the architecture
+ to <em><span class="c2">evolve over time</span></em>.
+ </li>
+ <li class="MsoNormal c3">
+ <strong><span class="c1">Document key architectural decisions and outstanding issues</span></strong><span
+ class="c1">.&nbsp; The <a class="elementLink"
+ href="./../../../practice.tech.evolutionary_arch.base/workproducts/architecture_notebook_9BB92433.html"
+ guid="_0XAf0MlgEdmt3adZL5Dmdw">Architecture Notebook</a>&nbsp;maintains a list of the architectural issues to make
+ it easy to understand which architectural decisions you’ve made and which you’ve not yet addressed.</span>
+ </li>
+ <li class="MsoNormal c3">
+ <strong><span class="c1">Implement and test key capabilities as a means to address architectural
+ issues</span></strong><span class="c1">.&nbsp; Resolving architectural issues typically requires not only
+ architectural brainstorming, but also associated prototyping.&nbsp; In other words, implement enough code to
+ validate the assumptions behind the architecture.&nbsp;The code becomes production code, except for anything thrown
+ away because it proves the architecture&nbsp;invalid.</span>
+ </li>
+</ul></problem>
<application><h3>
How to Read this Practice
</h3>
@@ -72,22 +82,16 @@
how it is organized.&nbsp;
</p>
<p>
- The best place to start is with the key concepts for the practice -- those concepts that are critical to understand in
- order to adopt the practice.&nbsp; An especially important concept for the Evolutionary Architecture practice is <a
- class="elementLinkWithType"
+ Next, review the key concepts for the practice.&nbsp; An especially important concept is <a class="elementLinkWithType"
href="./../../../core.tech.common.base/guidances/concepts/software_architecture_59A08DE0.html"
- guid="__O7tAMVvEduLYZUGfgZrkQ">Concept: Software Architecture</a>.&nbsp; Once you understand what architecture is, you
- can turn your attention to the artifact produced by the practice, the <a class="elementLinkWithType"
- href="./../../../practice.tech.evolutionary_arch.base/workproducts/architecture_notebook_9BB92433.html"
- guid="_0XAf0MlgEdmt3adZL5Dmdw">Artifact: Architecture Notebook</a>.&nbsp;&nbsp; Then you can&nbsp;review
- the&nbsp;practice's tasks.&nbsp; From the work products and the tasks, you can access applicable guidance -- guidelines
- and tool mentors associated with each task provide details of how to perform the task.&nbsp;Templates and checklists
- associated with the work products guide you in their completion and evaluation. You can also access the guidance
- provided by the practice directly, via the&nbsp;guidance folder.
+ guid="__O7tAMVvEduLYZUGfgZrkQ">Concept: Software Architecture</a>.&nbsp; Once you understand what architecture is, turn
+ your attention to the Architecture Notebook.&nbsp;&nbsp; Then review the&nbsp;tasks, accessing guidelines and tool
+ mentors associated with each task as needed.&nbsp;You can also access the guidance provided by the practice directly,
+ via the&nbsp;guidance folder.
</p>
<p>
- Once you have an understanding of these key elements of the practice, you can take a look at the provided list of
- enablement materials (see the&nbsp;"Additional Information" section of this document.
+ Be sure to take a look at the list of enablement materials for additional sources of information.&nbsp; See
+ the&nbsp;"Additional Information" section of this page.
</p>
<p>
For step-by-step instructions on how to adopt this practice, see <a class="elementLinkWithType"
