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 method of searching a service oriented architecture industry model repository comprising a meta model service associated with a physical asset repository, the meta model service comprising: at least one topic map meta model with data specific to a particular topic or industry vertical included within an information model repository common meta-meta model, the information model repository common meta-meta model included within a meta-meta-meta model with a topic map based index. The method comprises: a computer receiving entry of a search term for the service oriented architecture industry model repository; the computer searching the service oriented architecture industry model repository for the search term; and displaying results of the searching of the service oriented architecture industry model repository as a topic map comprising data representing meta model service through a graphical interface.

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: 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 for building a service oriented architecture industry model repository comprising: creating a meta-meta-meta model with a topic map based index; pre-populating the meta-meta-meta model with a topic map based index using the data from the physical asset repository and known relationships between topics, associations, and occurrences in topic maps within the meta model service; pre-populating an information model repository common meta-meta model comprising reusing a taxonomy specific to an industry vertical as a common ontology for the topic map based index; pre-populating the at least one topic map meta model with data specific to a particular topic or industry vertical from the physical asset repository; and pre-populating models of the at least one topic map meta model with data specific to a particular topic or industry vertical from the physical asset repository.

Abstract: A method for implementing topic map meta models of a service oriented architecture (SOA) industry model repository (IMR) comprising a meta model service associated with a physical asset repository. The meta model service includes at least one topic map meta model with data specific to a particular topic or industry vertical included within an information model repository common meta-meta model, and the information model repository common meta-meta model included within a meta-meta-meta model with a topic map based index. The method comprises assigning topics, occurrences and attributes to the at least one topic map meta model with data specific to a particular topic or industry vertical; converting topics of the at least one topic map meta model with data specific to a particular topic or industry vertical into resource description framework triples; and persisting the resource description framework triples into a resource description framework repository.

Abstract: Providing intelligent recommendations of reusable software assets can begin with obtaining semantic topic maps that define semantic relationships between topics. A topic can represent a requirement or a reusable software asset. A semantic topic map can be written in accordance with a semantic framework using a Web ontology language and stored in a semantic Web repository. User-entered search criteria, representing a requirement, a user-selected search results filter, or a reusable software asset, can be received. A set of semantic topic maps can be identified for the user-entered search criteria. A set of inferred data items can be inferred from the set of identified semantic topic maps. The contents of both sets can be aggregated into a results table. A semantic results graph, a pictorial representation of topics and relationships, can be synthesized from the results table. The semantic results graph can be rendered within an associated user interface.

Abstract: An apparatus for automatically analyzing the impact of changing a business requirement on an IT infrastructure of an enterprise. A request is received to perform an analysis of an impact on the enterprise by changing a particular instance of the business requirement. A model repository is queried to determine which IT assets of the enterprise are impacted by changing the particular instance of the business requirement. An impact relevant subset of a topic map is received from the model repository representing the impact on the enterprise by changing the particular instance of the business requirement that includes the particular instance requirement as a root node and only those specific assets impacted by changing the particular instance requirement as connected nodes. Then, the impact relevant subset of the topic map representing the impact on the enterprise by changing the particular instance of the business requirement is outputted on an output device.

Abstract: A method for increasing quality of content provided to a user. Communities of practice a user is associated with are determined based on login data. A corresponding set of tags is retrieved for each of the communities of practice. All corresponding sets of tags are aggregated to define a role for the user. A personal set of tags associated with the user is retrieved. The personal set of tags is added to the aggregate of all corresponding sets of tags to create a new set of tags. A context of the user in the particular task is recorded. The new set of tags is filtered based on the context to create a sub-set of tags. A defined number of tag aware information sources are queried using the sub-set of tags. Content is received from the defined number of tag aware information sources based on the query. The content is outputted.

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.

Abstract: A standard based mapping of industry vertical models to legacy environments to suggest points of enterprise application integration. A representation of a first domain comprising industry model instance data is generated in a standard-based format from an enterprise industry model. A representation in the standard-based format of a second domain comprising legacy data is generated from the legacy environment. A set of inference rules is applied against the representation of enterprise industry model instance data and the representation of legacy data. One or more candidate legacy assets in the representation of legacy data capable of implementing an aspect of the enterprise industry model are identified. The identified one or candidate legacy assets for implementing the aspect of the enterprise industry model are then recommended to a user.

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: 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 requester or a service provider.

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.

Abstract: A method for consistently and dynamically mapping and maintaining a customized method set of tags particular to an extension point page, includes: extending static customized method content to the extension point page by: mapping static customized method content to an extension point page; wherein the extension point page is configured with collaborative content and dynamic content; filtering the dynamic content based on a set of tags associated with the extension point page; synchronizing the extension point page's tags to ensure that the dynamic content rendered in the extension point page has a set of updated tags to retrieve current syndicated content; wherein a method author defines the extension point page in the customized method; and wherein a method user views the extension point page.

Abstract: A method for tagging internet resource identifiers (IR) based on situationally aware software includes: determining a user's role, context, situation, and which uniform IR is currently being viewed by the user; retrieving one or more of: role and situation tags, and predefined vocabulary from a database in response to the determining; creating a community tag list in the event one or more community tags exist in response to the determined IR; providing the community tag list to the user; receiving a user selected community tag from the community tag list; tagging the IR with the user selected community tag; wherein in the event the community tag list has not been created, the IR is tagged with at least one of the retrieved role and situation tags, and the predefined vocabulary; and wherein the tagging is based on at least one of the user's context, role, or situation.

Abstract: A method for role based situation aware software includes: mapping one or more users to one or more communities of practice (CoP); aggregating a series of tags from the one or more CoP to form an initial set of role-based tags; filtering the initial set of role-based tags based on user context elements to form context sensitive user-role tags; querying one or more information services based on the context sensitive user-role tags; aggregating information obtained from querying the one or more information services; and providing the aggregated information to the user as dynamic context related content.

Abstract: A computer implemented method, system and computer program product for managing reusable software assets based on software requirements. A topic map can be expressed utilizing semantic web technology in order to model a relationship between a software requirement and a reusable software asset. The relationship includes the software assets needed to satisfy the software requirement, relationship between the software assets, and the location of the software assets. The semantic web representation can then leverage a standard web based query mechanism to allow meaningful queries to suggest best software assets to be utilized with the software requirement. The semantic web representation can also leverage standard XML (extensible markup language) tooling to provide consistence checking and inferencing of new data.

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.

Abstract: The present invention discloses a system that provides automated guidance for making architectural decisions when designing information services in a service-oriented architecture (SOA). Such a system can include a requirements manager, a reusable asset repository, and an asset advisory tool. The requirements manager can be configured to capture non-functional requirements for information services. The reusable asset repository can be configured to store design assets. The design assets can be stored according to a unique data model that associates each design asset with a non-functional requirement. The asset advisory tool can be configured to determine a list of recommended design assets for a user-selected non-functional requirement and document the architectural decision made from the list of recommended design assets.