WO2010020479A1 - Method and system for integrating development tools - Google Patents

Abstract

The invention relates to a method and a system (1) for integrating development tools (T), comprising a server (2) connected through a network (3) to computers (4) on which development tools (T) can be executed, wherein the development tools (T) automatically log in to the server (2), in the process specifying the respective tool class (TK) of the tool when said development tools are executed, and wherein the server (2) provides linking options between modeling elements (ME) of the logged-in development tools (T) of the same or different tool classes (TK).

Description

description

Method and system for integrating development tools

The invention relates to a method and a system for integrating development tools, and in particular the integration of different development tools, which are provided for the joint implementation of a software or a system development process.

When developing systems or processes, various development tools are typically used at different stages of development or at different levels of development to model and implement the systems and processes. Different developers are working on the development of, for example, a technical system or a technical process with different familiar development tools in which the system or the process is modeled using modeling elements or artifacts. Different development tools are used in different, partially overlapping development phases, whereby certain development tools can be used iteratively to concretize or refine the system model. In traditional development environments, the different development tools are not integrated with each other. In particular, connections or links between different modeling elements or artifacts of the various development tools are created manually. This manual implementation of interfaces between development tools is naturally very expensive and error-prone. So far, attempts have been made to facilitate the exchange of modeling elements or artifacts between the development tools by defining standard and exchange formats. However, the effort for manual exporting and importing or for creating links between different modeling elements of different development tools is not reduced. It is therefore an object of the present invention to provide a method and system for integrating development tools that avoids manual swapping of modeling elements between the development tools.

This object is achieved by a method with the features specified in claim 1.

The invention provides a method for integrating development tools with the steps:

^■ Log on development tools to a server by specifying the respective tool class of the development tool; and

^■ Provide linkage options between the server's modeling elements of the registered development tools of the same or different tool classes.

In one embodiment of the method according to the invention, a linking option for establishing a link between modeling elements is activated automatically or manually.

In one embodiment of the method according to the invention, a predetermined connection type of the link is selected.

In one embodiment of the method according to the invention, the linkage produced is unidirectional.

In an alternative embodiment of the method according to the invention, the linkage produced is bidirectional.

In one possible embodiment of the method according to the invention, the development tools are used for a first time Run on a computer automatically logged in to the server.

This makes it easier for a user to use the method according to the invention.

In one possible embodiment of the method according to the invention, the modeling elements are provided with access rights.

This offers the advantage that access to modeling elements of certain types can be blocked or saved.

In a further embodiment of the method according to the invention, the registered development tools and the links produced are stored between modeling elements of these development tools.

This allows a user to restart his development tool after interrupting his activity without data loss.

In one possible embodiment of the method according to the invention, the modeling elements have classes, instances, operations, attributes, associations, nodes and edges.

The invention further provides a system having the features specified in patent claim 9.

The invention provides a system for integrating development tools with a server connected via a network to computers on which development tools can be executed in each case, wherein the development tools automatically log on to a server by specifying their respective tool class and the Server linking options between modeling elements of the registered development ment tools of the same or different tool classes.

In one embodiment of the system according to the invention, the linking options provided can each be activated to produce a link between modeling elements of development tools.

In the following, embodiments of the method according to the invention and the system for integrating development tools according to the invention will be described with reference to the attached figures.

Show it:

Fig. 1 is a block diagram of a possible embodiment of the system according to the invention for the integration of

Development tools;

Figs. 2A, 2B show examples of simple development tools;

3 is a flowchart of a possible embodiment of the method according to the invention for integrating development tools;

4 is a diagram illustrating various methods or tool classes in a class diagram, as can be used in a possible embodiment of the system according to the invention;

5 shows an example of various modeling elements defined by development tools;

6 shows an exemplary embodiment of a tool integration broker, as can be used in an embodiment of the system according to the invention; 7 shows an exemplary embodiment for linking different modeling elements of different development tools via a user interface, as can be used in the system according to the invention.

As can be seen from Fig. 1, the inventive system 1 for integrating development tools in the embodiment shown there on at least one server 2, which is connected via a network 3 with different computers 4-1-4-2. The computers 4-1-4-2 may be computers of different developers or users. On the computers 4-1-4-2 different development tools are executable. These computers 4 are connected to a server 2 via a data network 3, which may be a local or a wide network. In one possible embodiment, the development tools T automatically log on to the server 2 while executing their respective tool class. The server 2 then provides linking options between modeling elements ME of the registered development tools T of identical or different tool classes TK. In one possible embodiment, the development tools T1, T2 log on to the server 2 when first executed on the respective computer 4-1-4-2. One or more development tools T can be executed on each computer 4 of the various users or developers. The development tools T can be any tools or software tools that are used to develop a process or a system, for example a technical software system or an object or a hardware. Examples of such development tools T are, for example, a requirements development tool or a UML (Unified Modeling Language) tool. Examples of requirement development tools are system-re- lated development tools, such as DOORS, ARTiSAN, or Rhapsody, whose modeling elements are ME and artifacts, respectively

Development process with modeling elements ME or artifacts of other development tools, such as a UML development tool to link or link. The Modeling elements ME of the various development tools T have, for example, classes, instances, operations, attributes, associations, nodes or edges.

The server 2 provides linking options between the modeling elements ME of the registered development tools Tl, T2, wherein the development tools T can be development tools of identical or different classes. The linking options provided by the server 2 can then be activated by a user or a developer to establish a link between the modeling elements ME of the different development tools T 1, T 2. In this case, the user can preferably select a predetermined connection type for a desired link. The selected link can be a unidirectional link from a modeling element ME-A of a first development tool T _A to another modeling element ME-B of another development tool T _B or a bidirectional link between the two modeling elements ME of the two development tools T _A , T _B. Selection and activation of a link by a user preferably takes place by means of an input device, for example via a keyboard or a computer mouse. In one possible embodiment, the activation of the linkage is triggered by an event that can be preconfigured by the user.

In one possible embodiment, the different modeling elements ME of the development tools T are each provided with access rights ZR. The modeling elements ME or artefacts can be provided with different visibility definitions or also user interfaces or access rights which the development tools T can communicate to the server 2 or an integration broker executed thereon when you log on.

Figures 2A, 2B show examples of development tools for developing a system. Fig. 2A shows an example of a Requirements development tool, which makes a request to the system to be developed. The simple requirement is: "The system must be able to be switched off in any state."

Fig. 2B shows a corresponding representation by means of a UML development tool. The development system has various states or states Z, wherein there are transitions t between the various states Z in order to move from one state to another state. The UML state graph shown in FIG. 2B shows the behavior of the system to be developed. As can be seen in FIG. 2B, one arrives from an initial state ZO in a transition tθ1 into a state Z1 and from there via a transition tlA into an off state ZA. Since all states Z1, Z2, Z3 have a transition t to the switch-off state ZA, namely the transitions tIA, t2A, t3A, the system represented in FIG. 2B by the development tool UML-Tool satisfies the request made in the request development tool according to FIG. 2A. More specifically, the transitions tlA, t2A, t3A satisfy the request made in the request-development tool. The transitions tlA, t2A, t3A are modeling elements ME of the UML tool. The semantic set shown in FIG. 2A is a modeling element ME of the request tool. With the method and system for integrating development tools T according to the invention, it is possible to generate or generate links or links between different modeling elements ME of different development tools T. For example, a link between the modeling elements ME of the requirements development tool according to FIG. 2A and the various modeling elements ME of the UML tool according to FIG. 2B can be provided in each case, for example between the modeling element ME according to FIG. 2A and the transitions tlA, t2A , t3A of the UML tool.

3 shows a simple flow chart of a possible embodiment of the method according to the invention for integrating tion of development tools T. In a first step Sl different development tools Tl, T2, T3, which are executable on different computers or computers 4, registered via the network 3 at the server 2, indicating a respective tool class TK of the development tool T. In a possible embodiment, this log-on takes place when the respective development tool T is first executed on the respective computer 4 at the server 2.

In a further step S2, the server 2 provides linking options between modeling elements ME of the registered development tools T of the same or different tool classes TK. The modeling elements ME are, for example, classes, instances, operations, attributes, associations, nodes, edges, and the like.

In step S3, one or more of the provided linking options are activated by a user or developer. In this case, the user may preferably first select a connection type which he wishes from a suggested list of connection types. For example, the links may be unidirectional or bidirectional.

4 shows different methods or tool classes TK. Each development tool or development tool T is assigned by the respective manufacturer at least one method or tool class TK. Development tools preferably cover the largest possible subset or subgroup of the respective tool class TK. As can be seen in the example according to FIG. 4, the development tool 3 has different subclasses, namely software development tool, hardware development tool or mechanics development tool. There is also a subclass for other tools. An example of a mechanics development tool is a CAD graphics program. Examples of software development tools include software development tools. definitions, for software module definitions, or for software design.

FIG. 5 shows artifacts or modeling elements ME of different tools T, for example a requirements development tool T1 and a UML development tool T2. The various special development tools or tools that log in the same way to the server 2 or the integration broker running on it, will access the resulting overall meta-model and different ones

Apply methods such as analysis, validation or verification. The registration of the tools or development tools T is preferably carried out dynamically, for example by means of the TCP / IP protocol. The common meta-model represented in FIG. 5 is obtained by calculating the union of all reported modeling elements ME or artifacts of the different development tools T. For example, the request-development tool Tl displays the artifacts or modeling elements ME "request", "feature", "application case" " on. The UML development tool T2 has the modeling elements ME "aggregation", "class", "composition", "attribute", "operation". The union of the modeling elements ME of the different development tools T creates an overall meta-model that can be accessed by the server Z or integration broker with the method class Code Generator or Tracing Analyzer.

FIG. 6 shows an integration broker executed on the server 2. Via plug-and-play connections, for example by means of the TCP / IP protocol, various development tools, for example a requirements development tool T1 and a UML tool T2 can be connected to interfaces or interfaces that serve as docking points , The Tool Integration Broker provides various interfaces or ports. As shown in FIG. 6, in the example shown, a plug-and-play connection is established at Port 2 with the UML development tool T2. The request development tool Tl is over its port A connected to the port 4 or the provided interface 4 of the tool integration broker. A Traceability Analyzer or an analysis development tool for tracking errors is connected to port 3 of the Tool Integration Broker. Such a tracking tool T3 serves, for example, to track whether all requirements or requirements are met or fulfilled.

FIG. 7 shows a user interface module, in which the server 2 offers a user the graphic option for linking or linking provided connection options. A so-called tool integration broker running on the server Z allows a number of development tools T limited by the hardware configuration to log on to the server Z and to offer their respective modeling elements ME or artifacts to all other development tools T for linking. In the embodiment illustrated in FIG. 7, a group of modeling elements ME of a first development tool T _A and a group of modeling elements ME of a further development tool T _B are displayed to the user on a screen via the user interface. It is now possible for the user to establish or activate a link between a modeling element ME-A of the first development tool T _A and a modeling element ME-B of the second development tool T _B. In the embodiment illustrated in FIG. 7, the user also has the option of selecting a predetermined connection type from a group of connection types before setting the link. For example, a user can click on a desired connection type from a group of connection types by means of an input device and then establish a link between a modeling element ME of the development tool T _A and the development tool T _B. For example, a user first clicks on the connection type 2 defining a one-way connection, and then creates a connection between the modeling element ME "request" of the development tool T _B , which is, for example, a request Definition tool, such as Doors, and the modeling element ME "composition", which is a modeling element ME of the design tool or a UML design tool T _A. To produce or activate the link, the user can, for example, after clicking on the connection type 2, first click on the modeling element "request" and then on the modeling element "composition" or make a corresponding input via an input keyboard. In a further step, the user can then, for example, activate further links or links between the modeling element "use case" and the modeling element "operation". If the user subsequently wishes to establish a link or a connection of the other connection type between modeling elements of the various development tools, he clicks on the right-hand side of the screen on the desired connection type, for example on connection type 1. Subsequently, a link is made, for example, between the modeling element "feature" and the modeling element "class" made by clicking the two graphically illustrated modeling elements ME. In the example shown in FIG. 7, two development tools or software tools T _A , T _{B are shown} on the user interface. In an alternative embodiment, a larger number of development tools T can be displayed simultaneously on the screen in order to link modeling elements ME in a larger number of development tools T with each other.

In one possible embodiment, different modeling elements ME can be provided with access rights. For example, the "feature" modeling element may be disabled for a particular developer or user, so that no link from this locked modeling element ME to other modeling elements can produce other development tools. The allocation of access rights

For example, ZR may be done by a development manager from a group of developers. The method system according to the invention offers the possibility of combining different methods and associated development tools or development tools T without having to define project-related interfaces and exchange formats. By providing methods or tool classes TK, different development tools T can be distinguished with respect to their functionality. When combining development tools into a chain of development tools within a development process, it is therefore possible with the system according to the invention to combine a plurality of development tools T of a method class, or to combine development tools T of different method classes with one another. For example, it is possible to combine two UML development tools, ie development tools of the same method class, whereby one development tool T allows a particularly good modeling of a class diagram, and the second UML development tool T is better suited for the modeling of state diagrams , In addition, it is also possible to combine or link development tools T of different tool classes TK. For example, a requirements development development tool T may be associated with a design development tool to facilitate finding errors or tracking errors. The invention provides a method for integrating development tools T, in particular software development tools in the field of software engineering, wherein the development tools are preferably model-based and have modeling elements or artifacts.

The inventive method for integrating development tools T can be implemented by an application program. In this case, the various development tools T register with the integration program or the integration broker, indicating the respective tool class TK of the development tool. The integration broker or the integration program according to the invention then provides linking options between the modeling elements ME of the registered development tools T of identical or different tool classes TK. riding. This is preferably done for a graphical user interface in which various modeling elements ME of the registered development tools T are displayed on a screen for the user visible and linking options including different types of links are selectable by the user to a link between the modeling elements ME the different development tools T automatically to produce or activate. In this case, the illustrated modeling elements ME can preferably be provided with access rights ZR for the respective user. The modeling elements ME represented by the development and integration broker typically include classes, instances, operations, attributes, associations, nodes, and edges. Other modeling elements ME of further development tools can also be represented graphically by the integration program according to the invention for producing links. Modeling elements ME of at least two different development tools T are linked by the integration broker according to the invention.

In one possible embodiment, the integration broker according to the invention or the method according to the invention for integrating development tools also makes it possible to establish links between the modeling elements ME within the same development tool T. The linking of modeling elements ME of more than two development tools with the same or different tool classes TK is possible in a possible embodiment of the integration broker according to the invention.

The application program for integrating development tools according to the invention may in one possible embodiment be loaded from the computers 2 by the computers 4 of different developers via the network 3. In an alternative embodiment, an application program for carrying out the method for integrating development tools is loaded from a data carrier and stored in the computer of a developer. lers or user executed. In one possible embodiment, in a first-time start or a first-time execution of the application program for implementing the method of integrating development tools via the network 3, all the development tools T available on the respective computer 4, including the modeling elements ME contained therein, are reported to the server 2. In an alternative embodiment, the registration of the various development tools T present on a computer 4 takes place in each case in the first embodiment of the respective development tool T.

The method according to the invention and the system according to the invention are not limited to the embodiments shown in the figures. For example, the production of a link between modeling elements ME can also take place via a touchscreen in that a user touches the modeling elements ME to be linked on the screen. In a further variant, the activation or the production of a link between modeling elements of different development tools can be carried out acoustically via a voice input and a corresponding speech recognition. In one possible embodiment, a speaker recognition for authentication of the respective user additionally takes place in order to check whether the respective user has the necessary access rights in order to link the selected modeling element ME with further modeling elements. The application program according to the invention for carrying out a method for integrating development tools can be executed on mobile or non-mobile terminals 4. The network 3 shown in FIG. 1 may also be an access network that communicates with mobile terminals 4 of different users via a wireless interface.

In a further alternative embodiment, the server 2 queries all development tools T present at the various terminals 4 and sets the application program Integration of development tools to the terminals 4 via the network 3 available.

Claims

claims A method of integrating development tools (T) comprising the steps of: a) logging in (S) development tools to a server (2) indicating the respective tool class (TK) of the development tool (T); and b) providing (S2) linking options between modeling elements (ME) of the registered development tools (T) of the same or different tool classes (TK) by the server (2). 2. The method of claim 1, wherein a linkage option for establishing a link between modeling elements (ME) is activated. 3. The method of claim 1 or 2, wherein a connection type of the link is selected. 4. The method of claim 3, wherein the linkage is unidirectional or bidirectional. 5. The method of claim 1, wherein the development tools (T) when first run on a computer (4) at the server (2) are automatically logged. 6. The method of claim 1, wherein modeling elements (ME) are provided with access rights (ZR). 7. The method according to any one of the preceding claims 1 to 6, wherein the registered development tools (T) and the links produced between modeling elements (ME) of these development tools (T) are stored. The method of claim 1, wherein the modeling elements (ME) include classes, instances, operations, attributes, associations, nodes, and edges. 9. System (1) for integrating development tools (T) with a server (2) connected via a network (3) to computers (4; on which development tools (T) are executable, the development tools (T) log in automatically when executed at the server (2) stating their respective tool class (TK) and the server (2) provides linking options between modeling elements (ME) of the registered development tools (T) of the same or different tool classes (TK). 10. System according to claim 9, wherein a provided link option for establishing a link between modeling elements (ME) of development tools (T) can be activated. 11. Computer program with program instructions for carrying out the method for integrating development tools according to claim 1 - 10. 12. Volume of the computer program according to claim 11 stores.