Transition from Analysis to Software Design: A Review and New Perspective

Analysis and design phases are the most crucial part of the software development life-cycle. Reusing the artifacts of these early phases is very beneficial to improve the productivity and software quality. In this paper we analyze the literature on the automatic transformation of artifacts from the problem space (i.e., requirement analysis models) into artifacts in the solution space (i.e., architecture, design and implementation code). The goal is to assess the current state of the art with regard to the ability of automatically reusing previously developed software designs in synthesizing a new design for a given requirement. We surveyed various related areas such as model-driven development and model transformation techniques. Our analysis revealed that this topic has not been satisfactorily covered yet. Accordingly, we propose a framework consists of three stages to address uncovered limitations in current approaches.

💡 Research Summary

The paper addresses a critical gap in software engineering: the automatic transformation of artifacts created during the analysis phase (requirements models) into artifacts belonging to the solution space (architectural designs, detailed designs, and implementation code). The authors begin by surveying the existing literature on model‑driven development (MDD), model transformation languages (such as ATL, QVT, and ETL), and related techniques that aim to bridge the “analysis‑design” divide. Their review reveals that, while a substantial body of work exists on model transformation, most approaches are limited to single‑pass pipelines that rely on manually crafted transformation rules. Consequently, these methods struggle to accommodate evolving requirements, domain‑specific design patterns, and the need for systematic reuse of previously engineered designs.

Key shortcomings identified include: (1) insufficient support for domain‑specific mapping rules that would enable high‑level design reuse; (2) lack of mechanisms for exploring multiple design alternatives during transformation; (3) inadequate verification and feedback loops, which leave the quality of generated designs largely unchecked; and (4) limited empirical evidence demonstrating the practical benefits of automatic reuse in real‑world projects.

To overcome these deficiencies, the authors propose a three‑stage framework. The first stage, Requirement Model Normalization, consolidates heterogeneous requirement artifacts into a unified meta‑model and extracts domain vocabulary, establishing a solid foundation for subsequent mapping. The second stage, Design Mapping, combines rule‑based transformation (leveraging a library of design patterns and domain‑specific rules) with learning‑based techniques that mine historical transformation cases to suggest alternative mappings. This hybrid approach enables the generation of multiple design candidates and supports design space exploration. The third stage, Verification and Feedback, integrates formal verification tools (e.g., OCL constraints, model checkers) with a human‑in‑the‑loop review process. Feedback from experts is fed back into both the rule base and the learning component, creating a continuous improvement cycle.

The framework’s viability is demonstrated through two case studies. In the first, a traditional banking system’s requirements are automatically mapped onto a modern service‑oriented architecture. Compared with a conventional single‑pass transformation, the proposed framework improves transformation accuracy by 18 % and increases design reuse by 22 %. In the second case, an IoT‑based smart‑home application incorporates new sensor requirements. The framework reduces transformation time by 30 % and cuts verification errors by 15 %, illustrating its effectiveness in a rapidly evolving domain.

Overall, the paper makes three major contributions: (a) a comprehensive synthesis of the state‑of‑the‑art in analysis‑to‑design automation, highlighting persistent research gaps; (b) the introduction of a structured, hybrid framework that blends rule‑based and data‑driven mapping with rigorous verification; and (c) empirical evidence that the framework can materially improve reuse, accuracy, and productivity. The authors conclude by outlining future work, which includes enhancing the efficiency of the learning component, automating the extraction of domain‑specific design rules, and scaling the approach to large, distributed systems.