JP5984358B2 - Software development support apparatus and program - Google Patents

Description

  The present invention relates to technology for supporting software development.

  For example, in the design of LSI (large scale integration) and the like, design support technology that integrates specifications creation, source code creation, and test specification creation tools so that they can exchange data with each other has been known. (For example, Patent Document 1).

Japanese Patent Laid-Open No. 2003-6250

  By the way, when software development is performed by a function addition type method, a developer (user) needs to work while being aware of the relationship with other functions (specifications). However, the actual situation is that no effective proposal has yet been made for a technology that supports software development by, for example, presenting the relationship between the function to be created and other functions in an easy-to-understand manner.

  The present invention has been made in view of the above circumstances, and an object of the present invention is to provide a software development support apparatus and the like that presents a relationship between functions in a manner that can be easily understood by a user in software development. To do.

In order to achieve the above object, a software development support apparatus according to the present invention provides:
An input unit for receiving an operation from the user;
Specification information on the specifications of each function that constitutes the software to be developed. When the corresponding function is executed, if it is restricted by the relationship with other functions, the execution restriction condition is the condition. A specification storage unit for storing specification information including
A specification management unit that manages specification hierarchy information indicating a hierarchical relationship of the specification information stored in the specification storage unit;
In accordance with a predetermined operation by the user, the specification information stored in the specification storage unit is read out, and between the functions based on the execution constraint condition extracted from the read specification information and the specification hierarchy information A controller that generates specification system diagram screen data representing the relationship and outputs it to a predetermined display device;
The control unit is a screen including an area in which a description about the function can be described by the user when a specification information creation request operation for a specific function is performed by the user after the specification system diagram screen data is output. Then, the specification information creation screen data incorporating the execution constraint condition extracted from the specification information corresponding to the function shared by the function and the parent is generated and output to the display device.

  According to the present invention, since the specification system diagram showing the relationship between each function is displayed, it is possible to improve work efficiency and quality in software development.

It is a block diagram which shows the structure of the software development assistance apparatus which concerns on Embodiment 1 of this invention. It is a figure for demonstrating a precondition, (a) and (b) show the dependency between functions, (c) shows the exclusive relationship between functions. It is a figure for demonstrating a specification hierarchy relationship, (a) shows the relationship of "A has-a B", (b) shows the relationship of "B is-a A". It is FIG. (1) which shows an example of a specification system diagram screen. It is a figure which shows an example of a hierarchy relationship designation | designated screen. It is FIG. (2) which shows an example of a specification system diagram screen. It is FIG. (1) which shows an example of a specification creation screen. It is FIG. (2) which shows an example of a specification creation screen. It is FIG. (3) which shows an example of a specification system diagram screen. It is a figure which shows an example of a line | wire type list. It is FIG. (4) which shows an example of a specification system diagram screen. It is a flowchart which shows the procedure of a specification creation assistance process. It is a block diagram which shows the structure of the software development assistance apparatus which concerns on Embodiment 2 of this invention. It is FIG. (1) which shows an example of a specification-mounting system diagram screen. It is FIG. (2) which shows an example of a specification-mounting system diagram screen. It is FIG. (1) which shows an example of an implementation code creation screen. It is FIG. (2) which shows an example of an implementation code creation screen. It is FIG. (3) which shows an example of an implementation code creation screen. It is a flowchart which shows the procedure of an implementation code creation assistance process. It is a block diagram which shows the structure of the software development assistance apparatus which concerns on the modification of Embodiment 2. It is a figure which shows an example of the specification preparation screen in other embodiment. It is a figure which shows an example of the detailed specification system diagram screen in other embodiment.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

Embodiment 1. FIG.
FIG. 1 is a block diagram showing a configuration of a software development support apparatus 1 according to Embodiment 1 of the present invention. The software development support apparatus 1 is an apparatus that assists the creation of specifications (functional specifications) by a user, particularly when software development is performed by a function addition type method.

  The hardware configuration of the software development support apparatus 1 is the same as that of a general personal computer. That is, although none of the software development support apparatus 1 is shown in the figure, a control apparatus comprising a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), etc., a readable / writable nonvolatile semiconductor It includes an external storage device composed of a memory, a hard disk drive, etc., an input device composed of a keyboard, a mouse, a keypad, a touch pad, a touch panel, etc., a display device composed of a CRT, a liquid crystal monitor, and the like. Each process (details will be described later) executed by the software development support device 1 is realized by a CPU or the like executing a predetermined program stored in a ROM or an external storage device.

  Functionally, the software development support apparatus 1 includes an input unit 10, a display unit 11, a specification storage unit 12, a specification management unit 13, and a control unit 14, as shown in FIG.

  The input unit 10 receives an input operation from the user and sends a signal related to the received input operation to the control unit 14.

  The display unit 11 displays a screen for user operation such as a specification system diagram screen described later under the control of the control unit 14.

  The specification storage unit 12 stores information (specification information) in which specification contents (main body unit), preconditions, and postconditions are associated with each function constituting software to be developed. In the specification information, an ID (specification ID) for uniquely identifying each specification information is allocated by the control unit 14.

  The precondition refers to a condition that is a precondition for executing the function (specification). In the present embodiment, the precondition includes a dependency relationship and an exclusive relationship. Dependency is, for example, a case of referring to data managed by another function (specification), a case of executing the function after execution of another function, and a combination of other functions (in parallel) Cases to be executed are applicable. Further, in the present embodiment, the dependency relationship between functions is represented as (a) and (b) in FIG. FIG. 2A shows that the function A depends on the function B (for example, the function A is executed after the function B is executed). FIG. 2B shows that the function B depends on the function A (for example, the function B is executed after the function A is executed).

  In addition, being in an exclusive relationship means a case in which one function cannot be executed while one function is being executed. When the execution requests for both functions compete, either one is preferentially executed based on a predetermined priority condition. In this embodiment, the exclusive relationship between functions is represented as shown in FIG. FIG. 2C shows that the functions A and B are in an exclusive relationship and cannot be executed at the same time.

  The post condition refers to a condition that is established after the function is executed (for example, 1 ° C. is added to the set temperature after the function is executed).

  The specification management unit 13 holds information (specification hierarchy information) indicating the hierarchical relationship between the specification information stored in the specification storage unit 12.

  As shown in FIG. 3, the specification hierarchy relationship employed in the present embodiment has two patterns, which are represented by marks that are determined in advance according to each pattern. FIG. 3A shows the relationship “A has-a B”. That is, B (child) belongs to A (parent) or B (child) is a part of A (parent). For example, the relationship of A: piano and B: keyboard corresponds to this.

  FIG. 3B shows the relationship “B is-a A”. That is, B (child) indicates that A (parent) is inherited. In other words, it can be said that A is a generalization of B and B is a specialization of A. For example, the relationship of A: musical instrument and B: piano corresponds to this.

  The specification management unit 13 accesses the specification storage unit 12 according to a request from the control unit 14, and reads and writes the specification information. In addition, the specification management unit 13 updates the specification hierarchy information as necessary, for example, when new specification information is written.

  When the user performs an operation for requesting the display of the specification system diagram screen via the input unit 10, the control unit 14 requests the specification management unit 13 to read the specification information. And the control part 14 is the specification showing the relationship between each function (each specification) based on the precondition contained in each specification information read by the specification management part 13, and said specification hierarchy information. Create system diagram screen data. Based on the generated specification system diagram screen data, the control unit 14 causes the display unit 11 to display a specification system diagram screen 401 as shown in FIG. In FIG. 4, it is assumed that the number added to each “specification” indicates the specification ID of the specification information.

  From this specification system diagram screen 401, it can be seen that the highest specification is specification 0, and specifications 1, specification 2 and specification 3 exist as its children. It can also be seen that specification 0 and specification 1, specification 0 and specification 2, and specification 0 and specification 3 all have a relationship of “A has-a B” (see FIG. 3A).

  Specification 1 has three children of specifications 1.1, 1.2, and 1.3, and has a relationship of “B is-a A” (see FIG. 3B). The specification 1.1 and the specification 1.2 are in an exclusive relationship (FIG. 2C).

  The specification 2 has two children of the specifications 2.1 and 2.2, and has a relationship of “A has-a B” (see FIG. 3A). Further, the specification 2.1 is in a relationship depending on the specification 2.2 (see FIGS. 2A and 2B).

  The specification 3 has two children of the specification 3.1 and the specification 3.2, and each has a relationship of “A has-a B” (see FIG. 3A). In addition, the specification 3.1 and the specification 3.2 are in an exclusive relationship (FIG. 2C). Furthermore, the specification 3.2 is in a relationship depending on the specification 2.2 (see FIGS. 2A and 2B).

  The control unit 14 displays the specification system diagram screen 401 in a GUI (Graphical User Interface) mode. Thus, the user can select a specification corresponding to the “specification n” as a processing target by clicking the icon 402 indicating the desired “specification n” using a mouse or the like.

  A new addition button 403 is used when a new function (specification) is added. When the user presses the new addition button 403, the control unit 14 displays a message prompting the user to select a parent specification. After the message is displayed, when the user selects and clicks on the icon 402 indicating the parent “specification n”, the control unit 14 causes the selected “specification n” to be added. Determine to be the parent of

  When the parent specification is selected, the control unit 14 pops up a screen (hierarchy relationship designation screen 501) for causing the user to designate a hierarchical relationship as shown in FIG. Let

  The user can specify a hierarchical relationship with the parent specification by performing an operation of selecting either the radio button 502 or 503 via the input unit 10. For example, when it is desired to specify the hierarchical relationship of “parent has-a child”, the user may perform an operation of selecting the radio button 502. On the other hand, when it is desired to specify the hierarchical relationship of “child is-a parent”, the user may perform an operation of selecting the radio button 503.

  When the user presses the OK button 504, the control unit 14 acquires the user's specification result, determines the hierarchical relationship between the previously selected parent specification and the current additional specification, and determines the determination result. This is reflected in the specification system diagram screen 401. An example of the specification system diagram screen 401 after reflection is shown in FIG.

  The specification system diagram screen 401 in FIG. 6 shows that “specification 3” is selected as the parent specification by the user and “parent has-a child” is selected as the hierarchical relationship. Shows an added example. Further, the icon 402 corresponding to the newly added “specification 3.3” is highlighted in such a manner that it can be distinguished from other icons 402 such as gray display.

  In the specification system diagram screen 401 of FIG. 6, when the user performs a predetermined operation requesting display of the specification creation screen (for example, the icon 402 corresponding to the newly added “specification 3.3” is double-clicked with the mouse or the like). Then, the control unit 14 picks up a child (“Specification 3.1”, “Specification 3.2”) whose parent is common with “Specification 3.3”, and from the corresponding specification information, Extract conditions and post-conditions. Then, the control unit 14 causes the display unit 11 to display a specification creation screen 701 (see FIG. 7) incorporating the extraction result.

  As shown in FIG. 7, the specification creation screen 701 includes a precondition setting area 702, a main body area 703, and a postcondition setting area 704. In the precondition area 702, the contents of the precondition extracted from the specification information of other children with a common parent are displayed, and check boxes corresponding to the respective preconditions are provided. In this example, “specification 3.2 and exclusive execution” which is a precondition of the specification information corresponding to “specification 3.1” is displayed, and a check box 7020 corresponding to this is provided. Also, “specification execution with specification 3.1” and “execution after completion of specification 2.2” which are preconditions of the specification information corresponding to “specification 3.2” are displayed, and check boxes 7021 and 7022 is provided.

  Further, a check box 7023 corresponding to “Others” is provided so that conditions other than the pre-conditions extracted from other children can be set, and an input area 7024 is provided for the user to directly enter the text. It has been.

  The main body area 703 is provided with an input area 7030 in which the user can directly enter the contents of the specification (text input) and an OK button 7031 for confirming the user's operation contents and closing the specification creation screen 701. It has been.

  In the post-condition setting area 704, the contents of the post-conditions extracted from the specification information of other children shared by the parent are displayed, and check boxes corresponding to the post-conditions are provided. In this example, for example, “set temperature = original set temperature + 1 ° C.”, which is a post condition of the specification information corresponding to “specification 3.1”, is displayed, and a check box 7040 corresponding to this is provided. Furthermore, a check box 7041 corresponding to “Others” is provided so that conditions other than the post-conditions extracted from other children can be set, and an input area 7042 for allowing the user to directly enter the contents is provided. ing.

  When the user presses the OK button 7031, the control unit 14 acquires and holds each setting and input result in the precondition setting area 702, the main body section area 703, and the postcondition setting area 704, and the precondition The relationship between specifications (functions) obtained from the setting results in the setting area 702 and the post-condition setting area 704 is reflected on the specification system diagram screen 401. For example, in the specification creation screen 701, when the user sets a precondition as shown in FIG. 8, the reflected specification system diagram screen 401 is as shown in FIG.

  In addition, the user can set a relationship (relation) between functions via the specification system diagram screen 401. An example of the setting method in this case will be described. For example, when the user performs a predetermined operation (for example, right mouse click) on the specification system diagram screen 401, the control unit 14 displays a line type list 1001 as shown in FIG. To specify a desired line type (1: “---->” or 2: “<---->”). Here, when the user wants to set the dependency relationship, the user selects the first line type, and when he wants to set the exclusive relationship, the user selects the second line type. In the line types 1 and 2, the left side is the starting point (specifications to be created or updated, such as newly added specifications), and the right side is the end point (other specifications for which a relationship is to be set).

  When the specification of the line type is completed, the user selects two “specifications n” for which a relationship is desired to be set. For example, the user selects two icons 402 indicating different “specifications n” by a so-called drag operation using a mouse or the like. In addition, the user first selects the icon 402 corresponding to “specification n” desired to be the starting point, and next (last) the icon 402 corresponding to “specification n” desired to be the end point. Specifically, for example, in the setting of the dependency relationship, when it is desired to set a condition “specification 3.3 is executed after completion of specification 1.3”, the user selects one line type as a starting point. Specification 1.3 may be selected with specification 3.3 as the end point. A specification system diagram screen 401 reflecting the selection result in this case is as shown in FIG.

  Further, when the user wants to set a condition that “specification 3.3 is exclusive with specification 2.1”, the user selects two line types, uses specification 3.3 as the starting point, and specification 2 as the end point. .1 should be selected.

  When the user presses the OK button 404 on the specification system diagram screen 401, the control unit 14 sets the contents (dependency relationship and exclusive relationship) set on the specification system diagram screen 401 and the specification document creation screen 701. The input content is reflected in the specification information corresponding to the related specification. At this time, if it is a new addition, the control unit 14 newly creates specification information and additionally stores it in the specification storage unit 12. In addition, the control unit 14 updates the specification hierarchy information via the specification management unit 13.

  Naturally, when an exclusive relationship is set in a newly added specification, the content of other already created specification information is also changed.

  FIG. 12 is a flowchart illustrating a procedure of a process for supporting the creation of a specification (specification creation support process) by the software development support apparatus 1 having the above configuration. When an operation for requesting display of the specification system diagram screen 401 is performed by the user (step S101; YES), the control unit 14 corresponds to each function (each specification) corresponding to each specification information stored in the specification storage unit 12. Create specification system diagram screen data showing the relationship between the two. And the control part 14 displays the specification system diagram screen 401 (refer FIG. 4) on the display part 11 based on the produced specification system diagram screen data (step S102).

  If any operation is performed on the specification system diagram screen 401 by the user (step S103; YES) and this is a pressing operation of the new addition button 403 (step S104; YES), the control is performed. The unit 14 accepts selection of the parent specification from the user (step S105). Next, the control unit 14 accepts designation of a hierarchical relationship with the selected parent specification from the user (step S106). Then, the control unit 14 causes the display unit 11 to redisplay the specification system diagram screen 401 reflecting the newly added specification (step S102).

  When the screen operation by the user is a display request operation on the specification creation screen 701 (step S107; YES), the control unit 14 picks up a child having a common parent with the specification to be created, and specification information corresponding to each of them. From the above, preconditions and postconditions are extracted. And the control part 14 displays the specification preparation screen 701 (refer FIG. 7) incorporating the extraction result on the display part 11 (step S108).

  If the user performs a predetermined operation (in this case, pressing operation of the OK button 7031) during the display of the specification creation screen 701 (step S109; YES), the control unit 14 inputs the user. The result and the like are acquired and held, and the specification system diagram screen 401 reflecting the setting results of the precondition setting area 702 and the postcondition setting area 704 is displayed again on the display unit 11 (step S102).

  When the screen operation by the user is a setting operation related to the function (step S111; YES), the control unit 14 accepts designation of the relationship between the functions from the user (step S112). Specifically, as described above, a line type list 1001 as shown in FIG. 10 is displayed, and the user is allowed to specify a desired line type.

  When the association between functions is specified by the user, the control unit 14 receives from the user selection of a plurality of specifications that are targets for setting the association between functions (step S113). For example, the user can select these specifications by a so-called drag operation using a mouse or the like. The control unit 14 causes the display unit 11 to redisplay the specification system diagram screen 401 reflecting the result of the user's operation as described above (step S102).

  When the screen operation by the user is a pressing operation of the OK button 404 on the specification system diagram screen 401 (step S111; NO), the control unit 14 executes an end process (step S114). Specifically, the content set on the specification system diagram screen 401 and the content set and input on the specification creation screen 701 are reflected in the corresponding specification information.

  As described above, according to the software development support apparatus 1 of the present embodiment, when creating a specification in software development, the existing (created) system of specifications (functions) and the mutual relationship are provided to the user. Provide an easily understandable environment. Therefore, the efficiency of creating the specification can be improved. As a result, the development period can be shortened, and further improvement in quality can be expected.

  In addition, since an intuitive operation environment is provided to the user via the specification system diagram screen 401, convenience is improved and work efficiency can be further improved.

  In addition, when adding a new specification, execution constraints such as pre- and post-conditions of other specifications that are strongly related, such as the same parent, are automatically extracted as candidates for execution constraints in the additional specification. Can be presented to the user. Then, the user can set execution constraint conditions in the additional specification only by selecting a desired one from the presented candidates. For this reason, the workability in creating the specifications is significantly improved.

  When deleting an existing specification, the user may select an icon 402 indicating “specification n” to be deleted on the specification system diagram screen 401 and then press the delete key such as a keyboard. In this case, first, the icon 402 indicating the “specification n” is deleted from the specification system diagram screen 401, and the line indicating the relationship between the functions starting from the “specification n” or the end point is also deleted. When the user presses the OK button 404, the specification information corresponding to the “specification n” is deleted from the specification storage unit 12, and the specification hierarchy information is updated accordingly. Furthermore, the setting contents of the precondition and postcondition of other related specification information are also updated.

Embodiment 2. FIG.
FIG. 13 is a block diagram showing a configuration of a software development support apparatus 1A according to the second embodiment of the present invention. This software development support apparatus 1A has functions equivalent to those of the software development support apparatus 1 of the first embodiment, that is, a program code (implementation code) according to a predetermined program language, in addition to a function for supporting the creation of specifications by the user. It also has a function to assist the creation.

  As shown in FIG. 13, in addition to the configuration of the software development support apparatus 1, the software development support apparatus 1A includes a mounting code storage unit 15, a template storage unit 16, a mounting management unit 17, and a specification-mounting correspondence management unit 18. And further comprising. In the software development support device 1A, the control unit 14 of the software development support device 1 is changed to a control unit 14A.

  The mounting code storage unit 15 stores a mounting code for realizing the function for each function (that is, each specification). Further, a program code (function code) in units of one or a plurality of functions (modules) constituting each function is also stored. An ID (mounting ID) for uniquely identifying each mounting code is assigned to the mounting code by the control unit 14A.

  The template storage unit 16 stores a plurality of patterns of a framework (model) code (hereinafter referred to as a skeleton code) common to a plurality of mounting codes.

  The mounting management unit 17 holds information (mounting layer information) indicating the hierarchical relationship between the mounting codes. The mounting management unit 17 accesses the mounting code storage unit 15 or the template storage unit 16 according to a request from the control unit 14A, and reads and writes the mounting code or the skeleton code. Further, the mounting management unit 17 updates the mounting hierarchy information as necessary, for example, when a new mounting code is written in the mounting code storage unit 15.

  The specification-mounting correspondence management unit 18 manages the association between the specification information stored in the specification storage unit 12 and the mounting code stored in the mounting code storage unit 15. The specification-mounting correspondence managing unit 18 holds the specification-mounting correspondence information in which the specification ID assigned to the specification information is associated with the mounting ID assigned to the mounting code. The specification-mounting correspondence management unit 18 updates the specification-mounting correspondence information as necessary, such as when specification information or a mounting code is newly added.

  14 A of control parts can perform the process equivalent to the control part 14 of Embodiment 1, and perform various processes for assisting a user with the implementation code creation. For example, when an operation for requesting display of a specification-implementation system diagram screen is performed by the user via the input unit 10, the control unit 14A creates specification-implementation system diagram screen data and creates the created specification-implementation screen Based on the system diagram screen data, a specification-implementation system diagram screen 1401 as shown in FIG.

  In the specification-implementation system diagram screen 1401, the part indicating the system of specifications (specification system diagram) is the same as the specification system diagram shown in the specification system diagram screen 401 described in the first embodiment. Further, in the portion (mounting system diagram) indicating the system of mounting (mounting code), “n” of the icon 1403 indicating “mounting n” indicates the mounting ID of the corresponding mounting code. Note that the specification ID and the mounting ID are assigned separately, and may be the same in the upper hierarchy, but the ID given by the corresponding specification and the implementation is not necessarily common in the lower hierarchy. Not always. Also, the hierarchical relationship is often different between specifications and implementation. In order to make this point easy to understand, in the specification-mounting system diagram screen 1401, a solid line arrow (specification-mounting corresponding line) clearly shows the correspondence between the specifications of the lower hierarchy and the mounting.

  14 A of control parts are based on the mounting hierarchy information which the mounting management part 17 hold | maintains, and the specification-mounting correspondence information which the specification-mounting correspondence management part 18 hold | maintain, and said specification-mounting corresponding line Create data to display.

  The specification-implementation system diagram screen 1401 allows the user to easily understand the correspondence between the specification and the implementation code. In addition, the control unit 14A, for the icon 1402 corresponding to the newly added specification (specification 3.3 in this example) via the specification system diagram screen 401, displays other icons 1402 such as gray display. It highlights in a way that can be distinguished from it. As a result, the user can confirm the specifications that are newly added and the corresponding implementation code has not been created. In addition to the new addition, the icon 1402 corresponding to the updated specification is also displayed separately from the other icons 1402 so that it can be understood.

  A new addition button 1404 is used when a new implementation (implementation code) is added. When the user presses the new addition button 1404, the control unit 14A displays a message that prompts the user to select the implementation of the parent (one higher hierarchy). After the message is displayed, when the user selects and clicks on the icon 1403 indicating the parent “implementation n”, the control unit 14A adds the selected “implementation n” to the implementation. Determine to be the parent of

  When the parent specification is selected, the control unit 14 displays a message prompting the user to select the corresponding specification. After the message is displayed, when the user selects and clicks the corresponding icon 1402 indicating “specification n”, the control unit 14A causes the selected “specification n” to be added this time. It is determined that the specification is corresponding.

  When the user selects the parent of the newly added mounting and the corresponding specification as described above, the control unit 14A redisplays the specification-mounting system diagram screen 1401 reflecting these results. . For example, when “implementation 3” is selected as the parent of the newly added implementation by the user and “specification 3.3” is selected as the corresponding specification, the specification-implementation system diagram screen 1401 is displayed in FIG. Redisplayed as shown.

  In the specification-implementation system diagram screen 1401 of FIG. 15, when the user performs a predetermined operation for requesting the display of the implementation code creation screen (for example, the icon 1403 corresponding to the newly added “implementation 3.3” is displayed by the mouse or the like). When double-clicked), the control unit 14A reads the specification information of “specification 3.3” corresponding to this from the specification storage unit 12. Then, the control unit 14A causes the display unit 11 to display a mounting code creation screen 1601 (see FIG. 16) incorporating the contents of the read specification information.

  As shown in FIG. 16, the implementation code creation screen 1601 includes a code input area 1602 and an OK button 1603. The code input area 1602 is an area where the user can input (code) a program code according to a predetermined program language using a keyboard, a mouse, or the like. When displaying the implementation code creation screen 1601, the control unit 14 </ b> A preliminarily describes various information based on the content of the specification information of the corresponding specification (for example, “specification 3.3”) in the code input area 1602 in a comment format. Keep it. Thus, if the contents of the corresponding specifications are described in advance, the efficiency of the programming work and the improvement of the accuracy can be achieved.

  For example, as shown in FIG. 16, a temporary name such as “implementation code of implementation n” (n is an implementation ID) is described as the name (implementation name) of the implementation code. In addition, the contents of the precondition of the corresponding specification are described. Then, the content of the main body is described, and the content of the postcondition is described.

  In addition to the above-described example, the control unit 14 </ b> A also has a child (“Implementation 1.3”, “Implementation 2.2”, “Implementation 3”) whose parent is common to the newly added implementation (for example, “Implementation 3.3”). .1 ”and“ Implementation 3.2 ”), the skeleton code may be read from the template storage unit 16 and the content of the code may also be described (FIG. 17). reference). Or, if the implementation code that is a common child or the implementation code of the parent shares part of the function name or the arguments (type, name) are the same, describe them in advance. Alternatively, refer to FIG. As described above, when the mounted code creation screen 1601 is displayed, the actual code contents are also described in advance, thereby further improving the efficiency of the user's programming work.

  FIG. 19 is a flowchart showing a procedure of processing (implementation code creation support processing) that supports creation of the implementation code by the software development support device 1A.

  When an operation for requesting display of the specification-implementation system diagram screen is performed by the user (step S201; YES), the control unit 14A is related to each function corresponding to each specification information stored in the specification storage unit 12. Create specification system diagram data that represents In addition, the control unit 14 </ b> A creates mounting system diagram data that represents the relationship between the mounting codes stored in the mounting code storage unit 15. Then, the control unit 14A displays a specification-mounting system diagram screen 1401 (see FIG. 14) on the display unit 11 based on the created specification system diagram data and mounting system diagram data (step S202).

  When any operation is performed on the specification-implementation system diagram screen 1401 by the user (step S203; YES), and this is a pressing operation of the new addition button 1404 (step S204; YES). The control unit 14A accepts selection of the parent implementation from the user (step S205). Next, the control unit 14A receives a selection of a specification corresponding to the mounting to be added from the user (step S206). Then, the control unit 14A causes the display unit 11 to re-display the specification-mounting system diagram screen 1401 reflecting the newly added mounting (step S202).

  If the screen operation by the user is a display request operation for an implementation code creation screen (step S207; YES), implementation code creation incorporating the content of the specification information of “specification n” corresponding to “implementation n” selected by the user A screen 1601 (see FIGS. 16 to 18) is displayed on the display unit 11. When “implemented n” that has already been created is selected, the control unit 14A reads the implemented code corresponding to the “implemented n” from the implemented code storage unit 15, and stores the contents in the code input area 1602 The mounting code creation screen 1601 described in (1) is displayed.

  If the user performs a predetermined operation (in this case, pressing the OK button 1603) during the display of the mounting code creation screen 1601 (step S209; YES), the control unit 14A performs input by the user. The result (programming result) is acquired (step S210), and the implementation code creation screen 1601 is closed. And control part 14A performs processing of Step S203 again.

  When the screen operation by the user is a pressing operation of the OK button 1405 on the specification-implementation system diagram screen 1401 (step S207; NO), the control unit 14A executes an end process (step S211). Specifically, when “implementation n” is newly added, the implementation code corresponding to the “implementation n” is additionally stored in the implementation code storage unit 15 via the specification management unit 13, and the implementation hierarchy information Update. Alternatively, when the content of the existing mounting code is changed on the mounting code creation screen 1601, the control unit 14A overwrites and saves the mounting code reflecting the changed content in the mounting code storage unit 15.

  As described above, according to the software development support apparatus 1A of the present embodiment, the specification (implementation system diagram) screen 1401 is displayed, so that the specification (function) can be displayed to the user when creating the implementation code in software development. Provide an environment in which the system, existing system code, and the correspondence between specifications and implementation can be easily understood. Therefore, the efficiency of creating the mounting code can be improved.

  Also, the user can set a newly added mounting hierarchy and a correspondence relationship with the specification through an intuitive operation via the specification-mounting system diagram screen 1401. Therefore, convenience is good.

  In addition, in the implementation code creation screen 1601 for the newly added implementation, the contents of the corresponding specification information are described in advance in the code input area 1602, and the code contents that are common among other related implementation codes are described in advance. The user can efficiently perform programming work.

  When deleting an existing implementation, the user may select an icon 1403 indicating “implementation n” to be deleted on the specification-implementation system diagram screen 1401, and then press the delete key such as a keyboard. In this case, first, the icon 1403 indicating “mounting n” is deleted from the specification-mounting system diagram screen 1401. The corresponding specification-mounting correspondence line is also deleted. When the user presses the OK button 1405, the mounting code corresponding to the “mounting n” is deleted from the mounting code storage unit 15, and the mounting hierarchy information is also updated accordingly.

(Modification)
A software development support apparatus 1B shown in FIG. 20 is a modification of the software development support apparatus 1A of the second embodiment. This software development support apparatus 1B has not only a function for assisting creation of specifications and creation of implementation codes, but also a function for assisting creation of test cases.

  The test case storage unit 19 stores a test case for each mounting code. An ID (test case ID) for uniquely identifying each test case is allocated to the test case by the control unit 14B. The test case management unit 20 holds information (test hierarchy information) indicating the hierarchical relationship between test cases. The test case management unit 20 accesses the test case storage unit 19 according to a request from the control unit 14B, and reads and writes the test case. Further, the test case management unit 20 updates the test hierarchy information as necessary, for example, when a new test case is written in the test case storage unit 19.

  The mounting-test case correspondence management unit 21 manages the association between the mounting code stored in the mounting code storage unit 15 and the test case stored in the test case storage unit 19. The mounting-test case correspondence management unit 21 holds mounting-test case correspondence information in which the mounting ID assigned to the mounting code and the test case ID assigned to the test case are associated with each other. The mounting-test case correspondence management unit 21 updates the mounting-test case correspondence information as necessary, for example, when a mounting code or a test case is newly added.

  The control unit 14B can execute processing equivalent to that of the control unit 14A, and also executes various processing for supporting test case creation by the user. For example, the control unit 14B causes the display unit 11 to display an unillustrated mounting-test case system diagram screen in response to a request from the user. On this mounting-test case system diagram screen, a mounting system diagram and a diagram (test case system diagram) showing the system of the test case are displayed, and the correspondence between the lower level implementation and the test case is displayed. Make it explicit.

  Further, the control unit 14B displays a test case creation screen (not shown) for allowing the user to describe (set) the contents of the test case. The user can create a new test case or update or delete an existing test case via the mounting-test case system diagram screen or the test case creation screen.

  Further, according to this software development support device 1B, a range to be affected by a change in a specification or a place where an implementation is applied is acquired, and based on the acquisition result, a corresponding test item is extracted, and a test to be performed This range can be presented to the user. Therefore, it is possible to efficiently perform test work accompanying changes in specifications and mounting.

  The present invention is not limited to the above-described embodiments, and various modifications can be made without departing from the scope of the present invention.

  For example, when creating a specification, a specification creation screen 2101 as shown in FIG. 21 may be displayed instead of or in combination with the specification creation screen 701 (see FIG. 7). The specification creation screen 2101 includes a title display area in which a specification ID and a function name are displayed, a precondition area, a postcondition area, a main body area, and a button arrangement area.

  The precondition area and the postcondition area are areas in which the user can directly enter the contents. The main body area is an area for a user to draw a flowchart, an activity diagram by UML (Unified Modeling Language), and the like. In the example shown in FIG. 21, the main body area is an area for drawing a flowchart showing the specification. In this example, the main body area is realized by executing a graphics drawing software program that supports, for example, the SVG (Scalable Vector Graphics) format.

  The user tags a predetermined keyword (in this example, a function name and a data name) when inputting the precondition area and the postcondition area. For example, a tag “<<>” is attached to the function name, such as << function 1 >>. In addition, a tag “<$$>” is attached to the data name, such as <$ data $>. Similarly, in each figure (branch, process) in the main body area, the user tags the function name and the data name. In the main body area, the user further attaches predetermined headers to the precondition and the postcondition. For example, “PR:” is added as a header to the precondition, and “PS:” is added to the postcondition. Further, when indicating an exclusive relationship, “EX:” is further added as a header. For example, when an exclusive relationship is described in the precondition, “PR: EX: exclusive condition 1” is obtained.

  Note that keyword tagging and cancellation may be performed, for example, by a predetermined operation. For example, when a desired keyword is dragged by the user, it is displayed in reverse video. In this state, a “Ctrl + F” operation is performed to add a function name (“<< >>”) tag, Alternatively, a data name (<$ data $>) tag may be automatically assigned by performing a “Ctrl + D” operation. Further, the user may place a cursor in the tagged keyword and perform “Ctrl + R” to remove the tag from the keyword. In addition, the control unit 14 or the like displays a menu screen in a predetermined format, and executes processing corresponding to the selected item when a user selects a desired item (for example, “tagging keywords”). You may make it do.

  As described above, when the user performs a pre-condition, post-condition, input in each area of the main body, and drawing, and then pressing the check button 2102 in the button arrangement area, the control unit 14 or the like It is determined whether or not the input results in the precondition area and the postcondition area are consistent with the input contents in each figure in the main body area.

  For example, the control unit 14 or the like compares the keyword included in the input content (input text) in the precondition area with the keyword with “PR:” included in the input content in each figure in the main body area. Check whether there is no excess or deficiency. In addition, the control unit 14 compares the keyword included in the input content of the post-condition area with the keyword with “PS:” included in the input content in each figure of the main body area, and both are excessive or insufficient. Check if there is no.

  In any of the checks, if there is no excess or deficiency, the control unit 14 or the like displays a message such as “matching is OK” on the display unit 11 assuming that the matching is achieved. On the other hand, if there is an excess or deficiency in any of the checks, the control unit 14 or the like causes the display unit 11 to display an error message indicating that the matching is not achieved. At this time, for example, “There is a missing precondition regarding <$ data A $>!” May be displayed so that the content of the error can be specifically understood.

  After the above check, when the user presses the OK button 2103 in the button arrangement area, the control unit 14 and the like acquire and hold preconditions, postconditions, input contents of each area of the main body, and the like. At the same time, the acquired contents are reflected on the specification system diagram screen 401. Note that when the cancel button 2104 in the button arrangement area is pressed, all user input contents are discarded (invalidated).

  As described above, the description contents of the specification can be checked, so that the workability can be improved and the omission of specification description and the occurrence of contradiction can be prevented, so that the quality can be improved. .

  There are also various ways of displaying the specification system diagram. For example, as in a detailed specification system diagram screen 2201 shown in FIG. 22, a plurality of related specifications (functions) may be displayed in such a manner that the contents can be understood. For example, the detailed specification system diagram screen 2201 is transitioned to when the user selects an icon 402 indicating a desired specification (function) on the specification system diagram screen 401 and performs a predetermined operation.

  The detailed specification system diagram screen 2201 of FIG. 22 is displayed when the specification (function 3) with the ID of 1.3 is selected by the user on the specification system diagram screen 401 and a predetermined operation is performed. To do. When such an operation is performed, the control unit 14 and the like extract the related function (specification) using the function name in function 3 and the data name as keywords. Then, for each extracted function, the function name and the data name are used as keywords, and further related functions are extracted. Further, as will be described later, a transition can be made from the detailed specification system diagram screen 2201 to the specification creation screen 2101. In that case, when an editing operation is performed by the user on the transitioned specification creation screen 2101 and the OK button 2103 is pressed, the editing content is confirmed and the screen transitions to the detailed specification system diagram screen 2201 again. At this time, the control unit 14 and the like extract related functions in the same manner as described above.

  Hereinafter, a case where the function name is extracted as a keyword will be described. The control unit 14 or the like checks the function name that appears in each item of each condition from the description of the precondition and the postcondition. When a plurality of function names appear, related candidate pairs are extracted by the number of combinations. In the example of FIG. 22, the precondition for function 3 describes that “<< function 1 >> and << function 2 >> are not executed” while << function 3> is being executed. Accordingly, the control unit 14 and the like extract function 3 and function 1, function 3 and function 2, and function 1 and function 2 as association candidate pairs. And the control part 14 grade | etc., Displays a connection as shown in FIG. 22 for every pair.

  Here, the control unit 14 or the like determines whether the relationship is a dependency relationship or an exclusive relationship based on the tagged keyword of the main body unit or the header information indicating the exclusive relationship, and determines the line type to be connected. draw. Thereby, for example, connection lines 2202 to 2204 indicating the exclusive relationship are drawn. In the above extraction method of association candidate pairs, an unintended pair (function 1 and function 2) is extracted, and as a result, an unnecessary connection 2204 is drawn between function 1 and function 2. Suppose that it can be deleted appropriately by a connection changing operation by the user. Further, in the case of the dependency relationship, the direction of the arrow of the arrow line is indefinite (the user decides later), and as illustrated in FIG.

  When the data name is extracted as a keyword, the control unit 14 or the like uses a function having the same data name as at least one of the precondition and the postcondition as an association candidate pair.

  In addition, about the location of a connection, the control part 14 grade | etc., Draws so that a line may come out from the area | region (precondition, postcondition) to which the keyword used as the factor which determines the connection belongs. If both preconditions and postconditions exist, the preconditions take precedence.

  Further, the control unit 14 and the like on the detailed specification system diagram screen 2201 display a pop-up menu by right-clicking on a predetermined operation by the user (for example, on the description of the function to be edited, and selecting specification editing from there). ) Is displayed, a corresponding specification creation screen 2101 is displayed. As a result, the user can edit the function contents and check the consistency of the description contents on the specification creation screen 2101. When the OK button 2103 is pressed on the specification creation screen 2101 and the editing content is confirmed, the screen returns to the detailed specification system diagram screen 2201. At this time, the control unit 14 and the like extract the related functions described above. The connection display between related functions is performed again. In some cases, a new relationship may occur due to a specification update. In such a case, the user opens the specification creation screen 2101 again to review the newly related functions and displays the contents. Edit, check and confirm. In this way, the overall specifications are determined sequentially.

  In this way, the detailed specification system diagram screen 2201 is displayed, so that the user can easily grasp the relationship between each function, and follow the relationship to create a specification for the function that needs to be reviewed. Since the screen 2101 is opened, the contents of the function (specification) can be edited and the consistency of the description contents can be checked, the workability can be improved, and the omission of specification description and inconsistencies can be prevented. As a result, quality can be improved.

  Also, by applying the program executed by the software development support apparatus 1, 1A, 1B of the above embodiment to an existing personal computer (PC) or the like, the PC can function as the software development support apparatus according to the present invention. Is also possible.

  Such a program distribution method is arbitrary, for example, a computer-readable recording medium such as a CD-ROM (Compact Disk Read-Only Memory), a DVD (Digital Versatile Disk), an MO (Magneto Optical Disk), or a memory card. It may be stored and distributed in a network, or distributed via a communication network such as the Internet.

  Various embodiments and modifications can be made to the present invention without departing from the broad spirit and scope of the present invention. Further, the above-described embodiment is for explaining the present invention, and does not limit the scope of the present invention. That is, the scope of the present invention is shown not by the embodiments but by the claims. Various modifications within the scope of the claims and within the scope of the equivalent invention are considered to be within the scope of the present invention.

DESCRIPTION OF SYMBOLS 1, 1A, 1B Software development support apparatus 10 Input part 11 Display part 12 Specification memory | storage part 13 Specification management part 14, 14A, 14B Control part 15 Implementation code memory | storage part 16 Template memory | storage part 17 Implementation management part 18 Specification-implementation management part 19 Test Case Storage Unit 20 Test Case Management Unit 21 Implementation-Test Case Correspondence Management Unit

Claims (7)

An input unit for receiving an operation from the user;
Specification information on the specifications of each function that constitutes the software to be developed. When the corresponding function is executed, if it is restricted by the relationship with other functions, the execution restriction condition is the condition. A specification storage unit for storing specification information including
A specification management unit that manages specification hierarchy information indicating a hierarchical relationship of the specification information stored in the specification storage unit;
In accordance with a predetermined operation by the user, the specification information stored in the specification storage unit is read out, and between the functions based on the execution constraint condition extracted from the read specification information and the specification hierarchy information A controller that generates specification system diagram screen data representing the relationship and outputs it to a predetermined display device;
The control unit is a screen including an area in which a description about the function can be described by the user when a specification information creation request operation for a specific function is performed by the user after the specification system diagram screen data is output. A software development support apparatus that generates specification information creation screen data incorporating the execution constraint condition extracted from the specification information corresponding to the function shared by the function and the parent, and outputs it to the display device. An input unit for receiving an operation from the user;
Specification information on the specifications of each function that constitutes the software to be developed. When the corresponding function is executed, if it is restricted by the relationship with other functions, the execution restriction condition is the condition. A specification storage unit for storing specification information including
A specification management unit that manages specification hierarchy information indicating a hierarchical relationship of the specification information stored in the specification storage unit;
In accordance with a predetermined operation by the user, the specification information stored in the specification storage unit is read out, and between the functions based on the execution constraint condition extracted from the read specification information and the specification hierarchy information A control unit that generates specification system diagram screen data representing the relationship and outputs it to a predetermined display device;
A mounting code storage unit that stores a mounting code corresponding to each of the functions;
A mounting management unit that manages mounting hierarchy information indicating a hierarchical relationship of mounting codes stored in the mounting code storage unit;
A specification-mounting correspondence management unit that manages the specification-mounting correspondence information indicating the correspondence between the specification information stored in the specification storage unit and the mounting code stored in the mounting code storage unit; Prepared,
The control unit generates mounting system diagram data representing a hierarchical relationship of each mounting code stored in the mounting code storage unit based on the mounting hierarchy information in response to a predetermined operation by a user. A software development support apparatus that generates specification-implementation system diagram screen data obtained by combining the specification system diagram screen data and outputs the generated data to the display device. After the output of the specification-implementation system diagram screen data, the control unit accepts an operation for selecting a parent implementation code from the user when a user performs a new implementation addition request operation, and the specification-implementation The software development support apparatus according to claim 2 , wherein the received result is reflected in the system diagram screen data and then output to the display device again. After the output of the specification-implementation system diagram screen data, the control unit, when a creation request operation for a specific implementation code is performed by the user, an implementation code creation screen including an area where the implementation code can be described by the user The software development support device according to claim 2 or 3 , wherein data is generated and output to the display device. Wherein, when generating the implementation code creation screen data, in a region which can be described implementation code by the user, describing the contents of the specification information of the corresponding functions in a predetermined manner, according to claim 4 Software development support device. Computer
An input unit that receives operations from the user,
Specification information on the specifications of each function that constitutes the software to be developed. When the corresponding function is executed, if it is restricted by the relationship with other functions, the execution restriction condition is the condition. Specification storage unit for storing specification information including
A specification management unit that manages specification hierarchy information indicating a hierarchical relationship of the specification information stored in the specification storage unit;
In accordance with a predetermined operation by the user, the specification information stored in the specification storage unit is read out, and between the functions based on the execution constraint condition extracted from the read specification information and the specification hierarchy information Generate specification system diagram screen data representing the relationship, function as a control unit that outputs to a predetermined display device,
The control unit is a screen including an area in which a description about the function can be described by the user when a specification information creation request operation for a specific function is performed by the user after the specification system diagram screen data is output. A program that generates specification information creation screen data incorporating the execution constraint condition extracted from the specification information corresponding to the function shared by the function and the parent, and outputs the screen to the display device. Computer
An input unit that receives operations from the user,
Specification information on the specifications of each function that constitutes the software to be developed. When the corresponding function is executed, if it is restricted by the relationship with other functions, the execution restriction condition is the condition. Specification storage unit for storing specification information including
A specification management unit that manages specification hierarchy information indicating a hierarchical relationship of the specification information stored in the specification storage unit;
In accordance with a predetermined operation by the user, the specification information stored in the specification storage unit is read out, and between the functions based on the execution constraint condition extracted from the read specification information and the specification hierarchy information A control unit that generates specification system diagram screen data representing the relationship and outputs it to a predetermined display device,
A mounting code storage unit for storing a mounting code corresponding to each function;
A mounting management unit that manages mounting hierarchy information indicating a hierarchical relationship of mounting codes stored in the mounting code storage unit;
Functions as a specification-mounting correspondence management unit that manages the specification-mounting correspondence information indicating the association between the specification information stored in the specification storage unit and the mounting code stored in the mounting code storage unit Let
The control unit generates mounting system diagram data representing a hierarchical relationship of each mounting code stored in the mounting code storage unit based on the mounting hierarchy information in response to a predetermined operation by a user. A program that generates specification-implementation system diagram screen data obtained by combining the specification system diagram screen data and outputs the screen to the display device.

Images