Abstract:
Implementation of a meta-model service of a service oriented architecture industry model repository into a web ontology language representation of at least one topic map meta-model into a plurality of temporal scope topic map meta-models representing states of the at least one topic map meta-model at different times. The implementation includes assigning topics, occurrences, and attributes from the meta-model service to the at least one topic map meta-model. The topics, occurrences, and attributes are assigned from the at least one topic map meta-model to plurality of temporal scope topic map meta-models. The topics, occurrences, and attributes from the plurality of temporal scope topic map meta-models are converted into resource description framework triples; and the resource description framework triples are persisted into the resource description framework repository.
Abstract:
A method of recognizing and supporting multiple versions of a canonical message model in a service oriented architecture industry model repository comprising determining differences between at least one first version of a message model and at least one other version of the message model; mapping the differences between the different versions of the message models to the SOA IMR; and providing the mapping of the differences between the message models to a message access service, mapping of differences between the message models are applied and updated to the later of the message models to support the versions of the canonical message models seamlessly.
Abstract:
A system for automatically creating a desired software application design. In response to an input to create a desired software application design, functional requirements for the desired software application design are retrieved. Then, non-functional requirements associated with each retrieved functional requirement are retrieved. In addition, software models associated with the retrieved functional requirements are retrieved. Further, software patterns associated with the retrieved non-functional requirements are retrieved. Then, the retrieved software models are transformed into software code for the desired software application design. Also, the retrieved software patterns are applied to associated code sequences in the software code to automatically create an architecture for the desired software application design. Finally, the architecture for the desired software application design is outputted for use by a user. The decisions made during the software application design process are also captured for analysis for future improvement of the desired software application design.
Abstract:
A plurality of topic maps are stored in one or more storage devices. Each of the topic maps represents information using topics, associations, and occurrences. Each of the topic maps provides meta data for assets stored in an asset repository. A computer provides one or more services over a network. At least one of the one or more services enables functionality of one or more user interfaces. The one or more services provide semantic search functionality for the assets of the asset repository. The semantic search functionality utilizes the topics, associations, and occurrences of one or more of the topic maps to find one of more of the assets of the asset repository that satisfies conditions input via one of the one or more user interfaces.
Abstract:
A tag management system for a user of a client-side portal application providing access to a set of services that include provisions for collaborative tagging of content comprises one or more data repositories configured to maintain one or more separate sets of tags, a messaging intermediary configured to provide access to the one or more data repositories and to provide for communication with the set of services, and a client-side agent configured to communicate with the set of services and access the one or more data repositories through the message intermediary to act on instructions provided by the user in one or more user roles. A set of tags corresponds to each service in each user role and specifies an available vocabulary for tagging content at that service. The agent is configured to access the one or more data repositories to load a first set of tags corresponding a user-specified service and a user-specified role, display the first set of tags to the user, and to communicate with the user-specified service to post tags selected by the user from the first set of tags to content at the user-specified service.
Abstract:
Provided is a Web Services Response Template (WSRT) that addresses the problems of efficiency and robustness to change in Web Services response by allowing a requestor to explicitly specify, in a response template what information is to be returned by the request. A requestor of a web service gets just the information it needs; different requestors of the same operation may get different information; and a responder sends the requestor only what is asked for so there is no problem when new information becomes available. WSRTs are specifically designed to allow the type of control needed in program-to-program (P2P) communication, while being very efficiently and simply processed by a web service. Thus, WSRTs address difficulties that arise in typical distributed, P2P communication without adding much overhead or complexity to either a service requestor or a service provider. The efficiency and flexibility afforded by WSRTs is essential to emerging enterprise architectures based on SOA (Service Oriented Architecture).
Abstract:
The present invention discloses a software development tool that includes a model development interface, an aspect design tool, and a model transformation engine. The model development interface can permit a developer to graphically design at least one software model. The aspect design tool for the model development interface can be configured to permit a user to specify at least one aspect to be applied to a model of the model development interface. The model transformation engine can transform a model of the model development interface having at least one aspect defined via the aspect design tool into automatically generated aspect code integrated with base language code.
Abstract:
A method of managing and maintaining scope in a of service oriented architecture industry model repository comprising defining boundaries and definitions of scope and scope propagation of topics, associations, and occurrences within the SOA IMR; managing boundaries and definitions of scope and scope propagation within the SOA IMR; and maintaining boundaries and definitions of scope and scope propagation within the SOA IMR.
Abstract:
In one illustrative embodiment, a computer-implemented method for identifying program components, generates, by a processor unit, associations between the program components stored in a computer usable storage medium to create a first set of relationships, and assigns, by the processor unit, a probability to each relationship in the first set of relationships to create a second set of relationships, wherein the probability indicates a strength of the associations between the program components.
Abstract:
A method, system and program product of managing multiple versions of enterprise meta-models within an enterprise model using semantic based indexing. The steps include: receiving a query; determining from the query a topic and at least two versions of a topic map meta-model of the enterprise meta-models to compare; applying the query to a merged topic map meta-model of the at least two versions of the topic map meta-model by searching a topic map based index of the merged topic map meta-model for the topic, producing a result; and using the result to translate the topic from the query in at least one of the at least two versions of the topic map meta-model to coexist and correspond to the other version of the topic map meta-model, allowing data between the at least two versions topic map meta-model of the enterprise meta-models within the enterprise model to be correlated.