--- In [email protected], "Nibeck, Mike" <[EMAIL PROTECTED]> wrote: > > The idea of being business driven is almost non existent anymore.
I agree, at least in part. A part of the reason is possibly this: business "requirements" rarely are. Instead, business requirements documents are usually full of technical decisions and solutions. Screen shots. File format layouts. Screen flow wire diagrams. All great tools. None are geared towards defining business requirements. But perhaps its just a naming issue. It seems perfectly reasonable for folks in groups other than IT to specify functional solutions/approaches in many cases. e.g. "We need a field to capture XYZ on screen ABC." While there is a business level need lurking behind that, it's a specific technical solution, not a business requirement. For many things, this level of specification is fine. For other things, it can lead to tunnel vision. Getting funding for an "SOA project" is similar to the above problem. It assumes an approach before understanding the needs. It assumes the approach is *the* important part. -Rob
