JP2004280811A - Data management device, data management control method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To manage design data capable of reducing artificial mistakes. <P>SOLUTION: A plurality of pieces of different design data for creating a program for obtaining a function of service are included in functional data for constituting the function of service. A data management device is provided with: a client terminal 10 which acquires a plurality of pieces of functional data; and a data control part 351 which collects each piece of functional data to which each piece of common design data belongs, stores or displays them as a single piece of functional data when each piece of the common design data is included in each piece of the design data on the basis of each piece of the design data included in each piece of the functional data acquired by the client terminal 10. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a data management device, a data management control method, and a program.

  Conventionally, a method of managing a design document has been proposed (for example, see Patent Document 1). For example, a design document indicating each function of a service may describe a change between a conventional module and a current module in each module. Then, when creating software using the design document, the operator needs to classify each function included in the design document for each software (module unit). Here, a module means a group of functional components on software for realizing the function of a service in functional units. In large-scale software, a worker realizes a service function by combining a plurality of modules.

  As shown in FIG. 10, for example, “function α design document”, “function β design document”, and “function γ design document” include main information for realizing function α, function β, and function γ, respectively. For example, a function a belonging to module A, a function e belonging to module B, a function h belonging to module C, etc.) are included. This functional design document describes a change of a module different from the conventional one for realizing the corresponding function.

  In order for the worker to classify the above functions into modules, for example, as shown in FIG. 11, for example, first, the client terminal 10 sends a function stored in the function data storage unit 41 in response to an operation instruction from the worker. An instruction to display the design document (functional data) is output to the data management device 30. The data management device 30 acquires the corresponding function data from the function data storage unit 41 based on the input command, and causes the client terminal 10 to display the acquired function data.

  Since the function a, the function e, the function h, and the like among the design data included in the functions α, β, and γ displayed on the client terminal 10 are not classified for each module, the worker The module A and the function e are classified manually by associating them with the module B and the function h with the module C (see FIG. 10).

After that, the operator inputs each design data classified for each module through the client terminal 10 for each module. As shown in FIG. 12, the data management device 30 stores the input design data in the module data storage unit 42 for each module (for example, for each ACC) or for each version (for example, every two versions) to be included. .
JP-A-2002-366589

  However, as described above, the worker refers to the functional design document displayed on the terminal, manually classifies each design data included in the functional design document for each corresponding module, and classifies the data. Since each design data for each module is re-input in association with each module or each version to be incorporated, human input mistakes frequently occur.

  On the other hand, when development is performed in parallel over a plurality of generations, design data serving as a base of development (hereinafter referred to as “base data”) among design data of a generation serving as a base of development. May be extracted, and the extracted maternal data may be used for the next plurality of generations. FIG. 13 is a diagram showing the management status of each design data in each generation. As shown in FIG. 13, for example, when there is parent data common to generation 2 or generation 3 in the design data group 1 in generation 1, the parent data is not only generation 1 but also generation 2 or generation 2. 3 needs to be managed in common.

  This matrix data is used in parallel for each generation, and if a part of the matrix data is changed in a certain generation, it is necessary to reflect the same changes in other generations in consideration of the influence range, There has been an artificial input error such that the reflection is omitted or an error occurs. In the case where some changes are made to many generations, the effects of human input errors become significant.

  With this, each design data included in each function data is efficiently classified and stored or displayed for each piece of information necessary for creating software for realizing the function, and each common data for a plurality of generations is shared. There has been a demand for the development of a system capable of managing each design data capable of reducing human error by collectively managing the design data.

  Accordingly, the present invention has been made in view of the above points, and provides a data management device, a data management control method, and a program capable of managing each design data capable of reducing human error. Aim.

  The invention according to the present application has been made to solve the above problem, and the function data for configuring the function of the service includes a plurality of different design data for creating a program for realizing the function. Based on each design data included in each acquired function data, if each design data includes common design data, each function data to which the common design data belongs is aggregated into one. It is stored or displayed as function data.

  According to the invention of this application, when each piece of design data includes each piece of common design data, each piece of function data to which each piece of common design data belongs is collected and stored as one piece of function data. By being displayed, each design data included in the function data can be stored or displayed for each piece of information (for example, each module) required when creating software for realizing the function. In addition, since each design data is stored or displayed for each of the above-mentioned necessary information without human intervention, human error is further reduced.

  In the above-mentioned invention, application information indicating information on a time at which the function data is applied is included in the function data, and based on each application information included in each of the acquired function data, each common information in each application information is When there is application information, each function data to which each piece of common application information belongs may be collected and stored or displayed as one function data.

  In this case, if there is common application information in each application information based on each application information (for example, for each included version) included in each acquired function data, the common application information Is collected and stored or displayed as one function data, so that the design data included in the function data can be stored for each application information.

  In the above invention, when the application information indicating the information about the time when the function data is to be applied is acquired, and the application information that matches the application information is stored based on the acquired application information, The function data to which the matching application information belongs (for example, the function data of the function α belonging to the second version) may be deleted.

  In this case, if application information that matches the non-application information is stored based on the acquired non-application information, the function data associated with the matching application information is deleted, Only function data associated with unnecessary application information can be quickly deleted.

  In the above invention, the function data includes each title name and different design data associated with each title name, and based on each title name included in the acquired function data, In the case where the common titles are included in the names and the contents of the design data associated with the common titles are different, the fact that they are different may be notified.

  In this case, based on each title name included in each of the acquired function data, each title name includes a common title name, and each design data is associated with each common title name. When the contents are different, the fact that the contents are different is notified, thereby preventing each worker from changing the common design data.

  In the above invention, the function data for implementing the function of the service includes each title name and different design data associated with each title name, and each of the function data included in the acquired function data. When each design data includes common design data based on the design data, each function data to which the common design data belongs is acquired, and each title name included in the acquired function data is acquired. If each of the common title names is included in the list, and the contents of the respective design data associated with the common title names are different, the fact that they are different may be notified.

  In this case, when each piece of design data includes each piece of common design data (for example, module A), each piece of function data to which each piece of common design data belongs is acquired. If each of the included title names includes a common title name, and the contents of the respective design data associated with the common title names are different, the fact that the contents are different is notified, An operator is prevented from changing common design data with each other, for example, for each module.

  Also, in the invention according to the present application, the function data for configuring the function of the service includes a plurality of different design data serving as a reference for creating a program for realizing the function, and the design data is changed. Later change data and application information indicating information on the time to apply the change data are obtained, and the change data is the same as the change information corresponding to the application information and other application information related to a later time than the application information. Is stored or displayed as

  According to the present invention, the change data after the design data is changed and the application information indicating the information on the timing of applying the change data are acquired, and the change data is obtained after the application information and the application information are applied. By storing or displaying the same as the change data corresponding to the other application information related to the timing, it is possible to easily change the common design data over a plurality of timings. That is, when there is common design data corresponding to a plurality of times, if the design data corresponding to one time is changed, the design data corresponding to a time later than the one time is also changed. As a result, human errors due to omission of reflection of changes or errors are reduced. As a result, if the worker changes only the design data corresponding to the corresponding time without being aware of each time, the changed content is reflected in the design data at a time later than the time. In addition, it is possible to easily change the design data that is the basis of development over each period and manage the change history.

  In the above invention, each application information is associated with a plurality of generations, and the change data may be stored or displayed as being the same as the change data corresponding to a later generation than the generation corresponding to the application information. Good. In this case, since the change data is stored or displayed as being the same as the change data corresponding to the generation subsequent to the generation corresponding to the application information, the common design data over a plurality of generations is collectively collected. Can be changed. That is, when there is common design data corresponding to a plurality of generations, if the design data corresponding to one generation is changed, the design data corresponding to a time later than the one generation is also changed. As a result, human errors due to omission of reflection of changes or errors are significantly reduced.

  In the above invention, a plurality of generations are associated with each application information, and the application information is associated with a plurality of different design data included in the function data. Of the application information corresponding to the specified generation, the application information regarding the latest time at which the change data is associated is specified for each design data, and each change data corresponding to the specified application information is one function. It may be stored or displayed as data.

  In this case, among the pieces of application information corresponding to the specified generation, application information relating to the latest time at which the change data is associated is specified for each design data, and each application information corresponding to the specified application information is specified. By storing or displaying the change data as one function data, it is possible to combine the latest change data in the designated generation into one.

  In the above invention, when the change data is not associated with each application information corresponding to the designated generation, the change data is associated with each application information corresponding to the generation earlier than the generation. The application information regarding the latest time of the application may be specified. In this case, among the application information corresponding to the specified generation, even if there is no application information associated with the change data, the application information associated with the latest change data in another generation is Since it is specified, not only the specified generation but also the previous generation can be considered, and the latest change data can be combined into one.

  In the above invention, each application information is associated with a plurality of generations, and the first design data as the change source of the acquired change data is changed in the application information relating to a time earlier than the acquired application information. If so, that may be reported. In this case, if the first design data from which the acquired change data is changed has been changed in the application information related to a time earlier than the acquired application information, the fact is notified by Since the effect of the changed portion on the same design data over a plurality of generations is notified to the operator, the operator can prevent the input error of the changed data in advance by checking the content of the notification.

  As described above, according to the present invention, it is possible to manage each design data that can reduce human error.

[First embodiment]
(Basic configuration of data management system)
A data management system 1 according to the present invention will be described with reference to the drawings. FIG. 1 is a schematic configuration diagram of a data management system 1 according to the present embodiment. As shown in FIG. 1, the data management system 1 includes client terminals 10a to 10c, a communication network 20, and a data management device 30 in this embodiment.

  FIG. 2 is a diagram showing how design data including software changes in various functions is classified for each module. As illustrated in FIG. 2, the data management system 1 performs, for example, a process of classifying a change point of each module included in the service function A or the service function B for each module. The data management system 1 that has performed this process performs a process of displaying or storing the changes classified for each module as a module design document. Here, in the present embodiment, a module means a group of functional components on software for realizing the function of a service in functional units. The detailed description of the data management system 1 is as follows.

  The client terminals 10a to 10c (data acquisition means) acquire a plurality of function data for configuring service functions. Here, the function data includes a plurality of different design data for creating a program for realizing the function. In the present embodiment, the design data specifies a changed part and a changed content of the software component in the module for realizing the function of the service.

  The design data includes application information indicating the time or class (including the number of included versions) at which the function data is applied. Further, the client terminals 10a to 10c acquire a plurality of pieces of non-applicability information indicating a time or a class at which the function data is not applied. This non-applicable information is information added to a design document whose inclusion has been forgotten due to a change in specifications after the design document has been created.

  The communication network 20 connects the client terminals 10a to 10c and the data management device 30 for communication.

  In the present embodiment, the data management device 30 (data control unit) includes a display 31, a keyboard 32, a memory 33, a data reading unit 34, a CPU 35, a hard disk 36, and a design data storage device 40. ing.

  In the present embodiment, the design data storage device 40 includes a function data storage unit 41 and a module data storage unit 42. The function data storage unit 41 stores a plurality of function data for realizing the function of the service. FIG. 3 is a diagram illustrating the contents of each function data stored in the function data storage unit 41.

  As shown in FIG. 3, in the present embodiment, the function data is, for example, “attribute” indicating the title name of the design data belonging to the function data, “change type” indicating the type to be changed, and data corresponding to “attribute”. “Design data” indicating the contents of the “design data”. Here, as shown in FIG. 3, the “attribute” is a version name (application information) indicating a time when function data is applied, a service function name, a module name to be changed, a function name to be changed, a change content, and each parameter. And the like.

  The “change type” includes deletion, change, or addition. The “design data” includes the contents of the version name (2nd and 3rd edition, etc.), the contents of the function name (A service, B service, etc.), the contents of the module to be changed (ACC, SDM, etc.), the contents of the change function (Acc_int , Sdm int, etc.), data corresponding to the changed content (initial setting data, etc.), and the content of each parameter (a_but, c_kng, etc.).

  The display 31 displays the contents of the data set in the design data storage device 40. The keyboard 32 receives an input operation from an operator.

  In the present embodiment, the hard disk 36 includes a data control program storage unit 361 that stores a data control program for realizing the present invention, and an OS storage unit 362 that stores an operating system. Further, the hard disk 36 stores a control program for controlling the data management device 30 and the like.

  The data reading unit 34 reads a program or the like stored in a storage medium (for example, a CD-ROM) in accordance with an instruction from the keyboard 32, and stores the read program or the like in the hard disk 36. Each program stored in the hard disk 36 is installed from the data reading unit 34.

  The CPU 35 includes a data control unit 351. The data control unit 351 is configured to, based on each design data included in each function data acquired by the client terminal 10, when each design data includes common design data, the common design data The function data to which the data belongs is collected and stored in the module data storage unit 42 as one function data. The “function data acquired by the client terminal 10” is not limited to only the function data acquired “directly” by the client terminal 10, but includes the function data stored in advance in the function data storage unit 41. Data shall be included.

  Specifically, as shown in FIG. 3, each design data included in the function data 1 is “A service” and “ACC”, and each design data included in the function data 2 is “B service”, If the design data is “ACC” and the design data included in the function data 3 is “C service” and “SDM”, the data control unit 351 includes the function data 1, the function data 2, and the function data 3 The common design data “ACC” is specified from the design data to be shared.

  The data control unit 351 specifies the function data 1 and the function data 2 to which the specified design data “ACC” belongs. The data control unit 351 collects the specified function data 1 and function data 2 and stores them as one function data in the module data storage unit 42, and displays the same contents on the screen of the client terminal 10.

  In addition, based on each “version name (application information)” acquired by the client terminal 10, the data control unit 351 determines, when there is a common “version name” among the “version names”, The function data to which the common “version names” belong is collected and stored in the module data storage unit 42 as one function data.

  Specifically, as shown in FIG. 4, each design data included in the function data 1 is “second edition”, “A service”, “ACC”. , “2nd edition”, “B service”, “ACC”... If the design data included in the function data 3 is “3rd edition”, “C service”, “SDM”. The control unit 351 specifies a common version name “2nd version” from among the design data included in the function data 1, the function data 2, and the function data 3.

  The data control unit 351 specifies the function data 1 and the function data 2 to which each specified version name “2nd version” belongs. The data control unit 351 collects the specified function data 1 and function data 2 and stores them as one function data in the module data storage unit 42, and displays the same contents on the screen of the client terminal 10. Arrows shown in FIG. 4 indicate how each function data is stored as one function data.

  Note that the data control unit 351 may store a set of the specified function data 1 and function data 2 in the module data storage unit 42 for each common module name. Each of the design data stored in the function data storage unit 41 and the module data storage unit 42 has the contents shown in FIG. 4 (version name; second and third editions, function name of service; A service, B service, C service) , D service, change module name; ACC, etc.), and may be other types of design data.

  Further, based on the non-applicability information acquired by the client terminal 10, the data control unit 351 stores the function to which the version name belongs when the version name matching the non-applicability information is stored in the module data storage unit 42. The data is deleted from the module data storage unit 42.

  Specifically, when the non-applicable information is “2nd edition”, the data control unit 351 stores the version name “2nd edition” that matches the non-applicable information “2nd edition” from the module data storage unit 42. Identify. As shown in FIG. 4, when the function data to which the specified version name “2 edition” belongs is function data 1 and function data 2 as shown in FIG. 4, the contents of the function data 1 and function data 2 From the module data storage unit 42. The data control unit 351 causes the content of the deleted data to be displayed on the screen of the client terminal 10.

  Further, the data control unit 351 includes, based on each attribute included in each function data acquired by the client terminal 10, common attributes among the attributes, and associates the common attributes with the common attributes. If the contents of the design data (conflicting change contents) are different, the difference is notified.

  Specifically, each function data is function data 1 and function data 2, and each attribute included in the function data 1 and function data 2 is "version name", "service function name", and "change function name". In this case, the data control unit 351 specifies common attributes “version name”, “service function name”, and “change function name” included in the function data 1 and the function data 2 for each function data.

  If at least the design data (for example, “Acc_int”, “Sdm int”) associated with the “change function name” common to the function data 1 and the function data 2 is different, the data control unit 351 determines that the difference is different. To inform. It is preferable that the data control unit 351 be notified with a warning sound or a warning mark (for example, a mark indicating a different part). This warning sound is output via a speaker provided in the client terminal 10. The warning sign is output on a screen provided in the client terminal 10.

  In addition, based on each design data included in each function data acquired by the client terminal 10, the data control unit 351 includes, when each design data includes common design data, Each function data to which the design data belongs is acquired, and based on each attribute included in the acquired function data, each attribute includes a common attribute, and each design is associated with the common attribute. If the contents of the data are different, it may be notified that the contents are different.

(Data management control method using data management system)
A data management control method using the data management system 1 having the above configuration can be performed according to the following procedure. FIG. 5 is a flowchart illustrating a procedure of the data management control method according to the first embodiment.

  As shown in FIG. 5, in step 101, the client terminal 10 displays a screen for instructing input of each function data. The client terminal 10 stores the input function data in the function data storage unit 41. Then, the client terminal 10 outputs a conversion command signal for converting the corresponding function data into a predetermined format to the data management device 30 in response to an operation instruction from the worker.

  The data control unit 351 to which the conversion command signal has been input from the client terminal 10 reads out the data control program (for executing the conversion procedure and the like) from the data control program storage unit 361 and executes the program.

  In step 102, the data control unit 351 acquires corresponding function data from the function data storage unit 41 in response to a request from the client terminal 10.

  In step 103, the data control unit 351 includes, based on each attribute included in each function data acquired by the client terminal 10, a common attribute in each attribute, and corresponds to the common attribute. It is checked whether or not the content of each attached design data (the content of the conflicting change) is different. If the common attributes are included in the attributes, and the contents of the design data (conflicting changes) associated with the common attributes do not differ, the data control unit 351 determines in step 104. When the contents of the respective design data are different, the process proceeds to step 105.

  In step 104, based on each design data included in each function data acquired by the client terminal 10, the data control unit 351 determines, when each design data includes common design data, The function data to which the respective design data (for example, the change module) belong is collected and stored as one function data in the module data storage unit 42, and the same contents are displayed on the screen of the client terminal 10.

  Alternatively, if there is a common “version name” among the “version names” based on the “version names (application information)” acquired by the client terminal 10, The function data to which the common “version names” belong is collected and stored as one function data in the module data storage unit 42, and the same contents are displayed on the screen of the client terminal 10.

  Alternatively, based on the non-applicability information acquired by the client terminal 10, the data control unit 351 stores the function to which the version name belongs when the version name matching the non-applicability information is stored in the module data storage unit 42. The data is deleted from the module data storage unit 42. The data control unit 351 causes the content of the deleted data to be displayed on the screen of the client terminal 10.

  In step 105, the data control unit 351 includes, based on each attribute included in each function data acquired by the client terminal 10, a common attribute in each attribute, and corresponds to the common attribute. It notifies that the contents (competitive changes) of each attached design data are different.

  Note that the program can also be executed according to the procedure shown in FIG. Note that the program can be recorded on a recording medium. Examples of the recording medium include a flexible disk, a compact disk, a hard disk, a memory card, a ROM, a punch card, and a tape.

  Further, the recording medium is not limited to a recording medium on which a program that can be directly executed by a computer is recorded, but records a program that can be executed once by installing it on another recording medium (such as a hard disk). It also includes a recording medium and a recording medium on which an encrypted or compressed program is recorded.

(Operation and effect of the data management system and the data management control method)
According to the invention of the present application, when the data control unit 351 includes the common design data in the design data based on the design data included in the function data, the data control unit 351 performs the common operation. By collecting each function data to which each design data belongs and storing or displaying the same as one function data, the data control unit 351 converts each design data included in the function data into software for realizing the function. Can be efficiently classified and stored for each piece of information required (e.g., for each module), and human input errors can be reduced.

  In addition, when there is a common “version” among the “versions” included in the design data, the data control unit 351 collects the functional data to which the common “version” belongs and collects one. By storing or displaying as the function data, the data control unit 351 can classify and store the design data included in the function data for each application information, and can further reduce artificial input mistakes. .

  Further, when the “version” that matches the inapplicability information is included in the module data storage unit 42 based on the inapplicability information, the data control unit 351 stores the function data associated with the “version” in the module data. By deleting from the storage unit 42, the data control unit 351 can quickly delete only the function data corresponding to unnecessary application information.

  In addition, the data control unit 351 includes, based on each attribute included in each function data, each attribute included in each attribute, and the contents of each design data associated with each common attribute are different. In such a case, by notifying the difference, the data control unit 351 can prevent each worker from changing design data that conflicts with each other.

  Finally, when the common design data is included in the design data included in the function data, the data control unit 351 acquires the function data to which the common design data belongs, and acquires the acquired function data. When the common attributes are included in the attributes included in the function data, and the contents of the design data associated with the common attributes are different, the fact that the contents are different is notified by notifying the difference. The unit 351 can prevent each worker from changing design data that conflicts with each other, for example, for each module.

[Second embodiment]
A second embodiment of the present invention will be described with reference to the drawings. FIG. 6 is a diagram illustrating an internal structure of the data management system 1 according to the present embodiment. As shown in FIG. 6, the data management system 1 has almost the same internal structure as that of the first embodiment, but differs from the process of storing design data groups and the function of the generation information storage unit 43. . Hereinafter, since it is the same as the first embodiment except for the difference from the first embodiment, the description other than the difference is omitted.

(Configuration of data management system)
FIG. 7 is a diagram showing a design data table stored in the function data storage unit 41. As shown in FIG. 7, the design data table is associated with generation information (for example, generation 1, generation 2, generation 3...) For indicating the timing or number of development improvements, and the generation information. And a design data group (function data) including the change data in the incorporated version number (application information such as 2-2.0, 2-2.1...) For indicating the time or number of times the change data (design data) ) Is associated.

  Here, in the present embodiment, for example, 2002-2 of generation 1 means data improved in February 2002, and 2003-1 of generation 2 indicates data improved in January 2003. It means that The included version number 2-2.0 means the basic data for February 2002, and 2-2.1 the first time improved from the data for February 2002. Data. Note that the same applies to other included version numbers and generation information, and a detailed description thereof will be omitted.

  The included version number 2-2.0 of the generation 1 includes design data a0, design data b0, design data c0, and a plurality of different design data (base data) serving as references for creating a program for realizing the function. The design data d0 and the design data e0 are associated with each other. As will be described later, the parent data is sequentially changed for each generation or for each included version. It should be noted that the parent data is generally one in which data in another generation is cited, and is assumed to be a type of change data described later.

  When the change data after the design data is changed and the included version number of the changed data are acquired, the data control unit 351 stores the changed data after the included version number and the included version number. Is stored in the function data storage unit 41 or displayed on the client terminal 10 as being the same as the change data corresponding to the other included version numbers regarding the timing of.

  As shown in FIG. 7, specifically, when the acquired change data is a1 ″ and the acquired included version number is 3-1.0, the data control unit 351 determines the included version number. At the location corresponding to 3-1.0 and the original design data A, the change data a1 "is stored or displayed, and the change data a1" is included. It is stored or displayed as the same as the change data corresponding to the numbers (3-1.1, 3-1.2, 3-1.3, 3-1.4 ...) (see the arrow in FIG. 7). 7, the data control unit 351 converts the acquired change data a1 "into a generation 3 that is later than the generation 2 corresponding to the acquired embedding version number 3-1.0. It is stored or displayed as the same as the changed data.

  The data control unit 351 assigns, for each design data (design data A, design data B,...), Among the included versions corresponding to the specified generation, the included version regarding the latest timing associated with the change data. The specified change data corresponding to the specified included version numbers is stored as one function data in the generation information storage unit 43 or displayed on the client terminal 10. The process of prompting the user to specify one of the generations is executed by the client terminals 10a to 10c.

  FIG. 8 is a diagram illustrating a state in which a plurality of pieces of change data corresponding to the latest included version number in a specific generation are collected as one function data. As shown in FIG. 8, when the designated generation is 1, the data control unit 351 sends the design data A, design data B, and design data corresponding to the latest included version number of the designated generation 1. A1 ′, b1, c0, d1, and e0 are specified as change data of C, design data D, and design data E (see the solid-line arrow in FIG. 8, processing 1), and each specified change data is identified as one. It is stored in the generation information storage unit 43 as function data (see generation 1 ′ in FIG. 8) or displayed on the client terminal 10.

  Similarly, when the designated generation is 2, the data control unit 351 transmits the design data A, design data B, design data C, design data D, and design data E corresponding to the latest included version number. A1 ″, b1 ′, c1 ″, d1, and e1 are specified as the change data (see the dashed-dotted arrows in FIG. 8, processing 1 and processing 2), and the specified change data is converted into one function data (FIG. 8 is stored in the generation information storage unit 43 or displayed on the client terminal 10. Since there is no change data of the design data D in the specified generation 2, the latest change data d1 in the generation 1 before the generation 2 is specified (see process 2 in FIG. 8). .

  When the designated generation is 3, the data control unit 351 changes the design data A, design data B, design data C, design data D, and design data E corresponding to the latest included version number. A1 ″, b2 ′, c1 ″, d1 ′, and e1 ″ are respectively specified (see arrows indicated by two-dot broken lines in FIG. 8, processing 1 and processing 2), and each specified change data is converted into one function data ( 8 is stored in the generation information storage unit 43 or displayed on the client terminal 10. Since there is no change data of the design data A and the design data C in the designated generation 3, The latest change data a1 ″ and c ″ in the generation 2 before the generation 3 is specified (see processing 2 in FIG. 8).

  In addition, based on the acquired change data and the included version number, the data control unit 351 changes the first design data from which the changed data is changed in a generation earlier than the generation corresponding to the included version number. If so, the client terminal 10 is informed. As shown in FIG. 8, specifically, when the acquired change data is a1 'and the specified generation information is generation 2, the generation data before generation 2 corresponding to the change data a1' is specified. Since the data has been changed to the changed data a1 'in generation 1, the data control unit 351 notifies the client terminal 10 of the change.

(Data management control method using data management system)
A data management control method using the data management system 1 having the above configuration can be performed according to the following procedure. FIG. 9 is a flowchart illustrating a procedure of the data management control method according to the second embodiment.

  As shown in FIG. 9, in step 201, the client terminal 10 urges input of change data corresponding to the included version number and generation information, and acquires the input change data. The client terminal 10 outputs the acquired change data to the data control unit 351.

  In step 202, the data control unit 351 determines, based on the acquired change data and the included version number, the timing at which the first design data from which the changed data is changed is earlier than the included version number (or generation). Check whether the included version (or generation) has been changed.

  Further, based on the acquired change data and the included version number, the data control unit 351 determines whether or not the first design data as the change source of the changed data is the included version regarding the time earlier than the included version number (or generation). If the number (or generation) has been changed, the process proceeds to step 203, where the first design data from which the changed data is changed is the included version number (or generation) related to a time earlier than the included version number (or generation). If no change has been made in (or generation), the process proceeds to step 204.

  In step 203, the data control unit 351 warns that the input change data has been changed in another generation information. Specifically, when the change data corresponding to the generation 1 as the generation information is a1 ', and when the change data a1' corresponding to the generation 2 as the generation information is input, the data controller 351 Since the same change data a1 'exists in each generation, a warning to that effect is issued.

  In step 204, the data control unit 351 reflects the input change data in other generation information. Specifically, when the generation information is generation 2 and the change data is a1 ", the data control unit 351 converts the input change data into a version after the included version number corresponding to the change data. It is stored in the function data storage unit 41 as being the same as the change data corresponding to the other included version numbers or generation information relating to the timing.

  In step 205, the client terminal 10 prompts for specification of specific generation information. When this generation information is specified, the latest change data in the specified generation information is stored or displayed as one function data by the following processing.

  In step 206, the data control unit 351 confirms whether or not there is an included version number related to the latest time to which the change information is associated among the included information corresponding to the specified generation information. If there is an included version number relating to the latest time associated with the change information, the data control unit 351 proceeds to the process of step 207, and includes the incorporated version number relating to the latest time associated with the change information. If there is no, the process proceeds to step 208.

  Specifically, when the specified generation information is generation 3, the change data b2 is associated with the included version number 3-2.0 in the design data B, and the included version number in the similar design data B. Since the change data b2 ′ is associated with 3.2.1, the data control unit 351 determines that the latest included version number 3-2.1 exists in generation 3 and design data B, and step 207 is performed. Move on to processing. On the other hand, when the specified generation information is generation 3, since the change data is not associated with each included version number in the design data A, the data control unit 351 sends the latest It is determined that there is no included version number, and the process proceeds to step 208. The process of step 206 is executed for each design data.

  In step 207, the data control unit 351 executes the extraction process 1 (the process 1 in FIG. 8). Specifically, as shown in FIG. 8, when the specified generation information is generation 1, the data control unit 351 determines that the change data corresponding to the latest included version number of the generation 1 is a1 ′, Since they are b1, c0, d1, and e0, the respective change data is stored in the generation information storage unit 43 as one function data (generation 1 ′ in FIG. 8).

  In step 208, the data control unit 351 executes the extraction process 2 (the process 2 in FIG. 8). Specifically, as shown in FIG. 8, when the specified generation information is generation 2, the data control unit 351 changes the design data D corresponding to the latest included version number of the generation 2 Does not exist, the latest change data d1 of the design data D in the generation 1 before the specified generation 2 is included in one function data (generation 2 ′ in FIG. 8) and stored in the generation information storage unit 43. Let it.

  Note that, except for the design data D corresponding to the generation 2, all the change data is associated with the included version number of the generation 2, and the data control unit 351 performs the processing of the latest The change data a1 ″, b1 ′, c1 ″, and e1 are included in one function data (generation 2 ′ in FIG. 8) and stored in the generation information storage unit 43.

  In step 209, the data control unit 351 checks whether the extraction processing 1 or the extraction processing 2 corresponding to all the design data in the specified generation information has been performed. Specifically, when the specified generation information is generation 2, the data control unit 351 changes the design data A, the design data B,... It is confirmed whether the data extraction processing 1 and the extraction processing 2 are executed and the extraction processing 1 or the extraction processing 2 in the last design data E is completed. When the extraction processing 1 or the extraction processing 2 corresponding to all the design data in the specified generation information has been executed, the data control unit 351 terminates the processing operation 2 and performs all the design in the specified generation information. If the extraction processing 1 or the extraction processing 2 corresponding to the data has not been executed, the process proceeds to step 206.

(Operation and effect of the data management system and the data management control method)
According to the present invention as described above, the change data after the design data is changed and the embedding version number that is information on the timing of applying the change data are acquired, and the change data is obtained from the embedding version number and the embedding version number. Is also stored or displayed as being the same as the change data corresponding to the other included versions regarding the later time, so that each common design data over a plurality of included versions can be easily changed. Become. In other words, when there is common design data corresponding to a plurality of included versions, if the design data corresponding to one included version is changed, the included versions after the one included version are changed. Is also changed, and human errors due to omission of reflection of the changed points or errors are reduced. As a result, if the worker changes only the design data corresponding to the included version number without being aware of each included version number, the changed content may be the included version number later than the included version number or Since the design data in the generations is also reflected, it is possible to easily change the design data, which is the base of development for each generation, and manage the change history.

  Also, since the change data is stored or displayed as being the same as the change data corresponding to the generation later than the generation corresponding to the included version number, the common design data across multiple generations is collectively changed. It is possible to be. That is, when there is common design data corresponding to a plurality of generations, if the design data corresponding to one generation is changed, the design data corresponding to a generation later than the one generation is also changed. As a result, human errors due to omission of reflection of changes or errors are significantly reduced.

  Furthermore, of the included versions corresponding to the specified generation, the included version regarding the latest time at which the change data is associated is specified for each design data, and each of the included versions corresponding to the specified included version is specified. By storing or displaying the changed data as one function data, it is possible to combine the latest design data in the designated generation into one.

  In addition, even if there is no included version number associated with the change data among the included version numbers corresponding to the specified generation, the included version number associated with the latest change data in another generation is also included. Since the number is specified, it is possible to combine the latest design data into one by considering not only the specified generation but also the previous generation.

  Further, when the original design data from which the acquired change data is changed has been changed in the included version number related to a time earlier than the acquired included version number, a notification to that effect is issued. Since the effect of the changed portion on the same design data over the next generation is notified to the operator, the operator can prevent the input error of the changed data in advance by checking the content of the notification.

  The invention in the second embodiment may be configured by combining the inventions in the first embodiment.

It is a figure showing the internal structure of the data management system in a first embodiment. It is a figure showing signs that each design data of each function is classified for every module in a first embodiment. It is a figure showing the contents of each function data memorized by the function data storage part in a first embodiment. It is a figure showing signs that each function data in a first embodiment is converted into a specific format. It is a flowchart which shows the procedure of the data management control method in 1st embodiment. It is a figure showing the internal structure of the data management system in a 2nd embodiment. It is a figure showing a situation when change data is changed in a 2nd embodiment. It is a figure showing signs that a plurality of change data in a 2nd embodiment are put together as one functional data. It is a figure showing the procedure of the data management control method in a 2nd embodiment. FIG. 2 is a conventional diagram showing a state in which design data of each function is classified for each module. 1 is a conventional diagram showing the internal structure of a data management system. FIG. 4 is a conventional diagram showing a state in which design data of each function is classified for each module and each version. FIG. 3 is a conventional diagram showing a management status of each design data in each generation.

Explanation of reference numerals

  DESCRIPTION OF SYMBOLS 1 ... Data management system, 10 ... Client terminal, 20 ... Communication network, 30 ... Data management device, 31 ... Display, 32 ... Keyboard, 33 ... Memory, 34 ... Data reading part, 35 ... CPU, 36 ... Hard disk, 40 ... Design data storage device 41 functional data storage unit 42 module data storage unit 43 generation information storage unit 351 data control unit 361 data control program storage unit 362 OS storage unit

Claims (21)

The function data for configuring the function of the service includes a plurality of design data for creating a program for realizing the function, a data acquisition unit for acquiring a plurality of the function data,
Based on the design data included in the function data acquired by the data acquisition means, if the design data includes common design data, the common design data belongs to the design data. A data management device, comprising: data control means for collecting each function data and storing or displaying the same as one function data. The function data includes application information indicating information on a time to apply the function data,
The data control unit, based on the application information included in the function data acquired by the data acquisition unit, includes, when there is common application information in the application information, the common application information. 2. The data management device according to claim 1, wherein each function data to which each application information belongs is collected and stored or displayed as one function data. The data obtaining unit obtains non-applicability information indicating information on a time when the function data is to be non-applied,
The data control unit is configured to, based on the non-applicability information acquired by the data acquisition unit, store the function data to which the application information belongs when the application information that matches the non-application information is stored. The data management device according to claim 2, wherein the data management device is deleted. The function data includes each title name and the respective design data associated with each title name,
The data control means includes, based on the title names included in the function data acquired by the data acquisition means, a common title name included in the title names, 2. The data management device according to claim 1, wherein when the contents of each design data associated with the name are different, the fact that the contents are different is notified. The function data includes each title name and the respective design data associated with each title name,
The data control means, based on the design data included in the function data acquired by the data acquisition means, when the common design data is included in the design data, Acquiring the respective function data to which the respective design data belongs, and based on the respective title names included in the acquired respective function data, the respective title names include the respective common title names, and the common respective titles. 5. The data management apparatus according to claim 4, wherein when the contents of the respective design data associated with the name are different, the difference is notified. The function data for configuring the function of the service includes a plurality of different design data serving as a reference for creating a program for realizing the function, a data management device that manages the function data,
Data acquisition means for acquiring change data after the design data has been changed, and application information indicating information on the time to apply the change data,
Based on the change data and the application information acquired by the data acquisition unit, the change data is the same as the change information corresponding to the application information and other application information relating to a time later than the application information. And a data control means for storing or displaying the data as a data management device. Each application information is associated with a plurality of generations,
The data control unit, based on the change data and the application information acquired by the data acquisition unit, the change data is the same as the change data corresponding to a later generation than the generation corresponding to the application information 7. The data management device according to claim 6, wherein the data management device is stored or displayed as being. A plurality of generations are associated with each application information, and the application information is associated with a plurality of different design data included in the function data,
Designation means for prompting designation of any generation,
Application information specifying means for specifying, for each design data, application information relating to the latest time at which the change data is associated, among the application information corresponding to the designated generation,
8. The data management device according to claim 7, wherein the data control unit stores or displays each change data corresponding to each application information specified by the application information specifying unit as one function data.   When the change data is not associated with each application information corresponding to the specified generation, the application information specifying unit determines that the change data corresponds to the application information corresponding to the generation before the generation. 9. The data management apparatus according to claim 8, wherein application information regarding the latest attached time is specified. Each application information is associated with a plurality of generations,
The data control unit is based on the change data and the application information acquired by the data acquisition unit, based on the application information of the first design data of the change source of the change data is earlier than the application information 7. The data management apparatus according to claim 6, wherein, when the data has been changed, the user is notified of the change. The function data for configuring the function of the service includes a plurality of design data for creating a program for realizing the function, a first step of acquiring a plurality of the function data,
On the basis of the respective design data included in the respective function data acquired in the first step, when the respective design data includes the respective common design data, the common respective design data belongs. A second process of collecting each function data and storing or displaying the same as one function data. The function data includes application information indicating a time or a class to apply the function data,
In the second step, based on the application information included in the function data acquired in the first step, if there is common application information in each of the application information, the common information 12. The data management control method according to claim 11, wherein each function data to which each application information belongs is collected and stored or displayed as one function data. In the first step, to obtain non-application information indicating the time or class to make the function data non-application,
In the second step, based on the non-application information acquired in the first step, if the application information that matches the non-application information is included, the function data to which the application information belongs is deleted. 13. The data management control method according to claim 12, wherein: The function data includes each title name and each of the different design data associated with each title name,
In the second step, based on the title names included in the function data acquired in the first step, each title name includes a common title name, and the common titles 12. The data management control method according to claim 11, wherein when the contents of the respective design data associated with the name are different, the difference is notified. The function data includes each title name and each of the different design data associated with each title name,
In the second step, based on the respective design data included in the respective function data acquired in the first step, if each of the design data includes common design data, Each function data to which each design data belongs is collected, and based on each title name included in the collected each function data, each title name includes a common title name, and each common title includes 15. The data management control method according to claim 14, wherein when the contents of the respective design data associated with the name are different, the fact of the difference is notified. The function data for configuring the function of the service includes a plurality of different design data serving as references for creating a program for realizing the function, and is a data management control method for managing the function data. ,
A first step of obtaining change data after the design data has been changed, and application information indicating information on a time to apply the change data,
Based on the change data and the application information acquired in the first step, the change data is the same as the change information corresponding to the application information and other application information related to a time later than the application information. And a second step of storing or displaying as a data management control method. On the computer,
The function data for configuring the function of the service includes a plurality of different design data for creating a program for realizing the function, a first step of acquiring a plurality of the function data,
Based on the respective design data included in the respective function data acquired in the first process, when the respective design data includes the respective common design data, the common respective design data belongs. A program for executing a process having a second step of collecting each function data and storing or displaying the same as one function data. The function data includes application information indicating a time or a class to apply the function data,
In the second step, based on the application information included in the function data acquired in the first step, if there is common application information in each of the application information, the common information The program according to claim 17, wherein the program is configured to execute a process of collecting each function data to which each piece of application information belongs and storing or displaying the same as one piece of function data. In the first step, to obtain non-application information indicating the time or class to make the function data non-application,
In the second step, based on the non-application information acquired in the first step, if the application information that matches the non-application information is included, the function data to which the application information belongs is deleted. The program according to claim 18, for causing a computer to execute a process. The function data includes each title name and each of the different design data associated with each title name,
In the second step, based on the title names included in the function data acquired in the first step, each title name includes a common title name, and the common titles 18. The program according to claim 17, wherein when the contents of the respective design data associated with the name are different, the program notifies the user of the difference. The function data includes each title name and each of the different design data associated with each title name,
In the second step, based on the respective design data included in the respective function data acquired in the first step, if each of the design data includes common design data, Each function data to which each design data belongs is collected, and based on each title name included in the collected each function data, a common title is included in each title name, and the common title name is 21. The program according to claim 20, wherein when the contents of the associated design data are different, the program notifies the user of the difference.

Images