Software Integration and Test Techniques in a Large Distributed Project: Evolution, Process Improvement, Results Paola Sivera - ESO

ICALEPCS 2007, Oct 2007, Knoxville TN2 Center of Array Pampa La Bola V. Licancabur Cº Chajnantor Chajnantor Plateau – looking north

ICALEPCS 2007, Oct 2007, Knoxville TN3 Antenna Prototypes at ALMA Test Facility: 2005

ICALEPCS 2007, Oct 2007, Knoxville TN4 ALMA Geographical distribution ALMA DRAO Penticton ALMA ATF Arcetri Observatory Jodrell Bank Brera Observatory IRAM Grenoble ATC Edinburgh NAOJ ESO NRAO Obs de Paris Univ. Calgary c c Santiago MPI Bonn DAMIR/IEM Madrid

ICALEPCS 2007, Oct 2007, Knoxville TN5 ALMA Management B. Glendenning G. Raffi K.Tatematsu Science Software Requirements R. Lucas High Level Analysis J. Schwarz Software Eng M.Zamparelli Common SW G. Chiozzi Executive P. Grosbol Control A. Farris Archiving A. Wicenec Observation Preparation A. Bridger Operations Support M. Chavan Offline J. McMullen Pipeline L. Davis Telescope Calibration R. Lucas Correlator J. Pisano Integration P. Sivera Scheduler A.Farris ACA M.Watanabe Trilateral Computing IPT Organisation Total Bilateral staff now: 40 FTEs Total trilateral staff now: 65 FTEs Total Bilateral staff now: 40 FTEs Total trilateral staff now: 65 FTEs

ICALEPCS 2007, Oct 2007, Knoxville TN6

7

8 ALMA System Dataflow

ICALEPCS 2007, Oct 2007, Knoxville TN9 ObsPrep Visual Editor (to select spectral setup)

ICALEPCS 2007, Oct 2007, Knoxville TN10 EXEC: Operator Master Client

ICALEPCS 2007, Oct 2007, Knoxville TN11 CASA Viewer Visibility displays (raw, corrected data) Image, data cube displays –Statistics; profiles; raster, contour, vector support

ICALEPCS 2007, Oct 2007, Knoxville TN12 Standards and Tools Alma Common Software Environment CVS organization Makefile Standard Test Environment (STE) Tool for automated testing Bug tracking tool (JIRA)

ICALEPCS 2007, Oct 2007, Knoxville TN13 ALMA Release Cycle Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Minor Release: Mar 31Major Release: Sep 30 Monthly integration = last day of the month ICD Freeze = 15 th of the month

ICALEPCS 2007, Oct 2007, Knoxville TN14 Lessons learned Releases twice per year but… Subsystem developers working in isolation Results thrown over the wall to ITS at release time –Each integration took ~2 months –At completion of integration code was already obsolete

ICALEPCS 2007, Oct 2007, Knoxville TN15 Function-based Teams

ICALEPCS 2007, Oct 2007, Knoxville TN16 FBTs organization ZSharedSimulator B (branch) SharedSimulator RootOfBranch (tag of the HEAD) ASharedSimulator BeforeMerge BTRUNK-SharedSimulator BeforeMerge CTRUNK-SharedSimulator AfterMerge (tag of the HEAD) SharedSimulator AfterMerge-B (branch) F SharedSimulator FINAL

ICALEPCS 2007, Oct 2007, Knoxville TN17 Summing it up FBTs advantages: –Improve communication –More effective involvement of testers Testing end-to-end since the beginning –Good for object-oriented software –A lot of maintenance on the test cases –It is not enough -> user tests

ICALEPCS 2007, Oct 2007, Knoxville TN18 Where we are Testing maturity (according to Boris Beizer) 1.there is no difference between testing and debugging: often during FBTs’ work 2.the purpose of testing is to show that the software works: at FBTs validation 3.the purpose of testing is to show that the software does not work: release validation 4.the purpose of testing is not to prove anything, but to reduce the perceived risk of not working to an acceptable value: release validation

ICALEPCS 2007, Oct 2007, Knoxville TN19 Future developments Make software more testable from its inception adoption of the test maturity model (TMM) … the list can be very long … For the near future we want to focus on: Stability tests More automation

ICALEPCS 2007, Oct 2007, Knoxville TN20 AOS Technical Building

ICALEPCS 2007, Oct 2007, Knoxville TN21 ALMA

ICALEPCS 2007, Oct 2007, Knoxville TN22

ICALEPCS 2007, Oct 2007, Knoxville TN23 MELCO : August 2007