Abstract

Software systems have become more complex, with myriad features and multiple functionalities. A major challenge in developing and maintaining such complex software is to identify potential conflicts among its features. Feature interaction analysis becomes progressively more difficult as software's feature combinations and available scenarios increase. Software maintainers need to identify and analyze conflicts that can arise from feature modification requests. Our approach combines Use Case Maps with Formal Concept Analysis to assist maintainers in identifying feature modification impacts at the requirements level, without the need to examine the source code. We demonstrate the applicability of this approach using a teleommunication case study.

-- DanielAmyot - 01 Apr 2008

Discussion

FormForVirtualLibrary edit

Title Feature Interaction Analysis: A Maintenance Perspective
Authors M. Shiri, J. Hassine, and J. Rilling
Type Conference
Conference/Journal Title 22nd IEEE/ACM International Conference on Automated Software Engineering (ASE), Atlanta, USA
Volume/Number
Editors R.E.K. Stirewalt, A. Egyed, and B. Fischer
Publisher ACM
Month November
Year 2007
Pages 437-440
DOI 10.1145/1321631.1321703
Keywords Change Impact Analysis, Feature Interaction, Formal Concept Analysis, Software Evolution, Use Case Maps
Topic attachments
I Attachment Action Size Date Who Comment
ASE07.pdfpdf ASE07.pdf manage 336 K 01 Apr 2008 - 13:47 DanielAmyot Prepublication version
Topic revision: r2 - 05 Nov 2009, AzaliaShamsaei
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback