Governing exposing services in a service model

Patent metadata

Field	Value
Publication number	US-10152692-B2
Application number	US-32702908-A
Country	US
Kind code	B2
Filing date	Dec 3, 2008
Priority date	Dec 3, 2008
Publication date	Dec 11, 2018
Grant date	Dec 11, 2018

Abstract

Methods and systems for governing service identification in an SOA governance model according to embodiments of the present invention are provided. Embodiments include receiving a set of input parameters for identifying candidate services for the SOA; determining whether the set of input parameters comply with a predetermined input parameter validation policy. If the set of input parameters comply with a predetermined input parameter validation policy, governing service identification includes identifying in dependence upon the set of input parameters one or more candidate services available for the SOA in existing SOA business applications and determining whether each candidate services available in existing SOA business applications comply with a predetermined service selection policy. If one of the candidate services available in existing SOA business applications complies with a predetermined service selection policy, governing service identification includes selecting the candidate service as a service available for the SOA and communicating the identification of that selected service to relevant stakeholders in the SOA.

First claim

What is claimed is:

1. A method of governing exposing services in a service model in a Service Oriented Architecture (‘SOA’), the method comprising:
receiving, by one or more modules of automated computing machinery, a list of candidate services available for exposure in an SOA;
selecting, by one or more modules of automated computing machinery, a service;
determining, by one or more modules of automated computing machinery, whether the service meets predetermined service architecture criteria, including:
determining whether aspects of the service comply with predetermined service specification requirements;
determining whether available subsystem components upon which the service will be deployed comply with predetermined subsystem requirements, wherein the predetermined subsystem requirements establish requirements of the subsystem of computing hardware and software upon which the service is deployed, wherein the service does not meet predetermined service architecture criteria if the subsystem components upon which the service will be deployed do not comply with the predetermined subsystem requirements;
determining whether required subcomponents of the service comply with service subcomponent requirements; and
determining whether the service complies with requirements for pre-condition service dependencies identifying another service that must properly execute before the service can begin executing;
determining whether the service complies with requirements for postcondition service dependencies identifying another service that must be invoked after the completion of the service;

if the service meets predetermined service architecture criteria, exposing the service including, by one or more modules of automated computing machinery, the service in the SOA and documenting the service in a service model for the SOA;
if the service does not meet predetermined service architecture criteria, determining, by a business member or business consult, whether the service is exempt from the predetermined service architecture criteria, including determining whether the service is exempt from predetermined service specification requirements, predetermined subsystem requirements, or predetermined subcomponent requirements;
if the service is exempt from predetermined service architecture criteria, including, by one or more modules of automated computing machinery, the service in the SOA and documenting the service in a service model for the SOA;
excluding the service from the SOA if the service is not exempt from predetermined service architecture criteria; and
in response to including one or more services in the SOA, communicating, via a computer network, the service model to relevant stakeholders.

2. The method of claim 1 wherein determining whether aspects of the service comply with predetermined service specification requirements further comprises determining whether the service complies with requirements for service dependencies, service composition and flow, non-functional aspects of the service, service message specifications, and the state of documents.

3. The method of claim 1 wherein determining whether available subsystem components upon which the service will be deployed comply with predetermined subsystem requirements further comprises determining whether the subsystem components comply with requirements for subsystem dependencies, service components, functional components, and technical components.

4. The method of claim 1 wherein determining whether required subcomponents of the service comply with service subcomponent requirements further comprises determining whether the required subcomponents comply with requirements for service component attributes, service component flow, service events, service messages, service component class diagrams, and service design.

5. A system of governing exposing services in a service model in a Service Oriented Architecture (SOX), the system comprising a computer processor, a computer memory operatively coupled to the computer processor, the computer memory having disposed within it computer program instructions that, when executed by the computer processor, cause the system to carry out the steps of:
receiving a list of candidate services available for exposure in an SOA;
selecting a service;
determining whether the service meets predetermined service architecture criteria including:
determining whether aspects of the service comply with predetermined service specification requirements;
determining whether available subsystem components upon which the service will be deployed comply with predetermined subsystem requirements, wherein the predetermined subsystem requirements establish requirements of the subsystem of computing hardware and software upon which the service is deployed, wherein the service does not meet predetermined service architecture criteria if the subsystem components upon which the service will be deployed do not comply with the predetermined subsystem requirements;
determining whether required subcomponents of the service comply with service subcomponent requirements; and
determining whether the service complies with requirements for pre-condition service dependencies identifying another service that must properly execute before the service can begin executing;
determining whether the service complies with requirements for postcondition service dependencies identifying another service that must be invoked after the completion of the service;

if the service meets predetermined service architecture criteria, exposing the service including the service in the SOA and documenting the service in a service model for the SOA if the service meets predetermined service architecture criteria;
in response to a determination, by a business member or business consultant, that the service does not meet predetermined service architecture criteria and is exempt from the predetermined service architecture criteria including predetermined service specification requirements, predetermined subsystem requirements, or predetermined subcomponent requirements including the service in the SOA and documenting the service in a service model for the SOA;
excluding the service from the SOA if the service is not exempt from predetermined service architecture criteria; and
in response to including one or more services in the SOA, communicating, via a computer network, the service model to relevant stakeholders.

6. The system of claim 5 wherein determining whether aspects of the service comply with predetermined service specification requirements further comprises determining whether the service complies with requirements for service dependencies, service composition and flow, non-functional aspects of the service, service message specifications, and the state of documents.

7. The system of claim 5 wherein determining whether available subsystem components upon which the service will be deployed comply with predetermined subsystem requirements further comprises determining whether the subsystem components comply with requirements for subsystem dependencies, service components, functional components, and technical components.

8. The system of claim 5 wherein determining whether required subcomponents of the service comply with service subcomponent requirements further comprises determining whether the required subcomponents comply with requirements for service component attributes, service component flow, service events, service messages, service component class diagrams, and service design.

Assignees

• Brown William A
• Holley Kerrie L
• Moore Garrison A
• Tegan William J
• IBM

Inventors

• Brown William A
• Holley Kerrie L
• Moore Garrison A
• Tegan William J

Classifications

• G06Q10/063

  Operations research, analysis or management · CPC title

• G06Q10/10 Primary

  Office automation; Time management · CPC title