SDE at ESA
INDEX <ul><li>Introduction </li></ul><ul><ul><li>Software Development Environment (SDE) Approach </li></ul></ul><ul><li>So...
<ul><li>The Software Development Environment Approach </li></ul><ul><ul><li>By January 2003, the Division set the strategi...
INTRODUCTION <ul><li>The situation starting in Q1/2003 to Q4/2006 …  </li></ul>ECLIPSE REQUIREMENTS MANAGEMENT IBM/Rationa...
INTRODUCTION <ul><li>The different areas correspond to specific  projects and sub-projects of the Software Development Env...
INTRODUCTION <ul><li>SDE Main Components Architecture, tools and interfaces </li></ul>
INDEX (Cont.) <ul><li>Introduction </li></ul><ul><ul><li>Software Development Environment (SDE) Approach </li></ul></ul><u...
<ul><li>Concept: central management of Infrastructure & Missions requirements </li></ul><ul><ul><li>Each new Mission Data ...
<ul><li>Requirement Management tool (DOORS) </li></ul>REQUIREMENTS MANAGEMENT (SDE-RM)   <ul><li>(Image taken from OPS-GD ...
<ul><li>Concept: evolution toward a Model-Driven Architecture approach </li></ul><ul><ul><li>The arrival of UML impacted o...
<ul><li>The Development Management tool (Enterprise Architect) </li></ul>DEVELOPMENT MANAGEMENT (SDE-DM)
<ul><li>Concept: Management of system tests and selection of the most suitable tool to be used as part of the SDE </li></u...
INDEX (Cont.) <ul><li>Introduction </li></ul><ul><ul><li>Software Development Environment (SDE) Approach </li></ul></ul><u...
<ul><li>Concept: centralised, integrated and process driven Configuration and Change Management System </li></ul><ul><ul><...
<ul><li>Phase I: Strategy Definition (Q3/2003) - Completed </li></ul><ul><ul><li>To define the project scope and to identi...
<ul><li>Phase III: Implementation (Q3/2005) - Completed </li></ul><ul><ul><li>Customize the selected tool to fulfill the r...
<ul><li>Telelogic Synergy Suite </li></ul><ul><ul><li>Telelogic Synergy / Change </li></ul></ul><ul><ul><ul><li>A process ...
<ul><li>SDE-CM tool for Change Mgt (Telelogic Synergy/Change) </li></ul>SDE-CCM ARCHITECTURE
<ul><li>SDE-CM tool for Configuration Mgt (Telelogic Synergy/CM) </li></ul>SDE-CCM ARCHITECTURE
INDEX (Cont.) <ul><li>Introduction </li></ul><ul><ul><li>Software Development Environment (SDE) Approach </li></ul></ul><u...
SDE-CCM LESSONS LEARNED <ul><li>Network security heavily constrained architectural options </li></ul><ul><ul><li>Remote ac...
SDE GENERAL ISSUES <ul><li>Significant effort will be dedicated to the tools integration </li></ul><ul><ul><li>Technically...
SDE SCHEDULE OVERVIEW (Tentative) <ul><li>SDE started by Q1/2003, expanding through the different areas… </li></ul>CONFIGU...
<ul><li>Thank you for your attention </li></ul><ul><li>Questions? </li></ul>QUESTIONS
Upcoming SlideShare
Loading in …5
×

OPS Forum Configuration and Change Management for Ground Segments 17.11.2006

1,106 views

Published on

Software quality is a dynamic attribute that depends on many activities spread across the lifecycle of the software and therefore can change (often for the worse) over the software's life time.

Requirements engineering, configuration management and change management activities in particular contribute significantly to the overall quality of software. These activities must be done through the different phases of the software's lifecycle in order to guarantee a substantial and measurable cost and risk reduction and the consequent increase of quality in the software. This applies for the development, maintenance and reengineering of software.
ESOC's Ground Systems Engineering Dept. launched the Software Development Environment (SDE) project aimed at reviewing the development, maintenance and reengineering processes, as well as to provide the most suitable set of tools to support these processes. In particular, regarding configuration and change management, the main objectives of the project are to select and deploy a suitable suite of CCM tools in the Infrastructure and Missions divisions and to review and improve the CCM practices, processes, life cycles and procedures existing in the divisions.

OPS-GIM will present the SDE and the different areas involved, outline the main goals, phases and approaches adopted, detail the configuration and change management area in terms of the project, processes, practices and infrastructure, and will enumerate some of the problems and experiences seen during the SDE-CM project in particular and the SDE in general.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,106
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
21
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

OPS Forum Configuration and Change Management for Ground Segments 17.11.2006

  1. 1. SDE at ESA
  2. 2. INDEX <ul><li>Introduction </li></ul><ul><ul><li>Software Development Environment (SDE) Approach </li></ul></ul><ul><li>Software Development Environment </li></ul><ul><ul><li>Requirements Management (SDE-RM) </li></ul></ul><ul><ul><li>Development Management (SDE-DM) </li></ul></ul><ul><ul><li>Validation Management (SDE-VM) </li></ul></ul><ul><li>Configuration and Change Management (SDE-CCM) </li></ul><ul><ul><li>SDE-CM Project and Phases </li></ul></ul><ul><ul><li>Telelogic Synergy/Change Synergy/CM </li></ul></ul><ul><ul><li>Configuration and Change Management Architecture </li></ul></ul><ul><li>Conclusion </li></ul><ul><ul><li>SDE Lessons Learned </li></ul></ul><ul><ul><li>SDE General Issues </li></ul></ul>
  3. 3. <ul><li>The Software Development Environment Approach </li></ul><ul><ul><li>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. </li></ul></ul><ul><ul><ul><li>Standardise the tools and methodologies to increase the quality and homogeneity of software. </li></ul></ul></ul><ul><ul><ul><li>Improve overall efficiency of the processes. </li></ul></ul></ul><ul><ul><ul><li>Reduction of costs and risks. </li></ul></ul></ul><ul><ul><ul><li>Reusability of the software (Infrastructure and Missions). </li></ul></ul></ul><ul><ul><ul><li>Improvement of the services provided by the Divisions. </li></ul></ul></ul><ul><ul><li>Additionally, the Software Development Environment had to </li></ul></ul><ul><ul><ul><li>Comply with internal Quality Management . </li></ul></ul></ul><ul><ul><ul><li>Adhere to ITIL best practices. </li></ul></ul></ul><ul><li>All the areas of the Software Development life cycle are addressed </li></ul><ul><li>Several new and existent tools involved in each of the areas </li></ul>INTRODUCTION
  4. 4. INTRODUCTION <ul><li>The situation starting in Q1/2003 to Q4/2006 … </li></ul>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
  5. 5. INTRODUCTION <ul><li>The different areas correspond to specific projects and sub-projects of the Software Development Environment. </li></ul>
  6. 6. INTRODUCTION <ul><li>SDE Main Components Architecture, tools and interfaces </li></ul>
  7. 7. INDEX (Cont.) <ul><li>Introduction </li></ul><ul><ul><li>Software Development Environment (SDE) Approach </li></ul></ul><ul><li>Software Development Environment </li></ul><ul><ul><li>Requirements Management (SDE-RM) </li></ul></ul><ul><ul><li>Development Management (SDE-DM) </li></ul></ul><ul><ul><li>Validation Management (SDE-VM) </li></ul></ul><ul><li>Configuration and Change Management (SDE-CM) </li></ul><ul><ul><li>SDE-CM Project and Phases </li></ul></ul><ul><ul><li>Telelogic Synergy/Change Synergy/CM </li></ul></ul><ul><ul><li>Configuration and Change Management Architecture </li></ul></ul><ul><li>Conclusion </li></ul><ul><ul><li>SDE Lessons Learned </li></ul></ul><ul><ul><li>SDE General Issues </li></ul></ul>
  8. 8. <ul><li>Concept: central management of Infrastructure & Missions requirements </li></ul><ul><ul><li>Each new Mission Data System is developed based on the infrastructure software produced by the infrastructure division. </li></ul></ul><ul><ul><li>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. </li></ul></ul><ul><ul><li>Reuse of Mission requirements by Infrastructure </li></ul></ul><ul><ul><li>Management of commonality between Missions ( Mission family e.g. ROS/MEX/VEX) </li></ul></ul><ul><li>Tool used: Telelogic DOORS and OPS-GD Renato project </li></ul><ul><li>Telelogic DOORS will be extended to interface other SDE tools </li></ul><ul><ul><li>SDE Configuration & Change Management (CCM - Telelogic Synergy) </li></ul></ul><ul><ul><li>SDE Validation Management (VM – Tool TBD) </li></ul></ul><ul><ul><li>SDE Development Management (DM – Enterprise Architect) </li></ul></ul>REQUIREMENTS MANAGEMENT (SDE-RM)
  9. 9. <ul><li>Requirement Management tool (DOORS) </li></ul>REQUIREMENTS MANAGEMENT (SDE-RM) <ul><li>(Image taken from OPS-GD RENATO) </li></ul>
  10. 10. <ul><li>Concept: evolution toward a Model-Driven Architecture approach </li></ul><ul><ul><li>The arrival of UML impacted on the way software is built. </li></ul></ul><ul><ul><li>The software development is slowly moving from code-centered to a model-centered (MDA) approach. </li></ul></ul><ul><ul><li>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 </li></ul></ul><ul><ul><li>OPS-GI run several activities to explore MDA and to identify benefits of adopting the technology. A number of problems were identified: </li></ul></ul><ul><ul><ul><li>Tool incompatibility: main reason is the standard (XML Metadata Interchange, XMI) that serializes the UML models so that they can be stored and retrieved. </li></ul></ul></ul><ul><ul><ul><li>Runtime environment dependency, </li></ul></ul></ul><ul><ul><ul><li>Lack of tool consolidation and quick evolution of the market. </li></ul></ul></ul><ul><li>Tool used: Enterprise Architect </li></ul><ul><ul><li>Enterprise Architect tool complies with XMI standards, disposes of code generation capabilities (and it is reasonably priced). </li></ul></ul><ul><ul><li>MagicDraw is used for the projects requiring XMI 2.1 </li></ul></ul><ul><ul><li>The models cover the static description of classes and some activity diagrams to show the data flow. </li></ul></ul>DEVELOPMENT MANAGEMENT (SDE-DM)
  11. 11. <ul><li>The Development Management tool (Enterprise Architect) </li></ul>DEVELOPMENT MANAGEMENT (SDE-DM)
  12. 12. <ul><li>Concept: Management of system tests and selection of the most suitable tool to be used as part of the SDE </li></ul><ul><ul><li>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. </li></ul></ul><ul><ul><li>The traceability between test cases and software requirements. </li></ul></ul><ul><ul><li>The coverage of requirements by the test plans. </li></ul></ul><ul><ul><li>The generation of statistical reports. </li></ul></ul><ul><ul><li>The production of the necessary test documentation. </li></ul></ul><ul><ul><li>The management of users and access rights to the test chain . </li></ul></ul><ul><li>Tool used: </li></ul><ul><ul><li>3 pre-selected tools: Mercury Quality Center, Salome TMF open source, and QaTraq open source. </li></ul></ul><ul><ul><li>Activity was started in September 2006 </li></ul></ul>VALIDATION MANAGEMENT (SDE-VM)
  13. 13. INDEX (Cont.) <ul><li>Introduction </li></ul><ul><ul><li>Software Development Environment (SDE) Approach </li></ul></ul><ul><li>Software Development Environment </li></ul><ul><ul><li>Requirements Management (SDE-RM) </li></ul></ul><ul><ul><li>Development Management (SDE-DM) </li></ul></ul><ul><ul><li>Validation Management (SDE-VM) </li></ul></ul><ul><li>Configuration and Change Management (SDE-CM) </li></ul><ul><ul><li>SDE-CM Project and Phases </li></ul></ul><ul><ul><li>Telelogic Synergy/Change Synergy/CM </li></ul></ul><ul><ul><li>Configuration and Change Management Architecture </li></ul></ul><ul><li>Conclusion </li></ul><ul><ul><li>SDE Lessons Learned </li></ul></ul><ul><ul><li>SDE General Issues </li></ul></ul>
  14. 14. <ul><li>Concept: centralised, integrated and process driven Configuration and Change Management System </li></ul><ul><ul><li>An integrated tool for Change and Configuration management </li></ul></ul><ul><ul><li>Consolidation of multitude set of tools in OPS-GI (eLog, M-Web, MS Access, CVS, etc.) </li></ul></ul><ul><ul><li>Centralised tool accessible from both ESA and Contractors premises </li></ul></ul><ul><ul><li>Improved practices: processes, lifecycles and procedures </li></ul></ul><ul><li>Tool used: CM Synergy Suite from Telelogic </li></ul><ul><li>Project Approach in four phases </li></ul><ul><ul><li>Strategy Definition </li></ul></ul><ul><ul><li>Tools Evaluation & Selection </li></ul></ul><ul><ul><li>Implementation </li></ul></ul><ul><ul><li>Deployment </li></ul></ul>CONFIGURATION AND CHANGE MANAGEMENT (SDE-CCM)
  15. 15. <ul><li>Phase I: Strategy Definition (Q3/2003) - Completed </li></ul><ul><ul><li>To define the project scope and to identify the stakeholders. </li></ul></ul><ul><ul><li>To get the management commitment </li></ul></ul><ul><li>Phase II: Tools Evaluation & Selection (Q2/2004) - Completed </li></ul><ul><ul><li>Configuration & Change Management requirements gathering </li></ul></ul><ul><ul><ul><li>Requirements organized in 14 dimensions and sub-dimensions </li></ul></ul></ul><ul><ul><li>Tools market screening: 18 tools considered and 3 preferred tools evaluated against the requirements </li></ul></ul><ul><ul><ul><li>IBM ClearCase/ClearQuest </li></ul></ul></ul><ul><ul><ul><li>Telelogic Synergy Suite (Synergy/Change and Synergy/CM) </li></ul></ul></ul><ul><ul><ul><li>CVS/Bugzilla </li></ul></ul></ul><ul><ul><li>Evaluation based on: </li></ul></ul><ul><ul><ul><li>OVUM and YPHISE reports on Configuration and Change Mgt </li></ul></ul></ul><ul><ul><ul><li>Requirements gathering interviews </li></ul></ul></ul><ul><ul><ul><li>Development of 3 prototypes evaluated during workshops </li></ul></ul></ul>CONFIGURATION AND CHANGE MANAGEMENT (SDE-CCM)
  16. 16. <ul><li>Phase III: Implementation (Q3/2005) - Completed </li></ul><ul><ul><li>Customize the selected tool to fulfill the requirements </li></ul></ul><ul><ul><li>First deployment in a reduced number of projects, including training </li></ul></ul><ul><ul><li>Review of the performance and adjustment of the system </li></ul></ul><ul><li>Phase IV: Deployment (Q3/2006) – On-going </li></ul><ul><ul><li>Architecture consolidation according to network evolution (new DMZ) </li></ul></ul><ul><ul><li>Complete integration between Synergy/CM and Synergy/Change to extend the benefits of a task-based SDE CCM </li></ul></ul><ul><ul><li>Interfacing to other SDE tools (e.g. eLOG, Assyst, DOORS and rest of available SDE tools) </li></ul></ul><ul><ul><li>Elaboration of CCM procedures applicable to ESA and Contractors </li></ul></ul><ul><ul><li>Deployment on all OPS-GI projects including data migration </li></ul></ul>CONFIGURATION AND CHANGE MANAGEMENT (SDE-CCM)
  17. 17. <ul><li>Telelogic Synergy Suite </li></ul><ul><ul><li>Telelogic Synergy / Change </li></ul></ul><ul><ul><ul><li>A process and lifecycle web-based application </li></ul></ul></ul><ul><ul><ul><li>Change Management for distributed teams </li></ul></ul></ul><ul><ul><ul><li>User-friendly and intuitive change request interface </li></ul></ul></ul><ul><ul><ul><li>Tailorable workflow </li></ul></ul></ul><ul><ul><li>Telelogic Synergy / Configuration Management </li></ul></ul><ul><ul><ul><li>A task-based client-server application </li></ul></ul></ul><ul><ul><ul><li>Supports parallel and distributed development (i.e. ESA, Industry and all our interconnected projects) </li></ul></ul></ul><ul><ul><ul><li>Advanced release management </li></ul></ul></ul><ul><li>SDE-CM Architecture </li></ul><ul><ul><li>Hardware: 2 servers, one in Relay LAN and one in Dev LAN </li></ul></ul><ul><ul><li>Single CPU (front server) and dual CPU (back server) Linux servers. </li></ul></ul><ul><ul><li>Compliant with ESA Network Security Policy </li></ul></ul>SDE-CCM ARCHITECTURE
  18. 18. <ul><li>SDE-CM tool for Change Mgt (Telelogic Synergy/Change) </li></ul>SDE-CCM ARCHITECTURE
  19. 19. <ul><li>SDE-CM tool for Configuration Mgt (Telelogic Synergy/CM) </li></ul>SDE-CCM ARCHITECTURE
  20. 20. INDEX (Cont.) <ul><li>Introduction </li></ul><ul><ul><li>Software Development Environment (SDE) Approach </li></ul></ul><ul><li>Software Development Environment </li></ul><ul><ul><li>Requirements Management (SDE-RM) </li></ul></ul><ul><ul><li>Development Management (SDE-DM) </li></ul></ul><ul><ul><li>Validation Management (SDE-VM) </li></ul></ul><ul><li>Configuration and Change Management (SDE-CM) </li></ul><ul><ul><li>SDE-CM Project and Phases </li></ul></ul><ul><ul><li>Telelogic Synergy/Change Synergy/CM </li></ul></ul><ul><ul><li>Configuration and Change Management Architecture </li></ul></ul><ul><li>Conclusion </li></ul><ul><ul><li>SDE Lessons Learned </li></ul></ul><ul><ul><li>SDE General Issues </li></ul></ul>
  21. 21. SDE-CCM LESSONS LEARNED <ul><li>Network security heavily constrained architectural options </li></ul><ul><ul><li>Remote access imposed 2-servers architecture located in Relay-LAN (Change Management) and Dev LAN (Configuration Management) </li></ul></ul><ul><ul><ul><li>CM Synergy was not design for such architecture which implies a lot of customisation </li></ul></ul></ul><ul><ul><ul><li>Absence of DMZ at ESOC and OPS-EC difficulties to set-up it </li></ul></ul></ul><ul><li>Processes and lifecycle review are essential </li></ul><ul><ul><li>Time consuming. Several meetings, presentations and workshops at different levels (technical, management, interdivisional) </li></ul></ul><ul><ul><ul><li>SDE CCM Phase II extended for more than 12 months, due to workload, difficulties with Contractor, prototypes development, several agreements. </li></ul></ul></ul><ul><ul><li>Independent (external) consultancy companies should be involved </li></ul></ul><ul><li>Management commitment and Users buy-in are critical success factor </li></ul><ul><li>The team in charge of each SDE must have a strong background in the implementation and deploying of the different SDE tools. </li></ul><ul><ul><li>Experienced in processes review and improvements </li></ul></ul><ul><ul><li>Proactive behavior and execution on each SDE area </li></ul></ul>
  22. 22. SDE GENERAL ISSUES <ul><li>Significant effort will be dedicated to the tools integration </li></ul><ul><ul><li>Technically this involves the interfaces, data exchange, database compatibility and others </li></ul></ul><ul><ul><li>Process management regarding who must use which tool in what moment </li></ul></ul><ul><li>Issues related to the user management at different levels </li></ul><ul><ul><li>Each tool disposes of its own user management mechanism and associated data (e.g. SDE-CM) </li></ul></ul><ul><ul><li>Problems to interface the user management data between the tools and to the standard ESA user management </li></ul></ul><ul><li>The teams involved in the software development and maintenance have to commit to the new processes and tools. </li></ul><ul><ul><li>Resistance from the user. The team must quickly obtain benefits compared with their previous tools: easy-of-use, efficiency of the processes, overall performance. </li></ul></ul><ul><ul><li>Unavailability of functionalities. No functionality (even minor features) of the old tools must be lost. </li></ul></ul>
  23. 23. SDE SCHEDULE OVERVIEW (Tentative) <ul><li>SDE started by Q1/2003, expanding through the different areas… </li></ul>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
  24. 24. <ul><li>Thank you for your attention </li></ul><ul><li>Questions? </li></ul>QUESTIONS

×