JP2010205153A - Repository management server - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a repository management server capable of reducing a design man-hour. <P>SOLUTION: In a repository management system having a plurality of terminal devices having a browser and a repository management server connected to the terminal devices through a network, the repository management server accesses a design information DB by making data described in HTML communicate with the terminal devices to retrieve, to update, to register, and to erase system information, subsystem information, sub application information, table information, screen information and an item dictionary. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a repository management server that performs system design by transmitting and receiving packets including data described in a predetermined communication description language with a plurality of terminal devices connected via a network according to a predetermined communication protocol.

  System design is the overall system design, the system is divided into multiple subsystems, each subsystem design, screen list design and table list design requirements definition process, each subsystem is divided into multiple sub-apps Designing each sub-app, screen layout of the screen belonging to each sub-app, screen action indicating screen transition based on triggering action and screen design such as screen item and basic design process for table design, and table manipulation The program development process is carried out through a detailed design process for designing the SQL specifications and environment design for the purpose.

  In the requirement definition process, documents such as a business requirement definition document and a business flowchart are outputs in the design of the entire system, and documents such as a subsystem list and a subsystem summary document are outputs in the subsystem design. In the basic design process, in the sub-application design, the sub-application summary document and the sub-application list, in the screen design, the screen layout, the screen action, the screen transition diagram, the screen item, and the table design are the column list. In the detailed design process, SQL specifications and environmental design documents are outputs.

  Conventionally, each design is individually designed by each designer using a terminal device, and the output design document is managed as a general file. In the review of the design document, the review was performed based on the printed design document or the design document distributed by file transfer. When a system is proposed to a customer, a screen layout screen is presented. The layout screen is created using a table creation tool or the like, or an HTML file described in HTML (Hyper Text Markup Language) is displayed on the screen as an image. It was created by displaying and capturing images, and was created separately from the design document.

  Screen items and table columns are defined with reference to the item dictionary, but cannot be defined in cooperation with the item dictionary on the terminal device screen. In addition, the subsystem list, sub-application list, transition diagram, and the like have to be created as separate design documents. Progress management was based on reports from designers.

  However, in the conventional system design, the design document is managed as a general file, and it is not managed centrally, so the management is insufficient. Since the review was based on the printed design document, labor and resources for printing the design document were wasted. Even when the design document is transferred and distributed, the effort to distribute the design document is wasted. Even when the system is presented to the customer, the layout screen image is created using a table creation tool or the like and presented to the customer, which causes a problem of extra man-hours.

  Since screen items and table columns could not be defined in conjunction with the item dictionary, there was a risk of input errors. In addition, since the subsystem list, the sub-application list, the screen transition diagram, and the like have to be created separately, there is a problem that extra man-hours are required. Progress management is also performed based on the declaration of the designer, and there is a problem that objective management cannot be performed in real time.

  The present invention has been made in view of the above-described problems, and a person who has access rights can manage a design document in a unified manner without printing or transferring the file to distribute the design document. It can be accessed through the network and reviewed on the screen of the terminal device, and it is not necessary to create a layout screen that is proposed to the customer separately from the design document or to create a list. An object of the present invention is to provide a repository management server that can define screen items and table columns without error by linking to a dictionary.

  According to the present invention, a repository management server that performs system design by transmitting and receiving packets including data described in a predetermined communication description language to a plurality of terminal devices connected via a network according to a predetermined communication protocol A system information database for storing system information relating to the entire system, a subsystem information database for storing subsystem information relating to each subsystem obtained by dividing the system into a plurality of subsystems, and a plurality of subsystems. A sub application information database that stores sub application information related to each sub application divided into a plurality of sub applications, a screen information database that stores screen information in each sub application, and table information related to each of the plurality of tables are stored. A data information database, an input data extraction unit that extracts data described in the communication description language included in the packet from the terminal device, and the data extracted by the input data extraction unit is a search request for system information The system information reference unit that searches the system information database and outputs system information as design information, and indicates that the data extracted by the input data extraction unit is a registration or update request for system information A system information registration / update unit for registering or updating the system information in the system information database based on the data extracted by the input data extraction unit; and the data extracted by the input data extraction unit is a subsystem. When indicating that it is an information retrieval request, When the system information database is searched and the subsystem information reference unit that outputs the subsystem information as the design information and the data extracted by the input data extraction unit indicate that it is a registration or update request of the subsystem information, A subsystem information registration / update unit for registering or updating the subsystem information in the subsystem information database based on the data extracted by the input data extraction unit, and the data extracted by the input data extraction unit When indicating that it is a search request for information, the sub-application information database is searched, the sub-application information reference unit that outputs the sub-application information as design information, and the data extracted by the input data extraction unit is registered in the sub-application information Or when indicating an update request, Based on the data extracted by the input data extraction unit, the sub application information registration / update unit for registering or updating the sub application information including information about the subsystem to which the sub application belongs in the sub application information database, and the input data extraction unit When the extracted data indicates a screen information search request, the screen information database is searched and the screen information reference unit that outputs the screen information as design information is extracted by the input data extraction unit When the data indicates a screen information registration or update request, the screen information including information about the sub-app to which the screen belongs is registered or updated based on the data extracted by the input data extraction unit. Screen information registration / update unit, and the input data extraction unit When the extracted data indicates a table information search request, the table information database is searched and the table information reference unit that outputs the table information as design information is extracted by the input data extraction unit. A table information registration / update unit for registering or updating the table information in the table information database based on the data extracted by the input data extraction unit, The design information output from the system information reference unit, the subsystem information reference unit, the sub application information reference unit, the screen information reference unit, and the table information reference unit based on the communication description language Edit the screen data of the corresponding reference screen displayed in The system information, the subsystem information, the sub-app information, the screen information, and the design information of the table information are input from the terminal device and edited into the corresponding registration / update screen data for registration or update. A repository management server including an output data editing unit is provided.

  According to the present invention, the repository management server searches the database, edits system information, subsystem information, sub-application information, screen information, and table information into screen data of the corresponding reference screen described in the communication description language. Since the data is stored in a packet and transmitted to the terminal device, the terminal device displays the design information of the system information, subsystem information, sub application information, screen information and table information on the relevant reference screen on the screen. Can be reviewed without distribution by printing or file transfer. Therefore, useless man-hours and wasteful use of resources can be reduced.

  Based on the communication description language, system information, subsystem information, sub application information, screen information, and table information design information are input from the terminal device and edited to the corresponding registration / update screen data for registration or update. The screen data is accommodated in a packet and transmitted to the terminal device. The terminal device can register / update the input design information in the database of the repository management server. It is possible to design a system through communication. In addition, the design information is highly referential, and the design information can be centrally managed, so that the design work can be made more efficient. Since the design document at the design stage is stored and accessible in a common database of the repository management server, objective and easy progress management can be performed.

1 is a schematic configuration diagram of a repository management system according to an embodiment of the present invention. It is a functional block diagram of the repository management server in FIG. FIG. 3 is a functional block diagram of a subsystem information access unit in FIG. 2. It is a functional block diagram of the sub application information access part in FIG. FIG. 3 is a functional block diagram of a screen information access unit in FIG. 2. It is a functional block diagram of the table information access part in FIG. It is a functional block diagram of the item dictionary access part in FIG. It is a logical block diagram of the database concerning this invention. It is a logic block diagram of screen information DB in FIG. It is a logical block diagram of the item information DB in FIG. It is a figure which shows the system information stored in system information DB in FIG. It is a figure which shows the subsystem information stored in subsystem information DB in FIG. It is a figure which shows the sub application information stored in sub application information DB in FIG. It is a figure which shows the screen layout information stored in the screen layout information DB in FIG. It is a figure which shows the action information stored in action information DB in FIG. It is a figure which shows the screen item information stored in the screen item information DB in FIG. It is a figure which shows the screen table information stored in screen table information DB in FIG. It is a figure which shows the test case stored in test case DB in FIG. It is a figure which shows the document information stored in document information DB in FIG. It is a figure which shows the column information stored in table information DB in FIG. It is a figure which shows the item dictionary information, the item use screen item information, and the item use column information which are stored in the item dictionary information DB in FIG. It is a figure which shows the user information stored in user information DB in FIG. It is a flowchart of an authentication and access right check. It is a flowchart of search / registration / update / deletion of system information. It is a flowchart in connection with a subsystem list screen. It is a flowchart of search / registration / update / deletion of subsystem information. It is a flowchart in connection with a sub application list screen. It is a flowchart of search / registration / update / deletion of sub application information. It is a flowchart in connection with a screen list screen. It is a flowchart in connection with a screen layout screen. It is a flowchart in connection with an action list screen. It is a flowchart in connection with a screen item list screen. It is a flowchart in connection with a screen transition diagram screen. It is a flowchart in connection with a screen table. It is a flowchart in connection with a table related figure. It is a flowchart in connection with a screen test case list screen. It is a flowchart in connection with a table list screen. It is a flowchart in connection with a table information screen. It is a flowchart in connection with an item dictionary screen. It is a flowchart in connection with an item dictionary screen. It is a flowchart in connection with a user list screen. It is a flowchart in connection with a group list screen. It is a flowchart regarding a design document output. It is a figure which shows a menu screen. It is a figure which shows a system information screen. It is a figure which shows a subsystem list screen. It is a figure which shows a subsystem information screen. It is a figure which shows a sub application list screen. It is a flowchart in connection with a sub application information screen. It is a figure which shows a screen list screen. It is a figure which shows a screen layout screen. It is a figure which shows an action list screen. It is a figure which shows a screen item screen. It is a figure which shows an item reference screen. It is a figure which shows a screen transition diagram. It is a figure which shows a table list screen. It is a figure which shows a table related figure. It is a figure which shows a test case list screen. It is a figure which shows a document list screen. It is a figure which shows a table list screen. It is a figure which shows a table reference origin screen. It is a figure which shows a table information screen. It is a figure which shows an item dictionary screen. It is a figure which shows an item use object list screen. It is a figure which shows an item use column list screen. It is a figure which shows a user information list screen. It is a figure which shows a user edit screen. It is a figure which shows a group list screen. It is a figure which shows a group edit screen. It is a figure which shows a printing screen.

  FIG. 1 is a configuration diagram of a repository management system according to an embodiment of the present invention. As shown in FIG. 1, the repository management system 1 includes a plurality of terminal devices 2 # i (i = 1 to n) and the terminal devices 2 # i (i = 1 to n) connected via a communication network 4. A repository management server 6 is provided. Reference numeral 2 # i indicates an arbitrary one of a plurality of terminal devices, but is abbreviated as 2 below.

  The terminal device 2 is a PC (Personal Computer), a WS (Work Station), or the like, and transmits communication data including design data described in a predetermined communication description language, for example, HTML, through a communication network 4, a predetermined communication protocol, For example, it is a terminal that performs system design by communicating with the repository management server 6 in accordance with HTTP (Hyper Text Transfer Protocol).

The communication protocol may be a protocol other than HTTP as long as communication with the repository management server 6 is possible via the network 4. The predetermined communication description language is such that the terminal device 2 uses software to display design information on the screen as a search result by the repository management server 6 included in the packet, and input or click operation using a keyboard or the like on the screen (both screen operation) If the design information can be registered / updated / deleted in the design information DB 8, the user information DB 10 and the group information DB 12, it is not limited to HTML.
Hereinafter, the predetermined communication protocol is described as HTTP, the predetermined communication description language is described as HTML, and the software is described as browser software (hereinafter also referred to as a browser).

  Although not shown, the terminal device 2 includes a CPU, a display device, an input unit, a ROM, a main memory, a storage medium, an I / O controller, a communication interface unit, and the like. The CPU executes browser software that creates communication data including design information described in HTML based on screen display or screen operation of screen data of design information described in an operating system (OS) or HTML. The display device is a monitor screen that displays design information and the like.

  The input means is a keyboard or the like that can input characters, numbers, etc., and a mouse for performing a click operation in a GUI (Graphical User Interface) environment that provides an intuitive input operation to the screen. The ROM is a memory that stores an OS program such as BIOS that is executed by the CPU when the terminal device 2 is activated.

  The main memory is a main memory that is loaded by various programs such as an OS and a browser and is executed by the CPU. The storage medium is a storage medium such as a hard disk or an optical disk, and stores browser software and the like. The I / O controller controls reading and writing of data from the CPU to the storage medium. The communication interface unit manages an interface between the communication network 6 and the CPU.

  The communication network 6 is a communication network such as a LAN (Local Area Network), and is limited to a LAN as long as system design is possible by communication of design information and the like between the terminal device 2 and the repository management server 6. Alternatively, a WAN (Wide Area Network), the Internet, or the like may be used. The communication network 6 includes a case where it is connected to the terminal device 2 via a wired communication cable such as a LAN cable or an optical fiber, or a case where it is connected wirelessly.

  The repository management server 6 includes a design information DB 8, a user information DB 10, and a group information DB 12. The hardware configuration of the repository management server 6 is the same as that of the terminal device 2, and each function is realized by executing a program on the CPU and functions as a Web application. Hereinafter, an outline of functions of the repository management server 6 will be described.

    (1) When the URL (Uniform Resource Locator) of the repository management server 6 is specified from the terminal device 2 and an access request packet to the repository management server 6 is received, it is described in HTML that requests input of a user ID and password. A response packet including authentication request screen data is transmitted to the terminal device 2.

    (2) When a packet including a user ID and a password is received from the terminal device 2, the user information DB 10 and the group information DB 12 are searched, and whether or not the user of the terminal device 2 has the right to access the repository management server 6 If the user has the right to access, the session is associated with the user, and a packet including the screen data of the menu screen described in HTML is transmitted to the terminal device 2.

    (3) When a packet in which the URL of the corresponding screen is specified based on the click operation on the menu screen shown in FIG. 44 from the terminal device 2 is received, the user information is based on the user name associated with the session. When the DB 10 and the group information DB 12 are searched and the user has the right to refer to the design information DB 8, the design information DB 8 is searched and the system name of the corresponding screen, the system code, the updater, the update date system information, etc. The design information is read out, the design information is edited into corresponding screen data such as a system information screen based on HTML, and a packet including the design information is transmitted to the terminal device 2.

    (4) Information specifying the URL of the corresponding screen and the design information to be searched based on the click operation on the screen shown in FIG. 45 from the terminal device 2 (subsystem ID, screen ID, If the user has the right to search the user information DB 10 and the group information DB 12 based on the user name associated with the session and refer to the design information DB 8. The design information DB 8 is searched, the corresponding design information is read, the design information is edited into screen data of the corresponding screen based on HTML, and a packet including the design information is transmitted to the terminal device 2.

    (5) Design information such as system information, subsystem information, sub application information, screen information, table information, dictionary information, and message information based on the input operation and click operation on the screen shown in FIG. When receiving a packet for instructing registration / update / deletion, design information included in the packet is extracted, and the user information DB 10 and the group information DB 12 are searched based on the user name associated with the session. If the user has an access right to register / update / delete etc. in the design information DB 8, design information such as system information and subsystem information is registered / updated / deleted in the design information DB 10 together with the user name and update date. In the case of registration / update of design information, the validity of the design information input from the terminal device 2 is checked, and if it is valid, it is registered / updated in the design information DB 8. Then, the terminal device 2 is notified of the processing result as to whether or not the processing has ended normally.

  (6) When a packet based on a user click operation on the menu screen shown in FIG. 44, a user list screen shown in FIG. 66, and a click operation on the user edit screen shown in FIG. The user information DB 10 and the group information DB 12 are searched based on the user name associated with the user information DB 10 when the user has the access right to register / update / delete the user information DB 10. The user information is read, the packet including the screen data of the user list screen is transmitted, and the user information is registered / updated / deleted in the user information DB 10 together with the user name and the update date.

  (7) When a packet based on the click operation on the group list on the user list screen, the group list screen shown in FIG. 68 and the click operation on the group details screen shown in FIG. 69 is received from the terminal device 2, it is associated with the session. Based on the user name, the user information DB 100 and the group information DB 12 are searched. When the user has an access right to register / update / delete the group information DB 12, the group information DB 12 is searched and the group information DB 12 is searched. Information is read, a packet including screen data of the group list screen is transmitted, and group information is registered / updated / deleted in the group information DB 12.

  (8) When a request packet for design document output based on a click operation for design document output on the menu screen is received from the terminal device 2, the design information DB 8 is searched and system information, subsystem list, screen list, and table list are searched. A packet including screen data of the design document output screen shown in FIG. 70, in which table information for each table name, sub-application list information for each subsystem, and screen information for each sub-application can be selected separately by check boxes 2 to send.

  (9) Upon receiving the design document print request packet based on the click operation for executing the design document output screen shown in FIG. 70 from the terminal device 2, the design information DB 8 is searched and each item selected by the check box is displayed. Corresponding design information is read and written in a print file according to a predetermined layout and format. At this time, when it is necessary to create header information such as an updater and update date, the header information is created according to the layout of the print document and written into the print document file. When the creation of the print document file is completed, it is transferred to the terminal device 2.

  (10) When logoff is designated by the screen operation of the terminal device 2, the session is released.

  The design information DB 8 in FIG. 1 stores system information, subsystem information, sub application information, screen information, table information, item dictionary information, and message information design information. Here, the design information includes a design document created by a document creation tool or a table creation tool, an image image of a screen layout, and the like.

  The user information DB 10 is for storing user information regarding each user, and stores user information such as a user name, a login ID, a password, and an e-mail address. The group information DB 12 groups persons who have the right to access the design information DB 8, such as administrators and developers, according to roles, for example, and the administrator authority, development authority, and login for each group. This is a database for setting access rights such as authority, reference authority and review authority.

  Hereinafter, functions of the repository management server 6 will be described in detail. FIG. 2 is a functional block diagram of the repository management server 6 in FIG. As shown in FIG. 2, the repository management server 6 includes a packet reception unit 13, a packet transmission unit 14, an input data extraction unit 15, an output data editing unit 16, an authentication unit 18, an access right check unit 20, and a menu screen generation unit 22. , System information access unit 24, subsystem information access unit 26, sub application information access unit 28, screen information access unit 30, table information access unit 32, item dictionary access unit 34, message information access unit 36, print file creation unit 38, etc. Have

  The packet receiving unit 13 receives a request packet based on HTPP including data described in HTML from the terminal device 2. Based on the request from the terminal device 2, the packet transmission unit 14 transmits to the terminal device 2 a response packet including data edited in the screen data of the screen corresponding to the design data based on HTML according to HTTP.

  The input data extracting unit 15 generates information related to the click operation of the user's button from the data described in HTML included in the request packet from the terminal device 2, the link information related to the click operation to the link, and the click operation. A program (for example, in Java (registered trademark) script, as a link information, href = javascript: trigger JavaScript program name (argument (screen ID, etc.)) and setting Is operated, the set data, the design information input by the user, the information checked by the check box, and the design information transmitted by the repository management server 6 (for example, in HTML, the hidden value, for example, impu type = “hidden” id = “xxx” value = “AAA” etc.) and information related to design information to be referred / updated / deleted transmitted from the terminal device 2 (selected) (Folder ID, subsystem ID, sub-application ID, screen ID, etc. information) specifying a folder, subsystem, sub-application, screen layout screen, etc. are extracted.

  For example, when updating subsystem information / sub-application information / screen layout information / table information, etc., a subsystem ID / sub-application ID / screen ID / table for specifying a subsystem / sub-application / screen / table to be updated This is because a number is required. If a subsystem or the like can be specified, a number assigned by the system such as a subsystem ID may be used, or a code, name, ID, or the like input by a designer. Below, the case where system ID etc. are provided in the system is demonstrated to an example.

  In addition, by associating the selected system ID, subsystem ID, sub application ID, and the like with the session, for example, on the screen layout screen, by using the sub application ID associated with the session, the setting by hidden is omitted. Can do.

  The output data editing unit 16 includes a system information access unit 24, a subsystem information access unit 26, a sub application information access unit 28, a screen information access unit 30, a table information access unit 32, an item dictionary access unit 34, a message information access unit 36, and Based on the design template output from the print file creation unit 38, the screen data is edited into screen data according to HTML. The screen data includes design information displayed on the terminal device 2, information defining the button, information defining a check box that enables selection of each row displayed in the list of subsystems, link information, hidden value, and the like. And a program (such as Javascript) that operates with a click operation as a trigger for generating an event. The authentication unit 18 has the following functions.

  (1) When the URL of the repository management server 6 from the terminal device 2 is specified and a request packet for access to the repository management server 6 is received, authentication request screen data requesting input of a user ID and password described in HTML Is output to the packet transmitter 14.

  (2) When the user ID and password transmitted from the terminal device 2 and extracted by the input data extraction unit 15 are input, the user information DB 10 and the group information DB 12 are searched, and the input user ID and password are the user. If it is registered in the information DB 10 and the right to log in to the group to which the user belongs is determined, it is determined that the authentication has been performed normally, and the menu screen generation unit 22 is instructed to generate a menu screen. If the user has the right to log in to the repository management server 6, the session and login ID are associated with each other and related information is registered in the session management table. Which group the user belongs to may be registered in the user information DB 10 or may be set through Active Directory.

  The access right check unit 20 searches the user information DB 10 and the group information DB 12 based on the login ID associated with the session, and is given the right to access the design information DB 8 to the group to which the user with the login ID belongs. It is determined whether or not. If you have the right to access, allow access. If you do not have the right to access, deny access. The menu screen generation unit 22 generates screen data of the menu screen shown in FIG. 44 based on HTML and outputs the screen data to the packet transmission unit 14. The screen data of the menu screen includes the URL of the corresponding screen as each link information.

  The system information access unit 24 has the following functions.

  (1) When the system is clicked on the main menu screen or the like and the URL of the system information screen shown in FIG. 45 is received, the access right check unit 20 searches the design information DB 8 when access is permitted to the user. System name, system code, a list of folder names for classifying documents related to the entire system, and system information such as the updater and update date of the system information, and the system ID for identifying the system information and system Based on this, the output data editing unit 16 is instructed to edit the screen data of the system information screen shown in FIG.

  (2) When the update button is clicked on the system information screen, in addition to the system information input from the terminal device 2 to the input field, the system ID (in the case of update) and the update operation on the system information screen Is transmitted. When access is permitted by the access right check unit 20, the system code, system name, remarks, and user (updater) associated with the session and update date entered by the designer and included in the request packet are designed. Register in the information DB8. At this time, a system ID for uniquely specifying the system code is assigned and registered in the design information DB 8 together with the information.

  When an update button or the like is clicked, the output data editing unit 16 receives a request packet including data specifying the selected system such as a URL indicating which click operation is performed on which screen and a system ID. Since the screen data (defined by hidden, button definition, etc.) is edited so as to be transmitted from, the processing contents on the repository management server 6 side, that is, the data extracted by the input data extraction unit 15, that is, A processing program is identified. When a system, subsystem, or the like is clicked, the URL of the corresponding screen is set as link information, and the screen to be edited at that time is specified.

  (3) When a folder is clicked on the system information screen, when access is permitted to the user by the access right check unit 20, based on the system ID and the URL of the system information screen as link information + folder ID, The design information DB 8 is searched and a list of document information belonging to the designated folder is output together with the system name, system code, and remarks, and the system information, system ID, selected folder ID, and document name of each line are output. Based on the document ID as the link information and the document ID of each line, the output data editing unit 16 is instructed to edit the system information screen data including the definition of a check box that enables selection of each line.

  (4) When the folder creation button is clicked on the system information screen, when the user is permitted access by the system access right check unit 20, when the user clicks based on the system ID included in the request packet The folder name set by the operation of the JavaScript program is registered in the design information DB 8 and a folder specified by the folder name is created. At this time, a folder ID is assigned and registered in the design information DB 8.

  (5) When the folder deletion button is clicked on the system information screen, when access is permitted by the user from the access right check unit 20, the selected system ID included in the request packet from the terminal device 2 and Based on the folder ID, the document information belonging to the corresponding folder is deleted from the design information DB 8, and the folder corresponding to the folder ID and the document file belonging to the folder are deleted.

  (6) When the add button is clicked on the system information screen, the system ID set by Javascript and the folder ID of the selected folder are output, and the documents belonging to the folder are registered based on these information The output data editing unit 16 is instructed to edit the screen data of a document registration screen (upload screen) for (upload).

  (7) When the registration button is clicked on the document registration screen, when access is permitted by the access right check unit 20, the system ID, folder ID, document ID (in case of update), system ID and folder ID In addition to uploading the document from the terminal device 2 to the folder having the folder name corresponding to the document information, the document information such as the document name, file type and file size, and the updater and update date corresponding to the user ID associated with the session are designated in the design information DB 8. Register with. In the case of new registration, a document ID is given and registered in the design information DB 8.

  (8) When the delete button is clicked on the system information screen, when the user is permitted access by the access right check unit 20, the selection is checked in the check box set in each row of the document name list. Corresponding document information is deleted from the design information DB 8 based on the system ID, the selected folder ID, and the document ID, and corresponds to the document ID stored in the folder corresponding to the system ID and folder ID. Delete the document file to be used.

  (9) When the document name is clicked on the system information screen, when the user is permitted access by the access right check unit 20, the document is based on the system ID, the folder ID, and the document ID as the link information. The file is read and transferred to the terminal device 2.

  As shown in FIG. 3, the subsystem information access unit 26 includes a subsystem information reference generation unit 40 and a subsystem list generation unit 42. The subsystem information reference generation unit 40 has the following functions.

  (1) When the update button is clicked on the subsystem information screen shown in FIG. 47, when access is permitted by the user from the access right check unit 20, the same as when the update is clicked on the system information screen In addition, the subsystem ID (other than 0 for update, 0 for additional registration), subsystem code, subsystem name and remarks, and the updater and update date associated with the session are set in the design information DB 8. Register with. In the case of new creation, a subsystem ID is assigned and registered in the design information DB 8.

  (2) When a folder is clicked on the subsystem information screen, when the user is permitted access by the access right check unit 20, it is specified in the same manner as when the folder is clicked on the system information screen. Each row can be selected based on the subsystem information such as a list of document information belonging to the folder, the subsystem ID, the selected folder ID, the document ID as the link information of the document name of each row, and the document ID of each row. The output data editing unit 16 is instructed to edit the subsystem information screen data including the definition of the check box.

  (3) The processing when the folder creation button is clicked on the subsystem information screen is the same as when the folder creation button is clicked on the system information screen, just by replacing the system ID with the subsystem ID.

  (4) The processing when the folder deletion button is clicked on the subsystem information screen is the same as that when the folder deletion button is clicked on the system information screen only by changing the system ID to the subsystem ID.

  (5) The processing when the add button is clicked on the subsystem information screen is the same as when the add button is clicked on the system information screen only by changing the system ID to the subsystem ID.

  (6) The processing when the registration button is clicked on the document registration screen is the same as when the registration button is clicked on the system information screen, only the system ID is replaced with the subsystem ID.

  (7) The processing when the delete button is clicked on the subsystem information screen is the same as that when the delete button is clicked on the system information screen only by changing the system ID to the subsystem ID.

  (8) The processing when the document is clicked on the subsystem information screen is the same as when the document is clicked on the system information screen only by changing the system ID to the subsystem ID.

  (9) When the back button is clicked on the subsystem information screen, the design information DB 8 is searched based on the system ID, and a list of system names, system codes, subsystem names, subsystem codes, and remarks is displayed. Based on these information, the system ID, the subsystem ID of each row, the subsystem ID as the link information of the subsystem name of each row, and the Javascript program name of the trigger, the definition of a check box that enables selection of each row is defined. The output data editing unit 16 is instructed to edit the subsystem list screen data shown in FIG.

  (10) When the add button is clicked on the subsystem list screen, the output data editing is performed so that the subsystem information screen data is edited based on the system ID and the subsystem ID (= 0) set by Javascript. The unit 16 is instructed.

  (11) When the delete button is clicked on the subsystem list screen, when the user is permitted access by the access right check unit 20, the deletion is selected from the check boxes set in each row of the subsystem name list. The corresponding subsystem information is deleted from the design information DB 8 based on the checked subsystem ID.

  (12) When the subsystem name is clicked on the subsystem list screen, when the user is permitted access by the access right check unit 20, the JavaScript is operated and the subsystem ID set based on the link information The design information DB 8 is searched based on the system name, the system code, the corresponding subsystem name, the subsystem code and remarks, the updater and the update date, and the information, system ID and subsystem are output. Based on the ID, the output data editing unit 16 is instructed to edit the subsystem information screen data.

  The subsystem list generation unit 42 has the following functions.

  When the subsystem information is clicked on the menu screen or the like, when the user is permitted access by the access right check unit 20, the design information DB 8 is searched and the subsystem consisting of the subsystem name, subsystem code and remarks is searched. Output a list of system information, select each row based on this information, system ID, subsystem ID as link information of subsystem name of each row + trigger JavaScript program name, and subsystem ID of each row subsystem The output data editing unit 16 is instructed to edit the subsystem list screen data shown in FIG. 46 including the definition of the check box to be enabled.

  As shown in FIG. 4, the sub application information access unit 28 includes a sub application information reference generation unit 50 and a sub application list generation 52. The sub application information reference generation unit 50 has the following functions.

  (1) When the update button is clicked on the sub application information screen shown in FIG. 49, when access is permitted by the access right check unit 20, the subsystem ID and sub application ID (= 0) (new registration In other words, the sub application code, the sub application name and remarks, the updater associated with the session, and the update date are registered in the design information DB 8 based on the subsystem ID and the subsystem ID to which the sub application belongs (in the case of updating). In the case of new registration, a sub application ID is assigned and registered in the design information DB 8.

  (2) When a folder is clicked on the sub-application information screen, when access is permitted by the user from the access right check unit 20, it is designated in the same manner as when the folder is clicked on the system information screen. Each row can be selected based on the sub-application information such as a list of document information belonging to the folder, the subsystem ID, the sub-application ID, the selected folder ID, the document ID as the link information of the document name of each row, and the document ID of each row. The output data editing unit 16 is instructed to edit the sub application information screen data including the definition of the check box to be checked.

  (3) The processing when the folder creation button is clicked on the sub-application information screen is the same as when the folder creation button is clicked on the system information screen just by replacing the system ID with the sub-application ID.

  (4) The processing when the folder deletion button is clicked on the sub application information screen is the same as that when the folder deletion button is clicked on the system information screen only by changing the system ID to the subsystem ID.

  (5) The processing when the add button is clicked on the sub-application information screen is the same as when the add button is clicked on the system information screen only by changing the system ID to the sub-app ID.

  (6) The processing when the registration button is clicked on the document registration screen is the same as when the registration button on the document registration screen for system information is clicked only by changing the system ID to the subsystem ID.

  (7) The processing when the delete button is clicked on the sub-application information screen is the same as when the folder creation button is clicked on the system information screen just by replacing the system ID with the sub-application ID.

  (8) The processing when the document is clicked on the sub application information screen is the same as when the document is clicked on the system information screen only by changing the system ID to the subsystem ID.

  (9) When the back button is clicked on the sub application information screen, the design information DB 8 is searched based on the subsystem ID, and the system name, system code, selected subsystem name, and subsystem name are searched. A list of subsystem names and a list of sub application codes, sub application names, and remarks are output so that they can be selected. These information, subsystem ID, sub application ID of each row, and sub application ID as link information of the subsystem name of each row Based on the above, the output data editing unit 16 is instructed to edit the subsystem list screen data shown in FIG. 48 including the definition of a check box that enables selection of each row.

  (10) When the add button is clicked on the sub application list screen, the output data editing unit 16 is configured to edit the sub application information screen data based on the subsystem ID and the sub application ID (= 0) set by Javascript. To instruct.

  (11) When the delete button is clicked on the sub application list screen, when access is permitted by the access right check unit 20, the deletion check is performed in the check box set in each row of the sub application name list. The corresponding sub application information is deleted from the design information DB 8 based on the subsystem application ID that has been set.

  (12) When a sub application name is clicked on the sub application list screen, when access is permitted to the user by the access right check unit 20, Javascript operates and based on the sub application ID set based on the link information. The design information DB 8 is searched, and the system name, system code, subsystem name, subsystem code, corresponding sub application code, sub application name and remarks, and the updater and the update date are output. Based on the above, the output data editing unit 16 is instructed to edit the sub application information screen data.

  The sub application list generation unit 52 has the following functions.

  (1) When the sub application information is clicked on the sub system information screen, when the user is permitted access by the access right check unit 20, the design information DB 8 is searched and the system name, the system code, and the selection are selected. Output a list of subsystem names and sub-app codes, sub-app names and remarks so that the sub-system name and subsystem name can be selected, and this information, subsystem ID, sub-app ID of each row, sub of each row Based on the sub application ID as the system name link information + the JavaScript program name of the trigger, the output data editing unit 16 is instructed to edit the subsystem list screen data including the definition of a check box that enables selection of each row.

  (2) When the search button is clicked on the sub application list screen, when access is permitted by the access right check unit 20, the design information DB 8 is searched based on the selected subsystem name, The system name, system code, selected subsystem name, subsystem name list and sub application code, sub application name and remark list are output so that the subsystem name can be selected. Based on the sub application ID of each row and the sub application ID as the link information of the subsystem name of each row, the output data editing unit 16 edits the subsystem list screen data including the definition of a check box that enables selection of each row. To instruct.

  As shown in FIG. 5, the screen information access unit 30 includes a screen layout information reference generation unit 60, an action information reference generation unit 62, a screen item information reference generation unit 64, a screen table information reference generation unit 66, and a test case information reference generation. Unit 68, document information reference generation unit 70, screen list generation unit 72, screen transition diagram generation unit 74, and table relation diagram generation unit 76.

  The screen layout information reference generation unit 60 has the following functions.

  (1) When a screen ID is clicked on the screen list screen, when an access right is granted to the user by the access right check unit 20, based on the screen ID that identifies the screen as link information of the screen ID, Search the design information DB 8 to select a system name, a system code, a subsystem name, a subsystem code, a sub application name, a sub application code, a subsystem name and a sub application name, and a list of subsystem names and sub application names, and corresponding Output a list of action information such as name, ID, type, trigger item, transition destination, and condition for the screen ID, screen name, screen type, purpose of use and processing contents, screen of the screen ID Information, screen ID, screen image file name, URL as screen image link information, action 51. The screen layout screen data shown in FIG. 51 including the definition of a check box that enables selection of each row is edited based on the action number as the link information of the action ID of the list + the JavaScript program name of the trigger and the action number of each row. To the output data editing unit 16. When a screen file name is specified by the terminal device 2 and a screen read request is made, the requested screen image is read. When an image in the screen layout screen is clicked, an HTML file of an image linked to the screen image is read.

  (2) When the update button is clicked on the screen layout screen, when access is permitted by the access right check unit 20, the screen ID (in case of update) or the selected subsystem name and sub application name ( In the case of new registration), the screen layout information including the screen ID, the screen name, the screen type, the purpose of use, and the processing content, and the updater and update date associated with the session are registered in the design information DB 8. In the case of new registration, a screen ID is assigned and registered in the design information DB 8.

  (3) When the return button is clicked on the screen layout screen, when access is permitted by the user from the access right check unit 20, the return click operation is performed on the screen layout screen. Search the design information DB 8 and edit the output data to edit the screen data of the screen list screen based on the list of subsystem names and sub application names that can select the system name, system code, subsystem name, and sub application name. To the unit 16. Note that the design information DB 8 may be searched based on the sub application ID of the sub application to which the screen corresponding to the screen ID of the screen layout screen belongs, and the screen list screen may be output.

  (4) When the new creation button is clicked on the screen list screen, the design information DB 8 is searched and the system name, system code, subsystem name, subsystem code, sub application name, sub application code, subsystem name, and Based on the list of subsystem names and sub-application names that allow selection of the sub-app name, the output is output to the output data editing unit 16 so as to edit the screen layout screen data.

  (5) When the delete button is clicked on the screen list screen, when the user is permitted access by the access right check unit 20, the deletion is performed in the check box set in each line of the screen name list. Based on the checked screen ID, the screen information of the corresponding screen is deleted from the design information DB 8.

  The action information reference generation unit 62 has the following functions.

  (1) When an action ID is clicked on the action list screen or screen layout screen, when access is permitted by the access right check unit 20, the screen ID and trigger JavaScript are set based on the link information. The setting information DB 8 is searched based on the action number, the action information corresponding to the screen ID and the action number is output, and edited to the screen action editing screen data based on the action information, the screen ID and the action number. The output data editing unit 16 is instructed.

  (2) When the registration button is clicked on the screen action editing screen, when the user is allowed access by the access right check unit 20, in the case of additional conditions, the screen is based on the screen ID and action number. The action information related to the condition addition entered on the action edit screen, the updater associated with the session, and the update date are additionally registered in the design information DB 8, and in the case of addition, on the screen action edit screen based on the screen ID. The action information related to the added addition, the updater associated with the session, and the update date are registered in the design information DB 8, and in the case of update, the action updated on the screen action edit screen based on the screen ID and action number Design information D indicating the updater and update date associated with the information and session To update to 8. In the case of new registration, an action number is assigned and registered in the design information DB 8.

  (3) When the add condition button is clicked on the screen action list screen or the screen layout screen, when access is permitted to the user by the access right check unit 20, the screen ID and action of the selected screen layout Based on the action number checked in the check box of the list, the design information DB 8 is searched, and action information such as name, ID, type, trigger item and condition is output for the action corresponding to the action ID. The output data editing unit 16 is instructed to edit the screen action editing screen data based on the action information, the screen ID, and the action number.

  (4) When the add button is clicked on the screen action list screen or the screen layout screen, the output data editing unit 16 is instructed to edit the action editing screen data based on the selected screen ID. .

  (5) When the delete button is clicked on the screen action list screen or the screen layout screen, when the user is permitted access by the access right check unit 20, the screen ID and action of the selected screen layout screen are displayed. Based on the action number checked in the check box in the list, the action information corresponding to the action number is deleted from the design information DB 8.

  The screen item information reference generation unit 64 has the following functions.

  (1) When the screen item list is clicked on the screen layout information screen and the URL of the screen item list screen shown in FIG. 53 is received, the screen is displayed when the access right check unit 20 permits the user to access. Based on the ID, the design information DB 8 is searched, and the presence / absence of dictionary item cooperation of the screen item of the screen layout screen corresponding to the screen ID, name, ID, object type, display type, input / output, number of display digits, and display line List of screen item information of the number, the updater and the update date, and the screen item number as the link information of the screen item number, the screen item number of each screen item and the item name of each row + trigger An action (not shown) including the definition of a check box that enables selection of each line of a screen item based on the Javascript program name. As edited down edit screen data, it instructs the output data editing unit 16.

  (2) When an item name is clicked on the screen item list screen, when the user is permitted access by the access right check unit 20, the item name set based on the link information by the screen ID and Javascript is displayed. Based on the screen item number, the design information DB 8 is searched, and screen item information corresponding to the screen item number of the screen corresponding to the screen ID is output. These screen item information, screen ID, screen item number, dictionary As for the link, the output data editing unit 16 is instructed to edit the screen item editing screen data based on the screen program number + trigger JavaScript program name as link information.

  (3) When the add button is clicked on the screen item list screen, the screen ID of the selected screen layout screen, and the dictionary linkage, the screen information is based on the screen item number + trigger Javascript program name as link information. The output data editing unit 16 is instructed to edit the item editing screen data.

  (4) When the delete button is clicked on the screen item list screen, when the user is permitted access by the access right check unit 20, the screen ID of the selected screen layout screen and the screen item list are checked. Based on the screen item number checked in the box, the screen item information corresponding to the screen item number of the screen corresponding to the screen ID is deleted from the design information DB 8.

  (5) When dictionary linkage is clicked on the screen item edit screen, when access is permitted by the access right check unit 20, the screen item number set by Javascript based on the link information + item reference Based on the URL of the screen, the design information DB 8 is searched, and a list of item dictionary information is output. The item dictionary number + trigger Javascript is used as link information for the name of the item dictionary that is not linked to this list. Based on the program name, the output data editing unit 16 is instructed to edit the item reference screen data. Thereby, the item dictionary in which the screen items are dictionary-linked can be confirmed by the presence or absence of the link information. When an item name is clicked on the item reference screen, JavaScript operates, and an item dictionary number to be linked to the dictionary on the screen item editing screen that is the parent screen is set as dictionary linkage information. At this time, it is determined whether or not each item dictionary is associated with the column by searching the item use table information in the setting information DB 8.

  (6) When the update button is clicked on the screen item edit screen, when access is permitted by the access right check unit 20, the screen ID (in the case of new registration) or the screen ID and screen item number ( Screen item information including presence / absence of dictionary cooperation (item dictionary number for dictionary cooperation in the case of dictionary cooperation) entered on the screen item editing screen, as well as the updater and update date associated with the session Is updated / added to the design information DB 8. If dictionary linkage is set for the screen item, the screen ID, the screen name, and the item use screen information of the item dictionary name are registered in the design information DB 8. In the case of new registration, a screen item number is assigned and registered in the design information DB 8.

  The screen table information reference generation unit 66 has the following functions.

  (1) When the table list is clicked on the screen layout information screen or the like and the URL of the screen table list screen shown in FIG. 56 is received, when the user is permitted access by the access right check unit 20, the screen ID is set. Based on this, the design information DB 8 is searched, and the table name, table ID, presence / absence of reference, presence / absence of registration, presence / absence of update, and presence / absence of deletion of the screen table information corresponding to the screen ID And a list of screen table information of the updater and update date are output, and each row is selected based on the screen table number + trigger Javascript program name and table number of each row as link information of the list information and table name Screen table list with definition of check boxes to be enabled As edited data, it instructs the output data editing unit 16.

  (2) When the table name is clicked on the screen table list screen, when the user is permitted access by the access right check unit 20, the screen ID and the screen table number set based on the link information by Javascript are set. Based on this, the design information DB 8 is searched, a table name corresponding to the screen table number and a list of table names enabling selection of each table name are output, and based on these information, screen ID and screen table number, The output data editing unit 16 is instructed to edit screen table editing screen data (not shown).

  (3) When the add button is clicked on the screen table list screen, the output data editing unit 16 is instructed to edit the screen table editing screen data based on the screen ID of the selected screen layout. .

  (4) When the delete button is clicked on the screen table list screen, when the user is permitted access by the access right check unit 20, the screen ID of the selected screen layout and the check box of the screen table list are displayed. The corresponding screen table information is deleted from the design information DB 8 on the basis of the screen table number checked in FIG.

  (5) When the update button is clicked on the screen table edit screen, when access is permitted by the access right check unit 20, the screen ID (in the case of new registration) or the screen ID and screen table number ( In the case of updating), the screen table information input on the screen table editing screen, the updater associated with the session, and the update date are registered / updated in the design information DB 8. In the case of new registration, a screen table number is assigned and registered in the design information DB 8.

  The test case information reference generation unit 68 has the following functions.

  (1) When the test case list is clicked on the screen layout information screen or the like and the URL of the screen test case list screen shown in FIG. 58 is received, the screen is displayed when access is permitted by the access right check unit 20 to the user. Based on the ID, the design information DB 8 is searched, and the action name, case number, test content, assumed result and execution date as the screen test case information for the screen layout corresponding to the screen ID, the updater, and the update date screen Output test case list information, and define a check box that enables selection of each row based on this information, test case number as link information of test number + Javascript program name of trigger and test case number of each row Including screen test case list screen data shown in FIG. As editing, it instructs the output data editing unit 16.

  (2) When a test number is clicked on the screen test case list screen, the screen test case set by Javascript based on the screen ID and link information when the user is permitted access by the access right check unit 20 The design information DB 8 is searched based on the number, the screen test case information corresponding to the test case number is output, and the screen test case editing screen is based on the screen test case information, the screen ID, and the test case number. The output data editing unit 16 is instructed to edit the data.

  (3) When the add button is clicked on the screen test case list screen, the output data editing unit 16 is instructed to edit the screen test case edit screen data based on the selected screen ID.

  (4) When the delete button is clicked on the screen test case list screen, when access is permitted by the access right checking unit 20, the screen ID of the selected screen layout and the screen test case list are displayed. Based on the test case number checked in the check box, the screen test case information corresponding to the test case number is deleted from the design information DB 8.

  (5) When the update button is clicked on the screen test case edit screen, when access is permitted by the access right check unit 20, the screen ID (in the case of new registration) or the screen ID and the test case number Based on (in the case of update), the screen test case information input on the screen test case edit screen, the updater associated with the session, and the update date are registered / updated in the design information DB 8. In the case of new registration, a screen test case number is assigned and registered in the design information DB 8.

  The document information reference generation unit 70 has the following functions.

  (1) When the document list is clicked on the screen layout information screen or the like and the URL of the document list screen shown in FIG. 59 is received, when access is permitted by the access right check unit 20, the screen ID is used. The design information DB 8 is searched to output the document name, file type, file size and list information of the screen document of the updater and the update date for the screen layout corresponding to the screen ID. 59. The output data so as to be edited into the screen document list screen data shown in FIG. 59 including the definition of a check box that enables selection of each row based on the document ID as the link information of the document + the JavaScript program name of the trigger and the document ID of each row. Editorial department 16 It instructs.

  (2) When a document name is clicked on the screen document list screen, when access is permitted to the user by the access right check unit 20, based on the screen document ID set based on the link information by Javascript, The design information DB 8 is searched, the screen document information is output, and the output data editing unit 16 is instructed to edit the screen document editing screen data (not shown) based on the screen ID and the screen document ID.

  (3) When the add button is clicked on the screen document list screen, the output data editing unit 16 is instructed to edit the screen document editing screen data (not shown) based on the selected screen ID.

  (4) When the delete button is clicked on the screen document list screen, when the user is permitted access by the access right check unit 20, the screen ID of the selected screen layout and the check box of the screen document list are displayed. The screen document information corresponding to the screen document ID is deleted from the design information DB 8 on the basis of the screen document ID checked in FIG.

  (5) When the update button is clicked on the screen document editing screen, when the user is permitted access by the access right check unit 20, the screen ID (in the case of new registration) or the screen ID and the screen document ID ( In the case of updating), the screen document information input on the screen document editing screen, the updater associated with the session, and the update date are registered / updated in the design information DB 8. In the case of new registration, a screen document ID is assigned and registered in the design information DB 8.

  The screen list generation unit 72 has the following functions.

  (1) When the screen information is clicked on the sub application information screen and the URL of the screen list screen is received, when the access right is granted to the user by the access right check unit 20, the design information DB 8 is stored based on the sub application ID. Search, system name, system code, subsystem name, subsystem code, sub-app name, list of selectable subsystem names and sub-app names, screen ID of screen layout belonging to sub-app, screen name, screen type, etc. FIG. 50 includes a definition of a check box that outputs a list of layout information and enables selection of each row based on the information, the screen ID as link information of the screen ID + the JavaScript program name of the trigger, and the screen ID of each row. To edit the screen list screen data shown in To instruct the force data editing unit 16. Even if the screen information is clicked on the sub-application information screen, etc., the sub-application ID is not inherited on the screen list screen, and the screen list is not displayed. It is also possible to display only a list of screens and display a screen list by search.

  (2) When the search button is clicked on the screen list screen, when the access permission check unit 20 permits the user to access the search, the selected subsystem name, sub application name, and last update date designation range The design information DB 8 is searched based on the system name, the system code, the subsystem name, the subsystem code, the subsystem name, the sub application code, the sub application name, and the update date within the specified range of the last update date. The corresponding screen layout information belonging to the sub-app is output, and a check box definition that enables selection of each row is defined based on the information, the screen ID as the link information of the screen ID, and the screen ID of the screen layout of each row. The output data editing unit 16 is instructed to edit the screen list including the screen list.

  The screen transition diagram generation unit 74 has the following functions.

  When the screen transition diagram is clicked on the screen layout information screen or the like, when access is permitted by the user from the access right check unit 20, the design information DB 8 is searched based on the selected screen ID, From the action information, the screen layout information (screen name, screen ID) of the screen corresponding to the screen ID, the screen layout information (screen name, screen ID) of the transition source screen that transitions to the screen corresponding to the screen ID, and the screen ID. Output the screen layout information (screen name, screen ID) of the transition destination screen that transitions from the corresponding screen, create an image based on this information, and edit it to the screen transition diagram screen data shown in FIG. The output data editing unit 16 is instructed to do so.

  The table relation diagram generation unit 76 has the following functions.

  When a table related diagram is clicked on the screen layout information screen or the like, when access is permitted by the user from the access right check unit 20, the design information DB 8 is searched based on the selected screen ID, From the screen table information, on the screen corresponding to the screen ID, output the name of the table to be referenced and the table to be updated, the table ID, create an image based on these information, and edit it to the screen table related diagram screen data The output data editing unit 16 is instructed to do so.

  As shown in FIG. 5, the table information access unit 32 includes a column information reference generation unit 80, an index information reference generation unit 82, a table information reference generation unit 84, a reference source screen information generation unit 86, and a table list generation unit 88. Have.

  The column information reference generation unit 80 has the following functions.

  (1) When a table ID is clicked on the table list screen or the like, when the user is permitted access by the access right check unit 20, the design information DB 8 is searched based on the table number as link information. Table ID of the table corresponding to the table number, table information such as table name, etc., and for each column of the table, list and update of item dictionary linkage, column ID, column name, presence of primary key, data type, etc. The table information, the table number, the column number of each row, and the dictionary linkage, as a link information, the row number can be selected based on the Javascript program name of the trigger check box The table information screen data shown in FIG. To, instructs the output data editing unit 16.

  (2) When new creation is clicked on the table list screen, the output data editing unit 16 is instructed to edit the table information screen data.

  (3) When the delete button is clicked on the table list screen, when access is permitted by the user from the access right check unit 20, based on the table number checked in the check box of the table list, The table information corresponding to the table number is deleted from the design information DB 8.

  (4) When a dictionary is clicked on the table information screen, when access is permitted by the access right check unit 20, the column number set by Javascript based on the link information + the item shown in FIG. Based on the URL of the screen, the design information DB 8 is searched, and a list of item dictionary information is output. The item dictionary number + Instructs the output data editing unit 16 to edit the item reference screen data based on the Javascript program name of the trigger. Thereby, it is possible to confirm the item dictionary in which the columns are linked to the dictionary by the presence or absence of the link information. When an item name is clicked on the item reference screen, JavaScript operates and an item dictionary number for dictionary cooperation is set as dictionary cooperation information for the column of the table information screen that is the parent screen. At this time, it is determined whether or not each item dictionary is dictionary-linked with the column by searching the item use table information in the design information DB 8.

  (5) When the update button is clicked on the table information screen, when access is permitted by the access right check unit 20, the table ID, the table name, and the remarks are based on the table number (in the case of update). Column information such as presence / absence of dictionary linkage, column ID, column name, presence / absence of primary key, etc. is registered / updated in the design information DB 8, and the column ID, Item usage table information of column names and item dictionary names is registered in the design information DB 8. When table information is newly registered, a table number and a column number are assigned and registered in the design information DB 8.

  (6) When the back button is clicked on the table information screen, the design information DB 8 is searched, and based on the operation on the table information screen, the system name, system code, subsystem name, sub A list of system codes and table information is output, and the information, table number of each row, table information screen URL as table ID link information + table number, and reference source are based on the table number as link information. The output data editing unit 16 is instructed to edit the table list screen data shown in FIG. 60 including the definition of a check box that enables selection of each row.

  The index information reference generation unit 82 refers to / creates / updates index information about a table and has the following functions.

  (1) When an index is clicked on the table information screen and a URL of an index information screen (not shown) is received, when access is permitted by the access right check unit 20, the design information DB 8 is stored based on the table number. It searches and outputs a system name, system code, table name, table ID, and remarks, and instructs the output data editing unit 16 to edit index information screen data (not shown) based on these information.

  (2) When the new creation button is clicked on the index information screen, when access is permitted by the access right check unit 20, the design information DB 8 is searched based on the table number, and the table number is set. Outputs a list of columns such as column ID and column name of the corresponding table, and an order number that enables selection of the index order for each column, and enables selection of each row based on this information and the column number of each row. The output data editing unit 16 is instructed to edit the index information screen data including the definition of the check box to be checked. In the index information screen, an index ID for a column whose order is designated as an index is displayed in a predetermined area, and when selected, index information such as an index ID and an index type is displayed in an input field. It has become.

  (3) When the delete button is clicked on the index information screen, when the user is permitted access by the access right check unit 20, the corresponding index information is deleted from the design information DB 8 based on the table number.

  (4) When the update button is clicked on the index information screen, when access is permitted to the user by the access right check unit 20, the order of the index is based on the table number and the column number selected by the check box. And index information such as an index ID is registered in the design information DB 8.

  The other table information reference generation unit 84 refers to, creates, and updates external reference information and SQL management information related to a table, and has the following functions.

  (1) When an external reference is clicked on the table information screen and a URL of an external reference information screen (not shown) is received, the external reference information screen data is instructed to be edited in the same manner as the index information screen. When a new creation button / delete button / update button is clicked on the external reference information screen, the design information DB 8 is accessed and a click operation on the index information screen according to the access right check of the access right check unit 20 Similarly, external reference information such as a reference name ID and a reference destination table name is newly created / deleted / updated for a column of a table to be externally referenced. In the external reference screen, a reference name ID for a column to be externally referenced is displayed in a predetermined area, and when selected, external reference information such as a reference name ID, a reference destination table name ID, and a reference destination table name is displayed. It is displayed in the input field.

  (2) When SQL management is clicked on the column information screen or the like and a URL of an SQL management screen (not shown) is received, when access is permitted by the access right check unit 20, the operation on the index information screen Similarly, based on the click operation of the new create button / delete button / update button, the design information DB 8 is accessed to newly create SQL management information such as the SQL name, SQL description, execution plan, and execution result related to SQL management. / Delete / update.

  The reference source screen information generation unit 86 has the following functions.

  When the reference source is clicked on the table list screen, the URL of the reference source screen shown in FIG. 61 and the table number shown in FIG. 61 set by Javascript based on the link information when the access right checking unit 20 permits the user to access. The design information DB 8 is searched based on the table ID, and a list of screen IDs, screen names, etc., for referring / creating / updating / deleting the table corresponding to the table number is output. The output data editing unit 16 is instructed to edit. Further, when a screen becomes a reference source of another table based on the screen table information, another table name is output.

  The table list generation unit 88 has the following functions.

  (1) When the table is clicked on the system information screen shown in FIG. 26 and the URL of the table list screen shown in FIG. 60 is received, when the user is permitted access by the access right check unit 20, the design information DB 8 To output a list of table information such as the presence or absence of a reference source screen based on the system name, system code, table ID of each table, table name, expected number of rows, table size and screen table information. Check that each row can be selected based on the information, the table number of the table of each row, the URL of the table list screen as the link information of the table ID + the table number and the table number as the link information of the reference source + the JavaScript program name of the trigger Table list screen data shown in FIG. 60 including box definitions As editing, it instructs the output data editing unit 16.

  (2) When a search is clicked on the table list screen, the design information DB 8 is stored based on the table ID and table name entered in the input field when access is permitted by the access right check unit 20 to the user. Search and output a list of table information of the corresponding table. These information, table number of each row table, table number as table ID link information, table number as reference source link information + trigger number Based on the Javascript program name, the output data editing unit 16 is instructed to edit the table list screen data including the definition of a check box that enables selection of each row.

  (3) When DDL generation is clicked on the table list screen, the output data editing unit 16 is instructed to edit the DDL output screen data based on the table ID and table name input in the input field, and the DDL output is performed. DDL is generated according to check items such as the schema description on the screen.

  As illustrated in FIG. 7, the item dictionary access unit 34 includes an item information reference generation unit 90, an item use screen information reference generation unit 92, and an item use table information reference generation unit 94.

  The item information reference generation unit 90 has the following functions.

  (1) When the dictionary is clicked on the main menu screen or the like and the URL of the item dictionary screen shown in FIG. 63 is received, the access right check unit 20 searches the design information DB 8 when the user is permitted access. , System code, system name, item name (sum), item name (English), type, number of digits, screen and list of item information such as DB, etc., these information, item dictionary number of each row, each row Based on the item dictionary number as the link information of the item name, the item dictionary number as the link information of the screen of each line + the Javascript program name of the trigger, the item dictionary number as the link information of the DB of each line + the Javascript program name of the trigger, The output data editing unit 16 is instructed to edit the item dictionary screen data. The screen is the number of screen items of the screen linked to the item in the dictionary, and the item use screen information in the design information DB 8 is searched to count the number of screen items linked to the item in the dictionary. The DB is the number of columns in the table linked to the item in the dictionary, and the item use table information in the design information DB 8 is searched to count the number of columns linked to the item in the dictionary.

  (2) When an item name (sum) is clicked on the item dictionary screen, when the user is permitted access by the access right check unit 20, the design information DB 8 is stored based on the item dictionary number as link information. Search and output item dictionary information such as system name, system code, item name (sum), item name (English), type and number of digits, and items not shown based on these information and item dictionary number The output data editing unit 16 is instructed to edit the dictionary editing screen data.

  (3) When the screen is clicked on the item dictionary screen, the URL + of the item dictionary object list set by Javascript based on the link information of the screen when the user is permitted access by the access right check unit 20 Based on the item dictionary number, the item use screen information in the design information DB 8 is searched, and the screen items (screen item ID, screen item name, type, etc.) of the screen (screen ID and screen name) linked with the item dictionary are dictionaryd. ) Is output, and the output data editing unit 16 is instructed to edit the item usage object list screen data shown in FIG. 64 based on the information.

  (4) When the DB is clicked on the item dictionary screen, when the user is permitted access by the access right check unit 20, the item usage column list screen set based on the DB link information by Javascript is displayed. Based on the URL + item dictionary number, the item use column information of the design information DB 8 is searched, and the columns (column ID, column item name, type, etc.) of the table (table ID and table name) linked to the item dictionary are dictionary-linked. A list is output, and the output data editing unit 16 is instructed to edit the item use column list screen data shown in FIG. 65 based on the information.

  (5) When a search is clicked on the item dictionary screen, when access is permitted by the access right check unit 20, the item name (sum) and item name (English) entered in the input field are used. Search the design information DB 8 and output item dictionary information (item name (sum), item name (english), type, screen, DB, etc.) that matches the item name (sum) and item name (english). Based on these, the output data editing unit 16 is instructed to edit the item dictionary screen data in the same manner as when the dictionary shown in (1) is clicked.

  (6) When duplicate item search (sum) / duplicate item search (English) is clicked on the item dictionary screen, when access is permitted by the access right check unit 20, the design information DB 8 is searched. , Item dictionary information (item name (sum), item name (english), type, etc., screen, DB, etc.) with duplicate item names (sum) / item names (english) is read out, and (1 The output data editing unit 16 is instructed to edit the item dictionary screen data in the same manner as when the dictionary shown in FIG.

  (7) When an unused item is clicked on the item dictionary screen, the access right check unit 20 searches the item use screen information and the item use table information in the design information DB 8 when access is permitted by the user. For each item, the number of screen items and the number of columns linked to the dictionary are counted, and the item dictionary information (item name (sum), item name (English), number of columns linked to the dictionary is 0), Type) is output, and based on these, the output data editing unit 16 is instructed to edit the item dictionary screen data.

  (8) When the add button is clicked on the item dictionary screen, the output data editing unit 16 is instructed to edit the item dictionary editing screen data (not shown).

  (9) When the delete button is clicked on the item dictionary screen, when access is permitted by the access right check unit 20, deletion is checked with the check box set in each line of the item dictionary name list. The item dictionary information is deleted from the design information DB 8 based on the item dictionary number of the item dictionary.

  (10) When the update button is clicked on the item dictionary edit screen, when access is permitted by the access right check unit 20, the item name (sum), based on the item dictionary number (in the case of update), Item name (English), type, number of digits, and detailed item dictionary information are added / updated to the design information DB 8. In the case of new registration, an item dictionary number is assigned and registered in the design information DB 8.

  When the registration button is clicked on the screen item editing screen or the item dictionary number is set as dictionary cooperation, the item use screen information reference generation unit 92 is based on the design information DB 8 based on the screen ID and the screen item number. The screen ID and screen name of the screen corresponding to the screen ID, the screen item ID and screen item name corresponding to the screen item number, and the item name corresponding to the item dictionary number are registered as item use screen information.

  When the update button is clicked on the table information screen, the item use table information reference generation unit 94 is designed based on the table number and the column number when the item dictionary number is set as dictionary cooperation for each column. In the information DB 8, a table ID and table name corresponding to the table number, a column ID and column name corresponding to the column number, and an item name corresponding to the item dictionary number are registered as item use table information.

  The message information access unit 36 in FIG. 2 has the following functions.

  (1) When a message is clicked on a menu screen or the like and a URL of a message list screen (not shown) is received, when access is permitted by the access right check unit 20, the design information DB 8 is searched for the message. Output a list of message information such as code, level and content, and based on this information, the message number of the message in each line, the message number as the link information of the message code in each line + the Javascript program name of the trigger, The output data editing unit 16 is instructed to edit the message list screen data (not shown) including the definition of the check box.

  (2) When the search button is clicked on the message list screen, when access is permitted by the access right check unit 20, the design information DB 8 is searched based on the code and level entered in the input field. Then, message information (code, level, contents) matching the code and level is output, and based on these, the output data editing unit 16 is configured to edit the message list screen data in the same manner as (1). Instruct.

  (3) When the file output button is clicked on the message list screen, when access is permitted by the access right checking unit 20, the Java property file is based on the message displayed in the message list. Create

  (4) When a new creation button is clicked on the message list screen, when access is permitted by the user from the access right check unit 20, the code, level, and content are edited into message definition screen data having input fields. Thus, the output data editing unit 16 is instructed.

  (5) When the delete button is clicked on the message list screen, when the user is permitted access by the access right check unit 20, deletion is checked in the check box set in each line of the message list. The message information is deleted from the design information DB 8 based on the message number of the message.

  (6) When registration is clicked on the message definition screen, when access is permitted to the user by the access right check unit 20, the message information of the code, level, and content is based on the message number (in the case of update). Is registered in the design information DB 8. In the case of new registration of a message, a message number is assigned and registered in the design information DB 8.

  (7) When a code is clicked on the message list screen, when access is permitted to the user by the access right check unit 20, setting information is set based on the message number set based on the link information by Javascript. The DB 8 is searched, the code, level, and contents are output, and the output data editing unit 16 is instructed to edit the message definition screen data based on the message number.

  The print file creation unit 38 has the following functions.

  (1) When the design document output is clicked on the menu screen, when the user is permitted access by the access right check unit 20, the design information DB 8 is searched and the system name, table name list, subsystem Name, sub application name for the subsystem, and screen name for the sub application are output, and based on these information, system information, table information of each table, message list, item dictionary information, sub application list, and each screen 70, including screen layout information, screen action information, screen item information, screen table list, screen table related diagrams, and the definition of check boxes that allow design document output formats to be selected. The output data editing unit 16 is instructed to do so.

  (2) When the execution button is clicked on the design document print screen, the access right check unit 20 searches the design information DB 8 when the user is permitted to access the item chucked by the check box. Then, header information such as an updater and update date is created, the corresponding design information DB 8 is searched according to each item, and the following processing is performed.

  (A) In the case of system information, a list of system name, system code, and document information (folder name, document name, file type, file size) related to the system is output according to the print output format specified by the layout and check box. .

  (B) In the case of a subsystem list, layout and printing of subsystem information such as subsystem code, subsystem name, remarks, and a list of documents (folder name, document name, file type, file size) related to the subsystem Output according to the output format.

  (C) In the case of a screen list, for each sub application name and sub application code, a screen list of screen ID, screen item, screen name, screen type, usage purpose and processing content is output according to the layout and output format.

  (D) In the case of a table list, a table list such as a table ID, a table name, an estimated number of rows, and a table size is output according to the print output format specified by the layout and check box.

  (E) For a table, table information such as table ID, table name and remarks, presence / absence of dictionary linkage, column information such as column ID and column name, list of reference source screens such as screen ID and name, index Information, external reference information, and SQL management information are output according to the print output format specified by the layout and check boxes.

  (F) In the case of an item dictionary, a list of item dictionary information such as item name, type, number of screens, number of DBs, etc., item use screens such as screen ID, screen name, screen item name, screen item ID, etc. for each item dictionary A list of information and a list of column information used for items such as table ID, table name, column name, column ID, etc. are output according to the print output format specified by the layout and check box.

  (G) In the case of a sub-application list, the system name, system code, subsystem name, subsystem code, each sub-application name, sub-application code, and document information related to the sub-application (folder name, document name, file type, file size) are laid out And output according to the print output format specified by the check box.

  (H) For screens, for each screen layout, screen layout information such as subsystem name, sub-app name, screen ID, screen name, screen type, and screen image, for screen actions, action list, screen In the case of items, a list of screen item information such as presence / absence of dictionary cooperation, screen item names, screen item IDs, etc. In the case of screen transition diagrams, the screen ID and screen name of the transition source screen, the screen ID and screen name of the transition destination Based on the above, create an image image of the screen transition diagram, and in the case of a screen table, create an image image of the table-related diagram and / or screen table list that the screen references / registers / updates / deletes, and specify it in the check box According to the printed output format.

  8 to 22 are diagrams showing logical structures of databases of the design information DB 8, the user information DB 10, and the group information DB 12 in FIG. As shown in FIG. 8, the design information DB 8 includes a system document DB 100 that stores documents related to the system, and a subsystem document DB 102 # i (i = i =) that stores documents related to subsystems obtained by dividing the system into a plurality of subsystems. 1 to n and i are the number of subsystems), and each sub-application document DB 104 # ij (i = 1 to n, j = 1 to n, j is a document storing a document related to a sub-application divided into a plurality of sub-applications. Screen document / image DB 106 ijk (i = 1 to n, j = 1 to n, k = 1 to n, k is stored in the sub application). Number of screens), system information DB 107 for storing system information, subsystem information DB 108 for storing subsystem information, sub Sabuapuri information DB110 for storing pre-information, the screen information DB112 for storing screen information, table information DB114 for storing table information, including message information DB118 for storing item dictionary information DB116 and message information storing item dictionary information.

  As shown in FIG. 9, the screen information DB 112 includes a screen layout information DB 130 for storing screen layout information, an action information DB 132 for storing action information, a screen item information DB 134 for storing screen item information, and a screen for storing screen table information. It includes a table information DB 136, a test case DB 138 for storing test cases, and a document information DB 139 for storing document information.

  As shown in FIG. 10, the item dictionary information DB 116 includes an item dictionary DB 140 that stores an item dictionary, an item use screen information DB 142 that stores item use screen information, and an item use table information DB 144 that stores item use table information.

  As shown in FIG. 11, the system information DB 107 includes a system name, a system code, and a document file name ij related to the system (i = 1 to n, j = 1 to n, i is the number of folders, and j is a folder number). The number of document files to which the user belongs and the folder name i (i = 1 to n, i is the number of folders), the updater, and system information of the update date are stored. A system ID that uniquely identifies a system name or a folder ID that identifies a folder may be assigned and stored in the system information DB 107 as system information. The document file may have a one-to-one or one-to-n (n ≧ 2) folder name.

  As shown in FIG. 12, the subsystem information DB 108 includes a system name, a subsystem name i (i = 1 to n, i is the number of subsystems), a subsystem code i (i = 1 to n), and a subsystem. Document file name ijk related to (i = 1 to n, j = 1 to n, k = 1 to n, j is the number of folders belonging to each subsystem, k is the number of document files belonging to each folder) and folder name ij (i = 1 to n, j = 1 to n), updater and update date subsystem information are stored. In the case of new registration of a subsystem, a subsystem ID that uniquely identifies each subsystem name or a folder ID that identifies a folder may be assigned and stored in the subsystem information DB 108 as subsystem information.

  As shown in FIG. 13, the sub application information DB 110 includes a subsystem name i (i = 1 to n, i is the number of subsystems), and a sub application name ij (i = 1 to n, j = 1 to n, j The number of sub-apps belonging to each sub-system), document file names ijkl (i = 1 to n, j = 1 to n, k = 1 to n, l = 1 to n, k) associated with the sub-apps Number, l is the number of document files belonging to each folder) and folder name ijk (i = 1 to n, j = 1 to n, k = 1 to n, l = 1 to n), updater and update date The sub application information is stored. In the case of new registration of a sub application, a sub application ID for specifying each sub application name or a folder ID for specifying a folder may be assigned and stored in the sub application information DB 108 as sub application information.

  As shown in FIG. 14, in the screen layout information DB 130, for each screen, the subsystem name, sub-app name, screen name, screen ID, screen type (normal screen / pop-up screen) to which the screen belongs, usage purpose, processing content, The screen layout information including the updater and the update date is stored. In the case of new registration, a screen ID that uniquely identifies each screen in the system may be assigned and stored in the screen layout information DB 130 as screen layout information.

  As shown in FIG. 15, in the action information DB 132, for each screen, the subsystem name to which the screen belongs, the sub application name, the screen name, the screen ID, and the action name i (i = 1 to n, i are the actions of the screen) Number), action IDi (i = 1 to n), type (own screen transition, other screen transition), trigger item i (i = 1 to n), transition destination screen i (i = 1 to n), condition, description And action information including the updater and the update date are stored. In the case of new registration of action information, an action number that uniquely identifies at least the action information in the screen may be assigned and stored in the action information DB 132.

  As shown in FIG. 16, in the screen item information DB 134, for each screen, a subsystem name to which the screen belongs, a sub application name, a screen name, presence / absence of dictionary cooperation, a screen item name i (i = 1 to n, i is a screen) The number of items), screen item IDi (i = 1 to n), object type (text box, component box, button), display type, input / output, updater, and update date are stored. In the case of new registration of a screen item, at least a screen item number that uniquely identifies the screen item in the screen may be assigned and stored in the screen item information DB 134.

  As shown in FIG. 17, in the screen table information DB 136, for each screen, the subsystem name to which the screen belongs, the sub application name, the screen name, and the table name i (i = 1 to n, i is referred to / registered / updated by the screen) / Number of tables to be deleted), table IDi (i = 1 to n), presence / absence of reference, presence / absence of registration, presence / absence of update, presence / absence of deletion, screen table information including updater and update date.

  As shown in FIG. 18, in the test case information DB 138, for each screen, the subsystem name to which the screen belongs, the sub application name, the screen name, the action name i (i = 1 to n, i is the number of actions), the test number , Test case information including test contents, assumed result, execution date, updater, and update date are stored. In the case of new registration of a test case, at least a test case number uniquely specified in the screen may be assigned and stored in the test case information DB 138.

  As shown in FIG. 19, in the document information DB 139, for each screen, the subsystem name to which the screen belongs, the sub application name, the screen name, and the document file name i related to the screen (i = 1 to n, i is the number of document names). ) And the test case information including the updater and the update date are stored. In the case of new registration of document information, at least a document ID uniquely specified in the screen may be assigned and stored in the document information DB 139.

  As shown in FIG. 20, the table information DB 114 includes a system name, a table name, a table ID, an estimated number of rows, a record size and remarks, and whether or not each column has dictionary linkage, column IDi (i = 1 to n, Table information including i is the number of columns), column name i (i = 1 to n), key type (whether or not there is a primary key), data type, updater, and update date is stored. In the case of newly adding table information, a table number that identifies the table in the system may be assigned and stored in the table information DB 114.

  Although not shown, in the table information DB 114, for a table, an index is defined in a column, an index order, index information such as an index ID and an index type, and a column referring to an external table is a reference name ID and a reference destination. External reference information such as a table name and SQL management information are further stored.

  As shown in FIG. 21A, the item dictionary DB 140 has a system name, item dictionary name (sum) i (= 1 to n, i is the number of item dictionaries), item dictionary name (English) (i = 1). N), item dictionary information including type (numerical value / character string), number of digits, details, updater, and update date is stored. An item dictionary number may be assigned to the item dictionary and stored in the item dictionary DB 140. As shown in FIG. 21B, the item use screen information DB 142 includes screen IDi (i = 1 to n, i is the number of screens linked in the dictionary), screen item IDi (i = 1 to n), and item dictionary. The name (sum) is stored. As shown in FIG. 21C, the item use table information DB 144 has a table IDi (i = 1 to n, i is the number of columns linked in the dictionary), a column IDi (i = 1 to n), and an item dictionary name. i (sum) (i = 1 to n) is stored.

  As shown in FIG. 22A, the user information DB 10 includes a login ID (i = 1 to n, i is the number of users), a password i (i = 1 to n), and a name i (i = 1 to 1). n), user information of kana i (i = 1 to n), mail address i (i = 1 to n) and telephone i (i = 1 to n) are stored. As shown in FIG. 22B, the group information DB 12 includes a group name i (i = 1 to n, i is the number of groups), an LDAP group name i (i = 1 to n), and an administrator for each group. Stores group information including authority, development authority, login authority, and reference authority. The presence / absence of administrator authority refers to the authority as a system administrator, for example, the presence / absence of authority such as reference / update / registration / deletion of the user information DB 10 and the group information DB 12.

  The presence / absence of development authority refers to rights as a developer, for example, authority to refer / update / register / delete the design information DB 8. The presence or absence of login authority means the presence or absence of the right to log in to the repository management server 6. The presence or absence of reference authority refers to the presence or absence of authority to refer to the design information DB 8, for example. In this way, it is possible to determine the group to which the user belongs according to the role of the administrator or developer of the user, and to set the presence or absence of various rights for each group. The system information, subsystem information, sub-application information, screen information, table information, item dictionary information, etc. may be set with or without authority to access the design information DB 8, and developers may be grouped by subsystem or sub-application. Thus, the authority to access each subsystem or sub-application may be set in detail.

  23 to 43 are flowcharts showing the system design method, and FIGS. 44 to 70 are views showing screens. Hereinafter, the system design method will be described with reference to these drawings.

(1) User authentication and access right check When the URL of the repository management server 6 is specified by the terminal device 2 and a request packet for access to the repository management server 6 is received, the user ID and password described in HTML are input. Authentication request screen data for requesting is transmitted to the terminal device 2. The login ID and password transmitted from the terminal device 2 and extracted by the input data extraction unit 15 are input. In step S2 in FIG. 23, it is determined whether authentication is performed. If a positive determination is made, the process proceeds to step S4. If a negative determination is made, the process proceeds to step S18.

  In step S4, it is checked whether or not the login ID is registered in the user information DB 10. If a positive determination is made, the process proceeds to step S8. If a negative determination is made, the process proceeds to step S17. In step S8, it is checked whether or not the password is registered in the user information DB 10. If it is affirmation determination, it will progress to step S10. If a negative determination is made, the process proceeds to step S17. In step S10, the group to which the user belongs is specified. In step S12, the group information DB 12 is searched to check the login authority for the group. In step S14, the presence / absence of login authority is checked. If the determination is affirmative (login authority exists), the process proceeds to step S16. If the determination is negative (no login right), the process proceeds to step S17. Allow in step S16. In step S17, it is not permitted. If the authentication is affirmed, a response including the screen data of the menu screen shown in FIG. 44 described in HTML and set by the URL of the corresponding screen as link information is transmitted to the terminal device 2. At this time, the user is associated with the session, and the related information is stored in the table.

  In the case of checking the access right, the process proceeds to step S18, and the group is specified from the login ID. In step S20, it is checked whether or not the access is a reference access. If a positive determination is made, the process proceeds to step S22. If a negative determination is made, the process proceeds to step S30. In step S22, the group information DB 12 is searched to check whether there is a reference authority or a development authority. In step S24, it is checked whether or not there is a reference authority.

  If the determination is affirmative (when the reference authority exists), the process proceeds to step S26 and is permitted. If a negative determination is made (in the case where there is no reference right), the process proceeds to step S28 and is not permitted. When the access right check is update / registration / deletion, the process proceeds to step S30, and the right (update right) for updating / registering / deleting the group information DB 12 is checked. The case of having update authority is the case of having development authority. In step S32, it is checked whether or not there is an update authority. If a positive determination is made, the process proceeds to step S34. If a negative determination is made, the process proceeds to step S36. Allow in step S34. In step S36, it is not permitted.

(2) System information (2.1) Reference to system information (a) When a system is specified When a system is clicked on the menu screen shown in FIG. 44 (click operation is called designation), the system information shown in FIG. When the URL of the screen is received, the access right is checked in step S2 in FIG. It is checked whether or not it is permitted in step S4. If a positive determination is made, the process proceeds to step S6. If the determination is negative, the process ends.

  In step S6, the system information DB 107 is searched to output system information such as a list of system names, system codes, folder names, updaters and update dates of the system information, and links between these system information, system IDs and folders. Based on the folder ID as information, the output data editing unit 16 is instructed to edit the screen data of the system information screen shown in FIG.

  Based on the system information, the system ID, and the folder ID as the link information, the output data editing unit 16 edits the data into HTML screen data according to the template of the system information screen. The packet transmission unit 14 accommodates screen data in a packet according to HTTP and transmits the packet to the terminal device 2. Items that are not displayed on the screen other than the link information are set to, for example, a hidden value. Also, the HTML screen data includes Javascript that is activated with a click on a button or link as a trigger. Since the processing of the output data editing unit 16 and the packet transmission unit 14 is the same in the following description, the description thereof is omitted.

(B) When a folder is designated When a folder is designated on the system information screen, the access right is checked in step S33 in FIG. It is checked whether or not it is permitted in step S34. If a positive determination is made, the process proceeds to step S36. If the determination is negative, the process ends. Based on the URL + folder ID of the system information screen as the link information of the folder specified in step S36, the system information DB 107 is searched, and a list of document information belonging to the specified folder is output. Based on the document ID as the link information, the document ID of the document in each line of the document, the system ID, and the selected folder ID, the output data is edited so as to be edited into system information screen data including a definition of a check box that enables selection of each line. The editing unit 16 is instructed.

(2.2) Registration / Update of System Information When update is designated on the system information screen, an access right is checked in step S8 in FIG. It is checked whether or not it is permitted in step S10. If a positive determination is made, the process proceeds to step S12. If the determination is negative, the process ends. In step S12, based on the system ID (in the case of update), the system code input in the input field, the system name and remarks, the user (updater) associated with the session, and the update date are registered in the system information DB 107 /Update. In the case of new registration, a system ID is assigned and registered in the system information DB 107.

(2.3) Folder creation / deletion When folder creation / deletion is designated on the system information screen, the access right is checked in step S22 in FIG. It is checked whether or not it is permitted in step S23. If a positive determination is made, the process proceeds to step S24. If the determination is negative, the process ends. In step S24, in the case of creating a folder, the folder name is registered in the system information DB 107 based on the folder name input on the folder name request screen displayed by operating JavaScript on the system information screen and the system ID. A folder with a folder name is created, and in the case of deleting a folder, based on the selected folder ID and system ID, the document information belonging to the folder corresponding to the folder ID is deleted from the system information DB 107 and the folder is deleted. delete.

(2.4) Registration of document information (a) When addition is specified on the system information screen, the system ID and the folder ID of the selected folder are output in step S14 in FIG. Based on this information, the user is instructed to edit the document registration screen (upload screen) data for registering the document belonging to the folder.

  (B) When registration (upload) is designated on the document registration screen, the access right is checked in step S16 in FIG. It is checked whether or not it is permitted in step S18. If a positive determination is made, the process proceeds to step S20. If the determination is negative, the process ends. The document file is uploaded from the terminal device 2 to the folder corresponding to the folder ID specified in step S20, and the document name and file are based on the system ID, folder ID, document ID (in the case of update) and the uploaded document file. The type, the folder name to which the document belongs, the user (updater) corresponding to the user ID associated with the session, and the document information of the update date are registered in the system information DB 107.

(2.5) Deletion of Document Information When deletion is specified on the system information screen, the access right is checked in step S25 in FIG. It is checked whether or not it is permitted in step S26. If a positive determination is made, the process proceeds to step S28. If the determination is negative, the process ends. In step S28, the document information is deleted from the system information DB 107 based on the system ID, the folder ID of the selected folder, and the document ID for the document whose deletion is checked in the check box in each row of the document name list. To do. At this time, the user (updater) corresponding to the user ID associated with the session and the document information of the update date are registered in the system information DB 107 and the document file corresponding to the document ID is deleted from the folder corresponding to the folder ID. .

(2.6) File transfer of document information When a document is designated on the system information screen, an access right is checked in step S29 in FIG. It is checked whether or not it is permitted in step S30. If a positive determination is made, the process proceeds to step S32. If the determination is negative, the process ends. In step S32, the document file is read based on the system ID, the folder ID, and the document ID as the link information of the designated document. In step S34, the document file is transmitted to the terminal device 2.

(3) Subsystem list (3.1) When a subsystem is specified on the menu screen or the like When a subsystem is specified on the menu screen or the like shown in FIG. 44 and the URL of the subsystem list screen shown in FIG. 46 is received The access right is checked in step S40 in FIG. It is checked whether or not it is permitted in step S42. If a positive determination is made, the process proceeds to step S44. If the determination is negative, the process ends. In step S44, the subsystem information DB 108 is searched to output a list of system names, system codes, subsystem codes, subsystem names, and remarks, and subsystem IDs for each row of the information, system ID, and subsystem. Based on the subsystem ID + trigger Javascript program name as the subsystem name link information, an instruction is given to edit the screen data of the subsystem list shown in FIG. 46 including the definition of a check box that enables selection of each row.

(3.2) When a subsystem is designated on the subsystem list screen When a subsystem is designated on the subsystem list screen, an access right is checked in step S50 in FIG. It is checked whether or not it is permitted in step S52. If a positive determination is made, the process proceeds to step S54. If the determination is negative, the process ends. In step S54, the subsystem information DB 108 is searched based on the system ID and the subsystem ID set based on the link information by Javascript, and the system name, the corresponding subsystem code and subsystem name, and the subsystem A list of folder names, subsystem information updater and update date subsystem information are output, and based on the subsystem information, system ID, subsystem ID, and folder ID as the link information of the folder name, The subsystem information screen data shown in FIG. 47 is instructed to be edited.

(3.3) Addition of subsystem information When addition is specified on the subsystem list screen, the system ID is output in step S48 in FIG. 25 to instruct to edit the subsystem information screen data. .

(3.4) Deletion of Subsystem Information When deletion is designated on the subsystem list screen, the access right is checked in step S56 in FIG. In step S58, it is checked whether or not it is permitted. If a positive determination is made, the process proceeds to step S60. If the determination is negative, the process ends. Based on the subsystem ID of the subsystem checked in the check box in step S60, the subsystem information of the corresponding subsystem is deleted from the subsystem information DB.

(4) Subsystem information (4.1) Registration / update of subsystem information When update is designated on the subsystem information screen, an access right is checked in step S100 in FIG. It is checked whether or not it is permitted in step S102. If a positive determination is made, the process proceeds to step S104. If the determination is negative, the process ends. In step S104, the subsystem code, the subsystem name and remarks, the user (updater) associated with the session, and the update date are registered in the subsystem information DB 108. In the case of new registration of subsystem information, a subsystem ID is assigned and registered in the subsystem information DB 108.

(4.2) Folder creation / deletion When folder creation / deletion is designated on the subsystem information screen, the system ID becomes the subsystem ID and the system information DB 107 stores the subsystem information in steps S114 to S116 in FIG. Processing similar to that in steps S25 to S28 in FIG. 24 is performed only by replacing the DB 108.

(4.3) When a folder is designated When a folder is designated on the subsystem information screen, the access right is checked in step S130 in FIG. In step S132, it is checked whether or not it is permitted. If a positive determination is made, the process proceeds to step S134. If the determination is negative, the process ends. Based on the folder ID and the subsystem ID as the link information of the folder specified in step S134, the subsystem information DB 108 is searched, and a list of document information belonging to the specified folder is output. Based on the document ID as the link information, the document ID of each row, the system ID, the subsystem ID, and the folder ID of the designated folder, the subsystem information screen data including a definition of a check box that enables selection of each row is edited. Instruct.

(4.4) Registration of document information (a) When addition is specified on the subsystem information screen, only the system ID is replaced with the sub application ID in step S106 in FIG. 26, and step S14 in FIG. Similar processing is performed.

  (B) When registration is specified on the document registration screen, the system ID is replaced with the sub application ID and the system information DB 107 is replaced with the subsystem information DB 108 in steps S108 to S112 in FIG. Processing similar to S20 is performed.

(4.5) Deletion of Document Information When deletion is specified on the subsystem information screen, the system ID is simply replaced with the sub application ID and the system information DB 107 is replaced with the subsystem information DB 108 in steps S117 to 120 in FIG. Thus, the same processing as in steps S25 to S28 in FIG. 24 is performed.

(4.6) Transfer of Document File When a document is specified on the subsystem screen, the system ID is replaced with the sub application ID and the system information DB 107 is replaced with the subsystem information DB 108 in steps S122 to S128 in FIG. Only the process similar to the process of step S29-step S32 in FIG. 24 is performed.

(5) Sub-application list (5.1) When a sub-application is specified on the subsystem screen, etc. When the sub-application is specified on the subsystem screen and the URL of the sub-application list screen shown in FIG. 48 is received, the steps in FIG. In S150, the access right is checked. It is checked whether or not it is permitted in step S152. If it is affirmation determination, it will progress to step S154. If the determination is negative, the process ends. In step S154, the sub application information DB 110 is searched to select a system name, a system code, a selected subsystem name, a selected subsystem code, and a list of subsystem names so that the subsystem name can be selected. Output a list of sub-app codes, sub-app names, and remarks of sub-apps belonging to the sub-system, and sub-app ID as a link information of the sub-app ID and sub-app name of each row of the system ID, sub-system ID, and sub-app name + trigger Based on the program name of Javascript, it is instructed to edit the screen data of the sub-application list shown in FIG. 48 including the definition of a check box that enables selection of each row. If a sub-app is specified on the menu screen, the sub-app list is not displayed because no sub-system is selected. The list of sub-apps may be displayed only when a search is designated.

(5.2) When search is specified When a search is specified on the sub-application list screen, an access right is checked in step S171 in FIG. In step S172, it is checked whether or not it is permitted. If it is affirmation determination, it will progress to step S174. If the determination is negative, the process ends. Based on the subsystem name selected in step S174, the sub application information DB 110 is searched. A list of sub-app codes, sub-app names, and remarks of the sub-apps belonging to the sub-system selected in step S176 is output, and the link information of these information, system ID, sub-system ID, and sub-app ID and sub-app name of each row of sub-apps Instructed to edit the screen data of the subsystem list including the definition of a check box that enables selection of each row based on the sub application ID + the JavaScript program name of the trigger.

(5.3) When a sub application is designated on the sub application list screen When a sub application is designated on the sub application list screen, an access right is checked in step S160 in FIG. In step S162, it is checked whether or not it is permitted. If it is affirmation determination, it will progress to step S164. If the determination is negative, the process ends. In step S164, the sub application information DB 110 is searched based on the sub application ID as link information, and the system name, subsystem code, subsystem name, corresponding sub application name, sub application code, list of folder names for the sub application, sub application Subsystem information of the information updater and update date is output, and the sub application information screen data shown in FIG. 49 is displayed based on the sub application information, the subsystem ID, the sub application ID, and the folder ID as the link information of the folder name. Instruct to edit.

(5.4) Addition of sub application information When addition is specified on the sub application list screen, the subsystem ID is output in step S158 in FIG. 27, and is edited into the sub application information screen data based on the subsystem ID. To instruct.

(5.5) Deletion of sub-application information When deletion is specified on the sub-application list screen, the access right is checked in step S166 in FIG. In step S168, it is checked whether or not it is permitted. If a positive determination is made, the process proceeds to step S170. If the determination is negative, the process ends. Based on the sub application ID of the sub application checked in the check box in step S170, the sub application information of the corresponding sub application is deleted from the sub application information DB 110.

(6) Sub-application information (6.1) Registration / update of sub-application information When an update is designated on the sub-application information screen, an access right is checked in step S200 in FIG. It is checked whether or not it is permitted in step S202. If a positive determination is made, the process proceeds to step S204. If the determination is negative, the process ends. Based on the subsystem ID of the subsystem selected in step S204, the sub application code, the sub application name and remarks input in the input field, the user (updater) associated with the session, and the update date are stored in the sub application information DB 110. sign up.

(6.2) Folder creation / deletion When folder creation / deletion is designated on the sub application information screen, the system ID is replaced with the sub application ID and the system information DB 107 is replaced with the sub application information DB 110 in steps S214 to S216 in FIG. Only the process similar to step S25 to step S28 in FIG. 24 is performed.

(6.3) When a folder is designated When a folder is designated on the sub application information screen, the access right is checked in step S228 in FIG. In step S230, it is checked whether or not it is permitted. If a positive determination is made, the process proceeds to step S232. If the determination is negative, the process ends. Based on the folder ID and the sub application ID as the link information of the folder specified in step S232, the sub application information DB 110 is searched, a list of document information belonging to the specified folder is output, and these information and link information Instructed to edit the sub application information screen data including the definition of a check box that enables selection of each row based on the document ID, the document ID of each row, the system ID, the subsystem ID, and the folder ID of the designated folder. .

(6.4) Registration of document information (a) When addition is specified on the sub application information screen, the system ID is replaced with the sub application ID in step S206 in FIG. 28, and the same as step S14 in FIG. Perform the process.

  (B) When registration is specified on the document registration screen, only the system ID is replaced with the sub application ID and the system information DB 107 is replaced with the sub application information DB 110 in steps S208 to S212 in FIG. 28, and steps S16 to S20 in FIG. The same processing is performed.

(6.5) Deletion of Document Information When deletion is specified on the sub application information screen, the system ID is replaced with the sub application ID and the system information DB 107 is replaced with the sub application information DB 110 in steps S217 to S220 in FIG. 24, the same processing as step S25 to step S28 is performed.

(6.6) File Transfer of Document File When a document is specified on the sub application information screen, the system ID is replaced with the sub application ID and the system information DB 107 is replaced with the sub application information DB 110 in steps S222 to S228 in FIG. Only the process similar to the process of step S29-step S32 in FIG. 24 is performed.

(7) Screen List (7.1) When a Screen is Designated on the Subsystem Screen etc. When a screen is designated on the subsystem screen and the URL of the screen list screen shown in FIG. 50 is received, step S250 in FIG. Check the access right. It is checked whether or not it is permitted in step S252. If it is affirmation determination, it will progress to step S254. If the determination is negative, the process ends. In step S254, the subsystem information DB 108, the sub application information DB 110, and the screen layout information DB 130 are searched based on the subsystem ID and the sub application ID, and the system name, system code, selected subsystem name and subsystem code, sub List of subsystem names for which system names can be selected, selected sub application code and sub application name, list of sub application names for which sub application names can be selected, screen codes of screens belonging to the selected sub application, screen names, screen types FIG. 11 is a diagram including a definition of a check box that outputs a list of usage purposes and processing contents, and enables selection of each row based on the information, the screen ID of each row of the screen, and the screen ID as link information of the screen ID. In the screen data of the screen list screen shown in 50 An instruction to collecting. When a screen is designated on the menu screen or the like, since no subsystem or sub-application is selected, the screen list is not displayed but is displayed when a search described later is designated. Even when a screen is specified on the sub application information screen, it may be displayed when a search is specified without displaying a list of screens.

(7.2) When search is specified When a search is specified on the screen list screen, an access right is checked in step S279 in FIG. It is checked whether or not it is permitted in step S280. If it is affirmation determination, it will progress to step S282. If the determination is negative, the process ends. The image layout information DB 130 is searched based on the subsystem name and sub application name selected in step S282 and the designated range of the last update date. A list of screen codes, screen names, screen types, usage purposes, and processing contents of screens belonging to the subsystems and sub-applications selected in step S284 and whose screen information includes the last update date within the specified range is output. The screen ID of each row of the screen, the screen ID as the link information of the screen ID + the JavaScript program name of the trigger, and edit the screen data of the screen list screen including the definition of the check box that enables selection of each row. To instruct.

(7.3) When a Screen ID is Designated on the Screen List Screen When a screen ID is designated on the screen list screen, an access right is checked in step S260 in FIG. In step S262, it is checked whether or not it is permitted. If it is affirmation determination, it will progress to step S264. If the determination is negative, the process ends. In step S264, the screen layout information DB 130 is searched based on the screen ID set by Javascript based on the link information, and the selected subsystem name, sub application name, subsystem name, and sub application name can be selected. A list of system name and sub application name, screen ID, screen name, screen type, purpose of use, processing contents, screen layout information updater and screen layout information on the update date are output, and these information, screen ID, screen The screen layout information screen data shown in FIG. 51 is instructed to be edited based on the image image file name and the URL as the link information of the screen image.

(7.4) New creation designation When new creation is designated on the screen list screen, the screen layout screen data is instructed to be edited in step S258 in FIG.

(7.5) Deletion of Screen Information When deletion is designated on the screen list screen, the access right is checked in step S274 in FIG. In step S276, it is checked whether or not it is permitted. If it is affirmation determination, it will progress to step S278. If the determination is negative, the process ends. Based on the screen ID checked in the check box in step S278, the screen ID screen is obtained from the screen layout information DB 130, action information DB 132, screen item information DB 134, screen table information DB 136, test case DB 138, and document information DB 139. Delete screen information related to.

(8) Screen Layout Information (8.1) Reading Screen Image Image When the file name of the screen image image is specified on the screen layout screen, the image image corresponding to the file name is read in step S300 in FIG. . The image is transmitted to the terminal device 2. In step S302, the action information DB 132 is searched based on the screen ID. In step S304, a list of action information including name, ID, type, trigger item, transition destination, condition, and description is output, and this information, action number of each line, action number as action ID link information + Javascript program name Based on this, it is instructed to edit the screen data of the action list in FIG. 50 including the definition of a check box that enables selection of each row.

(8.2) Reading the HTML file of the screen When the screen image is designated on the screen layout screen, the HTML file (screen ID.html) of the screen corresponding to the screen ID is read in step S306 in FIG. The HTML file of the screen is transmitted to the terminal device 2, and the screen is displayed by the browser based on the HTML file of the screen.

(8.3) Registration / Update of Screen Layout Information When an update is specified on the screen layout screen, an access right is checked in step S310 in FIG. It is checked whether or not it is permitted in step S312. If it is affirmation determination, it will progress to step S314. If the determination is negative, the process ends. In step S314, the screen ID (in the case of updating), the selected subsystem name and sub application name, the screen ID input in the input field, the screen name, the screen type, the purpose of use, the screen layout information of the processing content, and the session The updater and the update date associated with are registered and updated in the screen layout information DB 130.

(8.4) Add Condition When the add condition is specified on the screen layout screen, the access right is checked in step S316 in FIG. In step S318, it is checked whether or not the permission is granted. If a positive determination is made, the process proceeds to step S320. If the determination is negative, the process ends. In step S320, the action information DB 132 is searched based on the selected screen ID and the action number selected by the check box. In step S322, the action information including the name, ID, type, trigger item, transition destination, condition, and description of the corresponding action is output, and the action edit screen data is edited based on the information, screen ID, and action number. To instruct.

(8.5) Addition of Action Information When addition is specified on the screen layout, an instruction is given to edit the screen action edit screen data based on the screen ID in step S334 in FIG.

(8.6) Deleting Action Information When deletion is specified on the screen layout screen, an access right is checked in step S316 in FIG. It is checked whether or not it is permitted in step S336. If a positive determination is made, the process proceeds to step S338. If the determination is negative, the process ends. In step S340, the corresponding action information is deleted from the action information DB 132 based on the action number and the screen ID that are checked for selection among the check boxes set in each row of the action list. At this time, the updater and update date corresponding to the user ID associated with the session are registered in the action information DB 132.

(9) Action Information (9.1) Action List When an action list is specified on the screen layout screen and the URL of the action list screen is received, the access right is checked in step S360 in FIG. In step S362, it is checked whether or not it is permitted. If it is affirmation determination, it will progress to step S364. If the determination is negative, the process ends. In step S364, the action information DB 132 is searched based on the screen ID. In step S366, a list of action information of name, ID, type, trigger item, transition destination, condition, and description is output, and the action as link information of these information, screen ID, action number of each action, and action ID Based on the number + the Javascript program name of the trigger and the action number of each line, it is instructed to edit the screen data of the action list screen shown in FIG.

(9.2) Condition Addition When condition addition is specified on the action list screen, the same processing as steps S316 to S322 in FIG. 30 is performed in steps S360 to S366 in FIG.

(9.3) Addition of Action Information When addition is designated on the action list screen, the same processing as step S314 in FIG. 30 is performed in step S368 in FIG.

(9.4) Deletion of Action Information When deletion is designated on the action list screen, the same processing as steps S336 to S340 in FIG. 30 is performed in steps S378 to S382 in FIG.

(9.5) Action ID designation When an action ID is designated on the action list screen, the access right is checked in step S378 in FIG. In step S380, it is checked whether or not it is permitted. If a positive determination is made, the process proceeds to step S382. If the determination is negative, the process ends. In step S382, the action information DB 132 is searched based on the screen ID and the action number set based on the link information by Javascript, and the action information of name, ID, type, trigger item, transition destination, condition, and description is obtained. Based on the action information, the screen ID, and the action number, the screen action editing screen data is instructed to be edited.

(9.6) Action Information Registration / Update / Condition Addition When registration is specified on the screen action edit screen, the access right is checked in step S384 in FIG. It is checked in step S386 whether or not it is permitted. If it is affirmation determination, it will progress to step S390. If the determination is negative, the process ends. In step S390, it is checked whether conditions are added. If it is affirmation determination, it will progress to step S392. If a negative determination is made, the process proceeds to step S394. In step S392, a condition is added to the action information DB 132 based on the screen ID and the action number. In step S392, the action information of the corresponding action is registered / updated in the action information DB 132 based on the screen ID (in the case of new registration) or the screen ID and the action number (in the case of updating). At this time, the updater and update date corresponding to the user ID associated with the session are registered in the action information DB 132. In the case of new registration, an action number is assigned and registered in the action information DB 132.

(10) Screen item information (10.1) Screen item list When the screen item list is specified on the screen layout screen and the URL of the screen item list shown in FIG. 53 is received, the access right is checked in step S400 in FIG. To do. It is checked whether or not it is permitted in step S402. If a positive determination is made, the process proceeds to step S404. If the determination is negative, the process ends. In step S404, the screen item information DB 134 is searched based on the screen ID. In step S407, a list of screen item information such as presence / absence of dictionary cooperation, name, ID, object type, display type, input / output, etc. is output for the screen item, and the screen item number of each line of the information, screen ID, and screen item. Based on the screen item number as the link information of the screen item name + the Javascript program name of the trigger, it is instructed to edit the screen data of the screen item list screen including the definition of the check box that enables selection of each row.

(10.2) Addition of Screen Item Information When addition is specified on the screen item list screen, an instruction is given to edit the screen item edit screen data based on the screen ID in step S408 in FIG.

(10.3) Deletion of Screen Item Information When deletion is specified on the screen item list screen, an access right is checked in step S410 in FIG. It is checked in step S412 whether or not it is permitted. If it is affirmation determination, it will progress to step S414. If the determination is negative, the process ends. In step S414, for the screen item that is selected in the check box set in each row of the screen item list, the corresponding screen item information is deleted from the screen item information DB 134 based on the screen ID and the screen item number. To do. At this time, the updater and update date corresponding to the user ID associated with the session are registered in the screen item information DB 134.

(10.4) Name designation of screen item When a name is designated on the screen item list screen, an access right is checked in step S416 in FIG. In step S418, it is checked whether or not it is permitted. If a positive determination is made, the process proceeds to step S420. If the determination is negative, the process ends. In step S420, the screen item information DB 134 is searched based on the screen ID and the screen item number set on the basis of the link information by Javascript. In step S522, screen item information such as name, ID, object type, display type, and input / output is output, and the screen item information, screen ID, screen item number, and dictionary link link information as screen item number + Javascript. Instructs the screen item edit screen data to be edited based on the program name.

(10.5) Dictionary Linkage of Screen Items When dictionary linkage is designated on the screen item edit screen, dictionary linkage of the following screen items is performed in step S424 in FIG. When the access right is checked and permitted, the item dictionary DB 140 is searched based on the screen item number set by Javascript based on the link information + the URL of the item reference screen, and the item name (sum), item name 54, a list of item dictionary information of type and number of digits is output, and based on the item dictionary information and item dictionary number as the link information of the item name (sum) + trigger Javascript program name, FIG. Instructed to edit the item reference screen data shown in At this time, no link information is set in the item dictionary for the item dictionary in which the screen items are dictionary-linked. When the item name (sum) is specified on the item reference screen, JavaScript operates on the item reference screen, and the item dictionary number specified for dictionary cooperation is written to the image item editing screen which is the parent screen of the item reference screen. It is.

(10.6) Registration of Screen Item When registration is designated on the screen item edit screen, the access right is checked in step S424 in FIG. In step S428, it is checked whether or not it is permitted. If it is affirmation determination, it will progress to step S430. If the determination is negative, the process ends. In step S430, based on the screen ID (in the case of new registration) or the screen ID and the item dictionary number (in the case of updating), it is associated with the presence / absence of dictionary cooperation, name, ID, object type, display type, input / output, and session. The screen item information for the updater and update date corresponding to the user ID is registered / updated in the screen item information DB 134. If there is item dictionary cooperation, the screen ID, item ID, and item dictionary name (sum) are registered in the item use screen information DB 142 based on the screen ID, screen item number, and item dictionary number.

(11) Screen transition diagram When the screen transition diagram is specified on the screen layout screen and the URL of the screen transition diagram is received, the access right is checked in step S450 in FIG. It is checked in step S452 whether or not it is permitted. If it is affirmation determination, it will progress to step S454. If the determination is negative, the process ends. In step S454, the action information DB 132 of the screen corresponding to the designated screen ID is searched based on the screen ID. In step S456, the screen ID and screen name of the transition destination are output.

  In step S458, the screen layout information DB 130 is searched based on the screen ID. In step S460, the screen ID, screen name, and screen type of the screen designated are output. In step S462, the action information DB 132 is searched. A screen ID and a screen name having the screen ID designated in step S464 as a transition destination are output as a transition source screen. In step S466, an image of the screen transition diagram is created and an instruction is given to edit the screen transition diagram screen data shown in FIG.

(12) Screen Table List Information (12.1) Screen Table List When a table list is specified on the screen layout screen and the URL of the screen table list screen is received, the access right is checked in step S500 in FIG. In step S502, it is checked whether or not it is permitted. If it is affirmation determination, it will progress to step S504. If the determination is negative, the process ends. In step S504, the screen table information DB 136 is searched based on the screen ID. In step S506, the name of the table to be referred / registered / updated / deleted on the screen corresponding to the screen ID and a list of screen table information of the table ID are output, and the information, the screen ID, the screen table number of each row, and the table Based on the screen table number as the link information of the table name of each row, it is instructed to edit the screen table list screen data shown in FIG.

(12.2) Addition of Screen Table Information When addition is specified on the screen table list screen, an instruction is given to edit the screen table edit screen data based on the screen ID in step S508 in FIG.

(12.3) Deletion of Screen Table Information When deletion is specified on the screen table list screen, the access right is checked in step S510 in FIG. In step S512, it is checked whether or not it is permitted. If it is affirmation determination, it will progress to step S514. If the determination is negative, the process ends. In step S514, the corresponding screen table information is deleted from the screen table information DB 136 on the basis of the screen ID selected in the check box set in each row of the screen ID and table list. At this time, the updater and update date corresponding to the user ID associated with the session are registered in the screen table information DB 136.

(12.4) Designation of Table When a table is designated on the screen table list screen, the access right is checked in step S516 in FIG. In step S518, it is checked whether or not it is permitted. If it is affirmation determination, it will progress to step S520. If the determination is negative, the process ends. In step S522, the screen table information DB 136 is searched based on the screen table number set based on the link information by the screen ID and Javascript + the URL of the screen table screen, and the selected table name and table name can be selected. A list of table names to be output, whether reference / registration / update / deletion of the selected table is output, and the screen table edit screen data is edited based on the information, screen ID, and screen table number. Instruct.

(12.5) Registration / Update of Screen Table Information When registration is designated on the screen table edit screen, an access right is checked in step S524 in FIG. In step S526, it is checked whether or not it is permitted. If a positive determination is made, the process proceeds to step S528. If the determination is negative, the process ends. In step S528, based on the screen ID (in the case of new registration) or the screen ID and the screen table number (in the case of updating), the subsystem name, sub-app name, screen name, table name, and reference / registration / update / delete The presence / absence screen table information is registered / updated in the screen table information DB 136. At this time, the updater and update date corresponding to the user ID associated with the session are registered in the screen table information DB 136. In the case of new registration, a screen table number is assigned and registered in the screen table information DB 136.

(13) Screen table related diagram When a table related diagram is specified on the screen layout screen or the like and the URL of the screen table related diagram is received, the access right is checked in step S550 in FIG. In step S552, it is checked whether or not it is permitted. If it is affirmation determination, it will progress to step S554. If the determination is negative, the process ends. In step S554, the screen table information DB 136 of the screen corresponding to the screen ID specified by the screen ID is searched based on the screen ID. In step S556, the table name and table ID referred to are output. In step S558, the table name and table ID to be updated are output. In step S560, the screen layout information DB 130 is searched based on the screen ID, and the screen name of the designated screen ID is output. An instruction is made to create an image of the screen table related diagram specified in step S562 and edit it to the screen table related diagram shown in FIG.

(14) Screen test case list screen (14.1) Screen test case list When the test case list is specified on the screen layout screen and the URL of the screen test case list screen is received, the access right is checked in step S600 in FIG. To do. In step S602, it is checked whether or not it is permitted. If it is affirmation determination, it will progress to step S604. If the determination is negative, the process ends. In step S604, the test case DB 138 is searched based on the screen ID. In step S606, a list of test cases such as action names, test numbers, test contents, etc. is output, and these information, screen ID, test case number of each case, test case number as test case link information + Javascript program Based on the name, it is instructed to edit the screen test case list screen data shown in FIG. 58 including the definition of a check box for selecting each row.

(14.2) Addition of Test Case When addition is specified on the screen test case list screen, an instruction is given to edit the screen test case edit screen data based on the screen ID in step S608 in FIG.

(14.3) Deletion of Test Case When deletion is specified on the test case list screen, the access right is checked in step S610 in FIG. In step S612, it is checked whether or not it is permitted. If it is affirmation determination, it will progress to step S614. If the determination is negative, the process ends. In step S 614, the corresponding test case is deleted from the test case DB 138 based on the test case number and screen ID of the test case that is checked for selection among the check boxes set in each row of the test case list. At this time, the updater and update date corresponding to the user ID associated with the session are registered in the screen test case information DB 138.

(14.4) Designation of test case When a test case number is designated on the test case list screen, an access right is checked in step S616 in FIG. It is checked in step S618 whether permission has been granted. If it is affirmation determination, it will progress to step S620. If the determination is negative, the process ends. In step S620, the screen test case information DB 138 is searched based on the screen ID and the test case number set based on the link information by Javascript, and the test case such as the action name, test number, and test content is output. Based on the information, the test case number, and the screen ID, the screen test case edit screen data is instructed to be edited.

(14.5) Registration / Update of Test Case When registration is designated on the test case edit screen, the access right is checked in step S622 in FIG. In step S624, it is checked whether or not it is permitted. If a positive determination is made, the process proceeds to step S626. If the determination is negative, the process ends. In step S626, based on the screen ID (in the case of new registration) or the screen ID and the test case number, the update name and the update date corresponding to the action name and test number, and the user ID associated with the session are displayed on the screen test case information. Register in DB138. In the case of new registration, a test case number is assigned and registered in the screen test case information DB 138.

(15) Screen Document List When a document list is specified on the screen layout information screen or the like, the screen document list shown in FIG. 59 displays a list of document information about the screen together with the screen layout information. Similar to the layout information screen, the document information list is the same as the system information screen except that no folder is specified. Addition is addition of document information, and deletion is deletion of selected document information, which is the same as in the case of the system information screen or the like.

(16) Table list (16.1) When a table is specified When a table is specified on the system screen or the like and the URL of the table screen list screen shown in FIG. 60 is received, the access right is determined in step S650 in FIG. Check. It is checked in step S652 whether or not it is permitted. If it is affirmation determination, it will progress to step S654. If the determination is negative, the process ends. In step S654, the table information DB 114 is searched. In step S656, a table list such as a system name, system code, table ID, and table name is output so that the information and each row of the table can be selected by a check box, and the table number as the link information for the reference source + Instructs to edit the screen data of the table list screen based on the program name of the trigger JavaScript.

(16.2) When search is specified When a search is specified on the table list screen, an access right is checked in step S668 in FIG. In step S670, it is checked whether or not it is permitted. If it is affirmation determination, it will progress to step S672. If the determination is negative, the process ends. A table matching the table ID or table name specified in step S674 is searched from the table information DB 114. In step S674, a list of matching tables is output, and each row can be selected based on this information, the table number as the link information of the table ID of each row + the JavaScript program name of the trigger and the table number table of each row. Instruct to edit the screen data of the table list screen including the definition of the check box.

(16.3) When a table ID is designated on the table list screen When a table ID is designated on the table list screen, an access right is checked in step S692 in FIG. It is checked in step S693 if permission has been granted. If a positive determination is made, the process proceeds to step S694. If the determination is negative, the process ends. In step S694, the table information DB 114 is searched based on the table number set by Javascript based on the table number and link information + the URL of the table information screen. In step S696, a list of dictionary linkage presence / absence, column ID, column name, and the like is output for the column of the table corresponding to the table ID, and the column number + Based on the Javascript program name of the trigger, it is instructed to edit the table information screen data shown in FIG.

(16.4) New creation designation When new creation is designated on the table list screen, it is instructed to edit the table information screen data in step S660 in FIG.

(16.5) Deletion of Table When deletion is specified on the table list screen, the access right is checked in step S660 in FIG. It is checked in step S662 if permission has been granted. If a positive determination is made, the process proceeds to step S664. If the determination is negative, the process ends. Based on the table number checked in the check box in step S664, the table information is deleted from the table information DB 114. At this time, the updater and update date corresponding to the user ID associated with the session are registered in the table information DB 114.

(16.6) DDL generation When DDL generation is specified on the table list screen, the access right is checked in step S676 in FIG. It is checked in step S678 whether or not it is permitted. If it is affirmation determination, it will progress to step S680. If the determination is negative, the process ends. The table information DB 114 is searched based on the table ID specified by the table number selected in step S682. In step S682, a DDL is generated from the table information.

(16.7) Reference Source Screen List When a reference source is specified on the table list screen, the access right is checked in step S684 in FIG. In step S686, it is checked whether or not it is permitted. If it is affirmation determination, it will progress to step S686. If the determination is negative, the process ends. In step S688, the screen table information DB 136 is searched based on the table number (+ URL of the reference source screen) set based on the link information by Javascript. Outputs a list of screen source IDs, names, screen types, reference source information on presence / absence of reference / creation / update / deletion of reference source screens that reference / create / update / delete the table corresponding to the table ID specified in step S690. Then, based on these, it is instructed to edit the reference source screen data shown in FIG.

(17) Table information (17.1) Reference to column information When a column is designated on the index information screen or the like and the URL of the table information screen shown in FIG. 62 is received, the access right is checked in step S700 in FIG. Do. In step S702, it is checked whether or not it is permitted. If a positive determination is made, the process proceeds to step S704. If the determination is negative, the process ends. In step S704, the table information DB 114 is searched based on the table number. In step S706, table information such as the table ID, table name, expected number of rows, and record size is output. In step S708, a list of column information such as the presence / absence of dictionary cooperation, column ID, column name, and data type so that it can be selected is output, and the column number is used as the information, the column number of each row, and link information for dictionary cooperation. + Based on the Javascript program name of the trigger, it is instructed to edit the screen data of the table information screen shown in FIG.

(17.2) Update / Registration of Column Information When update is specified on the table information screen, the access right is checked in step S710 in FIG. In step S712, it is checked whether or not it is permitted. If it is affirmation determination, it will progress to step S714. If the determination is negative, the process ends. Register / update the table ID, table name, remarks, expected number of lines and remarks input in step S714 and column information in the table information DB 114 based on column information such as the presence / absence of dictionary cooperation and the selected data type. To do. At this time, the updater and update date corresponding to the user ID associated with the session are registered in the table information DB 114. For columns with dictionary linkage, the item usage table information is updated / registered in the item usage table information DB 144 based on the table ID, column ID, and item dictionary number for dictionary linkage. In the case of new registration, a column number is assigned and registered in the table information DB 114.

(17.3) Dictionary Linkage When dictionary linkage is specified on the table information screen and the column number + URL of the item reference screen set by Javascript based on the link information is received, column dictionary linkage is performed in step S716 in FIG. The following processing is performed. Based on the column number set by Javascript + URL of the item reference screen, the item dictionary DB 140 is searched to output a list of item dictionary information, and this list, column number, and item dictionary that is not linked to the dictionary are output. The name is instructed to be displayed on the item reference screen data shown in FIG. 54 based on the item dictionary number + trigger Javascript program name as link information. When an item dictionary is clicked on the item reference screen, Javascript operates on the item reference screen using the click as a trigger, and the column corresponding to the column number on the table information screen in which the dictionary-linked item dictionary number is the parent screen Written. When the dictionary linkage information is designated to be updated on the table information screen, the item use table information is written in the item use table information DB 144 based on the column number and the item dictionary number.

(17.4) Index information When an index is specified on the table information screen or the like, the access right is checked. When access is permitted, the table information DB 114 is searched based on the table number, the table ID, the table name, and the like are output, and based on these, the index information screen data is instructed to be edited. When new creation is specified on the index information screen, the access right is checked. When access is permitted, the table information DB 114 is searched based on the table number, and a list of columns in the table is output so that each column can select an index order. Based on these, the index information is output. Instructs the screen data to be edited. When deletion is specified on the index information screen, the access right is checked. When access is permitted, the corresponding index information is deleted from the table information DB 114 based on the table number.

  When update is specified on the index information screen, the access right is checked. If access is permitted, the index order, index ID, index type, and the like are registered in the index information table information DB 114 for the column IDs whose check boxes are checked. On an index information screen (not shown), an index ID set as an index is displayed in a predetermined area. When the mouse is over the index ID, index information about the index ID is displayed.

(17.5) External reference When an external reference is specified on the table information screen, the access right is checked and permitted based on the designation of new creation / deletion / update as in the index information screen operation. The table information DB 114 is accessed, and external reference information such as an external reference table name and table ID is newly created / deleted / updated for a column to be externally referenced. At this time, an external reference table name and a table ID to be externally referenced can be selected for each row of the column. In addition, a reference name ID for a column to be externally referenced is displayed in a predetermined area, and external reference information such as a reference destination table name is displayed by selecting the reference name ID.

(17.6) SQL management When SQL management is designated on the column information screen or the like, the access right is checked. When access is permitted, the SQL management information related to the table is accessed on the table information DB 114 based on the designation of new creation / deletion / update as in the operation on the index information screen, and the SQL management SQL management information such as the SQL name, SQL description, execution plan, and execution result is newly created / deleted / updated.

(18) Item dictionary (18.1) When a dictionary is specified When a dictionary is specified on the system screen or the like and the URL of the item dictionary screen shown in FIG. 63 is received, the access right is checked in step S750 in FIG. I do. It is checked in step S752 if permission has been granted. If it is affirmation determination, it will progress to step S754. If the determination is negative, the process ends. In step S754, the item dictionary DB 116 is searched. In step S756, the item use screen information DB 142 is searched based on the item dictionary name (English) of each item dictionary, and the number of screen items linked to the item dictionary is counted. In step S758, the item use table information DB 144 is searched based on the item dictionary name (English), and the number of columns in the table linked with the item dictionary is counted.

  In step S758, a list of item dictionaries such as system name, system code, item name (sum), item name (English), type, number of digits, number of screen items linked in dictionary, number of columns linked in dictionary, etc. is output. For this information, the item dictionary number as the link information of the item name + the Javascript program name of the trigger, and the number of screen items associated with the dictionary, the item dictionary number as the link information + the program name of the Javascript of the trigger and the dictionary The number of linked columns is edited in the screen data of the item dictionary screen including the definition of a check box that enables selection of each row based on the item dictionary number as link information + the JavaScript program name of the trigger. Instruct.

(18.2) When search is designated When a search is designated on the item dictionary screen, an access right is checked in step S770 in FIG. In step S778, it is checked whether or not the permission is granted. If a positive determination is made, the process proceeds to step S782. If the determination is negative, the process ends. The item dictionary DB 140 is searched based on the item name (English / Japanese) input in step S784. In step S783, based on the matching item name (English / Japanese), the item use screen information DB 142 is searched, and the number of screen items linked to the item dictionary is counted.

  In step S784, the item use table information DB 144 is searched based on the matching item name (English / Japanese), and the number of columns in the table linked with the item dictionary is counted. In step S785, a list of item dictionaries such as system name, system code, item name (sum), item name (English), type, number of digits, number of screen items linked in dictionary, number of columns linked in dictionary, etc. is output. These items of information, item dictionary number as item name link information + trigger Javascript program name, and dictionary linked screen item numbers, item dictionary number as link information + trigger Javascript program name and dictionary linkage For the number of columns that have been specified, an instruction is given to edit the screen data of the item dictionary screen including the definition of a check box that enables selection of each row based on the item dictionary number as link information + the JavaScript program name of the trigger. To do.

(18.3) When Duplicate Item Search (Japanese / English) is Designated When Duplicate Item Search (Japanese / English) is designated on the item dictionary screen, the access right is checked in step S786 in FIG. It is checked in step S788 whether or not it is permitted. If it is affirmation determination, it will progress to step S790. If the determination is negative, the process ends. Based on the item name (English / Japanese) input in step S790, a duplicate item (Japanese / English) in the item dictionary DB 140 is searched. In step S791, the item use screen information DB 142 is searched based on the duplicate item name (English), and the number of screen items linked to the item dictionary is counted.

  In step S792, the item use table information DB 144 is searched based on the duplicate item name (English), and the number of columns in the table linked with the item dictionary is counted. In step S793, a list of item dictionaries such as system name, system code, item name (sum), item name (English), type, number of digits, number of screen items linked in dictionary, number of columns linked in dictionary, etc. is output. These items of information, item dictionary number as item name link information + trigger Javascript program name, and dictionary linked screen item numbers, item dictionary number as link information + trigger Javascript program name and dictionary linkage For the number of columns that have been specified, an instruction is given to edit the screen data of the item dictionary screen including the definition of a check box that enables selection of each row based on the item dictionary number as link information + the JavaScript program name of the trigger. To do.

(18.4) Addition designation When addition is designated on the item dictionary screen, an instruction is given to edit the item dictionary editing screen data in step S762 in FIG.

(18.5) Deletion of Item Dictionary When deletion is specified on the item dictionary screen, the access right is checked in step S764 in FIG. It is checked in step S766 whether or not it is permitted. If a positive determination is made, the process proceeds to step S768. If the determination is negative, the process ends. In step S768, the item dictionary is deleted from the item dictionary DB 140 based on the item dictionary number checked in the check box.

  Further, the item use screen item information of the corresponding item dictionary is deleted from the item use screen information DB 142 and the dictionary of the corresponding screen item is not linked from the screen item information DB 134. The item use column information of the corresponding item dictionary is deleted from the item use table information DB 144, and the corresponding column dictionary is not linked from the table information DB 144.

(18.6) When an unused item is designated When an unused item is designated on the item dictionary screen, an access right is checked in step S800 in FIG. In step S802, it is checked whether or not it is permitted. If a positive determination is made, the process proceeds to step S804. If the determination is negative, the process ends. In step S804, the item dictionary DB 140 is searched. In step S806, based on each item name (English), the item use screen information DB 142 is searched, and the number of screen items linked to the item dictionary is counted.

  In step S808, the item use table information DB 144 is searched based on each item name (English), and the number of columns associated with the item dictionary is counted. In step S810, the system name, the system code, and the item dictionary information in which both count numbers are 0 (unused items) are output, and the item dictionary number as the link information of the information and the item name + the Javascript program name of the trigger As for the number of screen items associated with the dictionary, the item dictionary number as the link information + the JavaScript name of the trigger JavaScript, and the number of columns associated with the dictionary, the item dictionary number as the link information + the JavaScript name of the trigger JavaScript. Based on this, it is instructed to edit the screen data of the item dictionary screen including the definition of a check box that enables selection of each row.

(18.7) Item Name Specification on Item Dictionary Screen When an item name (sum) is specified on the item dictionary screen, the access right is checked in step S812 in FIG. It is checked in step S814 whether or not it is permitted. If it is affirmation determination, it will progress to step S816. If the determination is negative, the process ends. In step S818, the item dictionary DB 140 is searched based on the item dictionary number (+ URL of the item definition screen) set based on the link information by the JavaScript of the trigger. In step S818, for the item dictionary corresponding to the item name / item ID, the item name (sum), item name (English), type, number of digits, and details are output, and based on these information and item dictionary number, the item dictionary Instructs the dictionary editing screen data to be edited.

(18.8) Updating Item Dictionary When update is specified on the item dictionary editing screen, the access right is checked in step S820 in FIG. In step S822, it is checked whether or not it is permitted. If a positive determination is made, the process proceeds to step S824. If the determination is negative, the process ends. In step S824, the item dictionary number (in case of update), item name (sum), item name (English), type and number of digits, and the updater and update date corresponding to the user ID associated with the session are registered in the item dictionary DB 140. /Update.
In the case of new registration, an item dictionary number is assigned and registered in the item dictionary DB 140.

(18.9) Screen designation When a screen is designated on the item dictionary screen, an access right is checked in step S826 in FIG. In step S828, it is checked whether or not it is permitted. If it is affirmation determination, it will progress to step S830. If the determination is negative, the process ends. In step S830, the item dictionary DB 140 is searched based on the item dictionary number set by Javascript based on the link information and the URL of the item use object list screen, and based on the item ID (English) corresponding to the item dictionary number. The item use screen information DB 142 is searched. In step S832, the screen item information DB 134 is searched based on the screen item ID of the item use screen item information. In step S834, a list of screen IDs, screen names, object IDs, object names, types, and the like of the screen items that are dictionary-linked with the item dictionary is output, and based on these pieces of information, the item use object list shown in FIG. Instructs the screen data to be edited.

(18.10) DB designation When a DB is designated on the item dictionary screen, an access right is checked in step S836 in FIG. In step S838, it is checked whether or not it is permitted. If it is affirmation determination, it will progress to step S840. If the determination is negative, the process ends. In step S840, the item dictionary DB 140 is searched based on the item dictionary number set by Javascript based on the link information and the URL of the item use column list screen, and based on the item ID (English) corresponding to the item dictionary number. The item use table information DB 144 is searched. In step S842, the table information DB 114 is searched based on the column ID of the item use column information. In step S844, a list of column IDs, table names, column IDs, column names, types, and the like of the columns linked to the item dictionary is output, and based on these pieces of information, an item use column list screen shown in FIG. Instruct the data to be edited.

(19) Message When a message is specified on the menu screen or the like, when the access right check is permitted, the message information DB 118 is searched, and a list of message information such as code, level and content is output for the message. Based on this information, message ID for each line, and code of each line as link information, message ID + trigger's Javascript program name, edit to message list screen data including definition of check box that enables selection of each line To instruct.

  When the search is specified on the message list screen, when the access right is checked and permitted, the message information DB 118 is searched based on the input code and level, and the message information (code , Level, and content), and based on these, each row has a message ID, and each row code has a message ID as a link information + trigger Javascript program name to select each row. Instructs the message list screen data including the definition to be edited. When a code is specified on the message list screen, when the access right is checked and permitted, the message information DB 118 is searched based on the message ID set based on the link information by Javascript and the URL of the message definition screen. The message information such as the code, the level, and the content is output, and the message definition screen data is instructed to be edited based on the information and the message ID.

  When file output is specified on the message list screen, a Java property file is created based on the message displayed in the message list when the access right is checked and permitted. When new creation is specified on the message list screen, the message definition screen data is instructed to be edited when the access right check is permitted.

  When deletion is specified on the message list screen, message information is displayed based on the message ID that is checked for deletion in the check box set in each line of the message list when access permission is checked and allowed. Delete from the information DB 118. At this time, the updater and update date corresponding to the user ID associated with the session are registered in the message information DB 118. When registration is specified on the message definition screen, when the access right is checked and permitted, the message ID (in case of update), code, level and content, and the updater and update corresponding to the user ID associated with the session The message information of the day is registered in the message information DB 118.

(20) User Information (20.1) User List When a user is specified on the menu screen and receives the URL of the user information list screen shown in FIG. 66, the access right is checked in step S850 in FIG. In step S852, it is checked whether or not it is permitted. If a positive determination is made, the process proceeds to step S854. If the determination is negative, the process ends. In step S854, the user information DB 10 is searched. In step S856, a list of user information such as login IDs and names is output, and each line is changed based on the user number + Javascript program name as link information of these information, the user number of each line, and the name of each line. The user is instructed to edit the screen data of the user information list screen shown in FIG. 66 including the definition of check boxes that can be selected.

(20.2) Search When a search is specified on the user list screen, an access right is checked in step S858 in FIG. In step S860, it is checked whether or not it is permitted. If a positive determination is made, the process proceeds to step S862. If the determination is negative, the process ends. The user information DB 10 is searched based on the login ID or name input in step S862. In step S864, matching user information is output, and each line can be selected based on the user number + trigger Javascript program name as link information of the information, the user number of each line, and the name of each line. Instruct to edit the screen data of the user information list screen including the definition of the check box.

(20.3) Addition designation When addition is designated on the user list screen, an instruction is given to edit the user edit screen data in step S866 in FIG.

(20.4) Deletion of User When deletion is specified on the user list screen, the access right is checked in step S868 in FIG. In step S870, it is checked whether or not it is permitted. If a positive determination is made, the process proceeds to step S872. If the determination is negative, the process ends. In step S872, the user information is deleted from the user information DB 10 based on the user name number checked in the check box.

(20.5) Name designation When a name is designated on the user list screen, an access right is checked in step S874 in FIG. It is checked in step S876 whether or not it is permitted. If it is affirmation determination, it will progress to step S878. If the determination is negative, the process ends. In step S878, the user information DB 10 is searched based on the user number and the URL of the user edit screen + user edit screen set based on the link information by Javascript. In step S880, user information such as a login ID and a name is output, and an instruction is given to edit the user edit screen data shown in FIG. 67 based on the information and the user number.

(20.6) Update When update is specified on the user edit screen, the access right is checked in step S882 in FIG. It is checked in step S884 if permission has been granted. If it is affirmation determination, it will progress to step S886. If the determination is negative, the process ends. In step S886, user information such as a login ID, password, and name is registered / updated in the user information DB 10 based on the user number (in the case of new registration).

(21) Group information (21.1) Group list When the group list is designated on the user list screen and the URL of the group list screen shown in FIG. 68 is received, the access right is checked in step S900 in FIG. In step S902, it is checked whether or not it is permitted. If a positive determination is made, the process proceeds to step S904. If the determination is negative, the process ends. In step S904, the group information DB 12 is searched. In step S906, a group main shaft, an LDAP mapping name, and a group description list of group descriptions are output, and the group number + trigger Javascript program name is used as link information of these information, the group number of each row, and the name of each row. Based on this, it is instructed to edit the screen data of the group list screen shown in FIG. 68 including the definition of a check box that enables selection of each row.

(21.2) Search When a search is specified on the group list screen, an access right is checked in step S908 in FIG. In step S910, it is checked whether or not it is permitted. If it is affirmation determination, it will progress to step S912. If the determination is negative, the process ends. The group information DB 12 is searched based on the group name or LDAP mapping name input in step S912. In step S914, the matching group information is output, and the check box for selecting each row based on the group number + trigger Javascript program name as link information of the information, the group number of each row, and the name of each row. Instruct to edit the screen data of the group information list screen including the definition.

(21.3) Addition designation When addition is designated on the group list screen, an instruction is given to edit the group edit screen data shown in FIG. 69 in step S916 in FIG.

(21.4) Deletion of Group When deletion is designated on the group list screen, the access right is checked in step S918 in FIG. In step S920, it is checked whether or not it is permitted. If it is affirmation determination, it will progress to step S922. If the determination is negative, the process ends. In step S922, group information is deleted from the group information DB 12 based on the group number checked in the check box.

(21.5) Name designation When a group name is designated on the group list screen, an access right is checked in step S924 in FIG. In step S925, it is checked whether or not it is permitted. If a positive determination is made, the process proceeds to step S926. If the determination is negative, the process ends. In step S926, the group information DB 12 is searched based on the group number set by Javascript based on the link information + the URL of the group edit screen. In step S922, group information such as a group name is output, and an instruction is given to edit the group edit screen data based on the information and the group number.

(21.6) Update When update is designated on the group edit screen, the access right is checked in step S930 in FIG. In step S932, it is checked whether or not it is permitted. If a positive determination is made, the process proceeds to step S934. If the determination is negative, the process ends. In step S934, group information such as a group name, an LDAP mapping name, and a group description is registered / updated in the group information DB 12 based on the group number (in the case of new registration).

(22) Design document output (22.1) Design document output screen When the design document output is specified on the menu screen and the URL of the design document output shown in FIG. 70 is received, the access right is checked in step S950 in FIG. In step S952, it is checked whether or not it is permitted. If it is affirmation determination, it will progress to step S954. If the determination is negative, the process ends. In step S954, the system information DB 107 is searched. In step S956, the system name is output. In step S958, the subsystem information DB 108 is searched. In step S960, the subsystem name is output. In step S962, the sub application information DB 110 is searched for the subsystem. In step S964, the sub application name is output.

  In step S966, the screen information DB 112 is searched for the sub application. In step S968, the screen name is output. It is checked in step S970 if there is a next screen. If a positive determination is made, the process returns to step S962. If a negative determination is made, the process proceeds to step S972. In step S972, it is checked whether or not there is a next sub application name. If a positive determination is made, the process returns to step S962. If a negative determination is made, the process proceeds to step S974. In step S974, it is checked whether or not there is a next subsystem. If a positive determination is made, the process returns to step S958. If a negative determination is made, the process proceeds to step S976. In step S976, the table information DB 114 is searched, and a list of table names is output.

  In step S978, a list of system names, subsystem names, sub-app names, and table names is output, and based on these pieces of information, the subsystem list, screen list and table list, and table definition for each table name, Message list, item dictionary, each subsystem name, sub application list, each screen name related to sub application name, screen layout definition, screen action definition, screen item definition, screen table list and screen table related diagram, and print file type i An instruction is given to edit the design document output screen data shown in FIG. 70 including the definition of a check box that enables selection of each row of (i = 1 to n).

(22.2) Printing Execution When execution is specified on the design document output screen, the selected items checked by the check boxes in step S980 are extracted in the order of arrangement. The access right is checked for the item extracted in step S984. It is checked in step S986 whether or not it is permitted. If a positive determination is made, the process proceeds to step S988. If the determination is negative, the process ends. In step S988, design information corresponding to the check item is searched from the design information DB 8. In step S990, it is checked whether automatic generation is necessary. What needs to be automatically generated is, for example, a screen transition diagram, a table relation diagram, or the like. If a positive determination is made, the process proceeds to step S992. If a negative determination is made, the process proceeds to step S994.

  In step S992, it is automatically generated from the design information. In accordance with the print file type specified in step S996, a header record is created based on the design information such as the updater and update date, and written into the print file. In step S998, a record is created from the corresponding design information or automatically generated design information according to the layout and the print file type, and written to the print file. In step S1000, it is checked whether there is a next check item. If it is affirmation determination, it will return to step S980. If a negative determination is made, the process proceeds to step S1002. In step S1002, the print file is transferred to the terminal device 2.

  According to the present embodiment described above, it is possible to work in a browser by developing a repository management system as a Web application from a design work that has been conventionally performed on a document basis using a document creation tool.

  Further, the design information database is excellent in referenceability, and the design information can be centrally managed, so that the design work can be made more efficient. It also has a document management function and can manage all design information. Organically connect the item dictionary with screen item information and column information, automatically generate screen transition diagrams, display various aggregate information, check the consistency of input items of each design information, search the affected area, and to design information Access control and progress management. No need to print design documents or distribute design files for review, and display design information on terminal devices for review, etc., reducing man-hours without using wasted resources .

  Since the table list, subsystem list, sub application list, screen transition diagram, and table relation diagram are automatically generated, man-hours can be reduced.

DESCRIPTION OF SYMBOLS 1 Repository management system 2 # i (i = 1-n) Terminal device 4 Network 6 Repository management server 8 Design information DB
10 User information DB
12 Group information DB

Claims (14)

A repository management server that performs system design by transmitting and receiving packets including data described in a predetermined communication description language with a plurality of terminal devices connected via a network according to a predetermined communication protocol,
A system information database for storing system information about the entire system;
A subsystem information database for storing subsystem information relating to each subsystem divided into a plurality of subsystems;
A sub-application information database that stores sub-application information related to each sub-application, each of the plurality of subsystems divided into a plurality of sub-applications;
A screen information database for storing screen information in each of the sub-applications;
A table information database for storing table information related to each of a plurality of tables;
An input data extraction unit for extracting data described in the communication description language included in a packet from the terminal device;
When the data extracted by the input data extraction unit indicates a system information search request, the system information reference unit that searches the system information database and outputs system information as design information;
When the data extracted by the input data extraction unit indicates a registration or update request for system information, the system information is registered or updated in the system information database based on the data extracted by the input data extraction unit A system information registration / update unit,
When the data extracted by the input data extraction unit indicates a subsystem information search request, the subsystem information reference unit searches the subsystem information database and outputs the subsystem information as design information;
When the data extracted by the input data extraction unit indicates a subsystem information registration or update request, the subsystem information is stored in the subsystem information database based on the data extracted by the input data extraction unit. Subsystem information registration / update section to register or update;
When the data extracted by the input data extraction unit indicates a sub application information search request, the sub application information reference unit that searches the sub application information database and outputs the sub application information as design information;
When indicating that the data extracted by the input data extraction unit is a sub-application information registration or update request, based on the data extracted by the input data extraction unit, the subsystem to which the sub-application belongs to the sub-application information database. A sub application information registration / update unit for registering or updating the sub application information including information;
When the data extracted by the input data extraction unit indicates a screen information search request, the screen information reference unit that searches the screen information database and outputs the screen information as design information;
When the data extracted by the input data extraction unit indicates a screen information registration or update request, information about the sub-app to which the screen belongs to the screen information database based on the data extracted by the input data extraction unit A screen information registration / update unit for registering or updating the screen information including:
When the data extracted by the input data extraction unit indicates a table information search request, the table information reference unit that searches the table information database and outputs the table information as design information;
When the data extracted by the input data extraction unit indicates a registration or update request for table information, the table information is registered or updated in the table information database based on the data extracted by the input data extraction unit A table information registration / update unit
The design information output from the system information reference unit, the subsystem information reference unit, the sub application information reference unit, the screen information reference unit, and the table information reference unit is transferred to the terminal device based on the communication description language. Edit the screen data of the corresponding reference screen to be displayed, and input design information of the system information, the subsystem information, the sub application information, the screen information, and the table information from the terminal device based on the communication description language. An output data editing section for editing the corresponding registration / update screen data for registration or updating;
A repository management server.   The system information, the subsystem information, and the sub-application information are document information of a document related to the entire system, document information of a document related to the subsystem, document information of a document related to the sub-application, and a folder for classifying the documents. The output data editing unit displays a list of folder names on the reference screen, and edits the screen data to each folder that can be specified. The system information reference unit, the subsystem information reference unit When the folder name is designated, the sub-application information reference unit searches for document information classified by the folder name and outputs a list of document information. The output data editing unit outputs the communication description language to the communication description language. A list of document information classified by the folder based on the folder is edited in the screen data so as to be displayed on the reference screen. Repository management server according to claim 1 wherein the.   When the screen information reference unit indicates that the data extracted by the input data extraction unit is a screen table information search request indicating a relationship between the screen and a table to be referred to, updated or deleted on the screen, It includes a screen table information reference unit that searches a screen information database and outputs screen table information. The screen information registration / update unit registers or updates the screen table information with the data extracted by the input data extraction unit. A screen table information registration / update unit for registering or updating the screen table information in the screen information database, and the output data editing unit is output from the screen table information reference unit. Screen table reference screen for displaying screen table information on the terminal device based on the communication description language The screen data is edited, and the design information of the screen table information is input from the terminal device based on the communication description language, and edited into table registration / update screen data for registration or update. Repository management server.   Extracted by the item dictionary database storing each item dictionary information, the item use screen information database storing dictionary linkage information between the screen item of the screen and the item dictionary registered in the item dictionary database, and extracted by the input data extraction unit An item dictionary information reference unit that searches the item dictionary database and outputs a list of item dictionary information, when the displayed data indicates a request for definition of dictionary cooperation between the item on the screen and the item dictionary; When the data extracted by the input data extraction unit is a request for registration or update of the screen item information, and the screen item indicates that it is a request for registration or update of dictionary cooperation with the item dictionary, The item usage for registering or updating in the item usage screen information database that the screen item is dictionary-linked with the item dictionary. A screen information registration / update unit, and the output data editing unit displays a list of the item dictionaries output from the item dictionary information reference unit on the terminal device based on the communication description language, The repository management server according to claim 1, wherein each item dictionary is edited into screen data of an item reference screen that can be specified for dictionary cooperation.   An item dictionary list generation unit that searches the item dictionary database and outputs a list of item dictionary information when the data extracted by the input data extraction unit indicates that the item dictionary list is requested; A screen item number counting unit that searches a used screen information database and outputs the number of screen items having dictionary cooperation for each item dictionary; and the output data editing unit is configured to use the item dictionary based on the communication description language. Screen data of an item dictionary list screen including information specifying each item dictionary as link information that includes each item dictionary information and the number of screen items output by the list generation unit, and enables specification of the number of screen items in each row 5. The repository management server according to claim 4, which is edited as follows.   When the data extracted from the input data extraction unit indicates that the number of screen items is designated, the item use screen information database is searched, and the screen items that are dictionary-linked with the designated item dictionary are searched. An item use object list creation unit for outputting a list is further provided, and the output data editing unit is configured to list item use objects based on a list of screen items output by the item use object list generation unit based on the communication description language. The repository management server according to claim 5, wherein the repository management server edits the screen data of the screen.   An item dictionary database for storing each item dictionary information, an item use table information database for storing dictionary linkage information between the column of the table and an item dictionary registered in the item dictionary database, and extracted by the input data extraction unit When the data indicates a request for definition of dictionary cooperation between the column of the table and the item dictionary, the item dictionary database is searched, and an item dictionary information reference unit that outputs a list of item dictionary information; When the data extracted by the input data extraction unit is a request for registration or update of the table information, and the column indicates a request for registration or update of dictionary cooperation with the item dictionary, the column is Register or update that the item dictionary is linked to the item dictionary in the item use table information database. An item usage table information registration / update unit, and the output data editing unit stores a list of the item dictionaries output from the item dictionary information reference unit on the terminal device based on the communication description language. The repository management server according to claim 1, wherein the repository management server is configured to display and edit each item dictionary into screen data of an item reference screen that can be specified for dictionary cooperation.   An item dictionary list generation unit that searches the item dictionary database and outputs a list of item dictionary information when the data extracted by the input data extraction unit indicates that the item dictionary list is requested; A column number counting unit that searches a usage table information database and outputs the number of columns having dictionary cooperation for each item dictionary; and the output data editing unit generates the item dictionary list based on the communication description language The item dictionary information output by the section and the number of columns are edited into screen data of an item dictionary list screen including information for specifying each item dictionary as link information that allows designation of the number of columns in each row. Item 8. The repository management server according to item 7.   When the data extracted from the input data extraction unit indicates that the number of columns is designated, the item use table information database is searched, and a list of columns that are dictionary-linked with the designated item dictionary is displayed. An item use column list creation unit for outputting is further provided, and the output data editing unit is configured to display an item use column list screen based on the column list output by the item use column list generation unit based on the communication description language. The repository management server according to claim 8, wherein the repository management server edits the data.   When the data extracted by the input data extraction unit indicates that the request is one of a list of subsystems belonging to the system, a list of sub-applications belonging to the subsystem, a list of screens belonging to the sub-applications, and a list of tables belonging to the system, A list that searches any one of the subsystem information database, the sub application information database, the screen information database, and the table information database, and outputs a list of the subsystem list, subsystem list, screen list, and table list. And further comprising an information generation unit, wherein the output data editing unit is capable of selecting each row of the list output by the list information generation unit based on the communication description language using a check box, and a subsystem for each row of the list , Sub-apps, screens and Repository management server according to claim 1, wherein the editing on the screen data of the list screen that allows specify either of Buru.   When the data extracted by the input data extraction unit indicates that any row of the subsystem, sub-application, screen, and table of each row is designated, the subsystem information reference unit, the sub-application information reference unit, the screen Any of the information reference unit and the table information reference unit searches the subsystem information database, the sub application information database, the screen information database, and the table information database, and designates the specified subsystem, sub application, Outputs any design information of the corresponding subsystem information, sub application information, screen information and table information of the screen and table, and the output data editing unit is any of the subsystem information, sub application information, screen information and table information. The design information, the communication description Repository management server according to claim 10, wherein the editing screen data of the corresponding screen displayed on the terminal device based on.   Refer to the user information database that stores user information about users, whether each group has administrator authority related to the right to manage the system, development authority related to the right to edit the design document, and the design document. A group information database for storing presence / absence of reference authority related to the right to perform, the corresponding user information registered in the user information database and the group information database, and the group of the group to which the requested user belongs The requesting user determines the presence or absence of administrator authority, the presence or absence of the development authority, and the presence or absence of the reference authority, and the requesting user determines that the system information database, the subsystem information database, the sub application information database, the screen information database, and the Right to access table information database Further repository management server according to claim 1, wherein equipped whether the determined access right check section has.   When the data extracted by the input data extraction unit indicates a design document output request, the system information database, the subsystem information database, and the table information database are searched, and the system name, subsystem name, and A design document output information generation unit that outputs a list of table names is further provided, and the output data editing unit includes system information, subsystem list, screen list and table list, table information for each table name, and sub-application for each subsystem. The repository management server according to claim 1, wherein the repository information is edited into screen data of a design information output screen that enables selection of any one of the screen information and a plurality of output formats for the list information and each sub-application.   When the data extracted by the input data extraction unit indicates a request to execute design document printing, the system information database, the subsystem database, the sub application database, and the screen information corresponding to each of the selected items 14. The repository according to claim 13, further comprising a print file generation unit that searches either the database or the table information database, reads design information, and generates a print file according to a predetermined layout and the selected output format. Management server.

Images