Via Radovan, a slide set that makes some odd and ambiguous claims (granted, it is just a slide set), including this doozy;

Projects and enterprises should define their Service Architecture FIRST

Requirements and process need to be in the context of that architecture

Geez, and folks rag on me for claiming that the Web is a far more general solution than believed; apparently, you can just assume SOA for all problems, independent of their requirements! Think of all the time saved actually trying to fit a solution to the requirements of the problem! 8-)

I can only assume this is an error.


no comment until now

Add your comment now