Configuration Management
The Missing Link in Web Engineering
1st Edition
Published on 1. January 2000
296 pages
978-1-58053-389-8 (ISBN)
Description
Authored by an internationally known expert in configuration management (CM) solutions, this unique new book helps experienced professionals and novices alike see why CM is critical to the survival of their company's e-commerce and e-business development and management. Unlike other books on configuration management, this book examines CM from a "e;business value"e; perspective and shows why CM is critical to successful software development and, in particular, web development and maintenance. You learn why your company's e-business and e-commerce - encompassing web content, web applications, back-office applications, code and data - simply will not survive or thrive without CM. This practical, comprehensive book provides a thorough overview of CM technology, and reveals "e;best practice"e; techniques for selecting and deploying automated CM solutions. Nine key challenges facing e-commerce are detailed, along with practical guidelines for avoiding common pitfalls that can quickly derail your e-business. Case studies provide real-world examples of how major e-commerce companies use CM techniques for web development and maintenance today.
More details
Other editions
Additional editions
Book
10/2000
Artech House Publishers
€89.50
Shipment within 10-20 days
Content
- Intro
- Contents
- Preface xv
- Acknowledgments xvii
- 1 The Internet is a Fabulous Invention, But...
- The beginnings of maintenance problems 5
- The Web crisis consequence 6
- The Web changes everything 9
- Speed has changed everything 10
- Companies that embraced the Web created new opportunities 12
- Companies that ignored the Web are paying the price 16
- We need Web engineering 18
- Companies are busy now 19
- The future and some good advice 21
- Be proactive and win! 22
- An outline of each chapter 22
- Why I wrote this book 24
- The audience for this book 26
- Key messages from this chapter 26
- 2 The Nature of the World Wide Web 29
- The Internet rules! 30
- The beauty and potential of the Web 31
- The phases of Web acceptance 34
- Initial focus for companies concerning their Web systems 36
- Mistakes are made too easily and are very costly 37
- The Web crisis 40
- What is driving the Web crisis? 42
- Web systems can be very complex 44
- Web system architecture and terminology 48
- Nine key Web crisis challenges 52
- Signs of a crisis point 65
- The nature of Web programming 65
- Key messages from this chapter 68
- 3 Understanding the Many Views of Configuration Management 73
- Configuration management is configuration management regardless of object type 74
- The essence of configuration management: Key notions and terms 78
- The value and benefits of configuration management 83
- Signs of a configuration management problem 87
- What drives companies to a configuration management solution 88
- How success drives companies to configuration management 89
- Unified view of configuration management 93
- The eight functional areas of software configuration management 94
- Key decisions companies must make, or mistakes I see too often 102
- Key messages from this chapter 103
- 4 The Automation of Configuration Management 107
- Automated, not manual, configuration management 109
- Spectrum of configuration management tools 109
- Not all configuration management tools are the same 111
- CM for Web teams 112
- What the configuration management vendors are doing 116
- What is the best configuration management tool? 118
- Enterprise-wide solution or project-specific solution? 119
- Relationship to other disciplines and tools 121
- Concepts, or architectural elements, in configuration management tools 124
- The death and resurrection of the configuration management industry 131
- Key messages from this chapter 132
- 5 Configuration Management Tool Selection and Deployment 135
- Configuration management opens up a can of worms 137
- Size matters, but it does not change how adoption is done 137
- Quick and dirty adoption or methodical adoption? 138
- The good, the bad, and the ugly about adoption 140
- Why companies fail at adopting a configuration management solution 141
- The model of the configuration management solution 143
- Sequence of steps in the configuration management solution 146
- How long are the tool selection and adoption going to take? 172
- ROI and useful metrics 173
- How can we recover from tool adoption failure, or turn shelfware into UseWare ? 176
- The value of configuration management vendors 177
- The big gap regarding standards 180
- Should the tool follow the process or should the process follow the tool? 181
- Key messages from this chapter 182
- 6 Case Studies in Configuration Management Automation of Web Systems 185
- What I did 186
- The messages and best practices 186
- Case study: Carclub.com 189
- Case study: eCampus.com 192
- Case study: EDS 196
- Case study: Lockheed Martin Aeronautical Systems 204
- Case study: Lycos 206
- Case study: NASD 210
- Case study: OneSource Information Services Inc. 219
- Case study: USinternetworking 222
- Appendix A
- A.1 Configuration management questionnaire 230
- A.2 Categories of configuration management requirements 240
- A.3 Categories of risks 240
- A.4 Process description 244
- A.5 Types of process or process levels 245
- A.6 Example of a CM process model 245
- A.7 Template for configuration management status report 253
- A.8 Template for risk management plan 255
- A.9 Template for a pilot project plan 258
- About the Author
- Index
