Solution Vision

SOLUTION VISION (SV) – It is a high-level architectural design which responds to current business needs. The changes in the architectural layer are built into those Requirements. It always comes with  business value, never alone as changes in architecture are never the target by itself. It is a part of business change, step by step moving towards a Reference Architecture. It is a true heart of incremental continuous transformation of organization in the architectural landscape. In some cases  it might contain changes like a new Component, a shift of capabilities from one Component to another, decommissioning Application/Components/technology/capability and others like migrations etc.

One of the most important elements of a good SV is involvement of developers in its creation. Effective cooperation between the architect and developers/ devops/admins is crucial to ensure high-quality architecture and effective implementation.   Understanding the assumptions presented by the architect should be built through the participation of the architect in the daily life of the development team.

In the context of building solutions, the architect with business is responsible for the creation of high-quality non-functional requirements, including safety requirements. The architect should be sure that the solution he is building is based on good NFR

SV implementation:

Creation of Solution Vision is built into organization SDLC and it is always triggered by  current business Requirements. It transforms business initiative into an architectural design of one or more applications showing them as logical components with their capabilities and interaction between them. It should cover all changes in the hardware layer and define Non Functional Requirements for business initiative as they are major inputs for a good architectural design.

 The key for a proper implementation of it is to do incremental changes in the architectural landscape providing new Components, interactions, capabilities step by step with a full compliance to a Reference Architecture, information form CPD, Standards. Using this approach organizations have a faster beneficial outcome and a chance to test a benefit hypothesis which stood behind implementation, having a possibility for faster adoption and learnings, saving money compared to a big transformation project (big bum projects).

The target of an enterprise is not to make changes in the architecture layer by itself , but to make changes  which bring value for the organization. That is why we should only make as many of them as they would be sufficient for a proper economic outcome and secure technological growth of the enterprise. That is why it has to be tightly combined into enterprise SDLC.

For example, Solution Vision can be introduced into a software development environment based on the scrum methodology in the model in which this document is input for the operation of individual teams. The architect builds a vision of the solution for the entire initiative and it is transmitted to individual application teams. This is illustrated in the diagram below.

An abstract illustration of placing Solution Vision in SDLC