Suche Bilder Maps Play YouTube News Gmail Drive Mehr »
Meine Bibliothek | Hilfe | Erweiterte Buchsuche | Webprotokoll | Anmelden

Books

Non-Functional Requirements in Software Engineering

Frontcover
1 Rezension
Kluwer Academic, 2000 - 439 Seiten
Non-Functional Requirements in Software Engineering presents a systematic and pragmatic approach to `building quality into' software systems. Systems must exhibit software quality attributes, such as accuracy, performance, security and modifiability. However, such non-functional requirements (NFRs) are difficult to address in many projects, even though there are many techniques to meet functional requirements in order to provide desired functionality. This is particularly true since the NFRs for each system typically interact with each other, have a broad impact on the system and may be subjective. To enable developers to systematically deal with a system's diverse NFRs, this book presents the NFR Framework. Structured graphical facilities are offered for stating NFRs and managing them by refining and inter-relating NFRs, justifying decisions, and determining their impact. Since NFRs might not be absolutely achieved, they may simply be satisfied sufficiently (`satisficed'). To reflect this, NFRs are represented as `softgoals', whose interdependencies, such as tradeoffs and synergy, are captured in graphs. The impact of decisions is qualitatively propagated through the graph to determine how well a chosen target system satisfices its NFRs. Throughout development, developers direct the process, using their expertise while being aided by catalogues of knowledge about NFRs, development techniques and tradeoffs, which can all be explored, reused and customized. Non-Functional Requirements in Software Engineering demonstrates the applicability of the NFR Framework to a variety of NFRs, domains, system characteristics and application areas. This will help readers apply the Framework to NFRs and domains of particular interest to them. Detailed treatments of particular NFRs - accuracy, security and performance requirements - along with treatments of NFRs for information systems are presented as specializations of the NFR Framework. Case studies of NFRs for a variety of information systems include credit card and administrative systems. The use of the Framework for particular application areas is illustrated for software architecture as well as enterprise modelling. Feedback from domain experts in industry and government provides an initial evaluation of the Framework and some case studies. Drawing on research results from several theses and refereed papers, this book's presentation, terminology and graphical notation have been integrated and illustrated with many figures. Non-Functional Requirements in Software Engineering is an excellent resource for software engineering practitioners, researchers and students.

Was andere dazu sagen - Rezension schreiben

Es wurden keine Rezensionen gefunden.

Ähnliche Bücher

Verweise auf dieses Buch

Aus anderen Büchern

Methodologies and Software Engineering for Agent Systems: The Agent-Oriented ...
Perspectives on Software Requirements
Alle Ergebnisse von Google Books »

Aus Google Scholar

Requirements Engineering: A Roadmap
Bashar Nuseibeh, Steve Easterbrook
Tropos: An Agent-Oriented Software Development Methodology
Paolo Bresciani, Anna Perini, Paolo Giorgini, Fausto Giunchiglia, John Mylopoulos - 2004 - Autonomous Agents and Multi-Agent Systems
Towards requirements-driven information systems engineering: the ...
Jaelson Castro, Manuel Kolp, John Mylopoulos - 2002 - Information Systems
Quality of service for workflows and web service processes
Jorge Cardoso, Amit Sheth, John Miller, Jonathan Arnold, Krys Kochut - 2004 - Web Semantics: Science, Services and Agents on the World Wide Web
Alle Suchergebnisse von Google Scholar »

Referenzen von Webseiten

Non-Functional Requirements in Software Engineering
Non-Functional Requirements in Software Engineering presents a systematic and pragmatic approach to `building quality into' software systems. ...
www.utdallas.edu/ ~chung/ BOOK/ book.html

citeulike: Non-Functional Requirements in Software Engineering ...
Non-Functional Requirements in Software Engineering (THE KLUWER INTERNATIONAL SERIES IN SOFTWARE ENGINEERING Volume 5) (International Series in Software ...
www.citeulike.org/ user/ sdehousse/ article/ 408725

Herrmann : Software Engineering iia: Requirements Engineering und ...
Non-functional requirements in software engineering / by Lawrence Chung ... - Boston, Mass. [ua] : Kluwer Academic, 2000. - XXX, 439 S. : graph. Darst. ...
www.rzuser.uni-heidelberg.de/ ~f25/ kvv/ ss2007/ k-108.htm

Quantifying non-functional requirements: a process oriented ...
Abstract. In this work, we propose a framework for. quantifying non-functional requirements (nfrs). This. framework uses quality characteristics of the ...
ieeexplore.ieee.org/ iel5/ 9273/ 29455/ 01335697.pdf?arnumber=1335697

Non-Functional Requirements: From Languages Elicitation to Modelling
Non-Functional Requirements: From. Languages. Elicitation to Modelling. Luiz Marcio Cysneiros. Department of Computer Science. University of Toronto ...
portal.acm.org/ citation.cfm?doid=581339.581452

Quantifying Non-Functional Requirements: A Process Oriented Approach
Abstract. In this work, we propose a framework for. quantifying non-functional requirements (nfrs). This. framework uses quality characteristics of the ...
www.gracehopper.org/ 2004/ Proceedings/ PDF/ ni_Hill.pdf

[Paper] Using Classpects for Integrating Non-Functional and ...
[6] L. Chung, B. Nixon, E. Yu, and J. Mylopoulos, Non-Functional Requirements in Software Engineering(Kluwer Academic, 2000). [7] J. Mylopoulos, L. Chung, ...
www.actapress.com/ PDFViewer.aspx?paperId=23337

Analysis of Conflicts among Non-Functional Requirements Using ...
Analysis of Conflicts among Non-Functional Requirements Using Integrated. Analysis of Functional and Non-Functional Requirements ...
doi.ieeecomputersociety.org/ 10.1109/ COMPSAC.2007.73

Evolving System Architecture to Meet Changing Business Goals: an ...
Evolving System Architecture to Meet Changing Business Goals: an Agent and. Goal-Oriented Approach. Daniel Gross & Eric Yu. Faculty of Information Studies ...
csdl.computer.org/ comp/ proceedings/ re/ 2001/ 1125/ 00/ 11250316.pdf

Functional requirements, non-functional requirements, and ...
Functional requirements, non-functional requirements,. and architecture should not be separated. –A position paper. Barbara Paech,* Allen H. Dutoit,** ...
www.empress-itea.org/ publications/ EMPRESS_05.pdf

Über den Autor (2000)

Eric Yu is Associate Professor in the Faculty of Information at the University of Toronto.

Bibliografische Informationen