2. Unified Processes
• Unified Process (UP)
• Rational Unified Process (RUP)
• Agile Unified Process (AUP)
• Open Unified Process (OpenUP)
3. Unified Process (UP)
• The Unified Process (UP) is a software process
framework.
• Basic properties:
– Usage of use-cases
– Architecture-centric
– Iterative
– Incremental
– Risk-mitigation
– Object-oriented
4. Rational Unified Process (RUP)
• The Rational Unified Process (RUP) is a
software process developed and marketed by
IBM Rational Software.
• The RUP provides the details required for
implementing projects using the UP, including
guidelines, templates, and tools.
5. Agile Unified Process (AUP)
• Agile Unified Process (AUP) is a combination
of agile approaches and a simplified version of
the Rational Unified Process (RUP).
• AUP is scalable. In other words, it can be
applied to small and large projects.
• The AUP lifecycle is serial in the large, whereas
it is iterative in the small.
6. Disciplines of AUP
• Model
• Implementation
• Test
• Deployment
• Configuration Management
• Project Management
• Environment
7. Phases of AUP
• Inception
• Elaboration
• Construction
• Transition
8. Philosophy
• Stakeholders should know the project goal.
• Simplicity.
• Agility.
• Focus on high-value activities.
• Tool independence.
• Tailor to meet your own needs.
9. Open Unified Process (OpenUP)
• The Open Unified Process (OpenUP) is a part
of the Eclipse Process Framework.
• OpenUP is an open source process framework
developed within the Eclipse Foundation.
• http://epf.eclipse.org/wikis/openup/
• It provides best practices from a variety of
software development projects.
10. Open Unified Process (OpenUP)
• OpenUP is an agile process.
• OpenUP is iterative and incremental.
• OpenUP employs a pragmatic and agile
philosophy that focuses on the collaborative
nature of software development.
• It is tool-independent.
11. Open Unified Process (OpenUP)
• OpenUP/Basic
– The most agile and lightweight form of OpenUP is
OpenUP/Basic.
– It is designed for small projects.
12. Layers of OpenUP
• Micro-increments
• Iterations
• Project phases
– Inception
– Elaboration
– Construction
– Transition
13. Micro-Increments
• At a personal level, team members contribute
their work in micro-increments, which
typically represent the outcome of a few hours
to a few days of work.
• Progress of micro-increments are shared for
work visibility, trust and teamwork.
14. OpenUP Principles
• Collaboration.
• Balancing competing priorities to maximize
stakeholder value.
• Focusing on the architecture early to minimize
risks.
• Obtaining continuous feedback and
improving.
