On OO Design Consistency in Iterative Development

Bellur, Umesh; Vallieswaran, V.

doi:10.1109/itng.2006.102

Cited by 15 publications

(12 citation statements)

References 8 publications

(6 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In order to evaluate the consistency of the design models, these authors propose evaluating the well-formedness of UML diagrams. The proposal of Bellur and Vallieswaran [12] extends the proposal of Lange and Chaudron [27] focusing on the quality of UML conceptual models as well as on the code. These authors identify 4 types of defects for use-case diagrams, 2 types of defects for sequence diagrams, 5 types of defects for the specification of the method sequences, 3 types of defects for the class diagram, 8 types of defects for the state transition diagrams, 2 types of defects for the component diagram, and 2 types of defects for the deployment diagram.…”

Section: Related Workmentioning

confidence: 96%

“…Bellur and Vallieswaran [12] perform an impact analysis of UML design models. This analysis evaluates the consistency of the design and the impact of a design change over the code.…”

Section: Related Workmentioning

confidence: 99%

“…Currently, there are some approaches that detect defects in conceptual models (such as [11,12]), which are mostly focused on 2 Advances in Software Engineering the detection of defects that come from either the data perspective (data models) or the process perspective (process models). However, defect detection has not been clearly accomplished from the interaction perspective (interaction models) even though all of these perspectives (data, process, and interaction modeling) are essential to specify a correct conceptual schema used in an MDD context [13].…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

A Quality Model for Conceptual Models of MDD Environments

Marín

Giachetti

Pastor

et al. 2010

Advances in Software Engineering

View full text Add to dashboard Cite

In Model-Driven Development (MDD) processes, models are key artifacts that are used as input for code generation. Therefore, it is very important to evaluate the quality of these input models in order to obtain high-quality software products. The detection of defects is a promising technique to evaluate software quality, which is emerging as a suitable alternative for MDD processes. The detection of defects in conceptual models is usually manually performed. However, since current MDD standards and technologies allow both the specification of metamodels to represent conceptual models and the implementation of model transformations to automate the generation of final software products, it is possible to automate defect detection from the defined conceptual models. This paper presents a quality model that not only encapsulates defect types that are related to conceptual models but also takes advantage of current standards in order to automate defect detection in MDD environments.

show abstract

Section: Related Workmentioning

confidence: 96%

“…Bellur and Vallieswaran [12] perform an impact analysis of UML design models. This analysis evaluates the consistency of the design and the impact of a design change over the code.…”

Section: Related Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

A Quality Model for Conceptual Models of MDD Environments

Marín

Giachetti

Pastor

et al. 2010

Advances in Software Engineering

View full text Add to dashboard Cite

show abstract

“…In order to evaluate the consistency of the design models, these authors propose the evaluation of the well-formedness of UML diagrams. The proposal of Bellur et al [Bellur and Vallieswaran 2006] extends the proposal of Lange et al [Lange and Chaudron 2004] focusing on the quality of UML conceptual models as well as on the code. The general characteristics of the Bellur et al proposal are the following:…”

Section: Proposal Of Bellur Et Al (2006)mentioning

confidence: 91%

“…Bellur et al [Bellur and Vallieswaran 2006] perform an impact analysis of UML design models. This analysis evaluates the consistency of the design and the impact of a design change over the code.…”

Section: Proposal Of Bellur Et Al (2006)mentioning

confidence: 99%

Functional Size Measurement and Model Verification for Software Model-Driven Developments: A COSMIC-based Approach

Campusano¹,

Mariela²

View full text Add to dashboard Cite

UML models consistency management: Guidelines for software quality manager

Bashir

Lee

Khan

et al. 2016

International Journal of Information Management

View full text Add to dashboard Cite

Abstract-Unified Modeling Language (UML) has become the de-facto standard to design today's large-size object-oriented systems. However, focusing on multiple UML diagrams is a main cause of breaching the consistency problem, which ultimately reduces the overall software model's quality. Consistency management techniques are widely used to ensure the model consistency by correct model-to-model and model-to-code transformation. Consistency management becomes a promising area of research especially for model-driven architecture. In this paper, we extensively review UML consistency management techniques. The proposed techniques have been classified based on the parameters identified from the research literature. Moreover, we performed a qualitative comparison of consistency management techniques in order to identify current research trends, challenges and research gaps in this field of study. Based on the results, we concluded that researchers have not provided more attention on exploring inter-model and semantic consistency problems. Furthermore, state-of-the-art consistency management techniques mostly focus only on three UML diagrams (i.e., class, sequence and state chart) and the remaining UML diagrams have been overlooked. Consequently, due to this incomplete body of knowledge, researchers are unable to take full advantage of overlooked UML diagrams, which may be otherwise useful to handle the consistency management challenge in an efficient manner.

show abstract

On OO Design Consistency in Iterative Development

Abstract: In agile software development practices, the system evolves iteratively but does so in a manner consistent with its design rationale.

Cited by 15 publications

References 8 publications

A Quality Model for Conceptual Models of MDD Environments

A Quality Model for Conceptual Models of MDD Environments

Functional Size Measurement and Model Verification for Software Model-Driven Developments: A COSMIC-based Approach

UML models consistency management: Guidelines for software quality manager

Contact Info

Product

Resources

About