Just like the Enterprise Architect, the Solution architect works with cartography and models.
His day-to-day work consists of communication, As-Is situation, roadmap or expected To-Be.
More generally, the Solution Architect manages all deliverables of his IT Projects and is in charge of the update of EA referential.

The Solution Architect works with the same tools than the Enterprise Architect or the Domain Architect.
He develops cartography for his IT Projects and uses these tool for his communication and completes IT Project documents.
To work out Solution Architecture a certain number of models are used in order to share different views on the IT Projects and ensure consistency.

To communicate, the SA:

• Starts with a description of the As-is of the IT Projects.
• Afterwards he describes different To-Be scenarios, as well as the different migration paths between the As-Is and the To-Be.
• Lastly, the created documentation should explain the established choices for the different projects.

With description of As-Is and the ability to make a choice regarding the needed solution of the To-Be for his projects, the Solution Architect is the bridge between the objectives and execution.

It is in that perspective, that the Solution Architect prepares a result of a negotiation between the wishes & feasibility, a pilot of the quality for the IS projects and means of managing the costs (Reduction in the number of project failures, avoidance of overlap and/or double functions).

Just like the Enterprise Architect, the Solution architect works with cartography and models.
His day-to-day work consists of communication, As-Is situation, roadmap or expected To-Be.
More generally, the Solution Architect manages all deliverables of his IT Projects and is in charge of the update of EA referential.

The Solution Architect works with the same tools than the Enterprise Architect or the Domain Architect.
He develops cartography for his IT Projects and uses these tool for his communication and completes IT Project documents.
To work out Solution Architecture a certain number of models are used in order to share different views on the IT Projects and ensure consistency.

To communicate, the SA:

• Starts with a description of the As-is of the IT Projects.
• Afterwards he describes different To-Be scenarios, as well as the different migration paths between the As-Is and the To-Be.
• Lastly, the created documentation should explain the established choices for the different projects.

With description of As-Is and the ability to make a choice regarding the needed solution of the To-Be for his projects, the Solution Architect is the bridge between the objectives and execution.

It is in that perspective, that the Solution Architect prepares a result of a negotiation between the wishes & feasibility, a pilot of the quality for the IS projects and means of managing the costs (Reduction in the number of project failures, avoidance of overlap and/or double functions).

Communication, As-Is situation, roadmap or expected To-Be are the day-to-day work of a domain architect.
In case the Enterprise architect would manages the domain architect, than the domain architect would manage the solution architects.

The Domain Architect works with the same tools than the Enterprise Architect.
He develops cartography & models and uses these tools for his communication.
To work out Domain Architecture he or she uses a certain number of models in order to share different views regarding the information system. They ensure consistency of the information system in the Domain and in the Enterprise.

The DA presents an expression of a business vision for a specific domain, proposes a reflection on different choices and makes sure that these choices are in line with the Business Strategy.
To set up a communication, the DA:

• starts with a description of the Information System for his own domain.
• Afterwards a descirption is made of the different To-Be scenarios, as well as the different migration paths between As-Is and To-Be scenarios.
• Finaly, it is documentation which will explain the established choices.

By describing different To-Be scenarios, the DA creates a framework for future systems.
In this role, a scope must be defined which specifies the functional and technical limits in which projects must fit.
This framework is a scientific balances between the corporate interest and specific interests to each project.

With description of As-Is and the build of the To-Be for a Domain, this role is the bridge between the objectives and the execution.
In fact, the DA is there to create the link between documentation and assess the strategic objectives and the operational activities realized thanks to IT tools.
In this perspective, the DA expresses the result of a negotiation between the wishes & feasibility, a pilot of the quality for the IS components and means of managing the costs (Reduction in the number of project failures, avoidance of overlap and/or double functions).

Communication, As-Is situation, roadmap or expected To-Be are the day-to-day work of a domain architect.
In case the Enterprise architect would manages the domain architect, than the domain architect would manage the solution architects.

The Domain Architect works with the same tools than the Enterprise Architect.
He develops cartography & models and uses these tools for his communication.
To work out Domain Architecture he or she uses a certain number of models in order to share different views regarding the information system. They ensure consistency of the information system in the Domain and in the Enterprise.

The DA presents an expression of a business vision for a specific domain, proposes a reflection on different choices and makes sure that these choices are in line with the Business Strategy.
To set up a communication, the DA:

• starts with a description of the Information System for his own domain.
• Afterwards a descirption is made of the different To-Be scenarios, as well as the different migration paths between As-Is and To-Be scenarios.
• Finaly, it is documentation which will explain the established choices.

By describing different To-Be scenarios, the DA creates a framework for future systems.
In this role, a scope must be defined which specifies the functional and technical limits in which projects must fit.
This framework is a scientific balances between the corporate interest and specific interests to each project.

With description of As-Is and the build of the To-Be for a Domain, this role is the bridge between the objectives and the execution.
In fact, the DA is there to create the link between documentation and assess the strategic objectives and the operational activities realized thanks to IT tools.
In this perspective, the DA expresses the result of a negotiation between the wishes & feasibility, a pilot of the quality for the IS components and means of managing the costs (Reduction in the number of project failures, avoidance of overlap and/or double functions).

The EA is a tool for communication through cartography & models. To work out Enterprise Architecture requires to define and to realize a certain number of models in order to share different views on the information system. These models and cartographies ensure consistency of the information system.

As EA is a Tool for communication, it's also the expression of a vision. EA is the reflection of choices and these choices are Business Strategic choices. To communicate, EA begin with a description of the Information System. Afterwards EA describes different To-Be scenarios, as well as the different migration paths, between the As-Is and the To-Be scenario’s. Lastly, it is the documentation which will make it possible to explain the established choices.

With the description of different To-Be scenarios, EA is a framework for the future systems. In this role, EA must define the scope which specifies the functional and technical limits in which projects must fit. This framework is a scientist balances between the corporate interest and specific interests to each project. EA is used as framework to decide on the situation to be implemented.

With description of As-Is and the build of the To-Be, EA is the bridge between the objectives and the execution. In fact, EA is to link document and assess between the strategic objectives and the operational activities realized thanks to IT tools. In this perspective, EA is, in the same time, result of a negotiation between the wishes & feasibility, a pilot of the quality for the IS components and a means of managing the costs :

• Reduction in the number of project failures ,
• Avoidance of overlap and/or double functions.

Why Should You Choose Us?

Efficiently unleash cross-media information without cross-media value. Quickly maximize timely deliverables for real-time schemas. Dramatically maintain clicks-and-mortar solutions without functional solutions.

Completely synergize resource sucking relationships via premier niche markets. Professionally cultivate one-to-one customer service with robust ideas. Dynamically innovate resource-leveling customer service for state of the art customer service.

Learn More