JP2008269280A - Software development support system, development support method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To enable restoration of operation history over shared data after reflecting all the contents of an operation history database in a shared database. <P>SOLUTION: In a system equipped with: a shared database 1 which stores the software models developed by the unified modeling language (UML) and shared by all developers; an editing database 2 which stores a divided software model of which development and operation is divided for every developer; and an operation history database 3 which is shared by developers and registers operation history for every developer, a history information database 9 is prepared. When all operation histories of the operation history database are reflected in a shared database, the operation history data and specification information which can specify this operation history data are packaged into one and it is created/saved as a back up history information. History information is restored by retrieving the back up history information by designating the specific information. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a software development support system and development support method using a unified modeling language (UML), and more particularly to management of operation history in software development work.

  UML (Unified Modeling Language) is a modeling language for software development, and is a notation method for expressing the structure of a system to be developed, and allows developers to communicate with each other.

  Software development by UML supports various work related to software development, such as a specification creation support function, an analysis design support function, and a schedule management function of a system to be developed. Use cases (system function definition), activity diagrams (flow of operations), sequence diagrams (interactions between objects), object diagrams (instance snaps) as notation to support system specification creation, analysis design, and implementation Shot notation), class diagram (defining a static model), and the like are created (for example, see Non-Patent Document 1).

  In addition, the software development support system also has a collaborative work support function for team development, which manages each developer's operations as operation history, such as creating use case diagrams and adding class methods. . This collaborative work support function establishes a file distribution environment so that each developer can share and create shared data (such as various UML diagrams) of a system to be developed (see, for example, Patent Document 1).

  FIG. 10 is a block diagram of the main part of the software development support system. This system configuration consists of a shared database (DB) 1 that stores software models shared by all developers, an editing database 2 that stores shared models that are shared by each developer, and an operation history for each developer. A developer shared operation history database 3 to be registered and a project database 4 for storing a system development schedule are mounted. These databases are used as data storage devices, and the specification creation support function 5, the analysis design support function 6, the collaborative work support function 7 and the schedule management function 8 are installed as computer software, so that specification creation work, analysis design work, etc. Support.

In addition, on the main screen of the software development support system, as shown in the example of FIG. 11, the TODO list for each developer is displayed in a list, and the importance (emergency, reference, etc.), type (bug, change, etc.), transmission Person, contents, deadline, etc.
Meiden Times 2006 September / October, Vol. 310 No. 5 Japanese Patent Laid-Open No. 11-306060

  As described above, when a certain system is analyzed and designed by a plurality of developers, each developer develops a system by sharing an operation history. At this time, if a problem occurs in the system, if the operation history remains, the cause can be investigated by investigating the contents. However, if all the contents of the operation history database 3 are reflected in the shared database 1, the entire operation history is deleted in order to maintain consistency between the contents of the shared database 1 after the reflection and the contents of the operation history database 3. The cause of the failure cannot be determined.

  For example, as shown in FIG. 12, consider creating a class diagram A and creating a class P on it. First, there is no data in the shared database 1, and the operation history database 3 has operation histories “create class diagram A” and “create class P”. When these operation results are reflected in the shared database 1, “class diagram A” and “class P” exist as data in the shared database 1. Here, if “create class diagram A” and “create class P” remain as operation histories, the same data will be created twice, and the consistency of the data will not match. , Erase all of these operation histories.

In addition, the content requested by one developer to another developer is supported by the developer, and if so, from the TODO list, the importance, type, Since only the sender, content, and time limit information can be obtained, it is not possible to know when and how it was handled. The purpose of the present invention is to record the operation history for shared data even after all the contents of the operation history database are reflected in the shared database. Is to provide a software development support system, a development support method, and a program that can restore the system.

  In order to solve the above-described problems, the present invention creates / saves the operation history operated in the development work as backup history information when the developer performs the development work and registers the development data in the shared database. The past operation history can be searched based on the backup history information.

(1) A shared database that stores software models that are developed in a unified modeling language (UML) shared by all developers, an editing database that stores shared software models that are shared and operated by each developer, and development Software development support system with a developer-shared operation history database that registers operation history for each developer,
When the shared software model is created and all the operation histories of the operation history database are reflected in the shared database and registered in the shared database, the operation history data and the specific information that can specify the operation history data are combined into one. Registration means to create / save backup history information packaged together,
Search means for searching the backup history information registered by the registration means by specifying the specific information;
It is provided with.

  (2) When all the operation histories of the operation history database are reflected in the shared database and the contents of the operation history database are cleared, the data of all the databases in the state before the reflection is copied, and this is stored in the backup folder Is provided with storage means for storing as a file.

(3) display means for displaying an operation history list of files stored in the backup folder;
And a return means for replacing the data of the three databases, the shared database, the operation history database, and the history information database, included in the operation history selected from the operation history list display screen with the data of the current database, respectively. To do.

(4) A shared database that stores software models that are developed in a unified modeling language (UML) shared by all developers, an editing database that stores shared software models that are shared and operated by each developer, and development Software development support system with a developer-shared operation history database that registers operation history for each developer,
When the shared software model is created and all the operation histories of the operation history database are reflected in the shared database and registered in the shared database, the operation history data and the specific information that can specify the operation history data are combined into one. Registration step to create / save backup history information packaged together,
A search step of searching for the backup history information registered by the registration means by designating the specific information;
It is characterized by having.

  (5) When all the operation histories of the operation history database are reflected in the shared database and the contents of the operation history database are cleared, the data of all the databases in the state before the reflection is copied, and this is stored in the backup folder A storage step of storing the file as a file.

(6) a display step for displaying an operation history list of files to be stored in the backup folder;
And a return step of replacing the data of the three databases, the shared database, the operation history database, and the history information database, included in the operation history selected from the operation history list display screen with the data of the current database, respectively. .

  (7) The processing procedure in the software development support method described in the above (4) to (6) is configured to be executable by a computer.

  As described above, according to the present invention, when the developer performs the development work and registers the development data in the shared database, the operation history operated in the development work is created / saved as backup history information, Since the past operation history can be searched based on this backup history information, the operation history for the shared data can be restored even after all the contents of the operation history database are reflected in the shared database.

In particular,
(1) History information can be packaged and stored in a certain unit. By specifying the developer as a keyword, history information can be easily searched.

  (2) The operation history list can be used to investigate the cause when a problem occurs. Operations can be returned in units of operation history versions.

  (3) With the operation history list, the creation date and time and creator of a certain model can be grasped.

  (4) The operation history of other developers can be easily browsed from the to-do list by the to-do list list on the main screen.

  (5) History information can be easily set at the time of registration in the shared database by inputting history information in advance at the operation stage using the operation content setting dialog.

  FIG. 1 is a block diagram of the main part of a software development support system showing an embodiment of the present invention. The difference between FIG. 10 and FIG. 10 is that a history information database 9 is provided, and the developer shares the development work. When the development data at this time is registered in the shared database, the operation history operated in the development work is stored. It is stored in the history information database 9 as backup history information, and past operation history can be searched based on this backup history information.

  FIG. 2 shows an example of the data structure of history information stored in the history information database 9, and information that can identify the operation history at the time when the developer shares the operation history (registers in the operation history database 3). Package together with (shared database version, developer information, operation details, registration date, etc.). The history information may be packaged by adding information that can be specified other than the above.

  FIG. 3 shows a configuration diagram of the history information management function, and each function is additionally installed as software in the collaborative work support function 7. The operation history sharing registration function 11 is operated when the developer performs specifications creation, analysis design, and the like, and reflects the development data (shared software model) obtained in the editing database 2 as shared data, as in the past. History and development data are registered in both databases 1 and 3. The history information creation function 12 creates history information as shown in FIG. 2 according to work such as specification creation and analysis design by the developer. The history information saving function 13 saves the history information created by the history information creation function 12 in the history information database 9 when the developer finishes a single work and reflects it as shared data. At this time, if there is a related to-do list, the to-do list setting function 14 associates history information with one or more corresponding to-do lists (lists stored in the project database 4).

  When all the contents of the operation history database 3 are reflected in the shared database 1 and the contents of the operation history database 3 are cleared, the history information backup function 15 performs the current operation of the shared database 1, the operation history database 3, and the history information database 9. The data is collected and copied to a dedicated location (for example, a folder having a version number as a name) secured in an arbitrary database, and stored in the backup folder 16 as a file.

  Thereafter, as in the prior art, the operation history main registration function 17 causes the contents of the operation history database 3 to be reflected in the shared database 1 and the contents of the operation history database 3 are all erased. In accordance with this, all the contents of the history information database 9 are also deleted.

  When there is nothing in the operation history database 3 (when no operation is performed), for example, when the operation history main registration function 17 is continuously performed, the copied operation history database 3 and history information database 9 are used. The above-described processing is not performed because there is a possibility that the contents of are erased and overwritten with empty ones.

  An example of operation history registration processing and search processing using history information will be described below.

  (Example 1) An example in which a class diagram creation operation is reflected in a shared database of operation histories.

1-1. Registration of Class Diagram to Shared Database FIG. 4 and FIG. 5 show that as a class diagram creation operation, developer D creates class diagram A, creates class P and class Q, and creates this as shared database 1. Shows a schematic diagram for sharing registration.

  In FIG. 4, it is assumed that the shared database 1 is version “1” and has no contents. Among the history information “1”, the version of the shared database 1, developer information, registration date / time, and operation history data are acquired from the software development support system. The version of the shared database 1 is the version “1” of the current shared database, the developer information is “developer D” who created the class diagram A, and the registration date and time is the operation in which the developer D registers the operation history to share. Time of the system performed “2007/2/1 09:30”, the operation history data is an operation history “three types of operation history“ class diagram A creation ”“ class P creation ”“ class Q creation ” 1 ".

  On the other hand, the operation contents representing the results of a plurality of operation history data cannot be acquired from the software development support system. Therefore, a dedicated history information setting dialog is displayed, and the developer D inputs the operation content in a natural language. Displaying a list of operation histories in this dialog makes it easier for developers to input operation details. When the developer presses the setting button, the operation information entered by the developer is set to “Create class that implements function F” and packaged history information “1” is created and added to the history information database 9 To do.

  FIG. 5 shows a case where there is a to-do list related to developer D, which is related to the corresponding to-do list. All the to-do lists for the developer are displayed in the history information setting dialog, and the corresponding to-do list is selected. Associate by.

1-2. Reflecting Operation History to Shared Database FIGS. 6 to 8 are schematic diagrams from the time the developer D reflects the operation history to the shared database until the history is browsed after the operation 1-1.

  FIG. 6 shows the process until the operation history is reflected in the shared database. The version of the shared database 1 is “1”, and the operation history database 3 and the history information database 9 contain “operation history 1” and “history information 1” of 1-1, respectively.

  When the developer D reflects this “operation history 1” in the shared database 1, the three databases of the shared database 1, the operation history database 3, and the history information database 9 are newly added with the version “1” of the current shared database. A folder (backup folder 16) is created and stored as backup “1” therein.

  Thereafter, the contents of the operation history database 3 and the history information database 9 are emptied, and since there is only one operation history, the version of the shared database is increased by one to “2”. If there are two operation histories, the operation history is increased to “3”. Further, “history information 1” in the TODO list points to “history information 1” of backup “1”.

  As described above, each time the operation history is reflected in the shared database, the above operation is performed to create a folder (for example, backup 1) for each version of the shared database, and the shared database 1 is operated as backup data therein. Stored in the history database 3 and the history information database 9.

  FIG. 7 shows a display example of past operation history. By reading the operation history database 3 and the history information database 9 for each backup folder and displaying the contents in an operation history list screen or a tree format, the operation history can be searched and viewed in the past. By displaying not only the operation history but also history information, the developer can check detailed information on past operations.

  In addition, by pressing the “return operation” button, the operation is returned to the operation history selected in the operation history list. Using the above backup, the data in the three databases of the shared database, the operation history database, and the history information database in the folder of the selected operation history version are replaced with the data of the current database, respectively. Since these three databases are of the same period when the consistency of the model is actually maintained, there is no error even if they are replaced. If the current database is backed up to another folder, it can be easily restored by restoring the backed up database.

  When searching the operation history with developer information, check the developer information and select the target developer, the operation history list will display only the operation history for which the developer exists in the developer information. . FIG. 8 shows an example of searching an operation history using developer information as a keyword. Since version 1 is for developer D, but version 2 is not for developer D, only version 1 is displayed in the operation history list. There may be another item other than developer information as a keyword.

  If the contents of the operation history database are empty and the operation history is subsequently reflected in the shared database, the version of the shared database will not change.Therefore, depending on how the folder name is created, an empty database is created in the same folder. There is a possibility of overwriting. In such a case, it can be avoided by not reflecting the operation history in the shared database itself.

  (Example 2) An example in which operation details are described in advance.

  In Example 1 described above, when a developer registers his operation for sharing, the developer inputs the operation content in a natural language for the first time. If the operations are simple and few, it is easy to input the operation contents at this time. On the other hand, when operations with different contents are performed in order to correspond to a plurality of items in the TODO list and these operations are registered in the share at once, it is very difficult to input the operation contents at this time.

  Therefore, as shown in FIG. 9, an area in which the operation content is described in advance is added to the editing database 2. The editing database 2 is for temporarily storing the contents operated for each developer, and the operation contents are added to this.

  In FIG. 9, a dedicated operation content setting dialog for inputting the operation content is prepared, and the developer inputs the operation content. When the dialog is displayed, the currently set operation content is displayed in advance in the input field. In addition, by displaying the operation list together, the developer can easily input the operation contents with reference to the operation. When the “set” button is pressed, the operation content in the editing database 2 is replaced with the operation content input in the dialog. If the “Cancel” button is pressed, the operation content is not changed.

  The present invention is a development support method having a part or all of the processing procedure of the software development support system shown in the above embodiment, or provided as a program configured to execute the processing procedure in this method by a computer. can do.

The principal part block diagram of the software development assistance system which shows embodiment of this invention. Data structure example of history information database. History information management function block diagram. Schematic diagram (1) when sharing registration from creation of use case diagram. Schematic diagram (2) when sharing registration from creation of use case diagram. An example of reflecting the operation history to the shared database. An example of past operation history display. An example of searching past operation history. An example of the data structure of an edit database. The principal part block diagram of a software development support system (conventional). An example of a TODO list list on the main screen. An example of reflecting operation history to sharing.

Explanation of symbols

1 Shared Database 2 Edit Database 3 Operation History Database 4 Project Database 5 Specification Creation Support Function 6 Analysis Design Support Function 7 Joint Work Support Function 8 Schedule Management Function 9 History Information Database

Claims (7)

A shared database that stores software models that are developed in a unified modeling language (UML) shared by all developers, an editing database that stores shared software models that are shared and operated by each developer, and each developer In a software development support system equipped with a developer shared operation history database for registering operation history,
When the shared software model is created and all the operation histories of the operation history database are reflected in the shared database and registered in the shared database, the operation history data and the specific information that can specify the operation history data are combined into one. Registration means to create / save backup history information packaged together,
Search means for searching the backup history information registered by the registration means by specifying the specific information;
Software development support system characterized by comprising   When all the operation history of the operation history database is reflected in the shared database and the contents of the operation history database are cleared, the data of all the databases in the state before the reflection is copied, and this is stored as a file in the backup folder. The software development support system according to claim 1, further comprising storage means for storing. Display means for displaying a list of operation history files to be stored in the backup folder;
And a return means for replacing the data of the three databases, the shared database, the operation history database, and the history information database, included in the operation history selected from the operation history list display screen with the data of the current database, respectively. The software development support system according to claim 1. A shared database that stores software models that are developed in a unified modeling language (UML) shared by all developers, an editing database that stores shared software models that are shared and operated by each developer, and each developer In a software development support system equipped with a developer shared operation history database for registering operation history,
When the shared software model is created and all the operation histories of the operation history database are reflected in the shared database and registered in the shared database, the operation history data and the specific information that can specify the operation history data are combined into one. Registration step to create / save backup history information packaged together,
A search step of searching for the backup history information registered by the registration means by designating the specific information;
A software development support method characterized by comprising:   When all the operation history of the operation history database is reflected in the shared database and the contents of the operation history database are cleared, the data of all the databases in the state before the reflection is copied, and this is stored as a file in the backup folder. 5. The software development support method according to claim 4, further comprising a saving step of saving. A display step for displaying a list of operation history files to be saved in the backup folder;
And a return step of replacing the data of the three databases, the shared database, the operation history database, and the history information database, included in the operation history selected from the operation history list display screen with the data of the current database, respectively. The software development support method according to claim 4.   A program characterized in that the processing procedure in the software development support method according to claim 4 can be executed by a computer.

Images