Supporting commonality and variability analysis of requirements and structural models

Authors:
Kentaro Kumaki;Ryosuke Tsuchiya;Hironori Washizaki;Yoshiaki Fukazawa
Affiliations:
Waseda University, Tokyo, Japan;Waseda University, Tokyo, Japan;Waseda University, Tokyo, Japan;Waseda University, Tokyo, Japan
Venue:
Proceedings of the 16th International Software Product Line Conference - Volume 2
Year:
2012

Citing 7
Cited 1

A graph distance metric based on the maximal common subgraph

Pattern Recognition Letters
Introduction to Modern Information Retrieval

Introduction to Modern Information Retrieval
Recovering Traceability Links between Code and Documentation

IEEE Transactions on Software Engineering
Assessing merge potential of existing engine control systems into a product line

Proceedings of the 2006 international workshop on Software engineering for automotive systems
A framework for constructing semantically composable feature models from natural language requirements

Proceedings of the 13th International Software Product Line Conference
Reverse engineering feature models

Proceedings of the 33rd International Conference on Software Engineering
Eliminating the adoption barrier

IEEE Software

Recovering traceability links between requirements and source code in the same series of software products

Proceedings of the 17th International Software Product Line Conference

Quantified Score

Hi-index	0.00

Visualization

Abstract

The commonality and variability analysis of legacy software assets requires high costs in terms of personnel and time in extractive core asset development. We propose a technique for supporting the commonality and variability analysis, targeting the requirements and structural models of legacy software assets for the development of a feature diagram and a product line architecture (PLA). We analyze the commonality and variability of the sentences as requirements and classes as structural models by calculating similarities based on a vector space model. By using our technique, the costs in terms of personnel and time required for the analysis of legacy software assets can be reduced.