Governing Realizing Services In A Service Oriented Architecture

• US 20100138252A1
• Filed: 12/02/2008
• Published: 06/03/2010
• Est. Priority Date: 12/02/2008
• Status: Abandoned Application

• 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.
• Application Number:
  US12/326,412
• Publication Number:
  US 20100138252A1
• Time in Patent Office: Days
• US Class Current: 705/7
• CPC Class Codes: G06Q 10/0631 Resource planning, allocation, distributing or scheduling for enterprises or organisations
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Governing realizing services in a Service Oriented Architecture (‘SOA’) including receiving a preliminary service model and a preliminary SOA service architecture; allocating services in the preliminary service model (704) to service components; allocating service components to service layers in the preliminary SOA service architecture;if the service components and the services allocated to the service components are technically feasible in the layers of the preliminary SOA architecture to which they are allocated, updating the service model; if the updated service model meets predetermined SOA compliance requirements, communicating the SOA compliant updated service model to relevant stakeholders in the SOA.

Claims

1. A method of governing realizing services in a Service Oriented Architecture (‘

SOA’

), the method

receiving a preliminary service model and a preliminary SOA service architecture;

allocating services in the preliminary service model (704) to service components;

allocating service components to service layers in the preliminary SOA service architecture;

determining whether the service components and the services allocated to the service components are technically feasible in the layers of the preliminary SOA architecture to which they are allocated;

if the service components and the services allocated to the service components are technically feasible in the layers of the preliminary SOA architecture to which they are allocated, updating the service model;

determining whether the technically feasible updated service model meets predetermined SOA compliance requirements;

if the updated service model meets predetermined SOA compliance requirements, communicating the SOA compliant updated service model to relevant stakeholders in the SOA.

2. The method of claim 1 further wherein allocating service components to service layers in the preliminary SOA service architecture further comprises:

identifying architectural layers for functional components; and

identifying architectural layers for nonfunctional components.

3. The method of claim 2 further wherein allocating service components to service layers in the preliminary SOA service architecture further comprises defining rules for architectural layer interaction.

4. The method of claim 3 further comprising documenting the rules defining architectural layer interaction.

5. The method of claim 1 wherein determining whether the service components and the services allocated to the service components are technically feasible in the layers of the preliminary SOA architecture to which they are allocated further comprises:

selecting an architectural review board; and

receiving from the architectural review board a feasibility decision.

6. The method of claim 5 wherein receiving from the architectural review board a feasibility decision further comprises receiving a decision that the service components and the services allocated to the service components are not technically feasible in the layers of the preliminary SOA architecture to which they are allocated;

and the method further comprises;

reallocating services in the preliminary service model to service components.

7. The method of claim 5 wherein receiving from the architectural review board a feasibility decision further comprises receiving a decision that the service components and the services allocated to the service components are not technically feasible in the layers of the preliminary SOA architecture to which they are allocated;

and the method further comprises;

reallocating service components to service layers in the preliminary SOA service architecture.

8. The method of claim 5 wherein selecting an architectural review board further comprises selecting at least one solution architect and at least one business architect.

9. The method of claim 1 wherein determining whether the updated service model meets predetermined SOA compliance requirements further comprises determining whether the technically feasible updated service model complies with SOA service ownership rules.

10. The method of claim 1 further comprising reallocating services in the preliminary service model to service components if the updated service model does not meet predetermined SOA compliance requirements.

11. The method of claim 1 further comprising reallocating service components to service layers in the preliminary SOA service architecture if the updated service model does not meet predetermined SOA compliance requirements.

12. A service for governing realizing services in a Service Oriented Architecture (‘

SOA’

), the method

allocating services in the preliminary service model (704) to service components;

allocating service components to service layers in the preliminary SOA service architecture;

if the service components and the services allocated to the service components are technically feasible in the layers of the preliminary SOA architecture to which they are allocated, updating the service model;

if the updated service model meets predetermined SOA compliance requirements, communicating the SOA compliant updated service model to relevant stakeholders in the SOA.

13. A system of governing realizing services in a Service Oriented Architecture (‘

SOA’

), the system

means for receiving a preliminary service model and a preliminary SOA service architecture;

means for allocating services in the preliminary service model (704) to service components;

means for allocating service components to service layers in the preliminary SOA service architecture;

means for determining whether the service components and the services allocated to the service components are technically feasible in the layers of the preliminary SOA architecture to which they are allocated;

means for updating the service model if the service components and the services allocated to the service components are technically feasible in the layers of the preliminary SOA architecture to which they are allocated,

means for determining whether the technically feasible updated service model meets predetermined SOA compliance requirements;

means for communicating the SOA compliant updated service model to relevant stakeholders in the SOA if the updated service model meets predetermined SOA compliance requirements.

14. The system of claim 13 further wherein means for allocating service components to service layers in the preliminary SOA service architecture further comprises:

means for identifying architectural layers for functional components; and

means for identifying architectural layers for nonfunctional components.

15. The system of claim 14 further wherein means for allocating service components to service layers in the preliminary SOA service architecture further comprises means for defining rules for architectural layer interaction.

16. The system of claim 15 further comprising means for documenting the rules defining architectural layer interaction.

17. The system of claim 13 wherein means for determining whether the service components and the services allocated to the service components are technically feasible in the layers of the preliminary SOA architecture to which they are allocated further comprises:

means for selecting an architectural review board; and

means for receiving from the architectural review board a feasibility decision.

18. The system of claim 17 wherein means for selecting an architectural review board further comprises means for selecting at least one solution architect and at least one business architect.