By Topic

Conflict-Centric Software Architectural Views: Exposing Trade-Offs in Quality Requirements

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

2 Author(s)
Juha Savolainen ; Nokia Research Center, Finland ; Tomi Mannisto

Architectural documentation improves the overall understanding of a proposed software system's design, but its true value comes from facilitating the process of satisfying architecturally significant requirements (ASRs). Architectural views are a tool for documenting ASRs in the context of particular quality attributes. Views offer a convenient way to capture architectural decisions, rationales, and alternatives considered. However, when multiple stakeholders have conflicting quality requirements, traditional architectural views tend to scatter their resolutions throughout the documentation.

Published in:

IEEE Software  (Volume:27 ,  Issue: 6 )