Creating and approving a document of understanding
This lesson shows you how to use the governance enablement profile to create a document of understanding (DOU), and govern it through its lifecycle, to the Asset Approved state.
What you should be able to do
- Create a new document of understanding (DOU).
- Propose the DOU.
- Approve the DOU scope.
- Propose the DOU specification.
- Approve the DOU specification.
- Submit the DOU for approval.
- Approve the DOU.
Roles participating in this task:
The Development role creates a document of understanding (DOU) and transitions it up to the submit for approval state. | |
The SOA Governance role approves the document of understanding. |
Introduction
Having considered the basic requirements for the new application, the development team must consider whether existing services can be reused. They identify that their new application, Commercial Address Formatter, can reuse an existing service called Address Formatter service, offered by the Common Services group; they therefore create a document of understanding (DOU). A DOU forms the basis for the relationship between a consumer of a service and the provider of that service; in this tutorial, the consumer is the Commercial Address Formatter application, and the service consumed is the Address Formatter service. The creation of the DOU culminates in a consuming service, process or application having an active service level agreement in place with the service provider.
Part 1: Creating a DOU
The service consumer development team has identified the service that the Commercial Address Formatter application must consume, and instigate the consumption process by creating a new DOU.
Part 2: Proposing the DOU scope
The basic details of the DOU have been specified, and it can now be proposed for review.
Part 3: Approving the DOU scope
The owner of the proposed provider service for this DOU approves the consumer's plan to consume the service. By approving this proposal, the service provider is making an operational decision that indicates that, although the resources necessary to meet the service level that the Commercial Address Formatter application requires might not yet be in place, these will be provided when needed.
Part 4: Proposing the DOU specification
A member of the service provider development team proposes the DOU specification to the consumer organization.
Part 5: Approving the DOU specification
The DOU consumer representatives now give the final approval of the DOU that has been proposed between the Commercial Address Formatter and Address Formatter services. By approving this DOU, they are agreeing that the capabilities detailed in the service version specifications will meet the requirements of the Commercial Address Formatter application. Additionally, this confirmation of acceptance of the DOU indicates that they have all the detailed interface, binding and policy information required for them to continue the development of the Commercial Address Formatter application.
Part 6: Submitting the DOU for Approval
Having been approved by all the consumer and provider stakeholders, the DOU is now submitted, by the consumer representatives, to the SOA governance team for approval. This is the final seal of approval from the governance team that the relationship between the consumer and provider can be entered into.
Part 7: Approving the DOU
The SOA governance team review and approve the DOU.
What you did in this lesson
- Created a new DOU.
- Proposed the DOU for review.
- Approved the DOU scope.
- Proposed the DOU specification.
- Approved the DOU specification.
- Submitted the DOU for approval.
- Approved the DOU.