scispace - formally typeset
Proceedings ArticleDOI

STREAM-ADD - Supporting the Documentation of Architectural Design Decisions in an Architecture Derivation Process

Reads0
Chats0
TLDR
An extension of the STREAM process, named STREAM-ADD (Strategy for Transition between Requirements and Architectural Models with Architectural Decisions Documentation) is defined, which aims to systematize the documentation of architectural decisions by the time they are made and to support the refinement of the architecture according to such decisions.
Abstract
Requirements Engineering and Architectural Design are activities of the software development process that are strongly related and intertwined. Thus, providing effective methods of integration between requirements and architecture is an important Software Engineering challenge. In this context, the STREAM process presents a model-driven approach to generate early software architecture models from requirements models. Despite being a systematic derivation approach, STREAM does not support the documentation of architectural decisions and their corresponding rationale. Recent studies in the software architecture community have stressed the need to treat architectural design decisions and their rationale as first class citizens in software architecture specification. In this paper we define an extension of this process, named STREAM-ADD (Strategy for Transition between Requirements and Architectural Models with Architectural Decisions Documentation). This extended process aims to systematize the documentation of architectural decisions by the time they are made and to support the refinement of the architecture according to such decisions. In order to illustrate our approach, it was applied for creating the architecture specification of a route-planning system.

read more

Content maybe subject to copyright    Report

Citations
More filters

Seventh ACIS International Conference on Software Engineering, Artificial Intelligence, Networking, and Parallel/Distributed Computing

TL;DR: The first € price and the £ and $ price are net prices, subject to local VAT, and the €(D) includes 7% for Germany, the€(A) includes 10% for Austria.
Proceedings ArticleDOI

MADCAT: A Methodology for Architecture and Deployment of Cloud Application Topologies

TL;DR: A methodology tackling the practical problems encountered when designing and deploying cloud applications is introduced, addressing the complete application development lifecycle, from architectural design to concrete deployment topologies provisioned and executed on cloud infrastructure.
Book ChapterDOI

Supporting consistency between architectural design decisions and component models through reusable architectural knowledge transformations

TL;DR: An AK transformation language supporting reusable AK transformations from pattern-based ADDs to component-and-connector models is introduced and it is shown that it offers high reusability, is largely automated and scalable, and can deal with the complexity of large numbers of recurring decisions.
Proceedings ArticleDOI

Towards an Evidence-Based Understanding of Emergence of Architecture through Continuous Refactoring in Agile Software Development

TL;DR: Based on a large-scale empirical study involving 102 practitioners who had worked with agile and architecture approaches, it is found that whether or not architecture emerges through continuous refactoring depends upon several contextual factors.
Proceedings ArticleDOI

The Evolution of Architectural Decision Making as a Key Focus Area of Software Architecture Research: A Semi-Systematic Literature Study

TL;DR: A semi-systematic literature review of 218 papers published over the last four decades that have contributed to a better understanding of architectural design decisions (ADDs) and human aspects in architectural decision making (ADM), and group decision making is presented.
References
More filters
Book

Pattern-oriented Software Architecture: A System of Patterns

TL;DR: Patterns.
Book ChapterDOI

On Non-Functional Requirements in Software Engineering

TL;DR: This chapter reviews the state of the art on the treatment of non-functional requirements (hereafter, NFRs), while providing some prospects for future directions.
Book

Requirements Engineering: Processes and Techniques

TL;DR: Tried and tested techniques such as data-flow and object-oriented models are covered as well as some promising new ones and are all based on real systems descriptions to demonstrate the applicability of the approach.

Modelling strategic relationships for process reengineering

John Mylopoulos, +1 more
TL;DR: This thesis proposes a modelling framework i* (pronounced i-star) consisting of two modelling components: the Strategic Dependency (SD) model and the Strategic Rationale (SR) model, which describes a process in terms of intentional dependency relationships among agents.
Book

Documenting Software Architectures: Views and Beyond

TL;DR: This lecture maps the concepts and templates explored in this tutorial with well-known architectural prescriptions, including the 4+1 approach of the Rational Unified Process, the Siemens Four Views approach, and the ANSI/IEEE-1471-2000 recommended best practice for documenting architectures for software-intensive systems.
Related Papers (5)