Unified Process for e-Science (UPeSC) NeSC 12-13 December 2002.
-
Upload
lauren-silva -
Category
Documents
-
view
213 -
download
1
Transcript of Unified Process for e-Science (UPeSC) NeSC 12-13 December 2002.
Unified Process for e-Science(UPeSC)
NeSC12-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…
12-13.12.2002 e-Science Project Managers Forum
Core featuresUse-Case DrivenArchitecture-CentricIterative and IncrementalOrganisation: Phases & Workflows
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
12-13.12.2002 e-Science Project Managers Forum
Architecture-Centric‘common vision’Most important model elementsDifferent views
Architectural baseline (‘small skinny system’)
12-13.12.2002 e-Science Project Managers Forum
Iterative and Incremental
Iterations: ‘mini-projects’Use-case selection: Most important risks
Incremental development
12-13.12.2002 e-Science Project Managers Forum
Extensions
RUP: Rational Unified ProcessEUP: Enterprise Unified ProcessUPeSC: Unified Process for e-Science
12-13.12.2002 e-Science Project Managers Forum
RUPNew workflows: Business modeling Deployment Config & Change Mgt Project Mgt Environment
12-13.12.2002 e-Science Project Managers Forum
EUPRUP + workflows: Ops & Support Enterprise Mgt
RUP + phases: Production Retirement
12-13.12.2002 e-Science Project Managers Forum
UPeSC Evolution(by accident, not design)
Use-casesScience problemsSequence diagramsDomain modelUse-cases…
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?
12-13.12.2002 e-Science Project Managers Forum
Sequence diagrams
12-13.12.2002 e-Science Project Managers Forum
Domain model
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
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)
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
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
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