Creating and approving a document of understanding

What you should be able to do

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.

1. If you have security enabled, and have assigned separate user IDs to each of the governance enablement profile roles, as described in Governing an SCA service: the consumer story, log in to the dashboard with the user ID that is assigned to the Development role. Otherwise, go to the next step.
2. In the dashboard, switch to the Development view by selecting it in views list in the title bar. Ensure that the Overview page is selected.
3. Create a new DOU.
   1. Click Actions > Create a Document of Understanding (DOU).
   2. Enter Commercial Address Formatter consumption of Address Formatter in the Name field.
   3. Enter http://requirements.jkhle.com/requirements.jsp&id=7785 in the Requirements Link field. This is a link, fictitious in this case, to the relevant DOU item in JKHL Enterprises' requirements tracking tool. Note that if the requirements are specified in a document rather than in a requirements tracking tool, you add the document as a target of the Artifacts relationship.
4. Define the service consumer.
   1. Click Add Capability Version underneath the Consumer heading.
   2. Enter C in the Name field, select Commercial Address Formatter from the auto-suggest list. The application version is added as a target of the Consumer relationship.
5. Define the service provider.
   1. Click Add Capability Version underneath the Provider heading.
   2. Enter A in the Name field, select Address Formatter from the auto suggest list. The service version is added as a target of the Provider relationship.
   3. Click Finish to save your changes.

Part 2: Proposing the DOU scope

The basic details of the DOU have been specified, and it can now be proposed for review.

• Transition the DOU to the Asset Scope Review state. Select Action > Propose , and note that the new governance state is Asset Scope 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.

• Transition the DOU to the Asset Scope Review state. Select Action > Approve Scope, and note that the new governance state is Asset Scoped.

Part 4: Proposing the DOU specification

A member of the service provider development team proposes the DOU specification to the consumer organization.

• Transition the DOU to the Asset Specification Review state. Select Action > Propose Asset Specification, and note that the new governance state is Asset Specification Review.

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.

• Transition the DOU to the Asset Specified state. Select Action > Approve Asset Specification , and note that the new governance state is Asset Specified.

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.

• Transition the DOU to the Asset Review state. Click Submit Asset for Approval, and note that the new governance state is Asset Review.

Part 7: Approving the DOU

The SOA governance team review and approve the DOU.

1. If you have security enabled, and have assigned separate user IDs to each of the governance enablement profile roles, log in to the dashboard with the user ID that is assigned to the SOA Governance role. Otherwise, go to the next step.
2. In the dashboard, switch to the SOA Governance view by selecting it in the view list in the title bar. Ensure that the Overview page is selected.
3. In the Watch List widget, click Commercial Address Formatter consumption of Address Formatter to display the DOU details.
4. Transition the DOU to the Asset Approved state.
   • In the Detail widget, click Action > Approve Asset, and note that the new governance state is Asset Approved.

What you did in this lesson