Well, we've attempted to illustrate clearly the steps to designing your new CM solution, and hopefully you've figured out how to get started on this planning phase. As outlined in their book Use Case Driven Object Modeling with UML (Addison-Wesley, 1999), Doug Rosenberg and Kendall Scott summarized the goals of use case modeling:
You've built use cases that together account for all of the desired functionality of the system.
You've produced clear and concise written descriptions of the basic course of action, along with appropriate alternate courses of action, for each use case.
You've factored out scenarios common to more than one use case.
Once you have accomplished these things, you should be ready to design the next stage of your CM system.
Remember: bridges don't just happen. They take years of planning, followed by systematic implementation. The result is a resource that can improve the lives of those who use it. The same can be said for a solid configuration management system.
Our next few chapters will continue to explore the different aspects of configuration management deployment, including VOB architecture, security and data integrity, integration of other back-office applications, and customer-facing deployment strategies, such as training and support.