software integration and test techniques in a large distributed project: evolution, process...
TRANSCRIPT
Software Integration and Test Software Integration and Test Techniques in a Large Techniques in a Large Distributed Project: Distributed Project: Evolution, Process Evolution, Process
Improvement, ResultsImprovement, Results
Paola Sivera - ESO
ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN 2
ALMA Geographical distribution
ALMA
DRAOPenticton
ALMAATF
ArcetriObservatory
Jodrell Bank
BreraObservatory
IRAMGrenoble
ATCEdinburgh
NAOJ
ESO
NRAO
Obs deParis
Univ.Calgary
c
c
Santiago
MPI Bonn
DAMIR/IEMMadrid
ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN 3
ALMAManagement
B. GlendenningG. Raffi
K.Tatematsu
Science Software Requirements
R. Lucas
High Level Analysis
J. Schwarz
Software EngM.Zamparelli
Common SWG. Chiozzi
ExecutiveP. Grosbol
ControlA. Farris
ArchivingA. Wicenec
Observation Preparation
A. Bridger
Operations Support
M. Chavan
OfflineJ. McMullen
PipelineL. Davis
Telescope Calibration
R. Lucas
CorrelatorJ. Pisano
IntegrationP. Sivera
SchedulerA.Farris
ACAM.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, 15-19 Oct 2007, Knoxville TN 4
ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN 5
ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN 6
ALMA System Dataflow
ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN 7
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 8
ALMA Release Cycle
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Minor Release: Mar 31 Major Release: Sep 30
• • • • • • • • • • • •
Monthly integration = last day of the month
ICD Freeze = 15th of the month
ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN 9
Function-based Teams
ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN 10
FBTs organization
Z SharedSimulator-2006-02-B (branch) SharedSimulator-2006-02-RootOfBranch (tag of the HEAD)
A SharedSimulator-2006-02-BeforeMerge
B TRUNK-SharedSimulator-2006-02-BeforeMerge
C TRUNK-SharedSimulator-2006-02-AfterMerge (tag of the HEAD)
SharedSimulator-2006-02-AfterMerge-B (branch)
F SharedSimulator-2006-02-FINAL
ICALEPCS 2007, 15-19 Oct 2007, Knoxville TN 11
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 12
Where we are
Testing maturity (according to Boris Beizer)
1. there is no difference between testing and debugging 2. the purpose of testing is to show that the software works 3. the purpose of testing is to show that the software does
not work 4. 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 13
Future developments
• Make software more testable from its inception • adoption of the test maturity model (TMM)