Are your customers not so impressed
with the results of SOA projects and is the reason the projects take too
long.
SOA/BPM came as an alternative for
the only reason that it provides higher developer productivity and business
agility (because for reusability). Is that promise met?
Even today all SOA projects (any
small to medium package or feature) takes somewhere 4 to 6 months. This is
where the WOW effect goes out.
The reasons are well known, recently
a number of discussions on Industrializing SOA (or Factory model for SOA) cover
that, can be found here and here
Like memory leaks, time leaks in the
SOA project. In one we see 'Out of memory' and the other 'Out of budget'. Ask your customers how much
time gets wasted because of these issues not well managed.
- Development Approach
- Agile / Iterative
- Deployment automation
- Maven/Hudson Vs ANT
- Continuous Integration
- Configuration plans
- Dependency between components
- Testing automation
- Regression testing / unit test scripts
- Test coverage
- Way to manage test data sets
- Integration testing
- Error Handling / monitoring
- Version control
- Binary management
- Use of MDS
- Virtualization for dev and test environments
- Automation scripts (devops)
- stubbing out system dependencies
