Semi-automatic architectural pattern identification and documentation using architectural primitives

Haitzer, Thomas; Zdun, Uwe

doi:10.1016/j.jss.2014.12.042

Cited by 9 publications

(10 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Considering this premise, some papers in the SLR present technology implementations or report lessons learned, but without any validity study. On the other hand, eight research works [18, 22, 25, 29–31, 47 ] are considered to have a high level of rigor and relevance, because these papers are applied to large‐sized applications.…”

Section: Methodsmentioning

confidence: 99%

“…Haitzer and Zdun [30 ] applied static analysis to identify candidate patterns and their variants by the compliance of pattern templates and pattern catalogues. The results are processed and visualised with UML diagrams and domain‐specific models.…”

Section: Reconstruction and Reverse Engineering Of Software Architementioning

confidence: 99%

“…The input for architecture reconstruction in these works is the source code, where external libraries can be removed. On the other hand, the authors in [23, 30, 31, 48 ] aim to propose architectural clues to identify and analyse architectural patterns and styles, and to suggest correct design patterns in OO systems or systems written in Java. Source code or classes represented through UML diagrams are used as input, which produces a high‐level system, candidate patterns, or the correct implementation of design patterns as output.…”

Section: Reconstruction and Reverse Engineering Of Software Architementioning

confidence: 99%

“…Traceability must be preserved to guarantee the viability of the process (F.11). Studies such as [14, 30, 39, 40 ] store and analyse the traceability links between requirements or features and architecture or code. The rating is used to prioritise dependencies, patterns, or code smells to be solved or applied in architecture.…”

Section: Key Findingsmentioning

confidence: 99%

See 3 more Smart Citations

Towards a reference process for software architecture reconstruction

et al. 2020

View full text Add to dashboard Cite

Nowadays, software systems remain useful and competitive; entail the inevitable need to change over time and to be adapted to new technologies, platforms, and architectures. These quick changes imply following systematic, automated, or standardised processes that provide recommendations and guidelines to architects during software architecture reconstruction. Considerable research work on architecture reconstruction has been conducted. However, it needs to be studied thoroughly to determine what are the common activities and elements to reconstruct software architectures, and to define a reference process for systematically guiding the evolution of software architectures. This work addresses the need for defining a process for software architecture reconstruction called software improvement in the reconstruction of architectures (SIRA). This process has been rigorously designed from the results of a systematic literature review and a small survey of related work. As a result, SIRA integrates and extends previous research and can be conceived as a reference process to reconstruct software architectures in a semi‐automated way. In addition, this work also determines the common elements of the architecture reconstruction process: (i) techniques and activities; (ii) architectural elements, patterns, and attributes; (iii) mechanisms and strategies; and (iv) the automation and recommendation tasks of the process.

show abstract

Section: Methodsmentioning

confidence: 99%

Section: Reconstruction and Reverse Engineering Of Software Architementioning

confidence: 99%

Section: Reconstruction and Reverse Engineering Of Software Architementioning

confidence: 99%

Section: Key Findingsmentioning

confidence: 99%

See 2 more Smart Citations

Towards a reference process for software architecture reconstruction

et al. 2020

View full text Add to dashboard Cite

show abstract

“…Mavridou Anastasia pointed out that architecture can be represented by logic, and architectural style can be described by configurations [8] . Thomas Haitzer proposed a semiautomated architectural pattern identification method based on architecture primitives [9] . The Service-oriented Architecture pattern identification method based on model checking was proposed by Penta and Sandonep in 2007 [10] .…”

Section: Introductionmentioning

confidence: 99%

Identify MVC architectural pattern based on ontology

Yin¹,

Wang

2019

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

MVC architectural pattern is widely used in software architecture design. It helps decouple the processing and the visualization of system data. Identified MVC architectural pattern helps understand how the software is actually implemented based on MVC architectural pattern, and further improve the consistency between design and source code. This paper proposes an ontology-based MVC architectural pattern identification method. Firstly, we use the combination of design patterns to describe the structure of MVC architectural pattern, so as to construct the MVC ontology of concept layer. Then we construct a program dependency graph by extracting the dependencies between entities in the target system, and build the ontology of instance layer. Finally, the MVC architectural pattern ontology of the specific target system is inferred by ontology reasoner in order to obtained MVC architectural pattern and the pattern elements included in each component. We use open source projects as the benchmark, and the experimental results show that our method effectively identify the MVC architectural pattern and the pattern elements in software system.

show abstract