JP2009289129A - Method, device, system and program for supporting software development - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To prevent design information in an upstream process from being affected by design information which is registered against the order of processes. <P>SOLUTION: A method for supporting software development, by managing design information in a software development support device is provided. A storage section of the software development support device stores reference relation schema information, defining the correspondence between the design information in the upstream process and design information in a downstream process, and alternate identification attribute information for estimating the correspondence relationship among design information pieces. When design information is input into the software development support machine, reference source design information corresponding to the input design information is identified, on the basis of the reference relationship schema information; and when the reference source design information cannot be identified, the reference source design information is estimated, on the basis of the alternate identification attribute information, the consistency between the input design information and the estimated reference source design information or identified reference source design information is determined, and then the input design information is registered, on the basis of the determination result of the consistency. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a technology that supports software development, and more particularly to a technology that supports software development in a large-scale project that requires a large number of people and processes.

  In a large-scale project involving a plurality of developers, development work is generally advanced based on a design document and a specification change sheet created in advance. Since each developer works independently of each other, there is a possibility that the design information of the downstream process is generated or changed prior to the design information of the upstream process. In order to cope with such a case, there has been proposed a technique for guaranteeing consistency with design information of an upstream process and a downstream process that are affected when certain design information is generated or changed.

  For example, in the technology disclosed in Patent Document 1, when related information between design information is acquired and managed, and there is a change in the design information, the developer is flagged with other related design information. Notify and provide design information that may change.

Further, in the technique disclosed in Patent Document 2, a common part of a plurality of design information is extracted and centrally managed, and when there is a change in the design information, the common part that is centrally managed is changed. , Automatically reflect the change and support the specification change.
JP-A-5-35460 JP 2006-79212 A

  The techniques disclosed in Patent Document 1 and Patent Document 2 distinguish design information from upstream processes or downstream processes having some relationship (for example, a reference utilization relationship) with design information when certain design information is generated or changed. However, it is assumed that both will be affected and will be subject to consistency guarantee. Therefore, the value of the design information of the upstream process that is the relation source (reference source) is changed to the value after the change by the change of the design information of the downstream process that is the relation destination (use destination) (in the case of Patent Document 2, automatically) In addition, in the case of Patent Document 1, there is a possibility of being overwritten unjustly (due to a work mistake).

  In addition, it is not possible to recognize the consistency state between the design information registered against the process order and the inconsistency factor when the inconsistency occurs.

  An object of the present invention is to provide a technique for ensuring consistency when design information is registered against a process order.

  In one form of the present invention, a software development support method for managing design information in a software development support device, the software development support device comprising a processor and a storage unit connected to the processor, the storage unit Includes reference relationship schema information that defines the correspondence between the design information of the upstream process and the design information of the downstream process, and alternative identification attribute information for estimating the correspondence between the design information, and the method includes: When the design information is input, the reference source design information corresponding to the input design information is specified based on the reference relation schema information, and the reference source design information cannot be specified, the alternative Based on the identification attribute information, the reference source design information is estimated, the input design information and the estimated reference source design information or the specified Determining consistency between Terumoto design information, on the basis of the consistency determination result, and registers the design information the input.

  According to an exemplary embodiment of the present invention, the consistency between the input design information and the reference source design information is determined, and the reference source design information is inappropriately influenced based on the consistency determination result. Design information can be registered so as not to give

  In the embodiment of the present invention, in the field of software, system design, development, and maintenance, when the downstream process is changed before the completion of the change process of the upstream process, the downstream process design information and Based on the registered definition information, related upstream design information is extracted or estimated. Thereafter, it is determined whether or not the related upstream process design information is added or updated, and whether or not the added or updated upstream design information is consistent with the related downstream design information. When matched, the downstream process is considered to have been officially changed.

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

(First embodiment)
FIG. 1 is a diagram showing a configuration of a software development support system 100 according to the first embodiment of this invention.

  The software development support system 100 according to the first embodiment of this invention includes a CPU 101, a memory 102, and an external interface 103, which are connected to each other via a bus 108.

  The CPU 101 executes business processing by processing a program stored in the memory 102. The memory 102 stores a program processed by the CPU 101 and data used when the program is processed.

  The external interface 103 connects the input / output device and the like to the CPU 101 and the memory 102. Specifically, an input device 104, an output device 105, a communication device 106, and an external storage device 107 are connected to the external interface 103.

  The input device 104 receives input from the user. The output device 105 outputs information requested by the user, processing results requested by the user, and the like. The communication device 106 is connected to an external device. For example, it is a network interface card (NIC) and is connected by another device via a network.

  The external storage device 107 stores programs and information used in the software development support system 100. The external storage device 107 is, for example, a nonvolatile storage medium.

  The programs stored in the external storage device 107 are a design information registration program 110, a reference source estimation program 111, a consistency state confirmation program 112, a state information notification program 113, a forced registration review program 114, and a reference source change confirmation program 115. . As described above, these processing programs are read into the memory 102 at the time of execution and executed by the CPU 101.

  Further, the external storage device 107 includes a design information storage unit 120 and a relationship information storage unit 130. The design information storage unit 120 and the relationship information storage unit 130 may be stored in an external storage device different from the program described above. For example, in the case of large-scale system development, the design information to be stored may be enormous, and may be stored separately in the storage device. Alternatively, a database server on which the database management system operates may be prepared separately, and the data stored in the design information storage unit 120 and the relationship information storage unit 130 may be managed.

  The design information storage unit 120 stores design information input from the outside via the input device 104. The design information is first written in the non-public design information 121 of the design information storage unit 120 of the external storage device 107. The public design information 122 stores design information whose consistency has been confirmed. The registration status information 123 stores information indicating the status of the registered design information. Specifically, it is a normal registration registered in a state in which the design information is guaranteed to be consistent with the upstream process or a forced registration registered in an inconsistent state.

  The relationship information storage unit 130 stores relationship information such as a reference relationship of design information. Specifically, the reference relationship schema definition and the alternative identification attribute definition are input from the outside via the input device 104 and are written in the reference relationship schema definition information 131 and the alternative identification attribute definition information 132, respectively. Further, the relationship information storage unit 130 stores reference relationship instance information 133, consistency state information 134, and forced registration review target information 135.

  The reference relationship instance information 133 stores information storing a combination of the identification attribute of the design information of the upstream process actually used by reference and the identification attribute of the design information of the usage destination. The consistency state information 134 stores information indicating the consistency between the design information of the reference source and the design information of the usage destination. The forced registration review target information 135 stores design information for which consistency is not guaranteed because of forced registration.

  Here, an outline of processing executed by each processing program will be described.

  The design information registration program 110 generates reference relationship instance information based on the design information read from the non-public design information 121 and the reference relationship schema definition information read from the reference relationship schema definition information 131. Further, the generated reference relationship instance information is written in the reference relationship instance information 133 of the relationship information storage unit 130.

  When the design information of the reference source of the reference relation instance information generated from the design information is unknown, the design information registration program 110 calls the reference source estimation program 111.

  Based on the design information read from the non-public design information 121 and the alternative identification attribute definition information read from the alternative identification attribute definition information 132, the reference source estimation program 111 has an unknown reference of the reference relationship instance information. The original design information is estimated, and the result is written together with the estimated value flag as the value of the design information of the reference source in the reference relation instance information 133.

  In addition, the design information registration program 110 executes the consistency state confirmation program 112. The consistency state confirmation program 112 compares the version or value of the design information of the reference source and the usage destination for the reference relation instance information read from the reference relation instance information 133, and matches the result as the consistency state between the reference relation instances. Write in the status information 134.

  The design information registration program 110 also includes design information, reference relationship instance information (including an external key of design information), and consistency state information (from the private design information 121, the reference relationship instance information 133, and the consistency state information 134). These three types of information are combined using the design information external key.

  At this time, the design information registration program 110 executes design information release by normal registration or design information release by forced registration.

  The disclosure of design information by normal registration is performed when the design information is “consistent state = consistent”. Specifically, “registration state = normal registration” is written in the registration state information 123 of the design information storage unit 120 together with the identification attribute value of the design information of the usage destination, and the design information of the usage destination is disclosed to the design information storage unit 120. Copy to design information 122.

  In addition, the design information is released by compulsory registration when “consistency state = inconsistency” of design information, “estimated value flag = NO” of design information of the reference source of the reference relation instance information, and version relation of design information Is performed when “reference source <use destination”. Specifically, “registration state = forced registration” is written to the registration state information 123 of the design information storage unit 120 together with the value of the identification attribute of the design information of the usage destination, and the forced registration review target information 135 of the relationship information storage unit 130 is written. The reference relation instance information is written together with the forced registration review condition, and the design information of the usage destination is copied to the public design information 122 of the design information storage unit 120. If inconsistency occurs because the design information of the reference source has not been registered, the "registration condition for forced registration = when the reference source is added", the design information of the reference source has been registered, but inconsistency If it has occurred, it is assumed that “revision condition for forced registration = when the reference source is updated”.

  The forced registration review program 114 executes the reference source change confirmation program 115 when a forced registration review request command is input from the outside. The reference source change confirmation program 115 reads the forced registration review target information from the forced registration review target information 135. At this time, when “forced registration review condition = when reference source is added”, the reference source estimation program 111 is executed to estimate the reference relationship instance information from the latest design information. If the reference source design information has been added, the forced registration review program 114 further executes the consistency state confirmation program 112.

  On the other hand, the forced registration review program 114 confirms whether or not the design information of the reference source has been updated from the latest design information in the case of “the review condition of forced registration = when the reference source is updated”. If the design information of the reference source has been updated, the forced registration review program 114 further executes the consistency state confirmation program 112. The consistency status confirmation program 112 confirms the consistency status between the reference relationship instances. If “consistency status = consistency”, the “registration status =” in the registration status information 123 corresponding to the design information of the usage destination of the reference relationship instance. Update to “Register”. Furthermore, the forced registration review target information of the forced registration review target information 135 corresponding to the design information of the usage destination of the reference relationship instance is deleted.

  When the design information registration is completed, compulsory registration review is completed, and when a status information reference request command is input from the outside, the status information notification program 113 receives the design information registration result, compulsory registration review result, design Information registration status information, reference relationship instance consistency status information, and forced registration review target information are output to the outside via the output device 105.

  FIG. 2 is a flowchart showing overall processing of the software development support system 100 according to the first embodiment of this invention.

  The software development support system 100 has a design information registration function, a forced registration review function, and a design information reporting function.

  First, the CPU 101 determines whether or not the process requested by the user is a design information registration request (step 200). If the process requested by the user is a design information registration request (the result of step 200 is “YES”), a design information registration process is executed (step 201). Here, for example, an external software developer can input the design information registration request at an arbitrary timing. Further, one or more pieces of design information to be registered can be designated by any method such as list designation and range designation. Details of the design information registration process will be described later with reference to FIG.

  On the other hand, when the process requested by the user is not a design information registration request (the result of step 200 is “NO”), the CPU 101 requests to review the design information forcibly registered the process requested by the user. It is determined whether or not (step 202). If the process requested by the user is a forced registration review request (the result of step 202 is “YES”), the forced registration review process is executed (step 203). Here, the forced registration review request can be input, for example, by an external software developer or project manager at an arbitrary timing or at a predetermined periodic timing. Further, one or more pieces of design information subject to a forced registration review request can be designated from the outside by any method such as list designation or range designation. Details of the forced registration review process will be described later with reference to FIG.

  Further, when the process requested by the user is not a forced registration review request (the result of step 202 is “NO”), the CPU 101 determines whether or not it is a status information reference request (step 204). . If the process requested by the user is a status information reference request (the result of step 204 is “YES”), status information reporting is executed (step 205). Here, the reference request for the state information can be input by an external software developer or project manager at an arbitrary timing or at a predetermined periodic timing, for example.

  In addition, status information reporting refers to registration status information for one or more design information specified by a user, consistency status information of a reference relationship instance for which the design information is a reference source or a destination, This is a process for outputting forcibly registered review target information having the value of the identification attribute of design information as an external key to the outside. In status information reporting, it is possible to output various information values as they are, or to output the number of cases where the various information values satisfy a certain condition.

  When the process requested by the user is not a request for referring to the state information (the result of step 204 is “NO”), the CPU 101 waits for an input from the user. When the design information registration process (step 201), the forced registration review process (step 203), or the status information reporting process (step 205) is completed, it is determined whether a program termination request command has been input from the user. (Step 206). If a program end request command is input (the result of step 206 is “YES”), this process ends. If the program end request command has not been input (the result of step 206 is “NO”), the input from the user is awaited.

  Next, a procedure for registering design information will be described in detail with reference to the flowchart of FIG.

  FIG. 3 is a flowchart illustrating a procedure of design information registration processing according to the first embodiment of this invention.

  The CPU 101 writes the edited design information input from the outside via the input device 104 into the non-public design information 121 by the design information registration program 110 (step 300). An external software developer may connect to the software development support system 100 during design work and edit the design information stored in the non-public design information 121 online. By doing so, it is possible to reduce the storage area used externally (client for the software development support system 100).

  The CPU 101 reads design information from the non-public design information 121 and further reads reference relationship schema definition information from the reference relationship schema definition information 131 by the design information registration program 110. Then, it is determined whether or not corresponding reference schema definition information exists for each design information (step 301).

  Here, the reference relationship schema definition information will be specifically described.

  When a software developer performs design work, the design information of the current process is expressed by referring to the design information of the upstream process, selecting a part of the design information of the upstream process, and embedding it in the design information of the current process. There is a case. The reference relationship schema definition information is used when it is required to select a part of the design information of the upstream process and embed it in the design information of the current process in order to ensure consistency between the upstream process and the current process. This is information that defines a combination of identification attributes of design information of a reference source and a usage destination.

  As an example, a case will be described in which an interface developer generates an interface definition with reference to a data item dictionary generated in an upstream process. Specific examples of upstream process design information, current process design information, and reference relationship schema definition information are shown in FIGS.

  FIG. 5 is a diagram illustrating an example of a data item dictionary corresponding to design information of the upstream process according to the first embodiment of this invention.

  The data item dictionary includes a data item identifier 500, a data item name 501, and a version 502. In addition, attributes such as data type, number of digits, update date and time are included.

  The data item identifier 500 is an identifier for identifying a data item. The data item name 501 is the name of the data item. The version 502 is a numerical value indicating the version of the data item, and is added every time the attribute of the data item is changed.

  FIG. 6 is a diagram illustrating an example of an interface definition corresponding to design information of the current process according to the first embodiment of this invention.

  The interface definition shown in FIG. 6 is definition information of an interface that outputs customer information with a customer name as an input item. The interface definition includes information necessary for generating the reference relationship schema definition information, such as an interface input item name 600, a first reference source data item identifier 601, a first reference source data item version 602, an interface output item name 603, a first item. It includes a second reference source data item identifier 604 and a second reference source data item version 605. Further, an interface identifier for identifying the interface is included.

  The interface input item name 600 is the name of the input item. The first reference source data item identifier 601 is an identifier of a data item corresponding to the input item. The first reference source data item version 602 is a version of the first reference source data item. The interface output item name 603 is the name of the output item. The second reference source data item identifier 604 is an identifier of the data item corresponding to the output item. The second reference source data item version 605 is a version of the second reference source data item.

  FIG. 7 is a diagram illustrating an example of the reference relationship schema definition information 131 according to the first embodiment of this invention.

  The interface definition is created by selecting data items corresponding to input items and output items. Specifically, referring to the data item name 501 of the data item dictionary shown in FIG. 5, the interface input item name 600 and interface output item name 603 of the interface definition shown in FIG. 6 are defined. The value of the data item identifier 500 of the data item dictionary is stored in the first reference source data item identifier 601 and the second reference source data item identifier 604 of the interface definition.

  The reference relationship schema definition information stores a correspondence between a reference source identification attribute 700 that is an upstream process and a use destination identification attribute 701 that is a downstream process. In the example described above, the identification attribute 700 of the reference source is the “data item identifier 500” of the data item dictionary, and the identification attribute 701 of the usage destination is “interface input item identifier” and “interface output item identifier” of the interface definition. Become.

  It is assumed that the reference relationship schema definition information has already been created when design information for downstream processes is input. For example, it is created by the project manager at the start of the project.

  The presence of the reference relationship schema definition corresponding to the design information means that the identification attribute of the design information matches the identification attribute of the design information used by the reference relationship schema definition.

  Now, the description returns to the flowchart of FIG.

  When there is a reference relationship schema definition corresponding to the design information read from the non-public design information 121 (the result of step 301 is “Yes”), the CPU 101 causes the design information registration program 110 to execute each design information. Reference relationship instance information is generated using the reference relationship schema definition information corresponding to. Further, it is determined whether or not the identification attribute of the design information that is the reference source of the reference relationship instance information is clear (step 302).

  Further, the reference relationship instance information generated in the process of step 302 is written in the reference relationship instance information 133 of the relationship information storage unit 130.

  As described above, the reference relation instance information is a combination of the identification attribute of the design information of the upstream process actually used for reference and the identification attribute of the design information of the use destination when the software developer performs the design work. It is the saved information. A specific example of the reference relationship instance information is shown in FIG.

  FIG. 8 is a diagram illustrating an example of the reference relationship instance information 133 according to the first embodiment of this invention.

  The reference relationship instance information 133 includes reference source design information 800 and use destination design information 810.

  The reference source design information 800 includes an identification attribute name 801, an identification attribute value 802, and an estimated value flag 803. For example, as the identification attribute name 801 and the identification attribute value 802 of the record 820, “data item identifier” corresponding to the field name and “D-0002” corresponding to the value are stored. The estimated value flag 803 indicates “NO” when the design information 800 of the reference source and the design information 810 of the usage destination are associated by the reference relationship schema definition information 131 or the like, and the design information 800 of the reference source is estimated. If it is a value, “YES” is stored. The initial value of the estimated value flag is set to “NO”. The estimated value flag 803 is set in the process of step 303 in FIG. 3, and details will be described later.

  The use destination design information 810 includes an identification attribute name 801 and an identification attribute value 802. An identification attribute name 801 and an identification attribute value 802 are included. The record 820 stores an “interface input item identifier” corresponding to the field name and “IFIN-0087” corresponding to the value.

  Now, the description returns to the flowchart of FIG.

  When the design information of the reference source is unknown in the design information of the usage destination, that is, when the software developer does not refer to and use the design information of the upstream process and independently generates the design of the current process (step If the result of 302 is “No”), it is determined whether or not the design information of the corresponding reference source can be estimated from the public design information (step 303).

  The reference source design information is estimated based on the alternative identification attribute definition information by executing the reference source estimation program 111.

  More specifically, first, the substitute identification attribute definition information is acquired from the substitute identification attribute definition information 132 based on the design information of the usage destination. Next, the corresponding public design information is acquired from the public design information 122 based on the acquired alternative identification attribute. The acquired public design information is estimated as design information of a reference source. A specific example of the alternative identification attribute definition information 132 is shown in FIG.

  FIG. 9 is a diagram illustrating an example of the alternative identification attribute definition information 132 according to the first embodiment of this invention.

  The alternative identification attribute definition information 132 includes a reference source development process 901, a reference source identification attribute 902, a usage destination development process 903, and a usage destination identification attribute 904.

  When the alternative identification attribute definition information 132 is searched to estimate the design information of the reference source, the design information of the usage destination, that is, the development process 903 of the usage destination and the identification attribute 904 of the usage destination are known. Therefore, the reference source development process 901 and the reference source identification attribute 902 are searched based on the use destination development step 903 and the use destination identification attribute 904. Then, the design information corresponding to the identification attribute 902 of the reference source corresponding to the reference source development process 901 is estimated from the public design information as the design information of the reference source.

  Now, the description returns to the flowchart of FIG.

  When the reference source design information can be estimated (the result of step 303 is “Yes”), the CPU 101 uses the identification attribute name and the estimated value flag as the identification attribute value of the estimated reference source design information. At the same time, it is written in the reference relationship instance information 133 as design information of the reference source. Note that the value of the estimated value flag set in this case is always “YES”. Thereafter, the process of step 304 is executed.

  When the design information of the reference source is clear, that is, when the software developer generates the design information of the current process by referring to the design information of the upstream process (the result of step 302 is “Yes”). , Step 304 is executed.

  The CPU 101 reads design information from the non-public design information 121 and further reads reference relation instance information from the reference relation instance information 133 by the matching state confirmation program 112. Then, the read design information and reference relationship instance information are combined based on the external key of the design information. Subsequently, the design information of the reference source of the reference relationship instance is compared with the version or value of the design information of the usage destination, and the consistency between the two is determined (step 304). Further, the determination result is written in the matching status information 134 of the relationship information storage unit 130 as the matching status between the reference relationship instances.

  Here, the consistency between the design information of the reference source of the reference relationship instance and the design information of the usage destination means that if the design information of the reference source is an estimated value, the values of the design information of the reference source and the usage destination match. When the design information of the reference source is not an estimated value, it is regarded as consistent if the versions of the design information of the reference source and the usage destination match. The matching status information includes identification information of the design information of the reference source and the usage destination and the matching status. A specific example of the matching state information is shown in FIG.

  FIG. 10 is a diagram illustrating an example of the matching state information 134 that stores the matching state between the design information according to the first embodiment of this invention.

  The matching status information 134 includes reference design information 1010, usage destination design information 1020, and matching status 1030. The design information 1010 of the reference source and the design information 1020 of the usage destination include the name of the identification attribute and the value of the identification attribute, respectively. The consistency state 1030 is information indicating whether or not the design information 1020 of the usage destination corresponding to the design information 1010 of the reference source is consistent. As described above, “consistency” or “inconsistency” is stored.

  Now, the description returns to the flowchart of FIG.

  When the design information of the reference source of the reference relationship instance and the design information of the usage destination are inconsistent (the result of step 304 is “inconsistent”), the CPU 101 executes the design information registration program 110 to perform the inter-reference relationship instance The reference information version and the design information version of the usage destination are compared (step 305).

  At this time, if the design information of the reference source is not an estimated value (“estimated value flag = NO”) and the version relationship of the design information is “reference source <use destination”, “external, current process (use The CPU 101 considers that the previous developer may forcibly register the design information because the developer has intentionally generated unique design information without referring to the design information of the upstream process (reference source). Step 307 is executed.

  On the other hand, if the version relation of the design information is “reference source> use destination”, the design information of the upstream process (reference source) is updated or deleted outside the developer of the current process (use destination). Therefore, it is assumed that the registration must be stopped once and the developer of the current process must confirm the affected party or make necessary corrections ”, and the CPU 101 executes the processing of step 311.

  Also, if the version relationship of the design information is “reference source = estimated value”, “the developer of either the upstream process or the current process has made a work error, so registration is stopped once and the upstream process and the current process The CPU 101 executes the processing of step 311 on the assumption that the developer of the process must confirm the affected party or make a necessary correction.

  When the design information of the reference source cannot be estimated (the result of step 303 is “NO”), the CPU 101 sets the consistency state of the reference relationship instance as “inconsistent” and writes it in the consistency state information 134 (step 306).

  The CPU 101 uses the design information registration program 110 to write the registration status of the design information as “forced registration” in the registration status information 123 (step 307). Here, the registration state information is information that stores a combination of the identification attribute of design information and the registration state of design information. A specific example of the registration status information 123 is shown in FIG.

  FIG. 11 is a diagram illustrating an example of the registration state information 123 that stores the registration state of the design information according to the first embodiment of this invention.

  The registration status information 123 includes a design information identification attribute 1101 and a registration status 1102. The registration status 1102 stores “normal registration” or “forced registration”. “Normal registration” is stored when it matches the design information of the reference source. On the other hand, “forced registration” is stored when it is necessary to review the design information of the reference source.

  Now, the description returns to the flowchart of FIG.

  The CPU 101 writes the reference relationship instance information in the forced registration review target information 135 by the design information registration program 110 (step 308). In addition, the review conditions for forced registration are written. The content to be written in the forced registration review condition is set to “when a reference source is added” when the design information of the reference source of the reference relation instance does not exist. If design information of the reference source of the reference relationship instance exists, the forced registration review condition is “when the reference source is updated”. In addition, when the identification attribute of design information of the same reference source and usage destination already exists at the time of writing, it is overwritten. A specific example of the forced registration review target information is shown in FIG.

  FIG. 12 is a diagram illustrating an example of the forced registration review target information 135 according to the first embodiment of this invention.

  The forced registration review target information 135 includes a forced registration review target 1210 and a forced registration review condition 1220. The forced registration review target 1210 includes reference design information and use destination design information. The version of the design information of the reference source is also included.

  Now, the description returns to the flowchart of FIG.

  When there is no reference relationship schema definition corresponding to the design information read from the non-public design information 121 (the result of step 301 is “No”), the CPU 101 reads it by the design information registration program 110. The registration state of the design information is written in the registration state information 123 as “normal registration” (step 309).

  The CPU 101 reads design information from the non-public design information 121 by the design information registration program 110, and overwrites and copies the design information to the public design information 122 (step 310).

  Finally, the CPU 101 notifies the registration result of the design information to the outside by the state information notification program 113 and ends the program (step 311). Here, the registration result of the design information is, for example, the registration state of the design information or the reason for canceling the registration. In addition, as a notification destination of the registration result, for example, in the case of a “working error of the developer of the reference source or the user”, the developer of the design information of the reference source and the user is notified, and in other cases Can be arbitrarily specified in accordance with a predefined notification condition, such as notifying only the developer of the design information of the usage destination. FIG. 13 shows a specific example in which a registration result notification destination, registration conditions, and a result of registration processing are summarized.

  FIG. 13 is a diagram illustrating an example of a correspondence between a registration condition and a registration process result according to the first embodiment of this invention.

  In the example shown in FIG. 13, the contents constituting the conditions at the time of registration include a reference relationship schema 1301, a reference source value 1302, a reference source estimation 1303 using an alternative identification attribute, a matching state 1304 between reference relationship instances, And a version relationship 1305 between the reference relationship instances.

  On the other hand, the result of the registration process includes an inconsistency factor 1311 between reference relationship instances, a registration process type 1312, a registration result notification destination 1313, and a forced registration review condition 1314.

  For example, for newly registered design information, if there is no information corresponding to the reference relationship schema 1301 (the result of step 301 is “NO”), it is assumed that the design information of the reference source does not exist, and there is inconsistency. It does not occur. As a result of the registration process, the type 1312 of the registration process is “normal registration”, and the developer of the current process that has registered the design information is notified.

  As another example, when the corresponding information is included in the reference relationship schema 1301 (the result of step 301 is “Yes”), and the identification attribute of the design information of the reference source is clear (the result of step 302 is “Yes”). )), When the version of the design information of the reference source is older than the registered design information, that is, when there is inconsistency with the design information of the reference source (the result of Step 303 is “Yes”), the reference Inconsistency is caused by newly registering design information before the original design information is updated. In this case, “forced registration” is performed, and the consistency is confirmed again at the timing when the design information of the reference source is updated.

  If inconsistency occurs due to an input error in the design information of the reference source or the design information of the usage destination (the result of step 305 is “NO”), the registration is stopped.

  In the design information registration process procedure, in steps 303 to 305, (1) whether or not the design information of the reference source can be estimated, and (2) the design source information of the reference relationship instance and the design information of the usage destination match. And (3) one of (a) normal registration, (ii) forced registration, and (iii) registration cancellation under the three types of conditions of the reference relation instance reference source and the design information version of the usage destination The registration process has been decided.

  As a modification of the first embodiment, if it is determined that only one of (i) forced registration and (u) registration cancellation registration processing can be selected in steps 303 to 305, status information notification The program 113 may notify the determination result to the outside, receive an instruction from the outside, and execute one of the processes in Step 306, Step 307, or Step 311.

  In this way, not only can the type of registration process be determined mechanically based solely on the characteristics of the design information requested to be registered from the outside and the relationship with other design information, but also the external that can change as the project progresses. It is possible to determine a more optimal type of registration processing after comprehensively considering the environment (for example, the skills of software developers and project managers, the scale of development, and the development schedule).

  The above is the detailed description of the design information registration procedure. Next, a forced registration review processing procedure will be described with reference to the flowchart of FIG.

  FIG. 4 is a flowchart showing a procedure for reviewing design information forcibly registered according to the first embodiment of this invention.

  The CPU 101 reads out the forced registration review target information from the forced registration review target information 135 by the forced registration review program 114. The identification attribute of the design information designated from the outside as the target of the forced registration review request in the process of step 202 in FIG. 2 is compared with the identification attribute of the design information of the use destination of the forced registration review target information. It is determined whether or not the information coincides with the forced registration review target information (step 400). If they do not match (the result of step 400 is “NO”), the status information notification program 113 notifies the outside of the fact that the forced registration cannot be reviewed (step 409), and the process ends. In this case, the target of the forced registration review request input from the outside is currently excluded from the review target for some reason, or coincides with a plurality of review targets.

  If the identification attribute of the design information designated from the outside matches the identification attribute of the design information of the usage destination of the forced registration review target information (the result of step 400 is “Yes”), the CPU 101 In 114, the review condition of the compulsory registration review target information that is matched in the process of step 400 is acquired. Then, it is determined whether the forced registration review condition is “when a reference source is added” or the forced registration review condition is “when a reference source is updated” (step 401).

  When the compulsory registration review condition is “when reference source is added” (the result of step 401 is “when reference source is added”), the CPU 101 causes the reference source estimation program 111 to match the compulsory registration review target information matched in step 400. Is estimated based on the alternative identification attribute definition information in the same procedure as the step 303 process of FIG. 3 (step 402).

  In addition, the value of the identification attribute of the design information of the reference source estimated here is written in the reference relationship instance information 133 as the design information of the reference source. Further, the name and the value of the identification attribute are set to “YES”, and the estimated value flag is written in the reference relation instance information 133. Also, the review condition of the compulsory registration review target information that coincides in step 400 is updated to “when the reference source is updated”.

  If the design information of the reference source cannot be estimated (the result of step 402 is “NO”), the CPU 101 notifies that the forced registration review has failed (step 407), and ends this process.

  On the other hand, when the forced registration review condition is “when the reference source is updated” (the result of step 401 is “when the reference source is updated”), the CPU 101 determines whether or not the design information of the reference source has been updated. (Step 408). Specifically, the design information is read from the non-public design information 121 by the reference source change confirmation program 115, and the design information of the reference source of the compulsory registration review target information that matches in the process of step 400 matches the value of the identification attribute. Search for design information and compare both versions. If the version of the current design information is older than the design information of the reference source of the forced registration review target information (the result of step 408 is “NO”), the reference source design information has not been updated, so forced registration That the review has failed (step 407), and the process is terminated.

  When the reference source design information is estimated (the result of step 402 is “YES”), or when the reference source design information is updated (the result of step 408 is “YES”), The matching status confirmation program 112 compares the version or value of the design information of the forcible registration review target information that matched in the process of step 400 and the design information of the use destination, and the two match in the same procedure as the process of step 304. It is determined whether or not there is (step 403). Further, the determination result is regarded as the consistency state between the reference relationship instances, and the consistency state information 134 is updated.

  If the reference source of the forced registration review target information and the design information of the usage destination do not match (the result of step 403 is “NO”), the CPU 101 notifies that the forced registration review has failed (step 403). 407), the process is terminated.

  If the reference source of the forced registration review target information matches the design information of the usage destination (the result of step 403 is “YES”), the CPU 101 uses the forced registration review program 114 to design the forced registration target design information. Is registered in the registration status information 123 as “normal registration” (step 404).

  The CPU 101 uses the compulsory registration review program 114 to forcibly register the review target information in which the identification attribute value of the design information of the reference source is the same in the process of step 400 among the reference relation instance information stored in the reference relation instance information 133. The reference relationship instance information 133 is updated with the estimated value flag of the reference relationship instance information equal to the identification attribute of the design information of the reference source of “NO” (step 405).

  Further, the CPU 101 deletes the forced registration review target information that coincided in the process of step 400 from the forced registration review target information 135 by the forced registration review program 114 (step 406).

  The CPU 101 notifies the forced registration review result to the outside through the state information notification program 113 (step 407), and ends this process. Here, the review result of forced registration is, for example, the registered state of design information after review. Further, as the notification destination of the forced registration review result, the developer of the design information and the project manager of the usage destination are designated in accordance with a notification condition arbitrarily defined in advance.

  The above is the detailed description of the processing procedure for reviewing forced registration.

  According to the first embodiment of the present invention, design information for which consistency is not guaranteed can be identified as design information forcibly registered. Therefore, it is possible to prevent the upstream process from being inappropriately affected even when the design information of the related downstream process is changed without waiting for the change in the upstream process.

  In addition, according to the first embodiment of the present invention, it is only necessary to mechanically determine the type of registration processing based only on the characteristics of the design information requested for registration from the outside or the relationship with other design information. The most appropriate type of registration process after comprehensive consideration in conjunction with the external environment (for example, the skills of software developers or project managers, the scale of development or the development schedule) that can change as the project progresses It becomes possible to decide.

(Second Embodiment)
In the first embodiment, when the value of the identification attribute of the design information of the reference source of the reference relationship instance information is unknown, the design information of the reference source is estimated. In the second embodiment, Registration will be canceled. Instead, prior registration of only the identification attribute of the reference source is possible. Note that the description common to the first embodiment is omitted as appropriate.

  FIG. 14 is a flowchart illustrating a procedure of design information registration processing according to the second embodiment of this invention.

  The difference from the registration processing of the first embodiment shown in FIG. 3 is that the value of the identification attribute of the design information of the reference source of the reference relationship instance information is unknown (the result of step 302 is “NO”). The identification information of the reference source can be registered in advance.

  In the second embodiment, “normal registration” and “preceding registration” can be selected and executed in the process of step 200 in FIG. 2 that is common to the first embodiment. Pre-registration is to pre-register at least only the identification attribute of design information that may be referenced and used in downstream processes.

  When the value of the identification attribute of the design information of the reference source of the reference relation instance information is unknown (the result of step 302 is “NO”), the CPU 101 selects prior registration of the identification information of the design information of the reference source It is then determined whether it has been executed (step 1401). If the preceding registration is not selected and executed (the result of step 1401 is “NO”), this process is executed to register all the attributes of the design information, so that the design information of the reference source is identified. Since the information does not exist, the fact that the registration of the design information has failed is notified (step 311), and this processing is terminated.

  When this process is executed by selecting the preceding registration of the identification information of the design information of the reference source (the result of Step 1401 is “YES”), the CPU 101 may perform the design that may be used for reference in the downstream process. At least the identification attribute of the information is registered in advance (step 1402). Thus, by registering the identification information of the design information of the upstream process in advance, it is possible to register the design information of the downstream process while maintaining consistency. In this case, it is not necessary to input all the design information of the upstream process, and it becomes easy to adjust the load on the developer of the upstream process.

  According to the second embodiment of the present invention, design information of a downstream process (use destination) is input in a state in which design information of a reference source is input, so that consistency of design information can be guaranteed. . In this case, as described above, input of upstream process design information is divided into two stages: (1) advance registration of only identification attributes and (2) registration of all attributes. By making the adjustment easier, it is possible to prevent a situation in which design information cannot be input in the downstream process because design information is not input in the upstream process.

It is a figure which shows the structure of the software development assistance system of the 1st Embodiment of this invention. It is a flowchart which shows the whole process of the software development assistance system of the 1st Embodiment of this invention. It is a flowchart which shows the procedure of the registration process of the design information of the 1st Embodiment of this invention. It is a figure which shows an example of the data item dictionary which is the design information of the upstream process of the 1st Embodiment of this invention. It is a flowchart which shows the procedure which reviews the design information forcibly registered of the 1st Embodiment of this invention. It is a figure which shows an example of the interface definition which corresponds to the design information of the present process of the 1st Embodiment of this invention. It is a figure which shows an example of the reference relation schema definition information of the 1st Embodiment of this invention. It is a figure which shows an example of the reference relationship instance information of the 1st Embodiment of this invention. It is a figure which shows an example of the alternative identification attribute definition information of the 1st Embodiment of this invention. It is a figure which shows an example of the matching status information which stores the matching status between the design information of the 1st Embodiment of this invention. It is a figure which shows an example of the registration status information which stores the registration status of the design information of the 1st Embodiment of this invention. It is a figure which shows an example of the forced registration review object information of the 1st Embodiment of this invention. It is a figure which shows an example of a response | compatibility with the conditions at the time of registration of the 1st Embodiment of this invention, and the result of a registration process. It is a flowchart which shows the procedure of the registration process of the design information of the 2nd Embodiment of this invention.

Explanation of symbols

100 Software Development Support System 101 CPU
102 Memory 103 External Interface 104 Input Device 105 Output Device 106 Communication Device 107 External Storage Device 108 Bus 110 Design Information Registration Program 111 Reference Source Estimation Program 112 Consistency Check Program 113 Status Information Notification Program 114 Forced Registration Review Program 115 Reference Source Change Check Program 120 Design information storage unit 121 Non-public design information 122 Public design information 123 Registration state information 130 Relationship information storage unit 131 Reference relationship schema definition information 132 Alternative identification attribute definition information 133 Reference relationship instance information 134 Consistency state information 135 Compulsory registration review target information

Claims (20)

A software development support method for managing software design information and supporting development in a software development support device,
The software development support apparatus includes a processor and a storage unit connected to the processor,
The storage unit stores reference relationship schema information that defines a correspondence between design information of an upstream process and design information of a downstream process, and alternative identification attribute information for estimating a correspondence between the design information,
The method
When the design information is input, based on the reference relationship schema information, identify the reference source design information corresponding to the input design information,
When the reference source design information cannot be specified, the reference source design information is estimated based on the alternative identification attribute information,
Determining consistency between the input design information and the estimated reference source design information or the specified reference source design information;
A software development support method, wherein the input design information is registered based on the consistency determination result.   2. The software development support method according to claim 1, wherein the design information is information generated at each development step in software development, and is held in correspondence with items constituting the design information. The alternative identification attribute information includes an identifier of the design information and an alternative identification attribute capable of substituting the identifier of the design information of the upstream process corresponding to the identifier of the design information,
The method
When the input design information is created without using the upstream process design information, the design information including the alternative identification attribute is searched based on the alternative identification attribute information.
3. The software development support method according to claim 1, wherein the searched design information is estimated as reference source design information. The method
When the reference source design information is specified, it is determined that the version is matched when the version of the input design information and the version of the reference source design information match,
When the reference source design information is estimated, a match is determined when the value of the input design information matches the value of the reference source design information. Item 4. The software development support method according to any one of Items 3 to 4. The process of registering the inputted design information includes:
When the reference design information and the input design information are determined to be consistent, the input design information is registered as it is,
When the reference source design information and the input design information are determined to be inconsistent and the version of the reference source design information is older than the version of the input design information, or the reference source design information is estimated If not, the design information is forcibly registered together with information indicating that the input design information is inconsistent,
When the reference source design information and the input design information are determined to be inconsistent and the version of the reference source design information is newer than the version of the input design information, or the reference source design information is estimated 5. The software development support method according to claim 4, wherein registration of the inputted design information is canceled if it has been done.   6. The software development support method according to claim 5, wherein the method re-determines the consistency of the forcibly registered design information at a predetermined timing. The predetermined timing is
When the reference source design information does not exist, it is a timing when the reference source design information is newly added,
The software development support method according to claim 6, wherein when the reference source design information exists, it is a timing at which the reference source design information is updated.   When the method is determined to be consistent with the reference source design information as a result of re-determination of the consistency of the design information registered forcibly, the method forcibly registered is inconsistent. 8. The software development support method according to claim 6 or 7, wherein information indicating that the information is deleted is deleted. The method
Presenting a determination result of consistency between the reference design information and the input design information,
Either normal registration for registering the input design information as it is, forced registration for registration with information indicating that the input design information is inconsistent, or canceling registration of the input design information 4. The software development support method according to claim 1, wherein the selection of the software is accepted. The method
Receiving an input of an identification attribute of design information referred to in a downstream process of the process corresponding to the design information;
The reference source design information is specified based on the input identification attribute when the design information of the downstream process is registered, according to any one of claims 1 to 9, The described software development support method.   The software development support method according to any one of claims 1 to 10, wherein the method notifies a registration result of the inputted design information.   In the case where the reference design information and the input design information are inconsistent, the method presents a factor causing the inconsistency based on the consistency determination result. The software development support method according to any one of claims 1 to 11. A software development support apparatus that includes a processor and a storage unit and manages design information generated in each development process in software development,
The storage unit stores reference relationship schema information that defines a correspondence between design information of an upstream process and design information of a downstream process, and alternative identification attribute information for estimating a correspondence between the design information,
The processor is
When the design information is input, based on the reference relationship schema information, identify the reference source design information corresponding to the input design information,
When the reference source design information cannot be specified, the reference source design information is estimated based on the alternative identification attribute information,
Determining consistency between the input design information and the estimated reference source design information or the specified reference source design information;
A software development support apparatus, wherein the input design information is registered based on the consistency determination result. The alternative identification attribute information includes an identifier of the design information and an alternative identification attribute capable of substituting the identifier of the design information of the upstream process corresponding to the identifier of the design information,
The processor is
When the input design information is created without using the upstream process design information, the design information including the alternative identification attribute is searched based on the alternative identification attribute information.
14. The software development support apparatus according to claim 13, wherein the searched design information is estimated as reference source design information. The processor is
When the reference source design information is specified, it is determined that the version is matched when the version of the input design information and the version of the reference source design information match,
14. When the reference source design information is estimated, it is determined that the value is the match if the value of the input design information matches the value of the reference source design information. Item 15. The software development support device according to Item 14. The process of registering the inputted design information includes:
When the reference design information and the input design information are determined to be consistent, the input design information is registered as it is,
When the reference source design information and the input design information are determined to be inconsistent and the version of the reference source design information is older than the version of the input design information, or the reference source design information cannot be estimated The design information is forcibly registered together with information indicating that the input design information is inconsistent,
It is determined that the reference source design information and the input design information are inconsistent, and the version of the reference source design information is newer than the version of the input design information, or the reference source design information is estimated. 16. The software development support apparatus according to claim 15, wherein the registration of the inputted design information is stopped when the input is received.   The software development according to claim 16, wherein when the reference source design information is newly added or updated, the processor re-determines the consistency of the forcibly registered design information. Support device.   The software development support apparatus according to claim 13, wherein the processor notifies a registration result of the input design information. A software development support system for managing design information generated in each development process in software development,
The software development support system includes a software development support device that manages the design information,
The software development support device includes:
A processor that executes business processing by processing a program; and a storage unit that stores data and programs necessary for business processing processed by the processor;
Managing the reference relationship schema information that defines the correspondence between the design information of the upstream process and the design information of the downstream process, and alternative identification attribute information for estimating the correspondence between the design information,
When the design information is input, based on the reference relationship schema information, identify the reference source design information corresponding to the input design information,
When the reference source design information cannot be specified, the reference source design information is estimated based on the alternative identification attribute information,
Determining consistency between the input design information and the estimated reference source design information or the specified reference source design information;
A software development support system, wherein the inputted design information is registered based on the consistency determination result. A program for managing design information executed in a software development support device and generated in each development process in software development,
The software development support apparatus stores reference relationship schema information that defines a correspondence between design information of an upstream process and design information of a downstream process, and alternative identification attribute information for estimating a correspondence between the design information. And
The program is
When the design information is input, a procedure for identifying reference source design information corresponding to the input design information based on the reference relationship schema information;
When the reference source design information cannot be specified, a procedure for estimating the reference source design information based on the alternative identification attribute information;
A procedure for determining consistency between the inputted design information and the estimated reference source design information or the identified reference source design information;
And a procedure for registering the inputted design information based on the consistency determination result.

Images