Solution Blueprint
A Solution Blueprint contains both the scope and design of the solution through a series of architecture patterns. Each architecture presents the solution and its core design assertions through a unique perspective, as we will now explore.
A blueprint is used as either an architectural plan or technical drawing. The concept was first introduced by Sir John Herschel in 1842, using a contact print process on light-sensitive sheets. It was a drawing of white lines on a blue background, thus its name. Traditional blueprints became obsolete as less expensive printing methods and computer technology became widely available.
The term has been used since then for many other purposes, including within the software industry, where it's taken on the role of the Solution Blueprint. It's best suited for CRM solutions, as well as solution architectural plans for other types of business applications where there are many stakeholders and different views are required...
