MDSE In Practice - Chapter 6 - Reading Notes

-

 Chapter 6 - Modeling Languages At A Glance

6.1 Anatomy of Modeling Languages
  • Ingredients: Abstract syntax, Concrete syntax, Semantics
  • GPL - General Pruposes Language.  DSL - Domain Specific Language.
  • Semantics can be defined as
    • Denotational
    • Operational
    • Transactional
6.2 Multi-View Modeling and Language Extensibility
  • Used to model orthogonal aspects of a system.
  • Typical: static/structural & dynamic.
  • Extensibility.  Sometimes GPL+specialization -> DSL
  • e.g. UML->SysML, SoaML
6.3 General-Purpose Vs Domain Specific Modeling Languages
  • DSLs - "are languages that are designed on purpose for a specific domain, context, or company, to support people who need to describe things in that domain."
  • GPL - "represent modeling notations that can be applied to any sector or domain for modeling purposes."
  • While UML might be faulty we know its faults.  Beware of creating your own UML.
6.4 General-Purpose Modeling: The case of UML
  • Well known & understood.
  • Full-fledged language suits.
  • Synthesis of a set of languages.
  • Complex, borne out of its history.
6.4.1 Design Practices
  • Uses a set of models.
  • Different levels of detail.
  • Extensible.
  • Supports pattern based design.
6.4.2 Structure Diagrams (or Static Diagrams)
  • Two levels
    • Conceptual Item
    • Architectural Representation
  • Conceptual ItemLevel
    • Class Diagram
    • Composite Structure Diagram
    • Object Diagram
  • Architectural Representation
    • Component Diagram
    • Package Diagram
    • Deployment Diagram
6.4.3 Behaviour Diagrams (or Dynamic Diagrams)
  • Use-Case Diagrams.
  • Activity Diagrams
  • State Machine Diagram
  • Interaction Diagrams
    • Sequence Diagram
    • Interaction Overview Diagram
    • Timing Diagram
6.4.4 UML Tools
- See Wikipedia

6.4.5 Criticisms and Evolution of UML
  • Criticism: Verbose, Cumbersome, Incoherent, Not easy to use in domain-specific scenarios.
  • Being addressed by OMG.
6.5 UML Extensibility: The Middle Way Between GPL and DSL

6.5.1 Stereotypes
  • Extend meta-classes
  • By
    • Base Metaclasses
    • Constraints
    • Tagged Values
    • Icon
6.5.2 Predicates
  • Restriction predicates. e.g. OCL

6.5.3 Tagged Values
  • tag-value pairs associated with a stereotype.
6.5.4 UML Profiling
  • A way of packaging extensions to define a DSL
  • Examples: SysML, SoaML, etc.
6.6 Overview of DSLs
  • Advantage is that it is suited specific domain& does not require users to learn a GPL.
6.6.1 Principles of DSLs
  • The language must provide good abstractions & be easy to use.
  • The language must not depend on a sole person's expertise.
  • The language must evolve.
  • The language must come with supporting tools & methods.
  • A good DSL must be open for extensions & closed for modifications.
  • Classification
    • Focus: Vertical (e.g. from an industry) or Horizontal (broad, e.g. SQL)
    • Style: Declarative or Imperative
    • Notation: Graphical or Textual
    • Internality: External (independent) or Internal (relies on extending a host language)
    • Execution: Model interpretation or Code generation
6.6.2 Some examples of DSLs
  • VHDL
  • I*
  • BPMN
  • IFML
6.7 Defining Modeling Constraints (OCL)
  • OCL - Object Constraint Language
  • A typed, declarative & side-effect-free specification language.
  • Constraints expressed as a set of invariants in the context of specified types.

Comments

Post a Comment

Popular posts from this blog

Creating Items in Sparx EA via Java

-
Introduction This short post provides guidance on how to create "things" in a Sparx EA model via the Java API. Theory Creating "things" in EA via Java is driven by the Add New method and the Collection class. The first example in the code is adding a "view" to an existing root node. The code below will retrieve the root GUID if the "i" variable is set to 0; rootPackageID = rep . GetModels (). GetAt ( i ). GetPackageGUID (); After obtaining the root GUID it is possible to create a view under the root node. Note the process of retrieving the packages under the root and placing them in a collection. The Add New process is driven from the Collection. Importantly, for a view, the code needs to set a flag which indicates a particular icon. This process is only required for views. org . sparx . Package root = rep . GetPackageByGuid ( rootPackageID ); // get the root Collection < org . sparx . Package > subPackages = r...
Read more

Flexible Method Pattern

-
This is the first in a series of posts on some of the coding patterns that I have been using with Peso .  I use the term 'pattern' loosely, referring to common code patterns that are repeated through out the implementation of the framework. The intent of the Flexible Method Pattern is to give callers of the framework functions/methods as much flexibility as possible, minimise the amount of boiler plate code required to use the framework, and keep the code as streamlined and simple as possible.  This pattern is made up of two parts. Type Specific Handling Often we might need to have the same logical operation being performed, pretty much the same way, for two or more different types corresponding to the same logical input. For example, a common operation is to retrieve an element given an ElementID or an ElementGUID.  There are two different methods on the Repository object to do this.  In the framework we can do a bit better than this.  We can write ...
Read more

Java and Enterprise Architect from Sparx Systems – Getting Started

-
Image
This is the first in a series of blogs relating to the use of Java with  Enterprise Architect (EA)  from Sparx Systems. The purpose of the blogs is to provide a starting point for Java programmers in their use of the language with EA. The  official post  from Sparx Systems is to use Java as a scripting language within EA. While this is useful, I have a preference to create Java applications outside of EA. The diagram below describes how a Java application can be created which interfaces into the  Sparx Object Model . The  connection  between the Java application and EA is a COM object (SSJavaCOM.dll) provided by EA. This  page  from EA provides information on how to install the COM object within your windows environment. The Java application’s “view” of the Object Model is via a JAR file ( eaapi) which provides the  linkage  between the COM object and the Java software. I use  Netbeans  for Java Develop...
Read more