1 / 22

FutureSTEP Project

FutureSTEP Project. 11 th NASA/ESA Workshop on Product Data Exchange 2009 Allison Barnard Feeney, NIST David Price, Eurostep. Background. ISO TC184/SC4 STEP. Producing data exchange standards for 25 years - ~30 major information models for product data exchange

dior
Download Presentation

FutureSTEP Project

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. FutureSTEP Project 11th NASA/ESA Workshop on Product Data Exchange 2009 Allison Barnard Feeney, NIST David Price, Eurostep

  2. Background

  3. ISO TC184/SC4 STEP • Producing data exchange standards for 25 years - ~30 major information models for product data exchange • formally specified in EXPRESS • standardized by ISO • in wide use in the manufacturing industry • supported by dozens of software tools • Production implementations in US aerospace, automotive and ship building companies have resulted in actual savings of $150M per year • STEP information models are of the high fidelity, high quality needed by US industry

  4. Yet… • Business requirements for IT have changed but STEP activities have not kept pace • EXPRESS and related implementation method standards work because people make them work, not because there is a consistent IT architecture behind them • STEP focus on data means its standards do not address other viewpoints that have become key to business process reengineering and systems integration over the past several years

  5. IT has Changed • The IT world has moved on • Web Services, Semantic Web, Ontologies, Reasoning • XML Schema, XSLT, RDF, OWL • Business Process/Rules Models, Topic Maps • UML, XMI, MDA, ODM, MOF, QVT, OCL • None are “domain models,” they are all IT • OMG and W3C standards are more widespread than EXPRESS; many more modelers and implementors understand them • Many good STEP models will not be widely used because STEP only uses EXPRESS • Bottom Line: The need for consensus information models remains, but STEP must adapt to keep its models relevant

  6. OMG and W3C Standards • OMG’s Unified Modeling Language is “the standard” for software engineering • Model Driven Architecture analogous to STEP Architecture • UML 2 is a family of languages with domain-specific extensions (e.g. SysML) • MDA relies on models expressed in the Meta Object Facility, and rendered in XML Metadata Interchange. • W3C technologies for the Semantic Web • Resource Description Framework (RDF) and the Web Ontology Language (OWL) are “the standard” for modelling semantics on the Web

  7. STEPs in the Right Direction • Many in this room have been in agreement for the past 5 years that STEP must adapt • STEP projects have addressed this through mappings to XML Schema (Part 28) and UML (Part 25) • These mappings were specified entirely in text and targeted version 1 of XML Schema and UML • Open-source projects have supported this migration “exff.org,” EU F6 projects “MEXICO” and “Interop S-10” • Initial mappings to UML and OWL and prototype tools published on exff.org in 2004 • STEP PLCS and now AP233 projects are extending less strongly typed models with OWL Reference Data

  8. Key Enabler • OMG has adopted the EXPRESS metamodel • EXPRESS is now an OMG language • OMG RTF underway now • Provides formal basis for mappings to UML and OWL that have existing OMG metamodels • EXPRESS schema exchange between MOF tools via XMI • EXPRESS-based data exchange using XMI • OMG Model Driven Architecture languages applied with EXPRESS schemas as input or output • For example, a formal mapping between AP233 EXPRESS and the OMG Systems Modeling Language (SysML) using OMG Query/View/Transform (QVT)

  9. Future of STEP • It is now possible to reproduce “the STEP architecture” in OMG’s MDA • MOF metamodel of EXPRESS defines the language • Use Object Constraint Language (OCL) for detailed constraints • Use Query/View/Transform for mapping between models and EXPRESS-X style transformations • EXPRESS schema exchange between MOF tools via XMI • EXPRESS-based data exchange using XMI • We can also do a lot more • Ontologies using OMG Ontology Definition Metamodel (ODM), Reasoning, Web services

  10. On Architectures • The “bigger vision” should be an architecture where modelers use the languages that appropriate for the task • UML for software, OWL for ontologies, EXPRESS for constrained data exchange • OMG’s MDA is a start in that direction • Standards and good open-source reference implementations in this area are required

  11. FutureSTEP Project

  12. Big Picture Concepts Model Driven Architecture Schema Can process Can map to/from Convert to Implemented as Activity Models Based on AP Model of EXPRESS Formally defines ODM Ontology EXPRESS Can use published published UML published OMG WebServices SC4 Can harvest standards from SysML

  13. Near-Term Goal– Harvesting STEP Future STEP Project ISO OMG Industry OMG EXPRESS STEP EXPRESS Schemas ODM/OWL Reasoner Harvesting Process, Specs & Tools OWL Reference Data UML Profile for EXPRESS STEP as UML UML 2 Tool & Executable UML Data APIs & Services Inter-related suite of stds Software Systems Integration XML Schema

  14. Harvesting Process • Provide recommendations to OMG and ISO STEP on how to work together better, for example • Can ISO STEP adopt OMG MDA instead or in addition to current modeling tools? • Can OMG MDA approach/tools learn any lessons from ISO STEP modular architecture? • What in ISO STEP is worth harvesting into OMG? • ISO EXPRESS is now an approved OMG language, should OMG take more advantage of that? • End Goal • Present recommendations for “Future STEP” to ISO STEP community in May – we hope that starts the process

  15. End Goal – New ISO STEP Approach Industry Extensions Reasoning SOA Standardized Core Ontologies And Mapping Data Exchange ROA

  16. Technical Specifications • EXPRESS/UML mapping • make UML class diagrams suitable for UML-based data exchange • compatible with EXPRESS-based data exchange • AP EXPRESS to ODM OWL mapping • EXPRESS to OWL mapping as QVT may be RFC to ODM specification • UML Profile for EXPRESS stereotypes specification • AP233/SysML mappings

  17. Proof-of-Concept Tools • Vanilla UML class diagrams from EXPRESS schema • AP-based OWL ontology from AP, RD and instance data • EXPRESS-as-UML class diagrams • Using proposed UML Profile for EXPRESS diagram notation • EXPRESS schemas represented using MOF of EXPRESS • NIST implementation already exists but needs upgrade to XMI 2 • OMG XMI for data exchange using UML driven from EXPRESS

  18. AP233 Reference Artifacts • Using an appropriate subset of AP233 as the example, the specification of: • AP233 as EXPRESS for data exchange • AP233 as UML Profile for EXPRESS • AP233 as vanilla UML for data exchange • AP233 as XML Schema for data exchange • AP233 as OWL for at least one scenario where reasoning is possible • AP233-based Class diagrams for higher level Systems Engineering Web services

  19. AP233 ARM EXPRESS AP233 ARM OWL EXPRESS-based code generators Reasoner AP233 ARM API or Service AP233 OWL Ref Data AP233 ARM XML Schema AP233 ARM UP4E XMI AP233 ARM UML 2 XMI UML-based code generators UML 2 Tool

  20. Progress • Draft 1 of EXPRESS/UML mapping • AP233 as UML provided to NIST for plug-fest, transformation tools • Issue resolution underway • OMG RTF underway for EXPRESS Metamodel • Held INCOSE and OMG mapping workshops for SysML/AP233 common areas • Participating in OMG Model Interchange team to ensure XMI capable of data exchange • Participated in NIST Ontology Summit 2009 – Ontologies as Next Generation Standards

  21. Plans • Process for enterprises to adapt STEP for software integration needs • Report to SC4 in May • Finalize mappings between STEP and OMG/W3C languages, models and data • June 2009 – publish working drafts for review • September 2009 – deliver specifications and demonstration

  22. Issues and Risks • How far should we “push” SC4 towards use of OMG MDA and related technologies? • Getting vendor buy-in • SysML vendors for AP233 export/import • EXPRESS vendors for OMG metamodel support • Testing new technologies • XMI for data exchange • QVT for computer-interpretable mappings – finding QVT tools to specify mapping is a problem • Turns out we are “the pioneer” in this area for publishing a standard transformation in an OMG standard • Transformation is key to MDA!

More Related