1 / 91

DEBAT - Critical Design Review 14, 15 October 2003

DEBAT - Critical Design Review 14, 15 October 2003. Agenda.

bena
Download Presentation

DEBAT - Critical Design Review 14, 15 October 2003

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DEBAT - Critical Design Review 14, 15 October 2003

  2. Agenda 14th October Afternoon14.30 - 15.00 Project Status15.00 - 15.15 Product Assurance Report15.15 - 17.00 Presentation of the principles of the Architectural & Detailed Design15th October Morning9.00 - 9.30 Software Verification & Validation Tests presentation9.30 - 10.00 Implementation Schedule Presentation10.00 - 12.00 Modeller Presentation

  3. Project status 14.30 – 15.00

  4. Project Organisation • Three main changes have been done into the project organisation: • 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. • Maud Granet, the project quality manager has left CS during this month. Josiane Denailhac is now the new project quality manager.

  5. Project Organisation • Current team

  6. Project Organisation • New team

  7. Project Organisation

  8. CDR Deliveries • The following deliveries were made during the month of September: • Architectural Design Document 1.1 SS/DEBAT/ADD describing the modules structure of the application, theirs relations, the sketches of GUI, menu trees, and the diagram of the main UML diagrams classes. • Design Technical Note 1.0 SS/DEBAT/DD_TN gathering all the background information required to understand the design, but that does not belong to the design proper (choices made, explanations, XML query language, etc …) • Interface Control Document 1.1 SS/DEBAT/ICD describing the interfaces of the APIs. • EAST Language Changes 1.0 SS/DEBAT/ELC describing the changes made to the EAST language; this will be the basis for a proposal to CCSDS to update the EAST standard • The Detailed Design Document 1.0 SS/DEBAT/DDD is a set of HTML pages directly generated from the code. The code, is in fact initialised (main classes, main functions, …), and sufficiently commented. The HTML generation is based on the comments. A Word version was generated (only to print it). • The Software Verification and Validation Plan 1.1 SS/DEBAT/SVVP describes the validation plan with the methodology, the environment and the data necessary

  9. Progress status • The work performed from PDR has been mainly focused on the Architectural design and Detail design, and on the implementation of the 2nd iteration of the new Data Modeller. • Architectural design and Detail design are completed. • Second iteration of the new DEBAT Modeller is nearly completed (a demo is planned tomorrow morning)

  10. Progress status • Detailed design

  11. Progress status • New Data Modeller

  12. Future work (from CDR to FAR) • Implementation & Unit tests • Integration & FAT

  13. Product Assurance Report 15.00 – 15.15

  14. Introduction • The aim of this presentation is to describe the quality actions performed from the beginning of the phase 2 and until the Critical Design Review. • Several quality actions were carried out : • Building of the templates for the header of Java & ADA classes, • Reminding the development team of the quality devices (files header comments, coding rules and metrics bounds), • Providing support for documentation (summary, plan type , ), • Controlling code and documentation, • Checking of the matrix of conformity of the documentation, • Participating in progress meetings.

  15. Let's focus on the Modeller control code • According to the Product Assurance Plan, a Modeller source code per language and per individual was checked in relation to the project coding standards. • The Modeller code control reveals that : • Comments frequency is better than the first control in July, • Some methods have a cyclomatic number ( the “V(G)” quantifies the complexity of the code structure) upper than the limit (max value = 30).

  16. Let's focus on - Controlling documentation for delivery • According to the Product Assurance Plan, five documents were controlled before being delivered: • Any quality comments were done on the documents. So they were approved by the quality manager.

  17. Let's focus on conclusion • The Modeller produced code respects the number of instruction and comments frequency whereas VG bounds is higher than its bound for few functions/methods. Thanks to the development team which undertakes to lower the VG, the quality of the produced code is satisfying.

  18. Architecture Design of DEBAT 15.15 – 16.00

  19. Functional architecture

  20. DEBAT functional architecture

  21. Functions of the improved EAST core • The existing capabilities are left unchanged (backward compatibility) • Several significant improvements are added • Addition of calculation capabilities • Addition of enhanced data checking capabilities • Addition of the definition of "external functions"  • Performance improvements • API • Updates and enhancements of the ADA, C/C++ and Fortran APIs • Creation of the Java API

  22. Functions of the DEBAT environment DEBAT Integrated Environment Framework, plug-in system & project management support DEBAT Modeller Definition of the logical & physical model, generation of documentation in HTML, PDF and Word formats, type library support DEBAT Producer & Editor Generation, reading, edition of data products DEBAT Extractor & Querying Search, query and extract values of a data product DEBAT Utilities Ascii-dump, data checker, data models comparison tool DEBAT Post-Processing Tools 2D visualisation, quick-look generator, data transformer DEBAT Packager DEBAT Local Web Site & Web Services

  23. Software architecture

  24. System design – Components decomposition view

  25. System design – Dependencies (1)

  26. System Design – Dependencies (2)

  27. System Design – Dependencies (3)

  28. General Features • Function • Installation • Internationalisation • Online help • Screenshot function • Printing capabilities • Interfaces • Help information stored in jar-packaged help set files • XML configuration file defining the help configuration • Property files and image files for the internationalisation • XML configuration file defining the configuration of the installation

  29. Integrated Environment • Function • Framework: user-friendly GUI to access the set of DEBAT functions • Plug-insystem: provide users with a mechanism to extend/modify the suite of tools • Project Management: provides a virtual organisation of the file system • Interfaces • XML file to store the configuration of the Framework • XML file to store the definition of the projects • Text file to store the messages sent to the logbook • Interfaces with the plugins • load Java plug-in and black box plug-in (i.e. written in another language) • communicate with them

  30. Integrated Environment – Framework GUI

  31. Integrated Environment – Plugin System

  32. Integrated Environment – Project Management

  33. EAST Core • Interpreter • Data reading (from files, sockets, stdin) • Support for multi-file data products • Direct access to data • Support for external functions • Data checking • Computed constraints • Several levels of checking • Queries Handler • Data Generator • Data writing (to files, socket, stdout) • Support for integer & real formats • Support for external functions • Direct access • Data generation • API

  34. EAST Core – Interfaces • Interfaces • EAST description file describing the format of the data products • EAST core configuration file (directory path and logbook conf.) • Data files and data flows (socket/stdin/stdout) • FRT file containing for each element the format to apply • Directives file containing directives to generate a data block • External Java functions allowing modifying the behaviour of EAST at runtime • External checking constraints

  35. Modeller • Function • MMI allowing users to model data formats • Generation of EAST/DEDSL • New modeling capabilities • Support for real/integer formats • Support for default value • Calculation capabilities • Support for external functions • Generation of customisable documents in RTF, PDF and HTML formats • Type library

  36. Modeller – Interfaces

  37. Modeller – Components dependencies

  38. DPE • Function • Data product consultation, generation, edition, checking and storage • Search capabilities • Data model display • Interfaces • Data model (XML-IF file) • Data files and flows (socket, stdin, stdout) • Directives files • Check results

  39. DPE – Components dependencies

  40. DPE - GUI

  41. DEQ • Function • Generation of XML views of data products • Creation and processing of XML-like queries • Search functions • Data extraction • Batch processing • Data model display • Interfaces • XML-IF files • Data files or flows • Queries files • XML data files

  42. DEQ – Components dependencies

  43. DEQ - GUI

  44. Utilities • Function • Ascii-Dump: a small utility used to generate an ascii representation of a data product in a simple tabular form or in XML • Data-Checker: a standalone tool that is able to verify if a data product is compliant with a given EAST description • Comparison Tool: compute and display the differences between two data models • Interfaces • EAST description file • XML-IF data model • Data file • Text dump and XML dump • Checking results file • XML file containing the differences between the XML-IF data models

  45. Utilities – Data Checker

  46. Utilities – Ascii Dump

  47. Utilities – Comparison Tool

  48. Post-Processing Tool • Function • 2D visualisation tool able to plot the data contained within a data product • Quick-look generator able to generate quick-looks from raw image data • Data transformer able to transform raw binary data products into XML documents in a customisable way • Interfaces • 2D visualisation • Graphs definitions • Data (static data or "live" data) • Jpeg or png images • Quick look generator • Raw data • EAST description file • Quick-look image • Data Transformer • Raw data • EAST description • Transformation configuration • XML file

  49. Post-Processing Tool – 2D visualisation

  50. Post-Processing Tool – Quick-look generator

More Related