to the problem space or the sale will not happen.
A good technology proposal succeeds only if its key dynamics are comprehensively and indelibly conveyed to the strategic technical buyer ... and you have only a few minutes to drive it home. In a SOA solution proposal, these key dynamics consist in its transformations and communications since they translate directly into operational and implementation feasibility and effectiveness.
SOA transformation and communication issues are gnarly and complex! Here are some samples:
- What programs make decisions, and what humans are in the loop?
- What processing will be factored out into reusable chunks, and when?
- How and where will transactions be transformed to common schemas?
- What are the phases for data and process conversion? What will be disrupted?
- How will the business rules of new partners be coordinated with ours?
- How are access controls implemented? Where are the audit points?
- Where are the process dependencies? How do errors and fixes propagate?
The bottom line requirement is that If you sell large SOA solutions or train an audience in complex processes, you must manifest - at the right level of concreteness and abstraction - how YOUR solution will connect to the boundaries of THEIR problem space.
