Quality-Centric Approach for Software Component Identification from Object-Oriented Code

Monte Carlo simulations and an application on cars data (with outliers) show the robustness of the Gini PCA and provide different interpretations of the results compared with

KEYWORDS: Software product line engineering; feature identification; feature model; source code variation; OO source code reverse engineering; software system variants; Formal

Composite component classes differ from primitive components in that their implementation is not defined by a single class but by an embedded architecture configura- tion, i.e., a

Its uses the concept of neighborhood graphs and compares a set of proximity measures for continuous data which can be more-or-less equivalent a

• Non-functional concerns: the concern of communi- cation corresponds to communication operations with other components, the concern of domain corresponds to the structure (class

When constructing the dependency graph, we have selected only those dependencies whose composing nodes contains at least one class, which means that the

Build- ing on Model Driven Engineering techniques, we then show how the very same QoSCL contracts can be exploited for (1) validation of individual com- ponents, by

Starting from a clean definition of what is a documentary database, we defined what is a subdatabase, the single type of our algebra and their operands which fit to