Abstract: A method, a system and a program product provide for defining for an information technology (IT) system that may be modeled within the context of a plurality of architecture viewpoints, and whose model elements are defined within a configuration file, a plurality of architecture viewpoints within a single UML model. The method, the system and the program product also provide for synchronously automatically updating a remainder of the architecture viewpoints when one of the architecture viewpoints is manually updated.

Abstract: A method, a system and a program product provide for defining for an information technology (IT) system that may be modeled within the context of a plurality of architecture viewpoints, and whose model elements are defined within a configuration file, a plurality of architecture viewpoints within a single UML model. The method, the system and the program product also provide for synchronously automatically updating a remainder of the architecture viewpoints when one of the architecture viewpoints is manually updated.

Abstract: Detection of heap dump occurrence is facilitated through maintenance of a heap dump location registry. The heap dump location registry indicates tools for which heap dump occurrence is to be detected. Based on periodically referencing the heap dump location registry, it is determined whether heap dump of a tool of the one or more tools has occurred. In one embodiment, startup and shutdown events of the tool are tracked to update execution status and process identifiers in the heap dump location registry, and the periodically references determines based on the indicators whether heap dump has occurred for the tool. In another embodiment, a heap dump location for heap dumps of the tool is obtained from the registry and the heap dump location is checked for the presence of heap dump files, which presence indicates occurrence of a heap dump for the tool.

Abstract: A Simple Network Management Protocol (SNMP)-based apparatus including an SNMP manager to monitor network hardware devices and define object identifiers (OIDs); a Simple SOA Performance Monitor (SSPM) manager to augment the OIDs with service-specific object identifiers to monitor services; and an SSPM agent associated with at least one service to collect details pertaining to the service, the details of the service being provided to the SSPM manager which in turn provides the details of the service to the SNMP manager. The SNMP-based apparatus may be implemented by at least one computing device. Also disclosed is a method of monitoring services and a computer program product.

Abstract: A traceability link establishing method and system. The method includes retrieving by a computing system, mapping data comprising data associating elements of a source model to elements of a target model. The computing system retrieves the target model and elements of the target model. The computing system processes an element of the elements. The computing system retrieves first traceability links from the element. The computing system processes the traceability links. The computing system retrieves supplier data associated with the traceability links. The supplier data comprises data associated with a first supplier. The computing system verifies if the supplier comprises a valid supplier. The computing system stores results of the verifying process. The results indicate if the supplier comprises a valid supplier.

Abstract: Techniques are provided for service-oriented (SOA) process decomposition and service modeling. In one aspect of the invention, the techniques include identifying meta-data entities, attributes of the meta-data entities and relationships between stereotypes of the meta-data model, managing the meta-data model for creating, modifying and removing modeling artifacts, and creating modeling templates from the meta-data model to facilitate addressing at least one need of industry-specific applications. In another aspect the invention, the techniques include packaging the method for SOA process decomposition and service modeling, facilitating lifecycle management of modeling assets, and facilitating maintenance of the modeling assets.

Abstract: Seamless transition from a Component Business Model (CBM) to a Services Oriented Architecture (SOA) is achieved by converting a tabular representation of a CBM Heat Map to a Unified Modeling Language (UML) representation, and automatically converting the UML representation of a CBM Heat Map to a first iteration of input used during the subsequent SOA solution development using Service Oriented Modeling and Architecture (SOMA).

Abstract: A method and system for migrating a UML model across UML profiles. After retrieving a UML model, a source UML element, a source UML profile, a source stereotype, and a source meta-class, the target UML profile, stereotype and meta-class are looked up in a mapping table based on the source UML profile, stereotype, and meta-class. The target UML profile is applied on the UML model. Based on the source meta-class being different from the target meta-class, relationships of the source UML element are retrieved, a target UML element is created, the relationships are copied to the target UML element, and the source UML element is removed from the UML model. The target stereotype is applied to the target UML element. The source stereotype is removed from the target UML element. The source UML profile is removed from the UML model.

Abstract: Model element characteristic preservation is provided when instantiating unified modeling language elements of a unified modeling language model. Requirements management tool elements become associated with a stereotype via, for instance, user assignment of the stereotype to a requirements type of the requirements management project. A stereotype assignment is obtained for a requirements management tool element, and the stereotype is automatically applied when instantiating a UML element representative of the requirements management tool element. Nesting and traceability relationships between the requirements management tool element and other requirements management tool elements are additionally preserved.

Abstract: Seamless transition from a Component Business Model (CBM) to a Services Oriented Architecture (SOA) is achieved by converting a tabular representation of a CBM Heat Map to a Unified Modeling Language (UML) representation, and automatically converting the UML representation of a CBM Heat Map to a first iteration of input used during the subsequent SOA solution development using Service Oriented Modeling and Architecture (SOMA).

Abstract: A method and system for defining an interface of a service in a service-oriented architecture environment. Definitions of atomic tasks of a request or response operation included in a service are received. Unique identifiers corresponding to the atomic tasks are assigned. A sequence map required to implement the service is received. The sequence map is populated with a sequence of the assigned unique identifiers corresponding to a sequence of the atomic tasks of the operation. At runtime, an interface of the service is automatically and dynamically generated to define the service by reading the sequence of unique identifiers in the populated sequence map and assembling the sequence of the atomic tasks based on the read sequence of unique identifiers.

Abstract: A Simple Network Management Protocol (SNMP)-based apparatus including an SNMP manager to monitor network hardware devices and define object identifiers (OIDs); a Simple SOA Performance Monitor (SSPM) manager to augment the OIDs with service-specific object identifiers to monitor services; and an SSPM agent associated with at least one service to collect details pertaining to the service, the details of the service being provided to the SSPM manager which in turn provides the details of the service to the SNMP manager. The SNMP-based apparatus may be implemented by at least one computing device. Also disclosed is a method of monitoring services and a computer program product.

Abstract: Detection of heap dump occurrence is facilitated through maintenance of a heap dump location registry. The heap dump location registry indicates tools for which heap dump occurrence is to be detected. Based on periodically referencing the heap dump location registry, it is determined whether heap dump of a tool of the one or more tools has occurred. In one embodiment, startup and shutdown events of the tool are tracked to update execution status and process identifiers in the heap dump location registry, and the periodically references determines based on the indicators whether heap dump has occurred for the tool. In another embodiment, a heap dump location for heap dumps of the tool is obtained from the registry and the heap dump location is checked for the presence of heap dump files, which presence indicates occurrence of a heap dump for the tool.

Abstract: A method, a system and a program product provide for defining for an information technology (IT) system that may be modeled within the context of a plurality of architecture viewpoints, and whose model elements are defined within a configuration file, a plurality of architecture viewpoints within a single UML model. The method, the system and the program product also provide for synchronously automatically updating a remainder of the architecture viewpoints when one of the architecture viewpoints is manually updated.

Abstract: 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.

Abstract: A cross-functional area service identification method and system. The method includes reading by a computing system, processes. The computing system processes process elements associated with the processes. The computing system identifies a first functional area associated with a first current process element of the process elements and a second functional area associated with a first parent process element of the first current process element. The computing system compares the first functional area to the second functional area and determines if the first functional area comprises a same functional area as the second functional area. The computing system generates and stores results indicating if the first functional area comprises a same functional area as the second functional area.

Abstract: A method for creation of an operational model from a service oriented architecture (SOA) solution architecture. The method includes: selecting an SOA solution architecture model from a plurality of SOA solution architecture models including a plurality of layers; retrieving at least one layer according to the SOA solution architecture model; retrieving at least one SOA model element corresponding to the at least one layer; searching for an operational model element type for the at least one SOA model element and reading the operational model element type; reading a technical environment including hardware, operating system and software product requirements for the operational model element type; creating an operational model element with the technical environment hardware, operating system and software product requirements; and generating an operational model including the specific hardware and software infrastructure required to deploy the SOA solution architecture solution.

Abstract: A method and system for defining an interface of a service in a service-oriented architecture environment. Definitions of atomic tasks of a request or response operation included in a service are received. Unique identifiers corresponding to the atomic tasks are assigned. A sequence map required to implement the service is received. The sequence map is populated with a sequence of the assigned unique identifiers corresponding to a sequence of the atomic tasks of the operation. At runtime, an interface of the service is automatically and dynamically generated to define the service by reading the sequence of unique identifiers in the populated sequence map and assembling the sequence of the atomic tasks based on the read sequence of unique identifiers.

Abstract: 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.

Abstract: A service re-factoring method and system. The method includes selecting by a computing system, a first service comprising a first name. The computing system receives a second name for a second service to be generated from the first service. The computing system executes a service refactoring software application, adjusts a granularity of the first service, and generates the second service. The computing system retrieves first traceability links associated with the first service and a first value associated with a first service identification technique. The first traceability links are created within the second service. The computing system generates a second value associated with a second service identification technique. The first service, the first name, and the first value are removed from the computing system. The computing system stores the second service, the second name, the second value, and the first traceability link.