130 likes | 291 Views
Software Integration and Test Techniques in a Large Distributed Project: Evolution, Process Improvement, Results. Paola Sivera - ESO. ALMA Geographical distribution. MPI Bonn. ATC. Jodrell Bank. Edinburgh. Univ. Calgary. DRAO. c. Penticton. ESO. c. ALMA. ATF. DAMIR/IEM Madrid.
E N D
Software Integration and Test Techniques in a Large Distributed Project: Evolution, Process Improvement, Results Paola Sivera - ESO
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
Standards and Tools • Alma Common Software • Environment • CVS organization • Makefile • Standard Test Environment • 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
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 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 • the purpose of testing is to show that the software works • the purpose of testing is to show that the software does not work • the purpose of testing is not to prove anything, but to reduce the perceived risk of not working to an acceptable value ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN
Future developments • Make software more testable from its inception • adoption of the test maturity model (TMM) ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN