JP2003140894A - Relating method of software development resources, and program therefor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To specify a specification created in a downstream process relating to constitutional elements when the description of some constitutional elements in a program function relation drawing created in an upstream process is changed. SOLUTION: A specification creating part 102 creates various specifications 103 from a program function relation drawing 101. Then, a relational information creating part 107 creates relational information between each constitutional element of the program function relation drawing 101 and the corresponding specification 103, and between specifications, in which data input and output relationship exists, and stores the information in affected relational information 108. When some constitutional elements of the program function relation drawing 101 or the specification 103 is changed, a change affected analysis part 109 refers to the affected relation information 108, and specifies the specification or the constitutional elements to be changed and affected.

Description

Detailed Description of the Invention

[0001]

TECHNICAL FIELD The present invention relates to a software development support tool for associating software development resources.

[0002]

2. Description of the Related Art Information related to software development resources is
When a change occurs in a part of the resource, it is used to identify the part where the change spreads. As a conventional method for associating resources, there is a method in which related information is added in file units between a specification created in an upstream process and a specification created in a downstream process based on the specification. On the other hand, in Japanese Unexamined Patent Application Publication No. 10-105390, an identifier is given to each fine-grained item of the specifications created in each process, and a cross-reference table showing whether or not there is a relationship between these items is created. The technology for managing related information is described.

Many tools for supporting project management have been provided as means for managing the relationship between work items and workers. The main purpose of these tools is to manage information about the progress of the project, such as the work man-hours of each work item and the planned completion date.

[0004]

In the above method of managing the relationship between development resources on a file-by-file basis, when the specification of the upstream process is changed, all the specifications of the downstream process related thereto are related. It will be. Therefore, even if some components in the specifications of the upstream process are changed, all the specifications of the related downstream processes are subject to change in units of specifications, and only the specifications related to the components to be changed. Cannot be identified. Further, in the technique described in Japanese Patent Laid-Open No. 10-105390, the change spread analysis can be performed on the fine-grained items in the specification, but it is necessary to manually create the cross-reference table, and When the relation of is changed, it is necessary to manually recreate the cross reference table.

An object of the present invention is to solve the above problems.

[0006]

In order to solve the above problems, in the present invention, development resources are associated with each other by the method described below.

A program, data, and a display screen constituting a business system to be developed are used as constituent elements, and a diagram describing a data input / output relationship between these constituent elements is called a program function relation diagram. The program function relation diagram manages the data input / output relationships among the respective program elements, data elements, screen elements and constituent elements constituting the program function fine-grained items.

The specifications corresponding to these program elements, data elements and screen elements are managed as a program definition specification, a data definition specification and a screen definition specification, respectively.

According to the present invention, a relation is generated between the constituent elements constituting the program function relation diagram and the corresponding specifications among various specifications, and the related constituent elements are supported based on the above data input / output relation. Generate relationships between specifications
The generated related information is stored in the storage device.

When a fine-grained item having a program function relation diagram is changed, the related information is traced to extract a specification having a relation with the changed fine-grained item, and the result is output. To do. As a result, it is possible to identify the influence part due to the change in the program function relation diagram.

Further, when various specifications are changed, the above-mentioned related information is traced, and the fine-grained items of the program function relation diagram which are related to the changed specifications, and the changed specifications. The specifications that are related to each other are extracted and the result is output. As a result, it is possible to identify the spillover part associated with changes in various specifications.

[0012]

BEST MODE FOR CARRYING OUT THE INVENTION A method of associating software development resources according to a first embodiment of the present invention will be described below with reference to FIGS.

First, an outline of a method for associating resources will be described with reference to FIG. The details of each component will be described later. The program function relation diagram 101 is a program function relation diagram describing the configuration of the business system to be developed, and is created by the user. The normal program function relation diagram 101 is created in units such as each business. 103 is a program function related diagram 101
Of the program definition specifications 104 that define the detailed specifications of the program, the data definition specifications 105 that define the detailed specifications of the data, and the screen definition specifications 106 that define the screen design. It consists of each file. Diagram of program functions created in advance 1
When the specification generation unit 102 is executed with 01 as an input, various specifications 104, 105, and 106 based on the program, data, and screen outline specification information (name of each element, etc.) configuring the program function relation diagram 101. Is automatically generated. Each specification generated here shall be shared by multiple persons in charge of maintenance. In addition, the specification generation unit 1
Along with the specification generation by 02, the related information generation unit 107
Is executed. Each specification 104 generated by this
Correspondences between 106 and corresponding fine-grained items of the program function relation diagram 101 are stored in the spread relation information 108. Here, the fine-grained item is a program function-related diagram 1
Each program that is a component of 01, input / output data for the program, and an input / output screen for the program. A specific example will be described later. Further, with regard to the specifications 104 to 106 corresponding to the respective constituent elements for which data is passed in the program function relation diagram 101, the ripple relation is stored in the ripple relation information 108.

After the above processing is performed, the fine-grained items in the program function relation diagram 101 or the specifications 104 to 1
When the change is made to 06, the change spread analysis unit 109 retrieves a part related to the changed part from the spread relationship information 108, and outputs the result to the change spread list screen 110, so that the spread part associated with the change. You can get a list of. The person-in-charge information 111 is a list of persons in charge of maintaining the specifications. Each of the specifications 104 to 106 and the worker in charge of the program function relation diagram 101 are set on the worker setting screen 112, and information on the worker assignment is stored in the worker assignment information 113. By executing the person-in-charge notification processing unit 114, it is possible to notify the person in charge of the transmission destination obtained by the change transmission analysis unit 109 of the change transmission.

Next, with reference to FIG. 2, a hardware configuration of a computer that performs the processing of the embodiment will be described. The external storage device 201 is an external storage device that stores programs, and includes a specification generation unit 102 and a related information generation unit 10.
7. Change spread analysis unit 109 and person-in-charge notification processing unit 11
Each program of 4 is stored. The external storage device 202 is
An external storage device in which data used or generated by a program is stored.
Various specifications 103, ripple information 108, personnel information 1
11 and respective files of the assignment information 113 in charge are stored. Reference numeral 204 is a central processing unit, and 203 is a main memory. The display device 205 is a display device such as a CRT display, and the input device 206 is an input device such as a keyboard and a mouse.

The relationship between these devices at the time of execution will be described. When a program stored in the external storage device 201 is called, the content of the program is read into the main storage device 203 and executed by the central processing unit 204. When the program requires data stored in the external storage device 202, the data is read into the main storage device 203 and processed by the central processing unit 204 according to the instruction content of the program. The processing result of the program is displayed on the display device 205. When data is input by the user from the input device 206, the central processing unit 20 is operated according to the instruction content of the program.
In step 4, the input data is processed, and if necessary, the processing result of the central processing unit 204 is written to the corresponding file in the external storage device 202. The display device 205 and the input device 206 are the client computer side and the external storage device 2.
The system may be composed of a plurality of computers such that 01 and 202 are on the server computer side.

FIG. 3 is a schematic diagram for explaining an example of information managed in the program function relation diagram 101. Numerals 301 to 304 are programs, 305 to 307 are input / output data, and 308 to 312 are fine grain items representing display screens. Arrows 313 to 327 are fine grain items indicating that data is transferred between the fine grain item of the transition source and the fine grain item of the transition destination. An identifier for managing the propagation relation information 108 described later is attached to each fine-grained item. N01 to N1 for 301 to 312
The identifier 2 is attached. The identifiers E01 to E15 are attached to 313 to 327. Further, the entire program function relation diagram 101 is assigned an identifier A for managing the assignment information 113 to be described later.

FIG. 4 is an example of the program definition specification 104 created based on the program function relation diagram 101. The program definition specification 104 is created for each fine-grained item representing each program appearing in the program function relation diagram 101. Each specification has a program name,
Described are the input item representing the data used by the program, the output item representing the data output by the program, the input screen from which the program is called, and the name of the output screen to which the output result of the program is passed. Usually, detailed specifications of other programs are described, but illustration is omitted here. Program definition specifications 401, 402,
403 and 404 are program function related diagrams 10 respectively.
It is a specification created corresponding to the first program 301, 302, 303, 304. Further, each specification is attached with a specification identifier for use in the spread relation information 108.

FIG. 5 shows an example of the data definition specification 105 created based on the program function relation diagram 101. The data definition specification 105 is a program function related diagram 101.
It is created for each fine-grained item that represents each data that appears in. In each specification, a data definition name and a data definition type indicating a data storage format such as RDB or file are described. The form of the data schematized in FIG. 3 indicates the data type. Although detailed specifications of normal data are described in the data definition specification 105, illustration is omitted here. The data definition specifications 501, 502, and 503 are input / output data 30 of the program function relation diagram 101, respectively.
5, 306 and 307 are specifications created in correspondence with each other. Further, each specification is attached with a specification identifier for use in the spread relation information 108.

FIG. 6 is an example of the screen definition specification 106 created based on the program function relation diagram 101. The screen definition specification is created for each fine-grained item representing each screen appearing in the program function relation diagram 101. The screen name and the next screen name are described in each specification. Other screen specifications are described in detail, but not shown here. Screen definition specifications 601, 602, 603, 6
04 and 605 are program function related diagrams 101, respectively.
It is a specification created in correspondence with the screens 308, 309, 310, 311, 312. Further, each specification is attached with a specification identifier for use in the spread relation information 108.

In order to automatically generate various specifications 103 from the program function relation diagram 101 created in advance, the specification generation unit 102 is executed. FIG. 7 shows an example of a flowchart of the specification generation unit 102. The flowchart will be described below. For the fine-grained item NP representing the program of the program function relation diagram 101 (step 70
1), the following steps 702 to 707 are repeated. First, a program definition specification P corresponding to NP is newly created (step 702), and the name of P, an input screen and an output screen are set (step 703). In the program function relation diagram 101, if there is a data input relationship from the fine-grained item NDI to NP representing certain input data (YES in step 704), the NDI name is set in the P input item (step 705). In the program function relation diagram 101, if there is a data output relationship from the NP to the fine-grained item NDO that represents certain output data (YES in step 706), the name of the NDO is set in the output item of P (step 707). Next, each fine grain item N representing the data of the program function relation diagram 101
For D (step 708), a data definition specification D corresponding to ND is newly created (step 709), and the name and data type of D are set according to the description content of ND (step 710). Step 709 for each ND
And 710 are repeated. Next, program function related diagram 10
For the fine-grained item NG representing the screen of 1 (step 71
1) The following steps 712 to 715 are performed. First, a screen definition specification G corresponding to NG is newly created (step 712), and the name of G is set (step 71).
3). Next, for the screen transition from NG (Step 71
4), the name of the transition destination screen is set in the next screen (step 715).

The specifications 104 shown in FIGS. 4, 5 and 6,
Reference numerals 105 and 106 are related to the program function shown in FIG.
01 is a specification generated in accordance with the flowchart example of the specification generation unit 102 shown in FIG. 7.

Next, using the processing result of the specification generation unit 103, the related information generation unit 107 which is a program for generating the spread relation information 108 will be described. FIG. 8 shows a flowchart example of the related information generating unit 107. The flowchart will be described below. First, for the fine-grain item N representing the constituent elements of the program function relation diagram 101 (step 801), S is a specification created from N (step 802), and the relation from N to S is generated (step 803). The association is expressed by associating N identifiers with S identifiers. Step 80 for each N
Repeat steps 2 and 803. Next, program function related diagram 1
For the fine-grained item E representing the data transfer relation of 01 (step 804), the specification created from the fine-grained item on the side of passing the E data is F (step 805), and the detail on the side of receiving the E data. When the specification created from the granularity item is T (step 806), a relation from F to T is generated (step 807). The association is expressed by associating the identifier of F with the identifier of T. Repeat steps 805, 806 and 807 for each E.

FIG. 9 shows the spread relation information 108 generated by the example of the flow chart of the relation information generating unit 107 shown in FIG. 8 from the program function relation diagram 101 and various specifications 103. Each transmission relation information is composed of an association source ID representing an identifier of a fine-grained item or a specification document of the program function relation diagram 101 which is an association source, and an association destination ID representing an identifier of a specification document which is an association destination. References 901 to 912 are the relationships from the fine-grained items 301 to 312 of the program function relation diagram 101 to the corresponding specifications. Reference numerals 913 to 927 are relationships between specifications corresponding to the fine-grained items 313 to 327 in the program function relationship diagram 101.

Next, a change ripple analysis method in the case where a part of the program function relation diagram 101 is changed will be described.
FIG. 10 is an example of a flowchart of the change spread analysis unit 109 when a part of the program function relation diagram 101 is changed. The flowchart will be described below. First, N is set as the identifier of the fine-grained item in the changed program function relation diagram 101 (step 1001). Next, the ripple relation information having N as the relation origin ID is searched from the ripple relation information 108, and is set as the relation destination r (step 1002). r
There is one. Finally, the related destination ID of r is output as the changed ripple portion of N (step 1003). As a result, it is possible to identify the change influence part when the relation source N is changed.

As an example, consider a case where the program 302, which is a fine-grained item in the program function relation diagram 101, is changed. At this time, the program 302 output by the flowchart of the change ripple analysis unit 109 shown in FIG.
The changed spread part of (product search) becomes the specification 402 by associating from the spread relation information of 902.

Next, a change ripple analysis method when the specification is changed will be described. FIG. 11 is an example of a flowchart of the change spread analysis unit 109 when various specifications are changed. The flowchart will be described below. First, the empty set is substituted for I to initialize I (step 11
01). Next, S is used as the identifier of the changed specification (step 1102), S is used as the relation destination ID, and the relation origin ID is the fine-grained item of the program function relation diagram 101. A search is performed and it is set as a relation source r (step 1103). There is one r. Further, N is set as the relation source ID of r (step 110).
4), N is added to I (step 1105). Then S
For all the propagation relation information other than r including as the relation source ID or the relation destination ID (step 1106), the relation source ID or the relation destination ID that is not S is added to I (step 1107). Finally, I is output as a changed ripple portion of S (step 1108). As a result, it is possible to identify the change influence part when S is changed.

As an example, consider the case where the specification 402 is changed. At this time, the change ripple analysis unit 109 shown in FIG.
The changed ripple portion of the specification document 402 output by the flowchart of FIG. 3 is the program 302 by tracing the identifier from the ripple relation information of 902, 918, 919, and 920.
(Product search), specifications 603 (product search screen), specifications 502 (product information), and specifications 604 (list output screen).

The change spread parts output by the change spread analysis unit 109 are displayed in a list on the change spread list screen 110.

Next, the function of notifying the person in charge of each specification belonging to the change spread portion of the change spread will be described. FIG. 12 is an example of the person-in-charge information 111. 1201-12
Reference numeral 06 is information on each person in charge, which is composed of a person in charge identifier and a name. The person-in-charge information 111 is created in advance by the user.

FIG. 13 is an example of the assignment assignment information 113 set via the assignment setting screen 112. 1301
Information 131313 is information on assignment in charge, and is composed of an identifier representing a program function relation diagram or a specification and a worker identifier representing a worker in charge of the work.

The person-in-charge notification processing unit 114 is a program for notifying the worker in charge of each change-spreading portion output by the change-spreading analysis unit 109 that a change has been made.
FIG. 14 shows a flowchart example of the person-in-charge notification processing unit 114. The flowchart will be described below. For the specification identifier i, which is each change spread part output by the change spread analysis unit 109 (step 1401), the person identifier p of i is obtained from the assigned assignment information 113 (step 1
402), referring to the person-in-charge information 111, the person in charge corresponding to p is notified of the change spread (step 1403).

As an example, FIG. 15 shows the correspondence between the specification identifier, which is the change spreading part extracted from the change spreading analysis unit 109 and the assigned assignment information 113 when the specification 402 is changed, and the person in charge identifier. 1501 to 1504 are assigned assignment information extracted from 1303, 1307, 1311, and 1312, respectively.

As a method of realizing the notification means to the person in charge,
By linking with a mail system, there is a method in which when a change occurs, an email is automatically sent to the worker in charge of each change spread part. As a result, the person in charge of the change influence can be automatically notified of the change influence.

Next, a method for associating software development resources according to the second embodiment of the present invention will be described with reference to FIGS.

First, the outline of the method for associating resources according to the second embodiment will be described with reference to FIG. Second
In the embodiment, a program function relation diagram creation unit 115 is added instead of each specification generation unit 102 in FIG. The user creates a program function relationship diagram 101 by picking up a specification group to be used from the various specification documents 103 created in advance and executing the program function relationship diagram creation unit 115 with them.

FIG. 17 shows an example of a flow chart of the program function relation diagram creating section 115. The flowchart will be described below. First, for each specification selected by the user (step 1701), a fine-grained item P of the program function relation diagram corresponding thereto is created (step 1702). That is, the name of each specification is associated with the assigned fine-grained item identifier. Next, for each program definition specification P selected by the user (step 1703), the following steps 1704 to 1714 are performed. First, the fine-grained item P created in step 1702
The identifier corresponding to is set to NP (step 1704).
Next, if DI is set in the P input item (YES in step 1705), the fine-grained item corresponding to the DI created in step 1702 is set to NDI (step 1706), and the data input relationship from NDI to NP is set. Create (step 1707). If DO is set in the output item of P (YES in step 1708), the fine-grained item corresponding to the DO created in step 1702 is set to NDO (step 1709), and a data output relationship from NP to NDO is created. (Step 1710). Furthermore, when GI is the input screen of P and NGI is the fine-grained item corresponding to the GI created in step 1702 (step 1
711), a data input relationship from NGI to NP is created (step 1712). Similarly, GO to P output screen,
When the NGO is the fine-grained item corresponding to the GO created in step 1702 (step 1713), NP to N
Create a data output relationship to GO (step 171)
4).

The process after creating the program function relation diagram 101 is the same as that of the first embodiment.

[0039]

According to the present invention, the constituent elements in the program function relation diagram are utilized by utilizing the related information between the constituent elements in the program function relation diagram and each specification and the person in charge of each work. When each or each specification is changed, the affected part can be detected, and the person in charge of each affected part can be automatically notified of the change.

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration of an embodiment.

FIG. 2 is a hardware configuration diagram of a computer according to the embodiment.

FIG. 3 is a diagram showing an example of a program function relation diagram 101.

FIG. 4 is a diagram showing an example of a program definition specification 104.

5 is a diagram showing an example of a data definition specification 105. FIG.

6 is a diagram showing an example of a screen definition specification 106. FIG.

FIG. 7 is a diagram showing an example of a flowchart of a specification generation unit 102.

FIG. 8 is a diagram showing an example of a flowchart of a related information generation unit 107.

FIG. 9 is a diagram showing an example of spread relation information 108.

FIG. 10 is a diagram showing an example of a flowchart of a change spread analysis unit 109 when a part of the program function relation diagram is changed.

FIG. 11 is a diagram showing an example of a flowchart of a change spread analysis unit 109 when various specifications are changed.

FIG. 12 is a diagram showing an example of person-in-charge information 111.

FIG. 13 is a diagram showing an example of assignment assignment information 113.

FIG. 14 is a diagram showing an example of a flowchart of a person-in-charge notification processing unit 114.

FIG. 15 is a diagram showing an example of the correspondence between a changed spread portion and its worker.

FIG. 16 is a block diagram showing a configuration of a second exemplary embodiment of the present invention.

FIG. 17 is a diagram showing an example of a flowchart of a program function relation diagram creation unit 115.

[Explanation of symbols]

101 ... Program function relation diagram, 102 ... Specification generation unit, 104 ... Program definition specification document, 105 ... Data definition specification document, 106 ... Screen definition specification document, 107 ... Related information generation unit, 108 ... Ripple relation information, 109 ... Change spread analysis unit, 111 ... Person information, 113 ... Assignment information, 1
14 ... Personnel notification processing unit, 115 ... Program function relation diagram creation unit

Continued front page    (72) Inventor Toshiya Chiba             1099 Ozenji, Aso-ku, Kawasaki City, Kanagawa Prefecture             Ceremony company Hitachi Systems Development Laboratory (72) Inventor Takeo Ishii             5030 Totsuka Town, Totsuka Ward, Yokohama City, Kanagawa Prefecture             Ceremony company Hitachi Ltd. software division (72) Inventor Kei Fujii             5030 Totsuka Town, Totsuka Ward, Yokohama City, Kanagawa Prefecture             Ceremony company Hitachi Ltd. software division F term (reference) 5B076 DD00 DD02 EC00 EC07 EC08

Claims (5)

[Claims] 1. A method of associating software development resources from a program function relationship diagram stored in a storage device and various specifications, wherein the program function relationship diagram is a program constituting a business system to be developed. , Data and display screens are defined as constituent elements, and data input / output relationships between the constituent elements are described. The various specifications are created in correspondence with the programs, data, and display screens. A program definition specification, a data definition specification, and a screen definition specification are included, and a relationship is generated between the constituent elements forming the program function relation diagram and a corresponding specification among the various specifications, and the data is generated. A relationship may be generated between specifications corresponding to the related component based on the input / output relationship, and the generated related information may be stored in a storage device. The association process between the software development resources, wherein. 2. When the specification of any of the constituent elements of the program function relation diagram is changed, the specification information corresponding to the changed constituent element is extracted with reference to the related information. And outputs the result, and when any one of the specifications is changed, the constituent element corresponding to the specification changed and the specification changed and The method for associating software development resources according to claim 1, wherein the specifications having a relationship are extracted based on a data input / output relationship and the result is output. 3. The assignment specification information for recording the correspondence between the specification sheet and a worker in charge thereof and the related information are referred to, and the specification sheet to be changed is associated with the data input / output relationship. 3. The method for associating software development resources according to claim 2, wherein the identifier of the worker in charge corresponding to the specification is extracted and the result is output. 4. A program for causing a computer to execute association between software development resources from a program function relation diagram stored in a storage device and various specifications, wherein the program function relation diagram is a development target. The programs, data, and display screens that make up the business system are defined as components, and the data input / output relationship between the components is described. The various specifications correspond to the programs, data, and display screens. Including the program definition specifications, the data definition specifications and the screen definition specifications created by the computer, and the computer corresponding to the constituent elements constituting the program function related diagram and the corresponding specifications among the various specifications. A procedure for generating a relation between the two, and a specification corresponding to the related component based on the data input / output relationship Program for executing a procedure for storing instructions to generate a link between, and the generated related information to the storage device. 5. When the specification of any of the constituent elements of the program function relation diagram is changed in the computer, the specification corresponding to the constituent element changed with reference to the related information. A procedure for extracting a document and outputting the result, and when any of the specifications of the specification is changed, the component corresponding to the specification that is changed with reference to the related information and the changed 5. The program according to claim 4, for executing a procedure of extracting the specification having a relationship based on the data input / output relationship with the specification and outputting the result.