Structured to follow the software life cycle, Patterns for Performance and Operability provides advice and examples-based instructions at every phase. You can read it from start to finish or go directly to those chapters that interest you the most. Whatever approach you choose, you will learn: How to: Am Define and document comprehensive non-functional requirements for any software system Am Define scope and logistics for non-functional test activities Am Execute non-functional tests and report results clearly and effectively Am Patterns for defensive software designs in common software scenarios that promote operability and availability Am Implement the right level of reporting, monitoring, and trending for highly available production software systems Patterns for: Am Software designs that support simpler and more efficient operation in a production environment Am Software design that support high-performance and scalability Strategies and Techniques for: Am Techniques for managing and troubleshooting during a production crisis Am Strategies for resisting project pressure to compromise on quality or completeness of non-functional activities in the software cycle... LoadRunner: http://www.mercury.com/us/products/performance-center/ loadrunner/ Moorea#39;s Law at Wikipedia: ... Oracle Real Application Clusters (RAC): http://www.oracle.com/database/rac_home.html Simple Network Management Protocolanbsp;...
|Title||:||Patterns for Performance and Operability|
|Author||:||Chris Ford, Ido Gileadi, Sanjiv Purba, Mike Moerman|
|Publisher||:||CRC Press - 2007-12-22|