AstroGrid Oversight Committee MRC, London 30 July, 2002

AstroGrid Oversight Committee AstroGrid and the Unified Software Development Process

AstroGrid Oversight Committee Options Work Package Traditional Grand design Integrate at end Unified Process ‘Agile’ process Iterative Multiple releases

AstroGrid Oversight Committee Work Package approach: Pros Institute ‘ownership’ Component support Easier to focus on R&D

AstroGrid Oversight Committee Work Package approach: Cons Development out of sequence Mid-term integration/release difficult User does not see whole product until end Development not risk-based Less knowledge spread Difficult to change direction Or to see the need for a change ~50% more resources needed

AstroGrid Oversight Committee Unified Process Architecture-centric Use-case driven Iterative

AstroGrid Oversight Committee Overview

AstroGrid Oversight Committee Iterative ~3 month iterations Full life-cycle each iteration Inceptionplanning Elaborationdesign Constructioncode Transitionrelease Working product release each iteration

AstroGrid Oversight Committee Unified Process: Pros Iterations  Multiple releases Knowledge spread Whole-project ‘ownership’ Easier to change direction Critical for leading-edge project ‘Right’ software built Right

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

AstroGrid Oversight Committee AstroGrid AGLI commitment to Unified Process Consortium buy-in Focus on delivery of VO

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