|
Tuesday, 06 May 2008 |
|
Enterprise Architecture has become a real container term; everyone uses it but means something slightly different. This confusion is not very constructive and certainly does not provide enterprise architecture with a positive image to other stakeholders. I therefore propose to reserve the term enterprise architecture only for the highest-level form of architecture; there where the organisation strategy needs to be made concrete.
 Comments (20)
|
|
more
|
|
|
Wednesday, 30 January 2008 |
|
A lot of organisations seem to think that Service Oriented Architecture (SOA) is the silver bullet for a lot of organisational issues, and that an Enterprise Service Bus (ESB) is a universal business adapter that can connect everything transparently. I strongly disagree with such statements: SOA and ESB are overhyped, and are mostly pushed by the IT industry.
Comments (6) |
|
more
|
|
|
Tuesday, 23 October 2007 |
|
Projects that have been working on the architecture for months. Infrastructure that takes forever to implement because it is just too complex, and that seems to do much more than we need. Endless discussions between enterprise architects and project members about issues that have been talked over again and again. Project architectures that look more like reference architectures and/or meta-models than project documents. What we need is architecture that is motivation driven.
Be the first to write a comment |
|
more
|
|
|
Wednesday, 19 September 2007 |
|
One of the key trends in the IT industry is that technology keeps changing. Was your application developed more than two years ago? Chances are high that it does not comply with new technological developments, product versions or design best-practices. Did you just learn a new programming environment? The latest framework will require you to learn much of it over again. All these new technologies are simply added to the existing environment, since we just cannot affort to stay behing the competition. Also, IT professionals generally get a kick out of learning and applying new technology.
Comments (3) |
|
more
|
|
|
Friday, 13 July 2007 |
|
Every now and then I ask myself: what is it I am really doing? I always seem to come up with the same type of answer, independent of the project I am currently in. My work basically consists of understanding the situation, formulating questions, finding answers by talking to a lot of people, and writing everything down in some structured form. Is this the essence of being an architect?
Be the first to write a comment |
|
more
|
|
|
Friday, 15 June 2007 |
|
Lately I have been involved in discussions on the role of models in enterprise architecture. Some people seem to think that an enterprise architecture describes detailed models of current and future situations. Typically these models are stored in an enterprise repository, that could also be filled partially by other sources such as the configuration management database or sourcecode files. Let's step back a little bit to look at the role of models in architecture in general.
Be the first to write a comment |
|
more
|
|
|
Sunday, 11 March 2007 |
|
My vision on architecture is that it is all about making fundamental choices, and influencing the right people in order to achieve the required change. This means that architecture is also very much concerned with change management and stakeholder management. I also believe that architecture should combine top-down and bottom-up views.
Be the first to write a comment |
|
more
|
|
|
