Building a Blueprint Solution
Once you have been through all the client discovery and requirements-gathering sessions, it’s up to the solution architect (SA) to create a viable solution for their project. Knowing what the client needs and how it should be implemented is an important step to a successful project. A good blueprint will be easily explained and defended. That, in turn, makes the sign-off by the client on the design a simple formality.
In this chapter, we’ll look at the following key topics:
- Knowing what goes into a solution blueprint
- Expressing user requirements
- Documents to include in the blueprint
- How to maintain a living document
