Project Management Plan / Reference : SS/DEBAT/PMP
Issue. : 1.2
Date : 08/07/2003
Page : 1
DEBAT Development of EAST Based Access Tools
Project Management Plan
Contract: 16562/02/I-LG
Reference: SS/DEBAT/PMP
Issue: 1.2
Date: 08/07/2003
Prepared by:Carlos Guerreiro / Date:
Checked by:
Maud Granet / Date:
Approved by:
Alain Roussel / Date:
DEBAT – Development of EAST Based Access Tools
/ DEBATProject Management Plan / Reference : SS/DEBAT/PMP
Issue. : 1.2
Date : 08/07/2003
Page : 1
Document Status Sheet
Document Title / DEBAT Project Management PlanDocument Reference Number / SS/DEBAT/PMP
Issue / Revision / Date / Reason for change
1 / 0 / 15/10/2002 / First issue of the PMP for Phase 1 of the project
1 / 1 / 31/10/2002 / Integration of comments from ESA
1 / 2 / 08/07/2003 / Updated for Phase 2
Document Change Records
Document Title / DEBAT Project Management PlanDocument Reference Number / SS/DEBAT/PMP
Document Issue/Revision Number / 1.0
Page / Paragraph / Reason for change
All / First issue
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
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
Table of contents
Document Status Sheet
Document Change Records
Table of contents
Table of figures
Acronyms and abbreviations
Applicable Documents
Reference Documents
1. Introduction
1.1 Project overview
1.2 Objectives of the document
1.3 Structure of the document
1.4 Evolution of the Project Management Plan
2. Project organisation
2.1 Process model
2.2 Overall project schedule and milestones
2.3 Facilities and resources
2.4 Project organisation chart
2.5 Organisational roles and responsibilities
2.5.1 The Project Director
2.5.2 The Project Manager
2.5.3 The technical manager
2.5.4 The Experts
2.5.5 The Development Team
2.6 Organisational boundaries and interfaces
2.6.1 Communications with ESRIN
2.6.2 Relation to CNES EAST project
3. Monitoring and control
3.1 Meeting and reporting
3.1.1 Meetings
3.1.2 Reporting
3.2 Schedule reporting and control
3.3 Risk management and register
4. Licenses issues
4.1 Principles of the DEBAT development and license
4.2 Terms of the proposed license
5. Phase 1 - Analysis and studies phase
5.1 Objectives
5.2 Work breakdown structure
5.3 Development plan, work logic and activities
5.3.1 Requirements collection and technical analysis
5.3.2 Implementations
5.3.3 DEBAT definition
5.3.4 Support to user group
5.3.5 Promotion
5.4 Schedule, meetings and deliveries
5.4.1 Schedule
5.4.2 Meetings
5.4.3 CS Deliveries and Customer Furnished Items
5.5 Work Packages Description
6. Phase 2 - Implementation phase
6.1 Objectives
6.2 Work breakdown structure
6.3 Work logic and activities
6.3.1 Software specifications and architectural design
6.3.2 Implementation, integration and acceptance tests
6.3.3 Promotion
6.3.4 Concept Validation
6.3.5 Proposals for CCSDS standards updates
6.3.6 Demonstration
6.3.7 Support to user group
6.3.8 Final presentation
6.4 Schedule, meetings and deliveries
6.4.1 Schedule
6.4.2 Meetings
6.4.3 CS Deliveries and Customer Furnished Items
6.5 Work Packages Descriptions
7. Warranty phase
7.1 Warranty principles
7.2 Warranty activities
8. Documentation tree
Table of figures
Figure 21 Major milestones
Figure 22 Overall project schedule and milestones
Figure 23 Project Organisation chart
Figure 51 Phase 1 Work Breakdown Structure
Figure 52 Analysis and studies phase ( phase 1)
Figure 53 Requirements collection and technical analysis work logic
Figure 54 Phase 1 interviews methodology
Figure 55 DEBAT definition work logic
Figure 56 Detailed schedule of DEBAT Phase 1
Figure 61 Outputs of DEBAT phase 1
Figure 62 Phase 2 WBS
Figure 63 Implementation plan for phase 2
Figure 64: Software Specifications & Architectural Design work logic
Figure 65: Implementation, integration & acceptance tests work logic
Figure 66: Detailed design work logic
Acronyms and abbreviations
ADD Architectural Design Document
AMSArchive Management System
APIApplication Program Interface
ARAcceptance Review
ATPAuthorisation To Proceed
CAControl Authority
CAIDControl Authority Identifier
CAOControl Authority Office
CAOSControl Authority Office System
CDFCommon Data Format
CDRCritical Design Review
CEOSCommittee on Earth Observation Science
CFI Customer Furnished Item
CNESCentre National D’Etudes Spatiales (French Space Agency)
COTS Commercial Off The Shelf
CCSDS Consultative Committee for Space Data Systems
DEALDisplay EAST Access List
DEBATDevelopment of EAST Based Access Tools
DEBAT-DMDEBAT Data Modeller
DEBAT-DPEDEBAT Data Producer & Editor
DEBAT-DEQDEBAT Data Extractor & Querying
DEBAT-PPTDEBAT Post Processing Tools
DEBAT-UTDEBAT Utilities
DDRData Description Record
DDUData Description Unit
DDFDesign Definition File
DEDData Entity Dictionary
DEDSLData Entity Description Specification Language
DEWData Extractor Wizard
DIPDissemination Information Package
DJFDesign Justification File
DUWData Update Wizard
DWDEBAT Workshop
EASTEnhanced ADA Sub SeT
ECSSEuropean Cooperation for Space Standardization
EOEarth Observation
ESAEuropean Space Agency
ESRINEuropean Space Research INstitute
ERS European Remote Sensing satellite
ESAEuropean Space Agency
EVAESA Virtual Archive
FAFinal Acceptance
FAQFrequently Asked Question
FARFactory Acceptance Review
FATFactory Acceptance Tests
FDIRFault Detection, Isolation and Recovery
FPFinal Presentation
FPAFinal Presentation and Acceptance
GUIGraphical User Interface
HDFHierarchical Data Format
HTMLHyper Text Mark-up Language
HTTPHyper Text Transfer Protocol
HW Hardware
ICDInterface Control Document
IDVPImplementation, Diffusion and Validation Plan
IRInterface Requirements
ITTInvitation To Tender
JSPJava Server Pages
KOMKick Off Meeting
MACAOMember Agency Control Authority Office
MMIMan-Machine Interface
NASNetwork Attached Storage
OAIS Open Archival Information System
OASISSpace Data Modelling Help Tool
OSATOn Site installation and Acceptance Tests
PAPProduct Assurance Plan
PDRPreliminary Design Review
PMPProject Management Plan
PUSPacket Utilisation Standard
PVLParameter Value Language
RBRequirements Baseline
RID Review Item Discrepancy
RTDResearch and Technology Development
SCMP Software Configuration Management Plan
SIPSubmission Information Package
SOAPSimple Object Access Protocol
SOWStatement of Work
SPMP Software Project Management Plan
SRRSystem Requirements Review
SVGScalable Vector Graphic
TM/TCTelemetry / Telecommand
TSTechnical Specifications
UDDIUniversal Description Discovery and Integration
URDUser Requirements Document
WSDLWeb Service Description Language
WWWWorld Wide Web
XMLeXtensible Mark-up Language
XSLeXtensible Stylesheet Language
XSLTeXtensible Stylesheet Language Transformation
Applicable Documents
Title / Issue / Date / ReferenceAD1 / ESRIN SOW “Development of EAST Based Access Tools” / 1.1 / 18/03/2002 / GSPS-RTDA-EOAD-SW-02-0001
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 Standards – Software / ECSS-E-40B
AD6 / ECSS - Space Engineering Standards - Software Product Assurance / ECSS-Q-80B
AD7 / CS SI Proposal for Phase 2 / March 2003 / CSSI/111-1/CG/PKV/3/140
AD8 / Minutes of Phase 2 Kick-off meeting (Authorisation To Proceed) / 30/04/2003 / /CRR/SS/DEBAT/006
Reference Documents
Title / Issue / Date / ReferenceRD1 / 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 Technical Note / 1.0 / 14/01/2003 / SS/DEBAT/TMTC_TN
RD4 / EAST current applications Technical Note / 1.0 / 14/01/2003 / SS/DEBAT/EAST_TN
RD5 / Requirements Collection Technical Note / 1.0 / 14/01/2003 / SS/DEBAT/RC_TN
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 Technical Note / 1.2 / 10/03/2003 / SS/DEBAT/SPM_TN
RD9 / Implementation, Diffusion and Validation Plan / 1.1 / 10/03/2003 / SS/DEBAT/IDVP
DEBAT – Development of EAST Based Access Tools
/ DEBATProject Management Plan / Reference : SS/DEBAT/PMP
Issue. : 1.2
Date : 08/07/2003
Page : 1
1.Introduction
1.1Project 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 toolscovering 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.2Objectives 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.3Structure 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
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.4Evolution 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.
2.Project organisation
2.1Process 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.2Overall 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 21 Major milestones
The following figure gives the project overall schedule:
Figure 22Overall project schedule and milestones
The following table gives the major milestones of the project.
Meeting / PurposeM0 - 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 warranty of 6 months.
2.3Facilities 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.4Project organisation chart
The following diagram presents the project organisation chart:
Figure 23 Project Organisation chart
The key personnel is the following:
- 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 person / Function within the project / Competence fields / Amount of time dedicated to the project (%)Alain ROUSSEL / Project Director / 19 years experience on project management. / Support to Project Management
Carlos GUERREIRO / Project Manager / Architectures, JAVA/CORBA: he’s currently in charge of the Space Studies Direction of Projects. / Project Management
Laurent COHEN / Technical Manager and Responsible for Advanced Technologies / Advanced technologies (Java, Web Services) / 100%
Frédéric BERRIRI / Responsible for EAST/OASIS core technologies / EAST/OASIS: he is currently the EAST project manager (CNES maintenance contract) / 75% DEBAT project
25 % EAST Maintenance Contract (CNES)
Olivier QUEYRUT / Responsible for TM/TC activities / TM/TC, SCOS-2000. / 100%
Claire PELLIZZARI / EAST expert / EAST/OASIS: she has more than 8 years experience of EAST. / 50% DEBAT project
50% EAST Maintenance Contract (CNES)
Jérôme FERREIRA / Design/Development team / EAST/OASIS: he has been working on EAST/OASIS since 09/2001 (EAST/OASIS CNES maintenance contract). / 75% DEBAT project
25% EAST Maintenance Contract (CNES)
Jérôme CANDAT / Design/Development team / XML/JAVA / 100%
Luc MAISONOBE / Freeware expert / Specialist of the freeware/open source issues. / 1 day per month
2.5Organisational roles and responsibilities
2.5.1The 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.2The 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:
- 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.3The 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.4The 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.