| <?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="-vY5HfUn9RSoqJC3J7QtxhA" |
| name="new_concept,_qhCTAFRREd2CWscN8Mx6rg" guid="-vY5HfUn9RSoqJC3J7QtxhA" changeDate="2008-09-04T17:59:01.093-0700" |
| version="7.5.0"> |
| <mainDescription><h3>
 |
| Why Practices?
 |
| </h3>
 |
| <p>
 |
| Practices enable a compositional approach to building methods. This approach offers the following benefits:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Adaptability and scalability
 |
| </li>
 |
| <li>
 |
| Incremental adoption
 |
| </li>
 |
| <li>
 |
| Easy to configure and use
 |
| </li>
 |
| <li>
 |
| Community development
 |
| </li>
 |
| </ul>
 |
| <h3>
 |
| Adaptability and Scalability
 |
| </h3>
 |
| <p>
 |
| Practices can be adapted to&nbsp;support a range of solutions.&nbsp;In particular, practices can be adapted to suit
 |
| your organization and supplemented by your own practices.
 |
| </p>
 |
| <p>
 |
| The core practices are based on a common framework that allows them to be composed.&nbsp; These core practices&nbsp;are
 |
| tool-agnostic, low-ceremony practices that can be extended to address a broad variety of development concerns, such as
 |
| SOA, geographical distribution, model-driven architecture and embedded systems. Tool and technology specific guidance
 |
| can be added, such as guidance on J2EE, and a variety of development tools. Some of these extensions can be quite
 |
| modest, adding&nbsp;for example&nbsp;just tool specific guidance to existing tasks, while others can be comprehensive,
 |
| defining processes that provide a radically expanded scope with new or altered artifacts, new or altered tasks, and new
 |
| or altered roles.
 |
| </p>
 |
| <p>
 |
| Extensions and additions to&nbsp;the practices&nbsp;can be:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| used internally by an organization
 |
| </li>
 |
| <li>
 |
| open source as a part of the Eclipse Process Framework (EPF) project
 |
| </li>
 |
| <li>
 |
| made freely available outside the open source licenses of Eclipse (EPL)
 |
| </li>
 |
| <li>
 |
| sold commercially as an extension to the basic framework, such as the IBM(R) Practices.
 |
| </li>
 |
| </ul>
 |
| <h3>
 |
| Incremental Adoption
 |
| </h3>
 |
| <p>
 |
| Each practice is described as a standalone capability that can be adopted by an organization or project.&nbsp;Each
 |
| practice may include enablement materials that explain how to get started.&nbsp;&nbsp;
 |
| </p>
 |
| <h3>
 |
| Easy to Configure and Use
 |
| </h3>
 |
| <p>
 |
| Creating a method is as simple as selecting the practices that you wish to adopt, and then publishing the
 |
| results.&nbsp;Each practice adds itself into the framework so that content can be viewed by practice, or across
 |
| practices by work product, role, task and so on.
 |
| </p>
 |
| <h3>
 |
| Community Development
 |
| </h3>
 |
| <p>
 |
| Since a practice can be easily authored on its own, practices are ideal for community development.&nbsp;The basic agile
 |
| practices for the&nbsp;EPF Practices are, in fact, developed by the Eclipse Process Framework community.&nbsp;
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
