Transcript Document
International Workshop on Fact-Oriented Modeling ORM 2014 The Fact Based Modelling Unifying System FAMOUS Towards implementing ECSS-E-TM-10-23 Serge Valera European Space Agency 22 September 2014 FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 1 Article 2 of the ESA Convention “To provide for and promote, for exclusively peaceful purposes, cooperation among European states in space research and technology and their space applications.” FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 2 ESA Member States & Cooperating States ESA now has 20 Member States. The national bodies responsible for space in these countries sit on ESA’s governing Council. Canada also sits on the Council and takes part in some projects under a Cooperation Agreement. Hungary, Estonia, Latvia and Slovenia are participating in the Plan for European Cooperating States (PECS), while other countries are in negotiation with ESA about joining this initiative. FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 3 ESA’s presence worldwide EAC ESTEC (Noordwijk) (Cologne) Salmijaervi (Kiruna) Harwell ESA HQ (Paris) Establishments Offices ESOC (Darmstadt) Brussels Redu Toulouse Oberpfaffenhofen Cebreros (Villafranca) Ground stations ESAC (Villanueva de la Cañada) ESRIN (Frascati) Moscow Washington Houston Santa Maria Kourou Maspalomas New Norcia Perth Malargüe FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 4 ESTEC, Noordwijk, The Netherlands FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 5 ESTEC, Noordwijk, The Netherlands Principal responsibilities Studies, preparation and management of ESA space programmes: Launchers Science Earth observation Telecommunication Navigation Human spaceflight Deep space exploration Technical support to ESA project teams, including preparation and coordination of ESA space technology R&D programme Product assurance and safety for ESA space programmes Management of ESTEC Test Centre and coordination with other test centres in Europe Employs • Approx. 2000 staff FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 6 Knowledge Sharing: the challenge FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 7 Knowledge sharing: The Problem Space system development partners usually differ from project to project Partners are geographically dispersed Different partners participate at different points in time in the project schedule Mother tongues differ (English and French are ESA’s “official” languages) Legacy/proprietary systems are often deployed Development processes and procedures are standardised but their application and interpretation vary Exchange of Information between partners is frequently misinterpreted FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 8 Knowledge Sharing: a typical example FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 9 An Example: the EarthCARE mission Cloud Profiling Radar: JAXA Satellite Prime Contractor: Astrium GmbH Base Platform: Astrium Limited Onboard Computer: RUAG Aerospace Star Tracker: Jena-Optronik GmbH Backscatter Lidar: Astrium-SAS Multispectral Imager: SSTL Broadband Radiometer: SEA Ltd. Launcher Russian Soyuz (Kourou or Baikonour) Zenit (Baikonour) ESA Kiruna Ground Station Flight Operation Segment: ESOC Payload Data Segments: ESRIN JAXA for CPR FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 10 EarthCARE: the Spacecraft, 1 FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 11 EarthCARE: the Spacecraft, 2 • Mission: – – • 8 years of developments (launch planned in 2016) 3 years of operations (including 6-month commissioning) Orbit: – – – LEO – Frozen Orbit – SSO Mean spherical altitude: 393 km (Routine) / 394.4 km (Cal/Val) Attitude control: 3-axis stabilized, yaw-steering control • Dry Launch Mass: approx. 2000 kg • Payload – – • Power Sub-system – – • 2 active instruments: ATLID & CPR 2 passive instruments: BBR & MSI Deployable solar array, GaAs triple junction cells, 21 m2 Average Power consumption: 1645 W Communication Links – – Average: <15 kbps (housekeeping) & <2.5 Mbps (science) S-Band: – – – Uplink: 64kbps (max 10 TCs/s) Downlink (with/without ranging): 128 kbps/1 Mbps X-Band downlink FBM 2014 | FAMOUS | Serge Valera | D/TEC for science data & stored HKTM : 150 Mbps slide 12 EarthCARE: the Spacecraft, 3 Measurement data I/F ATLID System synchronization BBR X-Band link ESRIN On-board computer downlink uni-directional uplink CPR MMFU Remote interface unit MSI Discrete & serial I/O MIL-STD 1553 P/L T T T T MIL-STD 1553 P/F S-Band Transponder S-Bandlink ESOC bi-directional P/F Thermal Control HDRM PCDU Thermistors & heaters Li-Ion Battery Solar Array AAD Star tracker GPS GPS sync. 1 Hz Magneto meter CESS Magneto torquer SADM SADE FBM 2014 | FAMOUS | Serge Valera | D/TEC RMU Reaction Wheel RCS system slide 13 EarthCARE: the Spacecraft, 4 Prime: Astrium GmbH RUAG Aerospace Base platform: Astrium Limited ESRIN Astrium-SAS SEA Ltd. JAXA Sideral SSTL RUAG Jena-Optronik GmbH ESOC FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 14 2014 ESA missions FBM 2014 | FAMOUS | Serge Valera | D/TEC under definition, development and operation slide 15 Knowledge Sharing : ESA missions FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 16 The customer/supplier chain FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 17 Customer/Supplier Hierarchy Usually ESA Top-level Customer Business Agreement PC Satellite Prime Contractor Specifications Supplier Customer Network of Customer-Supplier relationships Subsystem SubsystemSubcontractor Subcontractor Subsystem Subcontractor Business Agreements PayloadSubcontractor Payload PayloadSubcontractor Subcontractor Supplier Supplier Customer Customer ES 1 ES 2 Equipment ES... Supplier Equipment Supplier Equipment Supplier FBM 2014 | FAMOUS | Serge Valera | D/TEC PSC 1 SSC SSC 2… SSC 1 SSC SSC 2… US 1 US 2 Unit Supplier US... Unit Supplier Unit Supplier Business Agreements Products and associated information slide 18 Customer/Supplier interactions Enable, lead and control collaboration between all disciplines and parties Specify the Problem Requirements Customer Supplier Define the Solution Coordination and Control Design FBM 2014 | FAMOUS | Serge Valera | D/TEC * Realise the Product Manufacturing, Assembly & Integration, Verification & Validation slide 19 Concurrent engineering … Requirements Attitude & Orbit Control Thermal Requirements Comms Requirements Requirements Requirements Requirements Propulsion Power System Requirements Design Design Design Design Design Design Design Manufacturing, Integration, Manufacturing, Verification,Validation Integration, Manufacturing, Verification,Validation Integration, Manufacturing, Verification,Validation Integration, Manufacturing, Verification,Validation Integration, Manufacturing, Verification,Validation Integration, Manufacturing, Verification,Validation Assembly & Integration, Verification & Validation Collaborate, Coordinate and Control Iterate between Requirements, Design,, AIT, V&V Iterate across Disciplines FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 20 System engineering in the supply chain (product tree / WBS) Top Customer Requirements Customer Supplier M, A & I, V&V Design Requirements Prime Contractor Requirements Requirements Customer Supplier Design M, A & I, V&V M, A & I, V&V Design M, A & I, V&V Design 1st Tier Subcontractors Requirements Requirements Customer Supplier Design M, A & I, V&V Design M, A & I, V&V 2nd Tier Subcontractors nth Tier Subcontractors FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 21 effort Effort along the System Life-Cycle Design Requirements Manufacturing, Assembly & Integration, Verification & Validation Define the Solution Specify the Problem Realise the Product MDR PRR SRR PDR CDR QR FAR time FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 22 System Engineering – A modelling issue Provide all needed views and all needed reports on all system data from a consistent source Requirements Requirements Models including traceability links Customer Supplier Define the Solution Coordination & Control Design System / Architectural Design Model Trade-offs & Design Rationale Structure and Behaviour Models Analysis and Simulation Results FBM 2014 | FAMOUS | Serge Valera | D/TEC Realise the Product Data Common to all Disciplines Interfaces between Disciplines Configuration Control & Baselines Manufacturing, Assembly & Integration, Verification & Validation M, A & I Models (including Logistics) V & V Models (procedures, testcases, results, NCRs, waivers, close-out, VCDs) slide 23 System Engineering – A modelling issue, 2 Modelling is key and used everywhere in each sector of any organization However, interoperability between models is still a challenge Today, most organizations address interoperability at physical modelling level a huge effort is spent with limited results Exchange requires semantic interoperability to enable Exchange, there is a need for a GLOBAL MODELLING APPROACH that shall be addressed at semantic level FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 24 Toward global modelling E CSS ECSS The European Cooperation for Space Standardization FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 25 ECSS - the organization, 1 FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 26 Knowledge exchange: towards a solution Created in 1993 – www.ecss.nl Objectives: • Establish means by which the European Space Business can improve (i.e. reduce risk, cost & effort) the … Working Together • Provide a clear operational framework aiming at improving significantly the way space projects are developed in Europe • Focus on the WHAT i.e. the System Requirements excluding implementation specifics, i.e. no over-specification FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 27 The ECSS System FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 28 Toward Global Modelling E CSS ECSS Global Modelling – The ECSS vision FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 29 ECSS – the current status & a new vision 2014 – the ECSS System is standardized • 115 ECSS standards • Handbooks & technical memorandums including more than 23,000 requirements ECSS now enters in a maintenance and consolidation phase The interoperability between ECSS partners is a fact but compliance to all standard requirements remains a difficulty There is a need for supporting facilities/tools The ECSS standards express the needs of their stakeholders in an informal way Formal modelling including validation by the stakeholders can also help ! st 1 attempt - refer to ECSS-E-ST-70-41C FBM 2014 | FAMOUS | Serge Valera | D/TEC > 3000 requirements slide 30 E CSS ECSS Formal Modelling - the ECSS-E-TM-10-23 vision FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 31 ECSS-E-TM-10-23 • The TM describes the process that should be followed by all partners involved in the European Space projects to enable knowledge sharing and reuse • It identifies the need for a Space System Ontology that can be used by all partners to produce tools that are interoperable • It requires the development of an Ontology Engineering tool that : – provides the capability to fully specify and maintain the Ontology including the global conceptual model and the local conceptual views each local conceptual view corresponding to the conceptual model of a space system product – implements ontology versioning and all related capabilities – generates for each local view, the conceptual model of the related product – calculates the mapping between any 2 – generate the conceptual model of the supplier/customer exchange resulting from the calculated mapping FBM 2014 | FAMOUS | Serge Valera | D/TEC supplier/customer locals of the Ontology slide 32 Ontology Engineering Tool 1. Model at global level 2. Identify the locals: • PKT product view • IRIG product view • IRIGsupplier / PKTcustomer exchange view Generate the conceptual models of the products and the IRIG/PKT exchange Interface requirement specification (IRD) IRIG IRD PKT specification realisation Exchanged Data supplier FBM 2014 | FAMOUS | Serge Valera | D/TEC customer slide 33 ECSS-E-TM-10-23 – 2 approaches What methodology to use for the development of the Space System Ontology? 2 approaches have been introduced and being currently assessed: • based on the OMG’s Model-Driven Architecture (MDA) – • Since 2006, a UML representation of such Space System Ontology is being developed http://www.purl.org/ecss/ecss-e-tm-10-23/annex-b based on the Fact Based Modelling Architecture (FBM) – 2008-2012 ESA R&D related to fact based modelling – October 2009 decision taken during ORM 2009 workshop to standardize FBM the FBM WG – 2013-2014 ESA R&D - the Fact Based Modelling Unifying System FAMOUS2 – 2015,… FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 34 ESA / FAMOUS Some pre-requisites for FBM to be used in the European Space business 1. formal specification of the fact based modelling methodology – grounded on solid foundations logic based – covers the stakeholder’s hierarchical view of requirements conceptual hierarchies – understandable and able to be validated by stakeholders controlled natural language – meets the stakeholders’ needs of requirement’s expressiveness towards ISO TR9007 100% principle – fulfils the quality required for a customer’s requirements specification unambiguity, elementary, testability, consistency, completeness, verifiable, feasibility, traceability, … – aligned to customers’ needs, covers the requirement engineering cycle including from tacit to explicit knowledge modelling – … FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 35 ESA / FAMOUS, 2 2. standardized methodology e.g. ISO, OMG 3. availability of industrial FBM modelling tools 4. optimized for and aligned to suppliers’ needs – from specification conceptual modelling to architecture logical modelling and design physical modelling – – Support to reverse engineering, e.g. – from models developed by other modelling languages to FBM conceptual models – From database systems to FBM conceptual models etc. FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 36 The FBM WG FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 37 FBM Working Group www.factbasedmodeling.org Convenor S. Valera Secretary I. Lemmens Methods ORM T. Halpin CogNIAM S. Nijssen FCO-IM D. Smeets ActiveFacts, CQL C. Heath NORMA M. Curland Doctool J.P. Koster Richmond V. Morgante DOGMA R. Meersman Tools Experts Y. Tang H. Balster P. Bollen L. Bruil K. Evans B. Piprani R. Schmaal N. de la Cruz FBM 2014 | FAMOUS | Serge Valera | D/TEC A. le Cat slide 38 The FAMOUS 2 Consortium FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 39 FAMOUS 2 ESA/ESTEC contract no. 4000107725/12/NL Fact based Modelling Unifying System Toward implementing solutions for ECSS-E-TM-10-23A Consortium PNA Group ORM Solutions Technical team includes Inge Lemmens Jean-Paul Koster Terry Halpin Matt Curland FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 40 FAMOUS 2 - on-going, 1 FAMOUS methodology definition: • • FBM1002WD08 with extensions – support for multi models – derivation language – dynamic constraints time and event based – QUDV Quantities, Units, Dimensions and values compliance Customers’ needs – specification – – a generic modelling architecture modelling: a term used by everyone with different meanings visualization: a 3-level triangle-based architecture (data, schema, meta-schema) a conceptual modelling protocol from nothing to a conceptual model to formally specify the to-be-contracted system specification, focusing on the real needs, i.e. the WHAT, no over-specification/no HOW conceptual hierarchies (root natural/promoted concepts, existential dependent fact types/object types, leading roles, assembly concepts, …), customer/supplier root concepts’ interactions, root concept’s life cycle, … FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 41 FAMOUS 2 – on-going, 2 • • Supplier’s needs - realization – Engineering: automatic transformation from conceptual models to Logical & Physical models – Reverse engineering: semi-automatic transformation from databases to conceptual models – FBM formalization of logical and physical including: – Logical modelling including Relational SQL2011, UML, hierarchies – Physical modelling including Oracle SQL, XMI, XSD Semantic interoperability: – Global and locals modelling FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 42 Modelling - what meaning? , 1 ¿FBM? MODEL = combination of a SCHEMA and a POPULATION domain-specific level 3 modelling schema level 2 modelling population level 1 modelling FBM 2014 | FAMOUS | Serge Valera | D/TEC schema generic meta-schema population slide 43 Modelling - what meaning? , 2 ¿FBM? What should be the characteristics of any schema? self-contained, consistent, unambiguous, ... domain-specific level 3 modelling schema level 2 modelling population level 1 modelling FBM 2014 | FAMOUS | Serge Valera | D/TEC schema generic meta-schema population slide 44 Modelling - what meaning?, 3 ¿FBM? Modelling at schema level: supplier customer • seen from a conceptual perspective whose objective is to capture the stakeholders’ needs and to produce a conceptual view that represents the semantics conceptual modelling e.g. FBM specification realisation • seen from a technology perspective whose objective is to transform the conceptual view into a technological view that takes into account the stakeholders’ needs • seen from an implementation perspective whose objective is to implement that technology view through a specific tool implementation FBM 2014 | FAMOUS | Serge Valera | D/TEC logical modelling e.g. relational physical modelling e.g. Oracle SQL slide 45 Modelling - what meaning? , 4 ¿FBM? Modelling at population level: conceptual schema information conceptualize Transformation from tacit knowledge into explicit knowledge FBM 2014 | FAMOUS | Serge Valera | D/TEC data physical schema logical schema slide 46 Modelling - what meaning? , 5 ¿FBM? How to classify the modelling methodology/notation/…? what mean conceptual modelling, logical modelling and physical modelling? conceptual modelling logical modelling physical modelling L3 schema L3 schema L3 schema L3 population = L2 schema L3 population = L2 schema L3 population = L2 schema customer specification Product development life cycle FBM 2014 | FAMOUS | Serge Valera | D/TEC supplier architectural design realization detailed design time slide 47 FAMOUS, toward semantic interoperability Exchange at level 1 requires level 2 semantic equivalence* requires level 3 semantic equivalence* * taking into account the WHAT versus HOW differences i.e. – conceptual versus architectural design – architectural design versus detailed design conceptual modelling logical modelling physical modelling L3 schema L3 schema L3 schema L3 population = L2 schema L3 population = L2 schema L3 population = L2 schema the WHAT FBM 2014 | FAMOUS | Serge Valera | D/TEC the HOW slide 48 FAMOUS, a formal approach to modelling How to assess the semantic equivalence of the many level 3’s? Level 3 should be self-contained, consistent, unambiguous, … but not all level 3 fulfils that requirement ! FAMOUS approach: • Use a formal language (i.e. FBM) to specify the level 3’s • Assess how to transform both directions level 3’s schemas via the FBM schema clarification requests where needed ! ISO SQL-2001 UML SysML … … FBM … XSD XMI FBM 2014 | FAMOUS | Serge Valera | D/TEC Oracle slide 49 FAMOUS, toward complete specification… • Verbalization: – • ISO/ECSS compliance Reasoner – Conceptual model validation support e.g. derivation rules reasoning • Conceptual models’ optimization (semantic equivalence derivation rules/constraints, constraint derivation, identification of duplicates, etc.) • Validation of the methodology prior to ontology definition tool development • System specification of the ontology definition tool system • others ? FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 50 Modelling with FBM An example : ViDB - the VEGA launcher interface database FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 51 ViDB example, 1 FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 52 ViDB example, 2 FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 53 ViDB example, 3 FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 54 ViDB example, 4 FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 55 ViDB example, 5 FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 56 Modelling with FBM – toward the 100% principle ViDB – a Stakeholder’s view FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 57 FAMOUS – some new conventions Root Concept graphical representation native root concept promoted root concept external root concept native root concept promoted root concept external root concept Leading roles identified by blue-coloured connectors FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 58 ViDB – a stakeholder’s view, 1 FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 59 ViDB – a stakeholder’s view, 2 FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 60 ViDB – a stakeholder’s view, 3 FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 61 ViDB – a stakeholder’s view, 4 FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 62 ViDB – a stakeholder’s view, 5 FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 63 Conceptual hierarchies At population level, Reporting data RD , activities ACT, packets PKT and interpretation functions IFB are attached to a system element SE that collects all knowledge of a particular element of the VEGA launcher. At schema level, RD, ACT, PKT and IFN are said existential-dependent of the root concept SE. The ViDB schema states that the roles hosted by SE are leading roles. This implies that, at population level, all distance 1 facts are existential dependent to the related system element. The ViDB schema also states that IFN, RD, ACT and PKT are existential dependent of SE. This implies that all these distance 1 objects are existential dependent of the related system element. Recursively, all distance 1 facts and distance 1 objects of a distance n object is existential dependent of the related system element. FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 64 PKT root concept definition, 1 A root concept is defined by : • specifying all its “existential-dependent relations” i.e. its constituting fact types and object types • … FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 65 PKT root concept definition, 2 A root concept is defined by : • … • if the root concept is promoted, specifying the parent root concept • ... FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 66 PKT root concept definition, 3 A root concept is defined by : • … • pointing to relevant external FBM 2014 | FAMOUS | Serge Valera | D/TEC exposed by suppliers object types slide 67 Semantic interoperability, a key element The root concepts: • are key elements of the customer/supplier chain representing the configuration items of the System. • guarantee the integrity of the customer/supplier interfaces. PKT The root concepts provide means to visualize the conceptual models according to the stakeholders’ needs zooming in and out depending on the needs FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 68 Root concept life cycle ECSS has standardized the Space System life cycle ECSS-E-TM-10-23 adopts that life cycle for the root concepts. ECSS-E-ST-70-31 specifies requirements for the versioning of native root concepts and promoted root concepts FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 69 Root concept - global and locals Root concepts – key elements of the Global conceptual model and the local views Still to come: the Assembly concept means to group a number of fact types representing key elements of the global and locals FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 70 Space System Ontology How large can a space system ontology be? How many requirements a space system ontology definition tool should support? Some estimations Tool requirements for formally modelling at global level: – a product : from 1,000 to 200,000 requirements – the ECSS requirements: up to 200,000 rules – ECSS views: 200 locals – a space project: up to 1,000,000 rules – Space project views up to 2,000 locals FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 71 International Workshop on Fact-Oriented Modeling ORM 2014 Automatic Generation of database MMI from a domain ontology AuGeMMI Serge Valera European Space Agency 22 September 2014 FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 72 AuGeMMI ESA/ESTEC contract no. 4000108703/13/NL AuGeMMI Automatic Generation of database Man Machine Interface from a domain ontology Consortium: GMV Aerospace and Defence S.A.U. Astrium GmbH PNA Group ScopeSET Technology Deutschland Gmb Technical team includes: Jorge Pacios Harald Eisenmann Sjir Nijssen Armin Müller FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 73 AuGeMMI – the objective The Objective: Automate the production of SRDB applications Each Space Project develops its own SRDB software in line with all involved stakeholders The SRDB provides • means to capture and maintain all knowledge required to – test the spacecraft and its components during their development – operate the spacecraft when in-flights • multi-models support • local & remote access • import/export • consistency checking • root concepts’ versioning and non-conformance management • root concepts’ man machine interfaces • internal structure based man machine interfaces (for debugging) • etc. FBM 2014 | FAMOUS | Serge Valera | D/TEC e.g. engineering models, flight models slide 74 SRDB application framework The approach: • produce a generic SRDB application framework that implements all generic independent components of a SRDB • … FBM 2014 | FAMOUS | Serge Valera | D/TEC i.e. model slide 75 AuGeMMI development framework • … • produce the AuGeMMI development framework that: – • takes as input conceptual/logical/physical definitions produced by FAMOUS and automate the generation of the model-dependent SRDB components … FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 76 Integration • … • Integrate the model-specific SRDB components automatically generated by the AuGeMMI development framework onto the SRDB application framework resulting in a fully functional SRDB application software FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 77 Combining FAMOUS & AuGeMMI FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 78 AuGeMMI – on-going developments Specification: • A generic SRDB system specification • A formally expressed use case: the ViDB conceptual model and compliant SQL2011, Oracle and UML/XMI models • 2 prototype developments: – GMV an Oracle RDBMS SRDB with JHeadStart & Jdeveloper – ScopeSet an Eclipse based SRDB • Lessons learned FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 79 End of Presentation FBM 2014 | FAMOUS | Serge Valera | D/TEC slide 80