Characterizing Architecturally Significant Requirements

@article{Chen2013CharacterizingAS,
  title={Characterizing Architecturally Significant Requirements},
  author={Lianping Chen and Muhammad Ali Babar and Bashar Nuseibeh},
  journal={IEEE Software},
  year={2013},
  volume={30},
  pages={38-45}
}
This article presents a framework for characterizing architecturally significant requirements (ASRs) on the basis of an empirical study using grounded theory. The study involved interviews with 90 practitioners with an accumulated 1,448 years of software development experiences in more than 500 organizations of various sizes and domains. These findings could provide researchers with a framework for discussing and conducting further research on ASRs and can inform researchers' development of… 

Figures from this paper

Empirical Evaluation of an Approach that Stimulates Architectural Thinking during Requirements Gathering
TLDR
The goal of this PhD project is to enhance communication between the two roles by introducing a knowledge base with architectural knowledge to be used by business analysts using an empirical approach.
An Approach That Stimulates Architectural Thinking during Requirements Elicitation: An Empirical Evaluation
TLDR
An approach of using architectural knowledge that can serve as a communication medium between requirements analyst and software architects is designed and it is found that in the experience of the participating practitioners, the approach is relevant, easy to use and effective.
From architecture to requirements: Relating requirements and architecture for better Requirements Engineering
  • F. Chen
  • Computer Science, Business
    2014 IEEE 22nd International Requirements Engineering Conference (RE)
  • 2014
TLDR
This research aims at advancing RE practice through the co-development of requirements and architecture by utilizing the relationship between Architecturally Significant Requirements (ASRs) and Architectural Design Decisions (ADDs).
Identifying Architecturally Significant Functional Requirements
TLDR
ArcheR is envisaged, a tool that automates the identification of architecturally significant functional requirements from requirement specification documents and their classification into categories based on the different kinds of architectural impact they can have and recommend possible architectural solutions in response to the architectural impact.
Towards an Approach to Stimulate Architectural Thinking during Requirements Engineering Phase
  • Preethu Rose Anish
  • Computer Science
    2016 IEEE 24th International Requirements Engineering Conference (RE)
  • 2016
TLDR
This research will investigate how architects cope with missing information in real-world large scale projects and leverage the knowledge of experienced software architects and make it available to business analysts so that they are equipped to elicit a more complete set of requirements that feed sufficient information into the architecture design process.
What you ask is what you get: Understanding architecturally significant functional requirements
TLDR
A preliminary quantitative evaluation of the results against real-life software requirements specification documents indicated that software specifications in the sample largely do not contain the crucial architectural differentiators that may impact architectural choices and that PQs are a necessary mechanism to unearth them.
Grounded Architectures: Using Grounded Theory for the Design of Software Architectures
TLDR
By using GT, this work proposes an approach to systematically elicit ASRs and identify ADDs based on grounded theory (GT) which provides transparency and fosters objectivity.
Retrospection and Perspectives on Pragmatic Software Architecture Design: An Industrial Report
TLDR
A retrospective report on the extensive architecture design of a large scale mission-critical system conducted in a company, trying to incorporate newly proposed concepts and methods from academic realm and keeping introspective during the whole process.
MAPPING REQUIREMENTS TO A PRODUCT ARCHITECTURE SUPPORTED BY A PLM SYSTEM
TLDR
An approach for mapping requirements to architectural views of a product family is presented and 5 views are suggested, 2 requirement model views, a customer view and a functional view, and 3 views describing the product architecture; functional system, physical module and interface view.
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 17 REFERENCES
Weaving Together Requirements and Architectures
TLDR
The spiral life-cycle model addresses many drawbacks of a waterfall model by providing an incremental development process, in which developers repeatedly evaluate changing project risks to manage unstable requirements and funding.
Software architecture: foundations, theory, and practice
TLDR
This tutorial affords the participant an extensive treatment of the field of software architecture, its foundation, principles, and elements, including those mentioned above, and looks at emerging and likely future trends in this field.
Using grounded theory to study the experience of software development
TLDR
A model to help the software engineering researchers interpret the often fuzzy definitions found in Grounded Theory texts and share the experience and lessons learned during their research.
Architecture-driven problem decomposition
TLDR
This work shows how these two views can be reconciled and demonstrate how a choice of architecture can facilitate problem analysis, decomposition and subsequent recomposition, within the problem frames framework.
Relating Business Goals to Architecturally Significant Requirements for Software Systems
TLDR
This report illustrates how to use architecturally significant business goals to produce a set of derived quality attribute requirements that can then be vetted and elaborated with the appropriate goal-subject(s) and goal-object(s).
Managing Variability in Software Product Lines
TLDR
A conceptual framework of terminology for the concept of variability is provided and how variability can be managed in Software Product Lines is discussed.
A Systematic Review of Software Development Cost Estimation Studies
TLDR
A systematic review of previous work identifies 304 software cost estimation papers in 76 journals and classifies the papers according to research topic, estimation approach, research approach, study context and data set to provide a basis for the improvement of software-estimation research.
A Systematic Review of Software Development Cost Estimation Studies
TLDR
A systematic review of previous work identifies 304 software cost estimation papers in 76 journals and classifies the papers according to research topic, estimation approach, research approach, study context and data set to provide a basis for the improvement of software-estimation research.
The Discovery of Grounded Theory: Strategies for Qualitative Research
Most writing on sociological method has been concerned with how accurate facts can be obtained and how theory can thereby be more rigorously tested. In The Discovery of Grounded Theory, Barney Glaser
...
1
2
...