230 likes | 471 Vues
Software Integration and Test Techniques in a Large Distributed Project: Evolution, Process Improvement, Results. Paola Sivera - ESO. Chajnantor Plateau – looking north. V. Licancabur. Cº Chajnantor. Pampa La Bola. Center of Array. Antenna Prototypes at ALMA Test Facility: 2005.
E N D
Software Integration and Test Techniques in a Large Distributed Project: Evolution, Process Improvement, Results Paola Sivera - ESO
Chajnantor Plateau – looking north V. Licancabur Cº Chajnantor Pampa La Bola Center of Array ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN
Antenna Prototypes at ALMA Test Facility: 2005 ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN
ALMA Geographical distribution MPI Bonn ATC Jodrell Bank Edinburgh Univ. Calgary DRAO c Penticton ESO c ALMA ATF DAMIR/IEM Madrid NAOJ NRAO ALMA Santiago Arcetri Brera IRAM Observatory Obs de Observatory Grenoble Paris ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN
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, 15-19 Oct 2007, Knoxville TN
ALMA System Dataflow ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN
ObsPrep Visual Editor (to select spectral setup) ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN
EXEC: Operator Master Client ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN
CASA Viewer • Visibility displays (raw, corrected data) • Image, data cube displays • Statistics; profiles; raster, contour, vector support ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN
Standards and Tools • Alma Common Software • Environment • CVS organization • Makefile • Standard Test Environment (STE) • Tool for automated testing • Bug tracking tool (JIRA) ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN
ALMA Release Cycle ICD Freeze = 15th of the month Monthly integration = last day of the month Minor Release: Mar 31 Major Release: Sep 30 • • • • • • • • • • • • Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN
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, 15-19 Oct 2007, Knoxville TN
Function-based Teams ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN
FBTs organization ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN
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, 15-19 Oct 2007, Knoxville TN
Where we are Testing maturity (according to Boris Beizer) • there is no difference between testing and debugging: often during FBTs’ work • the purpose of testing is to show that the software works: at FBTs validation • the purpose of testing is to show that the software does not work: release validation • 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, 15-19 Oct 2007, Knoxville TN
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, 15-19 Oct 2007, Knoxville TN
AOS Technical Building AOS Technical Building ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN
ALMA - 2012 ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN
MELCO : August 2007 ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN