Data Conversion

I've run into an interesting quandry in my engagements - there are two completely different notions of what an "application architecture" is. For some, "application architecture" is the specification of standards around how programs get developed: the allowed languages, preferred patterns, and so forth. For others, it is documentation of the interactions between applications in the environment:

Enterprise Archiecture practitioners view a solid EA as critical to setting a three-to-five year strategic plan for the company. I don't see that view as frequently at the business leadership level. As EA practitioners, we need to be able to articulate how and why EA is important. Any kind of long-range planning follows a basic pattern: Purpose, Vision, Strategy, Objective, Plan. The Purpose is

IBM Information Server wins, Microsoft Office 2007 wins, Google snubbed, Oracle didn’t even know the awards were on.

Are you documenting your current IT architecture right now? Stop what you are doing and move away from the computer. You might be documenting something that is going to change before you've finished documenting it.

For those who are interested in what and why changes in day light savings - 2007. Attached below is a snippet from this link. Interesting detail of course is how this will affect the applications which are running...starting from

Earlier this month Najib had asked in reference to What is a Systems Architect and Systems Architecture Fundamentals

A Systems Architect responsibilities includes the ability to create, review, and update (don't forget this last one!) designs or blueprints to provide an overall direction for the system, project, department, or enterprise. See What is a Systems Architect? for more about the position. These

Many enterprises are starting to embrace blogging and one of the forerunners Six Apart is moving into the enterprise area. They have released their flagship product to corporations called "Movable Type Enterprise" which is to include priority customer support in the United States. Here is an excerpt from the article

Very interesting link. Couple of interesting concepts... MDA is more a lifecycle than a model... good idea. The interesting formula he coins E=MCsquared, where E is enterprise architecture and M for MDA and C-Squared for Cross Cutting Concerns. I like his way of looking at things - more practical than a theoretical exercise. Using MDA as a lifecycle is a good step than focusing on how

I've talked before about what architecture is. But how do you go about thinking about it?