Design – Build – Run: Applied Practices and Principles for Production-Ready Software Development

Chapter 25. Review and Wrap-Up

Some of the ideas and concepts discussed in this book will require more formal modeling, and, in some cases, would actually require you to prototype the solution. It is always worth prototyping something to ensure that the design (and implementation) is straight. There's nothing worse than putting something down in a design document only to find that it doesn't work when you come to implement it. This is true for everything and not just the code.

In terms of the case study, it is at this point that you'd start your detailed design and planning activities. The case study has helped to promote the analysis, design, and planning activities. You'd bring everything together and solidify your solution. However, I've simply used the case study to model real world scenarios against a hypothetical development project. It is not about documenting, reviewing, or even implementing the final solution for the case study, it is about learning from the lessons and considerations it has highlighted and applying these to your own projects and solutions.

This final chapter is organized into the following sections:

• Back to the Real World — This section summarizes some of the patterns and practices discussed in this book and it looks at a couple of them and the implications of implementing them on real-world projects. In doing so, it uses Visual Studio and the code supplied with this book to demonstrate some of the tools and concepts.

• Onwards and Upwards — This section ...