OpenUP 1.0 - Release Notes
The following considerations apply to OpenUP 1.0:
- Scope: OpenUP aims at being minimal and complete, focusing on only fundamental content required for a development process that can be used as-is for specific contexts. This means that we have on purpose de-scoped many content areas, including environment, advanced configuration management, GUI prototyping, database refactoring, and model-driven development, among others. Those and many other content areas may later be added as plug-ins extending OpenUP. While de-scoping we have ensured that the resulting process is complete enough to be applied by a team to build a software application.
- Field testing: OpenUP captures the vast experience of its authors on real projects and borrows from many different processes, including IBM Rational Unified Process, other variants of the Unified Process, DSDM, XP, Scrum, Eclipse Way, Agile Model-Driven Development, and the experience of contributors from a broad cross-section of environments. The content of OpenUP 1.0 has been written from scratch to provide a concise and well integrated process that takes an integrated, team-based and stakeholder focused approach that provides a fresh perspective on software development. OpenUP is stable enough to be used as is by project teams, and it will continue to evolve as teams adopt it and provide feedback.
- Extensibility: Customizations via extensibility (plug-ins) are encouraged to ease maintenance when new versions of OpenUP are released. However, we expect to change the structure of process elements in OpenUP for the next release to address scalability. This could mean that some restructuring of your plug-in may be required after OpenUP has been refactored.
- Consistency: OpenUP has been collectively written by many
people from a dozen or so organizations. However, we have firmly pursued consistency
in style of writing and depth of content through copy-editing, published authoring
guidelines and extensive reviews.
