Domain Specific Product Description Exchange

Slides:



Advertisements
Similar presentations
Fraunhofer FOKUS Competence Center MOTION FOKUS VIEW ON MODEL-BASED TEST DESCRIPTION LANGUAGES (TDLS) Alain-G. Vouffo Feudjio.
Advertisements

Language Specification using Metamodelling Joachim Fischer Humboldt University Berlin LAB Workshop Geneva
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 2, Modeling with UML, Part 4 UML 2 Metamodel.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
IT Requirements Capture Process. Motivation for this seminar Discovering system requirements is hard. Formally testing use case conformance is hard. We.
Object-Oriented Analysis and Design
Amit, Keyur, Sabhay and Saleh Model Driven Architecture in the Enterprise.
UML CASE Tool. ABSTRACT Domain analysis enables identifying families of applications and capturing their terminology in order to assist and guide system.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 5 Slide 1 Requirements engineering l The process of establishing the services that the.
ADML A result of cooperation and leverage! The Open Group W3C OMG MCC CMU.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
MDC Open Information Model West Virginia University CS486 Presentation Feb 18, 2000 Lijian Liu (OIM:
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Xactium xDSLs Run Models Not Code Tony Clark
Workshop on Integrated Application of Formal Languages, Geneva J.Fischer Mappings, Use of MOF for Language Families Joachim Fischer Workshop on.
Metadata Tools and Methods Chris Nelson Metanet Conference 2 April 2001.
Introduction to MDA (Model Driven Architecture) CYT.
2nd TTCN-3 User Conference, June The TTCN-3 Metamodel – A Basis for Tool Integration Ina Schieferdecker TU Berlin/Fraunhofer Fokus Hajo Eichler,
Modeling Component-based Software Systems with UML 2.0 George T. Edwards Jaiganesh Balasubramanian Arvind S. Krishna Vanderbilt University Nashville, TN.
Dr. Darius Silingas | No Magic, Inc. Domain-Specific Profiles for Your UML Tool Building DSL Environments with MagicDraw UML.
Service Service metadata what Service is who responsible for service constraints service creation service maintenance service deployment rules rules processing.
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
Parastoo Mohagheghi 1 A Multi-dimensional Framework for Characterizing Domain Specific Languages Øystein Haugen Parastoo Mohagheghi SINTEF, UiO 21 October.
CSCI 3428: Software Engineering Tami Meredith UML Unified Modeling Language.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 2, Modeling with UML: UML 2 Metamodel Note to Instructor: The material in this.
Ontologies Reasoning Components Agents Simulations An Overview of Model-Driven Engineering and Architecture Jacques Robin.
1 BTS330 Visual Modeling. What is Visual Modeling? 2 Copyright © 1997 by Rational Software Corporation Computer System Business Process Order Item Ship.
Use Case, Component and Deployment Diagrams University of Sunderland.
1 Advanced DataBases Unified Modelling Language An Introduction and Use Case Lecture 2 Susan Curtis.
Software Reuse. Objectives l To explain the benefits of software reuse and some reuse problems l To discuss several different ways to implement software.
1 The XMSF Profile Overlay to the FEDEP Dr. Katherine L. Morse, SAIC Mr. Robert Lutz, JHU APL
M&CML: A Monitoring & Control Specification Modeling Language
SysML 2.0 Requirements for Visualization
Modeling Formalism Modeling Language Foundations
IS301 – Software Engineering V:
Chapter 4 – Requirements Engineering
SysML 2.0 Formalism: Requirement Benefits, Use Cases, and Potential Language Architectures Formalism WG December 6, 2016.
SysML v2 Formalism: Requirements & Benefits
Java Beans Sagun Dhakhwa.
Software Reuse ©Ian Sommerville 2006.
SysML 2.0 Model Lifecycle Management (MLM) Working Group
Online Shopping APP.
Krishnakumar Balasubramanian
Specifying collaborative decision-making systems
SysML 2.0 Concept and Needs for Visualization
Chapter 2, Modeling with UML, Part 4 UML 2 Metamodel
Status of the Systems Engineering Concept Model (SECM)
Unified Modeling Language
Chapter 2 – Software Processes
Tools for Composing and Deploying Grid Middleware Web Services
Evaluating Compuware OptimalJ as an MDA tool
TDL: The ETSI Test Description Language
System Modeling Assessment & Roadmap Joint OMG/INCOSE Working Group
UML profiles.
Constructing MDA-based Application Using Rational XDE for .NET
TDL: The ETSI Test Description Language
An Introduction to Software Architecture
Chapter 7 –Implementation Issues
Status of the Systems Engineering Concept Model (SECM)
ETSI TC MTS TDL SC meeting Reports
Execute your Processes
ETSI TC MTS TDL SC meeting Reports
ETSI TC MTS TDL SC meeting Reports
TDL: The ETSI Test Description Language
NIEM Tool Strategy Next Steps for Movement
Subject Name: SOFTWARE ENGINEERING Subject Code:10IS51
Software Development Process Using UML Recap
Chapter 13 Logical Architecture.
Software Architecture & Design
Presentation transcript:

Domain Specific Product Description Exchange Dr Andy Evans Xactium Limited Contact: andy.evans@xactium.com www.xactium.com

Product Descriptions Large engineering projects need the ability to be able to capture and interchange product descriptions Examples: maintenance logs, test descriptions, vehicle configurations, and so on Although there is some commonality across products, there are often significant features that are specific to each domain. How do we manage these situations? ©Xactium Limited, 2005

Capturing Product Data We use languages to capture product data The following types of language are commonly used: General-purpose, low-level languages like XML, or other common lowest denominator data representation Specialised ‘product description’ languages like AP233, SEDRES, SysML General purpose modelling languages, i.e. UML ©Xactium Limited, 2005

Languages - Pros and Cons General purpose languages, e.g. XML Product description languages, e.g. SysML Un-restricted: can capture any type of data More intuitive, visual, semantically richer Semantically weak, difficult to maintain Fixed set of concepts that is hard to extend Uses general purpose concept types, e.g. component Stereotypes are a weak form of specialisation ©Xactium Limited, 2005

Domain Specific Languages A Domain Specific Language (DSL) is a language designed for a specific problem domain DSL’s directly capture domain concepts, e.g. maintenance logs, vehicle configurations, weapon trajectories Example: A language that allows you to visually model specific vehicle configurations, test them and generate specific component API’s. ©Xactium Limited, 2005

Benefits of DSL’s Engineers work with concepts that closely match the problem domain: E.g. user-interfaces are modelled using visual user-interface modelling languages More intuitive representation of problem domain to stakeholders: Stakeholders understand the models because they match their way of thinking about the problem Semantics of concepts can be fully described in a very focused way ©Xactium Limited, 2005

Managing and interchanging DSL’s We need a way of being able to rapidly construct DSL’s and provide support for them in tools We need a common denominator way of representing and interchanging DSL product descriptions as models We also need a way to make the DSL definitions themselves open and interchangeable ©Xactium Limited, 2005

Components of DSL’s Domain Concepts Semantics Visual/ Textual Syntax ©Xactium Limited, 2005

DSL’s as Models DSL’s can be modelled (just as we can model systems) Provide a model of domain concepts, visual/textual syntax, and semantics Key point: the languages used to model DSL’s are modelled themselves: Can therefore deploy DSL tools on other platforms by constructing tool mappings ©Xactium Limited, 2005

XMF-Mosaic XMF Engine MOF Runs on A platform for modelling, executing and deploying languages and their associated tools Based on MDA and associated meta-data standards (MOF) Everything is modelled, including the XMF-Mosaic platform itself DSL Modelling Language Model of Language Model of Product ©Xactium Limited, 2005

Advantages As models, the DSL definitions are fully transparent and interchangeable Models written in the language can be interchanged between any pair of tools that understand the DSL model Alternatively, we can define mapping rules to generate XML representations of models and DSL’s. ©Xactium Limited, 2005

Example Language for capturing specific classes of events (i.e. specialised event based view of a product) Compulsory events Optional events Internal and external actors Process: Model domain concepts Model diagram syntax Model semantics Model a mapping to another language (forms based language) ©Xactium Limited, 2005

Model of Domain Concepts ©Xactium Limited, 2005

Model of Diagram Syntax ©Xactium Limited, 2005

Model a Specific Product ©Xactium Limited, 2005

Map to a Forms Language ©Xactium Limited, 2005

Model of Semantics Validate model ©Xactium Limited, 2005

Semantics ©Xactium Limited, 2005

Construct Mappings to Interchange formats Model of XML Mapping ©Xactium Limited, 2005

Summary Product descriptions are written using languages Benefits from being able to use domain specific product description languages (DSL’s) XML and standards like SysML don’t facilitate this Can provide an open an transparent way of describing DSL’s by modelling them using meta-data standards like MOF Interchange capabilities provided through meta-data and standards like MDA XMF-Mosaic a fully integrated model-driven development environment that supports the modelling, execution and deployment of DSL’s ©Xactium Limited, 2005