Het platform voor open praktijkgericht onderzoek

product

Software architecture reconstruction and compliance checking

From ACM: "In cases where architectural documentation is outdated or missing, software architecture reconstruction (SAR) techniques may be used to create architectural views of a system. This paper describes a case study in which SAR techniques are applied to reconstruct module views of a case system; a debt settlements suite for local governments, developed in C#. A manual approach and its results are described and compared to the outcome of a layers reconstruction algorithm. Furthermore, this paper explains how software architecture compliance checking (SACC) techniques may help to test the results of reconstruction activities. In this study, SAR and SACC were supported by HUSACCT, a tool that provides rich sets of module and rule types in support of layers, facade, and gateway patterns." https://doi.org/10.1145/3129790.3129809

DOCUMENT

product

Teaching Software Architecture Concepts with HUSACCT

Author supplied: Teaching software architecture (SA) in a bachelor computer science curriculum can be challenging, as the concepts are on a high abstraction level and not easy to grasp for students. Good techniques and tools that help with addressing the challenging SA aspects in a didactically responsible way are needed. In this tool demo we show how we used the software architecture compliance checking tool HUSACCT for addressing various concepts of SA in our courses on software architecture. The students were introduced to architectural reconstruction and architecture compliance checking, which helped them to gain important insights in aspects such as the relation between architectural models and code and the specification of dependency relations between architecture elements as concrete rules.

DOCUMENT

Teaching Software Architecture Concepts with HUSACCT

product

Software architecture reconstruction research support as provided by HUSACCT

From the ACM record: "Software architecture reconstruction techniques may be used to understand and maintain software systems, especially in these cases where architectural documentation is outdated or missing. This paper presents the architecture reconstruction functionality of HUSACCT and describes how this functionality may be used and extended with algorithms in support of reconstruction research focusing on modular architectures. The tool provides a graphical user interface to select an algorithm, edit its parameters and to execute or reverse the algorithm. To study the results, browsers and diagrams are available. Furthermore, a user interface is provided to enhance the determination of the effectiveness of algorithms by means of the MoJoFM metric." https://doi.org/10.1145/3129790.3129819

DOCUMENT

product

Dependency Types and Subtypes in the Context of Architecture Reconstruction and Compliance Checking

Presented at the 2015 European Conference on Software Architecture Workshops. DOI 10.1145/2797433.2797491 http://dl.acm.org/citation.cfm?id=2797491 Software architecture reconstruction and compliance checking rely on supporting tools that analyze the modules in the code and their dependencies. Tools may provide a dependency type for each dependency to provide more detail on the actual usage relation. This study is aimed on the identification of dependency characteristics which can be determined accurately and which might be interesting for architects and researchers in the context of architecture reconstruction and compliance checking. A classification is proposed which distinguishes dependency types, related subtypes, and several other characteristics. To enable reflection on the usefulness of the classified dependency details, a prototype implementation has been developed for the analysis of Java based systems. A frequency analysis of the classified dependency characteristics in three open source systems is presented, as well as an analysis of a set of rule violating dependencies in one of these systems.

DOCUMENT

product

Instruments to Evaluate and Improve IT Architecture Work

Author Supplied: In the last decades, architecture has emerged as a discipline in the domain of Information Technology (IT). A well-accepted definition of architecture is from ISO/IEC 42010: "The fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution." Currently, many levels and types of architecture in the domain of IT have been defined. We have scoped our work to two types of architecture: enterprise architecture and software architecture. IT architecture work is demanding and challenging and includes, inter alia, identifying architectural significant requirements (functional and non-functional), designing and selecting solutions for these requirements, and ensuring that the solutions are implemented according to the architectural design. To reflect on the quality of architecture work, we have taken ISO/IEC 8402 as a starting point. It defines quality as "the totality of characteristics of an entity that bear on its ability to satisfy stated requirements". We consider architecture work to be of high quality, when it is effective; when it answers stated requirements. Although IT Architecture has been introduced in many organizations, the elaboration does not always proceed without problems. In the domain of enterprise architecture, most practices are still in the early stages of maturity with, for example, low scores on the focus areas ‘Development of architecture’ and ‘Monitoring’ (of the implementation activities). In the domain of software architecture, problems of the same kind are observed. For instance, architecture designs are frequently poor and incomplete, while architecture compliance checking is performed in practice on a limited scale only. With our work, we intend to contribute to the advancement of architecture in the domain of IT and the effectiveness of architecture work by means of the development and improvement of supporting instruments and tools. In line with this intention, the main research question of this thesis is: How can the effectiveness of IT architecture work be evaluated and improved?

DOCUMENT

Instruments to Evaluate and Improve IT Architecture Work

product

Navigating Interactive Story Spaces

Over the past decade, journalists have created in-depth interactive narratives to provide an alternative to the relentless 24-hour news cycle. Combining different media forms, such as text, audio, video, and data visualisation with the interactive possibilities of digital media, these narratives involve users in the narrative in new ways. In journalism studies, the convergence of different media forms in this manner has gained significant attention. However, interactivity as part of this form has been left underappreciated. In this study, we scrutinise how navigational structure, expressed as navigational cues, shapes user agency in their individual explorations of the narrative. By approaching interactive narratives as story spaces with unique interactive architectures, in this article, we reconstruct the architecture of five Dutch interactive narratives using the walkthrough method. We find that the extensiveness of the interactive architectures can be described on a continuum between closed and open navigational structures that predetermine and thus shape users’ trajectories in diverse ways.

DOCUMENT

product

Accountability and the Reconstruction of the Past

Many organizations have undergone substantial reorganization in the last decade. They re-engineered their business processes and exchanged proprietary, not integrated applications for more standard solutions. Integration of structured data in relational data bases has improved documentation of business transactions and increased data quality. But almost 90% of the information that organizations manage is unstructured, can not easily be integrated into a traditional database. Just like structured data, unstructured information in organizations are records, meant and used as evidence for organizational actions and transactions. Governments, courts and other stakeholders are making increasing demands for the trustworthiness of records. This is part of a long-term trend toward defining what accountability means in a digital era. An analysis of literature of information science, organization science and archival science illustrates that for accountability, reconstruction of the past is essential. Hypothesis of this paper is that for the reconstruction of the past each organization needs (at least) a combination of three mechanisms: enterprise records management, organizational memory and records auditing. Enterprise records management ensures that records meet the for accountability necessary quality requirements: integrity, authenticity, controllability and historicity. These requirements ensure records that can be trusted. Trusted records enhance the possibility of reconstructing the past. The organizational memory ensures that trusted records are preserved for as long as is necessary to comply to accountability regulations. It provides an information and communication technology infrastructure to (indefinitely) store those records and to keep them accessible. Records auditing audits enterprise records management and organizational memory to assess the possibility to reconstruct past organizational actions and transactions. These mechanisms ensure that organizations have a documented understanding of: the processing of actions and transactions within business processes; the dissemination of trusted records; the way the organization accounts for the actions and transactions within its business processes; and the reconstruction of actions and transactions from business processes over time. This understanding is important for the reconstruction of the past in digitized organizations and improve organizational accountability.

DOCUMENT

Accountability and the Reconstruction of the Past

product

Architecture Compliance Checking of Semantically Rich Modular Architectures

Abstract-Architecture Compliance Checking (ACC) is an approach to verify the conformance of implemented program code to high-level models of architectural design. ACC is used to prevent architectural erosion during the development and evolution of a software system. Static ACC, based on static software analysis techniques, focuses on the modular architecture and especially on rules constraining the modular elements. A semantically rich modular architecture (SRMA) is expressive and may contain modules with different semantics, like layers and subsystems, constrained by rules of different types. To check the conformance to an SRMA, ACC-tools should support the module and rule types used by the architect. This paper presents requirements regarding SRMA support and an inventory of common module and rule types, on which basis eight commercial and non-commercial tools were tested. The test results show large differences between the tools, but all could improve their support of SRMA, what might contribute to the adoption of ACC in practice.

DOCUMENT

Architecture Compliance Checking of Semantically Rich Modular Architectures

product

Rule Type Based Reasoning On Architecture Violations: A Case Study

Author supplied: "Abstract—Software architecture compliance checking (SACC) is an approach to monitor the consistency between the intended and the implemented architecture. In case of static SACC, the focus is mainly on the detection of dependencies that violate architectural relation rules. Interpretation of reported violations may be cumbersome, since the violations need to be connected to architectural resolutions and targeted qualities such as maintainability and portability. This paper describes an SACC case study which shows that inclusion of different types of rules in the SACC process enhances reasoning on architecture violations, especially if a rule type is related to specific architectural pattern. The SACC is performed with HUSACCT, an SACC-tool that provides rich sets of module and rule types in support of patterns such as layers, facade, and gateway. The case system is a governmental system developed in C#, which follows the .NET common application architecture. Even though the system appeared to be well-structured, the SACC revealed that 10 of the 17 architectural rules were violated."

DOCUMENT

Zoekresultaten

Producten 236

Software architecture reconstruction and compliance checking

Teaching Software Architecture Concepts with HUSACCT

Software architecture reconstruction research support as provided by HUSACCT

Dependency Types and Subtypes in the Context of Architecture Reconstruction and Compliance Checking

Instruments to Evaluate and Improve IT Architecture Work

Navigating Interactive Story Spaces

Accountability and the Reconstruction of the Past

Architecture Compliance Checking of Semantically Rich Modular Architectures

Rule Type Based Reasoning On Architecture Violations: A Case Study

Navigeer naar

Categorieën

Filters

Producten 236

Software architecture reconstruction and compliance checking

Teaching Software Architecture Concepts with HUSACCT

Software architecture reconstruction research support as provided by HUSACCT

Dependency Types and Subtypes in the Context of Architecture Reconstruction and Compliance Checking

Instruments to Evaluate and Improve IT Architecture Work

Navigating Interactive Story Spaces

Accountability and the Reconstruction of the Past

Architecture Compliance Checking of Semantically Rich Modular Architectures

Rule Type Based Reasoning On Architecture Violations: A Case Study