Often, I don’t have the detailed knowledge of a product, programming language or a system, so what I do is to review the basic foundation for the solution design.
In a recent Twitter discussion about requirements management, I wrote,
"Requirements management is like bookkeeping. You need to do it in business, but it doesn’t guarantee profits”
When talking about collecting requirements, one of the challanges is what we mean with requirements and level of detail. The requirements we ask for should also be possible to verify.
One of the challenges with Enterprise Architecture and high-level design is that the solution looks good on paper, but is not possible to implement in reality. This is especially tough if we are trying some new types of solution, at least in this organisation.
Based on the need from the user and business model, a high-level design hypothesis looks like something like the image below. We have done some architecture work prior to sketching the design, i.e. an evaluation of different options of how the solution would look like, but that is a subject for a separate post.