1 / 18

Unified Process for e-Science (UPeSC)

Unified Process for e-Science (UPeSC). NeSC 12-13 December 2002. USDP History. 1967: Ericsson: components 1987: Jacobson: Objectory Process 1995: Unified Method 1996: Rational Objectory Process 1997: Three Amigos  Unified Modeling Language

lesley-crawford
Download Presentation

Unified Process for e-Science (UPeSC)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. USDP History • 1967: Ericsson: components • 1987: Jacobson: Objectory Process • 1995: Unified Method • 1996: Rational Objectory Process • 1997: Three Amigos Unified Modeling Language • 1998: Rational Unified Processand still going… e-Science Project Managers Forum

  3. Core features • Use-Case Driven • Architecture-Centric • Iterative and Incremental • Organisation: Phases & Workflows e-Science Project Managers Forum

  4. Use-Case Driven • Capture functional requirements • ‘gives a user a result of value’ • Drives development process • Design • Build • Test e-Science Project Managers Forum

  5. Architecture-Centric • ‘common vision’ • Most important model elements • Different views  Architectural baseline (‘small skinny system’) e-Science Project Managers Forum

  6. Iterative and Incremental • Iterations: ‘mini-projects’ • Use-case selection: • Most important risks • Incremental development e-Science Project Managers Forum

  7. Extensions • RUP: Rational Unified Process • EUP: Enterprise Unified Process • UPeSC: Unified Process for e-Science e-Science Project Managers Forum

  8. RUP • New workflows: • Business modeling • Deployment • Config & Change Mgt • Project Mgt • Environment e-Science Project Managers Forum

  9. EUP • RUP + workflows: • Ops & Support • Enterprise Mgt • RUP + phases: • Production • Retirement e-Science Project Managers Forum

  10. UPeSC Evolution(by accident, not design) • Use-cases • Science problems • Sequence diagrams • Domain model • Use-cases • … e-Science Project Managers Forum

  11. Science Problems • Focus on problems to be solved • What is difficult? • What takes too long? • What is exciting? •  e-Science Project Managers Forum

  12. Sequence diagrams e-Science Project Managers Forum

  13. Domain model e-Science Project Managers Forum

  14. Hindsight • Start with Science • Work packages contra UP spirit • Many concerns vs ONE • Domain model not especially useful e-Science Project Managers Forum

  15. What is/was missing? • Hire Software Architect *from (before) start* •  VISION • Case studies in UP for e-Science/academic projects • Iterative planning process • Metrics • milestones/deliverables setting • Methods of collaborative working(in distributed team) e-Science Project Managers Forum

  16. 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 e-Science Project Managers Forum

  17. Next steps • Write-up AstroGrid as case study • Investigate planning approaches • (system dynamics approach?) • Better marriage of work package structure & single deliverable • Develop/promote believable metrics e-Science Project Managers Forum

  18. References • http://www.rational.com/products/rup/ • http://www.therationaledge.com • http://www.ambysoft.com/ • http://www.ronin-intl.com/publications/unifiedProcess.html e-Science Project Managers Forum

More Related