Configuration management best practices : practical methods that work in the real world /
Successfully Implement High-Value Configuration Management Processes in Any Development Environment As IT systems have grown increasingly complex and mission-critical, effective configuration management (CM) has become critical to an organization's success. Using CM best practices, IT professio...
Clasificación: | Libro Electrónico |
---|---|
Autor principal: | |
Otros Autores: | |
Formato: | Electrónico eBook |
Idioma: | Inglés |
Publicado: |
Upper Saddle River, NJ :
Addison-Wesley,
Ã2011.
|
Temas: | |
Acceso en línea: | Texto completo (Requiere registro previo con correo institucional) |
Tabla de Contenidos:
- Introduction
- Part 1 : The core CM best practices framework
- Chapter 1 Source Code Management
- Goals of Source Code Management
- Principles of Source Code Management
- 1.1 Why Is Source Code Management Important?
- 1.2 Where Do I Start?
- 1.3 Source Code Management Core Concepts
- 1.4 Defect and Requirements Tracking
- 1.5 Managing the Globally Distributed Development Team
- 1.6 Tools Selection
- 1.7 Recognizing the Cost of Quality (and Total Cost of Ownership)
- 1.8 Training
- 1.9 Defining the Usage Model
- 1.10 Time to Implement and Risks to Success
- 1.11 Establishing Your Support Process
- 1.12 Advanced Features and Empowering Users
- Conclusion
- Chapter 2 Build Engineering
- Goals of Build Engineering
- Principles of Build Engineering
- 2.1 Why Is Build Engineering Important?
- 2.2 Where Do I Start?
- 2.3 Build Engineering Core Concepts
- 2.4 Core Considerations for Scaling the Build Function
- 2.5 Build Tools Evaluation and Selection
- 2.6 Cost of Quality and Training
- 2.7 Making a Good Build Better
- 2.8 The Role of the Build Engineer
- 2.9 Architecture Is Fundamental
- 2.10 Establishing a Build Process
- 2.11 Continuous Integration Versus the Nightly Build
- 2.12 The Future of Build Engineering
- Conclusion
- Chapter 3 Environment Configuration
- Goals of Environment Configuration Control
- Principles of Environment Configuration Control
- 3.1 Why Is Environment Configuration Important?
- 3.2 Where Do I Start?
- 3.3 Supporting Code Promotion
- 3.4 Managing the Configuration
- 3.5 Practical Approaches to Establishing a CMDB
- 3.6 Change Control Depends on Environment Configuration
- 3.7 Minimize the Number of Controls Required
- 3.8 Managing Environments
- 3.9 The Future of Environment Configuration
- Conclusion
- Chapter 4 Change Control
- Goals of Change Control
- Principles of Change Control
- 4.1 Why Is Change Control Important?
- 4.2 Where Do I Start?
- 4.3 The Seven Types of Change Control
- 4.4 Creating a Change Control Function
- 4.5 Examples of Change Control in Action
- 4.6 Don't Forget the Risk
- 4.7 Driving the CM Process Through Change Control
- 4.8 Entry/Exit Criteria
- 4.9 After-Action Review
- 4.10 Make Sure That You Evaluate Yourself
- Conclusion
- Chapter 5 Release Management
- Goals of Release Management
- Principles of Release Management
- 5.1 Why Is Release Management Important?
- 5.2 Where Do I Start?
- 5.3 Release Management Concepts and Practices
- 5.4 The Ergonomics of Release Management
- 5.5 Release Management as Coordination
- 5.6 Requirements Tracking
- 5.7 Taking Release Management to the Next Level
- Conclusion
- Chapter 6 Deployment
- Goals of Deployment
- Principles of Deployment
- 6.1 Why Is Deployment Important?
- 6.2 Where Do I Start?
- 6.3 Practices and Examples
- 6.4 Conducting a Configuration Audit
- 6.5 Don't Forget the Smoke Test
- 6.6 Little Things Matter a Lot
- 6.7 Communications Planning
- 6.8 Deployment Should Be Delegated
- 6.9 Trust But Verify
- 6.10 Improving the Deployment Process
- Conclusion
- PART II: ARCHITECTURE AND HARDWARE CM
- Chapter 7 Architecting Your Application for CM
- Goals of Architecting Yo