1 / 17

The Knowledge Industry Survival Strategy (KISS)

The Knowledge Industry Survival Strategy (KISS). Tony Clark, Thames Valley University, London, UK Jorn Bettin, Sofismo , Switzerland. DSLs: Benefits and Problems. Benefits: express problems in a compact form that reflects the natural terminology of human domain experts

kimn
Download Presentation

The Knowledge Industry Survival Strategy (KISS)

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. The Knowledge Industry Survival Strategy (KISS) Tony Clark, Thames Valley University, London, UK Jorn Bettin, Sofismo, Switzerland

  2. DSLs: Benefits and Problems • Benefits: • express problems in a compact form that reflects the natural terminology of human domain experts • Raise the level of abstraction • Clean separation of concerns in problem space. • Problems: • Interoperability (similar to CASE tools in 90s) • Cannot realise tool chains. • No common framework, processes, terminology,... KISS @ OOPSLA 09

  3. Tool Chain Scenario Given: • A tool to support business motivation (goal) modelling. • A tool to design business components (information models + state machines) • A tool to design business processes (generate enterprise workflow applications) How would these work together to produce a complete application? KISS @ OOPSLA 09

  4. Tool Chain Requirements • Tools should be able to persist models. • A tool must be able to supply its models to another tool. • A tool must make its data format available • Inter-tool control • Precise model semantics KISS @ OOPSLA 09

  5. Tool Definitions and Terms • Model • Abstract Syntax • Concrete Syntax • Well-formedness • Language Definition • Semantics • Meta-language • Generic Tool • Model Transformation • Model Persistence • Model Weaving • Model Execution • Model Editor • Model Reader • Model Writer • Model Walker • Tool Interface • Tool Chain • Tool Framework KISS @ OOPSLA 09

  6. Current Approaches Standard-like technologies and OS : • UML • MOF • EMF, GMF, Xtext, oAW,... Vendor-specific technologies: • MS Visual Studio, Oslo • MetaCase, ... • MPS, Intensional, ... Research Technologies: • Stratego, ... KISS @ OOPSLA 09

  7. KISS: Aims and Core Values • Automate software construction from domain models. • Work with domain specific assets • Support the emergence of supply chains. • Open Source Infrastructure • Support the Agile Manifesto • Language Definition covers all Use Cases. KISS @ OOPSLA 09

  8. Interoperability: Tool Descriptors KISS @ OOPSLA 09

  9. Interoperability: Tool Chains KISS @ OOPSLA 09

  10. Interoperability: DSML Tools KISS @ OOPSLA 09

  11. Interoperability: Syntax KISS @ OOPSLA 09

  12. Interoperability: Syntax KISS @ OOPSLA 09

  13. Interoperability: Tool Interfaces KISS @ OOPSLA 09

  14. Interoperability: Behaviour KISS @ OOPSLA 09

  15. Interoperability: Meta-Models KISS @ OOPSLA 09

  16. Compliance Levels 0. No specific features are identifiable. 1. DSL tools interoperate through reified interfaces, e.g. persistence. 2. Tools interoperate through a common serialization format (shared meta-language through translation). 3. Dynamically shared data (shared meta-language). 4. Common language/model manipulation through common service (limited shared behaviour). 5. Interoperable behaviour through common behaviour representation. KISS @ OOPSLA 09

  17. Interoperability Compliance Levels KISS @ OOPSLA 09

More Related