Managing and maintaining scope in a service oriented architecture industry model repository

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.

Description

BACKGROUND OF THE INVENTION

The present invention relates to meta models, and more specifically to managing and maintaining scope in a service oriented architecture industry model repository.

Enterprises are adopting a model-driven development (MDD) approach to architecting and designing both the business architecture and the supporting IT system and applications. In order to promote the best practices and interoperability between industry participants both product vendors and industry associations are aggressively developing and making available analysis and design frameworks or industry models to support the model-driven development approach. The frameworks are targeted towards vertical industries and tend to be very complex.

For successful adoption of the complex industry models, scoping capability for both strategic and tactical purposes is important. In enterprise wide projects, it is important to provide users project-level model views that match their roles and needs. For example, a project manager may want to clearly view the specific scope of requirement that belong to his/her project while developers may want to view the specific elements of design-level models, such as services or data structures from which they will work, without being burdened with having to sift through the entire model to find those elements.

Typically industry associations are not concerned with specific tooling or usage methods and therefore do not provide any scoping aids. Any scoping that is provided is limited and based on explicit inputs and relationships and does not leverage any level of semantic technologies.

SUMMARY OF THE INVENTION

A method of managing and maintaining scope in a of service oriented architecture industry model repository is provided 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.

The method may further comprise creating a new meta model topic, association, or occurrence and topic, association, or occurrence name for the requirement model; creating a scope topic, association, or occurrence to identify that the new meta model topic, association, or occurrence is in the scope of the meta model; adding the scope topic, association, or occurrence to the topic, association, or occurrence name of the new meta model topic; creating resource description framework triples of the new meta model topic, association, or occurrence; and creating scope dependent uniform resource identifiers from the topic, association, or occurrence name for uniquely identifying the resource description framework triples created.

The scoping may be, but is not limited to inheritance scoping, industry vertical scoping, business scoping, and project scoping.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a computer network in which illustrative embodiments may be implemented.

FIG. 2 is a data processing system in which illustrative embodiments may be implemented.

FIG. 3 shows an overview of an industry model repository (IMR) solution architecture system including a service oriented architecture (SOA) industry model repository (IMR) component.

FIG. 4 shows an overview of a service oriented architecture (SOA) industry model repository (IMR) meta-model with OWL/RDF maps and vertical scoping.

FIG. 5 shows a service model supporting scoping of the SOA IMR.

FIG. 6 shows a message model supporting scoping of the SOA IMR

DETAILED DESCRIPTION OF THE INVENTION

With reference now to the figures, and in particular, with reference to FIGS. 1 and 2, exemplary diagrams of data processing environments are provided in which illustrative embodiments may be implemented. It should be appreciated that FIGS. 1 and 2 are only exemplary and are not intended to assert or imply any limitation with regard to the environments in which different embodiments may be implemented. Many modifications to the depicted environments may be made.

FIG. 1 depicts a pictorial representation of a network of data processing systems in which illustrative embodiments may be implemented. Network data processing system 1 is a network of computers in which the illustrative embodiments may be implemented. Network data processing system 1 contains network 2, which is the medium used to provide communication links between various devices and computers connected together within network data processing system 1. Network 2 may include connections, such as wire, wireless communication links, or fiber optic cables.

In the depicted example, server 4 and server 6 connect to network 2 along with storage unit 8. In addition, clients 10, 12, and 14 connect to network 2. Clients 110, 12, and 14 may be, for example, personal computers or network computers. In the depicted example, server 4 provides information, such as boot files, operating system images, and applications to clients 10, 12, and 14. Clients 10, 12, and 14 are clients to server 4 in this example. Network data processing system 1 may include additional servers, clients, and other devices not shown.

Program code located in network data processing system 1 may be stored on a computer recordable storage medium and downloaded to a data processing system or other device for use. For example, program code may be stored on a computer recordable storage medium on server 4 and downloaded to client 10 over network 2 for use on client 10.

In the depicted example, network data processing system 1 is the Internet with network 2 representing a worldwide collection of networks and gateways that use the Transmission Control Protocol/Internet Protocol (TCP/IP) suite of protocols to communicate with one another. At the heart of the Internet is a backbone of high-speed data communication lines between major nodes or host computers, consisting of thousands of commercial, governmental, educational and other computer systems that route data and messages. Of course, network data processing system 1 also may be implemented as a number of different types of networks, such as, for example, an intranet, a local area network (LAN), or a wide area network (WAN). FIG. 1 is intended as an example, and not as an architectural limitation, for the different illustrative embodiments.

With reference now to FIG. 2, a block diagram of a data processing system is shown in which illustrative embodiments may be implemented. Data processing system 20 is an example of a computer, such as server 4 or client 10 in FIG. 1, in which computer usable program code or instructions implementing the processes may be located for the illustrative embodiments. In this illustrative example, data processing system 20 includes communications fabric 22, which provides communications between processor unit 24, memory 26, persistent storage 28, communications unit 30, input/output (I/O) unit 32, and display 34.

Processor unit 24 serves to execute instructions for software that may be loaded into memory 26. Processor unit 24 may be a set of one or more processors, or may be a multi-processor core, depending on the particular implementation. Further, processor unit 24 may be implemented using one or more heterogeneous processor systems in which a main processor is present with secondary processors on a single chip. As another illustrative example, processor unit 24 may be a symmetric multi-processor system containing multiple processors of the same type.

Memory 26 and persistent storage 28 are examples of storage devices 36. A storage device is any piece of hardware that is capable of storing information, such as, for example, without limitation, data, program code in functional form, and/or other suitable information either on a temporary basis and/or a permanent basis. Memory 26, in these examples, may be, for example, a random access memory or any other suitable volatile or non-volatile storage device. Persistent storage 28 may take various forms depending on the particular implementation. For example, persistent storage 28 may contain one or more components or devices. For example, persistent storage 28 may be a hard drive, a flash memory, a rewritable optical disk, a rewritable magnetic tape, or some combination of the above. The media used by persistent storage 28 also may be removable. For example, a removable hard drive may be used for persistent storage 28.

Communications unit 30, in these examples, provides for communications with other data processing systems or devices. In these examples, communications unit 30 is a network interface card. Communications unit 30 may provide communications through the use of either or both physical and wireless communication links.

Input/output unit 32 allows for input and output of data with other devices that may be connected to data processing system 20. For example, input/output unit 32 may provide a connection for user input through a keyboard, a mouse, and/or some other suitable input device. Further, input/output unit 32 may send output to a printer. Display 34 provides a mechanism to display information to a user.

Instructions for the operating system, applications, and/or programs may be located in storage devices 36, which are in communication with processor unit 24 through communications fabric 22. In these illustrative examples the instructions are in a functional form on persistent storage 28. These instructions may be loaded into memory 26 for running by processor unit 24. The processes of the different embodiments may be performed by processor unit 24 using computer implemented instructions, which may be located in a memory, such as memory 26.

These instructions are referred to as program code, computer usable program code, or computer readable program code, that may be read and run by a processor in processor unit 24. The program code in the different embodiments may be embodied on different physical or tangible computer readable media, such as memory 26 or persistent storage 28.

Program code 38 is located in a functional form on computer readable media 40 that is selectively removable and may be loaded onto or transferred to data processing system 20 for running by processor unit 24. Program code 38 and computer readable media 40 form computer program product 42 in these examples. In one example, computer readable media 40 may be in a tangible form, such as, for example, an optical or magnetic disc that is inserted or placed into a drive or other device that is part of persistent storage 28 for transfer onto a storage device, such as a hard drive that is part of persistent storage 28. In a tangible form, computer readable media 40 also may take the form of a persistent storage, such as a hard drive, a thumb drive, or a flash memory that is connected to data processing system 20. The tangible form of computer readable media 40 is also referred to as computer recordable storage media. In some instances, computer readable media 40 may not be removable.

Alternatively, program code 38 may be transferred to data processing system 20 from computer readable media 40 through a communications link to communications unit 30 and/or through a connection to input/output unit 32. The communications link and/or the connection may be physical or wireless in the illustrative examples. The computer readable media also may take the form of non-tangible media, such as communication links or wireless transmissions containing the program code.

In some illustrative embodiments, program code 38 may be downloaded over a network to persistent storage 28 from another device or data processing system for use within data processing system 20. For instance, program code stored in a computer readable storage medium in a server data processing system may be downloaded over a network from the server to data processing system 20. The data processing system providing program code 38 may be a server computer, a client computer, or some other device capable of storing and transmitting program code 38.

The different components illustrated for data processing system 20 are not meant to provide architectural limitations to the manner in which different embodiments may be implemented. The different illustrative embodiments may be implemented in a data processing system including components in addition to, or in place of, those illustrated for data processing system 20. Other components shown in FIG. 2 can be varied from the illustrative examples shown. The different embodiments may be implemented using any hardware device or system capable of executing program code. As one example, the data processing system may include organic components integrated with inorganic components and/or may be comprised entirely of organic components excluding a human being. For example, a storage device may be comprised of an organic semiconductor.

As another example, a storage device in data processing system 20 is any hardware apparatus that may store data. Memory 26, persistent storage 28 and computer readable media 40 are examples of storage devices in a tangible form.

In another example, a bus system may be used to implement communications fabric 22 and may be comprised of one or more buses, such as a system bus or an input/output bus. Of course, the bus system may be implemented using any suitable type of architecture that provides for a transfer of data between different components or devices attached to the bus system. Additionally, a communications unit may include one or more devices used to transmit and receive data, such as a modem or a network adapter. Further, a memory may be, for example, memory 26 or a cache such as found in an interface and memory controller hub that may be present in communications fabric 22.

FIG. 3 shows the IMR architecture system 100 which may be part of the network data processing system 1 shown in FIG. 1 and includes a service oriented architecture (SOA) industry model repository (IMR) component 102. The SOA-IMR component 102 provides tools to facilitate the consumption and reuse of the model assets through topic map IMR meta model creation and topic map interface 104 and semantic web implementation 105 which represent and implement the IMR meta models using semantics provide by the OWL language. The SOA IMR component 102 is discussed in further detail in an application entitled, “SERVICE ORIENTED ARCHITECTURE INDUSTRY MODEL REPOSITORY META-MODEL WITH A STANDARD BASED INDEX” filed concurrently with the present application. This application is hereby incorporated by reference. Block 105 is described in greater detail below.

The IMR architecture system 100 includes federated physical model assets 103 that are stored in different types of repositories depending on the model driven framework tools and products that are being deployed by the system. The federated physical assets may include framework, industry models, business models, UML design applications, data models, business services, service components, and technical services. The federated physical assets are not limited to the assets shown in FIG. 3.

Applications and services 106 are provided to IMR users 108 through the network 109 using interfaces 107. The interfaces used by the IMR users 108 includes reports generation and tools supporting multi-formats and visualization tools supporting complex views. The applications and services 106 may include registration and profile management; creating and customizing repository meta model, importing customized and disparate model/data into the depository, examining/decomposing complex diagrams and structures, structure, link, and trace change disparate model/assets; advanced search and query, navigate/browse data assets; select and download model/assets, customize/add models/assets submit for repository upload; and impact analysis. The application and services are not limited to the assets shown in FIG. 3. The applications and services are described in greater detail in applications entitled “FRAMEWORK TO POPULATE AND MAINTAIN A SERVICE ORIENTED ARCHITECTURE INDUSTRY MODEL”, “IMPLEMENTING SERVICE ORIENTED ARCHITECTURE INDUSTRY MODEL REPOSITORY USING SEMANTIC WEB TECHNOLOGIES”, “RECOGNITION OF AND SUPPORT FOR MULTIPLE VERSIONS OF AN ENTERPRISE CANONICAL MESSAGE MODEL” filed concurrently with the present application. These applications are hereby incorporated by reference. The interfaces 107 are further described in greater detail in an application entitled, “SERVICE ORIENTED ARCHITECTURE INDUSTRY MODEL REPOSITORY META-MODEL WITH A STANDARD BASED INDEX” filed concurrently with the present application and hereby incorporated by reference.

The IMR users 108 may include but are not limited to repository administrator, model manager, system architect, and business analyst.

FIG. 4 shows a service oriented architecture (SOA) industry model repository (IMR) component 102 in greater detail. The SOA IMR component 102 includes a meta model service 202 associated with the physical asset repository. Within the meta model service 202 is a meta-meta-meta model 206 with a topic map based index, an information model repository (IMR) common meta-meta model 208 describing the relationship between the included meta models and at least one topic map meta model 210 with data specific to a particular topic or industry vertical. The topic map meta model 210 is associated with the physical asset repository 204 of model assets which includes but is not limited to model assets (RAM) 212, requirement models 214, and document models (wiki) 216.

The internal meta model service 202 of the SOA IMR component 102 is the SOA IMR meta-model service using ISO Standard topic map meta models 210. Topic maps map both web and real-world information resources, by reifying real-world resources as “subjects”, and creating “topic” constructs to capture their characteristics and relationships with other topics and subjects. By using the topic maps meta models 206, 208, and 210 as the repository internal meta model, a common meta model service interface 202 allows users to programmatically access, manage, and maintain these meta models.

The SOA IMR meta model service 202 maps or implements the ISO topic map meta models 210 to a web ontology language (OWL) representation of the topic map. The industry model repository (IMR) provides the context for the implementation of the ISO topic map meta models 210 to the OWL representation of the topic maps. The OWL representation of the topic map is stored in a resource description framework (RDF) semantic web repository 218. Scoping of the industry vertical or the topic map meta model 210 of the OWL representation of the topic map may occur.

In one embodiment of the present invention extends the service definition for the SOA IMR meta model service component with new fields and services for defining and managing multi-definitions of scope and scope propagation within the model constructs managed by the meta-model scoping service. The meta-model scoping service described below in detail, supports the industry model usage needs and is capable of defining scope and boundaries in the repository topic map meta model 210 and scope propagation through the captured relationships between multiple types of models.

In one embodiment of the present invention manages and maintains scope across boundaries in the industry model repository and can differentiate between different meta-models and artifacts. The scoping may be industry vertical scoping, inheritance scoping, business scoping and project scoping.

Industry vertical scoping identifies scope of Insurance versus Telco within topics (e.g. requirements, model assets), occurrences (e.g. web page or a URL to a RAS asset repository), and associations. In other words, distinguishing the differences in scope between the vertical industries.

Inheritance scoping identifies and scopes topics, occurrences and associations based on artifact inheritance relationships. For example, in Telco topics, identifying security identifier (SID) original artifacts versus a security identifier derived customized artifact.

Business scoping identifies and scopes topics, occurrences and associations based on business function areas, for example marketing versus procurement business scope.

Project scoping identifies and scopes topics, occurrences and associations based on project parameters or requirements.

The scoping may be queried directly from an artifact's explicit or implicit mapping. Explicit mappings occur when associations are created and stored in the industry model repository (IMR) Implicit mapping occur when the associations are derived based on inferences.

The scoping is not limited to the scoping listed above and may include other types of scoping as applicable.

FIG. 5 shows a service model for SOA IMR with a meta-model scoping service. The service model includes a TopicMapService port and interface 300 with operations that include getting TopicMap From Repository, TopicMap, Topics, Associations, and Occurrences, and setting the TopicMap, TopicMap From Repository, Topics, and Associations.

FIG. 6 shows the message model for the SOA IMR with a meta-model scoping service. The messages pertain to TopicMap 420, Topic 422, TopicName 424, Association 428 and AssociationRole 430, Occurrence 432, and Variant 426. As shown in FIG. 4, TopicName 424, Occurrences 432 and Association 428 and AssociationRole 430 can each have scope.

New scope dependent topics may be created on the client side using a programming language such as Java™, a programming language from Sun MicroSystems Inc. For example, a new meta—model topic may be created for the requirements models. The user then creates a scope topic to identify that this topic is in the scope of the meta-model. Then the scope is added to the topic name. A similar approach may be used to create scope dependent associations and occurrences of topics as well.

The topic is created with the appropriate scope by persisting the new topic as a RDF triple. With the scope information defined for the requirement model and the RDF triples, scope dependent uniform resource identifier's (URI's) for uniquely identifying the triples are created. The scope information defined for the requirement model, the RDF triples, and the topic map constructs can also provide namespace data. If a topic cannot be created with a meaningful scope dependent URI, multiple scopes may be necessary and each scope would be added onto the based URI. A similar approach may be used to create scope dependent URI's for associations and occurrences of topics as well.

By using the ISO Standard of topic maps as the meta-meta model, the capability of automated index building is present. All of the topics are represented by index elements and these index elements can be limited by scope. The associations show which other topics a specific topic is related to and the occurrences show where physical assets relating to these topics may be found.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

Any suitable computer usable or computer readable medium may be utilized. The computer-usable or computer-readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a transmission media such as those supporting the Internet or an intranet, or a magnetic storage device. Note that the computer-usable or computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory. In the context of this document, a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer-usable medium may include a propagated data signal with the computer-usable program code embodied therewith, either in baseband or as part of a carrier wave. The computer usable program code may be transmitted using any appropriate medium, including but not limited to the Internet, wireline, optical fiber cable, RF, etc.

Computer program code for carrying out operations of one or more embodiments of the present invention may be written in an object oriented programming language such as Java, Smalltalk, C++ or the like. However, the computer program code for carrying out operations of one or more embodiments of the present invention may also be written in conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

The present invention is described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention for example as shown in FIGS. 1-6. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.

Having thus described the invention of the present application in detail and by reference to embodiments thereof, it will be apparent that modifications and variations are possible without departing from the scope of the invention defined in the appended claims.

Claims

1. A method of managing and maintaining scope in a service oriented architecture (SOA) industry model repository (IMR) comprising a meta model service associated with a physical asset repository including model assets, requirement models, and document models, 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 comprising: a) defining boundaries and definitions of scope and scope propagation of topics, associations, and occurrences within the SOA IMR;b) managing boundaries and definitions of scope and scope propagation within the SOA IMR; andc) maintaining boundaries and definitions of scope and scope propagation within the SOA IMR, wherein the scope is inheritance scoping.

2. The method of claim 1, wherein the method further comprises: creating a new meta model topic, association, or occurrence and topic, association, or occurrence name for the requirement model;creating a scope topic, association, or occurrence to identify that the new meta model topic, association, or occurrence is in the scope of the SOA IMR;adding the scope topic, association, or occurrence to the topic, association, or occurrence name of the new meta model topic;creating resource description framework triples of the new meta model topic, association, or occurrence; andcreating scope dependent uniform resource identifiers from the topic, association, or occurrence name for uniquely identifying the resource description framework triples created.

3. The method of claim 1, wherein defining boundaries and definitions of scope and scope propagation within the SOA IMR further comprises differentiating between different meta models and artifacts within the meta model service of the SOA IMR.

4. The method of claim 1, wherein the scope is industry vertical scoping.

5. The method of claim 1, wherein the scope is business scoping.

6. The method of claim 1, wherein the scope is project scoping.

7. A computer system for a service oriented industry model repository architecture, the system comprising: a CPU, a computer readable memory, a non-transitory computer readable storage media, a plurality of service oriented architecture (SOA) industry model repositories (IMR) comprising a meta model service associated with a physical asset repository including model assets, requirement models, and document models, 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;first program instructions for defining boundaries and definitions of scope and scope propagation of topics, associations, and occurrences within the SOA IMR;second program instructions for managing boundaries and definitions of scope and scope propagation within the SOA IMR; andthird program instructions for maintaining boundaries and definitions of scope and scope propagation within the SOA IMR;the first, second, and third program instructions are stored on the non-transitory computer readable storage media for execution by the CPU via the computer readable memory. wherein the scope is inheritance scoping.

8. The system of claim 7, wherein the system further comprises: fourth program instructions for creating a new meta model topic, association, or occurrence and topic, association, or occurrence name for the requirement model;fifth program instructions for creating a scope topic, association, or occurrence to identify that the new meta model topic, association, or occurrence is in the scope of the SOA IMR;sixth program instructions for adding the scope topic, association, or occurrence to the topic, association, or occurrence name of the new meta model topic;seventh program instructions for creating resource description framework triples of the new meta model topic, association, or occurrence; andeighth program instructions for creating scope dependent uniform resource identifiers from the topic, association, or occurrence name for uniquely identifying the resource description framework triples created;the fourth, fifth, sixth, seventh and eighth program instructions are stored on the non-transitory computer readable storage media for execution by the CPU via the computer readable memory.

9. The system of claim 7, wherein the first program instructions for defining boundaries and definitions of scope and scope propagation within the repository of internal meta model service data further comprises differentiating between different meta models and artifacts within the meta model service of the SOA IMR.

10. The system of claim 7, wherein the scope is industry vertical scoping.

11. The system of claim 7, wherein the scope is business scoping.

12. The system of claim 7, wherein the scope is project scoping.

13. A computer program product for a service oriented industry model repository architecture, the computer program product comprising: a non-transitory computer readable storage media storing a plurality of computer readable memory, a plurality of service oriented architecture (SOA) industry model repositories (IMR) comprising a meta model service associated with a physical asset repository including model assets, requirement models, and document models, 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;first program instructions for defining boundaries and definitions of scope and scope propagation of topics, associations, and occurrences within the SOA IMR;second program instructions for managing boundaries and definitions of scope and scope propagation within the SOA IMR; andthird program instructions for maintaining boundaries and definitions of scope and scope propagation within the SOA IMR;the first, second, and third program instructions are stored on the non-transitory computer readable storage media, wherein the scope is inheritance scoping.

14. The computer program product of claim 13, wherein the computer program product further comprises: fourth program instructions for creating a new meta model topic, association, or occurrence and topic, association, or occurrence name for the requirement model;fifth program instructions for creating a scope topic, association, or occurrence to identify that the new meta model topic, association, or occurrence is in the scope of the SOA IMR;sixth program instructions for adding the scope topic, association, or occurrence to the topic, association, or occurrence name of the new meta model topic;seventh program instructions for creating resource description framework triples of the new meta model topic, association, or occurrence; andeighth program instructions for creating scope dependent uniform resource identifiers from the topic, association, or occurrence name for uniquely identifying the resource description framework triples created;the fourth, fifth, sixth, seventh and eighth program instructions are stored on the non-transitory computer readable storage media for execution by the CPU via the computer readable memory.

15. The computer program product of claim 13, wherein the first program instructions for defining boundaries and definitions of scope and scope propagation within the repository of internal meta model service data further comprises differentiating between different meta models and artifacts within the meta model service of the SOA IMR.

16. The computer program product of claim 13, wherein the scope is industry vertical scoping.

17. The computer program product of claim 13, wherein the scope is business scoping.

18. The computer program product of claim 13, wherein the scope is project scoping.