Composing non-functional concerns with use cases for trade-off analysis

Abelyn Methanie Laurito, Shingo Takada

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

Abstract

Functional and non-functional concerns are identified and refined during requirements analysis. These concerns are not always consistent; there may be conflicts between them, which must be discovered and resolved through trade-off analysis. Aspect-Oriented Requirements Engineering (AORE) can be used to first describe concerns independently of each other and then generate their composition. These are used to find conflicts and to conduct trade-off analysis. This paper uses the requirements conflict matrix (RCM) to represent the composition. It shows the positive or negative effect of non-functional concerns over use cases and other nonfunctional concerns. In order to support the RCM creation, Use Case Editor (UCEd), which is a tool that parses use case descriptions to provide simulation for conflict analysis, is extended to describe non-functional concerns and their relationships to other concerns. The extended tool uses the descriptions to generate representations for the composition in the form of RCM. The RCM is used as a reference for the "Conflicting Forces" method in order to gather questions for trade-off analysis with the stakeholders. A case study was performed to assess the effectiveness of the process and its tool support for trade-off analysis.

Original languageEnglish
Title of host publicationProceedings of the IASTED International Conference on Software Engineering and Applications, SEA 2010
Pages468-476
Number of pages9
DOIs
Publication statusPublished - 2010
EventIASTED International Conference on Software Engineering and Applications, SEA 2010 - Marina del Rey, CA, United States
Duration: 2010 Nov 82010 Nov 10

Other

OtherIASTED International Conference on Software Engineering and Applications, SEA 2010
CountryUnited States
CityMarina del Rey, CA
Period10/11/810/11/10

Fingerprint

Chemical analysis
Requirements engineering

Keywords

  • Aspect-Oriented Requirements Engineering
  • Non-functional concerns
  • Requirements analysis tool
  • Trade-off analysis
  • Use cases

ASJC Scopus subject areas

  • Software

Cite this

Laurito, A. M., & Takada, S. (2010). Composing non-functional concerns with use cases for trade-off analysis. In Proceedings of the IASTED International Conference on Software Engineering and Applications, SEA 2010 (pp. 468-476) https://doi.org/10.2316/P.2010.725-060

Composing non-functional concerns with use cases for trade-off analysis. / Laurito, Abelyn Methanie; Takada, Shingo.

Proceedings of the IASTED International Conference on Software Engineering and Applications, SEA 2010. 2010. p. 468-476.

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

Laurito, AM & Takada, S 2010, Composing non-functional concerns with use cases for trade-off analysis. in Proceedings of the IASTED International Conference on Software Engineering and Applications, SEA 2010. pp. 468-476, IASTED International Conference on Software Engineering and Applications, SEA 2010, Marina del Rey, CA, United States, 10/11/8. https://doi.org/10.2316/P.2010.725-060
Laurito AM, Takada S. Composing non-functional concerns with use cases for trade-off analysis. In Proceedings of the IASTED International Conference on Software Engineering and Applications, SEA 2010. 2010. p. 468-476 https://doi.org/10.2316/P.2010.725-060
Laurito, Abelyn Methanie ; Takada, Shingo. / Composing non-functional concerns with use cases for trade-off analysis. Proceedings of the IASTED International Conference on Software Engineering and Applications, SEA 2010. 2010. pp. 468-476
@inproceedings{c404206f2b7c4e9c996d41b6f54103b5,
title = "Composing non-functional concerns with use cases for trade-off analysis",
abstract = "Functional and non-functional concerns are identified and refined during requirements analysis. These concerns are not always consistent; there may be conflicts between them, which must be discovered and resolved through trade-off analysis. Aspect-Oriented Requirements Engineering (AORE) can be used to first describe concerns independently of each other and then generate their composition. These are used to find conflicts and to conduct trade-off analysis. This paper uses the requirements conflict matrix (RCM) to represent the composition. It shows the positive or negative effect of non-functional concerns over use cases and other nonfunctional concerns. In order to support the RCM creation, Use Case Editor (UCEd), which is a tool that parses use case descriptions to provide simulation for conflict analysis, is extended to describe non-functional concerns and their relationships to other concerns. The extended tool uses the descriptions to generate representations for the composition in the form of RCM. The RCM is used as a reference for the {"}Conflicting Forces{"} method in order to gather questions for trade-off analysis with the stakeholders. A case study was performed to assess the effectiveness of the process and its tool support for trade-off analysis.",
keywords = "Aspect-Oriented Requirements Engineering, Non-functional concerns, Requirements analysis tool, Trade-off analysis, Use cases",
author = "Laurito, {Abelyn Methanie} and Shingo Takada",
year = "2010",
doi = "10.2316/P.2010.725-060",
language = "English",
isbn = "9780889868786",
pages = "468--476",
booktitle = "Proceedings of the IASTED International Conference on Software Engineering and Applications, SEA 2010",

}

TY - GEN

T1 - Composing non-functional concerns with use cases for trade-off analysis

AU - Laurito, Abelyn Methanie

AU - Takada, Shingo

PY - 2010

Y1 - 2010

N2 - Functional and non-functional concerns are identified and refined during requirements analysis. These concerns are not always consistent; there may be conflicts between them, which must be discovered and resolved through trade-off analysis. Aspect-Oriented Requirements Engineering (AORE) can be used to first describe concerns independently of each other and then generate their composition. These are used to find conflicts and to conduct trade-off analysis. This paper uses the requirements conflict matrix (RCM) to represent the composition. It shows the positive or negative effect of non-functional concerns over use cases and other nonfunctional concerns. In order to support the RCM creation, Use Case Editor (UCEd), which is a tool that parses use case descriptions to provide simulation for conflict analysis, is extended to describe non-functional concerns and their relationships to other concerns. The extended tool uses the descriptions to generate representations for the composition in the form of RCM. The RCM is used as a reference for the "Conflicting Forces" method in order to gather questions for trade-off analysis with the stakeholders. A case study was performed to assess the effectiveness of the process and its tool support for trade-off analysis.

AB - Functional and non-functional concerns are identified and refined during requirements analysis. These concerns are not always consistent; there may be conflicts between them, which must be discovered and resolved through trade-off analysis. Aspect-Oriented Requirements Engineering (AORE) can be used to first describe concerns independently of each other and then generate their composition. These are used to find conflicts and to conduct trade-off analysis. This paper uses the requirements conflict matrix (RCM) to represent the composition. It shows the positive or negative effect of non-functional concerns over use cases and other nonfunctional concerns. In order to support the RCM creation, Use Case Editor (UCEd), which is a tool that parses use case descriptions to provide simulation for conflict analysis, is extended to describe non-functional concerns and their relationships to other concerns. The extended tool uses the descriptions to generate representations for the composition in the form of RCM. The RCM is used as a reference for the "Conflicting Forces" method in order to gather questions for trade-off analysis with the stakeholders. A case study was performed to assess the effectiveness of the process and its tool support for trade-off analysis.

KW - Aspect-Oriented Requirements Engineering

KW - Non-functional concerns

KW - Requirements analysis tool

KW - Trade-off analysis

KW - Use cases

UR - http://www.scopus.com/inward/record.url?scp=84862297305&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=84862297305&partnerID=8YFLogxK

U2 - 10.2316/P.2010.725-060

DO - 10.2316/P.2010.725-060

M3 - Conference contribution

AN - SCOPUS:84862297305

SN - 9780889868786

SP - 468

EP - 476

BT - Proceedings of the IASTED International Conference on Software Engineering and Applications, SEA 2010

ER -