Towards a framework for managing architectural design decisions

Bhat, M. Seetharama; Shumaiev, Klym; Matthes, Florian

doi:10.1145/3129790.3129799

Cited by 11 publications

(4 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…In addition, not only a design decision itself but also the rationale behind the decision should be documented [6], [7], [16]. The rationale comprises the justification and process that has led to a design decision [17], [18]. This rationale is required to determine why a decision has been made, even after a long period of time or if the decision-maker has left the project [19].…”

Section: Whatmentioning

confidence: 99%

The documentation of design decisions in engineering projects: A study in infrastructure development

Kinneging¹,

Siebelink

Graaf

et al. 2021

IJISPM

View full text Add to dashboard Cite

In most design projects, the documentation of design decisions is considered important. Among others, documentation of design decisions contributes to the traceability of decisions that shape a project’s development process, helps deal with changes in the project and prevents the recurrence of old discussions. Yet, little attention is given to documenting design decisions in the engineering literature. In this study, a theoretical framework for the key elements of this documentation process was developed. Four infrastructure projects were studied and compared to this framework by means of pattern matching. This method compares theoretical and empirical patterns and determines whether they match or do not match. The findings demonstrate that accessibility of documentation for all involved project parties and the division of documentation tasks are in accordance with the literature. However, the documentation of design decisions and their rationale is not done as completely as is recommended in theory. Literature states that the documentation of interrelations and context of decisions should be described thoroughly, but that is barely done in practice. In addition, the findings show that neither immediate documentation nor periodical monitoring of documentation is applied. Based on these findings, this research proposes a strategy for improving the documentation of design decisions.

show abstract

Section: Whatmentioning

confidence: 99%

The documentation of design decisions in engineering projects: A study in infrastructure development

Kinneging¹,

Siebelink

Graaf

et al. 2021

IJISPM

View full text Add to dashboard Cite

show abstract

“…The authors in [1] investigate tools for architects to make architectural design decisions in large software projects. The solutions include reuse of past architectural decisions, alternate choices, the rationale behind a choice, and ask experts about decisions.…”

Section: Related Workmentioning

confidence: 99%

“…We use LQN to not only model the details of communications between the components in the software system but also to model replaying of the events to build the state. The three main aspects of modeling the system execution model for ES systems are: (1) the grouping of features into aggregates, where the features use same data in an aggregate, and features need to communicate for data access between the aggregates, (2) event store simulation with new stream of events for every new instance of an aggregate is created, and (3) Event replay. The first aspect can be modeled by placing features in aggregates as single or separate stations in the LQN model so that features share a single queue or have separate queues for requests.…”

Section: Introductionmentioning

confidence: 99%

Aggregate Architecture Simulation in Event-Sourcing Applications using Layered Queuing Networks

Maddodi

Jansen

Overeem³

2020

Proceedings of the ACM/SPEC International Conference on Performance Engineering

View full text Add to dashboard Cite

Workload intensity in terms of arrival rate and think-time can be used accurately simulate system performance in traditional systems. Most systems treat individual requests on a standalone basis and resource demands typically do not vary too significantly, which in most cases can be addressed as a parametric dependency. New frameworks such as Command Query Responsibility Segregation and Event Sourcing change the paradigm, where request processing is both parametric dependent and dynamic, as the history of changes that have occurred are replayed to construct the current state of the system. This makes every request unique and difficult to simulate. While traditional systems are studied extensively in the scientific community, the latter is still new and mainly used by practitioners. In this work, we study one such industrial application using Command Query Responsibility Segregation and Event Sourcing frameworks. We propose new workload patterns suited to define the dynamic behavior of these systems, define various architectural patterns possible in such systems based on domaindriven design principles, and create analytical performance models to make predictions. We verify the models by making measurements on an actual application running similar workloads and compare the predictions. Furthermore, we discuss the suitability of the architectural patterns to different usage scenarios and propose changes to architecture in each case to improve performance. CCS CONCEPTS• Software and its engineering → Software performance.

show abstract

“…По сути работа представляет собой руководство по документированию для предотвращения потери знаний. В работе[32] предложена программная среда для управления проектными решениями по архитектуре крупных программных проектов. Эта среда предназначена для решения конкретных задач -извлечения и классификации проектных решений, аннотирования архитектурных элементов, выработки рекомендаций по альтернативным вариантам решений и назначения экспертов для принятия проектных решений.…”

unclassified

Ontology for Architectural Knowledge Condensation in a Co-Localized Agile Environment

Luis Robles,

Borrego,

Palacio

et al. 2023

Proceedings of ISP RAS

View full text Add to dashboard Cite

Agile software development companies considered small entities (VSE) face a new reality of remote development. Remote communication has generated many videos derived from video calls recorded for later reference. The video calls recorded contains architectural knowledge from virtual meetings and is essential for companies facing the knowledge vaporization problem. However, only some proposals in the literature can potentially manage AK in videos. This article proposes a solution to recover this architectural knowledge contained in videos using an ontology as a classification scheme, following the architectural knowledge condensation concept. We validated our proposal to manage architectural knowledge following the Methontology guidelines. Implementing an ontology as a classification scheme represents a step forward to achieving the condensation of architectural knowledge in an agile development environment for VSE.

show abstract

Towards a framework for managing architectural design decisions

Cited by 11 publications

References 20 publications

The documentation of design decisions in engineering projects: A study in infrastructure development

The documentation of design decisions in engineering projects: A study in infrastructure development

Aggregate Architecture Simulation in Event-Sourcing Applications using Layered Queuing Networks

Ontology for Architectural Knowledge Condensation in a Co-Localized Agile Environment

Contact Info

Product

Resources

About