Next Generation Process

with

Essential Modeling
Ivar Jacobson
with Pan Wei Ng and Ian Spence [email protected] [email protected]

Agenda A new paradigm with several exciting innovations Practice separation

Essential UML

Practice user experience using the card metaphor

Essential UML

Developing software by playing games Final words

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

A Next Generation Process is not monolithic

In the future, an ever present but invisible process

Process becomes second nature

Practice Separation Practice User Experience Practice Smartness

And the innovations of a new paradigm

A new paradigm
From the successes in modern software development
2005 Ivar Jacobson International

Practice is a First Class Citizen

the unit of adoption, planning and execution of process
Unified Process Camp Process Maturity Camp Agile Methods Camp

Essential Unified Process Primer / 01 - Essential Principles and Practices

A Next Generation Process is not monolithic

In the future, an ever present but invisible process

Process becomes second nature

Practice Separation Practice User Experience Practice Smartness

And the innovations of a new paradigm

A new paradigm
From the successes in modern software development
2005 Ivar Jacobson International

Practice is a First Class Citizen

the unit of adoption, planning and execution of process
Unified Process Camp Process Maturity Camp Agile Methods Camp

NEW

Essential Unified Process Primer / 01 - Essential Principles and Practices

New paradigm must appeal to two distinct communities

Process users Practitioners who apply the process to a project Select practices & add them to their process Key needs: simplicity, ease of use, understandability

Process engineers Experts who develop process content in the form of practices Have a deep understanding of process & practice structure etc Key needs: tailoring, extension and composition

Process descriptions dont need to be lengthy... Since there are lots of publications available, there is no need write a massive document. - Dave Thomas

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

Building on our heritage

Late 60s

Ericsson Approach

Objectory Process
87 96

97 98

The Unified Process

99 05

IBM Rational Unified Process

Really Good Software

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

However, there are challenges with UP based methods Unified Process is too heavy UP requires substantial investments in tools, training and mentoring
Find the knowledge
Knowledge base is too big, how to find just the right stuff?

Control the use of knowledge

How to manage project applying this stuff? What tools?

Learn the knowledge

Knowledge base is too big, How to learn the stuff I need?

Apply the knowledge

How to apply what I learn in a project?

We need to attack these challenges

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

Being Agile goes without saying for a NGP What characterizes an agile process
1. It includes social engineering patterns
War-room Everything is owned by someone Developer sandboxes Pair development

2. It is lightweight
Tacit knowledge instead of explicit knowledge

3. It usually has some specific technical practices

User stories Test driven design Refactoring

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

Agenda A new paradigm with several exciting innovations Practice separation

Essential UML

Practice user experience using the card metaphor

Essential UML

Developing software by playing games Final words

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

What is a Practice? Pragmatics

A Practice is a set of activities to give value to a particular stakeholder of a software organization A Practice explicit knowledge waiting to be put into action
A practice has a clear beginning and an end allowing it to be independently applied

Our practices are supplied as a set of cards and guidelines defining a way of doing something A use-case module in our AOSD book
It has a beginning and an end It may be a peer practice or extend an existing practice

More precisely

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

10

The Practices in the Essential Unified Process

Essential Practices

Technical Practices

Architecture

Component

Social Engineering Practices Process Practices Organizational Practices

Ti tl e

It is

Process

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

i Ev s te s er yw ting ? he re !
Iteration Product Team

Use Case

he

re

Modeling

11

Building a process eco-system around 8 Essential Practices There will be 100s of practices extending the essentials
Essential Practices
Systems Engineering Business UseCase Iteration Enterprise Product Architecture Line Eng. SOA

Architecture Aspect Orientation Robustness Analysis

Use Case REUSE

Domain Modeling

Model Driven Architecture

Component

Product

Technical Practices Social Engineering Practices Process Practices Organizational Practices

T i t l e

Process

Team

Modeling 6 Sigma Prince2

PSP / TSP

Pair Programming

Extended CMMI

Portfolio Management

Program Management
12

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

Agenda A new paradigm with several exciting innovations Practice separation

Essential UML

Practice user experience using the card metaphor

Essential UML

Developing software by playing games Final words

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

13

Modeling Essentials Practice

About using models to facilitate communication and produce useful documentation Focuses on establishing the appropriate style and type of models to drive development activities Enable software development teams to:
Communicate system requirements, structure and behavior Employ the right models to meet their needs Be agile in their approach to modeling and documentation Focus on the essentials, avoiding modeling paralysis and the production of unnecessary documentation

This is a cross-cutting practice that influences how the other practices are under-taken.
2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

14

Modeling Essentials supports the other practice goals

Product

Use Case

Architecture

Component

Involve stakeholders in the decision making process Ensure the product meets the real needs of the stakeholders

Work with customers to capture the essential requirements Use a systematic approach to ensure the correct design, implementation and verification of requirements Helps the other practices achieve their goals by establishing the appropriate style and type of models to drive the development activities

Establish a firm foundation for the incremental development of the solution Share the major decisions about the structure and organization of the implemented system

Develop and verify the separate parts of the system independently and in parallel Exploit third party frameworks and component libraries

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

15

What about UML 2.0? The UML 2.0 Infrastructure defines the foundational language constructs required for UML 2.0. It is complemented by UML 2.0: Superstructure, which defines the user level constructs required for UML 2.0.
It is 218 pages long!

The superstructure defines the six structure diagrams, three behavior diagrams, four interaction diagrams, and the elements that comprise them, and so is the part of the language that you'll encounter in UML 2.0 compliant tools.
It is 720 pages long!

Written by tool vendors for tool vendors!

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

16

What do practitioners want? To be able to easily communicate To model with or without tools To start with something simple A common language to communicate structure, behavior, ownership, packaging, dynamics and abstractions.

Is this something the UML gives us?

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

17

What do practitioners want? To be able to easily communicate re. To model with or without tools e wh f the To start with something simple me o behavior, A common language to communicate structure, s o 0% 8 ownership, packaging, dynamics ands abstractions. ere

h e n t ovid g i pr din at lue! i s h % t h va l i t 20 el e W th s ItIs this something the UML gives us?

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

18

Where do practitioners start? The Superstructure and Infrastructure Specifications? The Meta-Model? The Kernel? (part of the superstructure) The Core? (part of the infrastructure) At the lowest UML Compliance Levels?
Level 0 Entry Level Modeling Capability (formally defined in the UML Infrastructure) Level 1 Adds language units for use cases, interactions, structures and activities Level 2 Adds language units for deployment, state machine modeling and profiles Level 3 The complete UML adds language units for modeling information flows, templates and model packaging

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

19

Then, should we use UML for modeling? Absolutely, positively, definitely YES
UML is the standard for visual modeling of software systems It is a rare example of a universally popular and pervasive standard It has had a long and happy relationship with the Unified Process

But .
UML is language with a very broad scope Not all of its modeling capabilities are necessarily useful in all domains or applications UML is difficult for practitioners to approach and apply directly Essential UML focuses on the essential subset (the 20%) that is useful for any software development project

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

20

Where does Essential UML sit? It is an Extension to the Modeling Essentials Practice

Essential Practices

Architecture Iteration

Use Case

Component

Product

<<extend>> Essential UML

Title

Process
2005 Ivar Jacobson International

Team

Modeling
21

Essential Unified Process Primer / 01 - Essential Principles and Practices

Lets extract the essentials from the UML

The Essential UML presents the essence of the UML for use by practitioners.

Essential UML
<< imports >> It depends on the UML 2.0 language definition and benefits from its rigor and completeness

UML 2.0

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

22

Extending the Essential UML Practice

Practice Area Modeling

<<extend>>

Modeling For This

<<extend>>
Modeling

<<extend>>

Essential UML
Modeling For That

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

23

Essential UML elements and their applications

Diagram Class Diagram Component Diagram Used to Establishing key abstractions and designing components Defining component interfaces and establishing dependencies

Package Diagram Deployment Diagram

Structuring use-case, architecture, component and other models Communicating architecturally significant aspects of the deployment Establishing a common understanding of what the system must do for its users Showing flow of control within interactions and operations Describing lifecycles of key abstractions and dynamic behavior of components and classes Establishing the collaborations required to realize a use case Distributing responsibilities to key abstractions and establishing collaborations between components, interfaces and classes
Essential Unified Process Primer / 01 - Essential Principles and Practices 24

Use-Case Diagram

Activity Diagram State Machine Diagram Collaborations Interaction Diagrams

2005 Ivar Jacobson International

Essential UML: Summary Gets to the heart of the UML Presented in the context of its application within essential software development practices A simple way to get started Just enough UML for most projects Built on top of the UML 2.0 specification A new way to promote and publicize the UML

A complement to UML 2.0 Complements the Modeling Essentials Practice

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

25

Agenda A new paradigm with several exciting innovations Practice separation

Essential UML

Practice user experience using the card metaphor

Essential UML

Developing software by playing games Final words

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

26

Individu different al Flows may have degrees of elab oration

Apply card game metaphor for practice descriptions

2005 Ivar Jacobson International

2005 Ivar Jacobson International

Nobody reads.

UC

DD

A practice is a set of cards

st Te

se Ca

yT ecif Sp

est

ress Prog Track Use-C ase Sp ecificati on

Can be divorced from reality

Exe cute

m to us

Tes t

R er

r ep

ta en es

e tiv

Usually presented in books, web pages.

er att k a ip M Va ntia in ic a unic st ct ert art se m u bje xp Es Do mm s tr of p ct Su E je or Co ild ble s Bu pa ion 6 Pro dvis or Ca ess 200 ad A l, s ss r na es ba se atio ag rn te Am U an In M pe n bso e ely co co th s tiv S Ja ar Ac cts es Iv ire in D us B

ng ati ic : un h e to m ug th m ro ich am co tho wh te d e th an s a in a y lp ng . H ain d. nit of he eri s om e rtu ds th eed d loy ves e ep po ee ts ti ga n ta op d n en at er f th d n s m d old e o be sen rs es s a ire e in ille eh dg ill re es qu Sk tak wle n w rep riti hold us lem re m s no tio er e rio ke e b rob th ste p m e p sta th k olu y e s sto fin fy ate s nd th rs Cu De nti rsta nd lde alu red ng e v e 24 eli Id de rsta eho d e liv on od si de Un de tak an vi m e : n s re ge ills re d k U e th in th ptu ate kills wle n s ng Ca lid l S no tio ati

Not handy, not easy to work with them, etc.

A team/individual works on a set of instance cards

en Ess

tia

lU

nifi

ed

d an ts pu in f o. st e o ari f te os tem en d t o rp ys sc an se pu s ic g DD a e t a cif UC nin es r th r no spe ig fin fo o a es de s er rd m e ult th nts te fo as res he me n ys c d w le re fo tio fs st g p te cte n be em da ts n o A pe ati y im d st un tes tio are ex valu ectl es: fo ifiele sy a ting ple sts ecab e rr as e m : put s e te lts co t c vid en test to exec ed co n e e s tart of tth resu e DD s m a s ifi o Te Pro ecify the at th to b ecs omes te test ftwarUC ple r ati w th ts sp n tc fo e im Sp orify ic ssas tio ou: ine th the so s 24 ll st Ve if te n the ts a A pec rm ewta tentermn t of eet d Te on rfo g io em s e an pe owe ho tonde dit pmen lts tm m o st visi nin plan to: g fin Sy egrat re mus su klo All ple ted C on lo ve Int efi ed Bac De im ua tial e de sts it Re ifi -c (d : h the e Specif ec eval en th re e te abl ied ssswit s P Sp System cut d ut ted grewhen ) as w d Exe tem c ss ..n th tif Sys m Focu rds Inp eual pro edlo ste are ocity ie E wa n act to: ete F ble 1 o Iden fied xp mpl pro te d vel to ject eci Sp temPro 1.. are E contify s be an s ari n es Comp ..n ly ide -Ca gress Case ion Sys Steer en se ick n de to 1 ity is c ed pro Testmplet ts Qu activ fere an s rio n: e co Sc Int o derstifiU tio s emen ec Chegrat ble le klog leston 6 achiev : Sp na The Un e 1..nifica Bac eTesterutab stR dict mi an 200 a d Te d ec ce tone : en: em Te Pre ndmiles, st Sp s ariExecnest Syst per nal fi elo d V ed cheswh nd d Dev cifie yo s Spe em Te Asses atio coproa mplet test UCDD De ject Leada ne or be d Syst ta fi ch as A use- rn y is ap em ate te Pro a ivit d Evalu e d (su en In case anact de lts: st dresse 24 t actor su spec ad tD D on The mmen usessy ification have be on bs Bries ults and st Re en test e fly Des Lead co a syst ts)describe revisi d Spe em s how RecoTe whand items defec to sse cifi T t the s ect crib Ja Indepe og on d Sys ed achieve dre ad tem Backl si system does ar achieve esrios an st ed Re Exe Proj lyst ed Iv n te gr that goal rifi flo the for wseda goal cut Re na atio Ve Ana sce as . Module Sys able d rifi actor tem Use-castegr as Ve s been to n er marke e-Case Bullete elop ow In e spec 06 rked Dev ha d OutlineBac Cap The Us ificama s: ement ity is kn 20 tion en klo tureve al, st be oc er iev Teg ation Test ss ha requirements Defi ernation one ach team vel ce Exec Int scen ecific ne d in cont est Sp Pro ut es: ext bson e Mil arios an ed Essenti Ena a d coVe ble proach cking te ord fie tem rec al rify effective r Ja ni e Sys traUC d thProv th st to scop ap Test Outline abl Tes cut DD lU Iva e ev ide the : ende e managem ularly gress ter n 24 Exe ia Id devealu at the mmil deta reg s pro revisio to driv ent Re atioco ults ent en lopment ex nuou Dev elo ss nti activities res they to en tifydeliv n cr ecutab tee the other per defeer Co ite nstraand Fully Des E ocess su ct valu ria le sy ensure mo cribed d Pr that Esse re that s De e of th st ifie The klogntial Con th and pl 2006e em m Un Bac t test tents:tional, e eets Tes ac ey ntial ac1 ults Te Bactivity e rnaare Nam in klog Esse Res addr the le on Inte -Case st:1Ev is co utab Use ule esse back Briefobs m Exec em An Jac log Mod Syst Ivar alu Des plet d y1 Bas ated cription Defe d ed Back Essential cifie Spe em ic wh cts: Flow Unified Test en: s Te log Syst Process 0..n Alte Iden Proces st Re tified rnative fied Te sults Flows Exe ial Uni Ivar Jaco and cut Re st Esse bson Reco Intern : An abl Essent adde e Sys sults ntial ation aly tem d to Unifie Au mmen al, 2006 zed the ded d Pr Defec Pr tomat oces appr ed t s revision oach test Bac Ma ogram 24 klo es: g nual matic ing Iva te test r Ja ing sting co

ce Pro

ss

bson

Intern ation

al,

2006

rev

isio

n 24

published in 1989
27

Law of Nature: Most People dont read Manuals, etc.

Today, process descriptions are designed for process engineers

A card contains concise description of things to produce and things to do, etc.

Essential Unified Process Primer / 01 - Essential Principles and Practices

Essential Unified Process Primer / 01 - Essential Principles and Practices

* Ward Cunningham invented CRC cards,

28

The Essentials are in the cards

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

29

More are in the guidelines

Reference books

RUP Knowledge Base

I do test cases

Intelligent Agents
2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

30

Intelligent Agents Learn about Intelligent Agents and how they support software development at www.jaczone.com

I am an intelligent agent. I have knowledge. I am autonomous. I am goal-oriented.

JACZONE

WayPointer

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

31

Agenda A new paradigm with several exciting innovations Practice separation

Essential UML

Practice user experience using the card metaphor

Essential UML

Developing software by playing games Final words

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

32

The Essential UML are also in the cards

Implemented System

Component Diagram
component

Essentials

port component

A component diagram is used to show: Components in a system and the interfaces that they implement The dependencies that a component has on other component interfaces Essential Contents: Components a unit of software that implements a set of interfaces Ports interaction points with welldefined interfaces Provided Interfaces sets of services made available by the component Required Interfaces sets of services required by the component Dependency Relationships use of a component or interface by a component Recommended Stereotypes: <<subsystem>> A course-grained system component
revision 11

provided interface on port dependency relationship

required interface on port

provided interface

component

required interface

Essential UML

Ivar Jacobson International, 2006

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

33

More is in the guidelines

Implemented System Implemented System

Component Diagram Component Diagram

Essentials Essentials

component component port port component component

A component diagram is used to show: A component diagram is and to Components in a system usedthe show: interfaces that they implement the Components in a system and interfaces that they a component The dependencies thatimplement has on dependencies thatinterfaces The other component a component has on other component interfaces Essential Contents: Essential Contents: of software that Components a unit implements a set a interfaces Components of unit of software that implements a set of interfaces Ports interaction points with welldefined interaction points with well Portsinterfaces defined interfaces Provided Interfaces sets of services made available by the sets of services Provided Interfacescomponent made Interfaces sets of services Requiredavailable by the component required by Interfaces sets Required the component of services required by the component Dependency Relationships use of a component or interface by a component Dependency Relationships use of a component or interface Recommended Stereotypes: by a component Recommended Stereotypes: <<subsystem>> A course-grained system component <<subsystem>> A course-grained system component
revision 11 revision 11

provided required interface interface provided required on port on port interfacedependency interface on port on port relationship dependency relationship provided interface provided interface

component component

required interface required interface

Essential Unified Process Essential Unified Process

Ivar Jacobson International, 2006 Ivar Jacobson International, 2006

Reference books

I do Component Modeling

Intelligent Agents
2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

34

Agenda A new paradigm with several exciting innovations Practice separation

Essential UML

Practice user experience using the card metaphor

Essential UML

Developing software by playing games Final words

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

35

What is the game?

Current Situation and Opportunity

Good Software

How do we produce good software, quickly?

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

36

Surely process is the answer..

Current Situation and Opportunity

Good Software

a list of things to address

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

37

Surely process is the answer..

Current Situation and Opportunity

Good Software

and a map would be useful

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

38

Surely process is the answer..

Current Situation and Opportunity

Good Software

and an understanding of the skills needed

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

39

And the rules of the games we are playing

Use a Practice in a Project

[Development Game]

Use the Process to Plan the Project

Current Situation and Opportunity [Planning Game]

Good Software

Select Practices and Assemble a Process

[Process Improvement Game]

Three collaborating games. All made simpler by the practices and the cards.
2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

40

The Process Kernel Controlling the Games A practice independent micro-process Where we are going alphas What we are doing activity spaces What skills do we need - competencies

C om pe te nc ie s

uc

od

Pr

Th in gs

@ Key Generic Artifacts

2005 Ivar Jacobson International

@ Key Generic Activities

41

Essential Unified Process Primer / 01 - Essential Principles and Practices

The Process Kernel. Eight Top Alphas

Opportunity

Specified System

Implemented System

Executable System

Team

Backlog

Project

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

Th in gs
Way of Working

to

to

o
42

Their states tell you where you are

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

43

Lifecycle Patterns Adding control and milestones

Lifecycle Patterns

The Unified Process lifecycle adding control structures to a release cycle

Time

Inception
Life Cycle Objectives Project Viability Agreed
Do you understand scope and risk, and do you have a candidate architecture and a credible plan?

Elaboration
Life-Cycle Architecture Selected Approach Proven
Do you have a solution that is proven to work?

Construction
Initial Operating Capability Useable Solution Available
Is the product working and useable, are the users ready to receive it?

Transition
Product Release Development Completed
Is the product acceptable and is the development project over?

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

44

Inception Target States

Opportunity Specified System
Conceived

Implemented System
Approach Selected Approach Confirmed Interfaces Stable Integrated Production Quality Release Available Released

Executable System
Assembled Approach Validated Functionality Validated Ready to Deploy

Lifecycle Patterns

Opportunity Identified Problem Understood Value Established Viability Established Problem Addressed Benefit Accrued

Shared

Stable

Correct

Testable

Accepted

Fulfilled

Operational

Team

Backlog

Project

Way of Working

Set Up Mission Defined Driving Work Formed Change Under Control Focused Quality Goals Met Collaborating Sufficient Work Completed Outstanding Items Handed Over

Underway Gaps Analyzed Milestones Agreed Options Explored Risks Under Control Development Complete Responsibilities Handed Over Closed Essentials In Place Embedded

Key
Essential

Recommended

Disbanded

Handed Over

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

45

Elaboration Target States

Opportunity Specified System
Conceived

Implemented System
Approach Selected Approach Confirmed Interfaces Stable Integrated Production Quality Release Available Released

Executable System
Assembled Approach Validated Functionality Validated Ready to Deploy

Lifecycle Patterns

Opportunity Identified Problem Understood Value Established Viability Established Problem Addressed Benefit Accrued

Shared

Stable

Correct

Testable

Accepted

Fulfilled

Operational

Team

Backlog

Project

Way of Working

Set Up Mission Defined Driving Work Formed Change Under Control Focused Quality Goals Met Collaborating Sufficient Work Completed Outstanding Items Handed Over

Underway Gaps Analyzed Milestones Agreed Options Explored Risks Under Control Development Complete Responsibilities Handed Over Closed Essentials In Place Embedded

Key
Essential

Recommended

Disbanded

Handed Over

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

46

Construction Target States

Opportunity Specified System
Conceived

Implemented System
Approach Selected Approach Confirmed Interfaces Stable Integrated Production Quality Release Available Released

Executable System
Assembled Approach Validated Functionality Validated Ready to Deploy

Lifecycle Patterns

Opportunity Identified Problem Understood Value Established Viability Established Problem Addressed Benefit Accrued

Shared

Stable

Correct

Testable

Accepted

Fulfilled

Operational

Team

Backlog

Project

Way of Working

Set Up Mission Defined Driving Work Formed Change Under Control Focused Quality Goals Met Collaborating Sufficient Work Completed Outstanding Items Handed Over

Underway Gaps Analyzed Milestones Agreed Options Explored Risks Under Control Development Complete Responsibilities Handed Over Closed Essentials In Place Embedded

Key
Essential

Recommended

Disbanded

Handed Over

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

47

Transition Target States

Opportunity Specified System
Conceived

Implemented System
Approach Selected Approach Confirmed Interfaces Stable Integrated Production Quality Release Available Released

Executable System
Assembled Approach Validated Functionality Validated Ready to Deploy

Lifecycle Patterns

Opportunity Identified Problem Understood Value Established Viability Established Problem Addressed Benefit Accrued

Shared

Stable

Correct

Testable

Accepted

Fulfilled

Operational

Team

Backlog

Project

Way of Working

Set Up Mission Defined Driving Work Formed Change Under Control Focused Quality Goals Met Collaborating Sufficient Work Completed Outstanding Items Handed Over

Underway Gaps Analyzed Milestones Agreed Options Explored Risks Under Control Development Complete Responsibilities Handed Over Closed Essentials In Place Embedded

Key
Essential

Recommended

Disbanded

Handed Over

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

48

Using alpha states to monitor progress and health

Lifecycle Patterns

Actual State

Planned State

Opportunity

Specified System

Implemented System

Executable System

Team

Backlog

Project

Way of Working

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

49

Let us start where we always started

Use a Practice in a Project

[Development Game]

Use the Process Cards to Plan the Project

Current Situation and Opportunity [Planning Game]

Good Software

Select Practices and Assemble a Process

[Process Improvement Game]

Assemble a lightweight process

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

50

Play your cards to assemble your process What are you going to produce (artifacts) What skills do you need? What are you going to do (activities)? What do you do already?

Add

You need a Game Board

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

Finish here
51

The Game Board is a Start

Finish here Start here

Game Board

In more detail ... The Game Board is initially a process independent Kernel

C om pe te nc ie s

uc

Start here

Practice Practice Practice Practice

Game Board

od

Pr

Th in gs

@ Key Generic Artifacts

2005 Ivar Jacobson International

@ Key Generic Activities

52

Essential Unified Process Primer / 01 - Essential Principles and Practices

Th in gs

to

to

Populate it with your existing process.

Describe your own practices using the game board ...

People, Processes, Current Practices Your Process

Align

Game Board

...and write your own cards, add them to the game board Then select which Essential Practices to use and add to the game board
2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

Understand the Need

Ensure Stakeholder Satisfaction

Accept the System

Establish Project

Steer Project

Support Team

Conclude Project

Specify the System

Shape the System

Implement Software

Test the System

Release the System

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

Finish here
53 54

Start here

Understand the Need

Ensure Stakeholder Satisfaction

Accept the System

Establish Project

Steer Project

Support Team

Conclude Project

Specify the System

Shape the System

Implement Software

Test the System

Release the System

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

55

Let us now do something we didnt do before?

Use a Practice in a Project

[Development Game]

Use the Process to Plan the Project

Current Situation and Opportunity [Planning Game]

Good Software

Select Practices and Assemble a Process

[Process Improvement Game]

Apply a practice to help your team.

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

56

Use cards and gameboard to introduce a practice (eg. use case essentials)
Specified System
Conceived Shared Stable Correct Implemented Fulfilled

Start

Evolution of top alphas control the game

Scoped

Use-Case Modules

Specification Agreed
Specified System

Use-Case Module
Realized

Scoped
Use-case modules may be split into parts to allows groups of flows to be progressed at different rates

A use-case module is a cross-cutting view of a use case across the specified, implemented and executable systems. Use-case modules: Integrate the different system views provided by use-case driven development Enable consolidated status tracking of the use-case specification, realization and test cases included in the module

Specification Agreed Realized

Implemented

Evolution of subalphas control the moves of the game

Verified

Implemented
Described by: 1 Use-Case Specification 0..n Supplementary Requirements 1 Use-Case Realization 1..n Test Cases
revision 35

Verified

Essential Unified Process

Ivar Jacobson International, 2006

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

57

Development Game Dynamics

1. Define the goal of the game (or round)
Plan evolution of top alphas (major control elements) in terms of state progression. Select high-priority work items from Backlog (tasks, defects, changes), include these in the planning of the next move Define desired end states of sub-alphas (sub-ordinate control elements) Decide which activities to perform as part of the move Deal the relevant cards to team members Execute the activities in the appropriate environment Annotate cards and update the game board based on the outcome How did we score?

2. Examine the Backlog (consider current project situation)

3. Plan a move

4. Perform the tasks

5. Assess the results of the move

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

58

1. Define the goal of the game / round

Specified System
Conceived Shared Stable Correct Implemented Fulfilled

Where are we?

Start

Scoped

We need to get the specified system from conceived to shared.

Use-Case Modules

Specification Agreed

Realized

Explained in the guideline

Implemented

Verified

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

59

2. Examine Backlog
Backlog

In Play

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

60

2. Examine Backlog
Backlog

In Play

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

61

3. Plan the move find the activities

Specified System
Conceived Shared Stable Correct Implemented Fulfilled

Understand the need

Specify the System Find actors & use cases

Analyst

Start

Specify the System Select and prioritize use cases

Use-Case Modules

Specify usecase module

Analyst

- Find Actors and Use-Cases

Consult the state-activity table, or the practice workflow

Specification Agreed

Specify the System

- Select and Prioritize Use Cases

Which activities do we need to perform to get Scoped the specified system from conceived to shared?

Project Lead

Shape the System Identify Tests

Tester

Specifiy the System

Shape the System Realize use case

Test the System Build Test

Tester

Realized

Developer

Implement Software

Implemented

Test the System Execute Test

Tester

Verified

Specified System - Conceived - Shared

2005 Ivar Jacobson International

Release the System

D
62

Essential Unified Process Primer / 01 - Essential Principles and Practices

3. Plan the move define the work items

Specified System
Conceived Shared Stable Correct Implemented Fulfilled

Start

Scoped

Use-Case Modules

Specification Agreed

Realized

Implemented

Select an approach, create tasks and allocate resources

Verified

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

63

4. Perform the tasks

1 Collect the cards that provide the guidance needed to perform the task 2 Distribute work to the team by building hands of cards

UC Team A

Team performs the work in the most appropriate environment

Artifacts are produced and instance cards describe the findings

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

64

5. Assess the results

Instance cards represent the outcome of the work. The gameboard is updated accordingly.

Specified System
Conceived Shared Stable Correct Implemented Fulfilled

Use-Case Modules

e lw sfu scope es Start ucc and t em as s ases ed Sys w op usec ecifi h p e rk s Wo d som Thus S ARED H un ed. S Scoped fo s to gre is a resse g pr o
Specification Agreed

2 1 3

Realized

Implemented

Verified

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

65

Whats the next move?

Specified System
Conceived Shared Stable Correct Implemented Fulfilled

Understand the need

Specify the System Find actors & use cases

Analyst

Start

2 1 3

Specify the System Select and prioritize use cases

Project Lead

Scoped

Use-Case Modules

Specify the System Specify usecase module

Specification Agreed
Analyst

Shape the System Identify Tests

Tester

Shape the System Realize use case

Developer

Test the System Build Test

Tester

Realized

Scope all the use-case modules?

Implemented

Implement Software

Test the System

Verified

Execute Test
Tester

Release the System

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

66

Whats the next move?

Specified System
Conceived Shared Stable Correct Implemented Fulfilled

Understand the need

Specify the System Find actors & use cases

Analyst

Start

2 1 3

Specify the System Select and prioritize use cases

Project Lead

Scoped

Use-Case Modules

Specify the System

Shape the System Identify Tests

Tester

Specification Agreed

Or spike one use-case?

Specify usecase module

Analyst

Shape the System Realize use case

Developer

Test the System Build Test

Tester

Realized

Implement Software
Implemented

Test the System

Verified

Execute Test
Tester

Release the System

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

67

Agenda A new paradigm with several exciting innovations Practice separation

Essential UML

Practice user experience using the card metaphor

Essential UML

Developing software by playing games Final words

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

68

How it all fits together

Game Board

Finish here

Start here

References
Practices

Cards

Guidelines

Knowledge Base

Smart Practices
2005 Ivar Jacobson International

Agents and tools

Essential Unified Process Primer / 01 - Essential Principles and Practices

69

In a Nutshell...today:

You can have a platform independent process You can get Eight Essential practicesmore to come You can use Smart practices Capture and publish your own best practices Use the new paradigm
Cards and games bring the process to life Play all three process games

Re-focus process on to developer, not the process engineer

JACZONE

WayPointer

...the Next Generation Process is here today

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

70

EssUP Product Release Sign up for updates on EssUP and free product releases at
www.ivarjacobson.com

2005 Ivar Jacobson International

Essential Unified Process Primer / 01 - Essential Principles and Practices

71