Journal ArticleDOI
The Twin Peaks of Requirements and Architecture
TLDR
The twin peaks of requirements and architecture have been referred to as the twin peaks as mentioned in this paper, which describe the trade-offs that must be carefully considered and balanced between requirements and architectures.Abstract:
Quality concerns, often referred to as nonfunctional requirements, service-level agreements, quality attributes, performance constraints, or architecturally significant requirements, describe system-level attributes such as security, performance, reliability, and maintainability. In conjunction with functional requirements, these quality concerns drive and constrain a system's architectural design and often introduce significant trade-offs that must be carefully considered and balanced. The dependencies that exist between requirements and architecture have been referred to as the twin peaks of requirements and architecture. The guest editors of this special issue describe this unique situation.read more
Citations
More filters
Journal ArticleDOI
A systematic review of software architecture visualization techniques
TL;DR: This work aimed at systematically reviewing the literature on software architecture visualization to develop a classification of VTs in SA, analyze the level of reported evidence and the use of different VTs for representing SA in different application domains, and identify the gaps for future research in the area.
Proceedings ArticleDOI
How much up-front?: a grounded theory of agile architecture
TL;DR: A grounded theory of agile architecture is presented that describes how agile software teams answer the question of how much upfront architecture design effort is enough to help them determine how much effort they should put into up-front design.
Proceedings ArticleDOI
Probing for requirements knowledge to stimulate architectural thinking
Preethu Rose Anish,Balaji Balasubramaniam,Abhishek Sainani,Jane Cleland-Huang,Maya Daneva,Roel Wieringa,Smita Ghaisas +6 more
TL;DR: A new study with over 40 experienced architects is reported to identify reusable PQs for five areas of functionality and organize them into structured flows that can be used by Business Analysts to elicit and specify architecturally relevant information.
Book ChapterDOI
Relating System Quality and Software Architecture
TL;DR: System Quality and Software Architecture collects state-of-the-art knowledge on how to intertwine software quality requirements with software architecture and how quality attributes are exhibited by the architecture of the system.
Proceedings ArticleDOI
The General Data Protection Regulation: Requirements, Architectures, and Constraints
TL;DR: In this paper, the authors present an implementation for a software architecture that complies both with the requirements elicited and the constraints elaborated by the General Data Protection Regulation (GDPR).
References
More filters
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.
Journal ArticleDOI
Foundations for the study of software architecture
TL;DR: A model of software architecture that consists of three components: elements, form, and rationale is presented, which provides the underlying basis for the architecture in terms of the system constraints, which most often derive from the system requirements.
Journal ArticleDOI
Get ready for agile methods, with care
TL;DR: Although many of their advocates consider the agile and plan-driven software development methods polar opposites, synthesizing the two can provide developers with a comprehensive spectrum of tools and options, and a combined approach is feasible and preferable in some circumstances.
Journal ArticleDOI
Weaving together requirements and architectures
TL;DR: The spiral life-cycle model as mentioned in this paper addresses many drawbacks of a waterfall development process by providing an incremental development process, in which developers repeatedly evaluate changing project risks to manage unstable requirements and funding.
BookDOI
Relating Software Requirements and Architectures
TL;DR: The editors have divided the contributions into four parts: Part 1 Theoretical Underpinnings and Reviews addresses the issue of requirements change management in architectural design through traceability and reasoning, and Tools and Techniques presents approaches, tools, and techniques for bridging the gap between software requirements and architecture.