Utilizing domain models for application design and validation

Reinhartz-Berger, Iris; Sturm, Arnon

doi:10.1016/j.infsof.2009.03.005

Cited by 38 publications

(17 citation statements)

References 37 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Conducting two experiments, Tsoury and Reinhartz-Berger [16,17] compared the comprehensibility of Cardinality-Based Feature Modeling (CBFM) [18] and Application-based DOmain Modeling (ADOM) [19]. The comparison is based on comprehensibility of commonality-and variability-related concepts, including mandatory and optional elements, dependencies, variation points and variants.…”

Section: Comparison Of Feature Modeling Languagesmentioning

confidence: 99%

Comprehending Feature Models Expressed in CVL

Reinhartz-Berger

Figl

Haugen

2014

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

Abstract. Feature modeling is a common way to present and manage variability of software and systems. As a prerequisite for effective variability management is comprehensible representation, the main aim of this paper is to investigate difficulties in understanding feature models. In particular, we focus on the comprehensibility of feature models as expressed in Common Variability Language (CVL), which was recommended for adoption as a standard by the Architectural Board of the Object M anagement Group . Using an experimental approach with participants familiar and unfamiliar with feature modeling, we analyzed comprehensibility in terms of comprehension score, time spent to complete tasks, and perceived difficulty of different feature modeling constructs. The results showed that familiarity with feature modeling did not influence the comprehension of mandatory, optional, and alternative features, although unfamiliar modelers perceived these elements more difficult than familiar modelers. OR relations were perceived as difficult regardless of the familiarity level, while constraints were significantly better understood by familiar modelers. The time spent to complete tasks was higher for familiar modelers.

show abstract

Section: Comparison Of Feature Modeling Languagesmentioning

confidence: 99%

Comprehending Feature Models Expressed in CVL

Reinhartz-Berger

Figl

Haugen

2014

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

show abstract

“…Several works explicitly refer to dependencies between elements in the form of «alternative_or», «alternative_XOR», «requires», and «mutux» stereotypes. In order to evaluate the comprehension and utilization of variability aspects in UML-based methods and to identify factors that may affect these activities, we conducted an empirical study with a method, called Application-based DOmain Modeling (ADOM) [ 26,27]. We chose this method over other UML-based methods since it explicitly refers to extension variability and in particular to the selection and the addition of variants in certain variation points, aspects which other UML-based methods tend to neglect.…”

Section: Variability Modeling In Uml-based Methodsmentioning

confidence: 99%

“…The «multiplicity» stereotype, which is elaborated in [ 26], is used for specifying the range of elements in a product artifact that can be classified as the same element in the core asset. Two tagged values, min and max, are used for defining the lowest and upper-most boundaries of that range.…”

Section: The Adom Methodsmentioning

confidence: 99%

“…Variability is specified in terms of mandatory vs. optional features, alternatives, OR features, 'require' and 'exclude' dependencies among features, feature groups, and composition rules. UML-based methods (e.g., [ 13], [ 26], [ 28], [ 32], and [ 34]) usually suggest profiles for handling variability-related issues, including specification of mandatory and optional elements, dependencies among elements, variation points, and possible variants [ 15]. Some UML-based methods suggest extending UML or representing variability aspects orthogonally to "regular" UML models of the product families, e.g., [ 14].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Evaluating Comprehension and Utilization of Variability Aspects in UML-Based Models

Reinhartz-Berger

Sturm

Tsoury

2012

Lecture Notes in Business Information Processing

Self Cite

View full text Add to dashboard Cite

Abstract. In Software Product Line Engineering (SPLE), the ability of a software artifact to be used in different contexts is very essential for productivity. In order to manage and support this ability, different variability modeling methods have been proposed. An important group of such methods are based on UML. These methods typically introduce profiles for specifying mandatory and optional elements, identifying dependencies between elements, and modeling variation points and possible variants. However, the assessment of these methods still lacks. In this work, we have done a first step towards evaluating the comprehension and utilization of variability issues in UMLbased models by suggesting a comparison framework which refers to different aspects of variability specification. Based on this framework, we chose a specific UML-based method -ADOM -and examined how advanced information systems students understood and utilized a model specified using this method. The results showed that the different means for specifying variability were understood and utilized only to a limited extent and that variation points were the least comprehensible variability specification means.

show abstract

“…Additionally, in the area of domain engineering, we adopt the principles suggested by the Application Based Domain Modeling (ADOM) approach [ 4]. ADOM supports building reusable assets on the one hand, and representing and managing knowledge in specific domains on the other hand.…”

Section: Introductionmentioning

confidence: 99%

Tool Support for Enforcing Security Policies on Databases

Abramov

Anson

Sturm

et al. 2012

Lecture Notes in Business Information Processing

Self Cite

View full text Add to dashboard Cite

Abstract. Security in general and database protection from unauthorized access in particular, are crucial for organizations. It has long been accepted that security requirements should be considered from the early stages of the development. However, such requirements tend to be neglected or dealt-with only at the end of the development process. The Security Modeling Tool presented in this study aims at enforcing developers, in particular database designers, to deal with database authorization requirements from the early stages of development. This software demonstration shows how the Security Modeling Tool assists to define organizational security policies and use them during the application development to create a secured database schema.

show abstract

Utilizing domain models for application design and validation

Cited by 38 publications

References 37 publications

Comprehending Feature Models Expressed in CVL

Comprehending Feature Models Expressed in CVL

Evaluating Comprehension and Utilization of Variability Aspects in UML-Based Models

Tool Support for Enforcing Security Policies on Databases

Contact Info

Product

Resources

About