Principles for modeling language design

Paige, Richard F.; Ostroff, Jonathan S.; Brooke, Phillip J.

doi:10.1016/s0950-5849(00)00109-9

Cited by 51 publications

(38 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As we are mainly concerned about gathering basic metamodel information, we do not focus on building high-quality, sophisticated metamodels. Readers who are interested in the latter are referred to [6] [22][17] [26].…”

Section: Discussionmentioning

confidence: 99%

See 1 more Smart Citation

Semi-automatic generation of metamodels from model sketches

Wüest

Seyff

Glinz

2013

2013 28th IEEE/ACM International Conference on Automated Software Engineering (ASE)

View full text Add to dashboard Cite

Abstract-Traditionally, metamodeling is an upfront activity performed by experts for defining modeling languages. Modeling tools then typically restrict modelers to using only constructs de-fined in the metamodel. This is inappropriate when users want to sketch graphical models without any restrictions and only later assign meanings to the sketched elements. Upfront metamodeling also complicates the creation of domain-specific languages, as it requires experts with both domain and metamodeling expertise. In this paper we present a new approach that supports model-ers in creating metamodels for diagrams they have sketched or are currently sketching. Metamodels are defined in a semi-automatic, interactive way by annotating diagram elements and automated model analysis. Our approach requires no metamodel-ing expertise and supports the co-evolution of models and meta-models. Abstract-Traditionally, metamodeling is an upfront activity performed by experts for defining modeling languages. Modeling tools then typically restrict modelers to using only constructs defined in the metamodel. This is inappropriate when users want to sketch graphical models without any restrictions and only later assign meanings to the sketched elements. Upfront metamodeling also complicates the creation of domain-specific languages, as it requires experts with both domain and metamodeling expertise.In this paper we present a new approach that supports modelers in creating metamodels for diagrams they have sketched or are currently sketching. Metamodels are defined in a semiautomatic, interactive way by annotating diagram elements and automated model analysis. Our approach requires no metamodeling expertise and supports the co-evolution of models and metamodels.

show abstract

Section: Discussionmentioning

confidence: 99%

“…Design guidelines for DSLs can be found in [17] and [22]. [6] and [26] discuss design patterns for metamodels.…”

mentioning

confidence: 99%

Semi-automatic generation of metamodels from model sketches

Wüest

Seyff

Glinz

2013

2013 28th IEEE/ACM International Conference on Automated Software Engineering (ASE)

View full text Add to dashboard Cite

show abstract

“…This list was prioritized by a single-criterion AHP process [21] and these issues were subsequently tackled by a review of relevant literature. This resulted in a list of possible solutions, which were evaluated according to the design principles of Paige et al [22] to ensure consistency with the original design principles of the CHOOSE modeling language. In this respect, the relevant criteria are simplicity (i.e., no unnecessary complexity is introduced), uniqueness (i.e., no redundant or overlapping features), and consistency (i.e., language features meet design goals).…”

Section: Methodsmentioning

confidence: 99%

“…In table 1, these issues are ranked according to their importance, which was determined by using a single-criterion AHP procedure [21]. In the next paragraphs, solutions are formulated for each problem and an alternative is chosen according to the relevant design principles of Paige et al [22] (i.e., simplicity, uniqueness, and consistency). Afterwards, these solutions are evaluated by the business stakeholders, who were involved in the case study.…”

Section: Metamodelmentioning

confidence: 99%

Simplicity is not Simple: How Business Architecture in One of Belgium’s Biggest Companies Can Be Simple and Easy-to-Use

Clercq

Bernaert

Roelens

et al. 2015

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract. As organizations are becoming more complex, Enterprise Architecture (EA) serves as an important means to align the strategy with the operations and to achieve business/IT (i.e., Information Technology) alignment. Although numerous approaches have been designed for large enterprises, little EA research was oriented towards smalland medium-sized enterprises (SMEs). However, both organizational types are fundamentally different and require a tailored approach. Therefore, CHOOSE was designed as an EA approach that is in accordance with the needs of SMEs. By performing a case study in the department of a large enterprise, this paper aims to investigate how CHOOSE can be used outside its original context. More specifically, it will be examined how the metamodel and modeling method could be adjusted to deliver an overview and valuable insights about a complex business reality. To realize this, potential solutions for the encountered issues are formulated and evaluated by the involved business stakeholders.

show abstract

“…• Models on different levels of abstraction and from different viewpoints: An example is the OMG MDA's viewpoints of Computational Independent Models (CIM), versus Platform Independent Models (PIM) and Platform Specific Models (PSM) [20]. Relations between these models are important when evaluating them for some quality characteristics.…”

Section: What Characterizes Model-driven Engineering?mentioning

confidence: 99%

Developing a Quality Framework for Model-Driven Engineering

Mohagheghi

Dehlen

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. This paper presents some related work on quality frameworks and requirements for evaluating them. It also discusses characteristics of modeldriven engineering that are important when building a quality framework, such as its use of models in several stages of development and maintenance, generation of other artifacts from models and its multi-abstraction level approach that requires consistency and traceability. We present a 7-step process on how to define a quality framework that is adapted to model-driven engineering, and which integrates quality engineering with quality evaluation. As an example, the framework is applied on transformation quality. We maintain that the transformation process and transformation mapping should be discussed separately, as they require different approaches, and suggest quality goals, quality-carrying properties to achieve the quality goals and methods for evaluating these properties.

show abstract

Principles for modeling language design

Cited by 51 publications

References 8 publications

Semi-automatic generation of metamodels from model sketches

Semi-automatic generation of metamodels from model sketches

Simplicity is not Simple: How Business Architecture in One of Belgium’s Biggest Companies Can Be Simple and Easy-to-Use

Developing a Quality Framework for Model-Driven Engineering

Contact Info

Product

Resources

About