Enterprise / Solution architecture process 

As said, Enterprise and Solution architecture analyses can be delivered with minimal presence at customer premises by means of proactive well defined work packages. Activities typically planned at customer premises are:


Topics discussed during the meeting


Identification of analysis high-level scope, involved applications, number of stakeholders, requirements, bjectives and pain points to allow an overall effort estimation of the complete analysis.


Initial meeting with all required organization stakeholders.


Detail together the scope and debt of analysis, impacted ASIS business, applications and data architectures, the business & IT requirements and objectives, current strengths, weaknesses, opportunities and treats.


Align on the analysis approach, management expectations and acceptance criteria, and effort estimation of the analysis.


Depending on the size and complexity will we agree together on the frequency to divide the entire analysis period by reporting and alignment meetings.

During analysis

Enterprise & solution architecture alignment meetings.



Presentation of analysis, different options with their respective SWOT analysis, architectural ecommendations, delivery strategies and estimations.


Closure and acceptance of the analysis.

During each meeting we will align on the need and basis to continue the analysis, and confirm on the outstanding effort estimations.

·   Network architecture,

·   Application, data and technology architectures

Typical Enterprise / Solution Architecture document content:

General sections:

·   Project name, code, manager, sponsor, architect,

·   Principle organization stakeholders,

·   Document history,

·   Authors, contributors,

·   Approvals,

·   Referenced documents, sites, artefacts,

Architectural analysis:

·   Assumptions,

·   Dependencies,

·   Issues / Open points

·   Requirements and traecibility,

·   Global architecture Overview,

·   High-level Overview,

·   Product Models,

·   Order Types and scenarios,

·   Technical and functional use cases,

·   Impact on components :

·   <components subsections>,

·   Use of information and data :

·   Information Concepts in Scope

·   Technical, non-functional requirements,

·   Volumetric and Performance requirements,

·   Chinese Walls,

·   RSA, Security, checklists, operational, system installation & maintenance, user account management, references,

·    Delivery Strategy,

·    Estimations,

·    Executive Summary

Copyright ® 2011 TAKINA.be

BE 0838.923.504

IBAN BE89 7310 1995 4285

  For information: info@takina.be