The software development industry is increasingly realizing that success depends on a project’s long-term viability. To help with that effort, the Software Improvement Group (SIG) has identified ten guidelines for delivering code that’s easy to maintain and adapt over time.
While a full examination of these guidelines is available in Building Maintainable Software (O’Reilly), this report focuses on their application in the real world. Author and agile consultant Abraham Marin-Perez briefly explores each guideline and uses a running example to demonstrate how they can work together in a production environment. You’ll also get case studies of ten European organizations that have significantly benefitted from these guidelines.
The Ten Guidelines for Maintainable Software aren’t just a theoretical exercise. In fact, SIG created them after years of analyzing what made some software projects successful and maintainable, while many others ultimately fell short. By applying these guidelines, you’ll benefit from the wisdom of developers who preceded you.
Table of contents
- 1. “How Did We Get into This Mess?”
2. The Ten Guidelines
- Unit Guidelines
- Architectural Guidelines
- Enabling Guidelines
- 3. Applying the Ten Guidelines
- 4. Ten Real-World Use Cases
- Title: Real-World Maintainable Software
- Release date: October 2016
- Publisher(s): O'Reilly Media, Inc.
- ISBN: 9781491958582
You might also like
Expanded Edition (August 2018) Updated with Design Patterns episodes from the Clean Code series from Clean …
Go is rapidly becoming the preferred language for building web services. There are plenty of tutorials …
Semantic Software Design
With this practical book, architects, CTOs, and CIOs will learn a set of patterns for the …
Software Architecture Patterns
The success of any application or system depends on the architecture pattern you use. By describing …