JP2009104336A - Software deliverable management system and its method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a software deliverable management system and its method and a program for improving the efficiency of software development. <P>SOLUTION: A computer stores a plurality of software deliverables generated by creating information included in other software deliverables on the basis of information included in already generated software deliverables in a deliverable repository 13 in a state in which information of each software deliverable and information of other software deliverables generated on the basis of the information are associated with one another. When the information of the software deliverables stored in the repository 13 is changed by an information input unit 12, the computer extracts the information of other software deliverables associated with the changed information as influenced parts from the repository 13, and indicates on a display 11 only the influenced parts corresponding to the influenced contents selected by the input unit 12 among the extracted influenced parts. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a software product management system, a method, and a program therefor, which use a computer to identify an influence point of another software product based on a change in contents included in a software product created in software development.

  In software development, not only source code but also a user request, a simplified flow of software operation, and a document such as a design document for creating source code (hereinafter referred to as upstream product) are created as software products. Is done. These upstream deliverables are important for developing software that helps developers understand and meets user requirements during software development. However, when a software product that has already been created is changed due to a change in functionality during software development or operation, the software's functions must be accurately reflected. Other software artifacts related to the product will also need to be changed. In this case, there is a problem that as the number of software products increases, it becomes difficult to specify related software products and to specify a changed part in the software products. Therefore, various identification methods have been studied so far.

  By the way, software deliverables define dynamic deliverables that express dynamic information (tasks) for defining the behavior of the software to be developed, and data information necessary for the software to execute the behaviors. There have been proposed methods for identifying other software products that are affected by the change of the software product and the affected part.

For example, in Non-Patent Document 1, other relationships that are affected by a change in a dynamic product using a relationship between a plurality of dynamic products representing a functional operation of software, such as a UC description and a sequence diagram. It is possible to identify the dynamic product and its affected points.
Inoue et al. “Proposal of Propagation Location Identification Method in Product Change”, IEICE General Conference Proceedings, March 2007, p.549

  However, in the conventional example, when there are a large number of tasks for each of the large number of dynamic artifacts, when identifying other dynamic artifacts affected by the task change and the affected parts, a huge amount of dynamic artifacts are required. Since the product and its task are simply presented as the affected part, it is difficult for the developer to view the affected part, and this hinders efficient software development.

  The present invention has been made in view of the above problems, and an object of the present invention is to provide a software product management system, method, and program thereof that can improve the efficiency of software development.

  In order to achieve the above object, the software product creation system according to the present invention uses a computer to identify an influence location of another software product based on a change in content included in the software product created in software development. A software product management system that generates information included in another software product based on information input means and information included in the already created software product Storage means for storing a plurality of software deliverables in a state in which information on each software deliverable is associated with information on other software deliverables created based on the information, and software achievements stored in the storage means When information of an object is changed by the information input means, it is associated with the changed information. Only the affected part corresponding to the content selected by the information input means among the affected parts extracted by the identifying means and the affected part extracted by the identifying means from the storage means as the affected place information Display means.

  In addition, in order to achieve the above object, the software product creation method of the present invention uses a computer to determine the influence points of other software products based on changes in the contents included in the software product created in software development. A plurality of software products generated by creating information included in other software products based on information included in software products already created The product is stored in a predetermined storage unit in a state in which the information on each software product is associated with the information on the other software product created based on the information, and the software product stored in the storage unit If the information is changed by the specified information input unit, the other software associated with the changed information Extracted from the storage unit the information of the hardware product as impact points, in the extracted affected locations, it is displayed only effects the portion corresponding to the contents selected by the information input unit on a predetermined display unit.

  Furthermore, the software product management program of the present invention causes the computer to execute the software product creation method in order to achieve the object.

  As a result, since the information included in each software product is stored in a state associated with the information of other software products created based on the information, the information is changed when the information is changed. It is possible to extract all the information of other software products associated with the generated information. In this case, since only the affected part corresponding to the selected content is displayed, the developer can narrow down and browse the software product affected by the change and the affected part.

  According to the software product creation system, method, and program thereof of the present invention, it is possible to narrow down and browse the software product affected by the change and its affected part, so even if the number of software products becomes enormous, The developer can check the other software products affected by the change of the information included in the software product and the affected part without omission. Accordingly, it is possible to reliably prevent omission of correction of other software products affected by the change, so that the quality of the software products can be improved and the efficiency of software development can be greatly improved. .

  An embodiment of the present invention will be described below with reference to the drawings.

<Premise>
The software product is a static software product (hereinafter referred to as a static product) as a first software product that defines data information necessary for the software to be developed to realize its behavior. A dynamic software product (hereinafter referred to as a dynamic product) as a second software product expressing dynamic information (task) for defining the behavior of the software to be developed, In the present embodiment, a software product management system that identifies dynamic products and static products that are affected when the contents of a certain software product are changed, and the affected parts thereof will be described.

  A software product management system 10 according to the present invention comprises a computer mainly composed of a well-known CPU. As shown in FIG. 1, a display unit 11, an information input unit 12, a product repository 13, a specific result repository 14, and a control. It consists of part 15.

  The display unit 11 is a module for displaying information, such as a liquid crystal display, and displays a product drawing screen 20 as shown in FIGS. 2, 3, and 4 under the control of the control unit 15.

  The information input unit 12 is a module for inputting information, such as a keyboard and a mouse, and transmits input information to the control unit 15.

  The product repository 13 is a module that stores dynamic products and static products created in the software development process, a task achievement structure, a parameter dependency structure, and product rules described later.

  The specific result repository 14 is a module that stores the affected parts of the dynamic product and the static product that are affected when the contents of the software product are changed.

  The control unit 15 is a module that is connected to the modules 11 to 14 and delivers information between the modules 11 to 14 or information obtained by combining information between the modules 11 to 14. The control unit 15 is provided with a storage device such as a ROM, and the control unit 15 controls the modules 11 to 14 by executing a program stored in the storage device.

  In addition, the product drawing screen 20 is displayed on the display unit 11 with a configuration corresponding to each of correction / change of the software product, creation of a dynamic product, or creation of a static product. That is, as shown in FIG. 2, the product drawing screen 20 at the time of software product modification / change includes a product selection unit 21 for selecting a software product to be modified / changed, A drawing unit 22 for displaying the software product and a specific result list display unit 23 for displaying a list of the affected parts of the software product that are affected at the time of correction / change are configured.

  As shown in FIG. 3, the product drawing screen 20 at the time of creating the dynamic product includes a product selection unit 21 and a dynamic product drawing unit 24 for displaying the dynamic product to be created. And a static artifact display unit 25 for displaying a static artifact that is a basis of the dynamic artifact to be created, and a dynamic outcome created in a process upstream of the dynamic artifact to be created And a task display unit 26 for displaying the task of the object.

  Further, the product drawing screen 20 at the time of creating the static product is for displaying the product selection unit 21 and the static product that is the basis of the static product to be created, as shown in FIG. The reference unit 27 and a static product drawing unit 28 for displaying the static product to be created. Note that the information input unit 12 can be used to modify / change the software product, create a dynamic product, and create a static product. The dynamic product drawing unit 24 and the static product drawing unit 28 are provided with a registration instruction unit (not shown) for registering the created software product in the product repository 13. Registration can be instructed using the input unit 12.

<Formulation of dynamic product task>
In the dynamic product, behavior for functions realized by software is described as a flow of a plurality of tasks. This one task 30 is expressed as consisting of five elements: an input subject 31, an output subject 32, an operation 33, an input parameter 34, and an output parameter 35. When the task is expressed in natural language, the input subject 31, the output subject 32, the action 33, and the parameters 34 and 35 correspond to the subject, indirect object, predicate, and object, respectively. For example, as shown in FIG. 5, the input subject 31 of the task “Operator inputs OLT (Optical Line Terminal) information to the terminal” is “operator”, the output subject 32 is “terminal”, and the operation 33 is “input”. ”And the input parameter 34 is“ OLT information ”. When a task is expressed from a message in a sequence diagram in UML, the task 30 is shown as shown in FIG. The structure expressed as shown in FIGS. 5 and 6 is referred to as a task structure, and tasks and messages included in the dynamic product created by the dynamic product drawing unit 24 are converted into a task structure. Is stored in the deliverable repository 13.

  Even if the dynamic product has the same function to be expressed, the level of detail (granularity) of the task included in the dynamic product differs for each software development process. That is, as shown in FIG. 7, the granularity of the task 30a included in the dynamic product of the upstream process, for example, UC (use case), is determined by the plurality of tasks 30b included in the dynamic product of the downstream process, for example, the activity diagram. , 30c, 30d, which is coarser than the task granularity. Similarly, the granularity of each task 30b, 30c, 30d included in the activity diagram is coarser than the dynamic product of the downstream process, for example, multiple tasks 30e, 30f, 30g, 30h included in the sequence diagram. ing. Further, when the UC task 30a is broken down into the activity diagram tasks 30b, 30c, and 30d, the UC task 30a is between the UC task 30a and the activity diagram tasks 30b, 30c, and 30d. It is a task that is the basis of each task 30b, 30c, 30d in the activity diagram, and has a relationship that each task 30b, 30c, 30d in the activity diagram is created based on the UC task 30a. In the present embodiment, information representing such a relationship is expressed as an achievement relationship 40, and the task 30a of the UC and each task 30b, 30c, 30d of the activity diagram are linked by the achievement relationship 40. Note that the tasks 30b, 30c, 30d in the activity diagram and the tasks 30e, 30f, 30g, 30h in the sequence diagram are also linked by the achievement relationship 40 in the same manner as described above. In this case, the relationship between the task of the created dynamic product and the task for each process is expressed by a structure as shown in FIG. This structure is called a task achievement structure, and the task achievement structure is stored in the product repository 13.

<Formalization of static artifacts>
The static product describes data information (parameters) for realizing the behavior of the software. In the present embodiment, as shown in FIG. 8, the parameter 50 is expressed as including three elements, a set 51, an element 52, and a relation 53. For example, when a class diagram is expressed as an example of a static product, as shown in FIG. 9, class names are set to parameters 51a, 51b, 51c with parameters 50a, 50b, 50c, and class attributes are elements 52a-52e. In addition, the relationship between the classes corresponds to the relations 53a and 53b, respectively.

  An element 52a called "attr-a1" and an element 52b called "attr-a2" are connected to the set 51a called "Class-A", and an element 52b called "attr-a2" is connected to the set 51b called "Class-B" Class-B attribute, that is, an element 52c “attr-b1” is connected. Furthermore, a class 51 attribute “Class-C”, that is, an element 52d “attr-c1” and an element 52e “attr-c2” are connected to the set 51c “Class-C”.

  In addition, the set 51a called "Class-A" and the set 51b called "Class-B" are connected to each other by the relation 53a called "relation", and the set 51a called "Class-A" and the set called "Class-C" 51c are connected to each other by a relation 53b called “relation”.

  The structure expressed in this way is referred to as a parameter structure, and each parameter included in the static product is stored in the product repository 13 in a state converted to the parameter structure. In this case, all the parameters included in the static artifacts are formalized and stored, so that static artifacts expressed in various forms such as natural language, UML, unique graphics, etc. can be shared. It becomes possible to handle.

  The relations 53a and 53b may be generated when a developer creates a relation line between classes when creating a class diagram, or when the relations 53a and 53b are stored in the product repository 13 after the class diagram is created. It may be generated. Thereby, whether or not the relations 53a and 53b are generated is determined by the developer arbitrarily setting.

  Even if the static deliverables have the same parameters to be expressed, the viewpoint to be expressed is different for each software development process. For example, the parameters described in the static product of the upstream process are created based on the viewpoint that it is easy for humans to understand, but the parameters described in the static product of the downstream process are implemented as software It is created based on the viewpoint of ease of implementation and the operation speed at the time of software execution. However, even if the expressed viewpoints are different, the parameters of the static product of the downstream process are based on the parameters of the static product of the upstream process, such as using the parameter of the static product of the upstream process. Created. In the present embodiment, information relating the parameters of the static product of the upstream process and the parameters of the static product of the downstream process created based thereon is expressed as a dependency.

  This dependency will be described with reference to FIG. First, a glossary as a static product created in the upstream process, a data analysis model as a static product created in the process after the glossary is created, and a process after the data analysis model is created When there is a table design drawing as a static product, parameter structures 60, 61, and 62 corresponding to the glossary, the data analysis model, and the table design drawing are stored in the product repository 13, respectively. Here, when one parameter of the parameter structure 61 corresponding to the data analysis model is created based on one parameter of the parameter structure 60 corresponding to the glossary, the set, element, and relation constituting each parameter are created. Are related by dependency 70. The same applies to the case where one parameter of the parameter structure 62 corresponding to the table design drawing is created based on one parameter of the parameter structure 61 corresponding to the data analysis model. In this way, the relationship between the parameters of each static product is referred to as a parameter dependency structure, and the parameter dependency structure is stored in the product repository 13.

<Product rule>
Software deliverables created in software development are first created from an overview and detailed as the development process proceeds. In the dynamic product, as described above, the most abstract software product such as UC (Use Case) is created first, and software products such as activity diagrams and sequence diagrams are created as the process proceeds. As a result, the function of the software is detailed. Similarly, for static products, a glossary is first created, and as the process proceeds, products such as a data analysis model (class diagram) and a table design drawing are created, and parameters are refined. When creating a dynamic product, the parameters described in the static product are used. However, the number of static products required to create one dynamic product may be limited to several types. it can. For example, when creating a UC, the parameters necessary to represent the UC task are described in the glossary. When creating a sequence diagram, the parameters necessary to represent the sequence diagram message Is a table design drawing. As described above, when creating a dynamic product by associating a static product used when creating a certain dynamic product as shown in FIG. Can be easily acquired. The product constraint information (hereinafter referred to as a product rule) representing this association is configured as shown in FIG. 11 and stored in the product repository 13. In the present embodiment, although one product rule is used, it may be stored as a plurality of pieces of information for each correspondence relationship between a static product and a dynamic product.

<Create dynamic product>
In this case, the control unit 15 causes the display unit 11 to display the product drawing screen 20 with the configuration shown in FIG. The developer selects a dynamic product to be created in the product selection unit 21 of the product drawing screen 20. At this time, the control unit 15 outputs a static product corresponding to the selected dynamic product and a parameter structure corresponding to the static product based on the product rule stored in the product repository 13. Obtained from the property repository 13. In this case, the acquired static product is displayed on the static product display unit 25 of the product drawing screen 20. In addition, the control unit 15 acquires the task of the dynamic product created in the process upstream of the dynamic product selected by the product selection unit 21 from the product repository 13 and stores it in the task display unit 26. Display. Note that the format of the dynamic product drawn in the dynamic product drawing unit 24 may be a natural language, or a diagram based on UML such as an activity diagram and a sequence diagram.

  Here, the developer associates the dynamic product task element displayed in the dynamic product drawing unit 24 with the static product parameter element displayed in the static product drawing unit 25. I do. Specifically, after the developer selects an element of a parameter of a static product displayed in the static product display unit 25, that is, a set, element or relation, the developer is displayed in the dynamic product drawing unit 24. By selecting an element to be associated, that is, a subject, an action or a parameter, among the tasks of the dynamic product, the task of the dynamic product and the static displayed in the static product drawing unit 25 are selected. Associated with the parameter element of the deliverable. In the present embodiment, the existing GUI function is used to move the pointer to the parameter element displayed in the static product drawing unit 25 and click the mouse, and then display it in the dynamic product drawing unit 24. The association is performed by clicking an element of the task to be associated among the obtained dynamic products.

  At this time, the control unit 15 generates link information between the parameter element of the selected static product and the task element associated therewith, and stores the link information in the product repository 13.

  Next, the developer associates the dynamic product task displayed on the task display unit 26 with the dynamic product task displayed on the dynamic product drawing unit 24. This association is performed by the developer selecting the task of the dynamic product displayed in the dynamic product drawing unit 24 after selecting the task of the dynamic product displayed in the task display unit 26. . In the present embodiment, the existing GUI function is used to move the pointer to the task displayed on the task display unit 26 and click the mouse, and then the dynamic product displayed on the dynamic product drawing unit 24 is displayed. Each task can be associated by clicking on the task. At this time, the control unit 15 generates inter-task relationship information indicating that each task is associated with each other.

  As another method for creating a dynamic product, the technique described in Japanese Patent Application No. 2007-198845 proposed by the applicant may be used.

<Create static deliverables>
In this case, the control unit 15 causes the display unit 11 to display the product drawing screen 20 with the configuration shown in FIG. The developer selects a static product to be created by the product selection unit 21 of the product drawing screen 20, and then creates a static product by the static product drawing unit 28. In this case, the format of the static product to be created may be a diagram based on UML such as a natural language, a class diagram, a table design diagram, and an object diagram. At this time, the control unit 15 converts the created static product into a parameter structure. Further, the control unit 15 causes the reference unit 27 to display the static product created in the process upstream of the static product selected by the product selection unit 21.

  Next, the developer associates the parameter element of the static product displayed on the reference unit 27 with the parameter element of the static product displayed on the static product drawing unit 28. In this association, the developer selects the parameter element of the static artifact displayed in the static artifact drawing section 28 after selecting the parameter element of the static artifact displayed in the reference section 27. Is done. In the present embodiment, as in the case of creating the dynamic product described above, the pointer is moved to the parameter element displayed on the reference unit 27 and the mouse is clicked, and then displayed on the static product drawing unit 28. Each parameter element can be associated by clicking on the parameter element of the created static product.

  At this time, the control unit 15 selects the parameter element selected by the reference unit 27, that is, the set, element, or relation, and the parameter element selected by the static product drawing unit 28, that is, the set, element, or relation. Dependency 80 is generated between

  Create the required static deliverables by repeating the above operations.

<Product registration>
First, dynamic product registration will be described. After creating the dynamic product, the developer instructs the registration instruction unit of the product drawing screen 20 to register the dynamic product. At this time, the control unit 15 stores the created dynamic product in the product repository 13. In this case, the control unit 15 converts the dynamic product created based on the element information of each task and the inter-task relationship information into a task achievement structure, and stores the task achievement structure in the product repository 13. Note that the inter-task relationship information input at the time of creating the dynamic product is converted into the achievement relationship 40 in the task achievement structure.

  Next, registration of a static product will be described. After creating the static product, the developer instructs registration of the static product in the registration instruction unit of the product drawing screen 20. At this time, the control unit 15 stores the created static product in the product repository 13. The control unit 15 also includes a parameter structure corresponding to the created static product, a parameter structure corresponding to the static product displayed in the reference unit 27, and a dependency relationship 80 generated between the parameter structures. The parameter dependency structure created based on is stored in the product repository 13. In this way, the elements included in the parameter structure of each static product and the elements included in the parameter structure of another static product created based on the element are associated with each other in the result. Stored in the property repository 13.

  Further, in the same manner as described above, another software product is created on the product drawing screen 20 and registered. The registration of software products may be performed after all software products are created, or may be performed every time one software product is created.

<Identification of points affected by changes>
Assuming that the above product registration has been performed, other software products that need to be changed based on a partial change of a dynamic product or a static product that has already been created and registered, and its impact A method for specifying the location will be described with reference to FIGS. In the example shown in FIG. 13, each dynamic product shown in FIG. 7 is created based on each static product shown in FIG. That is, the UC is created based on the glossary, the activity diagram is created based on the data analysis model, and the sequence diagram is created based on the table design drawing. Note that link information 80 is generated between the operation of the task 30f in the sequence diagram and the set of parameter structures 62 (shown by bold lines) corresponding to the table design drawing.

  First, the product designated by the developer is acquired and displayed on the product drawing screen 20 (step S1). Specifically, after the product drawing screen 20 shown in FIG. 2 is displayed by the control unit 15, the developer wants to change the software product (dynamics) to be changed in the product selection unit 21 of the product drawing screen 20. When the deliverable or the static deliverable) is designated, the control unit 15 acquires the designated software deliverable from the deliverable repository 13 and sets a task structure or parameter structure corresponding to the software deliverable to the deliverable repository 13. Get from. Further, the control unit 15 displays the software product acquired from the product repository 13 on the drawing unit 22 of the product drawing screen 20. Then, the developer corrects the static product in the drawing unit 22. For example, when a table design drawing is selected from the software deliverables shown in FIG. 13, the table design drawing is displayed on the drawing unit 22, and the parameter structure 62 corresponding to the table design drawing is obtained from the product repository 13. To be acquired.

  Next, the element corresponding to the corrected part of the product corrected by the developer is specified using the task achievement structure or the parameter structure stored in the product repository 13 (step S2). Specifically, when the developer modifies an element constituting a task or parameter of a software product in the rendering unit 22 of the product rendering screen 20, the control unit 15 converts the modified element to an existing GUI function. Use to identify. For example, when the developer corrects the part “aaa” in the table design drawing of FIG. 13 (the part surrounded by a thick line in the figure), the parameter structure 62 corresponding to the table design drawing is changed to “aaa”. Corresponding locations (in this example, a set represented by a thick line) are specified.

  Next, an element related to the specified element is specified using the task achievement structure, the parameter dependency structure, and the link information 80 (step S3). Specifically, the control unit 15 sets other software product elements (hereinafter referred to as “related elements”) that are associated with the identified elements by the achievement relationship 40 or the dependency relationship 70 (hereinafter referred to as “related elements”). Extract from Further, the control unit 15 extracts a task or parameter element of the software product associated with the specified element by the link information 80. In this case, the control unit 15 identifies the extracted related element as an affected part.

  For example, among the parameters of the parameter structure 61 corresponding to the data analysis model of FIG. 13, the set (enclosed by a thick line) connected by the dependency 70 with the set specified in step S2 is the related element. Extracted as In addition, among the parameters of the parameter structure 60 corresponding to the glossary, a set connected with the dependency 70 with the set extracted as the related element (the one surrounded by a bold line) is also extracted as the related element. The Furthermore, the task 30f connected by the link information 80 with the set specified in step S2 is extracted as a related element. Furthermore, tasks 30a and 30b connected by the achievement relationship 40 with the task 30f extracted as related elements are also extracted as related elements.

<Registration of affected areas>
The control unit 15 stores the element identified in step S2 and the related element in the identification result repository 14 as the affected part. In the present embodiment, the affected part is classified and stored as “change” and “propagation”. “Change” is for storing the influence content of the element specified in step S2, the product name and product type of the software product including the element, the change content of the element, It is composed of the change type of the element. Here, the change type of the element indicates any one of addition, deletion, and update.

  “Propagation” is for storing the influence content of the related element, the product name and product type of the software product including the related element, the propagation content of the related element, and the related It consists of the element propagation type. Here, the propagation type of the related element is specified using the dynamic product change impact specifying function, that is, the achievement relationship 40, or the static product change impact specifying function, that is, the dependency. It represents whether it was specified using the relation 70.

  The related element corresponding to the affected area “propagation” is the achievement relationship 40 or the dependency existing between the software product including the related element and the software product including the element corresponding to the affected area “change”. As the number of 70 increases, the hierarchy is held deeper as shown in FIG.

<List of affected parts>
The control unit 15 acquires the affected part stored in the specific result repository 14, and displays the list on the specific result list display unit 23. In the present embodiment, the display mode of the affected part displayed on the specific result list display unit 23 is the same as that shown in FIG.

When the developer selects “change 1” from the influence points displayed in the specific result list display unit 23, the control unit 15 sets the product name of the influence point corresponding to “change 1” to the product selection unit 21. And the software product including the affected part is displayed on the drawing unit 22. At this time, the control unit 15 highlights the part corresponding to the affected part in the software product displayed on the drawing part 22 by using bold letters, highlights it, etc. Also make it stand out. When the developer selects “Propagation 1-1” among the affected points displayed on the specific result list display unit 23, the control unit 15 operates in the same manner as described above. Further, when the change type of the affected part is deletion, since the affected part is not displayed on the drawing unit 22, the control unit 15 indicates that there is no information corresponding to the affected part in bold type This is clearly shown in the drawing unit 22 using character information or the like.

  For example, when the data analysis model of FIG. 13 is displayed on the drawing unit 22, the part corresponding to the influence part extracted in step S3 (the part surrounded by the alternate long and short dash line in the figure) is displayed or displayed in bold. Light is displayed. Further, when the glossary is displayed on the drawing unit 22, the part corresponding to the affected part (the part surrounded by the alternate long and short dash line in the figure) is displayed or highlighted using bold letters, as described above. Further, when a UC, activity diagram, or sequence diagram is displayed on the drawing unit 22, a part corresponding to the affected part (a part surrounded by a broken line in the figure) is displayed or highlighted using bold characters.

<Narrowing down impact identification results>
The control unit 15 displays only the affected part corresponding to the content selected by the information input unit 12 on the specified result list display unit 23 among the affected parts displayed on the specified result list display unit 23. Thereby, it becomes possible to narrow down an influence location based on the said content. For example, when narrowing down the affected part “change”, the developer uses the information input unit 12 to select at least one of the product name, product type, change content, and change type. At this time, the control unit 15 displays only the affected part corresponding to the selected content on the specific result list display unit 23. Note that the operation when narrowing down the affected part of “propagation” is the same as described above.

  Here, when the task contents of the dynamic product called “OLT registration function sequence diagram” shown in FIG. 15 is changed, an operation when displaying the software product affected by the change and the affected part will be described. .

  The developer selects the OLT registration function sequence diagram in the product selection unit 21 of the product drawing screen 20. At this time, the control unit 15 acquires the OLT registration function sequence diagram from the product repository 13 and causes the drawing unit 22 to display the OLT registration function sequence diagram. In this case, the control unit 15 acquires a task structure corresponding to the OLT registration function sequence diagram from the product repository 13.

  Next, the developer modifies the OLT registration function sequence diagram displayed on the drawing unit 22 by using the information input unit 12. In this example, as shown in FIG. 16, the message name “send” is modified to “register”. At this time, the control unit 15 specifies a task corresponding to the corrected portion of the OLT registration function sequence diagram using the task structure.

  Further, the control unit 15 specifies the task of the other dynamic product and the element of the static product related to the specified task using the task achievement structure, the parameter dependency structure, and the link information 80. Here, a “Register sequence diagram” shown in FIG. 17B is used as an example of another dynamic product, and a “design class diagram” shown in FIG. 17C is used as an example of another static product. It explains using. Note that the task corresponding to the message “device information = register (OLT information)” in the OLT registration function sequence diagram of FIG. 17A is “SW-Data = Send (” in the Register sequence diagram of FIG. The task corresponding to the message “OLT-Data)” is associated with the achievement relationship 40. The message name “Send” in the Register sequence diagram of FIG. 17B is associated with the set “DBAccess” of the parameter structure corresponding to the design class diagram of FIG.

  The control unit 15 uses the task corresponding to the message “SW-Data = Send (OLT-Data)” in the Register sequence diagram as a related element, that is, an influence location, based on the specified correction location (task) and the achievement relationship 40. Extract. In addition, the control unit 15 also extracts a set “DBAccess” of the parameter structure corresponding to the design class diagram, which is associated with the message name “Send” in the Register sequence diagram and the link information 80, as an affected part.

  The control unit 15 stores the correction part and the influence part extracted as described above in the identification result repository 14. In this case, as shown in FIG. 18, the influence content of the correction portion is stored as “change 1”, and the influence content of the influence portion associated with the correction portion by the achievement relationship 40 is “propagation 1-1”. Remembered. In addition, the influence content of the influence part associated with the correction part via the achievement relationship 40 and the link information 80 is stored as “propagation 1-1-1.”

  Then, the control unit 15 acquires the affected part stored in the identification result repository 14, and displays the list on the identification result list display unit 23. The display mode of the product drawing screen 20 at this time is shown as in FIG. Next, when the developer selects the column “change 1” from the influence points displayed on the specific result list display unit 23 by using the information input unit 12, the control unit 15 performs the operation as shown in FIG. The software product including the correction portion corresponding to the change 1, that is, the OLT registration function sequence diagram is displayed on the drawing unit 22. In this case, the control unit 15 displays the part corresponding to the affected part in the OLT registration function sequence diagram displayed on the drawing unit 22, that is, “register” with emphasis in bold.

  Further, when the developer selects the column “Propagation 1-1” among the influence points displayed in the specific result list display unit 23 by using the information input unit 12, the control unit 15 is as shown in FIG. Then, a software product including a corrected portion corresponding to the propagation 1-1, that is, a register sequence diagram is displayed on the drawing unit 22. In this case, the control unit 15 displays the portion corresponding to the affected portion in the Register sequence diagram displayed on the drawing unit 22, that is, “Send” in a bold type and displayed.

  Furthermore, when the developer selects the column “Propagation 1-1-1” from the influence points displayed on the specific result list display unit 23 using the information input unit 12, the control unit 15 displays As shown, a software product including a corrected portion corresponding to the propagation 1-1-1, that is, a design class diagram is displayed on the drawing unit 22. In this case, the control unit 15 displays the portion corresponding to the affected portion in the design class diagram displayed on the drawing unit 22, that is, “DBAccess” with emphasis in bold.

  The control unit 15 displays only the affected part corresponding to the influence content selected by the information input unit 12 on the specified result list display part 23 among the affected parts displayed on the specified result list display part 23. For example, when a sequence diagram is specified for the influence content “product type” of the influence point “propagation”, the control unit 15 identifies only the influence point corresponding to the specified content as shown in FIG. The result is displayed on the result list display unit 23. In this case, the influence location “propagation 1-1-1” in the design class diagram that does not correspond to the specified product type is not displayed in the specific result list display unit 23.

  In this way, since only the affected part corresponding to the selected influence content is displayed, the developer can narrow down and browse the software product affected by the change and the affected part.

  As described above, in the above embodiment, since it is possible to narrow down and browse the software artifacts affected by the change and the affected parts, even if the number of software artifacts becomes enormous, the developer can select the software artifacts. Other software products that are affected by changes in the information included and the affected parts can be confirmed without omission. Accordingly, it is possible to reliably prevent omission of correction of other software products affected by the change, so that the quality of the software products can be improved and the efficiency of software development can be greatly improved. .

  In addition, a plurality of static artifacts including data for realizing the behavior of the software are associated with the data of each static artifact and the data of other static artifacts created based on the data, The data of each first software product is stored in the product repository 13 in association with the task of the dynamic product including the task including the data, and the dynamic product is stored in the dynamic product. The task is stored in the artifact repository 13 in a state in which the task and the task of another dynamic artifact created based on the task are associated with each other, and the static artifact data or the dynamic achievement stored in the artifact repository 13 When the task of the product is changed by the information input unit 12, the data of the static product and the task of the dynamic product associated with the changed data or task are extracted from the product repository 13 as the influence points. As a result, it is possible to identify the influence points for various types of software products.

  Further, the software product including the affected part selected by the information input unit 12 among the extracted affected parts is displayed on the display unit 11, and when the software product is displayed, the part corresponding to the affected part is displayed. Since it is displayed more prominently than other parts, the developer can be surely informed of the parts that are affected by the change of the software product.

  In addition, said embodiment is only a specific example of this invention, and this invention is not limited only to the said embodiment. For example, the present invention can also be realized by installing a program having the above-described creation procedure via a recording medium or a communication line in a known computer.

The figure which shows the structure of the software product management system in one Embodiment of this invention. Figure showing the product drawing screen Figure showing the product drawing screen Figure showing the product drawing screen Diagram showing task structure Diagram showing task structure Diagram showing task achievement structure Diagram showing parameter structure Diagram showing the relationship between static artifacts and parameter structure Diagram showing parameter-dependent structure Diagram showing deliverable rules Flow diagram showing the operation when identifying the location affected by the change The figure which shows the outline of the identification method of the influence part using a task achievement structure and a parameter dependence structure The figure which shows an example of the influence content memorize | stored as an influence location Figure showing the product drawing screen when changing software products Figure showing the product drawing screen when changing software products Diagram showing examples of dynamic and static artifacts The figure which shows an example of the influence content memorize | stored as an influence location Diagram showing the product drawing screen when the affected area list is displayed Diagram showing the product drawing screen when the affected area list is displayed Diagram showing the product drawing screen when the affected area list is displayed Diagram showing the product drawing screen when the affected area list is displayed Diagram showing the product drawing screen when narrowing down and displaying the affected areas

Explanation of symbols

  10 ... Software deliverable management system, 11 ... Display unit, 12 ... Information input unit, 13 ... Product repository, 14 ... Specific repository, 15 ... Control unit, 30,30a-30h ... Task, 40 ... Achievement relationship, 50, 50a-50c ... parameter, 51,51a-51c ... set, 52,52a-52e ... element, 53,53a, 53b ... relation, 70 ... dependency, 80 ... link information.

Claims (7)

A software product management system for identifying, using a computer, an affected part of another software product based on a change in content included in a software product created in software development,
The computer
Information input means;
A plurality of software artifacts generated by creating information included in other software artifacts based on information included in already created software artifacts, information on each software artifact and the information Storage means for storing information related to other software artifacts created in association with each other;
When the information of the software product stored in the storage unit is changed by the information input unit, the specifying unit that extracts the information of the other software product associated with the changed information from the storage unit as an affected part,
A software product management system, comprising: a display unit that displays only the affected part corresponding to the content selected by the information input unit among the affected parts extracted by the specifying unit. The storage means
A plurality of first software products including data for realizing the behavior of the software, data of each first software product, and data of other first software products created based on the data, Are stored in a state in which the data of each first software product is associated with the task of the second software product comprising the task including the data, and the second software product is stored in the second software product. The task of the software product of and the task of the other second software product created based on the task are stored in association with each other,
The specifying means is:
When the data of the first software product or the task of the second software product stored in the storage means is changed by the information input means, the first software product associated with the changed data or task The software product management system according to claim 1, wherein the data and the task of the second software product are extracted from the storage unit as an affected part. The display means includes
While displaying the software product including the affected part selected by the information input means among the affected parts extracted by the specifying means, when displaying the software product, the part corresponding to the affected part is displayed from other parts. The software product management system according to claim 1, wherein the software product management system is also displayed prominently. A software product management method for identifying, using a computer, an affected area of another software product based on a change in content included in a software product created in software development,
The computer
A plurality of software artifacts generated by creating information included in other software artifacts based on information included in already created software artifacts, information on each software artifact and the information Stored in a predetermined storage unit in a state of being associated with other software product information created in the
When the information of the software product stored in the storage unit is changed by the predetermined information input unit, the information of the other software product associated with the changed information is extracted from the storage unit as an affected part,
A software product management method characterized by displaying, on a predetermined display unit, only the affected part corresponding to the content selected by the information input unit among the extracted affected parts. The computer
A plurality of first software products including data for realizing the behavior of the software, data of each first software product, and data of other first software products created based on the data, Are stored in the storage unit in a state where the data of each first software product and the task of the second software product comprising the task including the data are associated with each other, and the second software product Is stored in the storage unit in a state in which the task of the second software product and the task of the other second software product created based on the task are associated with each other,
When the data of the first software product or the task of the second software product stored in the storage unit is changed by the information input unit, the first software product associated with the changed data or task The software product management method according to claim 4, wherein the data and the task of the second software product are extracted from the storage unit as an affected part. The computer
The software product including the affected part selected by the information input unit among the extracted affected parts is displayed on the display unit, and when the software product is displayed, the part corresponding to the affected part is changed to the other part. The software product management method according to claim 4, wherein the software product management method is displayed so as to stand out from the portion.   A software product creation program for causing a computer to execute the method according to any one of claims 4 to 6.

Images