OPS Forum Configuration and Change Management for Ground Segments 17.11.2006

SDE at ESA

INDEX

Introduction

Software Development Environment (SDE) Approach

Software Development Environment

Requirements Management (SDE-RM)

Development Management (SDE-DM)

Validation Management (SDE-VM)

Configuration and Change Management (SDE-CCM)

SDE-CM Project and Phases

Telelogic Synergy/Change Synergy/CM

Configuration and Change Management Architecture

Conclusion

SDE Lessons Learned

SDE General Issues

The Software Development Environment Approach

By January 2003, the Division set the strategic objective of standardising the software development and the maintenance practices used by the Department and its Contractors.

Standardise the tools and methodologies to increase the quality and homogeneity of software.

Improve overall efficiency of the processes.

Reduction of costs and risks.

Reusability of the software (Infrastructure and Missions).

Improvement of the services provided by the Divisions.

Additionally, the Software Development Environment had to

Comply with internal Quality Management .

Adhere to ITIL best practices.

All the areas of the Software Development life cycle are addressed

Several new and existent tools involved in each of the areas

INTRODUCTION

The situation starting in Q1/2003 to Q4/2006 …

ECLIPSE REQUIREMENTS MANAGEMENT IBM/Rational Requisite Pro? Telelogic Doors? Microsoft Word (track changes) CONFIGURATION MANAGEMENT CVS Visual SourceSafe CMS CHANGE MANAGEMENT eLog /Access MWeb ARTS Excel IBM/Rational Clearcase/ClearQuest ? Telelogic Synergy/Change/CM ? CVS/Bugzilla ? VALIDATION MANAGEMENT TESTING JUnit Custom Automatic Testing Mercury Quality Center Salome TMF QaTraq SVVP/Access CODE INSPECTION QUALITY METRICS Telelogic Logiscope IBM/Rational Purify/PurifyPlus IBM/Rational Quantify Parasoft Insure for C++ Software Quality and Coding Rules TNs Access DEVELOPMENT MANAGEMENT UML 1.1 Model Driven Architecture UML 2.0 XML XMI 2.1 Enterprise Architect ? MagicDraw Telelogic TAU ? IBM/Rational Rose Microsoft Visual Studio

INTRODUCTION

The different areas correspond to specific projects and sub-projects of the Software Development Environment.

INTRODUCTION

SDE Main Components Architecture, tools and interfaces

INDEX (Cont.)

Introduction

Configuration and Change Management (SDE-CM)

Conclusion

SDE Lessons Learned

SDE General Issues

Concept: central management of Infrastructure & Missions requirements

Each new Mission Data System is developed based on the infrastructure software produced by the infrastructure division.

The software engineering life cycle is based on a “delta” approach, where the missing functionality (the “delta”) is built on top of the infrastructure and based on a set of modified and new requirements.

Reuse of Mission requirements by Infrastructure

Management of commonality between Missions ( Mission family e.g. ROS/MEX/VEX)

Tool used: Telelogic DOORS and OPS-GD Renato project

Telelogic DOORS will be extended to interface other SDE tools

SDE Configuration & Change Management (CCM - Telelogic Synergy)

SDE Validation Management (VM – Tool TBD)

SDE Development Management (DM – Enterprise Architect)

REQUIREMENTS MANAGEMENT (SDE-RM)

Requirement Management tool (DOORS)

REQUIREMENTS MANAGEMENT (SDE-RM)

(Image taken from OPS-GD RENATO)

Concept: evolution toward a Model-Driven Architecture approach

The arrival of UML impacted on the way software is built.

The software development is slowly moving from code-centered to a model-centered (MDA) approach.

MDA is likely to become the norm in the medium term, but an early adoption in full scale of a specific tool is not advised

OPS-GI run several activities to explore MDA and to identify benefits of adopting the technology. A number of problems were identified:

Tool incompatibility: main reason is the standard (XML Metadata Interchange, XMI) that serializes the UML models so that they can be stored and retrieved.

Runtime environment dependency,

Lack of tool consolidation and quick evolution of the market.

Tool used: Enterprise Architect

Enterprise Architect tool complies with XMI standards, disposes of code generation capabilities (and it is reasonably priced).

MagicDraw is used for the projects requiring XMI 2.1

The models cover the static description of classes and some activity diagrams to show the data flow.

DEVELOPMENT MANAGEMENT (SDE-DM)

The Development Management tool (Enterprise Architect)

DEVELOPMENT MANAGEMENT (SDE-DM)

Concept: Management of system tests and selection of the most suitable tool to be used as part of the SDE

The deployment of the existing SCOS-2000 test plans (along with all the associated test data like configuration files and test scripts), which implies well built import capabilities from the proper file formats.

The traceability between test cases and software requirements.

The coverage of requirements by the test plans.

The generation of statistical reports.

The production of the necessary test documentation.

The management of users and access rights to the test chain .

Tool used:

3 pre-selected tools: Mercury Quality Center, Salome TMF open source, and QaTraq open source.

Activity was started in September 2006

VALIDATION MANAGEMENT (SDE-VM)

INDEX (Cont.)

Introduction

Conclusion

SDE Lessons Learned

SDE General Issues

Concept: centralised, integrated and process driven Configuration and Change Management System

An integrated tool for Change and Configuration management

Consolidation of multitude set of tools in OPS-GI (eLog, M-Web, MS Access, CVS, etc.)

Centralised tool accessible from both ESA and Contractors premises

Improved practices: processes, lifecycles and procedures

Tool used: CM Synergy Suite from Telelogic

Project Approach in four phases

Strategy Definition

Tools Evaluation & Selection

Implementation

Deployment

CONFIGURATION AND CHANGE MANAGEMENT (SDE-CCM)

Phase I: Strategy Definition (Q3/2003) - Completed

To define the project scope and to identify the stakeholders.

To get the management commitment

Phase II: Tools Evaluation & Selection (Q2/2004) - Completed

Configuration & Change Management requirements gathering

Requirements organized in 14 dimensions and sub-dimensions

Tools market screening: 18 tools considered and 3 preferred tools evaluated against the requirements

IBM ClearCase/ClearQuest

Telelogic Synergy Suite (Synergy/Change and Synergy/CM)

CVS/Bugzilla

Evaluation based on:

OVUM and YPHISE reports on Configuration and Change Mgt

Requirements gathering interviews

Development of 3 prototypes evaluated during workshops

Phase III: Implementation (Q3/2005) - Completed

Customize the selected tool to fulfill the requirements

First deployment in a reduced number of projects, including training

Review of the performance and adjustment of the system

Phase IV: Deployment (Q3/2006) – On-going

Architecture consolidation according to network evolution (new DMZ)

Complete integration between Synergy/CM and Synergy/Change to extend the benefits of a task-based SDE CCM

Interfacing to other SDE tools (e.g. eLOG, Assyst, DOORS and rest of available SDE tools)

Elaboration of CCM procedures applicable to ESA and Contractors

Deployment on all OPS-GI projects including data migration

Telelogic Synergy Suite

Telelogic Synergy / Change

A process and lifecycle web-based application

Change Management for distributed teams

User-friendly and intuitive change request interface

Tailorable workflow

Telelogic Synergy / Configuration Management

A task-based client-server application

Supports parallel and distributed development (i.e. ESA, Industry and all our interconnected projects)

Advanced release management

SDE-CM Architecture

Hardware: 2 servers, one in Relay LAN and one in Dev LAN

Single CPU (front server) and dual CPU (back server) Linux servers.

Compliant with ESA Network Security Policy

SDE-CCM ARCHITECTURE

SDE-CM tool for Change Mgt (Telelogic Synergy/Change)

SDE-CM tool for Configuration Mgt (Telelogic Synergy/CM)

INDEX (Cont.)

Introduction

Conclusion

SDE Lessons Learned

SDE General Issues

SDE-CCM LESSONS LEARNED

Network security heavily constrained architectural options

Remote access imposed 2-servers architecture located in Relay-LAN (Change Management) and Dev LAN (Configuration Management)

CM Synergy was not design for such architecture which implies a lot of customisation

Absence of DMZ at ESOC and OPS-EC difficulties to set-up it

Processes and lifecycle review are essential

Time consuming. Several meetings, presentations and workshops at different levels (technical, management, interdivisional)

SDE CCM Phase II extended for more than 12 months, due to workload, difficulties with Contractor, prototypes development, several agreements.

Independent (external) consultancy companies should be involved

Management commitment and Users buy-in are critical success factor

The team in charge of each SDE must have a strong background in the implementation and deploying of the different SDE tools.

Experienced in processes review and improvements

Proactive behavior and execution on each SDE area

SDE GENERAL ISSUES

Significant effort will be dedicated to the tools integration

Technically this involves the interfaces, data exchange, database compatibility and others

Process management regarding who must use which tool in what moment

Issues related to the user management at different levels

Each tool disposes of its own user management mechanism and associated data (e.g. SDE-CM)

Problems to interface the user management data between the tools and to the standard ESA user management

The teams involved in the software development and maintenance have to commit to the new processes and tools.

Resistance from the user. The team must quickly obtain benefits compared with their previous tools: easy-of-use, efficiency of the processes, overall performance.

Unavailability of functionalities. No functionality (even minor features) of the old tools must be lost.

SDE SCHEDULE OVERVIEW (Tentative)

SDE started by Q1/2003, expanding through the different areas…

CONFIGURATION CHANGE MANAGEMENT REQUIREMENTS MANAGEMENT DEVELOPMENT MANAGEMENT CODE INSPECTION QUALITY METRICS VALIDATION MANAGEMENT TESTING 2003 2004 2005 2006 2007 2008 DOORS (RENATO) DOORS DEPLOYMENT 2009 PHASE I PHASE II PHASE III PHASE IV PHASE I PHASE II 2010 2011 PHASE I PHASE II PHASE I PHASE II