Please note that eDoc will be permanently shut down in the first quarter of 2021!      Home News About Us Contact Contributors Disclaimer Privacy Policy Help FAQ

Quick Search
My eDoc
Session History
Support Wiki
Direct access to
document ID:

          Institute: MPI für Astronomie     Collection: Publikationen_mpia     Display Documents

ID: 709778.0, MPI für Astronomie / Publikationen_mpia
Practical experience with test-driven development during commissioning of the multi-star AO system ARGOS
Authors:Kulas, M.; Borelli, J. L.; Gässler, W.; Peter, D.; Rabien, S.; Orban de Xivry, G.; Busoni, L.; Bonaglia, M.; Mazzoni, T.; Rahmer, G.
Place of Publication:Bellingham, Wash.
Date of Publication (YYYY-MM-DD):2014
Audience:Not Specified
Abstract / Description:Commissioning time for an instrument at an observatory is precious, especially the night time. Whenever astronomers come up with a software feature request or point out a software defect, the software engineers have the task to find a solution and implement it as fast as possible. In this project phase, the software engineers work under time pressure and stress to deliver a functional instrument control software (ICS). The shortness of development time during commissioning is a constraint for software engineering teams and applies to the ARGOS project as well. The goal of the ARGOS (Advanced Rayleigh guided Ground layer adaptive Optics System) project is the upgrade of the Large Binocular Telescope (LBT) with an adaptive optics (AO) system consisting of six Rayleigh laser guide stars and wavefront sensors. For developing the ICS, we used the technique Test- Driven Development (TDD) whose main rule demands that the programmer writes test code before production code. Thereby, TDD can yield a software system, that grows without defects and eases maintenance. Having applied TDD in a calm and relaxed environment like office and laboratory, the ARGOS team has profited from the benefits of TDD. Before the commissioning, we were worried that the time pressure in that tough project phase would force us to drop TDD because we would spend more time writing test code than it would be worth. Despite this concern at the beginning, we could keep TDD most of the time also in this project phase This report describes the practical application and performance of TDD including its benefits, limitations and problems during the ARGOS commissioning. Furthermore, it covers our experience with pair programming and continuous integration at the telescope.
External Publication Status:published
Document Type:Other
Communicated by:N. N.
Affiliations:MPI für Astronomie
The scope and number of records on eDoc is subject to the collection policies defined by each institute - see "info" button in the collection browse view.