tag:blogger.com,1999:blog-2120400492278270391.post9125203242614019585..comments2023-08-23T06:57:04.599-07:00Comments on Enterprise Architecture - A Practitioner's View: Zachman, Frameworks and EAChris Birdhttp://www.blogger.com/profile/13436436994311245922noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-2120400492278270391.post-81510476360781607682009-11-30T07:56:55.587-08:002009-11-30T07:56:55.587-08:00Sally,
Of course you are right. The columns do ha...Sally,<br /><br />Of course you are right. The columns do have great relevance. It's just that I don't see a huge need to instantiate any of the cells. I agree with your "nudging" people towards separation of concerns. And, you know if that's what it does, it's useful. Probably not as revolutionary or insightful as some adherents would like, but valuable nonetheless.Chris Birdhttps://www.blogger.com/profile/13436436994311245922noreply@blogger.comtag:blogger.com,1999:blog-2120400492278270391.post-3486487073495132042009-11-30T06:06:33.069-08:002009-11-30T06:06:33.069-08:00Chris, nice blog.
Actually I have found that the ...Chris, nice blog. <br />Actually I have found that the columns do have some value, too, though sadly our journey was too short to get into this. When looking at Business Architecture, IT folk have a tendency to ignore the right hand 3 columns of the Framework, because they are more comfortable analysing data (or rather things, to be strictly correct) and processes/transformations. So the columns are useful as a checklist for completeness and as a means of nudging people towards appropriate separation of concerns.Cybersalhttps://www.blogger.com/profile/15258055798612329124noreply@blogger.com