GCS component development cycle

Rodríguez, J. A.; Macias, Rosa; Molgo, Jordi; Guerra, Dailos; Pi, Marti
Referencia bibliográfica

Software and Cyberinfrastructure for Astronomy II. Proceedings of the SPIE, Volume 8451, id. 84512Q-84512Q-12 (2012).

Fecha de publicación:
9
2012
Número de autores
5
Número de autores del IAC
5
Número de citas
1
Número de citas referidas
0
Descripción
The GTC1 is an optical-infrared 10-meter segmented mirror telescope at the ORM observatory in Canary Islands (Spain). First light was at 13/07/2007 and since them it is in the operation phase. The GTC control system (GCS) is a distributed object & component oriented system based on RT-CORBA8 and it is responsible for the management and operation of the telescope, including its instrumentation. GCS has used the Rational Unified process (RUP9) in its development. RUP is an iterative software development process framework. After analysing (use cases) and designing (UML10) any of GCS subsystems, an initial component description of its interface is obtained and from that information a component specification is written. In order to improve the code productivity, GCS has adopted the code generation to transform this component specification into the skeleton of component classes based on a software framework, called Device Component Framework. Using the GCS development tools, based on javadoc and gcc, in only one step, the component is generated, compiled and deployed to be tested for the first time through our GUI inspector. The main advantages of this approach are the following: It reduces the learning curve of new developers and the development error rate, allows a systematic use of design patterns in the development and software reuse, speeds up the deliverables of the software product and massively increase the timescale, design consistency and design quality, and eliminates the future refactoring process required for the code.