Improving the Consistency and Usefulness of Architecture Descriptions: Guidelines for Architects

Wohlrab, Rebekka; Eliasson, Ulf; Heldal, Rogardt

doi:10.1109/icsa.2019.00024

Cited by 17 publications

(16 citation statements)

References 29 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Lessons learned 5: 1) Upfront aspects balancing: As we can learn from software architecting, it is important to go towards "just-in-time architecture" [33] and to find a balance between upfront aspects (what is planned before the start of development) and emerging aspects (what appears as decisions are taken in the course of the development, e.g. by fixing wrong assumptions or making decision deliberately postponed) [36]. 2) Importance of the architecture: Software architecture is still important even during emergency development.…”

Section: B Software Architecture Design (53)mentioning

confidence: 99%

Lessons Learned from the Development of a Mechanical Ventilator for COVID-19

Bombarda

Bonfanti

Galbiati

et al. 2021

2021 IEEE 32nd International Symposium on Software Reliability Engineering (ISSRE)

Self Cite

View full text Add to dashboard Cite

During the COVID-19 pandemic, many researchers all over the world have offered their time and competencies to face the heavy consequences of the disease. This is the case of a group of physicists, engineers, and physicians that around the middle of March 2020 started to develop a simplified mechanical lung ventilator, called MVM (Mechanical Ventilator Milano), to answer the high request of ventilators for Acute Respiratory Distress Syndrome (ARDS) in intensive care units. A prototype was ready in around one month.Since medical software malfunctions can lead to injuries or death of patients, before marketing MVM ventilators and distributing them in hospitals, software certification in accordance with the IEC 62304 standard was mandatory to guarantee system reliability. The team was then complemented by computer scientists specifically devoted to this task. The software reengineering process, which lasted around two months from the end of the prototype, brought to a strong re-implementation of the device software components, which involved all the stakeholders in a continuous integration setting.In this paper, we report the experience of the MVM control SW re-engineering necessary to show evidence that the SW adheres to the standards and to consequently obtain the certification. We share results and lessons learned from this social project, where more than 100 volunteer researchers worked towards software certification at the extreme of their strength to get a real device finished in a rush since strongly required to support physicians in treating COVID-19 patients.

show abstract

Section: B Software Architecture Design (53)mentioning

confidence: 99%

Lessons Learned from the Development of a Mechanical Ventilator for COVID-19

Bombarda

Bonfanti

Galbiati

et al. 2021

2021 IEEE 32nd International Symposium on Software Reliability Engineering (ISSRE)

Self Cite

View full text Add to dashboard Cite

show abstract

“…Finally, based on past work [25,27], we find that governance of BOs is crucial. Roles can be part of a Governance Team, which governs a BO.…”

Section: Bomi Metamodelmentioning

confidence: 82%

“…Roles can be part of a Governance Team, which governs a BO. For instance, a Community of Practice is a potential governance team for architecture descriptions [25]. We collect interesting attributes of this relationship in the Governs association class, including the Coordination Mechanism (e.g., meetings, processes, standards, tools), and the Frequency of Coordination.…”

Section: Bomi Metamodelmentioning

confidence: 99%

“…In this paper, we address this gap by proposing a metamodel for boundary objects and methodological islands in large-scale systems development. This model is based on empirical data and accounts from ongoing projects [14,25,26]. By creating such a model, a complete picture of an organization's coordination needs and boundary objects can be established, analyzed, and used to identify and mitigate current issues in a more visual and structured way.…”

Section: Introductionmentioning

confidence: 99%

“…We found that BOs can belong to several super types (e.g., Technology, Task, or Planning) [14] and should be managed in groups of representatives of several teams [27]. Moreover, we studied architecture descriptions and interfaces as BOs [24,25]. We found that important dimensions of interface change are stability, time to perform a change, criticality, level of abstraction, distance to affected parties, number of affected components, position in the interface's lifecycle, and maturity of affected functions.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Modeling and Analysis of Boundary Objects and Methodological Islands in Large-Scale Systems Development

Wohlrab¹,

Horkoff²,

Kasauli³

et al. 2020

Preprint

Self Cite

View full text Add to dashboard Cite

Large-scale systems development commonly faces the challenge of managing relevant knowledge between different organizational groups, particularly in increasingly agile contexts. In previous studies, we found the importance of analyzing methodological islands (i.e., groups using different development methods than the surrounding organization) and boundary objects between them. In this paper, we propose a metamodel to better capture and analyze coordination and knowledge management in practice. Such a metamodel can allow practitioners to describe current practices, analyze issues, and design better-suited coordination mechanisms. We evaluated the conceptual model together with four large-scale companies developing complex systems. In particular, we derived an initial list of bad smells that can be leveraged to detect issues and devise suitable improvement strategies for inter-team coordination in large-scale development. We present the model, smells, and our evaluation results.

show abstract

DOMICO: Checking conformance between domain models and implementations

Zhong,

Zhang,

Huang

et al. 2023

Softw Pract Exp

View full text Add to dashboard Cite

As a predominant design method for microsservices architecture (MSA), domain‐driven design (DDD) utilizes a series of standard patterns in both models and implementations to effectively support the design of architectural elements. However, an implementation may deviate from its original domain model that uses certain patterns. The deviation between a domain model and its implementation is a type of architectural drift, which needs to be detected promptly. This paper proposes an approach, namely DOMICO, to check the conformance between the domain model and its implementation, by which the conformance is formalized by defining eight common structural patterns of domain modeling and their representations in both models and the corresponding source code. Based on the formalization, our approach can not only identify the discrepancies (e.g., divergence, absence, and modification) with respect to pattern elements, but also detect possible violations of 24 compliance rules imposed by the patterns. To validate DOMICO, we performed a case study to investigate its use in a supply chain project and its performance. The results show that DOMICO can accurately identify 100% inconsistency issues in the cases examined. As the first conformance checking approach for DDD, DOMICO can be integrated into the regular domain modeling process and help ensure the conformity of microservice implementations to models.

show abstract

Improving the Consistency and Usefulness of Architecture Descriptions: Guidelines for Architects

Cited by 17 publications

References 29 publications

Lessons Learned from the Development of a Mechanical Ventilator for COVID-19

Lessons Learned from the Development of a Mechanical Ventilator for COVID-19

Modeling and Analysis of Boundary Objects and Methodological Islands in Large-Scale Systems Development

DOMICO: Checking conformance between domain models and implementations

Contact Info

Product

Resources

About