Your SlideShare is downloading. ×
DEBAT Development of EAST Based Access Tools
         Project Management Plan




Contract: 16562/02/I-LG
Reference: SS/DE...
Reference : SS/DEBAT/PMP
                                                                            Issue                ...
Reference   : SS/DEBAT/PMP
                                        DEBAT                               Issue.      : 1.3
 ...
Reference     : SS/DEBAT/PMP
                                                         DEBAT                               ...
Reference     : SS/DEBAT/PMP
                                                          DEBAT                              ...
Reference     : SS/DEBAT/PMP
                                                           DEBAT                             ...
Reference   : SS/DEBAT/PMP
                               DEBAT                               Issue.      : 1.3
          ...
Reference   : SS/DEBAT/PMP
                            DEBAT                               Issue.      : 1.3
             ...
Reference   : SS/DEBAT/PMP
                                        DEBAT                               Issue.      : 1.3
 ...
Reference   : SS/DEBAT/PMP
                                        DEBAT                              Issue.      : 1.3
  ...
Reference : SS/DEBAT/PMP
                                                                                 Issue           ...
Reference   : SS/DEBAT/PMP
                                           DEBAT                               Issue.      : 1....
Reference   : SS/DEBAT/PMP
                                          DEBAT                               Issue.      : 1.3...
Reference   : SS/DEBAT/PMP
                                          DEBAT                               Issue.      : 1.3...
Reference   : SS/DEBAT/PMP
                                           DEBAT                               Issue.      : 1....
Reference   : SS/DEBAT/PMP
                                           DEBAT                                Issue.      : 1...
Reference   : SS/DEBAT/PMP
                                          DEBAT                                 Issue.      : 1...
Reference   : SS/DEBAT/PMP
                                                   DEBAT                                      I...
Reference   : SS/DEBAT/PMP
                                            DEBAT                               Issue.      : 1...
Reference   : SS/DEBAT/PMP
                                          DEBAT                               Issue.      : 1.3...
Reference   : SS/DEBAT/PMP
                                           DEBAT                               Issue.      : 1....
Reference   : SS/DEBAT/PMP
                                          DEBAT                               Issue.      : 1.3...
Reference   : SS/DEBAT/PMP
                                            DEBAT                                Issue.      : ...
Reference   : SS/DEBAT/PMP
                                          DEBAT                                  Issue.      : ...
Reference   : SS/DEBAT/PMP
                                         DEBAT                               Issue.      : 1.3
...
Reference   : SS/DEBAT/PMP
                                           DEBAT                               Issue.      : 1....
Reference   : SS/DEBAT/PMP
                                        DEBAT                               Issue.      : 1.3
 ...
Reference   : SS/DEBAT/PMP
                                           DEBAT                               Issue.      : 1....
Reference   : SS/DEBAT/PMP
                                         DEBAT                               Issue.      : 1.3
...
Reference   : SS/DEBAT/PMP
                                           DEBAT                               Issue.      : 1....
Reference   : SS/DEBAT/PMP
                                           DEBAT                               Issue.      : 1....
Reference   : SS/DEBAT/PMP
                                           DEBAT                               Issue.      : 1....
Reference   : SS/DEBAT/PMP
                                         DEBAT                               Issue.      : 1.3
...
Reference   : SS/DEBAT/PMP
                                          DEBAT                               Issue.      : 1.3...
Reference   : SS/DEBAT/PMP
                                           DEBAT                               Issue.      : 1....
Reference   : SS/DEBAT/PMP
                                         DEBAT                               Issue.      : 1.3
...
Reference   : SS/DEBAT/PMP
                                         DEBAT                                Issue.      : 1.3...
Reference   : SS/DEBAT/PMP
                                           DEBAT                             Issue.      : 1.3
...
Reference   : SS/DEBAT/PMP
                                          DEBAT                               Issue.      : 1.3...
Reference   : SS/DEBAT/PMP
                                          DEBAT                               Issue.      : 1.3...
DEBAT Project Management Plan.doc
DEBAT Project Management Plan.doc
DEBAT Project Management Plan.doc
DEBAT Project Management Plan.doc
DEBAT Project Management Plan.doc
DEBAT Project Management Plan.doc
DEBAT Project Management Plan.doc
DEBAT Project Management Plan.doc
DEBAT Project Management Plan.doc
DEBAT Project Management Plan.doc
DEBAT Project Management Plan.doc
DEBAT Project Management Plan.doc
DEBAT Project Management Plan.doc
DEBAT Project Management Plan.doc
DEBAT Project Management Plan.doc
DEBAT Project Management Plan.doc
Upcoming SlideShare
Loading in...5
×

DEBAT Project Management Plan.doc

684

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
684
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
19
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "DEBAT Project Management Plan.doc"

  1. 1. DEBAT Development of EAST Based Access Tools Project Management Plan Contract: 16562/02/I-LG Reference: SS/DEBAT/PMP Issue: 1.3 Date: 13/11/2003 Prepared by: Date: Laurent Cohen Checked by: Date: Josiane Denailhac Approved by: Date: Alain Lapeyre DEBAT – Development of EAST Based Access Tools
  2. 2. Reference : SS/DEBAT/PMP Issue : 1.3 DEBAT :/ Project Management Plan Date : 13/11/2002 Page :i Document Status Sheet Document Title DEBAT Project Management Plan Document Reference Number SS/DEBAT/PMP Issue Revision Date Reason for change 1 3 13/11/2003 Updated with project team changes and CDR deliveries 1 2 08/07/2003 Updated for Phase 2 1 1 31/10/2002 Integration of comments from ESA 1 0 15/10/2002 First issue of the PMP for Phase 1 of the project DEBAT – Development of EAST Based Access Tools
  3. 3. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : ii Document Change Records Document Title DEBAT Project Management Plan Document Reference Number SS/DEBAT/PMP Document Issue/Revision Number 1.3 Page Paragraph Reason for change 7-9 The project team has changed (paragraph 2.4.2) 44-45 Adding of the new documents delivered during the CDR and the new version updated after the CDR comments Document Title DEBAT Project Management Plan Document Reference Number SS/DEBAT/PMP Document Issue/Revision Number 1.2 Page Paragraph Reason for change 6 The Quality Engineer is now M. Granet 27 Removal of Work-Package descriptions sheets to reduce the document size (only a reference to CS proposal is kept) 28-38 Completion of chapters dedicated to Phase 2 40-41 Update of the documentation tree Document Title DEBAT Project Management Plan Document Reference Number SS/DEBAT/PMP Document Issue/Revision Number 1.1 Page Paragraph Reason for change 64 Mention of the documentation repository set-up on an ESA server. 64 Some typo fixed for documents references 64 Added: issues 1.1 of the PMP and PAP Document Title DEBAT Project Management Plan Document Reference Number SS/DEBAT/PMP Document Issue/Revision Number 1.0 Page Paragraph Reason for change All First issue DEBAT – Development of EAST Based Access Tools
  4. 4. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : iii Table of contents DOCUMENT STATUS SHEET.......................................................................................................I DOCUMENT CHANGE RECORDS.............................................................................................II TABLE OF CONTENTS...............................................................................................................III TABLE OF FIGURES.....................................................................................................................V ACRONYMS AND ABBREVIATIONS.......................................................................................VI APPLICABLE DOCUMENTS...................................................................................................VIII REFERENCE DOCUMENTS.......................................................................................................IX 1. INTRODUCTION..........................................................................................................................1 1.1 PROJECT OVERVIEW..........................................................................................................................1 1.2 OBJECTIVES OF THE DOCUMENT..........................................................................................................1 1.3 STRUCTURE OF THE DOCUMENT..........................................................................................................1 1.4 EVOLUTION OF THE PROJECT MANAGEMENT PLAN...............................................................................2 2. PROJECT ORGANISATION.......................................................................................................3 2.1 PROCESS MODEL..............................................................................................................................3 2.2 OVERALL PROJECT SCHEDULE AND MILESTONES.....................................................................................3 2.3 FACILITIES AND RESOURCES...............................................................................................................5 2.4 PROJECT ORGANISATION CHART..........................................................................................................5 2.4.1 First project organisation chart...........................................................................................5 2.4.2 Second project organisation chart.......................................................................................7 2.5 ORGANISATIONAL ROLES AND RESPONSIBILITIES....................................................................................9 2.5.1 The Project Director.............................................................................................................9 2.5.2 The Project Manager ...........................................................................................................9 2.5.3 The technical manager.......................................................................................................10 2.5.4 The Experts.........................................................................................................................10 2.5.5 The Development Team......................................................................................................10 2.6 ORGANISATIONAL BOUNDARIES AND INTERFACES.................................................................................11 2.6.1 Communications with ESRIN.............................................................................................11 2.6.2 Relation to CNES EAST project.........................................................................................11 3. MONITORING AND CONTROL..............................................................................................12 3.1 MEETING AND REPORTING...............................................................................................................12 3.1.1 Meetings.............................................................................................................................12 3.1.2 Reporting............................................................................................................................12 3.2 SCHEDULE REPORTING AND CONTROL................................................................................................13 3.3 RISK MANAGEMENT AND REGISTER....................................................................................................13 4. LICENSES ISSUES......................................................................................................................14 4.1 PRINCIPLES OF THE DEBAT DEVELOPMENT AND LICENSE...................................................................14 DEBAT – Development of EAST Based Access Tools
  5. 5. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : iv 4.2 TERMS OF THE PROPOSED LICENSE....................................................................................................15 5. PHASE 1 - ANALYSIS AND STUDIES PHASE......................................................................16 5.1 OBJECTIVES..................................................................................................................................16 5.2 WORK BREAKDOWN STRUCTURE.......................................................................................................17 5.3 DEVELOPMENT PLAN, WORK LOGIC AND ACTIVITIES.............................................................................18 5.3.1 Requirements collection and technical analysis.................................................................20 5.3.2 Implementations.................................................................................................................23 5.3.3 DEBAT definition...............................................................................................................23 5.3.4 Support to user group.........................................................................................................24 5.3.5 Promotion...........................................................................................................................25 5.4 SCHEDULE, MEETINGS AND DELIVERIES..............................................................................................27 5.4.1 Schedule..............................................................................................................................27 5.4.2 Meetings.............................................................................................................................27 5.4.3 CS Deliveries and Customer Furnished Items...................................................................28 5.5 WORK PACKAGES DESCRIPTION.......................................................................................................29 6. PHASE 2 - IMPLEMENTATION PHASE................................................................................30 6.1 OBJECTIVES..................................................................................................................................30 6.2 WORK BREAKDOWN STRUCTURE.......................................................................................................31 6.3 WORK LOGIC AND ACTIVITIES..........................................................................................................32 6.3.1 Software specifications and architectural design...............................................................32 6.3.2 Implementation, integration and acceptance tests.............................................................34 6.3.3 Promotion...........................................................................................................................35 6.3.4 Concept Validation.............................................................................................................36 6.3.5 Proposals for CCSDS standards updates...........................................................................36 6.3.6 Demonstration....................................................................................................................36 6.3.7 Support to user group.........................................................................................................36 6.3.8 Final presentation..............................................................................................................36 6.4 SCHEDULE, MEETINGS AND DELIVERIES..............................................................................................37 6.4.1 Schedule..............................................................................................................................37 6.4.2 Meetings.............................................................................................................................37 6.4.3 CS Deliveries and Customer Furnished Items...................................................................38 6.5 WORK PACKAGES DESCRIPTIONS.....................................................................................................40 7. WARRANTY PHASE..................................................................................................................41 7.1 WARRANTY PRINCIPLES..................................................................................................................41 7.2 WARRANTY ACTIVITIES...................................................................................................................41 8. DOCUMENTATION TREE.......................................................................................................42 DEBAT – Development of EAST Based Access Tools
  6. 6. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page :v Table of figures FIGURE 2-1 MAJOR MILESTONES.............................................................................................3 FIGURE 2-2 OVERALL PROJECT SCHEDULE AND MILESTONES....................................4 FIGURE 2-3 PROJECT ORGANISATION CHART....................................................................5 FIGURE 2-4 PROJECT ORGANISATION CHART....................................................................8 FIGURE 5-5 PHASE 1 WORK BREAKDOWN STRUCTURE.................................................17 FIGURE 5-6 ANALYSIS AND STUDIES PHASE ( PHASE 1)..................................................18 FIGURE 5-7 REQUIREMENTS COLLECTION AND TECHNICAL ANALYSIS WORK LOGIC...............................................................................................................................................20 FIGURE 5-8 PHASE 1 INTERVIEWS METHODOLOGY........................................................21 FIGURE 5-9 DEBAT DEFINITION WORK LOGIC..................................................................23 FIGURE 5-10 DETAILED SCHEDULE OF DEBAT PHASE 1.................................................27 FIGURE 6-11 OUTPUTS OF DEBAT PHASE 1..........................................................................30 FIGURE 6-12 PHASE 2 WBS.........................................................................................................31 FIGURE 6-13 IMPLEMENTATION PLAN FOR PHASE 2......................................................32 FIGURE 6-14: SOFTWARE SPECIFICATIONS & ARCHITECTURAL DESIGN WORK LOGIC...............................................................................................................................................33 FIGURE 6-15: IMPLEMENTATION, INTEGRATION & ACCEPTANCE TESTS WORK LOGIC...............................................................................................................................................34 FIGURE 6-16: DETAILED DESIGN WORK LOGIC................................................................35 DEBAT – Development of EAST Based Access Tools
  7. 7. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : vi Acronyms and abbreviations ADD Architectural Design Document AMS Archive Management System API Application Program Interface AR Acceptance Review ATP Authorisation To Proceed CA Control Authority CAID Control Authority Identifier CAO Control Authority Office CAOS Control Authority Office System CDF Common Data Format CDR Critical Design Review CEOS Committee on Earth Observation Science CFI Customer Furnished Item CNES Centre National D’Etudes Spatiales (French Space Agency) COTS Commercial Off The Shelf CCSDS Consultative Committee for Space Data Systems DEAL Display EAST Access List DEBAT Development of EAST Based Access Tools DEBAT-DM DEBAT Data Modeller DEBAT-DPE DEBAT Data Producer & Editor DEBAT-DEQ DEBAT Data Extractor & Querying DEBAT-PPT DEBAT Post Processing Tools DEBAT-UT DEBAT Utilities DDR Data Description Record DDU Data Description Unit DDF Design Definition File DED Data Entity Dictionary DEDSL Data Entity Description Specification Language DEW Data Extractor Wizard DIP Dissemination Information Package DJF Design Justification File DUW Data Update Wizard DW DEBAT Workshop EAST Enhanced ADA Sub SeT ECSS European Cooperation for Space Standardization EO Earth Observation ESA European Space Agency ESRIN European Space Research INstitute ERS European Remote Sensing satellite ESA European Space Agency EVA ESA Virtual Archive FA Final Acceptance FAQ Frequently Asked Question FAR Factory Acceptance Review FAT Factory Acceptance Tests DEBAT – Development of EAST Based Access Tools
  8. 8. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : vii FDIR Fault Detection, Isolation and Recovery FP Final Presentation FPA Final Presentation and Acceptance GUI Graphical User Interface HDF Hierarchical Data Format HTML Hyper Text Mark-up Language HTTP Hyper Text Transfer Protocol HW Hardware ICD Interface Control Document IDVP Implementation, Diffusion and Validation Plan IR Interface Requirements ITT Invitation To Tender JSP Java Server Pages KOM Kick Off Meeting MACAO Member Agency Control Authority Office MMI Man-Machine Interface NAS Network Attached Storage OAIS Open Archival Information System OASIS Space Data Modelling Help Tool OSAT On Site installation and Acceptance Tests PAP Product Assurance Plan PDR Preliminary Design Review PMP Project Management Plan PUS Packet Utilisation Standard PVL Parameter Value Language RB Requirements Baseline RID Review Item Discrepancy RTD Research and Technology Development SCMP Software Configuration Management Plan SIP Submission Information Package SOAP Simple Object Access Protocol SOW Statement of Work SPMP Software Project Management Plan SRR System Requirements Review SVG Scalable Vector Graphic TM/TC Telemetry / Telecommand TS Technical Specifications UDDI Universal Description Discovery and Integration URD User Requirements Document WSDL Web Service Description Language WWW World Wide Web XML eXtensible Mark-up Language XSL eXtensible Stylesheet Language XSLT eXtensible Stylesheet Language Transformation DEBAT – Development of EAST Based Access Tools
  9. 9. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : viii Applicable Documents Title Issue Date Reference AD1 ESRIN SOW “Development of 1.1 18/03/2002 GSPS-RTDA-EOAD-SW-02-0001 EAST Based Access Tools” AD2 Fax received from ESA 07/06/2002 IMT-CR/9021/02/I-LG AD3 CS Proposal "DEBAT" 21/06/2002 CSSI/111-1/CG/LM/2/453-1 AD4 Minutes of Kick-off Meeting 17/09/2002 /CRR/SS/DEBAT/001 AD5 ECSS – Space Engineering ECSS-E-40B Standards – Software AD6 ECSS - Space Engineering ECSS-Q-80B Standards - Software Product Assurance AD7 CS SI Proposal for Phase 2 March 2003 CSSI/111-1/CG/PKV/3/140 AD8 Minutes of Phase 2 Kick-off 30/04/2003 /CRR/SS/DEBAT/006 meeting (Authorisation To Proceed) DEBAT – Development of EAST Based Access Tools
  10. 10. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : ix Reference Documents Title Issue Date Reference RD1 DEBAT Product Assurance Plan 1.2 08/07/2003 SS/DEBAT/PAP RD2 Interviews Technical Note 1.0 14/01/2003 SS/DEBAT/I_TN RD3 EAST for TM/TC processing 1.0 14/01/2003 SS/DEBAT/TMTC_TN Technical Note RD4 EAST current applications 1.0 14/01/2003 SS/DEBAT/EAST_TN Technical Note RD5 Requirements Collection Technical 1.0 14/01/2003 SS/DEBAT/RC_TN Note RD6 User Requirements Document 1.2 10/03/2003 SS/DEBAT/URD RD7 Software Requirements Document 1.1 10/03/2003 SS/DEBAT/SRD RD8 Selection Process Methodology 1.2 10/03/2003 SS/DEBAT/SPM_TN Technical Note RD9 Implementation, Diffusion and 1.1 10/03/2003 SS/DEBAT/IDVP Validation Plan DEBAT – Development of EAST Based Access Tools
  11. 11. Reference : SS/DEBAT/PMP Issue : 1.3 DEBAT :/ Project Management Plan Date : 13/11/2002 Page :1 1. Introduction 1.1 Project overview The main objective of “Development of EAST Based Access Tools” project is to build a set of enhanced tools upon EAST technologies to provide engineers, scientists and end-users with powerful tools covering the entire data life cycle (modelling/definition, production/generation, editing, accessing, checking, processing, extracting, querying, post-processing…). Another objective is to promote and diffuse DEBAT tools family and concepts to the potential user community (existing fields of application or new ones) by making them aware of the availability and advantages of these enhanced tools (DEBAT workshop, Web site, demonstration kit…). The underlying philosophy is to build on the knowledge and capitalised experience gained during previous developments (CNES, CS and ESA) being carried out for several years, to take advantage of the lessons learned from current/past EAST user projects (limitations, expectations), and to take into account new requirements (coming from the analysis of a range of selected projects/missions) and forthcoming requirements. There are two major identified axes of work: • Improvements (or new developments) to existing tools within current fields of application: this covers the extensions and enhancements of EAST language and tools for well-known domains where the degree of confidence is high due to past experience. The final results of these developments are expected to be high quality software: reliable, well engineered, user friendly, properly documented and flexible. • TM/TC fields of application: this covers the application of EAST technologies to TM/TC processing which is a new and critical domain that requires in depth analysis. The main objective for this new field of application is to provide the “proof of concept”, i.e. to analyse (and potentially demonstrate) the feasibility and advantages gained from applying EAST in the TM/TC arena. 1.2 Objectives of the document This Project Management Plan is intended to define, organise, monitor and control all the activities to be carried out in the frame of the DEBAT project. 1.3 Structure of the document This document is organised as follows: Chapter 1: Introduction The current chapter gives an overview of the project and its objectives. Chapter 2: Project organisation DEBAT – Development of EAST Based Access Tools
  12. 12. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page :2 This chapter details the project organisation: the organisation chart and the organisational roles and responsibilities. Chapter 3: Monitoring and control This chapter describes the monitoring and control processes set up for the project. Chapter 4: Licenses issues This chapter deals with the licenses issues of the DEBAT software. Chapter 5: Phase 1 - Analysis and studies phase This chapter describes the work to be performed during the first phase of the project, together with the development plan, the schedule, meetings and deliveries. Chapter 6: Phase 1 - Implementation phase This chapter describes the work to be performed during the second phase of the project, together with the development plan, the schedule, meetings and deliveries. Chapter 7: Warranty phase This chapter details the principles and the work to be performed during the warranty phase. Chapter 8: Documentation tree This chapter gives the structure of the documentation produced in the frame of the project 1.4 Evolution of the Project Management Plan This Project Management Plan will be updated as necessary throughout the project, and at least for the beginning of the second phase of DEBAT. DEBAT – Development of EAST Based Access Tools
  13. 13. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page :3 2. Project organisation 2.1 Process model The project has a phased approach. There are two phases: • "Analysis and studies phase": this first phase covers mainly the identification, analysis and ranking of the limitations of the current tools set and expected enhancements for fulfilling the expressed requirements, the identification of other areas of work that might become candidates for future work, and the production of an overall implementation and diffusion plan. • "Implementation phase": this second phase covers mainly the design, implementation, validation and demonstration of the developments carried out during DEBAT project. 2.2 Overall project schedule and milestones The duration of the first phase is about 5 months, and the duration of the second phase is about 12 months. A negotiation period is foreseen between the two phases in order to consolidate the price of phase 2 (an Authorisation To Proceed - ATP - is required to proceed with Phase 2). The expected total duration of the project is 18 months. A warranty period of 6 months is foreseen at the end of the project. This warranty period begins after a check-out period of 3 months (the check-out period beginning at the Acceptance Review of the software by the Agency). Figure 2-1 Major milestones The following figure gives the project overall schedule: DEBAT – Development of EAST Based Access Tools
  14. 14. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page :4 Figure 2-2 Overall project schedule and milestones The following table gives the major milestones of the project. Meeting Purpose M0 - T0 KOM - Kick Off Meeting M1 - T0+1 Interviews at ESRIN M2 - T0+2 Progress meeting M3 - T0+4 SRR - System Requirements Review M4 - T0+5 DEBAT Workshop M5 - T0+5.5 End of phase 1 meeting M6 - T0+6 ATP - Authorisation To Proceed M7 - T0+8 PDR - Preliminary Design Review M8 - T0+10 CDR - Critical Design Review M9 - T0+12 Progress meeting M10 - T0+14 Progress meeting M11 - T0+16 FAR - Factory Acceptance Review M12 - T0+17 AR - Acceptance Review (provisional acceptance) M13 - T0+18 FP - Final Presentation (end of project) M14 - T0+20 Final Acceptance (end of check-out period) - start of DEBAT – Development of EAST Based Access Tools
  15. 15. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page :5 warranty of 6 months. 2.3 Facilities and resources All the work described in this contract will be carried out at CS premises. All hardware and software resources (i.e. machines, tools, etc.) will be provided by CS for the activities to be performed at his premises and by ESRIN for activities to be performed at ESRIN facilities (installation at ESRIN and on-site acceptance tests). The hardware and software used for the project are described in the Product Assurance Plan [RD1]. 2.4 Project organisation chart 2.4.1 First project organisation chart The following diagram presents the first project organisation chart: Figure 2-3 Project Organisation chart The key personnel is the following: DEBAT – Development of EAST Based Access Tools
  16. 16. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page :6 • The Project Director is Alain ROUSSEL. • The Project Manager is Carlos GUERREIRO. • The Technical Manager is Laurent COHEN. • The Project Quality Manager is Maud Granet. Three axes of work have been identified. A responsible has been nominated for each one: • EAST/OASIS core technologies: Frédéric BERRIRI • Advanced technologies (Java, Web Services) : Laurent COHEN • TM/TC activities: Olivier QUEYRUT Furthermore, several experts will be involved all the project long in order to support the project with their thorough technological knowledge: • EAST expert : Claire PELLIZZARI (she has been working on EAST for more than 8 years) • Freeware and Open source expert: Luc MAISONOBE • The development team will also include J. FERREIRA and J. CANDAT. The following matrix defines the list of the key personnel in a synthetic way: Name of the Function within Competence fields Amount of time person the project dedicated to the project (%) Alain Project Director 19 years experience on Support to Project ROUSSEL project management. Management Carlos Project Manager Architectures, Project Management GUERREIRO JAVA/CORBA: he’s currently in charge of the Space Studies Direction of Projects. Laurent Technical Advanced technologies 100% COHEN Manager and (Java, Web Services) Responsible for Advanced Technologies Frédéric Responsible for EAST/OASIS: he is 75% DEBAT project BERRIRI EAST/OASIS currently the EAST project 25 % EAST core technologies manager (CNES Maintenance Contract maintenance contract) (CNES) Olivier Responsible for TM/TC, SCOS-2000. 100% QUEYRUT TM/TC activities Claire EAST expert EAST/OASIS: she has more 50% DEBAT project PELLIZZARI than 8 years experience of 50% EAST EAST. Maintenance Contract DEBAT – Development of EAST Based Access Tools
  17. 17. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page :7 (CNES) Jérôme Design/Develop EAST/OASIS: he has been 75% DEBAT project FERREIRA ment team working on EAST/OASIS 25% EAST since 09/2001 Maintenance Contract (EAST/OASIS CNES (CNES) maintenance contract). Jérôme Design/Develop XML/JAVA 100% CANDAT ment team Luc Freeware expert Specialist of the 1 day per month MAISONOBE freeware/open source issues. 2.4.2 Second project organisation chart Three main changes have been done into the project organisation during the month of September of 2003: • Alain Roussel, the Project Director of the project has changed his responsibilities into the company. The Project Director is now Alain Lapeyre. He is an experimented Project Manager, he has 12 years experience. • Carlos Guerreiro, the project manager has left CS during this month. This departure has some impacts on the organisation of the DEBAT project. Laurent Cohen, previously the Technical Manager of the project is now the Project Manager, and Olivier Queyrut became the Technical Manager. • Jean-Yves Souillard is now replaced by Josiane Denailhac, she is now the new project quality manager. The following diagram presents the second project organisation chart: DEBAT – Development of EAST Based Access Tools
  18. 18. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page :8 A. LAPEYRE Project Director L. COHEN Project Manager J. DENAILHAC Project Quality Manager O. QUEYRUT Technical Manager O. QUEYRUT F. BERRIRI C. PELLIZZARI Advanced Technologies EAST/OASIS core technology EAST expert Luc MAISONOBE J. FERREIRA J. CANDAT J.C. BRUNET Freeware expert B. VIALADE E. BJORNTVEDT D. GARCIN Java expert Figure 2-4 Project Organisation chart The key personnel is the following: • The Project Director is Alain LAPEYRE. • The Project Manager is Laurent COHEN. • The Technical Manager is Olivier QUEYRUT. • The Project Quality Manager is Josiane DENAILHAC. Two axes of work have been identified. A responsible has been nominated for each one: • EAST/OASIS core technologies: Frédéric BERRIRI • Advanced technologies (Java, Web Services) : Olivier QUEYRUT • TM/TC activities: suspended Furthermore, several experts will be involved all the project long in order to support the project with their thorough technological knowledge: • EAST expert : Claire PELLIZZARI (she has been working on EAST for more than 8 years) • Freeware and Open source expert: Luc MAISONOBE DEBAT – Development of EAST Based Access Tools
  19. 19. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page :9 The following matrix defines the list of the key personnel in a synthetic way: Name of the Function within Competence fields Amount of time person the project dedicated to the project (%) Alain LAPEYRE Project Director 12 years experience on Support to Project project management. Management Laurent COHEN Project Manager Advanced technologies Project Management (Java, Web Services). He has experience in project management Olivier QUEYRUT Technical Manager Advanced technologies 100% and Responsible for (Java, Web Services) Advanced Technologies Frédéric BERRIRI Responsible for EAST/OASIS: he is 75% DEBAT project EAST/OASIS core currently the EAST project 25 % EAST technologies manager (CNES Maintenance Contract maintenance contract) (CNES) Claire PELLIZZARI EAST expert EAST/OASIS: she has 50% DEBAT project more than 8 years 50% EAST experience of EAST. Maintenance Contract (CNES) 2.5 Organisational roles and responsibilities 2.5.1 The Project Director He is responsible for marketing, administrative and financial follow-up as well as control and providing assistance. He delegates management of the project to the project head and supervises the operation by means of periodical co-ordination meetings. 2.5.2 The Project Manager He is responsible for satisfactory completion of the project. He represents CS in relation to Customer for performing the contract. He distributes the tasks within the team assigned to the project, defines responsibilities and rules on possible conflicts. He submits all decisions which are his responsibility to Customer and ensures that they are then carried out. The project head plays a significant part in technical development so that he grasps the whole project perfectly: DEBAT – Development of EAST Based Access Tools
  20. 20. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : 10 • he ensures that the project consistently complies with the design specifications and also with the standards and practices defined in the product assurance plan, • he manages and co-ordinates the members of the team responsible for the work, • he is Customer's main contact, • he chairs technical and progress meetings, • he follows up progress of each of the tasks as well as monitoring deadlines, • at the beginning of each phase, he plans development with the different members of the team as well as the cross-checking controls to be performed, • he ensures that these are carried out, • he checks that the documentation produced has been correctly filled out and that it complies with standards, • he closes cross-checking controls and follow-up and authorises delivery, • he alone is responsible for approving any request for internal technical modification from the CS project team, before submitting it to the Customer manager. 2.5.3 The technical manager The technical manager is the project manager assistant. He is responsible for design choices and for choosing the ways in which to produce different system components. This involves: • providing technical support to team members during prototyping, design and production phases, • federating the team members' design and production choices, • providing technical follow-up for performance of each of the tasks while sending progress reports to the project head, • participating in cross-checking controls, • participating in design, production and testing of components, • participating in system acceptance reviews, • defining and maintaining a critical item list. 2.5.4 The Experts The EAST expert is devoted to support the project through his thorough knowledge of the technologies involved. She is aimed at giving his expertise to assist the development team in the different phases of the project from the requirement analysis to the design choices and implementation. 2.5.5 The Development Team The members of the development team perform the tasks assigned to them by the CS project manager and report on the progress to the technical manager. This involves: • designing and implementing software elements, then participating in testing, integrating and validating them, • writing the corresponding documentation, • performing scheduled technical and quality cross-checking controls at the beginning of each phase by means of check-lists made by top management. DEBAT – Development of EAST Based Access Tools
  21. 21. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : 11 2.6 Organisational boundaries and interfaces 2.6.1 Communications with ESRIN Within the project, the responsible persons are the following: ESRIN CS Technical matters Alessandro Ciarlo Laurent Cohen (alessandro.ciarlo@esa.int) (laurent.cohen@c-s.fr) Administrative, financial Luc Govaert Alain Roux matters (luc.govaert@esa.int) (alain.roux@c-s.fr) 2.6.2 Relation to CNES EAST project The DEBAT project is based on EAST existing technologies and mainly on EAST core, EAST Interpreter and Generator and OASIS. CNES has a maintenance contract for EAST technology (at the time being, CS is in charge of this contract). The main contact at CNES concerning EAST technologies is Denis Minguillon (denis.minguillon@cnes.fr). As a matter of fact, some “connection points” are to be foreseen in the course of the project in order to ensure that CNES EAST technology corrections and evolutions (issued from the maintenance contract) and DEBAT EAST evolutions (issued from DEBAT project) will be compatible (the idea is to provide an unique EAST core version at the end of DEBAT, i.e. maintaining compatibility between DEBAT EAST developments and CNES EAST developments, and notably backward compatibility). CNES is ready to deliver the source code of EAST technology to CS (as DEBAT ESA contractor) and to authorise the improvements of this code (as long as it remains an unique core version that CNES would recover at the end of DEBAT). The following approach is proposed: • A delivery of EAST technology is expected at the beginning of the project KOM (sources code, documentation, installation procedures, etc.) for technical analyses/studies. • Another delivery of EAST technology is expected at ATP (start of phase 2) including the corrections/modifications issued from the CNES EAST maintenance contract. • Other possible deliveries could be considered depending on the corrections/evolutions issued from the maintenance contract. For instance, at ATP+4 and FAR-1 (one month before FAR). • Some internal meeting (between CS DEBAT team and CS EAST team) will be held in order to ensure proper and compatible work between the two teams. • As CNES will be involved in the users group, it will also be able to give its appraisal about the orientations of DEBAT. DEBAT – Development of EAST Based Access Tools
  22. 22. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : 12 3. Monitoring and control 3.1 Meeting and reporting 3.1.1 Meetings Project management is based on regular internal and external meetings. External meetings: any meeting taking place with CS and the Customer. During these meeting, CS takes the minutes of the proceedings. These are co-signed by both parties and contain at least: • date and place of meeting, • list of attendees, • agenda of the meeting, • main conclusions of the meeting, • statements of the actions agreed, due dates and responsible, • date and place of the next meeting. The potential attendees receives notice of the meeting as well as the agenda in order to prepare the meeting, at least 5 days before the latter takes place. The documentation required to support decisions to be discussed in the course of the meeting are made available to the ESA technical officer at least five days before the meeting. The frequency of such meeting is between six weeks to two months. Review meetings require in addition the preparation of the documents that are subject to review and acceptance, and the preparation of the milestone report. If applicable, the review is held by slides and demonstrations. Internal meetings: these are the meetings held at CS premises with CS employees. The objective of these meetings is to discuss technical problems and solutions, to monitor and control the progress status, and to plan the work to be achieved. 3.1.2 Reporting CS delivers at the end of each month a Monthly Progress Report containing at least the following elements: • Management information, • Technical status, • Progress since last report, • Delays identified or foreseen, • Corrective actions, • Encountered / anticipated problems, • Updated schedule, • Risk register, DEBAT – Development of EAST Based Access Tools
  23. 23. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : 13 • Actions Items List • Delivery and invoicing status A Milestone Report is to be delivered at each review meeting giving in addition a general plan for the work to be performed in the next stage of the project. 3.2 Schedule reporting and control The schedule (Gantt chart provided by Microsoft Project) will be updated on a regular basis and monthly reported to ESRIN. Monthly Progress Reports will include the updated schedule according to the current progress status of the tasks to be carried out. At any schedule update, an impact analysis will be performed showing notably the impact on the expected deliveries. 3.3 Risk management and register Risks are an inherent element of projects and need continuous attention throughout a project life cycle in order to manage schedule, technical performance and cost. The purpose of risk management is to identify risks as early as possible, adjust the development and integration strategy to mitigate those risks, and develop and implement a risk management process as an integral part of the DEBAT project. The project manager will be in charge of the risk register all the project long. The risk register will be included in the monthly progress reports. Risks are identified during the proposition and will be refined throughout the project and in particular during the specification phase. The following risk register is gathering the risks that have been identified directly from the proposal. Identifier Description Probability Impact Possible action R1 Availability of information Low High The information DEBAT project is strongly based upon should be made efficient collection of information from available to CS as several sources: interviews (users group, soon as possible to selected people for interviews,…), be taken into documentation (selected set of account (at the missions/projects, TM/TC arena, other beginning of the outcome,…), etc. project for the The access to the related information is available considered as critical. documentation). R2 Tight schedule High Medium Pragmatic working There is a risk associated to the shortness of principles should the schedule (the duration of first phase is allow to focus on only 5 months of the total 18 months essential work The project). This can be a too short period to exact scopes of the perform all the required work. studies shall be clearly defined. DEBAT – Development of EAST Based Access Tools
  24. 24. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : 14 4. Licenses issues This section presents, in its first part, principles for the DEBAT development and license, taking into account the CNES property on the EAST/OASIS software, which constitutes an important basis for the DEBAT software. In the second part, this section presents the terms of the proposed license for DEBAT. 4.1 Principles of the DEBAT development and license Hypothesis • The CNES is ready to deliver to CS the source code of EAST/OASIS which is the basis for the DEBAT developments. It is ready to authorise the improvements of EAST/OASIS code in order to integrate DEBAT requirements. This point is to be formalised in a license contract between CS and CNES in the early stages of the project. This license contract will be attached to this Project Management Plan as soon as available. • EAST/OASIS are governed by a license “freeware in binary form”: i.e. that anybody can use or redistribute the EAST/OASIS software in its binary form (without any fee), but the modification of this software is not allowed (the source code is not provided). • The new developments performed in the framework of DEBAT by CS, will be governed by a license “freeware in binary form” (same philosophy as EAST/OASIS current license). Proposal • Each source file specifically developed for DEBAT project is the property of CS. • Each unmodified source file coming from EAST/OASIS is the property of CNES. • For each source file coming from EAST/OASIS which has been modified in the framework of DEBAT, they become the property of CNES. Consequently, the property rights and the applicable license can be summarised as follows: EAST/OASIS files not EAST/OASIS files Files specifically Type of file modified for DEBAT modified for developed for DEBAT project DEBAT project project Property CNES CNES CS SI EAST/OASIS freeware EAST/OASIS CS freeware binary Applicable binary form freeware binary form license form The exhaustive list of the files governed by each license will be made available at the end of DEBAT project. It’s also important to mention that there are no runtime fees associated to the global DEBAT product (freeware approach and no COTS used). DEBAT – Development of EAST Based Access Tools
  25. 25. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : 15 At the end of the project, ESA, CNES and CS will be allowed to diffuse the entire DEBAT software for free in a binary form. CS will provide ESA with a non-exclusive, transferable license of DEBAT (for the code which is property of CS). This license will be extended to CNES. Furthermore, CS commits itself to license subsequent (performed outside the scope of DEBAT contract) versions of DEBAT for free to ESA, ESA’s users and CNES (same conditions as for the initial DEBAT software). 4.2 Terms of the proposed license As a summary, we can say that the DEBAT “freeware-in-binary-form” license (composed of EAST/OASIS license and CS licence) basically allows anybody to use or redistribute the binaries. Modification is not allowed (the source code is not provided). DEBAT – Development of EAST Based Access Tools
  26. 26. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : 16 5. Phase 1 - Analysis and studies phase 5.1 Objectives The main objective of this phase is to identify (through several studies and analysis) the limitations of the current EAST tools and the potential evolutions and enhancements able to respond adequately to the users (current users or new users) requirements. A number of analyses/studies are to be carried out in this first phase: • Requirements collection and technical analysis:  analysing the current EAST limitations and the requirements (interviews, comparison of existing functionalities versus a set of selected projects/missions, taking into account the requirements coming from TM/TC domains),  identifying the enhancements needed and performing their technical analysis,  compiling the expressed limitations and requirements into a wish list of “user requirements”. • DEBAT definition:  performing a trade-off between each ranked expressed “user requirement” (its potential added-value) and its cost,  selecting and constituting the more relevant implementation subset,  proposing an implementation plan for phase 2. • Support to users group:  maintaining close contacts with an users group set-up at the beginning of the project,  reporting to it the orientations, choices, encountered problems, and,  analysing its inputs (suggestions, assessments, …). • Promotion:  supporting a CNES/ESA DEBAT workshop, and,  publishing a Web site for promotion and diffusion purposes. • Some implementations are also foreseen:  Implementation of OASIS type library concept,  Development of the DEBAT framework MMI. DEBAT – Development of EAST Based Access Tools
  27. 27. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : 17 5.2 Work breakdown structure The work breakdown structure of DEBAT phase one is depicted below: Figure 5-5 Phase 1 Work Breakdown Structure DEBAT – Development of EAST Based Access Tools
  28. 28. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : 18 5.3 Development plan, work logic and activities The work logic for phase 1 is depicted in the following figure. Figure 5-6 Analysis and studies phase ( phase 1) The project starts with the “Requirements collections and technical analysis” task (WP-120000). This task includes: • Interviews stage (WP-121000): the interview activities allows to gather users feedback and to get the expected enhancements or limitations expressed by current users or potential new users. • Within current domains of application of EAST technology ( “EAST existing tools family WP-122000), the research for new requirements and limitations is achieved by implementing EAST format descriptions of the following data formats and by analysing the work done and the results obtained in order to identify the limitations and required enhancements:  CryoSat,  Envisat (MERIS, SCIAMACHY),  AMS2,  CDDP (CNES). DEBAT – Development of EAST Based Access Tools
  29. 29. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : 19 • Within the new TM/TC domain (“EAST for TM/TC processing” WP-123000), the research for new requirements and limitations is achieved by:  modelling the generic PUS Service 11 with EAST (directly from the book)  modelling the CryoSat Service 11 starting from the generic description,  and by analysing the work done and results obtained in order to identify the limitations and required enhancements. The compiled wish list issued from previous activities is reviewed and approved in the System Requirements Review - SRR. Some implementations are also to be performed during phase 1 (“Implementations” WP-130000): • Implementation of OASIS types library concept: this new feature appears to be often required by users. Moreover, this function is also of aid in performing the work on TM/TC activities. • DEBAT framework MMI mock-ups: these mock-ups allows to get early users feedback on the future DEBAT MMI. The next step is the “DEBAT definition” task (WP-140000), i.e. the definition of DEBAT implementation subset. The definition process is performed as follows: • A first step allows to define the more relevant implementation subset (to be agreed by ESA during negotiation phase), • The second step covers the preparation of the second phase by providing an overall implementation/diffusion plan and identifying interesting areas of future work (beyond the scope of DEBAT, for instance evolution requirements excluded from the implementation). The “DEBAT definition” task is followed by a negotiation period to agree with ESA the technical contents of the implementation phase. ESA is to provide an Authorisation To Proceed (ATP) before the start of the implementation phase. DEBAT – Development of EAST Based Access Tools
  30. 30. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : 20 5.3.1 Requirements collection and technical analysis The following figure describes the activities to be carried out during the “Requirements collection and technical analysis” activity. For each activity, it shows the inputs as well as the outputs of the tasks to be done. Figure 5-7 Requirements collection and technical analysis work logic DEBAT – Development of EAST Based Access Tools
  31. 31. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : 21 5.3.1.1 Interviews stage The main activities to be carried out during the interview stage are sketched hereafter: Figure 5-8 Phase 1 interviews methodology • The interview preparation allows to define an interview form permitting to express the users feelings and appraisal about EAST technology and its potential evolutions. This form is defined by CS and is approved by ESA before diffusion. This interview form shall at least take into account:  an user-oriented point of view: expression in term of functionalities, limitations and needs including also topics like support, training, promotion, etc.,  a technical point of view (known problems, performance needs, functionalities that could be implemented better, lack of some functions,…) including architectural/design factors (modularity, flexibility, openness, reliability, user-friendliness, …) as well as software quality factors (quality of documentation, …),  a market-perspective point of view including cost-efficiency analysis, gained productivity against other solutions (in-house or commercial products), etc.,  a free opinion column to leave enough freedom to people for expressing less-formalised feedback, This activity will also permit to select the people to be interviewed. The list of the foreseen people is to be defined in the early stages of the project. The interviewed people list would preferably be composed of:  people from the users group,  people from current projects using EAST technology,  people from potentially interested projects (EO projects, TM/TC projects, SCOS-2000, …), DEBAT – Development of EAST Based Access Tools
  32. 32. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : 22  people from CS EAST team with a strong experience in the technology. • The interview performance allows to diffuse and perform the interviews. The preferred way to perform the interview is by meeting the people to be interviewed (or eventually by phone or email). Furthermore, a mission to ESRIN is foreseen in the frame of the proposal in order to meet the current and potential interested users of EAST technology to facilitate (and potentially speed-up) the interview process. • The interview exploitation includes the abstraction, analysis and synthesis of the raw collected forms in order to extract and rationalise the main expressed limitations of EAST technology and the main expected requirements of DEBAT. 5.3.1.2 Identification and technical analysis of required enhancements and limitations This activity shall allow to identify the limitations of existing tools and the required enhancements to be taken into account in the future DEBAT software. The sources of information used as inputs are the following: • In the current fields of application of EAST technology, the research for limitations and new requirements is achieved by implementing data descriptions of some selected data formats as stated in [AD04]. The range of selected projects/missions is the following: CryoSat, Envisat (MERIS, SCIAMACHY), AMS2, CDDP (CNES). • In the fields of possible applications of EAST for TM/TC processing (with peculiar attention to SCOS-2000), the research for limitations and new requirements is achieved by implementing the EAST descriptions of the generic PUS Service 11 and by implementing/specialising this generic description for CryoSat Service 11. • Results coming from other related projects (CNES, ESA, ASTRIUM, others) such as Ariane, Helios, ATV, … using (or potentially interested) shall be considered if available in the early stages of the project. • CS EAST team will be involved in this process so as to optimise it. Our team keeps constant interaction with end users and therefore has a good knowledge of limitations and requirements from both a technical and an user point of view. The results obtained from the implementations of EAST data descriptions done during these activities are gathered in a Technical Note (TN-1 in the diagram Figure 5-7 Requirements collection and technical analysis work logic) covering the technical aspects (theoretical feasibility analyses, preliminary solutions identifying unclear issues or expected problems, critical issues, etc.) and also detailing the methodology used for the requirements collection and technical analysis. 5.3.1.3 Compilation of wish list This task is aimed at compiling with an adequate methodology (abstraction, synthesis, rationalising process, selection process) all the results gathered during the previous tasks in a set of “user requirements” that, if implemented, would be a suitable response to the needs of the projects taken as input. The outputs of this tasks are: • an User Requirements Document (URD) detailing the features that satisfy the identified needs. • a Technical Note (TN-2 in the diagram Figure 5-7 Requirements collection and technical analysis work logic) describing the methodology used to compile the wish list (abstraction methodology, selection criteria tables, …). DEBAT – Development of EAST Based Access Tools
  33. 33. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : 23 5.3.2 Implementations Some implementations are foreseen in the frame of DEBAT Phase 1: • Implementation of OASIS types library concept: the types library concept is aiming at helping users to manage and share common parts of data descriptions (and notably, sharing data types between several data descriptions, function that is not available in the current EAST tools). • DEBAT framework MMI mock-ups: the DEBAT framework MMI is aiming at providing users with a single entry point (highly customisable and very user-friendly) to all the DEBAT tools. 5.3.3 DEBAT definition The following diagram details the main activities and the methodology used for DEBAT definition. This task takes as input the wish list issued from the “Requirements collection and technical analysis” task. Figure 5-9 DEBAT definition work logic DEBAT – Development of EAST Based Access Tools
  34. 34. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : 24 The methodology used for the definition process covers the following steps: • The “Evaluation of wish items” activity starts with the definition of a criteria table for evaluating the added value of each wish item. This criteria table is to be defined in co- operation with the users group and is to be approved by ESA. Once all the criteria are well defined (potentially with priority levels assigned to them), the evaluation of each item in the wish list can be done according to the criteria table, in order to find the “added-value” of each item in the list. This evaluation shall take into account the outcomes from the DEBAT workshop and shall be carried out with close interactions with the users group. The cost of each item has also to be defined. • A “Trade-off” between cost and potential added-value is the logical next step in order to choose among the evaluated items. • The “Constitution of implementation subset” allows the selection of the most cost effective and relevant subset for the implementation. This task also includes the consolidation of external requirements, such as any constraints, validation and verification requirements and interface requirements. Tow outputs are to be produced: DC&V/VR (Design Constraints and Verification Requirements) and IR (Interface Requirements). • The “Preparation of phase 2” covers the production of an Implementation, Diffusion and Validation Plan (IDVP) that gives the suggested logical plan of developments. This plan shall also contain an outline plan for the completion of the data format description analysed during the “Requirements collection and technical analysis” phase, as well as an outline plan for “proof of concepts” activities for the TM/TC application of EAST technology. 5.3.4 Support to user group A small users group made in co-operation with ESA and CNES will follow the project. This users group is intended to provide from an end-user point of view: • its appraisal and assessment of the orientations given to the DEBAT tools (envisaged changes, critical choices), • some suggestions, needs or expected enhancements to be taken into account in the frame of DEBAT or in future areas of work, • its evaluation of the final tools and results. The user group is composed of the following persons: Name Email Affiliation Members Nestor Peccia Nestor.Peccia@esa.int ESA Gian Maria Pinna GianMaria.Pinna@esa.int ESA Eric Monjoux Eric.Monjoux@esa.int ESA Michel Nonon-Latapie Michel.Nonon@cnes.fr CNES Françoise Schiavon Francoise.Schiavon@cnes.fr CNES Thierry Guinle Thierry.Guinle@cnes.fr CNES EAST expert Denis Minguillon Denis.Minguillon@cnes.fr CNES DEBAT – Development of EAST Based Access Tools
  35. 35. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : 25 Co-ordinators Alessandro Ciarlo Alessandro.Ciarlo@esa.int ESA Carlos Guerreiro Carlos.Guerreiro@c-s.fr CS A constant interaction between the users group and CS is required all the project long so as to: • keep the group well informed of the status of the project (changes, choices, design,…), • to actively involve the group when crucial decisions are to be taken (and peculiarly during phase 1 for the requirements collection), • and to efficiently collect and process inputs coming from the group. The users group is assumed to communicate by email. In order to establish and maintain efficient contacts with the users group, the following is envisaged: • the documents produced in the course of the project are diffused to the users group in order to get its appraisal and early feedback (when possible the draft versions of the documents will be made available to the users group in order to get its early comments), • periodic reports gathering major information (orientations, choices, design,…) are sent to the group (frequency is about one month), • the users group is invited to attend the major milestones reviews (e.g. SRR, PRD, CDR, …) in order to be actively involved in the project, • a mailing-list mechanism can be set-up in order to track the exchanges between the users group and the DEBAT team: these exchanges could be published in a private area on the DEBAT Web site in order to allow an easy access for the users group. 5.3.5 Promotion 5.3.5.1 Support to workshop A workshop at ESTEC is foreseen around the end of phase 1 to make the interested community aware of EAST tools and DEBAT enhancements derived from this project. CS will contribute to this workshop providing presentations about the outcome of the requirements investigations and the foreseen developments, and collecting some early user feedback, as well as providing some technical support (publication of collected presentation on the Web and possibly short demonstrations). 5.3.5.2 Project Web pages A Web site for ensuring the promotion of EAST/DEBAT technology has to published on an ESA server in order to illustrate the objectives and context of DEBAT project, as well as the progress and outputs of the activities. The DEBAT Web site will be updated all the project long as necessary. The plan for content and update schedule of the project Web pages is described here below. A small set of pages will be published on an ESA Web server following the ESA guidelines and templates. These pages will contain at least the following sections: DEBAT – Development of EAST Based Access Tools
  36. 36. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : 26 • Objectives : describing briefly the objectives of DEBAT, • Context : presenting the context of the project (EAST technology and history), • User Group : presenting the user group, its role and responsibilities, • How it works : describing the working principles of EAST / DEBAT tools, • Documentation : pointing to the general documentation needed to understand the project and the technologies involved. These pages will remain on the ESA Web server: they describe introductory information about the project. These pages will be made available (published) for the end of October. These pages will point to the CNES EAST site allowing to get more detailed information about the current EAST tools. A more detailed set of pages will also be set-up. These pages will be published on a CS Web server as soon as it will be available (probably, at the beginning of year 2003). Until this server is available, these pages will be published on a temporary ESA Web server, and will be then moved to the CS Web server. These pages will contain the following sections: • News : giving the latest news of the project, • Context : giving the context of the project and its organisation, • Expression of requirements: to let the users express their requirements about the DEBAT software, • Publications : giving access to the documents relative to the project, • Downloads : to download the DEBAT tools and associated documentation, the demonstration kit, … • Tools on line : on-line demonstrations of the DEBAT tools suite, • FAQ • Site Map • Help and contacts A first version of these pages will be published for the M2 milestone. A consolidated version of these pages is expected for the SRR review. DEBAT – Development of EAST Based Access Tools
  37. 37. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : 27 5.4 Schedule, meetings and deliveries 5.4.1 Schedule The following picture details the schedule of Phase 1 (this schedule is generated with Microsoft Project): Figure 5-10 Detailed schedule of DEBAT Phase 1 5.4.2 Meetings The following table details the meetings in the first phase of the project. It also indicates the location and the duration of each meeting. Duration Meeting Purpose Date & Location (days) M0 KOM Kick Off Meeting 1 TO (ESRIN) 17/09/2002 M1 Interviews at ESRIN 3 TO+1 (ESRIN) 17/10/2002 M2 Progress meeting 1 TO+2 (CS)13/11/2002 M3 SRR - System Requirements Review 1 TO+4 (CS) 07/01/2003 DEBAT – Development of EAST Based Access Tools
  38. 38. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : 28 M4 DEBAT Workshop 3 TO+5 (ESTEC) 29-31/01/2003 M5 End of phase 1 meeting 1 TO+5,5 (CS)14/02/2003 5.4.3 CS Deliveries and Customer Furnished Items The table below details the deliveries to be produced by CS and the "customer furnished items" to be made available to CS. Meeting CS deliveries ESRIN deliveries M0 KOM Documentation/samples of data for: CryoSat, PMP (first issue at TO+1) Envisat (MERIS, SCIAMACHY), AMS2, PAP (first issue at TO+1) CDDP. Documentation for PUS Service 11 and CryoSat Service 11. Initial list of members for users group Initial list of target people for interviews (ESRIN) ESA web pages templates or guidelines Outcomes from related projects (if available) M1 Interviews at ESRIN Availability of selected target people for PMP first issue interviews at ESRIN. PAP first issue M2 Progress Progress Report M3 SRR (System Requirements Review) “Requirements Collection Technical Note” Preliminary EAST descriptions produced during technical analysis (if any) URD “Selection Process Methodology Technical Note” Milestone report Product Assurance Report M4 Workshop at ESTEC CS Presentations The organisation of the workshop is done by Demonstrations (if any) ESA/CNES. M5 End of P1 meeting OASIS software enhanced with the type library concept DEBAT framework MMI mock- ups SRD Implementation Plan DEBAT – Development of EAST Based Access Tools
  39. 39. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : 29 Meeting CS deliveries ESRIN deliveries Web pages Milestone report Product Assurance Report The contents of each deliverable document is given in the table below for each review. The contents of the documents have been tailored according to ESRIN Statement of Work [AD1] from the ECSS-E-40-B standards [AD5]. Customer End of Package Document Requirement SRR PDR CDR AR approval P1 File on file User Requirements X URD URD Document Functions and performance X SRD SRD RB requirements of the system Design constraints and X SRD verification and validation SRD RB requirements SRD Interface requirements X SRD RB 5.5 Work Packages Description The work-packages for Phase 1 are fully described in the CS proposal for Phase 1 [AD3].. DEBAT – Development of EAST Based Access Tools
  40. 40. Reference : SS/DEBAT/PMP DEBAT Issue. : 1.3 Project Management Plan Date : 13/11/2003 Page : 30 6. Phase 2 - Implementation phase 6.1 Objectives The phase 2 of the DEBAT project is the implementation phase: it covers the design, implementation, validation and demonstration of the developments carried out during the whole DEBAT project. The following schema presents how the phase 2 is integrated in the whole DEBAT project and in particular, it shows the previous activities. These activities allowed to identify the subset of user requirements to be implemented during the phase 2 and to define the implementation, validation and diffusion plans for the DEBAT software. Figure 6-11 Outputs of DEBAT phase 1 The research for the requirements had three sources: • Interviews stage [RD2]: the interview activities allow to gather users feedback and to get the expected enhancements or limitations expressed by current users or potential new users. • EAST for TM/TC processing study [RD3]: the research for requirements is achieved by modelling the generic PUS Service 11 and the CryoSat Service 11, and by analysing the work done and results obtained. A focus is also done on the SCOS-2000 Mission Control Centre in order to identify the requirements related to the potential use of DEBAT within SCOS-2000. • EAST current applications study [RD4]: the research for requirements is achieved by modelling some data products (CryoSat, Envisat, AMS2) and by analysing the work done and the results obtained. The “Requirements Collection Technical Note” [RD5] gathers all requirements identified in the previous stages. Then, the following documents describing the DEBAT software requirements and implementation have been produced: • The User Requirements Document [RD6] details the technical objectives of the DEBAT software by defining the user requirements as a preliminary phase to the software development life cycle. The user requirements are both extracted from the functionalities of DEBAT – Development of EAST Based Access Tools

×