astrogrid oversight committee mrc, london 30 july, 2002
TRANSCRIPT
AstroGrid Oversight Committee
MRC, London30 July, 2002
30.07.2002 AstroGrid Oversight Committee
AstroGrid and the Unified Software Development Process
30.07.2002 AstroGrid Oversight Committee
Options
Work Package Traditional Grand design Integrate at end
Unified Process ‘Agile’ process Iterative Multiple releases
30.07.2002 AstroGrid Oversight Committee
Work Package approach: Pros
Institute ‘ownership’Component supportEasier to focus on R&D
30.07.2002 AstroGrid Oversight Committee
Work Package approach: Cons
Development out of sequenceMid-term integration/release difficult User does not see whole product until
end
Development not risk-basedLess knowledge spreadDifficult to change direction Or to see the need for a change
~50% more resources needed
30.07.2002 AstroGrid Oversight Committee
Unified ProcessArchitecture-centricUse-case drivenIterative
30.07.2002 AstroGrid Oversight Committee
Overview
30.07.2002 AstroGrid Oversight Committee
Iterative
~3 month iterationsFull life-cycle each iteration Inception planning Elaboration design Construction code Transition release
Working product release each iteration
30.07.2002 AstroGrid Oversight Committee
Unified Process: Pros
Iterations Multiple releasesKnowledge spreadWhole-project ‘ownership’Easier to change direction Critical for leading-edge project
‘Right’ software built Right
30.07.2002 AstroGrid Oversight Committee
Unified Process: Cons
Where is support?More management effort owing to distributed project
Difficult to set targets up front Targets reviewed each iteration
30.07.2002 AstroGrid Oversight Committee
AstroGrid
AGLI commitment to Unified ProcessConsortium buy-inFocus on delivery of VO
30.07.2002 AstroGrid Oversight Committee
AstroGrid Personnel
Technical Lead focus on delivery
Project Manager focus on team building, R&D,
interactions
Developers flexible team deployment mixed development and R&D work