A key deliverable associated with the book is the PBE Development Practice. A development practice is a process component - that is, a part of an overall development process that can be combined with other practices to form a complete process. The practice contains details on the roles, tasks, work products and work flows associated with the PBE effort. We wrote the practice using Eclipse Process Framework Composer (EPFC) - a tool from the Eclipse project that is used to author and customize process content. Like Eclipse itself, EPFC is open source and free. A number of other practices are available from the EPFC project - SCRUM, XP, OpenUP and even some practices on writing practices (MAM). The content written using EPFC can also be used in Rational Method Composer (RMC) and combined with content published by IBM and others. RMC is a commercial product and there is a fee for the product and some of the content.
The PBE Practice is freely available from our website (patternsbasedengineering.net) and is released under a Creative Commons license that allows you to use and update the content.
If you are new to EPFC and EPF, I'd suggest taking a look at some of the documentation at the project's website: http://www.eclipse.org/epf/ where they have a number of articles and presentations. When working with EPFC you are able to load in a number of practices, update the content, add elements or hide elements. Once you have finished your customization (based on the needs of your project and team) you can publish the content to a website for access via any standard web browser.
So with that in mind, the question is: how do I leverage this foundation to integrate PBE into a specific process? There's no single answer, but we do provide some tips and guidance on how to integrate with SCRUM, XP and OpenUP. Chapter 8 in the book focuses on introducing the practice and discussing how to perform some of this integration work. A key aspect of this effort is knowing where you should start. We suggest starting small - there are quite a few elements to the PBE Practice as well as a number of elements in the PBE Patterns and Guidelines. We wouldn't want a team to get overwhelmed or bogged down in trying to learn and and adopt too many new things at once. Better to start small, have some successes and then build on those successes. With that in mind we suggest looking at a few of the tasks from the practice (Find Project Patterns, Design a Pattern, Use a Pattern, Build a Pattern Implementation and Capture Reuse Metrics). These tasks from the practice will then guide you toward some related patterns and guidelines that make sense to start with.