JP2006330998A - Design information management system and design information management method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a design information management system and a design information management method for efficiently managing a design specification comprising design data such as an application program, and design information including a design reason for the design specification. <P>SOLUTION: An individual identification ID is attached to design data edited by a design data edition part 12 and the resultant is stored in a design data repository 15, and a design information retrieval part 14 is provided which stores design information including a design reason related to each piece of design data in a design information repository 16 correspondingly to the identification ID and which gets access to the design information repository 16 on the basis of the design information including the design reason, so that the design data can be reused according to the design reason. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a design information management system for managing design data such as design documents and design information related to the design data.

  For design information management devices such as design documents, program sources, and development management data, for example, to facilitate resource management in a distributed development system using a network, and to improve efficiency and reliability by sharing and reusing resources. Improvement has been attempted (see, for example, Patent Document 1).

  Conventionally, in the design of software such as application programs, in order to reuse a design document created in the past, the design document designed based on the customer's request and the customer's request are often linked and managed. It was. However, there are no one-to-one correspondences between customer requirements and the designer's design issues, design intentions, and comments. As a result, the design reason and the design document are not associated with each other and managed.

Also, if you try to express the design reason in the design document, it will be managed as part of the design content, so it will be double management of the design document for customer submission and the design document describing the design intent. There was a problem.
JP 9-34696 A

  The present invention has been made to solve the above-described problems, and provides a design information management system that can efficiently manage design data such as design data and design reasons in a design document. For the purpose.

  According to claim 1 of the present invention, a design data editing unit that edits design data, a design data repository that stores each design data edited by the design data editing unit with an individual identification ID, and A design information repository that stores design information including design reasons related to the individual design data in correspondence with the identification ID; and a design information search unit that accesses the design information repository and searches for design information. Provided is a design information management system in which the design information search unit and the design data editing unit can be operated simultaneously.

  According to claim 2 of the present invention, the design information provides a design information management system having a design identification ID corresponding to the identification ID.

  According to a third aspect of the present invention, there is provided a design information management system in which the design information includes a design identification ID corresponding to the identification ID, a configuration object group, and object related information.

  According to claim 4 of the present invention, the design information provides a design information management system having information on a design problem.

  According to claim 5 of the present invention, the design data editing step for editing the design data, the step of storing the edited individual design data with an individual identification ID in the design data repository, and the individual design Design information including a step of storing design information including a design reason related to data in a design information repository corresponding to the identification ID, and a step of searching the design information by accessing the design information repository. In addition, a design information management method is provided in which design data being edited is displayed in an overlapping manner and can be operated simultaneously.

  According to the present invention, it is possible to efficiently manage design data of a software development design document such as an application program, and design information such as a design reason related to the design data. Therefore, it is possible to provide a design data management system such as object design in which desired design data is selected based on at least design information indicating a design reason, and the design data can be reused.

  Hereinafter, a design information management system according to an embodiment of the present invention will be described with reference to the drawings. In addition, in each figure, the same code | symbol is attached | subjected about the same location.

  First, the configuration of the embodiment of the present invention will be described.

  FIG. 1 shows a configuration example of a design information management system such as software such as an application program. This system is composed of a plurality of terminal computers connected to the operation input keyboard, mouse and display directly used by the designer, and a host computer connected to these terminal computers as hardware. For the sake of convenience, it will be described below divided into functional parts.

  A design data editing unit 12 for the designer 11 to edit design data as an object design work, a design information editing unit 13 for editing design information including design reasons related to the design data of the designer, and design information Is provided with a design information search unit 14 for searching for a design data, a design data repository 15 for managing design data, and a design information repository 16 for managing design information.

  When the designer inputs an operation and there is a request for searching design information such as a design reason, the design information searching unit 14 accesses the design information repository 16 and searches for the managed design information. The design information search unit 14 can be used simultaneously with the design data editing unit 12.

  FIG. 2 shows detailed functional unit configurations of the design data editing unit 12 and the design information editing unit 13. The design data editing unit 12 includes a design information editing unit calling unit 21 for calling the design information editing unit 13, a design data operating unit 22 for operating the design data, and a design information searching unit calling unit for calling the design information searching unit 14. 23, and a save instruction unit 24 for saving the editing result in the design data repository 15 and the design information repository 16.

  On the other hand, the design information editing unit 13 includes a design data editing unit calling unit 25 for calling the design data editing unit 12 and a design information operation unit 26 for operating the design information.

  The design data editing unit 12 and the design information editing unit 13 are switched to each other by the design information editing unit calling unit 21 and the design data editing unit calling unit 25. When switching from the design data editing unit 12 to the design information editing unit 13, the design data and the design information are combined and displayed on the design information operation unit 26. Further, only the design data is displayed on the design data operation unit 22 when switching from the design information editing unit 13 to the design data editing unit 12.

  FIG. 4 shows data managed by the design data repository 15 and the design information repository 16 and their association.

  The design data repository 15 is a repository for managing and storing design data created and edited by the designer 11 using the design data editing unit 12. Each design data has a design data identification ID 411, a design data name 412, a configuration object group 413, and object related information 414.

  On the other hand, the design information repository 16 is a repository for storing and managing design information edited by the designer 11 with the design information editing unit 13. The design information includes a design information identification ID 421, a design data identification ID 422, a configuration object group 423, object related information 424, a design task 425, a design reason / comment 426, and a latest data flag 427. The latest data flag 427 is used to represent design information for the latest design data.

  Since the design data identification ID 411 of the design data repository 15 is associated with the design data identification ID 422 of the design information repository 16, the design data repository 15 and the design information repository 16 retrieve design information corresponding to the design data. Can do.

  Next, a design work flow according to an embodiment of the present invention will be described with reference to FIGS.

  Start object design work for software such as application programs.

  In step S51, the designer 11 creates and edits design data by performing object design using the design data operation unit 22 of the design data editing unit 12.

  When the design information is edited during creation / editing of design data, the designer 11 uses the design information editing unit 13 to edit the design information in the procedure from step 52 onward. The designer 11 performs a design information editing unit calling operation and calls the design information editing unit 13 by the design information editing unit calling unit 21. The design information editing unit calling unit 21 passes the design data identification ID 411 already assigned to the design information editing unit 13 when the current design data is existing design data. The called design information editing unit 13 starts the determination as to whether or not the design information can be edited according to the flow of FIG.

  In step 61, it is determined whether or not the current design data has been changed since the start of design. As for the presence / absence of change in design data, the design information editing unit calling unit 21 obtains information on the presence / absence of change in design data together with the design data identification ID 411.

  If there is a change in the design data, it is determined in step 62 whether or not the change has an influence on the design information.

  The determination is performed as follows. First, the design information repository 16 is searched based on the passed design data identification ID 411, and the design information in which the latest data flag 427 is set is extracted.

  If there is no corresponding design information, it is determined that there is no influence. If there is corresponding design information, the design data repository 15 is searched based on the design data identification ID 411, and the configuration object group 413 and the object related information 414 of the target design data are acquired and already extracted. The constituent object group 423 of the design information and the object related information 424 are compared, and if both are the same, it is determined that there is no influence, and if they are different, it is determined that there is an influence.

  If it is determined that there is an influence, there is a possibility that there is a difference between the design data and the design information. In step S63, a review of the design information is instructed.

  When an instruction is given to review the design information, the designer 11 performs an operation in accordance with the instruction and removes the difference.

  In this way, after it is determined that there is no difference between the design data and the design information, that is, the design information can be edited, the design information editing unit 13 superimposes the design information on the design data being edited, The information is displayed on the information operation unit 26.

  The designer 11 inputs design information to the design information operation unit 26 by an input operation. (1) When inputting new design information, the design information operation unit 26 performs input of design information by the input operation. Design information can be input by designating the object group to be, so design information including the design reason is input. (2) When editing the existing design information, the design information including the design reason is edited because the design information can be edited by designating the target design information in step S52. (3) When deleting the existing design information, it can be deleted from the display of the design information operation unit 26 by designating the target design information in step S52.

  When work such as creation / editing of design information is completed, the design data editing call unit 25 of the design information editing unit 13 returns to the design data editing unit 12 by performing an input operation indicating that the designer 11 has completed.

  Next, when the designer 11 wants to use past design information, the design information can be searched in step S53.

  In this case, when the designer 11 performs an operation input for searching for design information, the design information search unit 14 can be used by the design information search unit calling unit 23 of the design data editing unit 12.

  The design information search unit 14 prompts the designer 11 to input a search condition (simultaneous display using one or more of sound, sound, and image is performed), so the designer 11 performs an operation and the search condition input unit 31. Enter search criteria in natural language. Then, the design problem 425 and the design reason 426 that match the input conditions are taken out from the design information repository 16 and displayed on the search result display unit 32. The designer 11 selects and designates desired design information from among these displays, whereby the detailed information of the design information is taken out and displayed on the design information detail display unit 33. The displayed contents are a configuration object group 423, an object configuration diagram created from the configuration object related information 424, a design task 425, a design reason / comment 426, and the like. From these display contents, the designer 11 determines whether or not the design data currently being created / edited can be used, and if it can be used, the detailed information is used.

  The design data / design information is stored in step S54 when the design work is finished. The save instruction unit 24 of the design data editing unit 12 instructs to save the design data repository 15 and the design information repository 16. If the design data is new data, the user is prompted to input the name of the design data, and the design data identification ID 411 is added when the design data is stored. At the time of saving in the design information repository 16, the latest data flag 427 is updated together with the design information. The saving instruction unit 24 ends the operation in the design data editing unit 12 when the saving to the repository is completed.

  According to the embodiment of the present invention described above, the design information search unit 14 is provided, and the design information stored in the design information repository 16 can be searched by the design information search unit 14. Since the design information search unit 14 can be used simultaneously with the design data editing unit 12, design information registered in the existing design information repository 16 can be taken out and reused for object design while designing software. Therefore, design efficiency can be improved. In addition, when developing software, the design data entered by each designer for an existing design document can be correctly grasped by considering the design reason for the design data, so the information of true meaning is shared. be able to.

  Furthermore, it is not necessary to manage the design document twice for each use such as design and submission.

  Note that the present invention is not limited to the above-described embodiment as it is, and can be embodied by modifying the constituent elements without departing from the scope of the invention in the implementation stage. For example, in the above-described embodiment, for convenience of explanation, each part having each function is described with an individual name. However, the part having each function is also used, or further divided into parts. Various design changes can be made, and implementation as software is also possible.

1 shows an overall configuration of a design information management system according to an embodiment of the present invention. A design data editing unit 12 and a design information editing unit 13 in the overall configuration of FIG. The design information search part 14 in the whole structure of FIG. 1 is shown. The structure of the design data repository 15 and the design information repository 16 in the whole structure of FIG. 1 is shown. The flowchart of a design information management system is shown. The flowchart of determination of whether design information can be edited is shown in the flowchart of the design information management system.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 11 ... Designer, 12 ... Design data edit part, 13 ... Design information edit part, 14 ... Design information search part, 15 ... Design data repository, 16 ... Design information repository, 21... Design information editing section calling section, 22... Design data operation section, 23... Design information searching section calling section, 24. ... Design information operation part, 31 ... Search condition input part, 32 ... Search result display part, 33 ... Design information detail display part.

Claims (5)

A design data editing section for editing design data;
A design data repository for storing each design data edited by the design data editing unit with an individual identification ID;
A design information repository for storing design information including design reasons related to the individual design data in correspondence with the identification ID;
A design information search unit for accessing the design information repository and searching for the design information;
A design information management system characterized in that the design information search unit and the design data editing unit can be operated simultaneously.   The design information management system according to claim 1, wherein the design information includes a design identification ID corresponding to the identification ID.   The design information management system according to claim 1, wherein the design information includes a design identification ID corresponding to the identification ID, a configuration object group, and object related information. The design information management system according to claim 1, wherein the design information includes information on a design problem. A design data editing step for editing the design data;
Storing the edited individual design data with an individual identification ID in the design data repository;
Storing design information including a design reason related to the individual design data in a design information repository corresponding to the identification ID;
Accessing the design information repository and searching for design information,
A design information management method characterized in that the searched design information and design data being edited are displayed in a superimposed manner and can be operated simultaneously.

Images