Unified Process for e-Science (UPeSC) NeSC 12-13 December 2002.

18
Unified Process for e- Science (UPeSC) NeSC 12-13 December 2002

Transcript of Unified Process for e-Science (UPeSC) NeSC 12-13 December 2002.

Page 1: Unified Process for e-Science (UPeSC) NeSC 12-13 December 2002.

Unified Process for e-Science(UPeSC)

NeSC12-13 December 2002

Page 2: Unified Process for e-Science (UPeSC) NeSC 12-13 December 2002.

12-13.12.2002 e-Science Project Managers Forum

USDP History1967: Ericsson: components1987: Jacobson: Objectory Process1995: Unified Method1996: Rational Objectory Process1997: Three Amigos Unified Modeling Language1998: Rational Unified Process

and still going…

Page 3: Unified Process for e-Science (UPeSC) NeSC 12-13 December 2002.

12-13.12.2002 e-Science Project Managers Forum

Core featuresUse-Case DrivenArchitecture-CentricIterative and IncrementalOrganisation: Phases & Workflows

Page 4: Unified Process for e-Science (UPeSC) NeSC 12-13 December 2002.

12-13.12.2002 e-Science Project Managers Forum

Use-Case Driven

Capture functional requirements‘gives a user a result of value’Drives development process Design Build Test

Page 5: Unified Process for e-Science (UPeSC) NeSC 12-13 December 2002.

12-13.12.2002 e-Science Project Managers Forum

Architecture-Centric‘common vision’Most important model elementsDifferent views

Architectural baseline (‘small skinny system’)

Page 6: Unified Process for e-Science (UPeSC) NeSC 12-13 December 2002.

12-13.12.2002 e-Science Project Managers Forum

Iterative and Incremental

Iterations: ‘mini-projects’Use-case selection: Most important risks

Incremental development

Page 7: Unified Process for e-Science (UPeSC) NeSC 12-13 December 2002.

12-13.12.2002 e-Science Project Managers Forum

Extensions

RUP: Rational Unified ProcessEUP: Enterprise Unified ProcessUPeSC: Unified Process for e-Science

Page 8: Unified Process for e-Science (UPeSC) NeSC 12-13 December 2002.

12-13.12.2002 e-Science Project Managers Forum

RUPNew workflows: Business modeling Deployment Config & Change Mgt Project Mgt Environment

Page 9: Unified Process for e-Science (UPeSC) NeSC 12-13 December 2002.

12-13.12.2002 e-Science Project Managers Forum

EUPRUP + workflows: Ops & Support Enterprise Mgt

RUP + phases: Production Retirement

Page 10: Unified Process for e-Science (UPeSC) NeSC 12-13 December 2002.

12-13.12.2002 e-Science Project Managers Forum

UPeSC Evolution(by accident, not design)

Use-casesScience problemsSequence diagramsDomain modelUse-cases…

Page 11: Unified Process for e-Science (UPeSC) NeSC 12-13 December 2002.

12-13.12.2002 e-Science Project Managers Forum

Science ProblemsFocus on problems to be solvedWhat is difficult?What takes too long?What is exciting?

Page 12: Unified Process for e-Science (UPeSC) NeSC 12-13 December 2002.

12-13.12.2002 e-Science Project Managers Forum

Sequence diagrams

Page 13: Unified Process for e-Science (UPeSC) NeSC 12-13 December 2002.

12-13.12.2002 e-Science Project Managers Forum

Domain model

Page 14: Unified Process for e-Science (UPeSC) NeSC 12-13 December 2002.

12-13.12.2002 e-Science Project Managers Forum

Hindsight

Start with ScienceWork packages contra UP spirit Many concerns vs ONE

Domain model not especially useful

Page 15: Unified Process for e-Science (UPeSC) NeSC 12-13 December 2002.

12-13.12.2002 e-Science Project Managers Forum

What is/was missing?Hire Software Architect *from (before) start* VISION

Case studies in UP for e-Science/academic projectsIterative planning processMetrics milestones/deliverables setting

Methods of collaborative working(in distributed team)

Page 16: Unified Process for e-Science (UPeSC) NeSC 12-13 December 2002.

12-13.12.2002 e-Science Project Managers Forum

What is good!

Acceptance of UP But still insisting on wp-based metrics

Risk-willing (vs risk-averse)Academics are used to: Incremental development Refactoring

Page 17: Unified Process for e-Science (UPeSC) NeSC 12-13 December 2002.

12-13.12.2002 e-Science Project Managers Forum

Next steps

Write-up AstroGrid as case studyInvestigate planning approaches (system dynamics approach?)

Better marriage of work package structure & single deliverableDevelop/promote believable metrics

Page 18: Unified Process for e-Science (UPeSC) NeSC 12-13 December 2002.

12-13.12.2002 e-Science Project Managers Forum

Referenceshttp://www.rational.com/products/rup/http://www.therationaledge.comhttp://www.ambysoft.com/http://www.ronin-intl.com/publications/unifiedProcess.html