Analyzing the Complexity of Domain Model Representations

Leitner, Andrea; Weiß, Reinhold; Kreiner, Christian

doi:10.1109/ecbs.2012.15

Cited by 8 publications

(2 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In fact, for most domains one domain model seems to be sufficient, since estimations for the other modeling paradigm can be derived from this domain model. The detailed metrics are described in [5]. Figure 2 shows the representation complexity of a domain model consisting of drivetrain configurations as well as software functions.…”

Section: Benefits Of Domain Multi-modelingmentioning

confidence: 99%

Optimizing problem space representations through domain multi-modeling

Leitner

Weis

Kreiner

2012

2012 Third International Workshop on Product LinE Approaches in Software Engineering (PLEASE)

Self Cite

View full text Add to dashboard Cite

This work states that there is a need for an optimized problem space representation for heterogeneous domains. We identify two modeling paradigms widely used in practice: Domain-Specific Modeling (DSM) and FeatureOriented Domain Modeling (FODM). Each modeling paradigm favors different domain characteristics. Especially the fact that software often is embedded either in a system or in a process and, therefore, is strongly influenced by its environment enforces the demand for a combined representation.We propose a concept for a multi-modeling approach based on existing technology. Multi-modeling means the combination of the two main modeling paradigms to represent a heterogeneous domain. The major benefit of the approach is the reduction of representation complexity by optimizing the representation of single subdomains. This will be shown on one representative case study from the automotive domain. Another advantage is the improved stakeholder communication because of familiar notations. A discussion of limitations shows potential for future work.

show abstract

Section: Benefits Of Domain Multi-modelingmentioning

confidence: 99%

Optimizing problem space representations through domain multi-modeling

Leitner

Weis

Kreiner

2012

2012 Third International Workshop on Product LinE Approaches in Software Engineering (PLEASE)

Self Cite

View full text Add to dashboard Cite

show abstract

“…To measure the domain model complexity we use the metrics from [3]. These metrics simply count the elements of the metamodel and distinguish between interface complexity, element complexity, and property complexity.…”

Section: Domain Model Complexitymentioning

confidence: 99%

Evaluation of Domain Modeling Decisions for Two Identical Domain Specific Languages

Preschern¹,

Kajtazovic²,

Kreiner³

2014

LNSE

Self Cite

View full text Add to dashboard Cite

Abstract-Decisions on domain model representations and on domain model scoping are a key task when developing software product lines. However, there is little guidance for t he choice whether a domain model should be represented by feature-oriented domain models or by domain-specific models and whether a domain should be described by a single domain model or by multiple domain models.In this paper we apply a method for assessing domain models on two automation system case studies which use domain specific languages (DSLs). The two case studies cover the same domain (warehouse automation) and were developed independently from one another. We evaluate how well the results of the domain model assessment method are suited for our case studies. For the evaluation we consider the development times of the DSLs, the size of the models, and we calculate DSL and code complexity metrics.

show abstract