|
Scott Ambler's Agile Unified Process (AUP) is a simplified version of the Rational Unified Process (RUP). It describes a simple, easy to understand approach to developing business application software using agile techniques and concepts yet still remaining true to the RUP. The AUP applies agile techniques include test driven design (TDD), Agile Modeling, agile change management, and database refactoring to improve your productivity. The Rational Unified Process (RUP) is an iterative software development process created by the Rational Software Corporation, now a division of IBM. The RUP is an extensive refinement of the (generic) Unified Process. ...
Agile Modeling is a supplement to other Agile Methodologies such as: Extreme Programming (XP) Scrum [1] Answers to Criticisms The principles and values of Agile Modeling practises help to mitigate the criticisms of Agile Software Development. ...
Phases
Like the RUP, the AUP is comprised of four phases: - 1. Inception
- The goal is to identify the initial scope of the project, a potential architecture for your system, and to obtain initial project funding and stakeholder acceptance.
- 2. Elaboration
- The goal is to prove the architecture of the system.
- 3. Construction
- The goal is to build working software on a regular, incremental basis which meets the highest-priority needs of your project stakeholders.
- 4. Transition
- The goal is to validate and deploy your system into your production environment.
Disciplines Unlike the RUP, the AUP only has seven disciplines:
1. Model. The goal of this discipline is to understand the business of the organization, the problem domain being addressed by the project, and to identify a viable solution to address the problem domain.
2. Implementation. The goal of this discipline is to transform your model(s) into executable code and to perform a basic level of testing, in particular unit testing.
3. Test. The goal of this discipline is to perform an objective evaluation to ensure quality. This includes finding defects, validating that the system works as designed, and verifying that the requirements are met.
4. Deployment. The goal of this discipline is to plan for the delivery of the system and to execute the plan to make the system available to end users.
5. Configuration Management. The goal of this discipline is to manage access to your project artifacts. This includes not only tracking artifact versions over time but also controlling and managing changes to them.
6. Project Management. The goal of this discipline is to direct the activities that takes place on the project. This includes managing risks, directing people (assigning tasks, tracking progress, etc.), and coordinating with people and systems outside the scope of the project to be sure that it is delivered on time and within budget.
7. Environment. The goal of this discipline is to support the rest of the effort by ensuring that the proper process, guidance (standards and guidelines), and tools (hardware, software, etc.) are available for the team as needed.
Philosophies The Agile UP is based on the following philosophies:
1. Your staff knows what they're doing. People aren't going to read detailed process documentation, but they will want some high-level guidance and/or training from time to time. The AUP product provides links to many of the details, if you're interested, but doesn't force them upon you.
2. Simplicity. Everything is described concisely using a handful of pages, not thousands of them.
3. Agility. The Agile UP conforms to the values and principles of the agile software development and the Agile Alliance. Agile software development is a conceptual framework for undertaking software engineering projects. ...
4. Focus on high-value activities. The focus is on the activities which actually count, not every possible thing that could happen to you on a project.
5. Tool independence. You can use any toolset that you want with the Agile UP. The recommendation is that you use the tools which are best suited for the job, which are often simple tools (like many of open source solutions).
6. You'll want to tailor the AUP to meet your own needs.
Releases The Agile Unified Process distinguishes between two types of iterations. A Development Release Iteration results in a deployment to the Quality Assurance and/or Demo area. A Production Release Iteration results in a deployment to the Production area. This is a significant refinement to the Rational Unified Process. The Rational Unified Process (RUP) is an iterative software development process created by the Rational Software Corporation, now a division of IBM. The RUP is an extensive refinement of the (generic) Unified Process. ...
 Image File history File links AgileUnifiedProcessTimeline20060704. ...
See also The Enterprise Unified Process (EUP) is an extension of the Rational Unified Process. ...
The Rational Unified Process (RUP) is an iterative software development process created by the Rational Software Corporation, now a division of IBM. The RUP is an extensive refinement of the (generic) Unified Process. ...
The IBM Rational Unified Process (RUP) is an iterative software development process created by the Rational Software Corporation, now a division of IBM. The RUP is not a single concrete prescriptive process, but rather an adaptable process framework. ...
External links | 
Feeds |
Contact