JPH1040082A - Method and device for managing production process - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a production process management system capable of efficiently and correctly executing the history management of work and products. SOLUTION: A storage device 100 is provided with a system constitution definition table 101 for storing a constitution definition table for defining relation ship between the names of products and the products, a process definition table 102 for defining order relation between the contents of work and the work, a system/process correspondence table 103 for defining correspondence between work and products, a Rev/process corresponded table 104 for allowing work to correspond to the history of products, and a product storing means 105 for storing edited product files. The tables 101 to 103 are defined by a definition input means 110 and the table 104 is automatically set through the edition of a work execution means 120. An information retrieving means 130 specifies a product code or a process code by utilizing the correlation of the tables 101 to 104 and simply and comprehensively retrieves and displays required relational information.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to the production management of software products such as documents and programs, and more particularly to a production process management system in which a work is associated with a product.

[0002]

2. Description of the Related Art A software system development business is a work of gradually creating a product such as a design document or a program through each process of a plan design, a function design, a software design, and a program creation. If specifications change or defects occur during this development process, it is necessary to change the product once created. For this reason, in a software system development business, there are a plurality of changed production processes due to specification changes and the like at the same time as a production process for creating a new system.

[0003] In order for a person in charge to correctly execute such work, a work flow and a product created for each work are defined as a production process, and work guidance is performed based on the work flow. The work here is the work of creating one or a plurality of deliverables, and the production process is a work in which the work and the order are determined. In this work guidance, a tool required for creating a product is automatically activated, and creation and modification of the product are possible. Further, a server machine for storing the product is prepared, and the product required for the work can be taken out.

As an example of a method for integrated management of production processes and deliverables in software development, see IPSJ Transactions on “Modeling of Software-Enhanced Development Process and Prototyping of Development Support System Based thereon (Vol.34; No. .1
1) "has been proposed.

[0005] On the other hand, a product newly created or changed is subjected to change history management, and all versions are generally identified and stored with a revision number added thereto.

[0006]

In the conventional software development management, there is a method of correctly guiding work according to a changed work plan, as in the above-mentioned cited reference support system. However, a method of associating the production process with the version of the deliverable, managing which document was changed in response to a certain defect or specification change, and comprehensively checking whether the change content was correct or omitted. There was no.

For this reason, it is not possible to specify the version of the product at any time from the history information of the conventional product, and it is not possible to track whether or not the related product has been changed when the specification is changed. Occasionally a leak occurred in the modification work.

Further, in the conventional software development management, registration of a product and its management information is mainly performed by an operator. As the amount of information increases due to the large scale of software, as in recent years, human registration omissions and input errors are inevitable. In such a case, management of the production process becomes impossible, and maintenance takes a long time. There is a risk that you will have to spend.

SUMMARY OF THE INVENTION An object of the present invention is to overcome the problems in the conventional software production management, automatically manage the history of work and deliverables, and easily and accurately retrieve necessary information. It is to provide a device.

[0010] In the description of the present invention, work is one.
This refers to the work of creating one or more deliverables, and the production process is the work that determines the content of work and the order between the work.

[0011]

SUMMARY OF THE INVENTION An object of the present invention is to manage a production process which manages the generation and change of a plurality of deliverables represented by specifications and programs, which are a plurality of components in a software system. In the method,
The system configuration including the name of the product and the parent-child relationship between the products, the process configuration including the content (or name) of each work in the production process and the order of the work, and the definition including the product version number of the first edition In the case of a work that defines a work / artifact correspondence that associates each work with each of the work and creates a change artifact, a work version number based on the work from the work / artifact correspondence. After retrieving the relevant product and editing the revised product in which the product has been changed, the base product version number is updated in ascending order to obtain the revised product version number, Achieved by registering in addition to the work / deliverable correspondence.

[0012] Further, the process configuration includes a work state of a work which is "incomplete" when defined, and after editing the product by a new or a change, the state of the work is changed from "incomplete" to "completed". It is characterized by the following.

[0013] With this, an arbitrary product is designated, and each of the product version numbers of the product and the content (or name) of the work that created the version are referred to with reference to the work / product correspondence. Related information can be searched and displayed.

Further, the definition of the process configuration includes a correspondence between a process code assigned to each process, such as creation of a predetermined function in the software system and an accident countermeasure, and the work, whereby an arbitrary process can be defined. By designating and referring to the process configuration and the work / product correspondence, history information of the work and the product of the process can be searched and displayed.

Further, in the definition of the process configuration, a work state of the process unit which is "unfinished" at the time of definition is specified, whereby an arbitrary process is designated. A list of tasks included in the process and their states can be displayed.

Further, in the definition of the process configuration, the name of a person in charge for each job is included, whereby an arbitrary person in charge is designated, and by referring to the process configuration and the work / product correspondence relationship, A list of the names of deliverables corresponding to the “unfinished” work of the person in charge can be displayed.

The production process management apparatus for realizing the method of the present invention includes a first table defining a system configuration including a name of the product and a parent-child relationship between the products, and a name of each job in the production process. A second table that defines the process configuration including the job order and the status of the job that is “unfinished” at the time of definition, and associating the product with the job including the product version number of the first edition at the time of definition A third table, a storage device having a product storage unit for accumulating the product, a definition input unit for receiving an input from a terminal to define the first to third tables, and When creating a deliverable, specify the deliverable version number that is the basis of the work from the work / deliverable correspondence, read out the relevant deliverable, edit the revised deliverable, and then edit the revised version. To use The new the product version number the work -
A computer device comprising: a processing device having a work execution means for additionally registering in the product correspondence.

According to the present invention, it is possible to easily search for a history of deliverables including unfinished / completed work and contents of changes, and to support smooth and complete software creation. Further, since the registration of the deliverable and its related information is automated through the editing process, labor saving and reliability of the process management can be improved.
In particular, since the history information covering the correspondence including the production process and the edition history of the deliverable is managed, it is possible to provide a software production process management device capable of acquiring necessary information accurately and easily.

[0019]

Embodiments of the present invention will be described in detail with reference to the drawings. In the following, the development of a software system is taken as an example.

FIG. 1 is a configuration diagram of a software production process management system according to one embodiment. This management system is realized by a computer device including a storage device 100, a definition input unit 110, a work execution unit 120, and an information search unit 130. Definition input means 110 and work execution means 1
20 is a process for receiving and processing information from a worker via an input terminal, and an information searching means 130 is a processing for searching and outputting to a display device in accordance with an instruction from the input terminal and a result of the work executing means 120. It is realized by the function of the CPU.

The storage device 100 includes a system configuration definition table 101 defining the relation between the names of the products and the products in the software system, a process definition table 102 defining the contents of the tasks and the order relation between the tasks, A system / process correspondence table 103 that defines the correspondence between deliverables, a Rev (version number) / process correspondence table 104 that defines the correspondence between work and deliverables and their version numbers, and results that store all versions of the completed deliverable file. An object storage means 105 is provided.

The definition means 110 receives an input from a terminal, and receives a system configuration definition table 101, a process definition table 102, and a system / process correspondence table 10
3 is set according to each format. Note that the system / process correspondence table 103 is
(Version number)-The process correspondence table 104 may absorb the information, and the defining means 110 may define the correspondence between the work and the product and the version number of the first version.

Here, the first table corresponds to the system configuration definition table 101, and the second table corresponds to the process definition table 102. The third table includes a system / process correspondence table 103 and R
The contents of the ev / process correspondence table 104 correspond to one.

The work executing means 120 includes the work guiding means 12
1 and a product editing means 122. The work guiding means 121 guides the work to the worker according to the process definition information set in the process definition table 102. The product editing means 122 supports the creation of the product by the worker, stores the created product file in the product storage means 105, and displays the relationship between the process and the created product version and the product file. Is automatically stored in the Rev / process correspondence table 104.

The information retrieving means 130 is provided for each table 101
A desired information search is performed on the information stored in .about.104 and output to a display device. Also, deliverable storage means 1
From 05, a desired product file is extracted and displayed.

FIG. 2 shows an example of the configuration definition view of the software system. A to G in the figure are symbols (product codes) for identifying the product. Box A,
B and C are documents, and boxes D, E, F and G are programs. The line connecting the boxes indicates the relationship between the deliverables, and here represents the order of creation of the deliverables and the range of influence when a change occurs.

For example, deliverable B (processing specification 1) is created based on deliverable A (functional specification), and deliverable D (module 1) is created based on deliverable B (processing specification 1). It means that it is done. Deliverable B (processing specification 1)
Is changed, the result D (module 1) is changed, and the result G (execution program) is also changed.

FIG. 3 shows an example of a system configuration definition table for defining a configuration view. The system configuration definition table 101 includes a set of a deliverable table 301 of (a) and a relation table 302 of (b), and each has a storage format as illustrated. The product table 301 stores a product name and a product code for uniquely identifying the product. The relationship table 302 stores the parent-child relationship of the product as a product code. For example, child products B and C are defined for parent product A, and child products E and F are defined for parent product C. This clarifies the range in which the creation order and the change of the parent deliverable are affected.

Product table 301 and relation table 30
2 is associated with the product code, and both tables can be searched based on this code. For example, when the deliverable B in the deliverable table 301 is changed, a child deliverable having the parent deliverable code B may be searched from the relation table 302. In the case of this example, first, the child product D is searched, and if the parent product code D exists, the child product G is subsequently searched.

The definition information is input by the definition input unit 110 to the definition information, and is set in the product table 301 and the relation table 302.

FIG. 4 shows a view of the production process 1 according to the first embodiment. The production process 1 represents the order in which all products are newly created in the software system development procedure (FIG. 2). The boxes in the figure represent work, and 1-1 and 1-7 are symbols (work codes) for identifying the work. The lines connecting the boxes indicate the order between tasks. For example, the work of the work code 1-5 is a new creation of the module 2 and is performed after the work of the work code 1-3.

For the sake of simplicity, in the production process of the present example, one product is created from one job. For example, the task of creating a module 2 corresponds to the product E in FIG.
Therefore, the production process 1 has the same structure as the product configuration view in FIG. However, a task may create multiple deliverables, or some tasks may not create a deliverable. In that case, the structure of the composition view of the production process and the product is different.

FIG. 5 shows an example of a process definition table for defining a view of the production process 1. The process definition table 102 includes a set of a process table 501, a work table 502, and a relation table 503, and has a storage format shown in FIGS.

The process table 501 shown in FIG.
It stores a process code for uniquely identifying a process such as "Create function" or "△△ Accident countermeasures", the content (or name) of the process, and the work status (completed / incomplete) for each process. The work table 502 in (b) includes the work code, the process code, the work content (or name),
The name of the worker in charge and the work status of the work are stored.
In the relation table 503 of (c), the order of the work is defined by the work code, such as the work 1-1 after the work 1-1.

Process table 501 and work table 5
02 is associated with a process code, and both tables can be searched by this process code. The work table 502 and the relation table 503 are associated with each other by a work code, and both tables can be searched by the work code. For example, the contents of the work performed after the function specification design (work 1-1) are the processing 1 design (work 1-2) and the processing 2
It is design (Job 1-3), and it can be seen that the charge is Suzuki and Tanaka respectively.

The information input from the terminal is input by the definition input means 110 to the process table 50.
1. Set in the work table 502 and the order table 503. The state of the work in the process table 501 and the work table 502 is set to “unfinished” when the work is defined, and “completed” is automatically set by the work executing means 120 when the work is completed.

FIG. 6 shows a view of the production process 2 according to the second embodiment. The production process 2 is a process for taking countermeasures against a defect that has occurred in a part of the software system shown in FIG. 2, and represents a work of changing the products C, E, F, and G.

FIG. 7 shows an example of the process definition table of the production process 2. Process definition table 102 of this example
Are defined by a set of a process table 701, a work table 702, and an order table 703 as shown in FIGS.

FIG. 8 shows an example of the system / process correspondence table. System / process correspondence table 103
Represents the correspondence between each task and the product created as a result of the task using a task code and a product code. Therefore, the job code is associated with the process definition table 102, and the product code is associated with the system configuration definition table 101. The illustrated example shows the correspondence between the product of the system in FIG. 2 and the work of the production process 1 in FIG. 4 and the work of the production process 2 in FIG. For example, job 1-1 is creation of deliverable A, job 1-3
Represents creation of the deliverable C, and job 2-1 represents a change of the deliverable C. Note that, as described above, the data can be absorbed into the Rev / process correspondence table 104 and put together.

When the relationship between the work order and the product has the same structure as in the system configuration and the production process 1 shown in FIG. 2, the process definition table 102 (FIG. 5) is obtained from the system configuration definition table 101 (FIG. 3). And the system / process correspondence table 103 (FIG. 8) can be automatically generated. Further, in the case of the production process 1, the process definition table 102,
The system / process correspondence table 103 can also be used.

Further, when a process of changing the specifications is defined, on the configuration view shown in FIG.
By selecting the boxes E, F, and G, the process definition table 102 in FIG. 7 and the system / process correspondence table 103 in FIG. 8 can be automatically generated.

FIG. 9 shows an example of the Rev / process correspondence table. The Rev / process correspondence table 104 stores job codes, deliverable codes, Rev numbers (version numbers), and storage locations (addresses) of deliverable documents. From this table, the revision and storage location of the product file created in each job can be known. These pieces of information are automatically set by the work execution unit 120.

Next, the processing operation of the work execution means 120 will be described.
The case of the production process 2 will be described as an example.

FIG. 11 shows a processing flow of the work guiding means. In the process of the work guiding means 121, first, a person in charge is designated and the process definition table 102 (the work table 7 in FIG.
02), and extracts the work code and the contents of the state “incomplete” (S101). Next, based on the work code
The process correspondence table 103 (FIG. 8) is searched to obtain the product code (S102), and the system configuration definition table 101 (product table 301 in FIG. 3) is searched to obtain the product name (S103). ), A list of “unfinished” jobs of the designated person in charge is displayed (S104).

FIG. 12 shows an example of a list of "unfinished" jobs of the designated person in charge by the work guiding means. The person in charge "Tanaka" changes the modules 2 and 3 indicated in the job content according to the job list.
Note that the job list can be a list of all jobs including “completed” by the designated person, AND conditions of a plurality of persons, and a list of jobs in production process units.

FIG. 13 shows a processing flow of the product editing means. The deliverable editing means 122 is started from the display of the work list (FIG. 12) by the work guiding means 121. First, when one job is selected from the job list on the screen and the edit button is pressed (S201, S202), it is determined whether or not the job is newly created (S203). If it is new, the process branches to S204, and if it is changed, the process branches to S205.

First, a case where the work code 2-2 of the change work is selected will be described. Deliverable editing means 122
Searches the Rev / process correspondence table 104 (FIG. 9) based on the product code E of the job 2-2, and specifies the storage location of the file having the largest Rev number among the product codes E Then, the latest file (Rev. No. 1 in this example) of the module 2 is extracted from the deliverable storage means 105 (S205).

Next, the editor is started, and the retrieved file is opened (S206). Here, the product document is changed by the person in charge. When the change is completed, the document is edited into a module 2 file (S
207), and store it in the product storage means 105. Here, it is assumed that the document is stored at address 1000009.

Next, the Rev / process correspondence table 10
4, the work and document relation information, that is, the work code “2-2”, the deliverable code “E”, the Rev number “2”, and the storage location “100009” are added (S4).
209). FIG. 10 shows the Rev.
4 shows an example of a process correspondence table. The Rev number is incremented by one for each product in ascending order. further,
The state of the work code 2-2 in the work table 702 is set to “completed” (S210). Thus, the Rev / process correspondence table 104 is automatically registered. In addition, Rev
The number may be automatically assigned and registered when a new work code is defined in the already-created product code on the system / process correspondence table 103.

On the other hand, if the document is new in S203, a new file is created with the product name newly registered in the product table 301 (S204), and the editor is started (S206) to create a document for the person in charge. Done. Thereafter, it is processed and stored as Rev number 1 in the same manner as in the case of change.

The Rev / process correspondence table 10
In the case of absorbing the system / process correspondence table 103 into a single unit, the work code, the product code, and the first version Rev number 1 are set at the time of definition. Rev
Number 1 may be automatic registration. Of course, the revised Rev
The number is automatically registered after editing or at the time of definition.

As described above, when all the work in the process is completed (S211), the state of the process code 2 in the process table 701 is set to "complete" (S21).
2).

In this embodiment, the editing editor has been described in a specific case.
It is also possible to launch a number of different editors within one process to continuously process the creation of various artifacts.

Next, the processing operation of the information retrieval means 130 will be described. FIG. 14 shows a flow of a search process from a deliverable as an example of information search, and FIG. 15 shows the interrelationship between tables used in this search.

The information retrieval means 130 first reads the deliverable table 1501 and displays the document list (S301). When one deliverable, for example, deliverable E is selected (S302), Rev.
The process correspondence table 1502 is searched (S303),
The work table 1503 is searched based on the work code (S304), the process table 1504 is searched based on the process code (S305), and the related information of the product E is extracted and displayed as a list (S306).

FIG. 16 shows a display example of a search result from an arbitrary product. For deliverable E (module 2), R
The related information such as the ev number, the process code, the contents, the work code, and the worker in charge are displayed.

As described above, it is possible to know the reason (process) of the product from the search result from the product. Further, since the file storage location can be specified from the Rev / process correspondence table 1502, the files of each Rev number are extracted and compared,
The difference can also be specifically displayed.

FIG. 17 shows another example of the information retrieval, a retrieval processing flow from the process, and FIG. 18 shows the interrelationship between the tables used in this retrieval.

The information search means 130 first displays a list of the process table 1801 (S401). For example, when the process code "2" is selected (S402), the work table 1802 is displayed based on the process code 2. A search is performed (S403), a Rev / process correspondence table 1803 is searched based on the work code (S404), and a deliverable table 1804 is searched based on the deliverable code (S405). The information is extracted and displayed in a list (S406).

FIG. 19 shows a display example of a search result from an arbitrary process. For the process 2, related information such as a work code, a charge, a product code, a product name, and a Rev number are displayed. Thereby, it is possible to know all the work codes related to the trouble countermeasures of the process 2 and their Rev numbers. Jobs whose Rev number has not been updated
There is no change or "incomplete".

Although the development of a software system has been described above as an example, the present invention is applicable to a wide range of tasks of generating and changing electronic files as a result of the work.

[0062]

According to the production process management method of the present invention, since the work of the production process is associated with the edition history of the product at the time of editing, the history of the product including the unfinished / completed work and the contents of the change can be easily obtained. You can search and help create software that is smooth and complete.

According to the production process management apparatus of the present invention, the registration of the product and its related information is automated through the editing process, so that labor saving and reliability of the process management can be improved. In particular, since the history information covering the correspondence including the production process and the edition history of the deliverable is managed, it is possible to provide a management device capable of acquiring necessary information accurately and easily.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a production process management system according to an embodiment of the present invention.

FIG. 2 is a system configuration definition view in the software system.

FIG. 3 is a configuration diagram showing a definition example of a system configuration definition table.

FIG. 4 is a view of a production process (1).

FIG. 5 is a configuration diagram showing a definition example of a process definition table of a production process (1).

FIG. 6 is a view of the production process (2).

FIG. 7 is a configuration diagram showing a definition example of a process definition table of a production process (2).

FIG. 8 is a configuration diagram showing a definition example of a system / process correspondence table.

FIG. 9 is a storage example of a Rev / process correspondence table (1).
FIG.

FIG. 10 is a configuration diagram showing a storage example (2) of a Rev / process correspondence table.

FIG. 11 is a processing flowchart of the work guiding means.

FIG. 12 is a display diagram of a work list by the work guiding means.

FIG. 13 is a processing flowchart of a product editing unit.

FIG. 14 is a processing flowchart of an information search unit by designating a deliverable;

FIG. 15 is a table correlation diagram referred to in the processing of FIG. 14;

FIG. 16 is a display diagram of a search result by the processing of FIG. 14;

FIG. 17 is a processing flowchart of an information search unit by process designation.

FIG. 18 is a table correlation diagram referred to in the processing of FIG. 17;

FIG. 19 is a display diagram of a search result by the processing of FIG. 17;

[Explanation of symbols]

100: storage device, 101: system configuration definition table, 102: process definition table, 103: system / process correspondence table, 104: Rev / process correspondence table, 105: deliverable storage means, 110: definition input means, 120: work Execution means, 121: work guidance means, 122: deliverable editing means, 130: information search means,
301: deliverable table, 302: relation table, 50
1, 701: process table, 502, 702: work table, 503, 703: order table, 1501,
1804: Result table, 1502, 1803 ... Re
v / process correspondence table, 1503, 1802... work table, 1504, 1801.

Claims (8)

[Claims] 1. A software production process management method for managing generation and change of a plurality of products represented by specifications, programs, and the like, which are a plurality of components in a software system. The system configuration including the parent-child relationship between the name and the product, the process configuration including the content (or name) of each job in the production process and the order of the work, and the product including the product version number of the first edition at the time of definition In the case of a job that defines a work / artifact correspondence that associates each job and creates a change artifact, the work / artifact correspondence is identified based on the work / artifact correspondence to identify the work version number. After retrieving the relevant product and editing the revised version of the product in which the product has been changed, the base product version number is updated in ascending order to become the revised product version number. How to manage the production process, characterized in that the registration in addition to the work-product correspondence. 2. The process configuration according to claim 1, wherein the process configuration includes a work status of the work that is “unfinished” when defined, and after editing the product by new or changed, changes the work status of the work from “unfinished”. A production process management method characterized by changing to "completed" and setting. 3. The product according to claim 2, wherein an arbitrary product is specified, and each of the product version numbers of the product and the name of the job that created the version (refer to the work / product correspondence). A method for managing a production process, wherein related information such as content is searched for and displayed. 4. The process according to claim 2, wherein the definition of the process configuration includes a correspondence between the process and a process code assigned to each process such as creation of a predetermined function in the software system or measures against an accident. A method of managing a production process, wherein an arbitrary process is designated, and reference is made to the process configuration and the work / product correspondence relationship to search for and display the history information of the work and product of the process. . 5. The process configuration according to claim 4, wherein the definition of the process configuration includes a work state of the process unit that is “unfinished” at the time of definition, and designates an arbitrary process, and the work state of the process is “unfinished”. A list of jobs included in the process and a state of the process, wherein the list is displayed. 6. The process configuration and the job / outcome according to claim 2, wherein the definition of the process configuration includes a name of a person in charge for each job, and specifies an arbitrary person in charge. Refer to the object correspondence, and refer to the “incomplete”
A method for managing a production process, wherein a list of names of deliverables corresponding to a job is displayed. 7. A software production process management device that manages generation and change of a plurality of products represented by specifications, programs, and the like, which are a plurality of components in a software system. A first table that defines a system configuration including a name and a parent-child relationship between deliverables, and a process configuration that includes a name of each job in a production process, an order between jobs, and a work state of a job that is “unfinished” when defined. A storage device having a second table to be defined, a third table for associating each of the deliverables with each of the jobs including a deliverable version number of the first edition at the time of definition, and a deliverable storage means for accumulating the deliverables Definition input means for receiving an input from a terminal to define the first to third tables; and when the task creates a result of the change, After identifying the product version number that is the basis of the work from the product correspondence relationship, reading out the corresponding product, editing the revised product, and then updating the product version number updated for the revised version to the work A production process management device, comprising: a computer device comprising a processing device having a work execution means for additionally registering the product correspondence relationship. 8. The job management system according to claim 7, wherein the second table includes a name of a person in charge of each job, a process code assigned to each process such as creation of a predetermined function or an accident countermeasure, and association of the job with the job, An apparatus for managing a production process, comprising: a search unit for designating an arbitrary person in charge or a process as the processing apparatus and searching for related information of a job related to the specified person or process.