Service Oriented Architecture (SOA) Design Checklist

Service Oriented Architecture (SOA) Design Checklist:
- Are the service interfaces using message formats from the canonical model?

- Have initial service contracts been defined between all known service consumers?

- Has the project established service contracts with services being provided by other teams, third-party packages, or external providers?

- Do the service contracts include release schedules for milestone builds that are synchronized with the schedule for service consumer development?

- Have service types been identified for all services, and appropriate service implementation platforms chosen based on those types?

- Have the non-functional requirements of the service been appropriately externalized from the business logic of the service?

- Have all naming conventions for services (for example, URLs, XML namespaces) been followed, both for the production environment and the development environments?

- Is there an appropriate separation between the service interface (XML Schema and/or WSDL definition) and the planned service implementation?

- For Web Services, is the service compliant with the WS-I Basic Profile 1.1?

- Do all service interfaces and/or contracts address exceptions and errors appropriately?

- Are all schemas in web services externally referenced via import?

- Are attributes and child elements used appropriately within XML schemas?

- Have data sensitivity requirements been identified for all data elements involved with message interactions?

- Have transactional requirements been identified for all service operations?

- Have test cases been established for all service operations?

- Are all services free of references to implement specific details?