Sotograph – A Pragmatic Approach to Source Code Architecture Conformance Checking

Bischofberger, Walter R.; Kühl, Jan; Löffler, S.

doi:10.1007/978-3-540-24769-2_1

Cited by 26 publications

(14 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…They recommended RM for organizations interested in systematically incorporating architecture conformance checking into their software development process, due to a well-defined architecture conformance process, centred on holistic high-level models as defined by architects. Indeed, several commercial tools have now been developed that incorporate similar functionality [45][46] and it is this type of approach that is the focus of this research. As such the next section will describe RM in greater detail.…”

Section: Conformance By Extractionmentioning

confidence: 99%

Real-Time Reflexion Modelling in architecture reconciliation: A multi case study

Buckley

Alí

English

et al. 2015

Information and Software Technology

View full text Add to dashboard Cite

ContextReflexion Modelling is considered one of the more successful approaches to architecture reconciliation. Empirical studies strongly suggest that professional developers involved in real-life industrial projects find the information provided by variants of this approach useful and insightful, but the degree to which it resolves architecture conformance issues is still unclear. ObjectiveThis paper aims to assess the level of architecture conformance achieved by professional architects using Reflexion Modelling, and to determine how the approach could be extended to improve its suitability for this task. MethodAn in-vivo, multi-case-study protocol was adopted across five software systems, from four different financial services organizations. Think-aloud, video-tape and interview data from professional architects involved in Reflexion Modelling sessions were analysed qualitatively. ResultsThis study showed that (at least) four months after the Reflexion Modelling sessions less than 50% of the architectural violations identified were removed. The majority of participants who did remove violations favoured changes to the architectural model rather than to the code. Participants seemed to work off two specific architectural templates, and interactively explored their architectural model to focus in on the causes of violations, and to assess the ramifications of potential code changes. They expressed a desire for dependency analysis beyond static-source-code analysis and scalable visualizations. ConclusionThe findings support several interesting usage-in-practice traits, previously hinted at in the literature. These include 1) the iterative analysis of systems through Reflexion models, as a precursor to possible code change or as a focusing mechanism to identify the location of architecture conformance issues, 2) the extension of the approach with respect to dependency analysis of software systems and architectural modelling templates, 3) improved visualization support and 4) the insight that identification of architectural violations in itself does not lead to their removal in the majority of instances.

show abstract

Section: Conformance By Extractionmentioning

confidence: 99%

Real-Time Reflexion Modelling in architecture reconciliation: A multi case study

Buckley

Alí

English

et al. 2015

Information and Software Technology

View full text Add to dashboard Cite

show abstract

“…Rational Software Architect [37] and Enterprise Architect [64] are two commercial tools that provide different functionalities useful for program comprehension, such as the reconstruction of static and dynamic UML diagrams; JDepend is used for the generation of design quality metrics, which allow to automatically measure the quality of a design in terms of its extensibility, reusability, and maintainability, but it does not provide any view that helps in understanding the architecture of the analyzed systems; ARMIN [42] is a tool for architectural reconstruction and mining which provides different representations that are useful as a starting point for reengineering a system to a new, desired architecture. Other commercial tools are Sotograph [12], which can test the conformance to a certain target architecture, and Lattix [58], which organizes architectural information using the Dependency Structure Matrix form.…”

Section: Software Architecture Reconstructionmentioning

confidence: 99%

A tool for design pattern detection and software architecture reconstruction

Fontana

Zanoni

2011

Information Sciences

View full text Add to dashboard Cite

“…Together the concepts described above supports describing and analyzing architectures at the abstraction-level provided by concepts of object-oriented programming languages. Architecture management tools like Lattix [15], Sotograph/Sotoarc [16], and SonarJ [17] work at this abstraction level. The application of the LISA toolkit at this abstraction level is described in [18].…”

Section: Basic Structure Layermentioning

confidence: 99%

Tool Support for Component-Based Software Architectures

Buchgeher

Weinreich

2009

2009 16th Asia-Pacific Software Engineering Conference

View full text Add to dashboard Cite

Principles of component-based software construction like decomposition, decoupling, late binding and late composition are mainstream concepts found in many software systems, technologies and domains. The definition of individual components and component properties is well supported on the level of programming languages. However, tool support for component-based software architectures is insufficient. In particular, component-level abstractions are not integrated well enough with lower-level architectural elements, architectural views are not editable or missing, and validation of componentbased system configurations is not provided. In addition, existing approaches only support a specific component technology and lack support for heterogeneous systems. We present a toolkit supporting the design, analysis and implementation of component-based software systems independent of concrete component models and technologies. The foundation of the toolkit is an architecture description metamodel that unifies concepts of existing component models and that scales from component-based applications to distributed service-oriented architectures. In this paper we focus on the concepts provided for modeling and visualizing different structural relationship of component-based system architectures.

show abstract

Sotograph – A Pragmatic Approach to Source Code Architecture Conformance Checking

Cited by 26 publications

References 2 publications

Real-Time Reflexion Modelling in architecture reconciliation: A multi case study

Real-Time Reflexion Modelling in architecture reconciliation: A multi case study

A tool for design pattern detection and software architecture reconstruction

Tool Support for Component-Based Software Architectures

Contact Info

Product

Resources

About