Unified Process

02/09/08

Basic Engineering Methods

1

UP or AUP

02/09/08

Basic Engineering Methods

2

Philosophy of UP

► ► ►

Your staff knows what they're doing. People are not 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 are interested, but doesn't force them upon you. Simplicity. Everything is described concisely using a handful of pages, not thousands of them. Agility. The Agile UP conforms to the values and principles of the agile software development and the Agile Alliance. 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. 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). You'll want to tailor the AUP to meet your own needs.
3

02/09/08

Philosophy of UP

► ► ►

Your staff knows what they're doing. People are not 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 are interested, but doesn't force them upon you. Simplicity. Everything is described concisely using a handful of pages, not thousands of them. Agility. The Agile UP conforms to the values and principles of the agile software development and the Agile Alliance. 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. 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). You'll want to tailor the AUP to meet your own needs.
4

02/09/08

Disciplines of UP
Model. Understand the business of the organization, the problem domain being addressed by the project, and identify a viable solution to address the problem domain. ► Implementation. Transform model(s) into executable code and perform a basic level of testing, in particular unit testing. ► Test. 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. ► Deployment. Plan for the delivery of the system and to execute the plan to make the system 02/09/08 5 available to end users.

Disciplines of UP
Configuration Management. Manage access to project artifacts. This includes not only tracking artifact versions over time but also controlling and managing changes to them. ► Project Management. Direct the activities that takes place within 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. ► Environment. Support the rest of the effort by ensuring that the proper process, guidance (standards and guidelines), and tools (hardware, 02/09/08 software, etc.) are available for the team as

6

Stages of UP

Inception
 Identify the initial scope of the project, a potential architecture for the system, and obtain initial project funding and stakeholder acceptance.

► ►

Elaboration
 Prove the architecture of the system.

Construction
 Build working software on a regular, incremental basis which meets the highest-priority needs of project stakeholders.

Transition
 Validate and deploy the system into the production environment.

02/09/08

7

Inception
► Not

iterated over ► Short (two day) time frame ► Results in vision statement ► Too long means you are thinking too hard instead of doing.

02/09/08

8

Elaboration
►Iterative ►Focus

on architecturally crucial elements ►Like spike tests but with architecture ►Answer “can it be done?” ►Refinements workshops ►Ends with requirements and code

02/09/08

9

Construction
► Development

of well understood aspects of problem ► Building on the stable architecture ► Testing ► Documentation

02/09/08

10

Transition
►Release

candidates ►Review and feedback ►Integration

02/09/08

11

02/09/08

12

Hallmarks of UP
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.

02/09/08

13

Work Products
►Vision ►Risk

List

02/09/08

14

Class issues

02/09/08

15

Final Deliverable
► Initial

project goals ► Process model used ► Internal communication plan ► External communication plan ► What got accomplished ► Client deliverables ► Task breakdown and who did what ► Difference between start and finish
02/09/08 16