WO2017141785A1 - 設計書の入出力装置、設計書の入出力システム及び設計書の入出力方法 - Google Patents

設計書の入出力装置、設計書の入出力システム及び設計書の入出力方法 Download PDF

Info

Publication number
WO2017141785A1
WO2017141785A1 PCT/JP2017/004537 JP2017004537W WO2017141785A1 WO 2017141785 A1 WO2017141785 A1 WO 2017141785A1 JP 2017004537 W JP2017004537 W JP 2017004537W WO 2017141785 A1 WO2017141785 A1 WO 2017141785A1
Authority
WO
WIPO (PCT)
Prior art keywords
design
design information
input
design document
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2017/004537
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
秀行 鹿糠
佑樹 近藤
知倫 中村
岳 斎藤
立川　茂
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hitachi Ltd
Original Assignee
Hitachi Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hitachi Ltd filed Critical Hitachi Ltd
Priority to MYPI2018702621A priority Critical patent/MY194133A/en
Publication of WO2017141785A1 publication Critical patent/WO2017141785A1/ja
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management

Definitions

  • the present invention relates to a technology for creating and inputting / outputting design documents having various layouts created and maintained by, for example, system development, etc., using spreadsheet software for the purpose of centralized management by the storage device.
  • design documents are created to describe design information related to the screens and databases that make up the computer system.
  • the design document is created by word processing software, spreadsheet (spreadsheet) software, or the like.
  • spreadsheet readsheet
  • a design document in the form of a spreadsheet is targeted.
  • Design documents are media for sharing design information among system developers.
  • the design document is structurally analyzed, and then the design information is converted into a database format for centralized management.
  • Patent Document 1 is known as an apparatus for mechanizing input / output between data written in such a spreadsheet and data in a database.
  • Design documents handled in system development differ in type, description items, and layout for each development project, and layout and items may be changed during development and maintenance.
  • the prior art requires a database schema change and data migration accompanying the schema change.
  • screens and processes for searching and editing design information stored in the database in accordance with a schema may be created. In this case, there has been a problem that the screens and processes need to be modified along with the schema change.
  • the present invention has been made in view of the above problems, and an object of the present invention is to make it unnecessary to modify a database schema when items or layouts described in a design document are changed.
  • the present invention is a design document input / output device that includes a processor and a memory and processes a spreadsheet format design document.
  • the design information definition is generated in advance and defines the structure of the design document.
  • a storage unit for storing a design information template having a definition for converting the design document in a spreadsheet format into a semi-structured data format; and receiving the design document in the spreadsheet format;
  • a conversion unit that sets the design information template based on the design information definition and outputs the design information in the semi-structure data format.
  • Design information in XML format can be stored as an XML file, stored in one column of the database, or stored in a storage device in a format such as an XML database, so even if the layout of the design document is changed There is no need to change the database schema.
  • XML format a semi-structured data format
  • FIG. 1 is a block diagram illustrating an example of a hardware configuration of a computer system according to a first embodiment of this invention.
  • 1 is a block diagram illustrating an example of functional elements of a computer system according to a first embodiment of this invention. It is a figure which shows Example 1 of this invention and shows an example of design document meta information. It is a figure which shows Example 1 of this invention and shows an example of design document meta information. It is a figure which shows Example 1 of this invention and shows an example of a design information definition body. It is a figure which shows Example 1 of this invention and shows an example of a design information model. It is a figure which shows Example 1 of this invention and shows an example of design information. It is a figure which shows Example 1 of this invention and shows an example of a design document model.
  • Example 1 of this invention shows an example of a design document. It is a figure which shows Example 1 of this invention and shows an example of a design document. It is a screen image which shows Example 1 of this invention and shows an example of a design document registration screen. It is a screen image which shows Example 1 of this invention and shows an example of a search condition input screen. It is a figure which shows Example 1 of this invention and shows an example of a search condition input screen. It is a screen image which shows Example 1 of this invention and shows an example of a design information search result display screen. It is a screen image which shows Example 1 of this invention and shows an example of a design information search result display screen.
  • Example 1 of this invention It is a screen image which shows Example 1 of this invention and shows an example of a design information search result display screen. It is a screen image which shows Example 1 of this invention and shows an example of a design information reference and edit screen. It is Example 1 of this invention, and is a flowchart which shows an example of a process of a design document meta information conversion part. It is a flowchart which shows Example 1 of this invention and shows an example of a process of a design information reading and conversion part. It is Example 1 of this invention, and is a flowchart which shows an example of a process of the design information search condition input screen output part. It is a flowchart which shows Example 1 of this invention and shows an example of a process of a design information search and a result display screen output part.
  • Example 1 of this invention is a flowchart which shows an example of a process of a design information reference and edit screen output part. It is Example 1 of this invention, and is a flowchart which shows an example of a process of the design information edit process part.
  • 1 is a block diagram illustrating an example of a configuration of a computer according to a first embodiment of this invention. It is Example 2 of this invention and is a block diagram which shows an example of the functional element of a computer.
  • the computer system according to the first embodiment of the present invention is a spreadsheet design document input / output system 100 including a design document meta information conversion device 101, a design information input / output device 102, and a client device 103.
  • FIG. 1 is a block diagram showing an example of a hardware configuration of a computer system.
  • the design document meta information conversion apparatus 101, the design information input / output apparatus 102, and the client apparatus 103 include a control and calculation unit 101 a, 102 a, and 103 a, an input unit 101 b, 102 b, and 103 b, and a storage unit.
  • the computer system includes 101c, 102c, and 103c, output units 101d, 102d, and 103d, and communication interface units 104a, 104b, and 104c. Note that the communication interface units 104a, 104b, and 104c are connected via a network.
  • the design document meta information conversion apparatus 101 and the design information input / output apparatus 102 realize data communication cooperation between the apparatuses via the communication interface units 104a and 104b.
  • the design information input / output device 102 and the client device 103 realize data communication between the devices via the communication interface units 104b and 104c.
  • These design document meta information conversion apparatus 101, design information input / output apparatus 102, and client apparatus 103 may be integrated.
  • the storage units 101c, 102c, and 103c are configured by a storage device including a nonvolatile storage medium such as a hard disk drive.
  • a computer software program that functions as the design document meta information conversion unit 201 and the table calculation unit 210 is stored in the storage unit 101 c of the design document meta information conversion apparatus 101.
  • the storage unit 102c of the design information input / output device 102 includes a design document reading / conversion unit 202, a design information search condition input screen output unit 203, a design information search / result display screen output unit 204, a design information reference / edit screen output unit 205. And a computer software program that functions as the design information editing processing unit 206 is stored.
  • the storage unit 103c of the client apparatus 103 stores a computer program that functions as a spreadsheet unit 211 that edits a design document, a computer program that functions as a browser 212, a spreadsheet design document, and a design document model. .
  • the storage unit 103c also stores a computer software program that functions as a browser that displays the screen transmitted from the design information input / output device 102 on the output unit 103d.
  • the control and calculation units 101a, 102a, and 103a include a processor and a memory as will be described later, and a program is loaded into the memory from the storage units 101c, 102c, and 103c and executed by the processor.
  • the design document meta information conversion unit 201 and the table calculation unit 210 realize each function by being read from the storage unit 101c and executed by the control and calculation unit 101a.
  • the design document reading / conversion unit 202, the design information search condition input screen output unit 203, the design information search / result display screen output unit 204, and the design information reference / edit screen output unit 205 are read from the storage unit 102c by the control / calculation unit 102a.
  • Each function is realized by being issued and executed.
  • the spreadsheet unit 211 and the browser 212 realize each function by being read from the storage unit 103c and executed by the control and calculation unit 103a.
  • the input units 101b, 102b, and 103b are input devices such as a mouse.
  • the output units 101d, 102d, and 103d are display devices such as various displays, and other output devices such as various printers can be connected thereto.
  • FIG. 20 is a block diagram showing an example of a computer constituting the spreadsheet-format design input / output system 100.
  • the illustrated example shows an example of the computer 10 operating as the design document meta information conversion apparatus 101, but the design information input / output apparatus 102 and the client apparatus 103 have the same configuration.
  • the computer 10 is connected to a processor 60 that performs control and arithmetic processing, a memory 70 that stores programs and data, a communication interface unit 104a that is connected to the network 40 and communicates with other computers, and a storage unit 101c.
  • the control and calculation units 101 a, 102 a, and 103 a illustrated in FIG. 1 correspond to the processor 60 and the memory 70.
  • the processor 60 is composed of a heterogeneous multi-core processor, and includes a plurality of CPU cores 61 and a plurality of GPU cores 62.
  • the processor 60 also includes a memory controller 63 connected to the memory 70, a display controller 65 connected to the output unit 101d, an I / O processor 83, a communication interface unit 104a, and an I / O connected to the storage interface 86.
  • the input unit 101b includes a keyboard, a mouse, and a touch panel.
  • the output unit 101d includes a display.
  • the memory 70 is loaded with the OS 71 and executed by the processor 60.
  • the OS 71 executes one or more software 72 such as a design document meta information conversion unit and a spreadsheet unit.
  • Each functional unit such as the design document meta information conversion unit 201 is loaded into the memory 70 as a program.
  • the processor 60 operates as a functional unit that provides a predetermined function by processing according to a program of each functional unit.
  • the processor 60 functions as the design document meta information conversion unit 201 by performing processing according to the design document meta information conversion program. The same applies to other programs.
  • the processor 60 also operates as a functional unit that provides each function of a plurality of processes executed by each program.
  • a computer and a computer system are an apparatus and a system including these functional units.
  • Information such as programs and tables for realizing each function of the design document meta information conversion apparatus 101 is stored in a storage device 101c, a nonvolatile semiconductor memory, a hard disk drive, a storage device such as an SSD (Solid State Drive), or an IC card, SD. It can be stored in a computer-readable non-transitory data storage medium such as a card or DVD.
  • FIG. 2 shows an example of a functional block diagram of the computer system.
  • the design information input / output device 102 is a computer that processes a design document used in a user's business.
  • the design document meta information conversion apparatus 101 generates, in a spreadsheet format, design document meta information 301 (FIG. 3) that defines the structure (items and layout) of the design document 304 b (FIG. 7B) according to a developer's operation. .
  • the design document meta information conversion unit 201 reads the design document meta information 301 and defines a design information definition body 302 (FIG. 4) that defines the structure of the design document 304 b and the design document 304 b.
  • the data is converted into a design information template 303 (FIG. 5) used for conversion.
  • the design document meta information conversion device 101 stores the converted design information definition body 302 and the design information template 303 in the storage unit 102c of the design information input / output device 102 used by the user.
  • a developer who uses the design document meta information conversion apparatus 101 generates a design document template 304a (FIG. 7A) corresponding to the design document meta information 301, and a storage unit of the design information input / output apparatus 102 used by the user. It is stored in 102c.
  • the user of the client apparatus 103 reads the design document template 304a by the spreadsheet unit 210, generates a spreadsheet-format design document 304b, and stores it in the storage unit 102c.
  • the client device 103 requests registration of the design document 304b in accordance with a user operation.
  • the design document meta information conversion unit 201 outputs a design document registration screen 305 to the client device 103.
  • the client apparatus 103 executes registration of the design document 304b from the design document registration screen 305.
  • the design information input / output device 102 accepts the spreadsheet format design document 304b
  • the design document reading and conversion unit 202 reads the design information definition body 302 and the design information template 303, and as described later, the design format input / output device 102
  • the design document 304b is converted into design information 310 in XML format and stored in the storage unit 102c.
  • the design information search condition input screen output unit 203 reads the design information definition body 302, generates a search condition input screen 306, and outputs it to the client device 103.
  • the search condition input screen 306 is a generic term for the search condition input screens 306a and 306b in FIGS.
  • the design information search and result display screen output unit 204 executes the search, refers to the design information definition body 302, and searches for the design information search result screen 307. Is transmitted to the client apparatus 103 as a search result.
  • the design information search result screen 307 is a generic name for the design information search result screens 307a, 307b, and 307c shown in FIGS. 11A to 12.
  • the design information reference / edit screen output unit 205 reads the design information 310 and the design information definition body 302 and references the design information. Then, an edit screen 308 is generated and output to the client device 103.
  • the client device 103 can edit the design information 310 from the design information reference and edit screen 308.
  • the design information editing processing unit 206 reads the design information 310 in the XML format and responds to the design information definition body 302 and the design information template 303. Then, a spreadsheet format design document 304 c is generated and transmitted to the client apparatus 103.
  • the design document meta information 301 is an example of a file stored in the storage unit 101 c of the design document meta information conversion apparatus 101 and is used by the design document meta information conversion unit 201.
  • one file is created by the spreadsheet unit 210 for each type of design document defined in the spreadsheet.
  • the design document meta information 301 includes the structure of the design document 304b that defines the items used in the spreadsheet format design document 304b (design document template 304a) used by the client apparatus 103 and the layout of the cell position of each item. It is a defined file.
  • One file of the design document meta information 301 includes “file type” (3011), “relation between item groups” (3012), “sheet type” (3013), and “single item group” (3014). And an element of “multiple item group” (3015).
  • Element “file type” (3011) defines the type of design document for each spreadsheet format file, and includes element “local name” and element “alphabet name”.
  • the element “sheet type” (3013) is defined for each sheet defined in the spreadsheet. Therefore, when a design document 304b composed of a plurality of sheets in a spreadsheet is targeted, the element “sheet type” (3013), the following “single item group” (3014), and “multiple item group” ( 3015) are defined.
  • the element “sheet type” (3013) includes an element “local name” and an element “alphabet name”.
  • the element “single item group” (3014) a group that defines the content of the item (single item) in which one value is defined for one item defined in the design document and additional information is defined.
  • the element “single item group” (3014) includes an element “local name” and an element “alphabet name”.
  • element “item number”, element “required flag”, element “single item local name”, element “single item alphabetic name”, and singular items on the spreadsheet Element “start row” and element “start column” are defined as information indicating the position, and element “type” and element “size” are defined as information necessary for displaying a single item on the screen. .
  • Type defines a format for display on the browser of the client apparatus 103
  • input indicates an input field
  • text indicates that a character string is displayed.
  • Size defines the number of input characters.
  • the element “multiple item group” (3015) a group that defines the content of the item (multiple items) in which a plurality of values are defined for one item defined in the design document and additional information is defined.
  • the element “multiple item group” (3015) includes an element “local name” and an element “alphabet name”. Also, as many as the number of items, element “item number”, element “required flag”, element “multi-item local name”, element “multi-item alphabetic name”, and multiple items from which position on the spreadsheet An element “start row” and an element “start column” are defined as information indicating whether to start, and an element “type” and an element “size” are defined as information required when displaying a plurality of items on the screen.
  • single item group (3014) and the element “multiple item group” (3015) may be omitted or plural according to the target design document.
  • the element “relation between item groups” (3012) includes an element “item number”, an element “parent item group name”, an element “child item group name”, and an element “description”. In the element “parent item group name” and the element “child item group name”, “English name” of “single item group” (3014) or “multiple item group” (3015) is entered.
  • the design document meta information 301 is stored in the storage unit 101c with the above contents.
  • the design document meta information 301 is created in advance by a developer who uses the design document meta information conversion apparatus 101 in correspondence with the design document 304 b used by the client apparatus 103, and is transmitted to the client apparatus 103.
  • the design document meta information 301 may be created by the design document meta information conversion apparatus 101 or may be generated by another computer.
  • the design document meta-information 301 is information in which configuration information including the structure and layout of the design document 304b in the spreadsheet format and the design document template 304a is defined in advance.
  • FIG. 4 shows an example of the design information definition body 302.
  • the design information definition body 302 is a file generated from one design document meta information 301 by the process of the design document meta information conversion unit 201 and stored in the storage unit 101c and the storage unit 102c.
  • the data configuration will be described with reference to the design information definition body 302 of FIG.
  • the design information definition body 302 is an XML format file and has “genericRule” (3021) as a root element.
  • the element “genericRule” (3021) has “localName” and “name” as attributes.
  • the value of “localName” is “local name” of “file type” (3011) of the design document meta information 301, and the value of “name” is “alphabetic name” of “file type” (3011) of the design document meta information 301.
  • the element “genericRule” (3021) includes a plurality of elements “relationship” (3022) and element “designSpecification” (3023).
  • the element “relationship” (3022) is generated by the process of the design document meta information conversion unit 201 as many as the “relationship between item groups” defined in the design document meta information 301.
  • the element “relationship” (3022) has “parentItem” and “childItem” as attributes.
  • the value of “parentItem” is derived from the “parent item group name” of the design document meta information 301, and the value of “childItem” is derived from the “child item group name” of the design document meta information 301. Each is set.
  • the element “designSpecification” (3023) is generated by the process of the design document meta information conversion unit 201 as many as the “sheet types” defined in the design document meta information 301.
  • the element “designSpecification” (3023) has “localName” and “sheetCls” as attributes.
  • the value of “localName” is “local name” of “sheet type” (3013) of the design document meta information 301
  • the value of “sheetCls” is “alphabetic name” of “sheet type” (3013) of the design document meta information 301.
  • the element “designSpecification” (3023) includes a plurality of elements “key”.
  • the element “key” is generated by the process of the design document meta information conversion unit 201 by the number of “single item groups” (3014) or “multiple item groups” (3015) of the design document meta information 301.
  • the element “key” has “localName”, “name”, and “type” as attributes.
  • the value of “localName” is determined by the process of the design document meta information conversion unit 201 from “local name” of “single item group” (3014) of design document meta information 301 or “local name” of “multiple item group” (3015). Is set.
  • the value of “name” is determined by the process of the design document meta information conversion unit 201 from “alphabetic name” of “single item group” (3014) of design document meta information 301 or “alphabetic name” of “multiple item group” (3015). Is set.
  • the value of “type” is set by the process of the design document meta information conversion unit 201 from “single” in the case of “single item group” (3014) or “list” in the case of “multiple item group” (3015).
  • the element “key” includes a plurality of elements “singleItemKey” when the value set to “type” is “single”, or the element “listItemKey” when the value set to “type” is “list” Including multiple.
  • the element “singleItemKey” (3024) is generated by the process of the design document meta information conversion unit 201 by the number of items defined in the “single item group” (3014) of the design document meta information 301.
  • the element “singleItemKey” (3024) has “localName”, “name”, and “mandatory” as attributes.
  • the value of “localName” is from “single item local name” of “single item group” (3014) of design document meta information 301, and the value of “name” is of “single item group” (3014) of design document meta information 301. From “single item alphabetic name”, the value of “mandatory” is “true” when “mandatory flag” in the design document meta information 301 is entered as “true”, and nothing is entered in “mandatory flag”. If not, “false” is set in the process of the design document meta information conversion unit 201.
  • the element “singleItemKey” (3024) includes an element “spreadsheet” and an element “webScreen”.
  • the element “listItemKey” (3025) is generated by the process of the design document meta information conversion unit 201 by the number of items defined in the “multiple item group” (3015) of the design document meta information 301.
  • the element “listItemKey” (3025) has “localName”, “name”, and “mandatory” as attributes.
  • the value of “localName” is from “multiple item local name” of “multiple item group” (3015) of design document meta information 301, and the value of “name” is “multiple item group” (3015) of design document meta information 301.
  • the value of “mandatory” is “true” when “mandatory flag” in the design document meta information 301 is entered, and “true” is nothing in “mandatory flag”. In this case, “false” is set in the process of the design document meta information conversion unit 201.
  • the element “listItemKey” (3025) includes one element “spreadsheet” and one element “webScreen”.
  • the essential flag is a flag for identifying an item that must be used in the design document 304b. If “ ⁇ ”, the flag is an essential item in the design document 304b. An item for which the mandatory flag is set to “ ⁇ ” serves as a search key in the search process.
  • the element “sheet” (3026) includes one element “cellLine” and one element “cellColumn”.
  • the value of the element “cellLine” (3026) is processed from the “start line” of the design document meta information 301, and the value of the element “cellColumn” is processed from the “start column” of the design document meta information 301. To set each.
  • the element “webScreen” (3027) includes one element “itemType” and one element “itemLength”.
  • the value of the element “itemType” is set from the “type” of the design document meta information 301, and the value of the element “itemLength” is set from the “size” of the design document meta information 301 by the process of the design document meta information conversion unit 201. .
  • the design information definition body 302 defines cell information determined by the row number (cellLine) and column number (cellColumn) of the spreadsheet-type design document 304b.
  • the design document read conversion unit 202 can acquire the structure of the spreadsheet-type design document 304b by referring to the design information definition body 302 corresponding to the design document 304b.
  • FIG. 5 shows a design information template used for converting the spreadsheet format design document 304b into the XML format, or a design information template used for reconverting the design information 310 stored in the storage unit 102c into the XML format.
  • An example of 303 is shown.
  • the design information template 303 is a file generated based on the design document meta information 301 by the process of the design document meta information conversion unit 201 and stored in the storage units 101c and 102c.
  • the data configuration will be described using the design information template 303 shown in FIG.
  • the design information template 303 is an XML format file having “documentCls” (3031) as a root element.
  • the element “documentCls” (3031) has “name”, “fileName”, and “date” as attributes.
  • the value of the attribute “name” is set by the process of the design document meta information conversion unit 201 from the “alphabetic name” of the “file type” (3011) of the design document meta information 301.
  • the value of the attribute “fileName” is set by the design document reading and conversion unit 202 from the “design document file name” input by the user on the design document registration screen 305.
  • the value of the attribute “date” is the date when the design document 304b is registered in the storage unit 102c by the design document reading and conversion unit 202, or when the design document edit processing unit 206 generates the design document 304c. Minutes and seconds are generated in the format of “YYYY / MM / DD / HH: MM: SS”, for example.
  • the element “documentCls” (3031) includes a plurality of elements “sheetCls” (3032).
  • sheetCls As “sheet types” (3013) defined in the design document meta information 301 are generated by the process of the design document meta information conversion unit 201.
  • “SheetCls” (3032) has “name” as an attribute. The value of the attribute “name” is set by the process of the design document meta information conversion unit 201 from “alphabetic name” of “sheet type” (3013) of the design document meta information 301.
  • the element “sheetCls” (3032) includes an element “singleItems” (3033) or an element “listItems” (3037).
  • Element “singleItems” (3033) is generated by the process of the design document meta information conversion unit 201 by the number of “single item groups” (3014) of the design document meta information 301.
  • the element “singleItems” (3033) has “name” as an attribute.
  • the value of the attribute “name” is set by the process of the design document meta information conversion unit 201 from “English name” of “single item group” (3014) of the design document meta information 301.
  • a plurality of elements whose element names are “single item alphabetic names” defined in the “single item group” (3014) of the design document meta information 301 are converted into the design document meta information conversion. It is generated and included by the processing of the unit 201.
  • the element value having the element name “single item alphabetic name” defined in “single item group” (3014) ⁇ of the design document meta information 301 a variable surrounded by “$ ⁇ ” is a design document meta information. Generated by the conversion unit 201.
  • variable name is a format in which “alphabetic name” of “sheet type” (3013) of design document meta information 301 and “alphabetic name” of “single item group” (3014) of design document meta information 301 are connected by “.”. Thus, it is generated by the design document meta information conversion unit 201.
  • the element “listItems” (3037) is generated by the process of the design document meta information conversion unit 201 by the number of “multiple item groups” (3015) of the design document meta information 301.
  • the element “listItems” (3037) has “name” as an attribute.
  • the value of the attribute “name” is set by the process of the design document meta information conversion unit 201 from “English name” of “multiple item group” (3015) of the design document meta information 301.
  • the element “listItems” (3037) includes one element “member” (3035). Note that “#foreach ($ member in $ XXXX)” is between the element “listItems” (3037) and “member” (3035), and “#end” is immediately after the element “member” (3035).
  • the design document meta-information conversion unit 201 generates a variable having a name in a format linked in the above.
  • a plurality of elements whose element names are “multiple item alphabetic names” defined in “multiple item groups” (3015) of the design document meta information 301 include a design document meta information conversion unit. It is generated and included in the process 201.
  • a variable enclosed by “$ ⁇ ” is a design document meta information.
  • the variable name is a format in which “alphabetic name” of “sheet type” (3013) of design document meta information 301 and “alphabetic name” of “multiple item group” (3015) of design document meta information 301 are connected by “.”. Thus, it is generated by the design document meta information conversion unit 201.
  • the design information template 303 defines a form for setting the value of the design document 304b in the XML format file when the design information 310 is generated. Therefore, the design document read conversion unit 202 can convert the value read from the spreadsheet format design document 304b in accordance with the design information definition body 302 into the design information template 303, thereby converting the value into the XML format design information 310. .
  • FIG. 6 is a diagram illustrating an example of the design information 310.
  • the design information 310 indicates a result obtained by converting the spreadsheet format design document 304 b generated by the client device 103 into the XML format by the design document reading and conversion unit 202 of the design information input / output device 102.
  • the design information 310 is generated by the design document reading and conversion unit 202 as information in which the contents of the design document 304b are set in the variable $ of the design information template 303 shown in FIG.
  • FIG. 7A shows Example 1 of the present invention and is a diagram showing an example of a design document template 304a.
  • the design document template 304 a is spreadsheet format information stored in advance in the storage unit 103 c of the client device 103.
  • the design template 304a in FIG. 7A shows a state of no input.
  • the design document template 304a includes a document classification 3031 indicating the type of the design document template 304a, a title 3032 for storing the title of the design document 304b, a component ID 3033, a component name 3034, a creator 3035, an updater 3036, Approver 3037, creation date 3038, update date 3039, approval date 3040, item number 3041 indicating data number, package name space 3042, class Japanese name 3043, class alphabetic name 3044, method It includes a Japanese name 3045, a method alphabetic name 3046, other component publication 3047, and a remark 3048 cell.
  • FIG. 7B shows the first embodiment of the present invention and is a diagram showing an example of the design document 304b.
  • the design document 304b in FIG. 7B shows the result of the user of the client apparatus 103 inputting a predetermined value in the spreadsheet unit 211 to the design document template 304a in FIG. 7A.
  • the code of each cell of the design document 304b is the same as that of the design document template 304a.
  • FIG. 7C shows the first embodiment of the present invention and is an example of the design document 304c.
  • the design document 304c in FIG. 7C is information indicating the design information edited on the design information reference and editing screen 308 shown in FIG.
  • step 1401 the design document meta information conversion unit 201 starts processing in response to an instruction from the input unit 101b.
  • step 1402 the design document meta information conversion unit 201 reads a file of the design document meta information 301 registered in advance in the storage unit 101c.
  • step 1403 the design document meta information conversion unit 201 generates the elements and values of the design information definition body 302 by the above-described method from the file information of the design document meta information 301 read in step 1402, and the design information definition body 302 Are generated and stored in the storage unit 101c.
  • step 1404 the design document meta information conversion unit 201 generates the elements and values of the design information template 303 by the above-described method from the file information of the design document meta information 301 read in step 1402. A file is generated and stored in the storage unit 101c.
  • step 1405 the design document meta information conversion unit 201 reads the file of the design information definition body 302 generated in step 1403 and the file of the design information template 303 generated in step 1404 from the storage unit 101c and reads the communication interface. Data transfer processing is performed via the unit 104 a and stored in the storage unit 102 c of the design information input / output device 102.
  • step 1406 the design document meta information conversion unit 201 outputs a message indicating the completion of processing to the output unit 101d.
  • the design document meta information conversion apparatus 101 generates the design information definition body 302 and the design information template 303 from the design document meta information 301 and stores them in the storage unit 102c of the design information input / output apparatus 102.
  • the design document read conversion unit 202 displays the design document registration screen 305 with the design information definition body 302 as an input, and accepts a spreadsheet format design document 304b created based on the design document template 304a. Then, the design document read conversion unit 2 receives the design document 304b, the design information definition body 302 and the design document template 304a generated by the design document meta information conversion apparatus 101, and generates design information 310.
  • FIG. 8 is a screen image showing an example of the design document registration screen 305 output from the design document reading conversion unit 202.
  • the design document registration screen 305 includes a registration target 3051 for selecting an element “file type” of all the design document meta information 301 registered in the storage unit 102c from a pull-down list, and a “design document file name” for inputting a file name. (3052) and a “registration button” are arranged.
  • the design document registration screen 305 is displayed on the output unit 103 d of the client device 103 that uses the design information input / output device 102.
  • a user or an administrator who uses the client apparatus 103 selects the registration target 3051 by operating the input unit 103b and inputs the design document file name 3052 and then operates the “register button”, the design document reading and converting unit 202 is operated. As a result, design information 310 is generated.
  • the design document reading and converting unit 202 that outputs the design information 310 by inputting the design document 304b in the spreadsheet format, the design information definition body 302, and the design information template 303 created based on the design document template 304a.
  • An example of the process will be described with reference to the flowchart shown in FIG.
  • step 1501 the design document reading and conversion unit 202 starts processing in response to an instruction from the input unit 103b of the client device 103.
  • step 1502 the design request reading and conversion unit 202 of the design information input / output device 102 receives the processing request transmitted from the input unit 103b via the communication interface unit 104c, and generates the design document registration screen 305.
  • the design document reading and conversion unit 202 sends a processing response to the client device 103 via the communication interface unit 104b, and displays the design document registration screen 305 on the output unit 103d of the client device 103.
  • “local name” of the element “file type” of all the design document meta information 301 registered in the storage unit 102c is listed in the list of options for “registration target” (3051) on the design document registration screen 305. .
  • step 1503 the client device 103 inputs “registration target” (3051) and “design document file name” (3052) on the design document registration screen 305 by operating the input unit 103b. "The button is accepted.
  • the client device 103 reads a file of the design document 304b corresponding to the “design document file name” (3052) input on the design document registration screen 305 from the storage unit 103c.
  • the client device 103 notifies the design information input / output device 102 of the data of the design document 304b, the “registration target” (3051) input on the design document registration screen 305, and the processing request via the communication interface unit 104c. Subsequent steps are executed by the design information input / output device 102.
  • step 1504 the character string selected in the “Registration Target” (3051) of the design document registration screen 305 from the design information definition body 302 file registered in the storage unit 102c by the design document reading and conversion unit 202.
  • a file of the design information definition body 302 having the same value as the attribute “localName” of the element “genericRule” (3021) of the design information definition body 302 is retrieved from the storage unit 102c and read.
  • step 1505 the design document reading and converting unit 202 stores the “file type” (3011) of the design document meta information 301 read in step 1504 from the files of the design document meta information 301 registered in the storage unit 102c.
  • the design information template 303 file having the same value as the “alphabetic name” as the value of the attribute “name” of the element “documentCls” (3031) of the design information template 303 is retrieved from the storage unit 102c and read.
  • step 1506 the design document reading and conversion unit 202 reads the spreadsheet-type design document 304b file read in step 1503 from the design document 304b file using the design information definition body 302 read in step 1504.
  • the item name (local name) and value of the item 3014 or the plurality of items 3015 are acquired.
  • the value of the attribute “mandatory” of the element “singleItemKey” (3024) or the element “listItemKey” (3025) of the design information definition body 302 read in step 1504 corresponding to a single item or a plurality of items from the file of the design document 304b. If the value of the single item 3014 or the plurality of items 3015 has not been input on the file of the design document 304b despite being “true”, the design document reading and conversion unit 202 outputs an error.
  • the design document reading and conversion unit 202 is an element of the design information definition body 302.
  • the item name is acquired from “singleItemKey” 3014 and this attribute “name”
  • the line position of the value for the item name is acquired from the element “cellLine” in the element “singleItemKey” (3024)
  • the column position of the value for the item name is obtained.
  • the value of the row position and the column position acquired from the element “cellColumn” in the element “singleItemKey” (3024) and acquired from the file of the design document 304b in the spreadsheet format is acquired.
  • the design document reading and conversion unit 202 repeats the above processing as many times as the number of elements “singleItemKey” (3024) included in the element “key” of the design information definition body 302.
  • the design document reading and conversion unit 202 reads the element “listItemKey” of the design information definition body 302. ”(3025) and the attribute name“ name ”, the line position of the value for the item name is obtained from the element“ cellLine ”in the element“ listItemKey ”(3025), and the column position of the value for the item name is the element“ From the element “cellColumn” in “listItemKey” (3025), the row position and the column position value acquired from the spreadsheet format design document 304b, and the row where the value exists by incrementing the row position one by one Get multiple values.
  • the design document reading and conversion unit 202 repeats the above processing as many times as the number of elements “listItemKey” (3025) included in the element “key” of the design information definition body 302. However, the design document reading and conversion unit 202 obtains the number of values acquired from the element “listItemKey” (3025) included in the element “key” of one design information definition body 302 by the attribute “listItemKey” (3025). “mandatory” is equal to the number of values specified by “true”.
  • the values up to the third line are filled, so the design document reading and conversion unit 202 has values up to the line where “item number” (3051) is “3”. To be acquired.
  • step 1507 the design document reading and conversion unit 202 first sets a variable to be embedded in the design information template 303 as follows in the value acquired in step 1506.
  • the design document reading and conversion unit 202 sets the value of the attribute “sheetCls” of the element “designSpecification” and the value of the attribute “name” of the element “key” of the design information definition body 302 read in step 1504 for the single item.
  • a variable is set in a format in which the value of the attribute “name” of the element “singleItemKey” (3023) is concatenated with “.”, And the value of the item acquired in step 1506 is substituted for this variable.
  • the design document reading and conversion unit 202 reads the value of the attribute “sheetCls” of the element “designSpecification” (3023) and the attribute “name” of the element “key” of the design information definition body 302 read in step 1504.
  • This variable is a list object, and the design document reading and conversion unit 202 sets a variable whose name is the value of the attribute “name” of the element “listItemKey” (3025) of the design information definition body 302 read in step 1504. .
  • the design document reading and conversion unit 202 obtains the values obtained from the list of class information (3053, 3054) and method information (3055, 3056) in the spreadsheet format design document 304b in step 1506 for each line of the list. And register this object with the list object.
  • the design document reading and conversion unit 202 generates the design information 310 by replacing the variable “$” in the design information template 303 with the value of the variable set as described above. Note that the portion enclosed by “#foreach ($ member in $ XXXX)” and “#end” in the design information 310 is processed as follows.
  • the design document reading and conversion unit 202 extracts “classlocalName” from “member” (3035) and sets it as the value. replace.
  • the design document reading and conversion unit 202 copies the element “member” (3035) and the elements included in this element as many as the number of objects registered in the list object, and sets the variable in the element as a value. Repeat the replacement process. The design document reading and conversion unit 202 finally deletes “#foreach ($ member in $ XXXX)” and “#end”.
  • step 1508 the design document reading and conversion unit 202 sets the attribute “date” of the element “documentCls” of the XML-format design information 310 generated in step 1507 to the date, date, time, and date when the above processing is executed.
  • the second is set in the format of “YYYY / MM / DD / HH: MM: SS”.
  • the design document reading and conversion unit 202 sets the name of the “design document file name” input by the user on the design document registration screen 305 to the value of the attribute “fileName” of the element “documentCls” illustrated in FIG. Then, the XML design information 310 file generated in step 1507 with the file name is stored in the storage unit 102c. Further, the design document reading and conversion unit 202 stores the received design document 304b in the storage unit 102c.
  • the design document reading and conversion unit 202 can store the XML format design information 310 in one field of the database stored in the storage unit 102c. Thereby, even if the layout and items of the design document 304b are changed, it is not necessary to modify the database storing the design information 310 in the XML format. Further, when the design information 310 is stored in one field of the database, the search process can be smoothly performed by maintaining the XML format.
  • the design document reading / conversion unit 202 finally outputs a message indicating that the process has been completed to the output unit 103d in step 1509 and ends.
  • the contents of the spreadsheet format design document 304b are converted into the XML format design information 310 and stored by the design document read conversion unit 202 setting the design information template 303 in accordance with the design information definition body 302. Stored in the unit 102c.
  • the design information 310 can be stored in one file or one column of the database, it is not necessary to modify the database as in the conventional example even if the layout or items of the design document 304b are changed. Therefore, it is possible to flexibly cope with various design documents 304b created or updated in system development, and it is possible to provide an input / output system 100 for a spreadsheet format design document that can easily customize the design document.
  • the design information 310 is not limited to the XML format but can be stored in one column in a desired format (format) such as a text format.
  • FIG. 16 is a flowchart showing an example of processing of the design information search condition input screen output unit 203. This process is executed when the design information input / output device 102 receives a search request from the client device 103.
  • the design information search condition input screen output unit 203 inputs the design information definition body 302 and the design information definition body 302, and outputs a search condition input screen 306a.
  • step 1601 the design information search condition input screen output unit 203 starts processing in response to an instruction (search request) from the input unit 103b of the client device 103.
  • the design information input / output device 102 receives a processing request from the input unit 103b via the communication interface unit 104b, and the design information search condition input screen output unit 203 generates a search condition input screen 306a.
  • step 1602 the design information search condition input screen output unit 203 reads all the design information definition bodies 302 registered in the storage unit 102c.
  • step 1603 the design information search condition input screen output unit 203 uses the value of the attribute “localName” of the element “designSpecification” (3023) of the read design information definition body 302 to “search target” of the generated search condition input screen 306 a. ”(3061).
  • step 1604 when the “search target” (3061) in FIG. 9 is selected by the user, the design information search condition input screen output unit 203 designs that match the “search target” (3061) selected by the user.
  • the information definition body 302 is specified. However, if “search target” is not selected by the user, this step is skipped.
  • the design information search condition input screen output unit 203 designates the “search target” (3061) selected by the user as the design information definition body 302 having the value of the attribute “localName” of the element “designSpecification” (3023). Is identified.
  • the design information search condition input screen output unit 203 generates, for each element “key” included in the specified design information definition body 302, an input form group having the value of the attribute “localName” of the element “key” as a name. .
  • the design information search condition input screen output unit 203 includes the attribute “mandatory” of the element “singleItemKey” (3024) or the element “listItemKey” (3025) included in the element “key” in the generated input form group.
  • an input form (3062, 3064) and a “search” (3063, 3065) button are generated for each value of the attribute “localName”.
  • FIG. 9 is a diagram showing an example of the search condition input screen 306a.
  • the search condition input screen 306a generated by the design information search condition input screen output unit 203 includes a “search target” (3061) for selecting a search target from a pull-down list, items to be searched, and “search” buttons 3063 and 3065.
  • search target (3061) for selecting a search target from a pull-down list, items to be searched, and “search” buttons 3063 and 3065.
  • An example including two input forms 3062, 3064 including is shown.
  • the value of the attribute “localName” of the element “key” is “class / method design information” and “class / method list” based on the design information definition body 302 shown in FIG.
  • the design information search condition input screen output unit 203 includes the element “relationship” in the element “designSpecification” (3023) of FIG. 4 as the “search target” (3061) selected by the user.
  • the design information search condition input screen output unit 203 displays the “parentItem” value and the “childItem” value.
  • a single item group or a plurality of item groups specified in the above are grouped together to generate an input form group, an input form, and a “search” button.
  • an element “relationship” attribute “parentItem” has a value of “classMethodDesignInfo” and a single item group “class / method design information (element“ key ”attribute“ localName ”
  • the value of “class / method design information”, the value of attribute “name” is “classMethodDesignInfo”, and the value of attribute “type” is “single”).
  • the design information search condition input screen output unit 203 has “classMethodList” as the value of the attribute “childItem” of the element “relationship” and the value of the attribute “localName” of the multiple item group “class / method list” (element “key” In the “Class / Method List”, the attribute “name” value is “classMethodList” and the attribute “type” value is “list”).
  • a search condition input screen 306b having “method design information-class method list” is generated as shown in FIG.
  • step 1605 the design information search condition input screen output unit 203 responds the processing response to the client device 103 via the communication interface unit 104b, and the search condition input screen 306a generated in step 1604 is output to the output unit 103d of the client device 103.
  • the process ends after displaying 306b.
  • FIG. 10 is a diagram showing an example of the search condition input screen 306b.
  • the search condition input screen 306a generated by the design information search condition input screen output unit 203 includes a “search target” (3061) for selecting a search target from a pull-down list or the like, a search item, and a “search” button 3067.
  • An example including two input forms 3066 is shown.
  • an input form combining a single item and a plurality of items whose names are “class / method design information-class / method list”. Shows an example generated by the design information search condition input screen output unit 203.
  • search condition input screens 306a and 306b shown in FIG. 9 or FIG. 10 are generated according to the contents of the design information definition body 302, and the user of the client apparatus 103 assigns a desired value to the search item in the input form.
  • the search can be executed by inputting and then pressing the “Search” button.
  • FIG. 17 is a flowchart illustrating an example of processing performed in the design information search and result display screen output unit 204.
  • the design information search and result display screen output unit 204 inputs the design information definition body 302 and the design information 310, executes design information search using the items of the input form received in FIG. 9 or FIG. Is output as a design information search result screen 307. This process is executed after the “search” buttons 3063, 3065, 3067 are clicked on the search condition input screens 306a, 306b.
  • step 1701 the “search” button is clicked on the search condition input screens 306a and 306b, and an instruction (search execution) is generated from the input unit 103b of the client apparatus 103.
  • This instruction is used as a design information search and result display screen output unit.
  • the design information search and result display screen output unit 204 accepts a processing request passed from the input unit 103b via the communication interface unit 104b, and the search condition (input form) input on the search condition input screens 306a and 306b.
  • the design information 310 is searched using the design information definition body 302 using the search item as a search key. That is, the design information search and result display screen output unit 204 searches the file type of the design information 310 according to the search condition.
  • the search range is determined by the design information search and result display screen output unit 204 in units of groups of input forms where the “search” button is clicked. For example, in the search condition input screen 306a of FIG. 9, when a search condition in the input form 3062 is input by “class / method design information” which is a group of input forms and the “search” button 3063 is clicked, design information definition In the body 302, the design information search and result display screen output unit 204 identifies the element “key” having the attribute “localName” having “class / method design information”. The design information search and result display screen output unit 204 acquires the value “classMethodDesignInfo” of “name” of the identified element “key” and uses the acquired value as the value of the attribute “name”. The storage unit 102c is searched in the range of “singleItems”.
  • search condition input screen 306a when a search condition is input in the input form 3064 of the “class / method list” that is a group of input forms and the “search” button 3065 is clicked, design information search and result display are performed.
  • the screen output unit 204 identifies an element “key” having a value of “class / method list” as the attribute “localName” in the design information definition body 302.
  • the design information search and result display screen output unit 204 acquires the “name” value “classMethodList” of the identified element “key”, and the design information element “name” has the acquired value as the attribute “name” value.
  • the storage unit 102c is searched in the range of “listItems” (3037).
  • the search condition is input on the input form 3066 of the “class / method design information-class / method list” as the input form group, and the “search” button 3067 is clicked.
  • the design information search and result display screen output unit 204 adds the element “key” whose attribute “localName” value has “class / method design information” or “class / method list” in the design information definition body 302. Identify.
  • the design information search and result display screen output unit 204 acquires the value “classMethodDesignInfo” or the value “classMethodList” of the specified element “key”, and uses these acquired values as the value of the attribute “name”.
  • the storage unit 102c is searched in the range of the elements “singleItems” and “listItems” of the design information 310 held by the user.
  • step 1703 the design information search and result display screen output unit 204 acquires the file type of the design information 310 searched in step 1702, that is, the value of the attribute “name” of the element “documentCls” of the design information 310.
  • step 1704 the design information search and result display screen output unit 204 reads the design information definition body 302 having the value acquired in step 1703 in the attribute “name” of the element “genericRule” from the storage unit 102c.
  • step 1705 the design information search and result display screen output unit 204 uses the design information 310 acquired in step 1702 and the design information definition body 302 acquired in step 1704, and the design information search results shown in FIGS.
  • the screen 307a, 307b or 307c is generated.
  • the search range of the design information search result screens 307a to 307c shown in FIGS. 11A to 12 is the range searched in step 1702, and the input form to which the “search” buttons 3063 to 3067 clicked on the search condition input screens 306a to 306b belong. Depends on the group.
  • the display screen output unit 204 searches a range of “class / method design information” corresponding to the value of the attribute “name” of the element “singleItems” of the design information.
  • the design information search and result display screen output unit 204 generates a “class / method design information search result screen” 307a shown in FIG.
  • the column header 3071 of the list of the “class / method design information search result screen” 307a includes “reference to design information” (3072) and the local name corresponding to the element name included in the element “singleItems”.
  • the attribute “name” of the element “singleItemKey” of the design information definition body 302 is specified, and the value of the attribute “localName” is assigned.
  • the design information search and result display screen output unit 204 generates a “class / method list search result screen” 307b shown in FIG.
  • the column header 3071 of the list includes “design information reference” (3072), a local name corresponding to the element name included in the element “member”, and an attribute “name” of the element “listItemKey” of the design information definition body 302.
  • the design information search and result display screen output unit 204 identifies and assigns a value of the attribute “localName”.
  • the search condition input screen 306b when a search condition is input in the input form 3066 of the input form group “class / method design information-class / method list” and the “search” button 3067 is clicked, design information search is performed.
  • the result display screen output unit 204 sets the “class / method design information” corresponding to the value of the attribute “name” of the element “singleItems” of the design information and the value of the attribute “name” of the element “listItems”. Search the corresponding "class / method list” range.
  • the design information search and result display screen output unit 204 generates a “class / method list search result screen” 307c in the form of these search results.
  • the design information search and result display screen output unit 204 assigns a “design information reference” (3072) and a local name corresponding to the element name included in the element “singleItems” to the column header 3071 of the list.
  • the attribute “name” of the element “singleItemKey” 302 is identified, the value of the attribute “localName”, and the local name corresponding to the element name included in the element “member” are stored in the element “listItemKey” of the design information definition body 302.
  • the attribute “name” is specified and the value of the attribute “localName” is assigned.
  • the value of “design information reference” (3072) in any of the above-described design information search result screens 307a, 307b, and 307c is a button for transitioning to the design information reference and editing screen 308, and is displayed in the design information of each row of the list.
  • the corresponding design document file name that is, the value of the attribute “fileName” of the element “documentCls” of the design information 310 is held.
  • the design information search and result display screen output unit 204 finally returns a process response to the client device 103 via the communication interface unit 104b in step 1706, and the design information generated in step 1705 in the output unit 103d of the client device 103.
  • the search result screens 307a to 307c are displayed and the process is terminated.
  • the design information input / output device 102 can output the search results based on the search conditions received from the client device 103 as the design information search result screens 307a, 307b, 307c.
  • the design information input / output device 102 searches the XML design information 310 file using the received search conditions. That is, even if the layout and items of the design document 304b are changed, the design information input / output device 102 can search for the XML-format design information 310 file. Therefore, unlike the conventional example, it is not necessary to modify the database in accordance with the layout or item change of the design document 304b, and the labor and operation cost associated with the change of the design document 304b can be reduced.
  • FIG. 18 is a flowchart showing an example of processing of the design information reference and edit screen output unit 205. This process is executed when “design information reference” (3072) on the design information search result screens 307a to 307c is clicked.
  • the design information reference / edit screen output unit 205 receives the design information definition body 302 and the design information 310 and outputs the design information reference / edit screen 308.
  • step 1801 the “design information reference” (3072) button displayed on the design information search result screen 307a, 307b, or 307c is clicked, and an instruction is generated from the input unit 103b of the client apparatus 103. Processing begins.
  • the design information reference and edit screen output unit 205 includes the design document file name assigned to the “design information reference” (3072) button in the value of the attribute “fileName” of the element “documentCls” (3031).
  • the information 310 is retrieved from the storage unit 102c.
  • step 1803 the design information reference and edit screen output unit 205 acquires the file type of the design information 310 read in step 1802, that is, the value of the attribute “name” of the element “documentCls” (3031) of the design information 310.
  • Step 1804 the design information definition body 302 having the attribute “name” of the element “genericRule” (3021) as the attribute “name” of the element “genericRule” (3021) is read from the storage unit 102c.
  • step 1805 the design information reference and edit screen 308 shown in FIG. 13 is used by using the design information definition body 302 read in step 1804 for the design information 310 acquired in step 1802 by the design information reference and edit screen output unit 205. Is generated.
  • the design information reference / edit screen output unit 205 corresponds to the value of the attribute “name” of the element “documentCls” (3031) of the design information 310 as the “file type” (3081) of FIG.
  • the value of the attribute “localName” of the element “documentCls” of the design information definition body 302 and the value of the attribute “fileName” of the element “documentCls” (3031) are generated as “file name” (3082).
  • the design information reference / edit screen output unit 205 performs the design in step 1804 corresponding to the value of the attribute “name” of the element “sheetCls” of the design information 310 as “sheet type” (3084) in the “file type” (3081). A value of the attribute “localName” of the element “sheetCls” of the information definition body 302 is generated.
  • the design information reference and edit screen output unit 205 generates the value of the attribute “date” of the element “documentCls” within the “registration date” (3083). Further, a single item group and a plurality of item groups are generated in the “sheet type” (3084).
  • the design information reference and edit screen output unit 205 sets the element value included in the element “singleItems” (3033) as an uneditable text on the design information reference and edit screen 308, or editable input. Whether the field is a field is determined by the value of the element “itemType” of the corresponding design information definition body 302, and the design information reference and edit screen 308 is generated.
  • the design information reference and edit screen output unit 205 stores the element “key” of the design information definition body 302 read in step 1804 corresponding to the value of the attribute “name” of the element “listItems” (3037).
  • the value of the attribute “localName”, the element included in the element “member” included in the element “listItems” (3037), and the value thereof are generated in a list format.
  • the design information reference and edit screen output unit 205 sets the local name corresponding to the element name included in the element “member” in the column header 3085 of the list, and the attribute of the element “listItemKey” (3025) of the design information definition body 302. Specify “name” and assign the value of attribute “localName”.
  • the design information reference and editing screen output unit 205 determines whether the value to be listed is a text that cannot be edited or an input field that can be edited on the screen.
  • the design information reference and edit screen 308 is generated by determining with the value of “itemType”.
  • the size of the area for displaying the values listed in the design information reference / edit screen 308 is the value of the element “itemLength” of the design information definition body 302 to which the design information reference / edit screen output unit 205 corresponds. Determine and generate a screen. When the “Add” (3086) button on the design information reference and edit screen 308 is clicked, a new line can be added to the list.
  • step 1806 the design information reference / edit screen output unit 205 returns a processing response to the client device 103 via the communication interface unit 104b, and the design information generated in step 1705 is referred to the output unit 103d of the client device 103. Then, the editing screen 308 is displayed and the processing is terminated.
  • the design information input / output device 102 can read the design information 310 in the XML format and display it as the design information reference and edit screen 308.
  • FIG. 19 is a flowchart showing an example of processing of the design information editing processing unit 206.
  • the design information edit processing unit 206 receives the design information definition body 302, the design information template 303, the design information 310, and the design document template 304a as input, and the design information 310 (FIG. 6) edited on the design information reference and edit screen 308.
  • the design document 304c (FIG. 7C) is output.
  • step 1901 when the “registration / design document output” (3088) button displayed on the design information reference and edit screen 308 is clicked, an instruction is generated from the input unit 103 b of the client apparatus 103, and the process is triggered by this instruction. Is started.
  • the design information editing processing unit 206 has a design information definition having the “file type” (3081) value of the design information reference and edit screen 308 as the attribute “localName” value of the element “genericRule” (3021).
  • the body 302 is read from the storage unit 102c.
  • the design information editing processing unit 206 stores the “file type” (3081) of the design document meta information 301 read in step 1902 from the files of the design document meta information 301 registered in the storage unit 102c.
  • the design information template 303 file having the same value as the “alphabetic name” as the value of the attribute “name” of the element “documentCls” of the design information template 303 is read from the storage unit 102c.
  • step 1904 the design information editing processing unit 206 first sets the “file name” (3082) of the design information reference and edit screen 308 to the value of the attribute “fileName” of the element “documentCls” (3031) of the design information template 303. Set.
  • the design information editing processing unit 206 reads the value of a single item or a plurality of items from the design information reference and edit screen 308 and substitutes it into a predetermined variable. Then, the design information 310 in the XML format is generated by setting the value of the variable in the design information template 303 read in step 1903.
  • the design information editing processing unit 206 receives the element “singleItemKey” (3024) or the element “listItemKey” (3024) of the design information definition body 302 read in step 1902 corresponding to a single item or a plurality of items from the design information reference and edit screen 308. 3025) When the value of the attribute “mandatory” is “true”, but the value of the single item or multiple items is not input on the design information reference and edit screen 308, or is not deleted Output an error.
  • the design information editing processing unit 206 When the value of the attribute “type” of the element “key” of the design information definition body 302 is “single” for the single item, the design information editing processing unit 206 has the element “singleItemKey” (3024) of the design information definition body 302 A value having the same name as the attribute “localName” in the header is acquired from the design information reference and edit screen 308. The design information editing processing unit 206 uses the acquired value as the value of the attribute “sheetCls” of the element “designSpecification” (3023), the value of the attribute “name” of the element “key”, and the element of the design information definition body 302.
  • a variable is generated in a format in which the value of the attribute “name” of “singleItemKey” (3024) is concatenated with “.”, And the value is substituted. The above process is repeated by the number of elements “singleItemKey” of the design information definition body 302.
  • the design information editing processing unit 206 When the value of the attribute “type” of the element “key” of the design information definition body 302 is “list” for a plurality of items, the design information editing processing unit 206 has an element “listItemKey” (3025) of the design information definition body 302 A plurality of values of the column having the same name as the attribute “localName” in the list header are acquired from the design information reference and edit screen 308.
  • the design information editing processing unit 206 uses the acquired value as the value of the attribute “sheetCls” of the element “designSpecification” (3023) of the design information definition body 302 and the value of the attribute “name” of the element “key”. Variables are generated in a format concatenated with "". This variable is a list object, and a value obtained from the design information reference and edit screen 308 by creating a variable whose name is the value of the attribute “name” of the element “listItemKey” (3025) of the design information definition body 302 Register.
  • the design information editing processing unit 206 generates the design information 310 by replacing the value of the variable generated as described above with the corresponding value of the “$” variable in the design information template 303. It should be noted that the processing of the portion surrounded by “#foreach (each $ member in $ XXXX)” and “#end” in the design information 310 is the same as the processing in step 1507 above.
  • the design information edit processing unit 206 generates the edited XML format design information 310 from the design information reference and edit screen 308.
  • the design information editing processing unit 206 stores the design information 310 generated in step 1904 in the storage unit 102c, and updates the design information 310 with the edited data.
  • the design information editing processing unit 206 can store the XML-format design information 310 in one column of the database.
  • step 1906 the design information editing processing unit 206 uses the design file template 304a stored in advance for each file type in the storage unit 102c as the “file type” (3081) value on the design information reference and edit screen 308. And read from the storage unit 102c.
  • step 1907 the design information editing processing unit 206 uses the design information definition body 302 read in step 1902 to update the design document template 304a read in step 1906 from the design information 310 generated in step 1904.
  • a design document 304c reflecting the design information 310 edited on the design information reference and edit screen 308 is generated.
  • the design information editing processing unit 206 uses the element “key” of the design information definition body 302 having the same value as the value of the attribute “name” of the element “singleItems” (3033) of the design information 310.
  • the element “singleItemKey” (3024) having the same value as the value of each element included in the element “singleItems” (3033) of the design information 310 in the attribute “name” (within the specified element “key”) Is identified.
  • Each element included in the element “singleItems” (3033) of the design information 310 is acquired from the element “cellLine” in the element “singleItemKey” (3024) and the spreadsheet column is acquired from the element “cellColumn”. Is reflected in the cell specified by the row and column acquired in the design template template 304a read in step 1906.
  • the design information editing processing unit 206 identifies the element “key” of the design information definition body 302 having the same value as the value of the attribute “name” of the element “listItems” (3037) of the design information 310. To do. Then, the design information editing processing unit 206 has an element “listItemKey” (within the specified element “key”) having the same value as the value of each element included in the element “member” of the design information 310 (within the specified element “key”). 3025).
  • the design information editing processing unit 206 acquires the spreadsheet row from the element “cellLine” in the element “listItemKey” (3025) and the spreadsheet column from the element “cellColumn”, and the element “member” of the design information 310. The value of each element included in is reflected in the cell specified by the row and column acquired in the design template template 304a read in step 1906.
  • the design information editing processing unit 206 adds the date, time, day, minute, and second of this process to the value of the attribute “date” of the element “documentCls” (3031) of the design information 310, for example “YYYY / MM / DD / HH: Set in the format of “MM: SS”.
  • step 1908 the design information editing processing unit 206 stores the design document 304c generated in step 1907 in the storage unit 102c, performs data transfer processing via the communication interface unit 104b, and stores it in the storage unit 103c of the client device 103. sign up.
  • the design information editing processing unit 206 may edit the design document 304c generated in step 1907 with the spreadsheet unit 211 on the client device 103, for example, and use this as the design document 304b.
  • the design information editing processing unit 206 finally outputs a message indicating that the processing has been completed to the output unit 103d in step 1908.
  • the design information 310 edited on the design information reference and edit screen 308 is stored in the storage unit 102c as XML data, and the design information 310 is converted into a spreadsheet design document 304c and sent to the client apparatus 103. Is output.
  • the first embodiment it is possible to realize a spreadsheet-style design document input / output system 100 that can flexibly cope with various design documents created in system development and can be easily customized.
  • the design information 310 may be stored as an XML file, stored in one column of the database, or stored in the XML database. Good.
  • the design document 304b is in the XML format, but if it is a semi-structured data format similar to XML (Extensible Markup Language), JSON (JavaScript Object Notation). Or the like.
  • the spreadsheet format is information generated by the spreadsheet units (spreadsheet software) 210 and 211, and may be configured to include cells having row and column identifiers and sheets having a plurality of cells.
  • the design document 304b of a spreadsheet format is converted into an XML format, edited, and searched If it is.
  • the design document 304b of the first embodiment may be replaced with input information
  • the design information definition body 302 may be replaced with an input information definition body
  • the design information template 303 may be replaced with a conversion information template.
  • FIG. 21 is a block diagram illustrating an example of functional elements of the computer 10 according to the second embodiment.
  • the second embodiment shows an example in which the design information input / output device 102 shown in the first embodiment is operated on the computer 10 as a virtual server.
  • Other configurations are the same as those of the first embodiment.
  • a virtualization unit 400 that provides computer resources to a virtual server operates, and one or more guest OSs 710-1 to 710-x operate on the virtualization unit 400.
  • the guest OS 710-1 provides a design information input / output server 102-1
  • the guest OS 710-x provides a virtual server 102-x.
  • the virtualization unit 400 and the guest OSs 710-1 to 710 -x are loaded into the memory 70 of FIG. 20 allocated by the virtualization unit 400 and executed by the processor 60.
  • the virtualization unit 400 provides the guest OSs 710-1 to 710-x with the input unit 102b, the storage unit 102c, the output unit 102d, and the communication interface unit 104b, which are computer resources of the computer 10.
  • the design document reading conversion unit 202 On the guest OS 710-1, the design document reading conversion unit 202, the design information search condition input screen output unit 203, the design information search and result display screen output unit 204, the design information A reference and edit screen output unit 205 and a design information edit processing unit 206 are operated.
  • the design document reading conversion unit 202 to the design information editing processing unit 206 provide the functions of the respective units when the processor 60 executes the respective programs, as in the first embodiment.
  • the client apparatus 103 connected via the network 40 can use each function of the design information input / output server 102-1 via the browser 212.
  • the browser 212 reads the design document read conversion unit 202 of the design information input / output server 102-1, and registers the design document 304b.
  • the client apparatus 103 transmits the design document 304b to the design information input / output server 102-1, and the design information input / output server 102-1 stores the received design document 304b in the storage unit 102c.
  • the design document read conversion unit 202 reads the design information definition body 302 and the design information template 303 corresponding to the design document 304b stored in the storage unit 102c, converts the design information template 303 into the XML design information 310, and stores it in the storage unit 102c. .
  • the virtualization unit 400 may generate the design information input / output server 102-1 in response to a request from the client device 103.
  • the computer resources of the computer 10 can be used effectively.
  • design document meta information conversion apparatus 101 and the client apparatus 103 shown in the first embodiment may be virtual servers on the computer 10.
  • the design information input / output server 102-1 may be operated in a cloud system having a plurality of computers 10.
  • the design information 310 in the XML format is stored in the storage unit 102c as an XML file, stored in one column (or one field) of the database storing the design information 310, or stored in the above-described XML database format or the like. Since it can be stored in the apparatus, it is not necessary to change the schema of the database even when the layout of the design document is changed.
  • the spreadsheet format design document 304b is converted into the XML format design information 310 and stored in the storage unit 102c.
  • the layout of the design document 304b is changed, it is not necessary to modify the file or database for storing the design information 310, and the labor and operation costs associated with the change of the design document 304b are reduced as compared with the conventional example. Can be reduced.
  • the design document meta information conversion device 101 changes the design document meta information 301 to reproduce the design information definition body 302 and the design information template 303. And transmitted to the design information input / output device 102.
  • the design information input / output device 102 uses the regenerated design information definition body 302 and the design information template 303 to convert the spreadsheet format design document 304b input as described above into the XML format and store the storage unit 102c. Can be stored.
  • the design information input / output device 102 also stores screens and processes for searching and editing the design information 310 by storing the regenerated design information definition body 302 and the design information template 303 in the storage unit 102c.
  • the design information 310 that can be automatically changed, edited, and re-stored can be output as a design document 304c in a spreadsheet format.
  • the present invention can flexibly cope with various design documents created or updated in system development, and the spreadsheet design document input / output system 100 that allows easy customization of the design document. Can be provided.
  • this invention is not limited to the above-mentioned Example, Various modifications are included.
  • the above-described embodiments are described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described.
  • a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment.
  • any of the additions, deletions, or substitutions of other configurations can be applied to a part of the configuration of each embodiment, either alone or in combination.
  • each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit.
  • each of the above-described configurations, functions, and the like may be realized by software by the processor interpreting and executing a program that realizes each function.
  • Information such as programs, tables, and files for realizing each function can be stored in a memory, a hard disk, a recording device such as an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a DVD.
  • control lines and information lines indicate what is considered necessary for the explanation, and not all the control lines and information lines on the product are necessarily shown. Actually, it may be considered that almost all the components are connected to each other.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • General Physics & Mathematics (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • General Engineering & Computer Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Data Mining & Analysis (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Databases & Information Systems (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Stored Programmes (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Document Processing Apparatus (AREA)
PCT/JP2017/004537 2016-02-19 2017-02-08 設計書の入出力装置、設計書の入出力システム及び設計書の入出力方法 Ceased WO2017141785A1 (ja)

Priority Applications (1)

Application Number Priority Date Filing Date Title
MYPI2018702621A MY194133A (en) 2016-02-19 2017-02-08 Design specification input and output device, design specification input and output system, and design specification input and output method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2016030214A JP6425672B2 (ja) 2016-02-19 2016-02-19 設計書の入出力装置、設計書の入出力システム及び設計書の入出力方法
JP2016-030214 2016-02-19

Publications (1)

Publication Number Publication Date
WO2017141785A1 true WO2017141785A1 (ja) 2017-08-24

Family

ID=59625883

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2017/004537 Ceased WO2017141785A1 (ja) 2016-02-19 2017-02-08 設計書の入出力装置、設計書の入出力システム及び設計書の入出力方法

Country Status (3)

Country Link
JP (1) JP6425672B2 (cg-RX-API-DMAC7.html)
MY (1) MY194133A (cg-RX-API-DMAC7.html)
WO (1) WO2017141785A1 (cg-RX-API-DMAC7.html)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7765117B1 (ja) * 2024-10-22 2025-11-06 株式会社ノベルワークス システム、コンピュータおよびデータ製造方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005092522A (ja) * 2003-09-17 2005-04-07 Nomura Research Institute Ltd 画面状態遷移システム、インターフェースシステム、画面状態遷移プログラム、インターフェースシステム用プログラム、画面状態遷移方法及びインターフェース方法
JP2010271968A (ja) * 2009-05-22 2010-12-02 Towa System Inc リポジトリ管理サーバ
JP2014222414A (ja) * 2013-05-13 2014-11-27 富士通株式会社 設計書データ作成支援プログラム、設計書データ作成支援方法および情報処理装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005092522A (ja) * 2003-09-17 2005-04-07 Nomura Research Institute Ltd 画面状態遷移システム、インターフェースシステム、画面状態遷移プログラム、インターフェースシステム用プログラム、画面状態遷移方法及びインターフェース方法
JP2010271968A (ja) * 2009-05-22 2010-12-02 Towa System Inc リポジトリ管理サーバ
JP2014222414A (ja) * 2013-05-13 2014-11-27 富士通株式会社 設計書データ作成支援プログラム、設計書データ作成支援方法および情報処理装置

Also Published As

Publication number Publication date
JP6425672B2 (ja) 2018-11-21
MY194133A (en) 2022-11-14
JP2017146923A (ja) 2017-08-24

Similar Documents

Publication Publication Date Title
US11822615B2 (en) Contextual editing in a page rendering system
CN108762743B (zh) 一种数据表操作代码生成方法及装置
KR101275871B1 (ko) ＳａａＳ 환경에서의 홈페이지 제작 시스템 및 방법, 그 방법을 컴퓨터에서 실행하기 위한 컴퓨터 프로그램이 기록된, 컴퓨터로 판독 가능한 기록 매체
US9817811B2 (en) Web server system, dictionary system, dictionary call method, screen control display method, and demonstration application generation method
JP2004005568A (ja) レガシー・アプリケーションの高速ｇｕｉ体裁更新
US8136043B2 (en) GUI generation apparatus and method for generating GUI
US20050132278A1 (en) Structural conversion apparatus, structural conversion method and storage media for structured documents
US20080250052A1 (en) Repopulating a database with document content
JP6676564B2 (ja) 開発支援システムおよび方法
US20240086179A1 (en) Software component update system, and software component update method
JP7692134B1 (ja) システム開発支援方法、プログラム及び開発支援システム
JP6425672B2 (ja) 設計書の入出力装置、設計書の入出力システム及び設計書の入出力方法
JP6231260B2 (ja) 画面制御システム、画面制御プログラム、画面作成支援プログラム及び画面制御方法
JP4686117B2 (ja) ソースコード変換装置、ソースコード変換方法、およびプログラム
US20190278570A1 (en) Annotating Features of a Resource to Facilitate Consumption in Different Computing Environments
Zahorodko et al. An approach for processing and document flow automation for Microsoft Word and LibreOffice Writer file formats.
JP6647954B2 (ja) 設計書の入出力装置、設計書の入出力システム及び設計書の入出力方法
JP5962116B2 (ja) 画面制御システム、画面制御プログラム、画面作成支援プログラム及び画面制御方法
JP6331307B2 (ja) 情報処理装置、情報処理装置の制御方法、およびプログラム
JP7763022B2 (ja) 情報処理装置、情報処理システム、制御方法、プログラム及び記録媒体
JP7411766B2 (ja) 設定業務支援装置、設定業務支援方法および設定業務支援プログラム
JP2013238976A (ja) ソースコード生成システム
JP2025162593A (ja) 情報処理システム、情報処理方法およびプログラム
Мерзликін et al. An approach for processing and document flow automation for Microsoft Word and LibreOffice Writer file formats
Gündoğan Automation of Artwork Processes

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17753043

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17753043

Country of ref document: EP

Kind code of ref document: A1