Recovery of a reference architecture

Eixelsberger, Wolfgang

doi:10.1145/288408.288417

Cited by 4 publications

(4 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Research on the methodology for creating a reference architecture is progressing. Eixelsberger's case study on recovering a reference architecture from an existing system uses an architecture structure description language (ASDL) and ADL to find commonalities of a system family [30]. This case study acknowledges that a reference model drives the creation of reference architectures and compares the ADL of instantiated systems to create a reference architecture in ASDL for the purpose of creating new systems.…”

Section: Methods Of Building Reference Architecturesmentioning

confidence: 99%

Development and Specification of a Reference Architecture for Agent-Based Systems

Regli

Mayk

Cannon

et al. 2014

IEEE Trans. Syst. Man Cybern, Syst.

View full text Add to dashboard Cite

The recent growth of agent-based software systems was achieved without the development of a reference architecture. From a software engineering standpoint, a reference architecture is necessary to compare, evaluate, and integrate past, current, and future agent-based software systems. The agent systems reference architecture (ASRA) advances the agent-based system development process by providing a set of key interaction patterns for functional areas that exist between the layers and protocols of agent-based systems. Furthermore, the ASRA identifies the points for interoperability between agent-based systems and increases the level of discussion when referring to agent-based systems. This paper presents methodology, grounded in software forensics, to develop the ASRA and provides an overview of the resulting architectural representation. The methodology uses an approach based on software engineering techniques adapted to study agent frameworks-the libraries and tools for building agent systems. The resulting ASRA can serve as an abstract representation of the components necessary for facilitating comparison, integration, and interoperation of software systems composed of agents.

show abstract

Section: Methods Of Building Reference Architecturesmentioning

confidence: 99%

Development and Specification of a Reference Architecture for Agent-Based Systems

Regli

Mayk

Cannon

et al. 2014

IEEE Trans. Syst. Man Cybern, Syst.

View full text Add to dashboard Cite

show abstract

“…This manual analysis draws from domain knowledge, design documents, source code and source code comments; together, these form architecturally significant concepts. The overhead of this manual analysis can be significantly reduced if a reference architecture is readily available for the domain of interest [26,13,9].…”

Section: The Combined Approachmentioning

confidence: 99%

An Iterative Framework for Software Architecture Recovery: An Experience Report

Roy

Graham

2008

Software Architecture

View full text Add to dashboard Cite

Abstract. Both architecture recovery and architecture evaluation play an important role in the area of software reverse-engineering. In this paper, we propose and evaluate a framework for incremental and iterative application of automated architecture recovery (using SWAG Kit) and architecture analysis (using SAAM.) We conclude that SWAG Kit helps in generating a low-level architecture that forms the basis of analysis, while SAAM helps in deriving from this a deeply understood conceptual architecture. The process is iterative, where SAAM analysis helps refine the parameters fed to SWAG Kit, in turn leading to a superior architecture for further analysis. We have applied this process to the extraction of the architectures of three open source compression tools, and we report on the strengths and weaknesses of the approach that this case study exposed. Over all, we conclude that the framework allowed us to understand the software architectures more deeply than would have been possible with the software architecture recovery process alone.

show abstract

“…Such structure is extracted using corresponding commonality analysis [7] and functionality-to-component mapping, and an architectural style that is valid for the product domain. More specifically, extraction of this structure includes the following steps.…”

Section: Adas: Reference Architecture For the Domainmentioning

confidence: 99%

“…Commonality Analysis: Using previously extracted architectural style and Eixelsberger's commonality analysis [7], the corresponding component-level details of the reference architecture can be extracted. This process emphasizes representation of the core functionality found in the related ADM through as-minimal-as-possible set of components and as-simple-as-possible structure.…”

Section: Adas: Reference Architecture For the Domainmentioning

confidence: 99%

Enhancing domain-specific software architecture recovery

Ivkovic

Godfrey

MHS2003. Proceedings of 2003 International Symposium on Micromechatronics and Human Science (IEEE Cat. No.03TH8717)

View full text Add to dashboard Cite

Performing software architecture analysis and recovery on a large software system is expensive and time consuming; when it is done at all, it is often performed within a narrow context, focused on a few areas of particular concern. However, for a long-lived system within a well understood application domain, the costs for performing detailed architecture recovery may be amortized over several generations of the system; the resulting models can also be broadened and put into context by incorporating information about the history and anticipated future evolution of both the application and its underlying domain. This paper proposes a systematic approach for organizing application domain knowledge into a unified structure called the Architectural Domain Assets Set (ADAS). The ADAS structure builds on previous research, as well as our experience in performing an architecture recovery of IBM's DB2. Our initial experiences in using ADAS suggest that it brings needed focus to the recovery process and provides assistance to domain-specific architecture recovery.

show abstract

Recovery of a reference architecture

Cited by 4 publications

References 7 publications

Development and Specification of a Reference Architecture for Agent-Based Systems

Development and Specification of a Reference Architecture for Agent-Based Systems

An Iterative Framework for Software Architecture Recovery: An Experience Report

Enhancing domain-specific software architecture recovery

Contact Info

Product

Resources

About