Models / Architecture Vision / Solution concept diagrams
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.

solution-concept-diagram

In this example, the main focus in on the "DiscountTravelOrderingSite" application component, and on the "BookTravel" 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 Sales person (Internal Actor) and Customer (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).

requirementRequirements: In this context, these are business requirements

goalGoal: A goal or objective of the enterprise.

external-actor-32External actor: An actor that is external to the enterprise.

internal-actor-32Internal actor: An actor that belongs to the enterprise.

DataBaseApplicationComponent32Database application component: Represents a repository. In pure SOA architecture, these elements should not appear. However, for legacy analysis or technology architecture, modeling repositories or repository deployment can be useful.

entity-componentEntity application component: An entity component is frequently derived from business entities, and is responsible for managing the access to the entity, and its integrity.

utility-componentUtility component: Represents an application component that is frequently reused, and most of the cases bought off the shelf.

system-federationSystem federation: A system federation is the coarser-grained application component. It assembles systems to federate them, such as in the example of cooperation between different information systems between different companies.

process-componentProcess application component: A process application component is responsible for a business process execution. It orchestrates the tasks of the process.

interaction-application-componentInteraction application component: Represents the top level components that manage the interaction with the external of the IS. In most cases, it is a GUI component, such as here a web interface.

ApplicationApplication: This application component corresponds to legacy applications, off the shelf products, or can be an assembly of application components.

togaf-process-32Business process: As presented in process maps (event diagrams). The business process is detailed in flow diagrams.

component-realizationComponent realization: An application component realizes the designated element, for example a business process.

assigned-linkAssigned link: Assignment of a goal to an element of the enterprise, typically an actor, an organization unit or a business process.

consumes-linkConsumes link: Expresses that a participant (e.g. an actor) consumes an element of the IS (service, operation, application component).

satisfy-linkSatisfy link: Expresses that an element of the IS satisfies a requirement.

Tags:
 

Comments  

 
+1 # George 2011-05-03 15:21
Just a terminology point :
The same element is used to represent goals and objectives.

However, TOGAF distinguishes the 2 terms (see TOGAF definitions):

Objective : A time-bounded milestone for an organization used to demonstrate progress towards a goal; for example, "Increase Capacity Utilization by 30% by the end of 2009 to support the planned increase in market share".
Goal : A high-level statement of intent or direction for an organization. Typically used to measure success of an organization.

In fact Goal is a kind of high level general requirement linked with a set of concretes objectives associated to a milestone.
Reply | Reply with quote | Quote
 
 
+1 # phil 2011-05-05 09:40
Hi George,

You are right. Using Modelio, this does not appear in the diagram. There are two ways to distinguish goals from objectives:
- define different goal container to separate objectives from goals
or
- use the "scope" property which can be strategic (same as TOGAF goals) operational (same as objectives) or relative (a refinement for objective)
Reply | Reply with quote | Quote
 

Add comment


Security code
Refresh

Login



Sign in to use the forum and be informed of the latest news.

Forum activity

More Topics »

Latest comments

Tag Cloud