The role of software architecture in requirements engineering

@article{Shekaran1994TheRO,
  title={The role of software architecture in requirements engineering},
  author={M. Chandra Shekaran and David Garlan and Michael Jackson and Nancy R. Mead and Colin M. Potts and Howard B. Reubenstein},
  journal={Proceedings of IEEE International Conference on Requirements Engineering},
  year={1994},
  pages={239-245}
}
The role of software architecture (which reflects high-level implementation constraints) in requirements engineering is clarified by providing perspectives on relevant issues, including the following: is requirements engineering merely a front end to the software development process that is concerned only with problem definition? Is software architecture an application-specific, high-level design of a system (for example, "an object-oriented system with a specified object hierarchy")? What is… 
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).
How Software Architecture can Frame, Constrain and Inspire System Requirements
TLDR
The experience is that a much more dynamic relationship can be achieved between these key activities within the system design lifecycle, that allows the architecture to constrain the requirements to an achievable set of possibilities, frame the requirements making their implications clearer, and inspire new requirements from the capabilities of the system's architecture.
Enterprise Modelling and the Teleological Approach to Requirements Engineering
TLDR
This paper describes an approach which involves the explicit modelling of organizational objectives, social roles and operations and the synthesis of these different perspectives towards a set of information systems requirements.
CHAPTER 2 SOFTWARE REQUIREMENTS
TLDR
This document proposes a breakdown of the SWEBOK Software Requirements Knowledge Area, concerned with the acquisition, analysis, specification, validation and management of software requirements.
Domains as a Prerequisite for Requirements and Software Domain Perspectives & Facets, Requirements Aspects and Software Views
  • D. Bjørner
  • Computer Science
    Requirements Targeting Software and Systems Engineering
  • 1997
We take software [systems] engineering to consist of three major phases: domain engineering, requirements engineering and software [systems] design engineering. We outline these and emphasise domain
On the similarity between requirements and architecture
Architectural Effects on Requirements Decisions: An Exploratory Study
TLDR
Specific types of architectural effects on requirements decisions are identified, as are different aspects of the architecture together with the extent of their effects.
Customized Choreography and Requirement Template Models as a Means for Addressing Software Architects’ Challenges
TLDR
A case-study is presented intended to discover and understand software architects’ challenges and to propose domain-specific models to address these challenges.
Requirements implementation in embedded software development
TLDR
To validate the feasibility of the developed framework, two case studies were carried out within embedded software development organisations and indicated that the framework was a useful foundation for improving the organisations' requirements implementation practices.
How do system architectures affect software requirements?
TLDR
Emerging results from an exploratory controlled study investigating the "characteristics" of newly elicited requirements gathered in the presence of an existing architecture are described.
...
...