Thank you, Rob, you are right. One more thing to add here: if the Business really participates in SOA, it has to validate all initial requirements against the business architecture to find the consequences of the requirement implementation and to validate the relevance of the requirement to the business needs. I saw many times when a requirement to add a field to the DB table or to the Web page was dictated by the operational convenience with no particular business value or mitigated business risk.
- Michael ________________________________ From: Rob Eamon <[EMAIL PROTECTED]> To: [email protected] Sent: Monday, November 3, 2008 7:06:07 PM Subject: [service-orientated-architecture] Re: Rhody tells you how to sell SOA --- In service-orientated- architecture@ yahoogroups. com, Michael Poulin <[EMAIL PROTECTED] .> wrote: > > ...I believe the IT has to get requirements from the latter business > level. To nitpick, I believe the various groups collaborate to define the business requirements. IT shouldn't "get" requirements from others (that's a role of order taker, which is rife with trouble). They work as a team to define the needs that are to be addressed and then they work together to define and develop an approach. IT uses the technical lens while other groups use other focuses. Together they determine the appropriate trade-offs to provide a working system. -Rob
