Software architects, developers, and project managers who've worked "in the
trenches" of SOA design and implementation over the last few years have
learned some hard and valuable lessons. Some of these lessons can help you
avoid the serious traps and pitfalls associated with SOA design and
implementation. Most of the gotchas that can run your SOA project into the
ground are issues that can be addressed early in your project and revolve
around proper project management and planning, architecture, and design.
This article offers seven guidelines for keeping your SOA projects on track,
based on lessons learned in past SOA projects. Ignore them and you may find
yourself S.O.L (SOA Outta Luck)!
1. Understand the Requirements and Manage Expectations
Proper requirements analysis techniques aren't unique to SOA, but they should
be mentioned, because this is where you run the... (more)