Defining service ownership for a service oriented architecture

• US 8,660,885 B2
• Filed: 08/12/2012
• Issued: 02/25/2014
• Est. Priority Date: 02/04/2008
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Brown, William A., Holley, Kerrie L., Moore, Garrison A., Tegan, William J.
• Primary Examiner(s): Boyce, Andre
• Assistant Examiner(s): JACKSON, ERNEST ADEYEMI
• Application Number:
  US13/572,670
• Publication Number:
  US 20120310710A1
• Time in Patent Office: 562 Days
• Field of Search: 705/7.11, 705/7.27, 705/7.29, 705/7.13, 705/7.37, 705/7.36
• US Class Current: 705/7.37
• CPC Class Codes: G06Q 10/06375 Prediction of business process outcome or impact based on a proposed change
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Defining service ownership for an SOA includes defining, in response to an event requiring a change in service ownership and in dependence upon data describing business functions within a business, a service domain. Embodiments also include reviewing the defined service domain for approval and upon approval of the defined service domain, identifying potential impact upon currently existing service domains caused by implementation of the defined service domain. Embodiments also include identifying a potential owner of the defined service domain in dependence upon a service type of the defined service domain and funding requirements of the service domain and presenting, to relevant stakeholders in the business, the potential owner of the defined service domain for approval. Upon approval of the potential owner of the defined service domain, embodiments include assigning the potential owner of the defined service domain responsibility for managing the defined service domain.

Claims

1. A computer implemented method of defining service ownership for a Service Oriented Architecture (‘

SOA’

), the method carried out in response to an event requiring a change in service ownership, the method comprising;

defining, by the computer, in dependence upon data describing business functions within a business, a service domain, including identifying a structure and scope for the service domain, wherein the structure and scope of the service domain identifies the business and information technology infrastructure used to operate services within the service domain and identifies the set of services included in the service domain;

identifying, by the computer, a potential impact upon currently existing service domains caused by implementation of the defined service domain wherein identifying by the computer potential impact upon currently existing service domains caused by implementation of the defined service domain further comprises;

determining, by the computer, whether implementation of the defined service domain will cause an impact on currently existing service domains; and

in response to determining that implementation of the defined service domain will cause an impact on currently existing service domains;

determining by the computer whether the impact on currently existing service domains is capable of being resolved;

in response to determining that the impact on currently existing service domains is not capable of being resolved, presenting by the computer the impact to a service domain ownership appeals board for appeal; and

receiving by the computer a decision from the service domain ownership appeals board; and

identifying, by the computer, a potential owner of the defined service domain in dependence upon a service type of the defined service domain and funding requirements of the service domain;

presenting, by the computer, the potential owner of the defined service domain for approval; and

determining by the relevant stakeholders whether the potential owner meets ownership criteria;

in response to determining that the potential owner does not meet ownership criteria, identifying, by the computer, one or more alternative potential owners; and

upon approval of the potential owner of the defined service domain, assigning, by the computer, the potential owner of the defined service domain responsibility for managing the defined service domain.

2. The method of claim 1 wherein the event requiring a change in service ownership comprises a decision to create a new service domain.

3. The method of claim 1 wherein the event requiring a change in service ownership comprises a decision to create a new service.

4. The method of claim 1 further comprising:

communicating, by the computer, a description of the implementation of the defined service domain and the approved potential owner of the defined service domain to relevant members of the business.

5. The method of claim 4 wherein communicating by the computer a description of the implementation of the defined service domain and the approved potential owner of the defined service domain to relevant members of the business further comprises:

tailoring, by the computer, for communication in dependence upon classifications of the relevant members of the business, the description of the implementation of the defined service domain and the approved potential owner of the defined service domain.

6. The method of claim 1 further comprising:

gathering, by the computer, metrics describing effectiveness of one or more steps of method of defining service ownership for an SOA; and

modifying, by the computer, in dependence upon the gathered metrics, the method of defining service ownership for an SOA.

7. A system of defining service ownership for a Service Oriented Architecture (‘

SOA’

), the system including a computer processor and computer memory, the computer memory including computer program instructions that, when executed by the computer processor, cause the system to carry out the steps of;

defining, in dependence upon data describing business functions within a business, a service domain, including identifying a structure and scope for the service domain, wherein the structure and scope of the service domain identifies the business and information technology infrastructure used to operate services within the service domain and identifies the set of services included in the service domain;

identifying, by the computer, a potential impact upon currently existing service domains caused by implementation of the defined service domain wherein identifying by the computer potential impact upon currently existing service domains caused by implementation of the defined service domain further comprises;

determining, by the computer, whether implementation of the defined service domain will cause an impact on currently existing service domains; and

in response to determining that implementation of the defined service domain will cause an impact on currently existing service domains;

determining, by the computer, whether the impact on currently existing service domains is capable of being resolved;

in response to determining that the impact on currently existing service domains is not capable of being resolved, presenting, by the computer, the impact to a service domain ownership appeals board for appeal; and

receiving, by the computer, a decision from the service domain ownership appeals board; and

identifying, by the computer, a potential owner of the defined service domain in dependence upon a service type of the defined service domain and funding requirements of the service domain;

presenting the potential owner of the defined service domain for approval;

determining, after presenting the potential owner of the defined service domain for approval, whether the potential owner meets ownership criteria;

in response to determining that the potential owner does not meet ownership criteria, identifying one or more alternative potential owners; and

assigning, upon approval of the potential owner of the defined service domain, the potential owner of the defined service domain responsibility for managing the defined service domain.

8. The system of claim 7 wherein the event requiring a change in service ownership comprises a decision to create a new service domain.

9. The system of claim 7 wherein the event requiring a change in service ownership comprises a decision to create a new service.

10. The system of claim 7 wherein the computer memory includes computer program instructions that, when executed by the computer processor, cause the system to carry out the step of:

communicating a description of the implementation of the defined service domain and the approved potential owner of the defined service domain to relevant members of the business.

11. The system of claim 10 wherein communicating a description of the implementation of the defined service domain and the approved potential owner of the defined service domain to relevant members of the business includes:

tailoring, for communication in dependence upon classifications of the relevant members of the business, the description of the implementation of the defined service domain and the approved potential owner of the defined service domain.

12. The system of claim 7 wherein the computer memory includes computer program instructions that, when executed by the computer processor, cause the system to carry out the steps of:

gathering metrics describing effectiveness of one or more steps of system of defining service ownership for an SOA; and

modifying, in dependence upon the gathered metrics, the system of defining service ownership for an SOA.