JP4535906B2 - UML model creation support method and apparatus - Google Patents

Description

  The present invention relates to a UML model creation support method and apparatus for supporting requirements analysis / system design work using UML and creation of specifications thereof in the work of developing computer software.

  Software development is generally classified into phases such as requirements analysis, system design, implementation, testing, and migration. For this reason, the software developer develops the software to be developed in each phase in each phase.

  Requirement analysis is the analysis of what functions software should have to meet the requirements of the person (requester) who wants to create software.

  System design considers how the software is configured and how it behaves in order to achieve the functions derived from the analysis.

In the above requirements analysis and system design, a technique called modelling is often considered effective. This is because the understanding of the system is deepened by expressing the static and dynamic aspects of the system using diagrams as well as text. As a language for modeling, UML (Unified Modeling Language) has been proposed.
Masayuki Otani and Koichiro Ochimizu, “Study on Automatic Generation Method of Workflow for Changing Work in UML Documents”, 20th Annual Meeting of the Japan Society for Software Science, 2003.09. Yuta Tahara, Makoto Matsushita, Katsuro Inoue: “Proposal of source code modification support method using change history of existing software”, IPSJ Research Report, 2002-SE-136, Vol.2002, No.23, pp. 57-64, 2002.3.7 Version management software: CVS, configuration management software: Rational ClearCase, TeleLogic CM Synergy (Reference URL / http: //www.atmarkit.co.jp/farc/rensai/config01/config01.html) Change management software: Rational ClearQuest, TeleLogic Synergy (Reference URL / http: //www.atmarkit.co.jp/farc/rensai/config03/config03.html) Published Patent Publication “JP 2001-166924” Name “Software Development Management Device and Management Method”

  In software development, UML is often used for requirements analysis and system design. In this case, the developer performs requirements analysis and system design by modeling the system using UML.

  However, since the UML model generally expresses various aspects of the system with a large number of diagrams, it is difficult to create and difficult to manage. As a result, when creating a UML model, there is a possibility that errors and contradictions are included.

  As one of the causes of errors and contradictions, not only are there many figures defined in UML, but multiple figures are necessary to express one function of the system and its correlation, and they are complicated to each other. Have a strong relationship.

  Therefore, there is a need for a mechanism that clarifies the relationship between a plurality of UML diagrams, prevents the occurrence of errors and contradictions, and supports the developer to easily create a UML model in a short period of time.

  The present invention has been made in view of the above problems, and an object of the present invention is to provide a UML model creation support method capable of clarifying the relationship between a plurality of UML diagrams and preventing occurrence of errors and contradictions. It is to provide such a device.

In order to achieve the above object, the present invention provides a UML model creation support method in the case where requirements analysis or system design is performed using UML using a computer device. A definition that consists of elements, elements, and relationships is stored, and a change in the UML model is a change operation that is either addition, update, or deletion, and changes either a diagram, element, or relationship remove the targets, at least one of of the relationship between figures and elements constituting the UML model, it was decided to remove the with the additional or diagram or element or relationship to create a new diagram or element or relationship Or , add a new element or relationship to the diagram, delete or update an element or relationship already described in the diagram, or Change the type, add or delete or update the attached information held by the element, change the type of the element, add / delete / update the attached information held by the relationship, or change the type of the relationship When the change operation is an update, the information to be added or updated when the change operation is addition or update is used as a parameter, and the information to be updated when the change operation is update is deleted The change operation, the change object, the change content, the parameter, and the definition that the target is the change are stored with the information to be deleted as a target, and the similarity of change is the “change operation” between two changes. "change target", "change the subject type" stores the definition assumed degree of similarity is high when the be "change" is coincident is large, the computing device Create a UML model in a data format based on the above definition, records the information about the changes that the computing device has been made as a change history against UML model being created, new information about changes of the UML model When a new change is recorded, it is assumed that a change made immediately before the new change is made affects the new change, and information about other changes affecting the new change is recorded. Is recorded in the change history, the dependency information that other changes existing as the record have affected the newly recorded change is recorded, and the UML model being created is newly changed. When a change is attempted, a change similar to the change is searched from the recorded change history by determining the similarity of the change, and obtained by the search. Track other changes that are affected by similar changes, and track changes that may occur in the future by replacing the parameters and targets of the tracked changes with the parameters and targets of the newly made changes When a UML model that has been created and presented and the UML model being created is changed, another change similar to the change is searched from the recorded change history by determining the similarity of these changes. Propose a creation support method.

  According to the UML model creation support method of the present invention, when a software developer uses UML to perform requirements analysis or system design using a computer device, the computer device has a relationship between the UML model and the figure and elements. And the definition that the change of the UML model is the addition, deletion, or update of at least one of the diagrams and elements that make up the UML model. Based on this, information on the change of the UML model is recorded as a change history.

  As a result, when at least one of diagrams, elements, and relationships constituting the UML model is added, deleted, or updated, information regarding the change is recorded as a change history.

Further, in order to achieve the above object, the present invention is a UML model creation support device comprising a computer device in the case of performing requirements analysis or system design using UML. The definition that is configured and the change of the UML model are either an addition, update, or deletion as a change operation, and a diagram, an element, or a relationship is a change target, and the diagrams and elements that make up the UML model And adding at least one of the relationship between a figure, an element, or a relationship, or deleting a diagram, an element, or a relationship, or adding a new element or relationship to a diagram Adding, deleting or updating elements and relationships already described in the diagram, changing the type of diagram, and additional information held by the element Adding or deleting or updating the distribution, changing the type of elements, changing the updating the relationship can add / delete / update attribute information held or was to change the type of relationship content The information to be added or updated when the change operation is addition or update is a parameter, the information to be updated when the change operation is update, and the information to be deleted when the change operation is deleted is the target. A storage means for storing a definition that the operation, change target, change content, parameter, and target are changes , and information related to a predefined change similarity , and a UML model in a data format based on the above definition create, it records information about changes made to the UML model being created as a change history, information about changes in the UML model When a new record is recorded, it is assumed that a change made immediately before the new change is made affects the new change, and information about other changes affecting the change is recorded. When there is a change history, a change history recording means for recording dependency information that a change existing as a record has affected the newly recorded change, and a UML model being created is changed In addition, when another change similar to the change is searched for from the change history by determining the similarity of these changes, and a new change is being made to the UML model being created A change similar to the change is searched from the change history by determining the similarity of the change, the other changes affected by the similar change are tracked, and the parameters of the tracked change And target Propose a UML model creation support apparatus and a means for presenting to create a change that might occur in the future by replacing the parameters and target newly added changes.

  According to the UML model creation support apparatus of the present invention, when a software developer performs a requirement analysis or system design using UML, the definition that the UML model is composed of diagrams, elements, and relationships The change of the UML model is based on the diagram that constitutes the UML model and the definition that it is to add, delete, or update at least one of the elements and the relationship. Record as change history.

  As a result, when at least one of diagrams, elements, and relationships constituting the UML model is added, deleted, or updated, information regarding the change is recorded as a change history.

  According to the present invention, in the conventional case where the UML model was created without assistance by the above method and apparatus, the consistency of the UML model was overlooked by overlooking the part that had to be changed. However, errors or contradictions occur, or rework occurs to try to match the consistency later, but with the assistance of the above method and device, these errors, contradictions, and rework occur. Software developers can easily create UML models in a short period of time.

  Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

  In the present embodiment, a method for supporting creation of a UML model is constructed by utilizing the property that the UML model is repeatedly changed and refined, and an apparatus for implementing this method is configured.

  In this embodiment, first, as shown in the table of FIG. 1, the configuration of the UML model and the change of the UML model are defined. That is, generally, UML defines nine types of diagrams: class diagrams, object diagrams, package diagrams, use case diagrams, collaboration diagrams, state chart diagrams, activity diagrams, component diagrams, and layout diagrams.

  In this embodiment, what is described in the UML diagram is defined as two types of “element” and “relation”. “Elements” include those described in the table of FIG. 1, and hold the auxiliary information described in this table. Further, the operation / attribute which is the attached information of “element” holds the attached information of the operation / attribute. “Relationship” is described in the table of FIG. 1 and holds the auxiliary information described in this table.

  That is, as shown in FIG. 1, “elements” include classes, objects, packages, use cases, actors, interfaces, N-term relations, activities, states, initial states, end states, history states, connection points, dynamic points. Selection points, forks, joins, branches, control icons (event transmission), control icons (event reception), components, and nodes are defined.

  In addition, as “relation”, association, link, aggregation, composition, generalization, dependence, realization, message, transition, control flow, and object flow are defined.

  Furthermore, as the attached information of “element”, name, attribute, operation, stereotype, entry action, exit action, do action, include action, active section, and lifeline are defined.

  Attached information of "Relation" includes name, stereotype, role name (parent / child), multiplicity (parent / child), direction of related name, parent-child direction, argument, return value, message line, trigger, guard , Actions are defined.

  Names, arguments, return values, visibility, and class operations (static) are defined as attached information of operations.

  As attribute attribute information, name, type, initial value, visibility, and class attribute (static) are defined.

  The “relation” has a direction, and the direction is called a parent / child. The relationship of the constituents that make up the UML model is as shown in FIG. 2. “Element” and “Relation” are subordinate to “Figure”, and “Attachment information” is assigned to each of “Element” and “Relation”. Is subordinate.

  In the present invention, as shown in the table of FIG. 3, the change of the UML model is the addition, deletion or update of the diagram (hereinafter referred to as addition / deletion / update), the addition / deletion / update of elements, the addition / It is defined as a change operation of either deletion / update.

  Adding a figure means creating a new figure. Similarly, deleting a figure is deleting a figure. Updating a diagram means adding a new element or relationship, deleting or updating an element or relationship already described in the diagram (hereinafter referred to as deletion / update), or changing the type of the diagram. It is.

  Adding an element means creating a new element. Similarly, deleting an element is deleting an element. Updating an element means adding / deleting / updating attached information (name, attribute, operation, stereotype, entry action, exit action, do action, include action, active section, lifeline) held by the element, or It is to change the element type.

  Adding a relationship means creating a new relationship. Similarly, deleting a relationship is deleting a relationship. Relationship update means attached information (name, multiplicity (parent / child), role name, direction of related name, parent / child orientation, stereotype, argument, return value, message line, trigger, guard, Action) is added / deleted / updated, or the type of relationship is changed.

  In the update of an element, special operation / attribute update is added in more detail, and additional information of the operation / attribute (name, argument, return value, visibility, class operation (static) or class attribute (static)) is added. / Deletion / update.

  All changes are made up of a change operation, a change target, change contents, parameters, and a target. The parameter stores information to be added when added and information to be updated when updated. However, it is blank for deletion. The target stores information to be updated when updated, and information to be deleted when deleted. However, it is blank when adding.

  Next, in this embodiment, a method for recording a history capable of tracking the process of changing the UML model is defined. Here, the meaning of tracking the change of the UML model will be described. When the UML model is changed, another change may occur due to the effect of the change. This is because a part of the UML model is changed so that consistency with another part cannot be obtained. For example, as shown in FIG. 4, when the UML diagram A is changed, it is assumed that the UML diagram B is changed in order to maintain consistency. At this time, the UML diagram C had to be changed in the same manner. However, if the developer does not notice it and overlooks it, a rework will occur for later consistency.

  That is, the change in the UML diagram A affects the UML diagram B and the UML diagram C, and changes are generated in these diagrams. In the present embodiment, the effect of such a change propagates. Relationships are defined as change history so that they can be tracked.

  Normally, the change history has a tree structure as shown in FIG. For example, when changes 111 to 113 occur due to the effect of the change 101, the relationship between these changes is recorded as a change history. Furthermore, when the change 121 occurs due to the effect of the change 111, when the change 122,123 occurs due to the effect of the change 112, or when the change 124,125 occurs due to the effect of the change 113 Records the relationship of these changes as a change history.

  Next, an embodiment of a method and apparatus for supporting creation of a UML model using the above definition and change history will be described. In the present embodiment, as shown in FIG. 6, an operation including a UML model creation unit 11, a change history recording unit 12, a change estimation unit 13, a change history database (hereinafter referred to as a change history DB) 14, a keyboard, a mouse, and the like. The UML model creation support system 10 is configured by a computer device including a display unit 16 including a unit 15 and a monitor display. The UML model creation support system 10 operates according to a computer program set in advance.

(Create UML model)
The UML model creation unit 11 is responsible for creating a UML model, stores a definition that the UML model is composed of diagrams, elements, and relationships. In addition to the normal UML model creation function, this embodiment In FIG. 2 has an input function of information used for creation support and a function of outputting information obtained by the present embodiment.

(Change log recording)
The change history recording unit 12 stores a definition that the change of the UML model is to add, delete, or update at least one of the diagrams and elements constituting the UML model, The change history is recorded in the change history DB 14 using the change history recording method defined as described above.

  Each unit of the UML model creation support system 10 operates as shown in FIG. That is, when the developer makes a change to the UML model created in the UML model creation unit 11 via the operation unit 15, the change history recording unit 12 records the change related to the changed UML model 21 in the change history DB 14. To do.

  The change log recording method is set in advance so that the change history recording unit 12 automatically records the change, and the change is explicitly selected when the developer makes a change. There are two types of methods, and any one of these can be set from the operation unit 15.

  In the case of automatic recording, when the developer changes the UML model, the change history recording unit 12 automatically records the change in the change history DB 14 and then changes made immediately before (already recorded as change history) It is determined that the change 22) has been affected, and the dependency relationship between the change 22 made immediately before and the change just made (change 23 created from the changed UML model 21) is recorded in the change history DB 14. To do. When the developer explicitly records the change, the change history recording unit 12 records the change 23 in the change history DB 14, and then the developer selects the affected change 22 from the change history DB 14. The change history recording unit 12 records the dependency between the change 22 affected and the change 23 just made in the change history DB 14.

  The overall flow of the change history recording process is as shown in FIG. That is, when the developer makes a change to the UML model created in the UML model creation unit 11 via the operation unit 15 (SA1), it is determined whether or not the UML model creation unit 11 is set to automatic change recording. When it is determined (SA2) and the automatic change recording is set, the change history recording unit 12 stores the change operation of the added change 23 and the change target, change contents, parameters, and target in the change history DB 14. In addition to recording (SA3), the dependency relationship between the change 23 and the change 22 made immediately before is recorded in the change history DB 14 (SA4).

  In addition, if the developer is set to record changes without being set to automatic change recording as a result of the determination of SA2, the change history recording unit 12 explicitly selects the developer. The change 23, that is, the change operation, change target, change contents, parameters, and target selected by the developer to be recorded is recorded in the change history DB 14 (SA6), and the change history recording unit 12 changes the affected change. It is determined whether or not 22 exists in the change history DB 14 (SA7), and if it exists, the dependency between the affected change 22 and the change 23 explicitly selected by the developer is recorded in the change history DB 14 (SA8).

(Change guess)
As shown in FIG. 9, the change estimation unit 13 operates when a new change is made to the UML model being created. That is, when a developer makes a new change to the UML model created in the UML model creation unit 11 via the operation unit 15, a change 32 that may occur due to the newly added change 31 The change estimation unit 13 estimates and creates this, and presents this to the developer via the display unit 16.

  There are two methods for operating the change inference unit 13: a method in which the change inference unit 13 automatically makes a guess when a new change is made in advance, and the software developer There are two types of methods of instructing to guess, and any one of these can be set from the operation unit 15.

  The change inference unit 13 stores information on the similarity of the predefined changes, and when the change inference unit 13 starts operation, the change inference unit 13 is similar to the newly added change 31. 33 is searched from the change history DB 14. Here, the search is performed by determining the similarity of changes recorded in the change history DB 14 according to the procedure shown in the flowchart of FIG. Is to get as a change. Note that the predefined similarity and the criterion based on the similarity are stored in advance in the change estimation unit 13.

  That is, as shown in the flowchart of FIG. 10, when determining the similarity of change, the change estimation unit 13 first determines whether or not the change operations match (SB1). The similarity determination process is terminated assuming that they are not similar. Further, when the change operations match, it is determined whether or not the change targets match (SB2), and when the change targets match, it is determined whether or not the change contents match. (SB3). As a result of this determination, this change is acquired as a similar change only when the change contents match (SB4).

  If the result of determination in SB2 indicates that the change targets do not match, the change estimation unit 13 determines whether the change target types match (SB5), and the change target types match. If not, the similarity determination process is terminated as not being similar. Further, when the types to be changed match, it is determined whether or not the changed contents match (SB6), and when the changed contents do not match, the similarity is determined as not similar. The process ends. If the contents of the change are the same, this change is acquired as a similar change (SB7).

  The criterion for determining that two changes are similar is whether or not the “change operation”, “change target”, “change target type”, and “change contents” match. However, there may be a plurality of similar changes in the change history DB 14.

  An example in the case where the determination criteria are satisfied will be described below. For example, when the change operation is about to acquire a change similar to the change of “add”, the change that is performing the same “add” satisfies the criterion. Is determined. The same applies to the change operation of “delete” and “update”.

  The determination criterion “change target matches” is, for example, when acquiring a change similar to a change whose change target is “device class” which is one of the elements “class” of the UML model. It is determined that changes for which the same “device class” is to be changed satisfy the criteria.

  The criterion of “matching type of change target” is, for example, trying to acquire a change similar to a change whose change target is “device class” which is one of the elements “class” of the UML model. In some cases, it is determined that a change for which the element “class” of the UML model of the same type satisfies the criteria.

  For example, when the user is trying to acquire a change in which a change operation “update name” is performed on an element of the UML model, the same “update name” change criterion is used. It is determined that the change that is changing the content satisfies the criteria.

  Further, the change estimation unit 13 may acquire a plurality of similar changes as a result of the search, and operates as follows for each change.

  The change estimation unit 13 tracks the change 34 in which the influence has propagated from the change 33 determined to be similar as a result of the search. If there are one or more affected changes, the change inference unit 13 replaces the parameters and targets of the tracked change 34 with the parameters and targets of the newly added change 31, and after the newly added change 31 A change 32 that may occur is estimated and created, and this is presented to the developer via the display unit 16.

  The overall flow of the change estimation process is as shown in the flowchart of FIG. That is, when the developer makes a change to the UML model created in the UML model creation unit 11 via the operation unit 15 (SC1), it is determined whether or not the change estimation unit 13 is set to change automatic estimation. (SC2) When the automatic change estimation is not set, the process proceeds to the process of SC9, which will be described later. When the automatic change estimation is set, the change estimation unit 13 sends similar changes from the change history DB 14. Obtain (SC3) and determine whether or not the obtained change is one or more (SC4).

  As a result of this determination, if there is no acquired change, the process is terminated. If there are one or more acquired changes, based on the change 33 acquired by the change estimation unit 13 (if there are multiple changes, each change). Track affected changes (SC5). Thereafter, the change estimation unit 13 determines whether or not there are one or more changes 34 obtained by tracking (SC6). If there is no change 34, the process is terminated and the change 34 obtained by tracking is determined. When there is one or more, the parameter 34 and the target of the change 34 obtained by tracking the change estimation unit 13 are replaced with the parameter and the target of the newly performed change 31, and the change 32 that may occur Is created (SC7), and the created change 32 is presented to the developer via the display unit 16 (SC8).

  If the result of the determination in SC2 is set to automatic change estimation, it is determined whether or not change estimation is instructed by the developer (SC9). Changes similar to 13 are acquired from the change history DB 14 (SC10), and it is determined whether there are one or more acquired changes (SC11).

  As a result of this determination, if there is no acquired change, the process is terminated. If there are one or more acquired changes, based on the change 33 acquired by the change estimation unit 13 (if there are multiple changes, each change). The change inference unit 13 tracks the affected change (SC12).

  Thereafter, the change estimation unit 13 determines whether or not there are one or more changes 34 obtained by tracking (SC13). If there is not, the process is terminated, and the change 34 obtained by tracking is obtained. When there is one or more, the parameter 34 and the target of the change 34 obtained by tracking the change estimation unit 13 are replaced with the parameter and the target of the newly performed change 31, and the change 32 that may occur Is created (SC14), and the created change 32 is presented to the developer via the display unit 16 (SC15).

  With the above two operations, the developer is supported to create a UML model using the change history. As a result, in the conventional case where the UML model was created without assistance from the above-described method and apparatus, the UML model cannot be kept consistent by overlooking the part that had to be changed. If an error or contradiction occurs or a rework occurs in the future to try to match its consistency, the support by the above method and device can prevent the occurrence of these errors, contradictions and rework. In this way, software developers can easily create UML models in a short period of time.

  Therefore, according to the present embodiment, the relationship between a plurality of UML diagrams can be clarified to prevent the occurrence of errors or contradictions.

  An embodiment of the present invention will be described below. In the present embodiment, as shown in FIG. 12, the UML model creation support apparatus 10 described above is used when an operation for developing a system (apparatus management system) 300 for managing the apparatus 200 is performed. This development target system 300 includes a database (DB) 310 and has a function of “registering a device to be managed in the system itself”.

  In order to design the DB 310 held in the device management system 300 and information to be managed, it is necessary to analyze the static structure of the device management system 300. Therefore, a table design diagram (FIG. 13), which is one of the class diagrams, for designing the table of the DB 310 held by the device management system 300 using UML is created.

  In addition, a data model diagram (FIG. 14), which is one of the class diagrams, for expressing the structure and attributes of information handled by the device management system 300 is also created. Since both the data model diagram and the table design diagram express information handled by the device management system 300, there are many common parts.

  It is necessary to cause the device management system 300 to perform an operation for realizing the function of “registering a device to be managed with the system itself”. Therefore, a sequence diagram (FIG. 15) for registering a device, which is one of the sequence diagrams, is created using UML, and the behavior of the device management system 300 is analyzed.

  By the end of software development, the UML model is repeatedly changed. An example of recording the change history is shown below.

  Assume that it is found during development that the behavior of registering the model name of the device is not described in the created sequence diagram (FIG. 15). The sequence diagram shown in FIG. 15 includes a browser 401, four objects “JSP” 402, “service” 403, “DAO” 404, “Entity” 405, an active section 406 corresponding to the browser 401, and “service” 403. , An active section 408 corresponding to “DAO” 404, and an active section 409 corresponding to “Entity” 405 are described. Further, the message 410 “Register” from the active section 406 corresponding to the browser 401 to the active section 407 corresponding to the “service” 403 and the active section 407 corresponding to the “service” 403 to the “DAO” 404 are supported. A message 411 “register (name, maxRate, minRate)” to the active section 408 and a message from the active section 408 corresponding to “DAO” 404 to the active section 409 corresponding to “Entity” 405 are described.

  Therefore, as shown in FIG. 16, a change is made such that the behavior for registering the model name of the apparatus (update of the message in the sequence diagram) is added to the sequence diagram.

  Here, in order to execute the “behavior of registering the device model name” added to the sequence diagram, the device management system 300 must have a table for storing the information (model name). Therefore, as shown in FIG. 17, a change is made to add “EQUIIPMENT_NAME” to the class EQIPMENT in the table design drawing.

  Since the data model diagram also expresses information managed by the device management system 300, as shown in FIG. 18, a change is made to add “equipmentName” to the class Equipment of the data model diagram as well.

  In this embodiment, it is assumed that the developer has selected the change history recording unit 12 to record the above change. Here, the developer determines that there is a change of `` Add model name '' between the table design drawing and the data model diagram, affected by the consistency with the sequence diagram to register the device 200, The developer gives an instruction to the change history recording unit 12 to record the dependency as shown in FIG. The above is an example of recording the change history.

  Similarly, the change for updating the argument (equipmentName is equipmentNumber) is as shown in FIG. Further, the change for deleting the argument (deletion of equipmentName) is as shown in FIG.

  Next, an example in which the UML model creation support apparatus 10 according to the present invention supports creation of a UML model using the change history will be described.

  In the same manner as described above, processing when it is found that the behavior of registering the device ID of the device 200 is not described in the sequence diagram shown in FIG. 16 will be described. In this case, the developer makes a change (message update) for adding a behavior for registering a device ID to the sequence diagram via the operation unit 15, as shown in FIG.

  Here, assuming that the developer gives an instruction to guess the change to the change estimation unit 13 via the operation unit 15, the change estimation unit 13 adds the above-described behavior for registering a device ID. The change history DB 14 is searched for whether there is a change similar to the change (FIG. 23).

  The change estimation unit 13 acquires a change similar to the change in FIG. 23 from the change history DB 14 and checks whether the change operations match. Then, all the changes recorded in FIG. 19 coincide with each other because the change operation is “update”. Next, the change estimation unit 13 checks whether or not the objects to be changed match. Then, it can be seen that “message (register)” in the (sequence diagram) matches. Further, it is checked whether or not the contents of change match. Then, since the change contents “add argument” match, it can be determined that the next change is similar, and the change is acquired as shown in FIG.

  Next, the change estimation unit 13 tracks changes that the acquired change has an influence from the change history DB 14. Then, it can be traced that there are two influences of “class (equipment)” and “class (equipment) change” recorded in FIG. 19. .

  Therefore, the change estimation unit 13 of the UML model creation support apparatus 10 sets “add attribute“ equipmentID ”to class (equipment)” and “add attribute“ equipment_id ”to class (equipment)”. Assuming that a corresponding change can occur in the future, as shown in FIG. 25, create a change that may occur (create a parameter substituting “equivalent to equipment ID”), This is presented to the developer via the display unit 16.

  Since the developer is presented here with a change that may occur in the future from the UML model creation support apparatus 10, the developer can check in advance whether the change will occur. Therefore, it is possible to prevent the possibility of overlooking the change that should have been made and the consistency of the UML model being lost.

  As described above, according to the present embodiment, the relationship between a plurality of UML diagrams can be clarified to prevent errors and contradictions from occurring.

  The above is an example of assisting the developer in creating a UML model using the recorded change history.

  Hereinafter, differences between the above-described conventional example and this embodiment will be described.

  Difference from the technology described in Non-Patent Document 1: The technology described in Non-Patent Document 1 supports the developer's work by defining a meta model of a UML document and automatically generating its dependency. However, the present embodiment is different in that it focuses on the dependency that does not appear as a meta model and uses it.

  Difference from the technology described in Non-Patent Document 2: The technology described in Non-Patent Document 2 is a technology that supports the correction of the source code by using the change history of the source code. It is different in that the creation of a UML model is supported from the viewpoint that a model such as UML has increased in development.

  Differences from the technology described in Non-Patent Document 3: With the technology described in Non-Patent Document 3, the history of changes can be managed and tracked by version management and configuration management software. Although it is the developer himself, the present embodiment is different in that the developer is supported by actively utilizing the change history.

  Difference from the technology described in Non-Patent Document 4: The technology described in Non-Patent Document 4 uses a change management software to manage changes in the UML model from the perspective of project management, and systematically from change request to execution In this embodiment, focusing on the dependency relationship between changes from the viewpoint of the developer, and the creation of the UML model is supported using this dependency relationship. Is different.

  Difference from the technology described in Patent Document 1: In Patent Document 1, a method that can refer to past product change information in claims 8 and 9 is proposed. It remains in the referencing method. However, the present embodiment is different not only in managing change information (change history) but also in supporting software development work by actively using the change information.

The figure explaining the definition regarding the structure of the UML model in one Embodiment of this invention The figure which shows the structure of the UML model in one Embodiment of this invention. The figure explaining the definition regarding the change of the UML model in one Embodiment of this invention The figure explaining an example when the consistency of a UML model cannot be maintained The figure explaining the change log in one embodiment of the present invention The block diagram which shows the UML model creation assistance apparatus in one Embodiment of this invention The figure explaining the operation | movement at the time of the change recording in one Embodiment of this invention The flowchart explaining the processing operation at the time of change recording in one embodiment of the present invention. The figure explaining the operation | movement at the time of the change estimation in one Embodiment of this invention The flowchart explaining the determination processing operation | movement at the time of the similar change acquisition in one Embodiment of this invention Flowchart describing processing operations for creating possible changes in one embodiment of the invention The figure which shows the development object system and apparatus in one Example of this invention. Table design in one embodiment of the present invention Data model diagram in one embodiment of the present invention The sequence diagram which registers the apparatus in one Example of this invention Sequence diagram after change in one embodiment of the present invention Table design after change in one embodiment of the present invention Data model diagram after change in one embodiment of the present invention The figure explaining the change history recorded in one Example of this invention The figure which shows an example of the change which updates the argument in one Example of this invention The figure which shows an example of the change which deletes the argument in one Example of this invention Sequence diagram after change in one embodiment of the present invention The figure which shows the change of the search object in one Example of this invention. The figure explaining the acquisition example of the similar change in one Example of this invention The figure explaining the example of a guess of the change which may occur in one Example of this invention

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 ... UML model creation assistance apparatus, 11 ... UML model creation part, 12 ... Change history recording part, 13 ... Change estimation part, 14 ... Change history DB, 15 ... Operation part, 16 ... Display part, 21 ... Changed UML Model, 22 ... Recorded change, 23 ... Created change, 31 ... Newly added change, 32 ... Change that may occur, 33 ... Similar change, 34 ... Change propagated 101, 111-113, 121-125 ... change, 200 ... device, 300 ... development target system, 310 ... database (DB), 401 ... browser, 402-405 ... object, 406-409 ... active section, 410-412 ... message.

Claims (2)

A UML model creation support method for performing requirements analysis or system design using UML using a computer device,
The computer device includes:
The UML model stores definitions that are made up of diagrams, elements, and relationships,
What is a change in the UML model?
Any one of addition, update, or deletion is a change operation, and any of figures, elements, or relationships is to be changed, and at least one of the figures, elements, and relationships constituting the UML model is changed to a figure, elements, or Adding a new relationship or deleting a diagram or element or relationship or deleting a diagram or adding a new element or relationship to a diagram, or deleting an element or relationship already described in the diagram Or update, change the type of diagram, add or delete or update the attached information held by the element, change the type of element, add / delete / update the attached information held by the relationship Or the update to change the type of relationship is the change content, and if the change operation is addition or update, it is added or updated. The target information is the information to be updated when the change operation is update, and the information to be deleted when it is deleted.
Storing the definition that the change operation, the change target, the change content, the parameter, and the target are changes ;
The similarity of change is
Store the definition that the similarity is high when there are many things that match or change the “change operation”, “change target”, “change target type”, and “change contents” between the two changes ,
The computer device creates a UML model in a data format based on the above definition, and the computer device records information about changes made to the UML model being created as a change history ,
When information related to the change of the UML model is newly recorded, the change made immediately before the new change is made affects the new change, and the new change is affected. If there is a record of information regarding other changes being present in the change history, record the dependency information that the other changes present as the record have affected the newly recorded change,
When a new change is made to the UML model being created, a change similar to the change is searched from the recorded change history by determining the similarity of the change, and the search is performed. Tracks other changes affected by similar changes obtained by, and may occur in the future by replacing the parameters and targets of the tracked changes with the parameters and targets of the newly made changes Create and present a change that has
When a UML model being created is changed, another change similar to the change is searched from the recorded change history by determining the similarity of these changes. Support method. A UML model creation support device comprising a computer device for performing requirements analysis or system design using UML,
A definition that the UML model is composed of diagrams, elements and relationships;
The change of the UML model is any one of addition, update or deletion as a change operation, and any one of the diagram, the element or the relationship is the change target, and at least one of the diagram, the element and the relationship constituting the UML model Add a new figure or element or relationship, or delete a new figure or element or relationship, or add a new element or relationship to the figure. Delete or update existing elements or relationships, change the type of figure, add or delete or update attached information held by an element, change the type of an element, attached information held by a relationship Change is to add / delete / update or change the relationship type, and the change operation is addition or update The information to be added or updated in the case is a parameter, the information to be updated when the change operation is update, the information to be deleted in the case of deletion is the target, the change operation, the change target, the change content, the parameter, A definition that the target is a change ,
Storage means for storing information relating to the similarity of predefined changes ;
When a UML model is created in a data format based on the above definition, information related to changes made to the UML model being created is recorded as a change history, and information related to changes in the UML model is newly recorded When a change made immediately before the new change is made affects the new change, and a record of information about other changes affecting the change exists in the change history Change history recording means for recording dependency information that a change existing as the record has affected the newly recorded change ;
Means for searching other changes similar to the change from the change history by determining the similarity of these changes when the UML model being created is changed;
When a new change is about to be made to the UML model being created, a change similar to the change is searched from the change history by determining the similarity of the change, and the similar change Track other changes that have affected and create and present changes that may occur in the future by replacing the parameters and targets of the tracked changes with the parameters and targets of the newly made changes UML model creation support apparatus characterized by comprising a means.

Images