| <?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="-Q-GudeReXWSmfMm2wFXDkg" |
| name="how_to_adopt_practice_fw_architecting,_qVnDgi2sEd2CiunvJQy6fQ" guid="-Q-GudeReXWSmfMm2wFXDkg" |
| changeDate="2008-11-13T14:37:03.078-0800" version="7.2.0"> |
| <mainDescription><h3>
 |
| Getting started&nbsp;
 |
| </h3>
 |
| <p>
 |
| Begin by making sure the team, including the key stakeholders, understands the&nbsp;and the key concepts and the
 |
| roadmaps.
 |
| </p>
 |
| <p>
 |
| The Practice Framework Architecting practice assumes that the method authoring environment has been set up.&nbsp; Make
 |
| sure that all team members can access the environment and understand how to use it.
 |
| </p>
 |
| <p>
 |
| This practice supports architecting a new practice framework, as well as customizing an existing practice framework
 |
| architecture.
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| To adopt the "architect new practice framework" aspects, start by identifying the context to be addressed by the
 |
| framework. It is recommended that the first time you apply this practice that you apply it to architect a practice
 |
| framework where the content to be included in the framework is well understood and where subject matter
 |
| experts&nbsp;of the framework are part of the authoring team. Architect the practice framework&nbsp;incrementally,
 |
| defining the guiding principals and the structure of the core&nbsp;first, followed by the detailing of the core
 |
| elements. See&nbsp;<a class="elementLinkWithType"
 |
| href="./../../../practice.mdev.auth.practice_fw_arch.base/guidances/roadmaps/arch_new_practice_fw_CE6D85ED.html"
 |
| guid="_eV2FoKEKEd2bTrLTU21QBw">Roadmap: Architect a New Practice Framework</a>&nbsp;for details.
 |
| </li>
 |
| <li>
 |
| To adopt the "customize existing practice framework architecture" aspects, start by identifying the framework you
 |
| want to customize and how you want to customize it. It is recommended that the first time you apply this practice
 |
| that you apply it to customize a practice framework that is well understood and where subject matter
 |
| experts&nbsp;of the framework (and the customization) are part of the authoring team. See&nbsp;<a
 |
| class="elementLinkWithType"
 |
| href="./../../../practice.mdev.auth.practice_fw_arch.base/guidances/roadmaps/customize_existing_practice_fw_arch_DE266E74.html"
 |
| guid="_VQlaMKEeEd2bTrLTU21QBw">Roadmap: Customize an Existing Practice Framework Architecture</a>&nbsp;for
 |
| details.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| As you apply the recommendations described in the practice, capture what you have learned, what worked for your team
 |
| and what didn't so that you can continually fine-tune how your team applies the practice.
 |
| </p><br />
 |
| <h3>
 |
| Common pitfalls
 |
| </h3>
 |
| <p>
 |
| The following are some common pitfalls when adopting this practice.
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Selecting a practice framework whose content is not well understood as your first framework using this
 |
| practice.&nbsp;If this is done, more time is spent understanding the framework itself rather than in effectively
 |
| applying the practice techniques.
 |
| </li>
 |
| <li>
 |
| Spending too much time architecting on paper.&nbsp;If this is done, the time it takes to deliver the framework is
 |
| extended as a lot of time is spent structuring as opposed to just enough to get an initial framework out to get
 |
| feedback, refining the structure, as needed. Try to keep the documentation clear and concise.&nbsp;Make sure that
 |
| the consumers of the architecture documentation (the development team) are comfortable with the format and content
 |
| of the documentation.&nbsp;Is there more or different information they would like see?&nbsp;Would they like to see
 |
| less?
 |
| </li>
 |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
