Proceedings Article10.1109/ISRE.1995.512554
Using non-functional requirements to systematically support change
TL;DR: It is shown how a historical record of the treatment of NFRs during the development process can also serve to systematically support evolution of the software system.
read more
Abstract: Non-functional requirements (or quality requirements, NFRs) such as confidentiality, performance and timeliness are often crucial to a software system. Our NFR-framework treats NFRs as goals to be achieved during the process of system development. Throughout the process, goals are decomposed, design tradeoffs are analysed, design decisions are rationalised, and goal achievement is evaluated. This paper shows how a historical record of the treatment of NFRs during the development process can also serve to systematically support evolution of the software system. We treat changes in terms: of (i) adding or modifying NFRs, or changing their importance, and (ii) changes in design decisions or design rationale. This incremental approach is illustrated by a study of changes in banking policies at Barclays Bank.
read more
Chat with Paper
AI Agents for this Paper
Find similar papers on Google Scholar, PubMed and Arxiv
Write a critical review of this paper
Analyze citations of this paper to find unaddressed research gaps
Citations
Towards modelling and reasoning support for early-phase requirements engineering
TL;DR: This paper argues that a different kind of modelling and reasoning support is needed for the early phase of requirements engineering, which aims to model and analyze stakeholder interests and how they might be addressed, or compromised, by various system-and-environment alternatives.
Identifying quality-requirement conflicts
Barry Boehm,Hoh Peter In +1 more
TL;DR: QARCC, a knowledge-based tool that helps users, developers, and customers analyze requirements and identify conflicts among them, is developed.
359
Dealing with non-functional requirements: three experimental studies of a process-oriented approach
Lawrence Chung,Brian A. Nixon +1 more
- 23 Apr 1995
TL;DR: An initial evaluation of the extent to which the framework's objectives are met is given, providing preliminary support for the usefulness of certain aspects of the framework, while raising some open issues.
232
SPL Conqueror: Toward optimization of non-functional properties in software product lines
Norbert Siegmund,Marko Rosenmüller,Martin Kuhlemann,Christian Kästner,Sven Apel,Gunter Saake +5 more
TL;DR: SPL Conqueror shows how non-functional properties can be qualitatively specified and quantitatively measured in the context of SPLs and discusses the variant-derivation process in SPL Conqueror that reduces the effort of computing an optimal variant.
188
Cooperative Information Systems: A Manifesto *
Giorgio De Michelis,Eric Dubois,Matthias Jarke,Florian Matthes,John Mylopoulos,Mike P. Papazoglou,Klaus Pohl,Joachim Schmidt,Carson Woo,Eric Yu +9 more
- 01 Jan 1997
TL;DR: This paper proposes a framework which views cooperative information systems as composed from three interrelated facets, viz. the system facet, the group collaboration facet, and the organizational facet; and presents an overview of these facets, emphasizing strategies they have developed over the past f ew years to accommodate change.
References
A field study of the software design process for large systems
TL;DR: A layered behavioral model is used to analyze how three of these problems—the thin spread of application domain knowledge, fluctuating and conflicting requirements, and communication bottlenecks and breakdowns—affected software productivity and quality through their impact on cognitive, social, and organizational processes.
2.3K
•Book
Problem-Solving Methods in Artificial Intelligence
Nils J. Nilsson
- 01 Jan 1971
TL;DR: This paper will concern you to try reading problem solving methods in artificial intelligence as one of the reading material to finish quickly.
1.7K
The TAME project: towards improvement-oriented software environments
Victor R. Basili,H. D. Rombach +1 more
TL;DR: The TAME system is an instantiation of the TAME software engineering process model as an ISEE (integrated software engineering environment) and the first in a series of Tame system prototypes has been developed.
Related Papers (5)
Lawrence Chung,Julio Cesar Sampaio do Prado Leite +1 more
- 04 Jul 2009
Anne Dardenne,Axel van Lamsweerde,Stephen Fickas +2 more
- 01 Apr 1993