Home > Research > Publications & Outputs > Modeling and composing scenario-based requireme...

Research

Links

Text available via DOI:

View graph of relations

Modeling and composing scenario-based requirements with aspects

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review

Published

Standard

Modeling and composing scenario-based requirements with aspects. / Araujo, J.; Whittle, J.; Kim, D.K.
Requirements Engineering Conference, 2004. Proceedings. 12th IEEE International. IEEE, 2004. p. 58-67.

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review

Harvard

Araujo, J, Whittle, J & Kim, DK 2004, Modeling and composing scenario-based requirements with aspects. in Requirements Engineering Conference, 2004. Proceedings. 12th IEEE International. IEEE, pp. 58-67. https://doi.org/10.1109/ICRE.2004.1335664

APA

Araujo, J., Whittle, J., & Kim, D. K. (2004). Modeling and composing scenario-based requirements with aspects. In Requirements Engineering Conference, 2004. Proceedings. 12th IEEE International (pp. 58-67). IEEE. https://doi.org/10.1109/ICRE.2004.1335664

Vancouver

Araujo J, Whittle J, Kim DK. Modeling and composing scenario-based requirements with aspects. In Requirements Engineering Conference, 2004. Proceedings. 12th IEEE International. IEEE. 2004. p. 58-67 doi: 10.1109/ICRE.2004.1335664

Author

Araujo, J. ; Whittle, J. ; Kim, D.K. / Modeling and composing scenario-based requirements with aspects. Requirements Engineering Conference, 2004. Proceedings. 12th IEEE International. IEEE, 2004. pp. 58-67

Bibtex

@inproceedings{08afb08e545746cd9dbc267e5ff46d15,
title = "Modeling and composing scenario-based requirements with aspects",
abstract = "There has been significant recent interest, within the aspect-oriented software development (AOSD) community, in representing crosscutting concerns at various stages of the software lifecycle. However, most of these efforts have concentrated on the design and implementation phases. We focus in This work on representing aspects during use case modeling. In particular, we focus on scenario-based requirements and show how to compose aspectual and non-aspectual scenarios so that they can be simulated as a whole. Non-aspectual scenarios are modeled as UML sequence diagrams. Aspectual scenarios are modeled as interaction pattern specifications (IPSs). In order to simulate them, the scenarios are transformed into a set of executable state machines using an existing state machine synthesis algorithm. Previous work composed aspectual and non-aspectual scenarios at the sequence diagram level. In This work, the composition is done at the state machine level.",
author = "J. Araujo and J. Whittle and D.K. Kim",
year = "2004",
doi = "10.1109/ICRE.2004.1335664",
language = "English",
isbn = "0-7695-2174-6",
pages = "58--67",
booktitle = "Requirements Engineering Conference, 2004. Proceedings. 12th IEEE International",
publisher = "IEEE",

}

RIS

TY - GEN

T1 - Modeling and composing scenario-based requirements with aspects

AU - Araujo, J.

AU - Whittle, J.

AU - Kim, D.K.

PY - 2004

Y1 - 2004

N2 - There has been significant recent interest, within the aspect-oriented software development (AOSD) community, in representing crosscutting concerns at various stages of the software lifecycle. However, most of these efforts have concentrated on the design and implementation phases. We focus in This work on representing aspects during use case modeling. In particular, we focus on scenario-based requirements and show how to compose aspectual and non-aspectual scenarios so that they can be simulated as a whole. Non-aspectual scenarios are modeled as UML sequence diagrams. Aspectual scenarios are modeled as interaction pattern specifications (IPSs). In order to simulate them, the scenarios are transformed into a set of executable state machines using an existing state machine synthesis algorithm. Previous work composed aspectual and non-aspectual scenarios at the sequence diagram level. In This work, the composition is done at the state machine level.

AB - There has been significant recent interest, within the aspect-oriented software development (AOSD) community, in representing crosscutting concerns at various stages of the software lifecycle. However, most of these efforts have concentrated on the design and implementation phases. We focus in This work on representing aspects during use case modeling. In particular, we focus on scenario-based requirements and show how to compose aspectual and non-aspectual scenarios so that they can be simulated as a whole. Non-aspectual scenarios are modeled as UML sequence diagrams. Aspectual scenarios are modeled as interaction pattern specifications (IPSs). In order to simulate them, the scenarios are transformed into a set of executable state machines using an existing state machine synthesis algorithm. Previous work composed aspectual and non-aspectual scenarios at the sequence diagram level. In This work, the composition is done at the state machine level.

U2 - 10.1109/ICRE.2004.1335664

DO - 10.1109/ICRE.2004.1335664

M3 - Conference contribution/Paper

SN - 0-7695-2174-6

SP - 58

EP - 67

BT - Requirements Engineering Conference, 2004. Proceedings. 12th IEEE International

PB - IEEE

ER -