Current Articles
| Categories
| Search
| Syndication
| Thursday, March 24, 2011 |
 |
The Enterprise Architect (EA) diary - Day 37-40 (EA & M&A)
By Administrator Account (admin) @ 4:56 AM :: Opinion :: 0 Comments :: 247 Views
|
|
The company that I worked for bought new company and I was send to map and evaluate the IT architecture. When I have to do this kind of work I tend to split it to two main steps. The first step is data collecting and mapping. This is the neutral stage when I’m just collecting the data and model it to get better understanding (no judgment).
This step includes collection of applications/products that being used to support business processes, how they connected one to each other and what data flows between them, which technologies they are using (including dev), their main components (and their data flow), databases and servers (including technologies and locations), interfaces with externals, DR solution in place and how they are dealing with non functional requirements (Performance, Reliability, availability, security, modifiability, maintainability, efficiency, ease of administration, scalability, monitoring etc’)
The second step is to understand how this given architecture fits and plug into our company principles and blue prints as well as to the business plans set up for the acquired company. In this phase I’m starting to ask more questions and to get better understanding of the current IT situation.
The result of such a visit is modelling of current IT landscape, mapping of existing gaps between what the acquired company has to offer and our architecture and business plans for this company and recommendation for immediate steps.
|
|
|
|
|
| Wednesday, March 16, 2011 |
|
The Enterprise Architect (EA) diary - Day 34-36 (Information Architecture)
By Administrator Account (admin) @ 6:47 AM :: Opinion :: 1 Comments :: 817 Views
|
|
Although enterprise architecture consider to be based on four domains (Business, Information, Applications and technology) for me the business and information domains are more important to become successful enterprise architect. There aren’t any doubts about the need to understand what is driving the business and what and how the business is reaching (and planning to reach) it strategy. Business architecture is crucial to make sure that IT is really supporting and planned to increase IT’s business support. Information architecture, which is critical for EA success is usually hide as sub domain of application architecture or doesn’t get the right attitude and resources.
|
| Read More.. |
|
|
|
|
| Thursday, March 10, 2011 |
|
The Enterprise Architect (EA) diary - Day 33 (Modelling, monitoring and health check)
By Host Account (host) @ 5:45 AM :: Opinion :: 0 Comments :: 277 Views
|
|
I manage to generate actual outcomes in two different areas today. I spend half of the day adjusting our retail business physical and logical. I’ve changed the physical architecture to reflect last changes in applications (new one), databases, servers and storage devices. The logical diagram went through a serious face lifting by braking applications into main sub models and their relations (including logical data storage). If you remember the handwrite drawing from my previous post, you can see how it looks now on a diagram.
he other half of the day was dedicated to health check ...
|
| Read More.. |
|
|
|
|
| Tuesday, March 08, 2011 |
|
The Enterprise Architect (EA) diary - Day 25-32 (Modeling & decentralized organization)
By Administrator Account (admin) @ 5:33 PM :: Opinion :: 0 Comments :: 281 Views
|
|
Working for company with different business units locating in different places around the world requires me to pay visits to our offices. In the last 6 days I paid a visit to our office in London and Manchester area (which belong to different business unit). The trip has two goals: to model changes in those offices current architecture and to reach an agreement regarding our target architecture (using the same principles and blueprints)
|
| Read More.. |
|
|
|
|
|