SOAR

Architecturally Significant Requirements (ASRs)

1. Introduction
2. Contents
   1. Essential content
   2. Described by
   3. Related alphas
3. States
   1. Elicited
   2. Self Checked
   3. Addressed
   4. Fulfilled
4. References

Introduction

Architecturally Significant Requirements (ASRs): An ASR is any functional or non-functional requirement that is relevant for the SoS software architecture and therefore drives the architectural design.

ASRs are often related to quality attributes, missions, constraints, and requirements derived from environmental conditions ¹ .

ASRs are obtained after agreement through different stakeholders to be further handled by the architecture. It must allow the Architectural Team to identify the best Candidate Architectural Solutions (CASs) for the system under development.

Contents

Essential content

N/A

Described by

• ASRs Documentation:

  [Brief description of the WorkProduct]

Related alphas

• Requirements (Parent)

• Architectural Team establishes with Architecturally Significant Requirements (ASRs)
• Architecturally Significant Concerns (ASCs) influence Architecturally Significant Requirements (ASRs)
• Architecturally Significant Requirements (ASRs) drive Software Architecture
• Candidate Architectural Solutions (CASs) fulfill Architecturally Significant Requirements (ASRs)
• Context influences Architecturally Significant Requirements (ASRs)
• Emergent Behaviors satisfy Architecturally Significant Requirements (ASRs)
• Stakeholders fulfill Architecturally Significant Requirements (ASRs)

States

Elicited

ASRs has been identified and accepted.

Checkpoints

The alpha is in this state when:

• The origin of the ASRs is clear.
• The identified ASRs are representative to the SoS as a whole or to a relevant part of the SoS.
• The rationale behind the ASRs is clear and aligned with SoS Missions.
• Conflicting ASRs are identified, negotiated, and attended to.
• The priority of the ASRs is clear.
• The impact of implementing the ASRs is understood.
• The mechanisms for managing these ASRs are in place.
• The prioritization scheme is clear.
• Constraints are identified and considered.
• The ASRs are captured and shared with the project teams and the stakeholders.
• Conflicts between stakeholders are solved.
• All related stakeholders and project teams agree with the identified ASRs.

Self Checked

The self-requirements are elicited.

Checkpoints

The alpha is in this state when:

• The origin of the self-ASRs is clear.
• Conflicting self-ASRs are identified, negotiated, and attended to.

Addressed

Enough of the ASRs have been addressed by a set of CASs.

Checkpoints

The alpha is in this state when:

• The CASs to address the ASRs are proposed.
• Bidirectional traceability between ASRs and CASs is clear.
• The related project teams and stakeholders accept the current set of CASs as adequate do address the ASRs.
• The development teams understand what has to be delivered in terms of implementation and agrees to deliver it.

Fulfilled

The current software architecture fully satisfies the established ASRs.

Checkpoints

The alpha is in this state when:

• The current architectural version is implemented and the system is operational.
• The architectural team and the stakeholders accept that the current software architecture accurately satisfies the ASRs.

References

¹ Chen, L., Ali Babar, M., Nuseibeh, B.: Characterizing Architecturally Significant Requirements. In: IEEE Software, Vol. 30, P. 38-45, 2013.

² ISO/IEC 42010 (IEEE Std) 1471-2000: Systems and Software engineering – Recomended practice for architectural description of software-intensive systems. (2011)

³ Hofmeister, C., Kruchten, P., Nord, R., Obbink, H., Ran, A., America, P.: A General Model of Software Architecture Design Derived from Five Industrial Approaches. In: Journal of Systems and Software, Vol. 80 Issue 1, January, P. 106-126, 2007

Copyright © 2014 ICMC Instituto de Ciências Matemáticas e de Computação, University of São Paulo (USP), Brasil - IRISA Institut de Recherche en Informatique et Systèmes Aléatoires, Université de Bretagne-Sud (UBS), France, ver. beta 1.0