OCDT-DEE. Open Concurrent Design Tool Deployment, Enhancement and Exploitation

Transcription

1 OCDT-DEE Open Concurrent Design Tool Deployment, Enhancement and Exploitation

2 OCDT Background OCDT developed to provide ESA with an upgraded infrastructure built around the ECSS-E-TM data model support Concurrent Design (CD) activities at ESA and other organisations exclusively built on top of freely available open source software components distributed to the user community under an ESA Community Open Source License. Collaboration and distribution is facilitated by the OCDT Community Portal which will provide users with information and access to OCDT itself. support infrastructure setup and operations backlog items development 2

3 ESA ITT AO/1-7812/14/NL/GLC ESA ITT AO/1-7812/14/NL/GLC : OCDT-DEE = Open Concurrent Design Server Deployment, Enhancement & Exploitation ESA ITT AO/1-7812/14/NL/GLC Customer: ESA TEC SYE (ESA Concurrent Design Facility) I am glad to notify you of the Agency's intention to place the activity in subject of this e- mail with RHEA Winning Proposal Team: Prime: RHEA System S.A. (Belgium) Sub: Critical Software (CSW)(Portugal) Kickoff: July 22nd 2014 Duration: Phase 1: 1 year; Phase 2: 1 year 3

4 OCDT-DEE Objectives To create an operational environment in which the OCDT software product can be maintained and distributed to all users in the community of concurrent design centers, under an ESA Community Open Source Software license. To establish support to end-users through on-line assistance, getting started materials and training courses. To operate and maintain a software problem reporting infrastructure, defect resolution and upgrade service. To enhance, promote and realise the use of OCDT for concurrent design of space systems, through active collection and processing of feedback from its users, and implementation of new features. To promote and facilitate the contribution by partners to the enhancement and evolution of the OCDT product, including support to further evolution of the ECSS-E- TM data model. To realise the integration with Domain Specific Tools (DSTs) that are used in concurrent design activities. To support ESA in strengthening and growing the community of concurrent design centers in order to increase the capabilities and competitiveness of the European space sector. Here we focus on the facilities/functionalities put in place to enable the objectives geared towards the communication and interaction with the User community. 4

5 OCDT User Community The OCDT community consists of end users and developers who are interested to share and exchange information, experiences, models, and tools related to concurrent engineering for space applications. Only persons working for an organisation that legally resides in an ESA member state or cooperating state qualify to be a member of the OCDT community. Community members have access to and share information on the subject of OCDT via the OCDT community portal, and as such, members of the community are registered on this portal. The governing body for the OCDT that will coordinate and harmonize feedback and needs of the concurrent design user community is the Concurrent Design User Board (CDUB) The members of the CDUB are representatives of the OCDT user community and it is to be expected to have members from, but not limited to: National agencies such as CNES, DLR, ASI, CSA, Prime integrators such as Airbus Defence and space, Thales Alenia Space and OHB Academic Concurrent Design Centres such as EPFL, TUDelft, University of Stuttgart, University of Lisbon, etc. Concurrent Design service providers, such as RHEA Key engineering software developers, such as RHEA and CSW. 5

6 OCDT Community Portal The OCDT Community Portal is the one stop environment for OCDT users (interested community members, end-users, software developers, administrators etc.). 6

7 OCDT Helpdesk Current status: Information for developpers and users in wiki format You have to look to find Forum with possibility to open and answer threads Downloads of e.g.: OCDT software Install docs Licences Envisaged/considered Improvements: Redmine extensions to improve knowledgebase and searching e.g. Q&A and FAQ functionality, or Joomla Helpdesk and Easy Discuss (StackOverflow-like). Workflow and user manual (for user and operator) , phone, skype Instant chat Users: Basic/Power: users having the skills to adapt and extend the OCDT environment and software, this also includes the (open source) software developers from the community. CD Engineers/Experts members of a CD study team, i.e. DE, SE, SEA and TL. Administrators: (e.g. at the industry/academia premises) user account management, IT infrastructure setup, maintenance, etc. Interested parties: those OCDT Portal visitors who want to know more in general about OCDT. 7

8 OCDT Helpdesk First Line support: as much self-service as possible. Information shall be easy to find, easy to use and presented in an intuitive manner. User manual (procedures to follow), FAQ, workflow, tips & tricks, regularly occurring issues and proposed solutions, and other knowledge bases, like training material. Second Line support: respond to specific user requests individually on topics for which either no answer could be found in the first line support or when hands-on support is needed like e.g. software installation problems, configuration problems, perceived defects in OCDT components, etc. Issues will be placed in the issue tracker. Credit to: Credit to Credit to 8

9 OCDT Open Source Development Environment Original Status: Redmine Issue tracker, Backlogs & Kanban Git First improvements: GitLab SonarQube Jenkins 9

10 OCDT Open Source Development Environment 10

11 OCDT Open Source Development Environment For the software contributors a workflow will be provided as well as a full description of the suggested development tools. Credit to: Credit to: Credit to: 11

12 Open Source Why? lower the threshold to adopt OCDT and CD methodology. facilitate and promote the community members to contribute to the enhancements and evolution of the OCDT and ECSS-E-TM Reuse contributions by the rest of its members promoting the collaboration and sharing of engineering knowledge and knowhow. The OCDT product is : setup as open-source software and is intended to be distributed under an ESA community open-source license to the user community, consisting of organisations that must be seated in one of the ESA Member States or cooperating states. comprised of only freely available and open-source software licensed components which are compatible to ESA s community open-source licenses. distributed according to two kinds of ESA community open-source license types; type 2, a so-called weak copyleft license and type 3, a so-called permissive license ; the license types are applicable to the different parts of the OCDT. 12

13 Training This project also includes the creation of an OCDT training and related material. The training envisages CD experienced, community member s domain experts i.e. member of a concurrent design study team with particular skills in and knowledge of a specific domain. The training will be given by a team of 2, i.e. the trainer and the trainer assistant. A training scenario/script will be created geared towards taking the audience as much as possible through hands-on exercises. A representative space mission design will be selected and scoped to fit the training purpose after which the model of this worked example will be implemented in the OCDT. Location envisaged is ESTEC Scheduled May

14 Schedule The OCDT Community Portal exists and is already accessible for OCDT Community Members in its present form/state to read and download documentation as well as the OCDT software. The OCDT-DEE project started end of July 2014, the schedule foresees the following elements to be fully up and fully running including all required new features at MTR1 (i.e. KO+6 months = End Jan2015). OCDT Community Portal OCDT On-Line Helpdesk System Operational OCDT Software Development Environment After the MTR1 most effort will be put in the further development of the OCDT software as well as domain specific tool integrations, which are over 50% of this contract value but not the scope of this paper. The project has a duration of 2 years. 14

15 Conclusion It is our (ESA, CSW & RHEA) firm believe that with this infrastructure in place the OCDT User Community, it being engineers, interested parties or software developers will have a professional one-stop shop for all their OCDT needs, questions and wishes. This contract is a testament of recognition of RHEA s Concurrent Design and Engineering expertise and software design and development competences. RHEA fully incorporates the OCDT and related support services into the RHEA product portfolio, in addition to and next to the RHEA proprietary Concurrent Design Tool (CDP ). --END-- 15

16 THANK YOU

17 WBS Phase1 Phase2 17

18 Deliverable documentation Doc.# File DRD Title Availability D01 MGT SDP OCDT-DEE Software Development Plan IR, updates at MTR1, FR1 D04 DDF SDD OCDT On-Line Helpdesk Software Design IR Document D05 DDF SUM OCDT On-Line Helpdesk Software User IR Manual D06 DJF N.A. Technical Note on Review of the OCDT Open MTR1 Source Software Development Environment and Proposed Improvements D07 DDF SUM OCDT Software Developers Manual MTR1 D08 DJF SVR OCDT Software Verification Report MTR1, updates at FR1, MTR2, FR2 D09 DDF SDD OCDT-<tool-name> DST Software Design Document At review for selected <toolname> integration (FR1, MTR2 or FR2) D10 DDF SUM OCDT-<tool-name> DST Software User Manual At review for selected <toolname> integration (FR1, MTR2 or FR2) D11 DJF SVR OCDT-<tool-name> DST Software Verification Report D12 DDF N.A. OCDT Training Course Material MTR1 D13 MGT N.A. Report on executed training course FR1, FR2 At review for selected <toolname> integration (FR1, MTR2 or FR2) 18

19 Deliverable Software SW.#z Title Programming Language/ platform Availability SW01 OCDT Community Portal Operational Ref. OCDT portal components MTR1, FR1, MTR2, FR2 SW02 OCDT On-Line Helpdesk System4 Redmine (TBC) MTR1 SW03 Operational OCDT Software Development Ref. OCDT portal components MTR1 Environment SW04 OCDT Persistent Data Store PSQL (PostgreSQL) Updates as agreed per SCRUM sprints SW05 OCDT Web Services Processor Coffeescript, Javascript Updates as agreed per SCRUM sprints SW06 OCDT Client Class Libraries C# Updates as agreed per SCRUM sprints SW07 OCDT ConCORDE end-user tool (add-in to C# Updates as agreed per SCRUM sprints MS Excel 2010) SW08 OCDT C# DST-SDK C# Updates as agreed per SCRUM sprints SW09 OCDT Python DST-SDK Python Updates as agreed per SCRUM sprints SW10 OCDT xmi_verter Python Updates as agreed per SCRUM sprints SW11 OCDT Community Portal Prototype of improvements Ref. OCDT portal components As agreed per SCRUM sprints SW12 OCDT-<tool-name> Adaptor(s) for selected DST(s) C# and Python At review for selected <tool-name> integration (FR1, MTR2 or FR2) 19

20 Phase 1 Schedule 20

21 Phase 1 Schedule (2) 21

22 Phase 2 Schedule 22

23 Phase 2 Schedule (2) 23