ObasCId(-Tool): an ontologically based approach for concern identification and classification and its computational support

The aspect-oriented requirements engineering (AORE) area intends to provide more appropriated strategies for software concern identification, classification (as crosscutting or non-crosscutting), and modularization, in the early phases of software development cycle. A commonly reported issue about the existing AORE approaches is the lack of appropriated resources (guidelines, processes, catalogs, among others) to support software engineers during the concern identification and classification. This work aims to mitigate this issue by proposing (i) a reference ontology for the software concern domain, called O4C (Ontology for Concerns); (ii) an ontologically based approach for AORE, called ObasCId, that suggests the usage of catalogs of software concerns and a well-defined process for supporting software engineers to perform these activities in a more systematic way; and (iii) a computational support, called ObasCId-Tool, that automates some activities of the ObasCId. Two quasi-experimental studies were performed on ObasCId and ObasCId-Tool, and their results indicated that these technologies may positively contribute for the concern identification and classification effectiveness without harming its execution time.

[1]  Ricardo de Almeida Falbo,et al.  SABiO: Systematic Approach for Building Ontologies , 2014, ONTO.COM/ODISE@FOIS.

[2]  João Araújo,et al.  Scenario modelling with aspects , 2004, IEE Proc. Softw..

[3]  Siobhán Clarke,et al.  Aspect-oriented analysis and design - the theme approach , 2005, Addison Wesley object technology series.

[4]  Paulo Afonso Parreira Júnior.  ObasCId: uma abordagem ontologicamente fundamentada para EROA , 2015 .

[5]  J. Wloka,et al.  On the Contributions of an End-to-End AOSD Testbed , 2007, Early Aspects at ICSE: Workshops in Aspect-Oriented Requirements Engineering and Architecture Design (EARLYASPECTS'07).

[6]  Rosângela Dellosso Penteado,et al.  ObasCId: An Ontologically-Based Approach for Concern Identification and Classification , 2016, SBCARS.

[7]  Ana Moreira,et al.  An XML-Based Language for Specification and Composition of Aspectual Concerns , 2006, ICEIS.

[8]  Hinrich Schütze,et al.  Introduction to information retrieval , 2008 .

[9]  João Araújo,et al.  A Metadata-Driven Approach for Aspect-Oriented Requirements Analysis , 2008, ICEIS.

[10]  Rosângela Dellosso Penteado,et al.  CrossCutting Concerns Identification Supported by Ontologies: A Preliminary Study , 2015, ICEIS.

[11]  Rosângela Dellosso Penteado,et al.  An Overview on Aspect-Oriented Requirements Engineering Area , 2014, ICEIS.

[12]  Ruzanna Chitchyan,et al.  A tool suite for aspect-oriented requirements engineering , 2006, EA '06.

[13]  Shulin Liu,et al.  Use Case and Non-functional Scenario Template-Based Approach to Identify Aspects , 2010, 2010 Second International Conference on Computer Engineering and Applications.

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

[15]  Barry W. Boehm,et al.  Identifying Quality-Requirement Conflicts , 1996, IEEE Softw..

[16]  Rosângela Dellosso Penteado,et al.  Aspect-Oriented Requirements Engineering - A Systematic Mapping , 2014, ICEIS.

[17]  A. Moreira,et al.  1 TOWARDS A COMPOSITION PROCESS FOR ASPECT-ORIENTED REQUIREMENTS , 2003 .

[18]  João Araújo,et al.  Multi-dimensional separation of concerns in requirements engineering , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[19]  Alessandro F. Garcia,et al.  A Comparative Study of Aspect-Oriented Requirements Engineering Approaches , 2007, First International Symposium on Empirical Software Engineering and Measurement (ESEM 2007).

[20]  Rosângela Dellosso Penteado,et al.  OnTheme/Doc - An Ontology-based Approach for Crosscutting Concern Identification from Software Requirements , 2015, ICEIS.

[21]  Siobhán Clarke,et al.  Theme: an approach for aspect-oriented analysis and design , 2004, Proceedings. 26th International Conference on Software Engineering.

[22]  Yuri Chernak.  Requirements Composition Table explained , 2012, 2012 20th IEEE International Requirements Engineering Conference (RE).

[23]  Fred D. Davis.  User Acceptance of Information Technology: System Characteristics, User Perceptions and Behavioral Impacts , 1993, Int. J. Man Mach. Stud..

[24]  Jon Whittle,et al.  Scenario Modeling with Aspects. , 2004 .

[25]  Cláudio Sant'Anna,et al.  On the Impact of Aspectual Decompositions on Design Stability: An Empirical Study , 2007, ECOOP.

[26]  F. S. Germano,et al.  A Pattern Language for Business Resource Management , 1999 .

[27]  Elis Montoro Hernandes.  Insight: uma abordagem guiada pela informação para análise qualitativa com suporte de visualização e mineração de texto , 2014 .

[28]  John Mylopoulos,et al.  Non-Functional Requirements in Software Engineering , 2000, International Series in Software Engineering.

[29]  C. Lopez,et al.  NDR Ontology: Sharing and Reusing NFR and Design Rationale Knowledge , 2008, 2008 First International Workshop on Managing Requirements Knowledge.

[30]  João Araújo,et al.  Modularisation and composition of aspectual requirements , 2003, AOSD '03.

[31]  Giancarlo Guizzardi,et al.  Ontological foundations for structural conceptual models , 2005 .