|
|
|
|
| LEADER |
04685nmm a2200385 u 4500 |
| 001 |
EB000625995 |
| 003 |
EBX01000000000000000479077 |
| 005 |
00000000000000.0 |
| 007 |
cr||||||||||||||||||||| |
| 008 |
140122 ||| eng |
| 020 |
|
|
|a 9781461552697
|
| 100 |
1 |
|
|a Chung, Lawrence
|
| 245 |
0 |
0 |
|a Non-Functional Requirements in Software Engineering
|h Elektronische Ressource
|c by Lawrence Chung, Brian A. Nixon, Eric Yu, John Mylopoulos
|
| 250 |
|
|
|a 1st ed. 2000
|
| 260 |
|
|
|a New York, NY
|b Springer US
|c 2000, 2000
|
| 300 |
|
|
|a XXX, 441 p
|b online resource
|
| 505 |
0 |
|
|a 1. Introduction -- 1.1 Introduction -- 1.2 The Nature of Non-Functional Requirements -- 1.3 Literature Notes -- 1 The NFR Framework -- 2. The Nfr Framework In Action -- 3. Softgoal Interdependency Graphs -- 4. Cataloguing Refinement Methods and Correlations -- II Types of Non-Functional Requirements -- 5. Types Of Nfrs -- 6. Accuracy Requirements -- 7. Security Requirements -- 8. Performance Requirements -- 9. Performance Requirements For Information Systems -- III Case Studies and Applications -- 10. Introduction to the Studies and Applications -- 11. A Credit Card System -- 12. An Administrative System -- 13. Application To Software Architecture -- 14. Enterprise Modelling and Business Process Redesign -- 15. Assessment of Studies -- Postscript
|
| 653 |
|
|
|a Symbolic and Algebraic Manipulation
|
| 653 |
|
|
|a Software engineering
|
| 653 |
|
|
|a Computer science / Mathematics
|
| 653 |
|
|
|a Artificial Intelligence
|
| 653 |
|
|
|a Software Engineering
|
| 653 |
|
|
|a Artificial intelligence
|
| 700 |
1 |
|
|a Nixon, Brian A.
|e [author]
|
| 700 |
1 |
|
|a Yu, Eric
|e [author]
|
| 700 |
1 |
|
|a Mylopoulos, John
|e [author]
|
| 041 |
0 |
7 |
|a eng
|2 ISO 639-2
|
| 989 |
|
|
|b SBA
|a Springer Book Archives -2004
|
| 490 |
0 |
|
|a International Series in Software Engineering
|
| 028 |
5 |
0 |
|a 10.1007/978-1-4615-5269-7
|
| 856 |
4 |
0 |
|u https://doi.org/10.1007/978-1-4615-5269-7?nosfx=y
|x Verlag
|3 Volltext
|
| 082 |
0 |
|
|a 005.1
|
| 520 |
|
|
|a 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 NFRFramework.
|
| 520 |
|
|
|a 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').
|
| 520 |
|
|
|a 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
|