Vol 9 No.1
ABSTRACT It is quite frequent to copy and paste code fragments in software development. The copied source code is called a software clone and the activity is referred to as code cloning. The presence of code clones hamper maintenance and may lead to bug propagation. Now-a-days, model driven development has become a standard industry practice. Duplicate parts in models i.e. model clones pose similar challenges as in source code. This paper presents an approach to detect clones in Unified Modeling Language class models. The core of our technique is the construction of a labeled, ranked tree corresponding to the UML class model where attributes with their data types and methods with their signatures are represented as subtrees. By grouping and clustering of repeating subtrees, the tool is able to detect duplications in a UML class model at different levels of granularity i.e. complete class diagram, attributes with their data types and methods with their signatures across the model and cluster of such attributes/methods. We propose a new classification of model clones with the objective of detecting exact and meaningful clones. Empirical evaluation of the tool using open source reverse engineered and forward designed models show some interesting and relevant clones which provide useful insights into software modeling practice.
ABSTRACT Lehman’s law of continuing change implies that software must continually evolve to accommodate frequently changing requirements in existing systems. Also, maintainability as an attribute of system quality requires that changes are to be systematically implemented in existing software throughout its lifecycle. To support a continuous software evolution, the primary challenges include (i) enhancing reuse of recurring changes; and (ii) decreasing the efforts for change implementation. We propose change patterns and demonstrate their applicability as reusable solutions to recurring problems of architectural change implementation. Tool support can empower the role of a designer/architect by facilitating them to avoid labourious tasks and executing complex and large number of changes in an automated way. Recently, change patterns as well as tool support have been exploited for architecture evolution, however; there is no research to unify pattern-driven (reusable) and toolsupported (automated) evolution that is the contribution of this paper. By exploiting patterns with tool support we demonstrate the evolution of a peerto-peer system towards client-server architecture. Evaluation results suggest that: (i) patterns promote reuse but lack fine-granular change implementation, and (ii) tool supports automation but user intervention is required to customize architecture change management.
ABSTRACT A formal Architecture Description Language (ADL) provides an effective way to dependency analysis at early stage of development. Π-ADL is an ADL that represents the static and dynamic features of software services. In this paper, we describe an approach of dependency analysis of SOA (Service Oriented Architecture) based system, at architecture level, through Π-ADL. A set of algorithms are also proposed for identification of dependency relationships from a SOA based system. The proposed algorithms would be useful to all stakeholders of SOA based system directly or indirectly. Finally, we automate our approach with a tool developed by us and named ‘DA-SOA’ (Dependency Analyzer for SOA Based Systems).
ABSTRACT The synergy between the disciplined (i.e. plan-driven) and agile (i.e. adaptive) approaches can achieve results that exceed any one of them separately in software development. In this paper, we focus on how introducing the disciplined agility approach called “SEI-Team Software Process” in MiniMax Software helped the company deals with the transitions between different stages in the internal learning and development change. Major stages, their discovered challenges, the needed methodological shifts and achieved breakthrough improvements in each stage will be explained. This development cycle can be summarized into three major stages. Summary of achievements per stage will be presented as well as a cross-stages analysis to illustrate the impact of these transitions and changes.