Progress on standardization and automation in software development on W7X

• Published in: Fusion engineering and design 2012-12, Vol.87 (12), p.2232-2237
• Main Authors: Kühner, Georg, Bluhm, Torsten, Heimann, Peter, Hennig, Christine, Kroiss, Hugo, Krom, Jon, Laqua, Heike, Lewerentz, Marc, Maier, Josef, Schacht, Jörg, Spring, Anett, Werner, Andreas, Zilker, Manfred
• Format: Article
• Language: English
• Subjects: Automation; Guidelines; ISO/IEC 15504; Product life cycle; Quality management; Quality standards; Software development; Standardization; W7-X
• ISSN: 0920-3796; 1873-7196
• DOI: 10.1016/j.fusengdes.2012.06.003

► For W7X software development the use of ISO/IEC15504-5 is further extended. ► The standard provides a basis to manage software multi-projects for a large system project. ► Adoption of a scrum-like management allows for quick reaction on priority changes. ► A high degree of software build automation allows for quick responses to user requests. ► It provides additional resources to concentrate work on product quality (ISO/IEC 25000). For a complex experiment like W7X being subject to changes all along its projected lifetime the advantages of a formalized software development method have already been stated [1]. Quality standards like ISO/IEC-12207 provide a guideline for structuring of development work and improving process and product quality. A considerable number of tools has emerged supporting and automating parts of development work. On W7X progress has been made during the last years in exploiting the benefit of automation and management during software development:–Continuous build, integration and automated test of software artefacts.∘Syntax checks and code quality metrics.∘Documentation generation.∘Feedback for developers by temporal statistics.–Versioned repository for build products (libraries, executables).–Separate snapshot and release repositories and automatic deployment.–Semi-automatic provisioning of applications.–Feedback from testers and feature requests by ticket system. This toolset is working efficiently and allows the team to concentrate on development. The activity there is presently focused on increasing the quality of the existing software to become a dependable product. Testing of single functions and qualities must be simplified. So a restructuring is underway which relies more on small, individually testable components with standardized interfaces providing the capability to construct arbitrary function aggregates for dedicated tests of quality attributes as availability, reliability, performance. A further activity is on improving the development cycle. The use of release cycles has already provided favourable concentration of work and predictability of delivery times. However, the demand has risen, to react quickly on priority changes from W7X-project management. So a more agile development cycle is being prepared relying on smaller working packages, shorter release cycles and an associated release plan giving the software development responsible the possibility to react on a shorter time scale.