| <?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.3/uma.ecore" epf:version="1.0.0" xmi:id="-I2j8LuHkworb0Y3EIlWfDQ" name="core_principles,_HEu9QBOHEduCNqgZdt_OaA" guid="-I2j8LuHkworb0Y3EIlWfDQ" changeDate="2006-11-13T10:02:46.356-0800" version="1.0.0"> |
| <mainDescription><h3> |
| OpenUP Core Principles |
| </h3> |
| <p> |
| OpenUP is based on four mutually supporting core principles: |
| </p> |
| <h4 style="MARGIN: 12pt 0in 3pt"> |
| Collaborate to align interests and share understanding |
| </h4> |
| <p> |
| Software is created by people with different interests and skills who must work together to create software |
| effectively. |
| </p> |
| <p> |
| Therefore, practices that foster a healthy team environment are key to success. A healthy team environment enables |
| effective collaboration that align the interests of project participants (development team, quality assurance, product |
| stakeholders, customers) and helps project participants develop a shared understanding of the project. |
| </p> |
| <h4 style="MARGIN: 12pt 0in 3pt"> |
| Balance competing priorities to maximize stakeholder value |
| </h4> |
| <p> |
| Systems need to be developed by balancing different, and sometimes competing,&nbsp;perspectives. For example, do you |
| want to minimize cost by reusing an existing capability, or by custom developing the capability to get it to do exactly |
| what you want? |
| </p> |
| <p> |
| Therefore, project participants and stakeholders must collaborate to develop a solution that maximizes Stakeholder |
| benefits and is compliant with constraints placed on the project. Achieving balance is a dynamic process, because, as |
| both the stakeholders and project participants learn more about the system, their priorities and constraints change. |
| </p> |
| <h4 style="MARGIN: 12pt 0in 3pt"> |
| Focus on articulating the architecture |
| </h4> |
| <p> |
| Without an architectural foundation, a system will evolve in an inefficient and haphazard way. Such a system often |
| proves difficult to evolve, reuse, or integrate without substantial rework. It’s also difficult to organize the team or |
| communicate ideas without the common technical focus that the architecture provides. |
| </p> |
| <p> |
| Therefore, use the architecture as a focal point for developers to align their interests and ideas by articulating the |
| essential technical decisions through the growing architecture.<span style="mso-spacerun: yes">&nbsp;</span> |
| </p> |
| <h4> |
| Evolve to continuously obtain feedback and improve |
| </h4> |
| <p> |
| It is usually not possible to know all stakeholders needs, be aware of all project risks, comprehend all project |
| technologies, or know how to effectively work with your colleagues. Even if it were possible to know all of this, some |
| of it is likely to change over the life of the project. |
| </p> |
| <p> |
| Therefore, divide the project into short, time-boxed iterations to demonstrate incremental value and to get early and |
| continuous feedback.<span style="mso-spacerun: yes">&nbsp;</span> |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |