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

Abstract

<P>PROBLEM TO BE SOLVED: To facilitate display, selection and usefulness in many occasions of a class which is a design target. <P>SOLUTION: A UML (Unified Modeling Language) figure creation section 1 creates a UML figure including a class figure by an object-oriented technique and saves it in a database 4. A class display section 5 carries out list display of all the classes of the class figure, and "display" or "not display" can be set for every class in this list display screen, and only the class in which "display" is checked by this setting is displayed. A class display history saving section 6 saves a setting history in which " display" or "not display" for every class is set in a file format in a database, and the status "display" or "not display" for every class is restored when carrying out class list display. Further, when saving the setting history in the database, it is saved by giving a name by file, and setting history is read by designating the name by file and the class display is restored based on this setting history. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a software development support system and a development support method using a unified modeling language (UML), and more particularly to class display and selection in software development using object-oriented technology.

  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.

  For software development by UML, use cases (system function definition), activity diagrams (flow of operations), sequence diagrams (between objects) are used as notations to support the creation, design, and implementation of the specifications of the system to be developed. Create interaction diagrams, object diagrams (instance snapshot notation), class diagrams (define static models), etc. UML defines 10 diagrams such as the above use case diagrams and class diagrams, but some UMLs have a function of creating diagrams that represent screens and screen transitions (for example, Non-Patent Document 1). reference).

  Each functional element used in these figures is a combination of screen parts (rectangle, ellipse, circle, arrow, actor symbol, connector symbol, node symbol, selection symbol, etc.) and characters (name and attribute information) defined in UML. Created with.

  In object-oriented technology, a class abstracts an element that has something in common with an object and defines it as a framework. In other words, if a class has a certain template, the object has a relationship of its substance. As shown in the example of FIG. 9, this class diagram expresses what structure the class has and the relationship between the classes.

Further, in the software development support system such as Patent Document 1, as shown in an example in FIG. 10A, the designed classes are arranged on a tree as a list, and the system developer can select a desired class from the list. Select to proceed with the design of that class.
Meiden Times 2006 September / October, Vol. 310 No. 5

  If the scale of the development target is small, the number of classes generated at the time of design is not so large, so it is relatively easy to display and select the desired class from the list of classes arranged on the tree. .

  On the other hand, when the scale of the development target is increased, the number of classes generated at the time of design becomes enormous, so that it becomes very difficult to display and select a desired class from the class list arranged on the tree. For example, as shown in FIG. 10B, if the classes handled by the developer are 1, 5 and 20, classes 1 and 5 are displayed on the screen, but class 20 is not displayed on the screen. For this reason, in order to obtain all class displays, it is necessary to scroll to the final class position and search.

  In addition, when a development target is jointly developed by a plurality of developers, the class in which each developer is in charge of design is determined, and the other classes are displayed in the class list.

  An object of the present invention is to provide a software development support system, a development support method, and a program that make it easy to display, select, and reuse classes to be designed.

  In order to solve the above-described problems, the present invention enables only the classes specified by the developer to be displayed in the class list, and further sets a class group to be displayed in the class list specified by the developer as a setting history to a database such as a file. It is stored in a (storage medium), and is further stored with a name for each file at the time of setting, and is characterized by the following system configuration, method and program.

(1) Create a UML diagram that describes each functional element using a combination of screen parts and characters defined in the Unified Modeling Language (UML), and support the creation, design, and implementation of the system to be developed based on this UML diagram. In the software development support system that
A UML diagram creation unit that creates a UML diagram including a class diagram based on object-oriented technology and stores it in a database;
List all classes in the class diagram saved in the database, and on this list display screen, you can set “display” / “not display” for each class, and check “Display” in this setting. And a class display unit that displays only the image.

  (2) When “display” or “not display” is set for each class by the class display unit, the setting history is stored in the database in a file format, and the class display unit displays a class list. In some cases, a class display history storage unit for restoring the “display” / “not display” state for each class is provided.

  (3) The class display history storage unit saves the setting history in which “display” / “not display” is set for each class by naming each file when storing it in the database. A feature is that a setting history is read by designating a name, and a class display is restored based on the setting history.

(4) Create a UML diagram that describes each functional element with a combination of screen parts and characters defined in the Unified Modeling Language (UML), and support the creation, design, and implementation of the system to be developed based on this UML diagram In the software development support method to
A UML diagram creation step for creating a UML diagram including a class diagram based on object-oriented technology and storing it in a database;
List all classes in the class diagram saved in the database, and on this list display screen, you can set “display” / “not display” for each class, and check “Display” in this setting. And a class display step for displaying only.

  (5) When “display” or “not display” is set for each class in the class display step, the setting history is stored in the database in a file format, and the class display step displays a class list. In some cases, a class display history storing step for restoring the “display” / “not display” state for each class is provided.

  (6) In the class display history saving step, the setting history in which “display” / “not display” is set for each class is saved in the database with a name for each file. A feature is that a setting history is read by designating a name, and a class display is restored based on the setting history.

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

  As described above, according to the present invention, only the classes specified by the developer can be displayed in the class list, and the classes to be displayed in the class list specified by the developer are stored in a database (memory) such as a file as a setting history. In addition, it is easy to display, select, and reuse the class to be designed because it is saved by naming each file at the time of setting.

In particular,
(1) By displaying only the classes designated by the developer in the class list, the developer can easily select the class in charge of the design.

  (2) The class group specified by the developer to be displayed in the class list is saved as a setting history in a storage medium such as a file, and the class group to be specified in the class list is read next time by loading the storage medium. Can be specified easily.

  (3) By assigning a name to each file stored in the storage medium, it is possible to create a class display state for each developer and reuse it.

  FIG. 1 is a configuration diagram of a software development support system showing an embodiment of the present invention, and mainly shows only functional blocks related to class design. Each unit in FIG. 1 is functionally configured by hardware resources of a computer system and software installed therein.

  The UML diagram creation unit 1 displays ten diagrams such as use case diagrams, activity diagrams, sequence diagrams, and class diagrams as display means for supporting the creation, design, and implementation of the specifications of the system to be developed (display medium). Create on the second screen. Further, in addition to the above ten figures, as shown in Non-Patent Document 1, a figure representing a screen or a screen transition is created.

  When creating these diagrams, rectangles, actor symbols, connector symbols, notes, etc. prepared in the UML common screen component 3 are appropriately pasted on the diagram being created on the screen of the display 2. Furthermore, name, attribute information, etc. are set in the graphic information of the UML diagram.

  The database 4 stores the graphic information of the UML diagram created by the UML diagram creation unit 1 and its name and attribute information in association with each other.

  In the UML diagram created by the above configuration, this embodiment proposes a software development support system that facilitates class display, selection, and reuse in class design, and will be described in detail below.

  The UML diagram created by the UML diagram creation unit 1 is stored in the database 4, and in the class diagram, the aggregation relationship and multiplicity between classes are set and stored. In this embodiment, a class display unit 5 is provided that displays a list of all classes stored in the database 4 and can set “display” or “not display” for each class on the list display screen. This is a list display screen shown in FIG. 2A. Each class has two states of “display” and “not display”, and when the class is checked, the state is “display”. When the check is removed from the class, the function configuration is set to “not display”.

  Furthermore, the class display unit 5 is provided with a filtering function for displaying only classes for which “display” is checked in the class list display. This is because, when “display” is checked on the class list display screen shown in FIG. 2A, only the classes in the “display” state are displayed as shown in FIG. Do not display classes that are not displayed. When the check is removed, all classes are displayed regardless of “display” or “not display”.

  In the class display by the class display unit 5 described above, when the software development support system is terminated and restarted, the developer must check the class to be displayed again and remove the check from the class not to be displayed. Don't be.

  In view of this, a class display history storage unit 6 is provided in the class list of the software development support system. The class display history storage unit 6 stores a “display” / “not display” setting history for each class in a database (storage medium). By preparing this class display history, when the class display unit 5 displays a list of classes, the class display unit 5 reads the class using the “display” / “not display” state for each class, and this class display history Restore state.

  Hereinafter, processing mainly related to the class display unit 5 and the class display history storage unit 6 will be described in detail.

  (1) A case where “display” and “not display” states of all classes in the class list are stored in a storage medium and read.

  FIG. 3A shows a class saving procedure. First, the number of classes in the class list is stored in a storage medium (S1), and it is checked whether there is a next class in the class list (S2). If there is a next class, the class (assumed to be A) is taken out from the class list. (S3), an identifier that can uniquely identify the class (A) is stored in the storage medium (S4), and the display state (“display” / “not display” state) of the class (A) is stored in the storage medium. (S5). These saving processes are repeated for all classes in the class list.

  FIG. 3B shows a class reading procedure. First, the number of classes is read from the storage medium (S6), and from this number of classes, it is checked whether there is a next class (S7). If there is, the following is repeated. First, the class identifier (assumed to be B) is read from the storage medium (S8), then the display status of the class “display” / “not display” (tentatively C) is read from the storage medium (S9). A class (assumed to be D) is acquired from the class identifier (B) (S10). If this class (D) exists, the display state (C) is set to it (S11), and if it does not exist, it is checked whether there is a next class.

  (2) When only the “display” class is stored in the storage medium and read.

  FIG. 4A shows a procedure for saving a “display” class. First, a class group to be “displayed” (assumed to be A) is obtained from the class list (S21), and the number of classes of the class group (A) to be displayed is stored in a storage medium (S22) and displayed. Check whether there is a next “display” class in the group (A) (S23), and if there is a next class, take out the next class (temporarily B) from the class group (A) (S24), An identifier that can uniquely identify (B) is stored in the storage medium (S25). These saving processes are repeated for all classes in the “display” class list.

  FIG. 4B shows a procedure for reading a “display” class. First, all classes in the class list are set to a “not display” state (S26), then the number of classes is read from the storage medium (S27), and from this number of classes, the next class is checked (S28). If so, repeat the following: First, a class identifier (tentatively C) is read from the storage medium (S29), and a class (tentatively D) is acquired from the class identifier (C) (S30). If this class (D) exists, a state of “display” is set for it (S31), and if it does not exist, it is checked whether there is a next class.

  (3) When only “not displayed” classes are stored in a storage medium and read.

  FIG. 5A shows a procedure for saving a class “not displayed”. First, a “not displayed” class group (assumed to be A) is acquired from the class list (S41), and the class number of the “not displayed” class group (A) is stored in the storage medium (S42), and the class not displayed. Check whether there is a next “not displayed” class in the group (A) (S43), and if there is a next class, take out the next class (temporarily B) from the class group (A) (S44), An identifier that can uniquely identify (B) is stored in the storage medium (S45). These saving processes are repeated for all classes in the “not displayed” class list.

  FIG. 5B shows a procedure for reading a “not displayed” class. First, all the classes in the class list are set to a “display” state (S46), then the number of classes is read from the storage medium (S47), and it is checked whether there is a next class from this class number (S48), If so, repeat the following: First, a class identifier (tentatively C) is read from the storage medium (S49), and a class (tentatively D) is acquired from the class identifier (C) (S50). If this class (D) exists, a “not display” state is set to it (S51), and if it does not exist, it is checked whether there is a next class.

  (4) In any of the above (1) to (3), when only the “display” class is checked for “display” at the end, only the classes in the “display” state are displayed, If not checked, all classes are displayed. Therefore, it is only possible to save / restore the “display” / “not display” state of each class in a specific situation. That is, only the last saved state can be restored.

  Therefore, the class display history storage unit 6 is provided with a function of storing each setting history in a storage medium with a name for each file. Further, a function is provided that reads a setting history by designating a name from the storage medium stored above and restores the class display based on the setting history.

  By adding these functions, the class saving procedure and reading procedure are realized by FIGS. 6 to 8, and compared to FIGS. 3 to 5, all of them are the same processing except that the name of the storage medium to be saved and read is designated. Become.

  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 so that the processing procedure of this method can be executed by a computer. can do.

The block diagram of the software development assistance system which shows embodiment of this invention. An example class list. Saving and loading the display state of all classes. Procedure for saving and loading the display state of the class to be displayed. Procedure for saving and loading the display state of classes not to be displayed. Saving and loading the display state of all classes (named). Procedure for saving and loading the display state of the class (named) to be displayed. Procedure for saving and loading the display status of classes (named) that are not displayed. An example of a UML class diagram. An example of a class list for a software development support system.

Explanation of symbols

1 UML diagram creation unit 2 Display 3 UML diagram screen component 4 UML diagram database 5 Class display unit 6 Class display history storage unit

Claims (7)

Software development that supports the creation, design, and implementation of the specifications of the system to be developed based on the UML diagram that represents each functional element using a combination of screen parts and characters defined in the Unified Modeling Language (UML) In the support system,
A UML diagram creation unit that creates a UML diagram including a class diagram based on object-oriented technology and stores it in a database;
List all classes in the class diagram saved in the database, and on this list display screen, you can set “display” / “not display” for each class, and check “Display” in this setting. A software development support system comprising a class display unit that displays only   When “display” and “not display” are set for each class by the class display unit, this setting history is stored in the database in a file format, and when the class display unit displays a class list, The software development support system according to claim 1, further comprising a class display history storage unit that restores a “display” / “not display” state for each class.   The class display history storage unit saves the setting history in which “display” / “not display” is set for each class with a name for each file when it is stored in the database, and designates the name for each file. 3. The software development support system according to claim 2, wherein the setting history is read and the class display is restored based on the setting history. Software development that supports the creation, design, and implementation of the specifications of the system to be developed based on the UML diagram that represents each functional element using a combination of screen parts and characters defined in the Unified Modeling Language (UML) In the support method,
A UML diagram creation step for creating a UML diagram including a class diagram based on object-oriented technology and storing it in a database;
List all classes in the class diagram saved in the database, and on this list display screen, you can set “display” / “not display” for each class, and check “Display” in this setting. And a class display step for displaying only the software development support method.   When “display” and “not display” are set for each class by the class display step, this setting history is stored in the database in a file format, and when the class display step displays a class list, 5. The software development support method according to claim 4, further comprising a class display history storage step for restoring a “display” / “not display” state for each class.   In the class display history saving step, the setting history in which “display” / “not display” is set for each class is saved in the database with a name for each file, and the name for each file is designated. 6. The software development support method according to claim 5, wherein the setting history is read and the class display is restored based on the setting history.   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