Re-establishing traceability method and system

[0001] The present invention relates to a method and associated system for re-establishing traceability between unified modeling language (UML) models.

[0002] Repairing various components of a software system typically comprises an inefficient process with little flexibility. Accordingly, there exists a need in the art to overcome at least some of the deficiencies and limitations described herein above.

[0003] The present invention provides a method comprising:

[0004] retrieving, by a computing system, a transformation mapping file comprising mapping data, wherein said mapping data comprises data associating elements of a source model to elements of a target model;

[0005] retrieving, by said computing system, said target model;

[0006] retrieving, by said computing system, first elements of said target model;

[0007] processing, by said computing system, a first element of said first elements;

[0008] retrieving, by said computing system, first traceability links from said first element, wherein said first traceability links are associated with said first element;

[0009] processing, by said computing system, said first traceability links;

[0010] retrieving, by said computing system, first supplier data associated with said first traceability links, wherein said first supplier data comprises data associated with a first supplier;

[0011] first verifying, by said computing system, if said first supplier comprises a valid supplier; and

[0012] storing, by said computing system, results of said first verifying, wherein said results of said first verifying indicates if said first supplier comprises a valid supplier.

[0013] The present invention provides a computing system comprising a processor coupled to a computer-readable memory unit, said memory unit comprising instructions that when executed by the processor implements a traceability link re-establishing method, said method comprising:

[0014] retrieving, by said computing system, a transformation mapping file comprising mapping data, wherein said mapping data comprises data associating elements of a source model to elements of a target model;

[0015] retrieving, by said computing system, said target model;

[0016] retrieving, by said computing system, first elements of said target model;

[0017] processing, by said computing system, a first element of said first elements;

[0018] retrieving, by said computing system, first traceability links from said first element, wherein said first traceability links are associated with said first element;

[0019] processing, by said computing system, said first traceability links;

[0020] retrieving, by said computing system, first supplier data associated with said first traceability links, wherein said first supplier data comprises data associated with a first supplier;

[0021] first verifying, by said computing system, if said first supplier comprises a valid supplier; and

[0022] storing, by said computing system, results of said first verifying, wherein said results of said first verifying indicates if said first supplier comprises a valid supplier.

[0023] The present invention provides a computer program product, comprising a computer readable medium comprising a computer readable program code embodied therein, said computer readable program code adapted to implement a traceability link re-establishing method within a computing system comprising a computer-readable memory unit, said method comprising:

[0024] retrieving, by said computing system, a transformation mapping file comprising mapping data, wherein said mapping data comprises data associating elements of a source model to elements of a target model;

[0025] retrieving, by said computing system, said target model;

[0026] retrieving, by said computing system, first elements of said target model;

[0027] processing, by said computing system, a first element of said first elements;

[0028] retrieving, by said computing system, first traceability links from said first element, wherein said first traceability links are associated with said first element;

[0029] processing, by said computing system, said first traceability links;

[0030] retrieving, by said computing system, first supplier data associated with said first traceability links, wherein said first supplier data comprises data associated with a first supplier;

[0031] first verifying, by said computing system, if said first supplier comprises a valid supplier; and

[0032] storing, by said computing system, results of said first verifying, wherein said results of said first verifying indicates if said first supplier comprises a valid supplier.

[0033] The present invention advantageously provides a simple method and associated system capable of repairing various components of a software system.

[0041] FIG. 1 illustrates a system 5 for re-establishing traceability links between unified modeling language (UML) models, in accordance with embodiments of the present invention. Traceability links provide relationships between elements of UML models. UML is a standardized general-purpose modeling language in the field of software engineering. UML includes a set of graphical notation techniques to create abstract models of specific systems (i.e., referred to as a UML model). System 5 performs the following functions:

• [0042] 1. Re-establishing traceability links between UML models.
• [0043] 2. Identifying broken traceability links between UML models.
• [0044] 3. Restoring the traceability links between UML models.
• [0045] 4. Implementation of functions 1-3 in UML based modeling tools.

[0046] System 5 of FIG. 1 comprises a computing apparatus 8a connected to a computing system 10 through a network 7. Network 7 may comprise any type of network including, inter alia, a local area network, (LAN), a wide area network (WAN), the Internet, etc. Computing apparatus 8a may comprise any type of computing apparatus including, inter alia, a personal computer, a laptop computer, a computer terminal, etc. Computing apparatus 8a may comprise a single computing apparatus or a plurality of computing apparatuses. Computing apparatus 8a is used by end users for communicating with (e.g., entering data) computing system 10. Computing system 10 may comprise any type of computing system(s) including, inter alia, a personal computer (PC), a server computer, a database computer, etc. Computing system 10 is used to retrieve data from computing apparatus 8a for re-establishing traceability links between UML models. Computing system 10 comprises a memory system 14. Memory system 14 may comprise a single memory system. Alternatively, memory system 14 may comprise a plurality of memory systems. Memory system 14 comprises a software application 18 and a database 12. Database 12 comprises all retrieved data (i.e., retrieved from computing apparatus 8a such as, inter alia, traceability links between UML models, mapping files, supplier data, etc) and any generated data (e.g., UML models, etc).

[0047] Software application 18 performs the following functions associated with an automated process for re-establishing traceability links between UML models:

• [0048] 1. Software application 18 loads a transformation mapping file from a current service oriented architecture (SOA) project. SOA comprises enterprise scale IT architecture for providing IT agility to support business agility.
• [0049] 2. Software application 18 retrieves model elements from a UML target model.
• [0050] 3. Software application 18 processes every model element in the target model.
• [0051] 4. Software application 18 retrieves all traceability links from a model element.
• [0052] 5. Software application 18 processes every traceability link retrieved from the model element.
• [0053] 6. Software application 18 retrieves a supplier associated with the traceability link.
• [0054] 7. Software application 18 verifies the existence of the supplier.
• [0055] 9. Software application 18 removes the traceability link if the supplier is not found.
• [0056] 10. Software application 18 (i.e., for a current model element of the target model) retrieves a corresponding model element of a source model from a transformation mapping file.
• [0057] 11. Software application 18 creates a traceability link from a target model element to a corresponding source model element.

[0058] The following steps illustrate an implementation example for re-establishing traceability links between unified modeling language (UML) models:

• [0059] 1. An architect (i.e. software architect) configures and invokes a model to model transformation. A model to model transformation comprises a process for converting one model to another model of a same system.
  • [0060] A. A CBM to SOA transformation may be used.
  • [0061] B. A UML model with a CBM model stereotype is used as source model for the transformation (as illustrated in FIG. 3).
  • [0062] C. The CBM model comprises the following model elements (as illustrated in FIG. 3).
    • [0063] a. A business competency—“Business Administration”
    • [0064] b. A business component—“Accounts Administration”
    • [0065] c. A business activity—“Account Opening”
  • [0066] D. A UML Model with a service model stereotype may be used as a target model for the transformation.
• [0067] 2. System 5 generates the following model elements in the target model corresponding to model elements of the source model (as illustrated in FIG. 3).
  • [0068] A. A domain—“Business Administration”
  • [0069] B. A functional area—“Accounts Administration”
  • [0070] C. A function—“Account Opening”
• [0071] 3. The architect enhances the target model (as illustrated in FIG. 4).
• [0072] 4. The source model is lost unexpectedly (as illustrated in FIG. 5) as illustrated by the following examples:
  • [0073] A. The file is corrupt.
  • [0074] B. There are version compatibility issues.
  • [0075] B. File deletion by mistake.
• [0076] 6. The architect realizes that the traceability links between the target and source models are lost (as illustrated in FIG. 5).
• [0077] 7. The architect triggers the algorithm of FIG. 2.
• [0078] 8. System 5 retrieves following model elements from the target model.
  • [0079] A. A domain—“Business Administration”
  • [0080] B. A functional area—“Accounts Administration”
  • [0081] C. A function—“Account Opening”
• [0082] 9. System 5 retrieves following traceability links from the model elements:
  • [0083] A. Business administration” between business competency (source model) and domain (target model).
  • [0084] B. “Account Administration” between business component (source model) and functional area (target model).
  • [0085] C. “Account Opening” between business activity (source model) and function (target model).
• [0086] 10. The system verifies an existence of a supplier for the traceability links: “Business Administration”, “Account Administration”, and “Account Opening”.
  • [0087] A. Since the source model was re-generated, it will not find the existence of a supplier (i.e., a null value) for these traceability links.
• [0088] 11. Due to non-existence of a supplier, system 5 removes the traceability links.
• [0089] 12. System 5 identifies the following source model elements from a transformation mapping file.
  • [0090] A. Business competency with a same name of Domain—“Business Administration”.
  • [0091] B. Business component with a same name of functional area—“Accounts Administration”.
  • [0092] C. Business activity with a same name of function—“Account Opening”.
• [0093] 13. System 5 creates a traceability link from the model elements of the target model to corresponding model elements of the source model (as illustrated in FIG. 6).
  • [0094] A. “Business Administration” domain to “Business Administration” business competency.
  • [0095] B. “Accounts Administration” functional area to “Accounts Administration” business component.
  • [0096] C. “Account Opening” function to “Account Opening” business activity.

[0097] FIG. 2 illustrates a flowchart describing an algorithm used by system 5 of FIG. 1 for re-establishing traceability links between unified modeling language (UML) models, in accordance with embodiments of the present invention. In step 200, a computing system (e.g., computing system 5 of FIG. 1) retrieves a transformation mapping file comprising mapping data. The mapping data comprises data associating elements (e.g., elements 305a . . . 305c as described with respect to FIG. 3, infra) of a source model (e.g., service model 302 as described with respect to FIG. 3, infra) to elements (e.g., elements 310a and 310b as described with respect to FIG. 3, infra) of a target model (e.g., target model 304 as described with respect to FIG. 3, infra). In step 202, the computing system retrieves the target model (e.g., from a database). In step 204, the computing system retrieves elements from the target model. In step 208, the computing system processes a first element of the elements. In step 210, the computing system retrieves first traceability links from the first element. The first traceability links are associated with the first element. In step 212, the computing system processes the first traceability links. In step 214, the computing system retrieves first supplier data associated with the first traceability links. The first supplier data comprises data associated with a first supplier. In step 218, processes the first supplier data in order to locate the first supplier. In step 220, the computing system verifies if the first supplier comprises a valid supplier.

[0098] If in step 220, the computing system verifies that the first supplier comprises a valid supplier then in step 223, the computing system determines if additional elements require processing. If in step 223, the computing system determines that additional elements require processing then step 208 is repeated for additional elements. If in step 223, the computing system determines that additional elements do not require processing then in step 238 the associated link (i.e., with the first supplier is stored) and the process is terminated.

[0099] If in step 220, the computing system verifies that the first supplier does not comprise a valid supplier then in step 224, the computing system removes the first traceability links. In step 228, the computing system identifies a second element of the elements that is associated with a source element of source elements from the source model. The identification process is based on the mapping data. In step 232, the computing system creates a second traceability link between the second element and the source element. In step 238, the second traceability link is stored and step 208 is repeated for additional elements.

[0100] FIG. 3 illustrates a source (CBM) model 302 and a target model 304, in accordance with embodiments of the present invention. Source model 302 comprises elements 305a . . . 305c and target model 304 comprises elements 310a and 310b.

[0101] FIG. 4 illustrates an enhance target model process 400, in accordance with embodiments of the present invention.

[0102] FIG. 5 illustrates a regenerated source (CBM) model 502 and a target model 504, in accordance with embodiments of the present invention. Target model 504 comprises broken traceability links 508.

[0103] FIG. 6 illustrates target model 504 of FIG. 5 with re-established traceability links 602, in accordance with embodiments of the present invention.

[0104] FIG. 7 illustrates a computer apparatus 90 (e.g., computing system 10 of FIG. 1) used for re-establishing traceability links between unified modeling language (UML) models, in accordance with embodiments of the present invention. The computer system 90 comprises a processor 91, an input device 92 coupled to the processor 91, an output device 93 coupled to the processor 91, and memory devices 94 and 95 each coupled to the processor 91. The input device 92 may be, inter alia, a keyboard, a software application, a mouse, etc. The output device 93 may be, inter alia, a printer, a plotter, a computer screen, a magnetic tape, a removable hard disk, a floppy disk, a software application, etc. The memory devices 94 and 95 may be, inter alia, a hard disk, a floppy disk, a magnetic tape, an optical storage such as a compact disc (CD) or a digital video disc (DVD), a dynamic random access memory (DRAM), a read-only memory (ROM), etc. The memory device 95 includes a computer code 97. The computer code 97 includes algorithms (e.g., the algorithm of FIG. 2) for re-establishing traceability links between unified modeling language (UML) models. The processor 91 executes the computer code 97. The memory device 94 includes input data 96. The input data 96 includes input required by the computer code 97. The output device 93 displays output from the computer code 97. Either or both memory devices 94 and 95 (or one or more additional memory devices not shown in FIG. 137 may comprise the algorithm of FIG. 2 and may be used as a computer usable medium (or a computer readable medium or a program storage device) having a computer readable program code embodied therein and/or having other data stored therein, wherein the computer readable program code comprises the computer code 97. Generally, a computer program product (or, alternatively, an article of manufacture) of the computer system 90 may comprise said computer usable medium (or said program storage device).

[0105] Still yet, any of the components of the present invention could be created, integrated, hosted, maintained, deployed, managed, serviced, etc. by a service provider who offers to re-establish traceability links between unified modeling language (UML) models. Thus the present invention discloses a process for deploying, creating, integrating, hosting, maintaining, and/or integrating computing infrastructure, comprising integrating computer-readable code into the computer system 90, wherein the code in combination with the computer system 90 is capable of performing a method for re-establishing traceability links between unified modeling language (UML) models. In another embodiment, the invention provides a business method that performs the process steps of the invention on a subscription, advertising, and/or fee basis. That is, a service provider, such as a Solution Integrator, could offer to re-establish traceability links between unified modeling language (UML) models. In this case, the service provider can create, maintain, support, etc. a computer infrastructure that performs the process steps of the invention for one or more customers. In return, the service provider can receive payment from the customer(s) under a subscription and/or fee agreement and/or the service provider can receive payment from the sale of advertising content to one or more third parties.

[0106] While FIG. 7 shows the computer system 90 as a particular configuration of hardware and software, any configuration of hardware and software, as would be known to a person of ordinary skill in the art, may be utilized for the purposes stated supra in conjunction with the particular computer system 90 of FIG. 7. For example, the memory devices 94 and 95 may be portions of a single memory device rather than separate memory devices.

[0107] While embodiments of the present invention have been described herein for purposes of illustration, many modifications and changes will become apparent to those skilled in the art. Accordingly, the appended claims are intended to encompass all such modifications and changes as fall within the true spirit and scope of this invention.