When We Say Domain, What's Our Choice?

Referred URL

http://herdingcats.typepad.com/my_weblog/2011/06/when-we-say-domain-whats-our-choice.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:+typepad/HerdingCats+(Herding+Cats)&utm_content=Google+Reade 

The current issue of Communications of the ACM, 06/2011, Vol. 54 No. 6 has an articled titled The Profession of IT, Who Are We - Now? There is a table of the professional subdivisions.

So where there is discussion of a method, a management processes, some technology, or anything pretty much that requires a domain and a context in that domain, maybe this table would be a start to answer the question - Have you tried your suggestion in one of these? If so, how did it turn out?

The challenge of course is to separate the generalizations - and likely over generalizations - of any suggestion from the specific domain and context processes. For example Earned Value Management (my favorite topic) is applicable in many domains, but a complete waste of time in others. So when there is an over blown statement like "EV is pure hog wash," and there is no domain or context in that domain, it is pretty hard to derive any value from the conjecture.

The same can be said for the over generalized agile process application, although the list of domains is likely much larger than mine - Aerospace Engineering.