International Business Machines Corporation

Kerard R Hogg

Gandhi Sivakumar

Faried Abrahams

Kent R Ramchand

Ahamed Jalaldeen

Vijayaganesh Subramanian

Sandeep R Patil

Ali P Arsanjani

Siddharth N Purohit

Abhinay Ravinder Nagpal

Ram Viswanathan

Manisha K Sharma

A method and associated system for generating a service specification of a solution. Each process of at least one process is decomposed into at least one atomic service process. The service specification of the solution to be compatible with both a process model framework that includes the at least one process and a data model framework that includes at least one data element that is indirectly matched to the at least one process. The service specification represents a respective process interface of each atomic service process that performs a respective atomic service in the solution. The customized service specification is stored in a database.

Generation of service specification of a solution

A metrics based design method and system is disclosed. The method includes receiving by a computer processor, an informational model comprising data objects, attributes, and relationships associated with a service. The data objects comprise sub-objects. The computer processor receives business affinity (BA) band data associated with the data objects, threshold levels associated with the business affinity (BA) band data, business affinity (BA) levels associated with the business affinity (BA) band data, and service interface operation parameters. The computer processor computes a business affinity (BA) for the informational model based on the business affinity (BA) band data, the threshold levels, the business affinity (BA) levels, and the service interface operation parameters. The computer processor computes a data variation percentage and a reusability count. The computer processor performs: a nested level computation for service valency, a factorization process for computing service valency, and a data element count.

Metrics based design method and system

A method and associated system for generating a service specification of a Service Oriented Architecture (SOA) solution. Each process of at least one process is decomposed into at least one atomic service process. The service specification of the SOA solution to be compatible with both a process model framework that includes the at least one process and a data model framework that includes at least one data element that is indirectly matched to the at least one process. The service specification represents a respective process interface of each atomic service process that performs a respective atomic service in the SOA solution. The customized service specification is stored in a database.

Generation of service specification of a service oriented architecture (SOA) solution

A system and associated method for automatically generating a service specification of a Service Oriented Architecture (SOA) solution. A process model framework and a data model framework are received as inputs. Processes in the process model framework perform services of various complexity levels. Processes are decomposed into a respective set of atomic service processes in the lowest complexity level and data objects are extracted from the decomposed atomic service processes. The data objects are associated with data elements of the data model framework. The data model framework is extended and flexibility patterns are added for reusability of the service specification. The service specification of the SOA solution is generated as process interfaces represented with the data objects according to inputs from a user customizing aspects of the service specification, for either a desired service of the SOA solution or a desired process in the process model framework.

A method and system for specifying a reusable process model. Sub-processes of a base process are identified as having a potential to be modified. By filling in values in a configurable pattern applied to each identified sub-process, dynamic categories are mapped to the identified sub-processes, thereby allowing the sub-processes to be reusable. A change to business requirements occurs, where the base process is based on the business requirements. Based on the change to the business requirements, a change to the values in the configurable pattern applied to a sub-process is received. The change to the values in the configurable pattern does not require a change to the base process.

Specifying reusable process models

An approach that provides routing a SIP message to a proxy server of a called party in a communication network is provided. In one embodiment, there is a routing tool that assists in routing a session initiation protocol (SIP) message to a called party. The routing tool, including a receiving component, receives a SIP message of a user making a call in the network. The routing tool further includes a parsing component configured to parse the message to determine the domain of the called party and performs a table lookup using the domain of the called party in order to: retrieve a destination code; embed the destination code into the message; and route the message based on the destination code.

Routing a session initiation protocol (SIP) message in a communication system

Computer-implemented methods, computer program products and computer systems that assess business logic architecture compliance by defining an ideal business logic architecture hierarchy of a desired application, retrieving one or more applications from a data repository, breaking down these applications into a plurality of processes and analyzing the plurality of processes for common inter-application processes. Common inter-application processes are located and store in the middleware layer. The desired application is developed using the applications and common inter-application processes from the middleware layer to provide a resultant application, followed by determining an actual business logic hierarchal structure of the resultant application. This actual business logic hierarchal structure of the resultant application is compared against the ideal business logic architecture hierarchy to calculate compliance thereof, which in turn, reflects the maturity level of the developed resultant application.

Method and apparatus for assessing layered architecture principles compliance for business analytics in traditional and SOA based environments

A method and system for specifying a data occurrence in a service-oriented architecture based environment. After a service specification phase of a service, a service interface is received and a service implementation is created. During a service realization phase, a data element of the service is determined to be sourced or not sourced by the service implementation. If the data element is sourced, then the data element is determined to be optional. If the data element is not sourced, then the data element is determined to be mandatory. The data occurrence including an indication of whether the data element is optional or mandatory is displayed. The service specification phase is repeated and the service interface is modified based on the displayed data occurrence.

Specifying data occurrence in SOA based environments

An approach is presented for specifying categories of data elements during a service specification phase of a service-oriented architecture (SOA) life cycle defined in a service modeling methodology like Service-Oriented Modeling and Architecture (SOMA). A Unified Modeling Language based SOA modeling tool for the service modeling methodology includes a middleware based integration plug-in that categorizes service-specific data elements as transaction elements, glue elements, core Common Information Model (CIM) elements, and elements extending the CIM elements, and associates the categorized data elements with corresponding operations of the service being modeled.

Data element categorization in a service-oriented architecture

Generating service specification of a service oriented architecture (SOA) solution

A method and system for specifying categories of data elements during a service specification phase of a service-oriented architecture (SOA) life cycle defined in a service modeling methodology like Service-Oriented Modeling and Architecture (SOMA). A Unified Modeling Language based SOA modeling tool for SOMA methodology includes a middleware based integration plug-in that categorizes retrieved service-specific data elements as transaction elements, optional controller elements, glue elements, optional extension patterns, extension elements and core Common Information Model entities, and associates the categorized data elements with corresponding operations of the service being modeled. A user interface provided by the plug-in enables input of the data elements into the categories and input of the associations between the categorized data elements and corresponding operations of the service being modeled. Furthermore, the plug-in generates and initiates storing of a service specification based on the categorization of the data elements.

Growing community of inventors

Riddells Creek, Australia

Kerard R Hogg