Solution concept diagrams

A solution concept diagram provides a high-level orientation of the solution that is envisaged in order to meet the objectives of the architecture engagement. In contrast to the more formal and detailed architecture diagrams developed in the following phases, the solution concept represents a pencil sketch of the expected solution at the outset of the engagement.

This diagram may embody key objectives, requirements and constraints for the engagement, and also highlight work areas to be investigated in more detail with formal architecture modeling. The purpose of this diagram is to quickly on-board and align stakeholders for a particular change initiative, so that all participants understand what the architecture engagement is seeking to achieve and how it is expected that a particular solution approach will meet the needs of the enterprise.

Present only the main application components of the solution, and summarize their connections using "access" dependencies. Connect them to existing applications when necessary. Connect them to requirements, processes or functions, themselves connected to goals. Also express (via "consumes" dependencies) which role uses which component.

A "macro" vision of the architecture of the targeted solution is therefore presented, including links to the goals and requirements that the different elements of the solution must satisfy.

In this example, the main focus in on the "TripReservationSite" application component, and on the "ReserveTrip" process application component. They satisfy the requirements "Internet Booking access" and Booking process automation". They correspond to the following enterprise goals : Improve productivity, improve the BPM, etc. The two main involved users are Account manager (Internal Actor) and Client (External Actor). Other application components are presented (Travel, Customer, Order, Accounting ERP, Portfolio Repository, Credit Card) mainly to show which new main components have to be developped, which repository will be reused or developed, and which legacy applications need to be connected (here the ERP).