| <?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.4/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" |
| epf:version="1.2.0" xmi:id="-l-ZsqrXu2nmVE1giLpI6iw" |
| name=",_qg1IAK__EduMeuOwJ2MpeQ" guid="-l-ZsqrXu2nmVE1giLpI6iw" changeDate="2007-07-09T08:02:31.562-0700" |
| version="1.0.0"> |
| <mainDescription><p> OpenUP combines elements of agile and unified methods to create a hybrid process 
 |
| that leverages proven best practices of both process perspectives. OpenUP includes 
 |
| these common elements of both perspectives: </p>
 |
| <ul>
 |
| 
 |
| <li> Time-boxed (time-limited) iterations that deliver incremental stable functionality 
 |
| to the stakeholders </li>
 |
| <li>
 |
| Frequent iteration assessments that adjust the course of product development
 |
| </li>
 |
| <li>
 |
| Tight collaboration between stakeholders and team members
 |
| </li>
 |
| <li>
 |
| Contextual requirements that reduce ambiguity and improve collaboration (use cases)
 |
| </li>
 |
| <li>
 |
| Classic best practices for designing object-oriented systems
 |
| </li>
 |
| <li>
 |
| Robust test cases
 |
| </li>
 |
| </ul>
 |
| <p> Unified processes have helped teams of many different sizes and in different 
 |
| industries become successful in solving their stakeholders' problems. OpenUP 
 |
| is a lightweight realization of these essential elements of a unified process:</p>
 |
| <ul>
 |
| <li>
 |
| Four phases (which contain iterations) that provide different perspectives during the development of the system
 |
| </li>
 |
| <li> Early focus on architecture so that a stable framework can be validated 
 |
| before the bulk of the system is implemented </li>
 |
| <li> Rigorous examination of mitigation of project risks that reduce the likelihood 
 |
| of unforeseen problems and increase project predictability </li>
 |
| <li> Use cases that characterize functional requirements and drive testing and 
 |
| development </li>
 |
| </ul>
 |
| <p> These agile processes and techniques that have a track record of improving 
 |
| a team’s success are incorporated into OpenUP: </p>
 |
| <ul>
 |
| <li>
 |
| A Scrum-based and collaborative approach to project management
 |
| </li>
 |
| <li>
 |
| An agile perspective of estimation and planning
 |
| </li>
 |
| <li> Self-organizing work assignments </li>
 |
| <li>
 |
| An evolutionary approach to architecture and design through different levels of refactoring
 |
| </li>
 |
| <li> Test-driven development </li>
 |
| </ul>
 |
| <p> Merging these different perspectives creates a process that is lightweight 
 |
| and robust, with a structure and components that have a proven history of making 
 |
| development teams successful in providing value to their stakeholders. </p>
 |
| <p> The OpenUP process defines roles to clearly specify what skills are necessary 
 |
| to perform certain tasks. At the same time, the process is intended to be applied 
 |
| to self-organizing teams. If a team member has the skills necessary to be an 
 |
| analyst, a tester, and a developer, then it’s appropriate for that individual 
 |
| to play all three of those roles. Roles are not meant to inhibit team members 
 |
| from performing any work that needs to be done. </p>
 |
| <p> Each of the subprocesses and the collaboration layer also support the <a href="http://www.agilemanifesto.org" target="_blank">Agile 
 |
| Manifesto</a>: </p>
 |
| <ul>
 |
| <li> <b>Collaboration: </b>Individuals and interactions over process and tools 
 |
| </li>
 |
| <li><b>Solutions: </b>Working software over comprehensive documentation </li>
 |
| <li><b>Intent: </b>Customer collaboration over contract negotiation </li>
 |
| <li><b>Management: </b>Responding to change over following a plan</li>
 |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
