| <?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" xmi:id="-nC9dJksbJ2joA-Wqhq4yhw" |
| name="new_supporting_material,_YADsQFlfEdul8L-IGeA7TA" guid="-nC9dJksbJ2joA-Wqhq4yhw" |
| changeDate="2006-10-27T03:14:21.533-0700" version="1.0.0"> |
| <mainDescription><p>
 |
| In 1999, Rational Software and the DSDM Consortium collaborated to produce a RUP/DSDM interoperability paper (see "<a class="elementLink" href="./../../../dsdm_openup/guidances/whitepapers/dsdm_rup.html" guid="_6LZh8FlkEdu-hcil0jQ6jA">DSDM and the Rational Unified Process</a>"). Much of that paper remains relevant when
 |
| considering using DSDM with OpenUP. The following excerpt is particularly appropriate.
 |
| </p>
 |
| <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
 |
| <p>
 |
| To quote the DSDM Manual,<br />
 |
| “DSDM is more a framework than a method. It does not say how things should be done in detail, but provides a
 |
| skeleton process and product descriptions that are to be tailored to suit a particular project or a particular
 |
| organisation”.
 |
| </p>
 |
| </blockquote>
 |
| <p dir="ltr">
 |
| In this sense, OpenUP complements DSDM by providing detailed guidance for the technical aspects of software
 |
| development.
 |
| </p>
 |
| <p dir="ltr">
 |
| Further, the paper notes that
 |
| </p>
 |
| <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
 |
| <p dir="ltr">
 |
| "It was suggested in an early meeting of the team that DSDM was a paradigm – you can approach software development
 |
| with a DSDM frame of mind, almost regardless of the process...If you are a RUP user and need to adopt a
 |
| business-centred RAD approach then DSDM will provide many useful techniques...<strong>In an ideal world it would be
 |
| nice to have all these techniques defined in a shopping basket or tool kit from which you could pick the
 |
| appropriate techniques regardless of the process being utilised.</strong>" (<em>original emphasis</em>)
 |
| </p>
 |
| </blockquote>
 |
| <p dir="ltr">
 |
| The Eclipse Process Framework in general - and Method Composer in particular - provide such a tool kit.
 |
| </p>
 |
| <p dir="ltr">
 |
| OpenUP/Basic defines a process that is minimal and complete from a technical team perspective. DSDM, like many Agile
 |
| methods, promotes active user involvement on a project. OpenUP provides for this with a minimalistic definition of the
 |
| Stakeholder role. The DSDM Plugin for OpenUP extends this Stakeholder role by adding four business roles and assigns
 |
| them specific responsibilities for key aspects of the project. These roles are;
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Executive Sponsor
 |
| </li>
 |
| <li>
 |
| Visionary
 |
| </li>
 |
| <li>
 |
| Ambassador User
 |
| </li>
 |
| <li>
 |
| Advisor User
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| These roles are applied to OpenUP in a complementary fashion. For simplicity, the DSDM roles have been applied to
 |
| existing Tasks and Products - no new tasks or products have been introduced to OpenUP in this plugin.
 |
| </p>
 |
| <p>
 |
| The addition of these roles to OpenUP promotes an&nbsp; <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">explicitly</span>
 |
| collaborative approach , where software development responsibility is shared by the business and technical communities.
 |
| It is the experience of DSDM practitioners and the wider Agile community that this significantly enhances the potential
 |
| for a successful project.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
