RSS Feed
Wednesday, December 10, 2008 | 
Well, last day of the AADI (application architecture development and integration) conference and transition to the first day of the EA (enterprise architecture) conference. I'm taking a break from listening to analysts and going to listen to what National City has done. They had a representative on my panel, and it seems like they have their ducks in a row. However, as that rep quipped, you can have a wonderful technology strategy and execution, but when your business buys up MBS's and CDO's right before the financial meltdown, there's little IT can do.
Aleks
16 hours ago
9 comments:
Well, these guys actually built the common services model. Helps when you have the CIO driving this down all the way to the bottom and reorganizing his world to suit the new construction model. Impressive, especially since they are 3x larger than Lincoln.
Aleks
Getting Started with EA: The first 200 days with Philip Allega
Just to start - I've never been given 200 days to build EA - usually my departments are up in 90 days.
So, as of October 2008, most EA organizations fall in the 2.1 score out of 5 - which Gartner calls ad-hoc, but really means disfunctional :)
I love it - Gartner has adopted our context definitions - Core and Common have been "leveraged" wholesale, and they are calling Value-Add "Distinct". Cool, nice to know that we're setting the vocabulary for the industry!
A
Philip is suggesting that a common requirements vision document be written. Having gone through this a couple of times now, I can't think of a more difficult path to tackle. At least we started on the backend of the SDLC and started ironing out the deployment and QA at the same time. The more I think about it, back to front technique is probably much more productive than front to back. Getting the QA/Deployment ironed out allows for quicker deployment of collected and agreed to requirements, which builds credibility for future releases.
Aleks
Ah, reality sets in. Socialization is the most important thing before having a meeting! Go figure!
Aleks
It looks like this presentation is skipping a step. Philip is going straight from Requirements to Principles to Models. How Principles flow into Models is a missing process - e.g. the Solution Context. The point is that Principles and Models are separated by a Technology Strategy step. Otherwise, trying to keep alignment and linkage between them is relatively difficult.
Aleks
IEEE 1471 specification provides the viewpoints and Gartner buckets them into Business, Technology and Information with Solution Architecture in the middle. Organizational and Risk concerns are completely missing.
Aleks
Well, it's starting to happen. I've been saying that if CEO's understood what EA does, there would be no way that they would allow, just from political perspective, EA to report anywhere but straight to them. Philip is mentioning a case where an enlightened CEO understood that.
Aleks
Post a Comment