|
|
|
|
| LEADER |
04132nmm a2200505 u 4500 |
| 001 |
EB001938433 |
| 003 |
EBX01000000000000001101335 |
| 005 |
00000000000000.0 |
| 007 |
cr||||||||||||||||||||| |
| 008 |
210123 ||| eng |
| 020 |
|
|
|a 9781420053357
|
| 020 |
|
|
|a 1420053353
|
| 020 |
|
|
|a 1420053345
|
| 050 |
|
4 |
|a QA76.76.D47
|
| 100 |
1 |
|
|a Ford, Chris
|
| 245 |
0 |
0 |
|a Patterns for performance and operability
|b building and testing enterprise software
|c Chris Ford [and others]
|
| 260 |
|
|
|a Boca Raton
|b Auerbach Publications
|c 2008
|
| 300 |
|
|
|a xix, 317 pages
|b illustrations
|
| 505 |
0 |
|
|a Introduction ; Production Systems in the Real World; Why Should I Read This Book?; The Non-functional Systems Challenge; What Is Covered by Non-functional Testing; Planning for the Unexpected; Patterns for Operability in Application Design; Summary; Planning and Project Initiation ; The Business Case for Non-functional Testing; Scoping and Estimating; Test and Resource Planning; Communication Planning; Summary; Non-functional Requirements ; What are Non-functional Requirements?; Do I Need Non-functional Requirements?; Roles and Responsibilities; Challenging Requirements; Establishing a Business Usage Model; Non-functional Requirements; Summary Designing for Operability ; Error Categorization; Design Patterns; The Characteristics of a Robust System; Infrastructure Services; Design Reviews; The Operability Review; Summary
|
| 505 |
0 |
|
|a Designing for Performance ; Requirements; Architecture; Patterns; Antipatterns; Algorithms; Technology; Software; Hardware Infrastructure; Summary; Notes; Test Planning ; Defining Your Scope; Load Testing Software; Additional Testing Apparatus; Test Environments; Test Beds; Historical Data; Summary; Test Preparation and Execution ; Preparation Activities; Script Development; Performance Testing; Operability Testing; Sustainability Testing; Challenges; Summary; Deployment Strategies ; Procedure Characteristics; Packaging; Deployment Rehearsal; Rollout Strategies; Case Study: Online Banking; Case Study: The Banking Front Office; Back-Out Strategies; Summary; Resisting Pressure from the Functional Requirements Stream ; A Question of Degree; Pressures from the Functional
|
| 505 |
0 |
|
|a Requirements Stream; Attention; Defining Success; Setting the Stage for Success; Summary Operations Trending and Monitoring ; Monitoring; Trending and Reporting; Error Reporting; Capacity Modelling and Planning; Summary; Troubleshooting and Crisis Management ; Reproducing the Issue; Determining Root Cause; Troubleshooting Strategies; Applying a Fix; Post-Mortem Review; Summary Common Impediments to Good Design ; Design Dependencies; What Is the Definition of Good Design?; Testing a Design; Common Impediments to Good Design; Design Principles; Summary References ; Articles; Books; Web Sites
|
| 505 |
0 |
|
|a Includes bibliographical references and index
|
| 653 |
|
|
|a COMPUTERS / Programming / Open Source / bisacsh
|
| 653 |
|
|
|a Computer software / Development / fast
|
| 653 |
|
|
|a Computer software / Development / http://id.loc.gov/authorities/subjects/sh85029535
|
| 653 |
|
|
|a COMPUTERS / Software Development & Engineering / Tools / bisacsh
|
| 653 |
|
|
|a Computer software / Specifications
|
| 653 |
|
|
|a COMPUTERS / Software Development & Engineering / General / bisacsh
|
| 653 |
|
|
|a Computer software / fast
|
| 653 |
|
|
|a Debugging in computer science / http://id.loc.gov/authorities/subjects/sh85036145
|
| 653 |
|
|
|a Debugging in computer science / fast
|
| 653 |
|
|
|a Débogage
|
| 041 |
0 |
7 |
|a eng
|2 ISO 639-2
|
| 989 |
|
|
|b OREILLY
|a O'Reilly
|
| 015 |
|
|
|a GBA762703
|
| 015 |
|
|
|a GBB7C6914
|
| 776 |
|
|
|z 9781420053357
|
| 776 |
|
|
|z 1420053353
|
| 776 |
|
|
|z 9781420053340
|
| 776 |
|
|
|z 1420053345
|
| 856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9781420053357/?ar
|x Verlag
|3 Volltext
|
| 082 |
0 |
|
|a 005.1
|
| 082 |
0 |
|
|a 620
|
| 082 |
0 |
|
|a 500
|
| 520 |
|
|
|a Examines common failure scenarios and defensive design patterns, focusing on the complexities of nonfunctional testing and the difficulty to express accurate nonfunctional requirements
|