Requirements modeling with the aspect-oriented user requirements notation (AoURN): A case study

29Citations
Citations of this article
28Readers
Mendeley users who have this article in their library.
Get full text

Abstract

The User Requirements Notation (URN) is a recent ITU-T standard that supports requirements engineering activities. The Aspect-oriented URN (AoURN) adds aspect-oriented concepts to URN, creating a unified framework that allows for scenario-based, goal-oriented, and aspect-oriented modeling. AoURN is applied to the car crash crisis management system (CCCMS), modeling its functional and non-functional requirements (NFRs). AoURN generally models all use cases, NFRs, and stakeholders as individual concerns and provides general guidelines for concern identification. AoURN handles interactions between concerns, capturing their dependencies and conflicts as well as the resolutions. We present a qualitative comparison of aspect-oriented techniques for scenario-based and goal-oriented requirements engineering. An evaluation carried out based on the metrics adapted from literature and a task-based evaluation suggest that AoURN models are more scalable than URN models and exhibit better modularity, reusability, and maintainability. © 2010 Springer-Verlag.

Cite

CITATION STYLE

APA

Mussbacher, G., Amyot, D., Araújo, J., & Moreira, A. (2010). Requirements modeling with the aspect-oriented user requirements notation (AoURN): A case study. In Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) (Vol. 6210 LNCS, pp. 23–68). https://doi.org/10.1007/978-3-642-16086-8_2

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free