Revealing Crosscutting Concerns in Textual Requirements Documents: An Exploratory Study with Industry Systems

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

8 Citations (Scopus)

Abstract

It is well-known that effective requirements analysis plays a crucial role in the quality of software systems. However, the scattered and tangled nature of certain system's concerns can hinder the proper understanding and treatment of import requirements. A key goal of prominent Aspect-Oriented Requirement Engineering (AORE) techniques, such as EA-Miner and Theme/Doc, is to support the automatic identification of crosscutting concerns at textual requirements documents. However, it is still unknown whether and which of these approaches produce accurate results in large text documents and according to the software engineers' expectations. In this context, this paper presents an analysis regarding the accuracy of the aforementioned AORE approaches when processing requirements of two industry software systems. Around 300 pages of requirements descriptions in these systems were the target of our investigation. In general, EA-Miner suffered more than Theme/Doc from the incompleteness and inconsistencies of requirements documents. In addition, other factors can differently influence each approach's accuracy, such as: the participation of requirements engineers, and the level of details provided in the requirements document.
Original languageUnknown
Title of host publicationCBSOFT - SBES
Pages111-120
Publication statusPublished - 1 Jan 2012
Event26º Simpósio Brasileiro de Engenharia de Software (SBES) -
Duration: 1 Jan 2012 → …

Conference

Conference26º Simpósio Brasileiro de Engenharia de Software (SBES)
Period1/01/12 → …

Cite this

@inproceedings{3d135ed64ed545efafdd56f80cb4b3fc,
title = "Revealing Crosscutting Concerns in Textual Requirements Documents: An Exploratory Study with Industry Systems",
abstract = "It is well-known that effective requirements analysis plays a crucial role in the quality of software systems. However, the scattered and tangled nature of certain system's concerns can hinder the proper understanding and treatment of import requirements. A key goal of prominent Aspect-Oriented Requirement Engineering (AORE) techniques, such as EA-Miner and Theme/Doc, is to support the automatic identification of crosscutting concerns at textual requirements documents. However, it is still unknown whether and which of these approaches produce accurate results in large text documents and according to the software engineers' expectations. In this context, this paper presents an analysis regarding the accuracy of the aforementioned AORE approaches when processing requirements of two industry software systems. Around 300 pages of requirements descriptions in these systems were the target of our investigation. In general, EA-Miner suffered more than Theme/Doc from the incompleteness and inconsistencies of requirements documents. In addition, other factors can differently influence each approach's accuracy, such as: the participation of requirements engineers, and the level of details provided in the requirements document.",
author = "J{\'u}nior, {Jo{\~a}o Baptista da Silva Ara{\'u}jo}",
year = "2012",
month = "1",
day = "1",
language = "Unknown",
pages = "111--120",
booktitle = "CBSOFT - SBES",

}

Júnior, JBDSA 2012, Revealing Crosscutting Concerns in Textual Requirements Documents: An Exploratory Study with Industry Systems. in CBSOFT - SBES. pp. 111-120, 26º Simpósio Brasileiro de Engenharia de Software (SBES), 1/01/12.

Revealing Crosscutting Concerns in Textual Requirements Documents: An Exploratory Study with Industry Systems. / Júnior, João Baptista da Silva Araújo.

CBSOFT - SBES. 2012. p. 111-120.

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

TY - GEN

T1 - Revealing Crosscutting Concerns in Textual Requirements Documents: An Exploratory Study with Industry Systems

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

PY - 2012/1/1

Y1 - 2012/1/1

N2 - It is well-known that effective requirements analysis plays a crucial role in the quality of software systems. However, the scattered and tangled nature of certain system's concerns can hinder the proper understanding and treatment of import requirements. A key goal of prominent Aspect-Oriented Requirement Engineering (AORE) techniques, such as EA-Miner and Theme/Doc, is to support the automatic identification of crosscutting concerns at textual requirements documents. However, it is still unknown whether and which of these approaches produce accurate results in large text documents and according to the software engineers' expectations. In this context, this paper presents an analysis regarding the accuracy of the aforementioned AORE approaches when processing requirements of two industry software systems. Around 300 pages of requirements descriptions in these systems were the target of our investigation. In general, EA-Miner suffered more than Theme/Doc from the incompleteness and inconsistencies of requirements documents. In addition, other factors can differently influence each approach's accuracy, such as: the participation of requirements engineers, and the level of details provided in the requirements document.

AB - It is well-known that effective requirements analysis plays a crucial role in the quality of software systems. However, the scattered and tangled nature of certain system's concerns can hinder the proper understanding and treatment of import requirements. A key goal of prominent Aspect-Oriented Requirement Engineering (AORE) techniques, such as EA-Miner and Theme/Doc, is to support the automatic identification of crosscutting concerns at textual requirements documents. However, it is still unknown whether and which of these approaches produce accurate results in large text documents and according to the software engineers' expectations. In this context, this paper presents an analysis regarding the accuracy of the aforementioned AORE approaches when processing requirements of two industry software systems. Around 300 pages of requirements descriptions in these systems were the target of our investigation. In general, EA-Miner suffered more than Theme/Doc from the incompleteness and inconsistencies of requirements documents. In addition, other factors can differently influence each approach's accuracy, such as: the participation of requirements engineers, and the level of details provided in the requirements document.

M3 - Conference contribution

SP - 111

EP - 120

BT - CBSOFT - SBES

ER -