Controlled Experiment in Crosscutting Concerns Identification from Software Requirements Specification

• Guilherme Legramante Martins UNIPAMPA
• Maicon Bernardino UNIPAMPA
• João Pablo Silva da Silva UNIPAMPA
• Elder Macedo Rodrigues UNIPAMPA

DOI: https://doi.org/10.5753/eres.2020.13732

Resumo

The concern is a group of requirements with the same purpose, which are known as crosscutting concerns when they are scattered and tangled in the system. Identifying and separating these concerns is a matter of huge importance to software maintainability and evolution. For this, some approaches are proposed. There are few experimental studies comparing and analyzing these approaches in detail. In this paper, our aim is to provide empirical evidence about two approaches in this context. We conducted a controlled experiment to compare the effectiveness of two approaches, which identify crosscutting concerns in the requirements specification, followed by an assessment of its perceived utility and ease of use. Our results indicate that, in this given context and planned scenario, there are significant differences between the effectiveness of ObasCId and Theme/Doc approaches.

Palavras-chave: Crosscutting Concerns, Controlled Experiment

Referências

Baniassad, E. and Clarke, S. (2004). Finding aspects in requirements with theme/doc.Early Aspects: Aspect-Oriented Requirements Engineering and Architecture Design,pages 15–22

Bourque, P., Fairley, R. E., et al. (2014).Guide to the software engineering body of knowledge (SWEBOK (R)): Version 3.0. IEEE Computer Society Press.

Caldiera, V. R. B.-G. and Rombach, H. D. (1994). Goal question metric paradigm.Encyclopedia of software engineering, 1:528–532.

Cook, T. and Campbell, D. (1979).Quasi-Experimentation: Design and Analysis Issues for Field Settings. Houghton Mifflin

Davis, F. D. (1993). User acceptance of information technology: system characteristics,user perceptions and behavioral impacts. 38(3):475 – 487.

Dijkstra, E. W. (1976).A Discipline of Programming. Prentice Hall.

Graybill, F., Iyer, H., and Burdick, R. (1998).Applied Statistics: A First Course in Inference. Data Warehousing Institute Series from. Prentice Hall.

IEEE (1990). Standard Glossary of Software Engineering Terminology.

Kiczales, G., Lamping, J., Mendhekar, A., Maeda, C., Lopes, C. V., Loingtier, J.-M., and Irwin, J. (1997).Aspect-oriented programming. Springer Berlin Heidelberg.

Meyer, B. (1997).Object-oriented Software Construction. Prentice Hall

Monteiro, S. D. (2017). Sistemas de recuperação da informação e o conceito de relevância nos mecanismos de busca: semântica e significacão

Parnas, D. L. (1972).On the criteria to be used in decomposing systems into modules.Communications of ACM.

Parreira Jr., R. A. D. P. (2018). ObasCId(-Tool): an ontologically based approach for concern identification and classification and its computational support.Journal of the Brazilian Computer Society, 24(1):3.

RESENDE, A. M. (2007).Um método para Identificação e Definição de Aspectos Iniciais. 209f. PhD thesis, Tese de Doutorado-Instituto Tecnológico de Aeronáutica, SãoJosé dos Campos.

Santanna, C. (2008).On the Modularity of Aspect-Oriented Design: a concern-driven measurement approach. PhD thesis, Centre for Telematics and Information Technology, University of Twente, Enschede, The Netherlands.

Wohlin, C., Runeson, P., H ̈ost, M., Ohlsson, M. C., Regnell, B., and Wessl ́en, A. (2012).Experimentation in Software Engineering. Springer, Norwell, MA, USA