Increasing Quality in Scenario Modelling with Model-Driven Development

Research output: Chapter in Book/Report/Conference proceedingConference contribution

2 Citations (Scopus)

Abstract

Models, with different levels of detail, share similar abstractions that can be reused by means of model-driven techniques such as transformations. For example, scenarios are a well-known technique in requirements engineering to represent behavioral flows in a software system. When using UML, scenarios are typically represented with activity models in the early stages of software development, while sequence models are used to describe more detailed object interactions as modeling progresses. This paper defines transformation rules to automate the migration from activity to sequence models. We present a case study illustrating the application of our transformation rules. Our preliminary assessment of the impact of the benefits of using these transformations points to: (i) a reduction of around 50% in the effort building sequence models, (ii) increased trace ability among models, and (iii) error prevention when migrating from different scenario notations.
Original languageUnknown
Title of host publicationQUATIC
Pages204-209
DOIs
Publication statusPublished - 1 Jan 2010
EventInternational Conference on the Quality of Information and Communications Technology (QUATIC) -
Duration: 1 Jan 2010 → …

Conference

ConferenceInternational Conference on the Quality of Information and Communications Technology (QUATIC)
Period1/01/10 → …

Cite this

@inproceedings{d099cdbdce424ed2bda2bfa695ea9387,
title = "Increasing Quality in Scenario Modelling with Model-Driven Development",
abstract = "Models, with different levels of detail, share similar abstractions that can be reused by means of model-driven techniques such as transformations. For example, scenarios are a well-known technique in requirements engineering to represent behavioral flows in a software system. When using UML, scenarios are typically represented with activity models in the early stages of software development, while sequence models are used to describe more detailed object interactions as modeling progresses. This paper defines transformation rules to automate the migration from activity to sequence models. We present a case study illustrating the application of our transformation rules. Our preliminary assessment of the impact of the benefits of using these transformations points to: (i) a reduction of around 50{\%} in the effort building sequence models, (ii) increased trace ability among models, and (iii) error prevention when migrating from different scenario notations.",
author = "J{\'u}nior, {Jo{\~a}o Baptista da Silva Ara{\'u}jo} and Moreira, {Ana Maria Diniz} and Goul{\~a}o, {Miguel Carlos Pacheco Afonso}",
year = "2010",
month = "1",
day = "1",
doi = "10.1109/QUATIC.2010.36",
language = "Unknown",
pages = "204--209",
booktitle = "QUATIC",

}

Júnior, JBDSA, Moreira, AMD & Goulão, MCPA 2010, Increasing Quality in Scenario Modelling with Model-Driven Development. in QUATIC. pp. 204-209, International Conference on the Quality of Information and Communications Technology (QUATIC), 1/01/10. https://doi.org/10.1109/QUATIC.2010.36

Increasing Quality in Scenario Modelling with Model-Driven Development. / Júnior, João Baptista da Silva Araújo; Moreira, Ana Maria Diniz; Goulão, Miguel Carlos Pacheco Afonso.

QUATIC. 2010. p. 204-209.

Research output: Chapter in Book/Report/Conference proceedingConference contribution

TY - GEN

T1 - Increasing Quality in Scenario Modelling with Model-Driven Development

AU - Júnior, João Baptista da Silva Araújo

AU - Moreira, Ana Maria Diniz

AU - Goulão, Miguel Carlos Pacheco Afonso

PY - 2010/1/1

Y1 - 2010/1/1

N2 - Models, with different levels of detail, share similar abstractions that can be reused by means of model-driven techniques such as transformations. For example, scenarios are a well-known technique in requirements engineering to represent behavioral flows in a software system. When using UML, scenarios are typically represented with activity models in the early stages of software development, while sequence models are used to describe more detailed object interactions as modeling progresses. This paper defines transformation rules to automate the migration from activity to sequence models. We present a case study illustrating the application of our transformation rules. Our preliminary assessment of the impact of the benefits of using these transformations points to: (i) a reduction of around 50% in the effort building sequence models, (ii) increased trace ability among models, and (iii) error prevention when migrating from different scenario notations.

AB - Models, with different levels of detail, share similar abstractions that can be reused by means of model-driven techniques such as transformations. For example, scenarios are a well-known technique in requirements engineering to represent behavioral flows in a software system. When using UML, scenarios are typically represented with activity models in the early stages of software development, while sequence models are used to describe more detailed object interactions as modeling progresses. This paper defines transformation rules to automate the migration from activity to sequence models. We present a case study illustrating the application of our transformation rules. Our preliminary assessment of the impact of the benefits of using these transformations points to: (i) a reduction of around 50% in the effort building sequence models, (ii) increased trace ability among models, and (iii) error prevention when migrating from different scenario notations.

U2 - 10.1109/QUATIC.2010.36

DO - 10.1109/QUATIC.2010.36

M3 - Conference contribution

SP - 204

EP - 209

BT - QUATIC

ER -