INES - National Institute of Science and Technology for Software Engineering

RSS feed


Calendar

September 2017
M T W T F S S
« Nov    
 123
45678910
11121314151617
18192021222324
252627282930  

 
  • INES at CBSOFT 2010 Tools Session

    (0)
    Publicado em July 28th, 2010News, Publications

    Three tools developed as related assets from activities of the INES project “Models, Techniques and Tools for Software Evolution” were selected for presentation at the CBSOFT 2010 Tools Session, in Salvador Bahia.

    * Analizo: an Extensible Multi-Language Source Code Analysis and Visualization Toolkit, Antonio Terceiro (UFBA), Joenio Costa (UCSAL), Paulo Meirelles (USP), Joao Miranda (USP), Luiz Romario Santana Rios (UFBA), Lucianna Almeida (USP), Christina Chavez (UFBA), Fabio Kon (USP)

    * Fir-Diagram: Ferramenta Baseada no Modelo FIR para Análise de Impacto de Mudanças em Interesses de Negócio, Antonio Oliveira Filho (UFBA), Fabrıcio de Freitas Cardim (FRB), Tiano Oliveira Dorea (FRB), Christina Chavez (UFBA)

    * An Eclipse-Based Multi-Perspective Environment to Visualize Software Coupling, Glauco Carneiro (UFBA), Paulo Júnior (UFBA), Arleson Nunes Graduação (UFBA), Manoel Mendonça (UFBA)

    , , , , , ,
  • MsC Dissertation - A Traceability Technique for Change Impact Analysis from Business Concerns

    (0)
    Publicado em December 25th, 2009News

    Antonio Oliveira Filho presented his Master dissertation - A Traceability Technique for Change Impact Analysis from Business Concerns (Uma Técnica de Rastreabilidade para Análise de Impacto de Mudanças em Interesses de Negócio), on 07/January/2010, at Unifacs.

    Antonio’s research has been developed at the Mestrado em Sistemas e Computaçāo, UNIFACS, under the supervision of Prof. Christina Chavez (UFBA).  This MsC dissertation is one of the results of the INES research project Models, Techniques and Tools for Software Evolution  (Modelos, Técnicas e Ferramentas para Evolução de Software).

    Abstract:

    Impact analysis is the identification of the potential consequences of a change, or estimating what needs to be modified to accomplish a change, including related costs and schedule estimates.

    In this work, we distinguish between two kinds of concerns related to impact analysis: (1) business-specific concerns, those related to stakeholders interested in checking if other business rules are impacted by the change and also need to be modified; and (2) software-specific concerns, those related to stakeholders interested in the impacted software artifacts that need to be modified. Several traceability techniques have been studied and none of them supported impact analysis that dealt with business-specific concerns with reasonable values of precision and recall for the discovered impacts.

    Our research work aims to support business-specific concerns during impact analysis, by proposing and evaluating a traceability technique that resorts on a new traceability model defined over business rules, with expected precision and recall values of 100%.

    , , , ,