Ebooks Link Collection and Review

Author: Scott L. Bain
Publisher: Addison Wesley Professional
Pub Date: February 27, 2008
Print ISBN-10: 0-321-50936-6
Print ISBN-13: 978-0-321-50936-9
eText ISBN-10: 0-321-55372-1
eText ISBN-13: 978-0-321-55372-0
Pages: 448

Overview
For software to consistently deliver promised results, software development must mature into a true profession. Emergent Design points the way. As software continues to evolve and mature, software development processes become more complicated, relying on a variety of methodologies and approaches. This book illuminates the path to building the next generation of software. Author Scott L. Bain integrates the best of today's most important development disciplines into a unified, streamlined, realistic, and fully actionable approach to developing software. Drawing on patterns, refactoring, and test-driven development, Bain offers a blueprint for moving efficiently through the entire software lifecycle, smoothly managing change, and consistently delivering systems that are robust, reliable, and cost-effective.

Reflecting a deep understanding of the natural flow of system development, Emergent Design helps developers work with the flow, instead of against it. Bain introduces the principles and practices of emergent design one step at a time, showing how to promote the natural evolution of software systems over time, making systems work better and provide greater value. To illuminate his approach, Bain presents code examples wherever necessary and concludes with a complete project case study.

This book provides developers, project leads, and testers powerful new ways to collaborate, achieve immediate goals, and build systems that improve in quality with each iteration.

Coverage includes

• How to design software in a more natural, evolutionary, and professional way
• How to use the "open-closed" principle to mitigate risks and eliminate waste
• How and when to test your design throughout the development process
• How to translate design principles into practices that actually lead to better code
• How to determine how much design is enough
• How refactoring can help you reduce over-design and manage change more effectively