JP2007249561A - Display system and program of screen transition diagram - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To display screen transition from one design drawing, a calling order of a series of components called by a certain screen, and a calling order of components of the whole system. <P>SOLUTION: The display screen comprises: three dimensional screen transition diagram data; display control data; a three dimensional screen transition diagram editing section; and a three dimensional screen transition diagram display section. Three dimensional positions of the components are determined by a definition of the calling order of the series of components. Change of visual line is changed by updating the display control data. The screen transition diagram, the series of the calling order and the calling order of the whole system are displayed, respectively, in a front view, a side view, and a top view of the design drawing. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a display system and program related to component call in a screen transition diagram in an application development system.

Currently, with the spread of the Internet, a great number of applications that are used through Web browsers have been developed. Such an application is called a Web application.
In recent web application development, it has become common to develop components by dividing them into functional layers called layers in order to clarify the dependency relationships between components and loosen the coupling between components. .

FIG. 62 is a diagram showing a configuration example of a general Web application. A screen layer (6201) including components that define screen transitions and display contents, an Action layer (6202) including components that process requests, A BL (Business Logic) layer (6203) composed of components that perform specific business processing, a DAO (Data Access Object) layer (6204) that manipulates data, and a DB (Data Base) composed of components that represent data ) Layer (6205). The component of the screen layer (6201) is the lowest layer component.
The lower layer component can be used by calling the processing of the upper layer component.
The arrows in the figure indicate the calling relationship of the components. For example, screen A (6207) in the figure indicates that Action1 (6208) is called.

In a Web application configured in this way, components with the same layer often have a program structure with similar processing. Therefore, a method is often used in which necessary information is defined in a design drawing, and a source code as a framework is automatically generated by inputting a design document defining a calling relationship and a template defining a source code generation rule as inputs.
62 of FIG. 62 shows an example of a tool for generating a component of the screen layer (6201). In this tool, a drawing called a screen transition diagram composed of a screen (6210) and a screen transition (6211) is defined. Generate source code that implements the specified screen transition based on the contents.

The following patent document 1 is given as a known technical document related to the present invention.
JP-A-7-219754

By the way, each component of a Web application is designed with different tools because the design target is the contents of the screen or the contents of processing for each layer. In addition, since the implementer directly implements the call relationship between layers in the automatically generated code, the call relationship of the entire system often does not remain as a design drawing later. Therefore, it was necessary to compare the design drawings for each layer or to read the source code directly in order to grasp the range of influence of the modification on the component.
This can be solved by describing the component call relationship of the entire system in another design drawing. However, since the number of components becomes enormous, it is very troublesome to describe each call relationship. Further, since the figure becomes complicated, there are problems that it is difficult to understand the screen transition that is important information and the calling order of a series of components that a certain screen calls.

  The purpose of the present invention is to display screen transitions from a single design drawing, the calling order of a series of components called by a screen, and the calling order of components of the entire system in an easy-to-understand manner, and facilitate the calling relationship of the components of the entire system. It is in the display method and program of the component call relation of the screen transition diagram that can be grasped.

In order to achieve the above object, a screen transition diagram display system according to the present invention includes a component and a plurality of hierarchies that define processing for operations on each screen in a screen transition diagram composed of a plurality of screens constituting an application. A system for displaying a call relationship with a screen,
For each screen constituting the screen transition diagram, screen definition information such as a screen name corresponding to an input operation on the screen transition diagram definition screen is received, and the position of the three-dimensional coordinate system corresponding to the input position on the definition screen as a display attribute Component definition information such as a component name corresponding to an input operation on the component definition screen for a screen definition means for generating a screen object having information and a predetermined three-dimensional shape, and a component over a plurality of layers for each generated screen The component definition means for generating a component having position information of a three-dimensional coordinate system corresponding to the input position on the definition screen as an acceptance and display attribute and predetermined three-dimensional shape information, and the calling order of the generated component calling order Call from the input means on the definition screen Component call order definition means for receiving call order information and generating a call line object having position information of a three-dimensional coordinate system corresponding to an input position on the definition screen as display attributes and predetermined three-dimensional shape information; For the screen transition of each screen defined by the definition means, the screen transition definition information is received from the input means on the screen transition definition screen, and the position information of the three-dimensional coordinate system corresponding to the input position on the definition screen is defined as a display attribute. Screen transition definition means for generating a screen transition object having 3D shape information, and the components and objects defined by the screen definition means, component definition means, component call order definition means, screen transition definition means, and 3D screen transition diagram data First storage means for storing the first storage and the first storage The three-dimensional screen transition diagram data stored in the stage is read out, and the screen, component, and calling relationship defined by each means are based on the three-dimensional position information and the three-dimensional shape information that each object and component hold as display attributes. And display means for displaying on a display screen as a screen transition diagram viewed from a specified viewpoint in a three-dimensional space.

In addition, this is a program that causes a computer to function as a system that displays a calling relationship between a component and a plurality of hierarchies that define processing for operations on each screen in a screen transition diagram including a plurality of screens constituting an application. And
Computer
For each screen constituting the screen transition diagram, screen definition information such as a screen name corresponding to an input operation on the screen transition diagram definition screen is received, and the position of the three-dimensional coordinate system corresponding to the input position on the definition screen as a display attribute Component definition information such as a component name corresponding to an input operation on the component definition screen for a screen definition means for generating a screen object having information and a predetermined three-dimensional shape, and a component over a plurality of layers for each generated screen The component definition means for generating a component having position information of a three-dimensional coordinate system corresponding to the input position on the definition screen as an acceptance and display attribute and predetermined three-dimensional shape information, and the calling order of the generated component calling order Call from the input means on the definition screen Component call order definition means for receiving call order information and generating a call line object having position information of a three-dimensional coordinate system corresponding to an input position on the definition screen as display attributes and predetermined three-dimensional shape information; For the screen transition of each screen defined by the definition means, the screen transition definition information is received from the input means on the screen transition definition screen, and the position information of the three-dimensional coordinate system corresponding to the input position on the definition screen is defined as a display attribute. Screen transition definition means for generating a screen transition object having 3D shape information, and the components and objects defined by the screen definition means, component definition means, component call order definition means, screen transition definition means, and 3D screen transition diagram data First storage means for storing the first storage and the first storage The three-dimensional screen transition diagram data stored in the stage is read out, and the screen, component, and calling relationship defined by each means are based on the three-dimensional position information and the three-dimensional shape information that each object and component hold as display attributes. It is characterized by functioning as a display means for displaying on a display screen as a screen transition diagram that can be seen from a specified viewpoint in a three-dimensional or three-dimensional space.

  According to the present invention, a screen transition in one design drawing, a calling order of a series of components called by a certain screen, and a calling order of components of the entire system are three-dimensionally displayed. It is possible to easily grasp the calling order of the components and the calling order of the components of the entire system. For example, when the component needs to be corrected, the correction range can be easily determined.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a system configuration diagram showing an embodiment of the present invention. A computer (104) having a keyboard (101) and a mouse (102) as input devices and a display device (103) is connected to an operation system ( 105), a three-dimensional screen transition diagram editing program (106), and a source code editing program (107).
On the display device (103), a window (108) of the three-dimensional screen transition diagram editing program (106) and a window (109) of the source code editing program (107) are displayed by the operation system (105).
The developer (110) operates the three-dimensional screen transition diagram editing program (106) using the keyboard (101) and the mouse (102), and referring to the display window (108), the source code editing program (107) Implement the source code.

  FIG. 2 is a functional block diagram showing a detailed configuration of the three-dimensional screen transition diagram editing program (106). The program (106) includes a three-dimensional screen transition diagram data storage unit (201) and a generation template storage unit (202). ), A display control data storage unit (203), a three-dimensional screen transition diagram display unit (204), a selected object determination unit (205), a three-dimensional screen transition diagram editing unit (206), and a source code generation unit (207).

The three-dimensional screen transition diagram data storage unit (201) has a function of reading and managing the three-dimensional screen transition diagram data of the external storage device.
The display control data storage unit (203) has a function of managing control data for displaying the three-dimensional screen transition diagram data (201) such as a line of sight and a drawing flag.
The generation template storage unit (202) has a function of managing a template for generating a source code from the three-dimensional screen transition diagram data stored in the three-dimensional screen transition diagram data storage unit (201).

  The three-dimensional screen transition diagram display unit (204) reads the three-dimensional screen transition diagram data stored in the three-dimensional screen transition diagram data storage unit (201), and displays screen transition diagram display means (208) and component call diagram display means. (209) The display control data stored in the display control data storage unit (203) is updated using the whole component call diagram display means (210). Then, the window drawing unit (211) is used to display the three-dimensional screen transition diagram data on the window (108) of the display device (103).

The window drawing unit (211) includes a three-dimensional object drawing unit (212) and a label drawing unit (213).
The three-dimensional object drawing means (212) has a function of drawing the three-dimensional screen transition diagram data on the window (108) with the display control data stored in the display control data storage unit (203) as an input.
The label drawing means (213) has a function of drawing a label character string held by the three-dimensional object in the vicinity of the three-dimensional object drawn in the window (108).

The selected object determination unit (205) has a function of acquiring a position where a mouse event occurs in the window and determining a selected three-dimensional object and a position in a three-dimensional space.
The result of the selected object determination unit (205) is passed to the three-dimensional screen transition diagram editing unit (206).

The 3D screen transition diagram editing unit (206) is a part for editing the 3D screen transition diagram data stored in the 3D screen transition diagram data storage unit (201). ) And a component call diagram editing unit (215).
The screen transition diagram editing unit (214) is a part that operates on the display contents of the screen transition diagram display means (208). The screen definition means (216), the calling order definition means (217), and the screen transition definition Means (218).

The component call diagram editing unit (215) is a part for operating the display contents of the component call diagram display means (209), and includes a component definition means (219).
The component definition means (219) calls the component position determination means (215) in an internal process.

  The source code generation unit (207) has a function of generating 3D screen transition diagram data for which editing has been completed and a source code serving as a framework of an application with a generation template as an input.

FIG. 3 is a configuration diagram of 3D screen transition diagram data stored in the 3D screen transition diagram data storage unit (201). This data includes a diagram name (301), a screen object group (302), Screen transition object group (303), Action object group (304), BL object group (305), DAO object group (306), DB object group (307), call line object group (308), It consists of a layer boundary object group (309) and a call order data group (310).
Among these, data excluding the call order data group (310) has a three-dimensional position and shape, and is particularly called a three-dimensional object (311).
In addition, the individual data of the Action object group (304), BL object group (305), DAO object group (306), and DB object group (307) are particularly referred to as components (312).
In the following, screen object group (302), screen transition object group (303), Action object group (304), BL object group (305), DAO object group (306), DB object group (307), call line For each object constituting the object group (308), layer boundary object group (309), and call order data group (310), a screen object (302d), a screen transition object (303d), an Action object (304), Subscript “d” is added such as BL object (305d), DAO object (306d), DB object (307), call line object (308d), layer boundary object (309d), and call order data (310d). ,"object To distinguish between "referred to.

As shown in FIG. 4, the three-dimensional object (311) includes, as common attribute items, an object ID (401), a label (402), a color (403), a coordinate transformation matrix (404), a shape ( 405).
The object ID (401) is composed of an integer value, and a unique one of the three-dimensional object (311) is calculated and stored when the three-dimensional object (311) is generated.
The label (402) is composed of an arbitrary character string.
The color (0403) is composed of numerical data composed of R, G, B and transparency.
The coordinate transformation matrix (404) is composed of determinant data that transforms coordinate data expressed in the local coordinate system into coordinate data in the world coordinate system.
The shape data (405) is composed of coordinate data of each vertex of the three-dimensional object (311).

As shown in the explanatory diagram of FIG. 5, the local coordinate system is a coordinate system that independently represents the shape of the three-dimensional object (501), and the world coordinate system is a three-dimensional object in which the three-dimensional object (501) is arranged. A coordinate system that defines a space.
The three-dimensional object (501) arranged in the three-dimensional space defined by the world coordinate system is converted into a two-dimensional figure by projection and displayed on the window (108) of the display device (103).
The projection plane coordinate system defines the projection plane for projecting a three-dimensional object placed in the world coordinate system, and the three-dimensional object (two-dimensional projection image) projected on the projection plane connects the viewpoint and the gaze point. It changes according to the line of sight and the direction of the upward vector of the projection plane.
When displaying a 3D object in a window, set the field of view that can be seen from the viewpoint, but set the range that can be seen from the viewpoint in front of the projection plane at the position of the front plane, and the range that can be seen in the depth direction from the back plane. Set at the position. A three-dimensional space of a rectangular parallelepiped on the front plane and the rear plane is a view volume.

In the embodiment according to the present invention, as shown in the figure, the positions of the projection plane and the back plane are determined based on the set line of sight and the upward vector, and the three-dimensional object (501) defined in the local coordinate system is determined. Performs parallel projection on the projection plane in the world coordinate system.
A projection image obtained by parallel projection is displayed by being mapped to the coordinate system of the window. Also, the label possessed by each three-dimensional object is acquired and drawn in the vicinity thereof.

FIG. 6 is a configuration diagram of display control data stored in the display control data (203). This data includes a viewpoint (601), a gazing point (602), a projection plane upward vector (603), and a drawing flag. It consists of a group (604).
The viewpoint (601) and the gazing point (602) are composed of coordinate data in the global coordinate system, and the projection plane upward direction vector (602) is composed of vector data in the global coordinate system.
The drawing flag (604) exists for each generated three-dimensional object (311) and is configured as a boolean type. It is assumed that the three-dimensional object (311) whose drawing flag (604) is false is not drawn in the window (108) and cannot be selected.

FIG. 7 is a diagram illustrating an example of the data structure of the screen object (302d).
The screen object (302d) represents a component of the screen layer, and holds a path (701) and a screen name (702) in addition to the common attributes shown in FIG. The shape (405) of the screen object (302d) is a cuboid, and the label (402) stores the same as the screen name (702).

FIG. 8 is a diagram illustrating an example of the data structure of the Action object (304d).
The Action object (304d) represents a component of the Action layer, and holds a class name (801), an argument (802), and a result ID (803) in addition to the common attributes shown in FIG.
A plurality of arguments (802) and result IDs (803) may be held by one Action object (302d), and there may be no data for the arguments (802). Note that the shape (405) of the Action object (304d) is a sphere, and the label (402) stores the same as the class name (801).

FIG. 9 is a diagram illustrating an example of the data structure of the BL object (305d).
The BL object (305d) represents a component of the BL layer, and in addition to the common attributes shown in FIG. 4, a class name (901), a method name (902), an argument (903), and a return value (904) ).
A plurality of arguments (903) may be held by one BL object (305d). Also, there may be no data. The shape (405) of the BL object (305d) is a sphere, and the label (402) stores a character string in which the class name (901) and the method name (902) are concatenated with sharp characters.

FIG. 10 is a diagram illustrating an example of the data structure of the DAO object (306d).
The DAO object (306d) represents a DAO layer component, and in addition to the common attributes shown in FIG. 4, a class name (1001), a method name (1002), an argument (1003), and a return value (1004). ).
A plurality of arguments (1003) may be held by one DAO object (306d). Also, there may be no data. It is assumed that the shape (405) of the DAO object (306d) is a sphere, and a character string in which the class name (1001) and the method name (1002) are concatenated with sharp characters is stored in the label (402).

FIG. 11 is a diagram illustrating an example of the data structure of the DB object (307d).
The DB object (307d) represents the components of the DB layer. In addition to the common attributes shown in FIG. 4, the DB name (1101), URL (1102), table name (1103), and column name (1104) ). One DB object (307) may hold a plurality of column names (1104). It is assumed that the shape (405) of the DB object (307d) is a cube, and a character string in which the DB name (1101) and the table name (1103) are concatenated with a period character is stored in the label (402).

FIG. 12 is a diagram illustrating an example of the data structure of the screen transition object (303d).
The screen transition object (303d) holds a transition source screen (1201), a result ID (1202), and a transition destination screen (1203) in addition to the common attributes shown in FIG.
In the transition source screen (1201) and the transition destination screen (1203), the object ID (401) of the corresponding screen object (302d) is stored. In addition, the result ID (803) of the Action object (304d) is stored in the result ID (1202).
The transition destination screen (1203) may be undefined depending on the editing stage.
The shape (405) of the screen transition object (303d) is an arrow extending from the position of the transition source screen (1201) to the transition destination screen (1203), and the result ID (1202) is displayed on the label (402). Shall be stored.

FIG. 13 is a diagram illustrating an example of the data structure of the call line object (308d).
The call line object (308d) holds a start object (1301), an end object (1302), and a call order (1303) in addition to the common attributes shown in FIG.
In the start object (1301) and the end object (1302), the object ID (401) of the corresponding component (312) is stored.
In the call order ID (1303), the ID of the call order data (310) is stored.
The shape (405) of the call line object (308d) is an arrow extending from the position of the start object (1301) to the end object (1302), and a blank character is stored in the label (402). .
The layer boundary object (309) exists for each layer and is represented by a plate-like plane whose position is fixed.
Each component (312) is arranged around the layer boundary object (309) of the corresponding layer.

FIG. 14 is a diagram illustrating an example of a data structure of the call order data (310d).
The call order data (310d) includes a call order ID (1401), a screen ID (1402), an Action ID (1403), a BL ID (1404), a DAO ID (1405), and a DB ID (1406). Hold.
The call order ID (1401) is composed of an integer value, and a unique value in the call order data group is calculated and stored at the time of generation. One call order data (310d) represents a series of call orders, and the object ID (401) of the target component is stored for each layer.
For example, in the example of FIG. 14, the Action object (304) whose object ID (401) is “3” calls the BL object (305) whose object ID (401) is “4” and “5”, respectively. Yes.

FIG. 15 illustrates the relationship between the three-dimensional object (311) arranged in the world coordinate system by the coordinate transformation matrix (404) and the content displayed in the window (108) by the three-dimensional screen transition diagram editing program (106). FIG.
In the figure, reference numeral 1501 denotes an arrangement example of the three-dimensional object (311), and reference numerals 1502, 1503, and 1504 denote examples of windows (108) displayed by the three-dimensional screen transition diagram editing program (106).
The line of sight in the present embodiment is parallel to any of the Zw axis positive direction (1505), the Xw axis negative direction (1506), and the Yw axis negative direction (1507) of the world coordinate system.
In this embodiment, a diagram (front view) projected along the Zw-axis positive direction (1505) is referred to as a screen transition diagram, and a diagram (side view) projected along the Xw-axis negative direction (1506) is referred to as a component call diagram. A figure (top view) projected along the negative Yw axis direction (1507) is called an overall component projection figure.

A screen transition diagram (1502) shows a screen transition relationship, and includes a screen object (1508) and a screen transition object (1509).
A component call diagram (1503) shows a series of call orders called by the screen, and includes a screen object (1510), an Action object (1511), a BL object (1512), a DAO object (1513), and a DB object. (1514), a call line object (1515), and a layer boundary object (1516).
The entire component call diagram (1504) shows the component call order of the entire system, and includes a screen object (1516), an Action object (1518), a BL object (1519), a DAO object (1520), and a DB object. (1521), a call line object (1522), and a layer boundary object (1523).

FIG. 16 is a flowchart showing an overall work procedure in the Web application development work using this system.
First, the developer (110) starts the three-dimensional screen transition diagram editing program (106) (step 1601), and designates the new creation of the three-dimensional screen transition diagram data by designating the diagram name (301) ( Step 1602).
Then, the three-dimensional screen transition diagram editing program (106) displays an initial screen for newly creating a screen transition diagram (1502) on the window (108) using the screen transition diagram display means (208) (step 1603). At this stage, no screen object is displayed in the screen transition diagram (1502) and is in a blank state.
Next, the developer (110) defines the screen object (1508) using the screen definition means (216) (step 1604).
When the definition of one screen object (1508) is completed, the developer (110) displays the component call diagram (1503) using the component call diagram display means (209) (step 1605).
Next, the developer (110) creates a call order data group (310) using the call order definition means (217), and displays the component call chart (1503) using the component call chart display means (209). Then, the component definition means (219) is used to define a series of components called by the screen object (1510) (step 1606).

When the definition of the calling order is completed, the developer (110) returns the display to the screen transition diagram (1502) using the screen transition diagram display means (208) (steps 1607 and 1608), and defines the screen object (1508). to continue.
When the definition of all the screen objects (1508) and the call order data (310) is completed (step 1609), the developer (110) defines the screen transition (1509) using the screen transition definition means (218) ( Step 1610).
When the definition of all the screen transitions (1509) is completed, the developer (110) uses the source code generation unit (207) to generate source code that is a framework of the application (step 1611).

  Next, the developer (110) uses the whole component call diagram display means (210) to display the whole component call diagram (1504) in the window (108) (step 1612). Further, a screen transition diagram (1502) and a component call diagram (1503) are also displayed as necessary. Then, the developer (110) implements specific processing for the source code generated by the source code editing program (107) with reference to the displayed content (step 1613). When the mounting is completed, the development ends (step 1614).

FIG. 17 is a flowchart showing the processing procedure of the screen transition diagram display means (208).
First, all the drawing flags (604) of the display control data in the display control data storage unit (203) are initialized with false (step 1701).
Next, the drawing flags (604) of all screen objects (302d) are set to true (step 1702).
Next, the drawing flags (604) of all the screen transition objects (303d) are set to true (step 1703).
Next, the direction of the line of sight is set to the Zw-axis positive direction so that the front view is displayed, and the upward vector of the projection plane is set to the Yw-axis positive direction (step 1704). Then, the three-dimensional object (311) in which the drawing flag (604) is true is drawn on the window (108), and the process ends (step 1705).

FIG. 18 is a flowchart showing the processing procedure of the component call diagram display means (209).
First, all the drawing flags (604) of the display control data in the display control data storage unit (203) are initialized with false (step 1801).
Next, the drawing flag (604) of the layer boundary object (309d) is updated with true (step 1802).
Next, one call order data (310d) designated by the developer (110) is acquired (step 1803).
Next, the three-dimensional object (311) referred to by the acquired call order data (310d) is acquired, and each drawing flag (604) is updated with true (step 1804).
Next, the call order ID (1401) is acquired from the selected call order data (310d), and the drawing flag (604) of the call line object (308d) with the matching ID (1303) is updated with true (step 1805). ).
Next, the line-of-sight direction is set to the Xw-axis negative direction and the on-projection vector is set to the Yw-axis positive direction so that the side view is displayed (step 1806). Then, the three-dimensional object (311) in which the drawing flag (604) is true is drawn on the window (108), and the process ends (step 1807).

FIG. 19 is a flowchart showing the processing procedure of the overall component call diagram display means (210).
First, all the drawing flags (604) of the display control data in the display control data storage unit (203) are initialized with false (step 1901).
Next, the drawing flag (604) of the layer boundary object (309d) is updated with true (step 1902).
Next, one call order data (310d) is acquired.
Next, the three-dimensional object (311) referred to by the acquired call order data (310d) is acquired, and each drawing flag (604) is updated with true (steps 1903 and 1904).
Next, the call order ID (1401) is acquired, and the drawing flag (604) of the call line object (308d) whose ID (1303) matches is updated with true (step 1905).
The above processing is performed for all the calling sequence data (310d) (step 1906).
Next, the direction of the line of sight is set to the Yw-axis negative direction and the projection plane upward vector is set to the Z-axis negative direction so as to display the top view (step 1907). Then, the three-dimensional object (311) in which the drawing flag (604) is true is drawn on the window (108), and the process ends (step 1908).

FIG. 20 is a flowchart showing the processing procedure of the screen definition means (216).
First, the values of the positions Xw and Yw in the global coordinate system are acquired from the position (X, Y) in the window designated by the developer (110) using the selected object determination unit (205) (steps 2001 and 2002).
Next, a new creation screen is displayed to the operator (110), and an input of a path and a screen name is accepted (step 2003). If the OK button is operated (step 2004), the screen object (302d) is generated and stored based on the input content (step 2005, 2006), and the center position in the global coordinate system is set to (Xw, A coordinate transformation matrix (405) defined as Yw, 0) is calculated and stored (step 2007).

FIG. 21 is a flowchart showing the processing procedure of the calling order defining means (217).
First, the screen object (302d) designated by the developer (110) is acquired using the selected object determination unit (205) (step 2101).
Next, an operation menu for the screen (1508) is displayed, and a new input or selection of the calling order is selected or a developer input is accepted (step 2102).
When the developer (110) designates the new creation of the calling order (step 2103), the calling order data (310d) is newly created (step 2104), and the object ID (401) of the selected screen object (302) is set. The data is stored in the calling order data (310d) (step 2105).

The component call diagram (1503) is displayed using the component call diagram display means (209), and the definition of the component (311) is accepted (step 2106).
In step 2103, when the developer (110) instructs selection of the calling order, all the calling order data (310d) is acquired from the three-dimensional screen transition diagram data stored in the three-dimensional screen transition diagram data (201). Then, the list is displayed on the selection window to accept input (step 2107).
When the developer (110) selects any of the call order data (310d) and presses the OK button (step 2108), the selected call order data (310d) is acquired (step 2109), and the component call diagram display is performed. The component call diagram (1503) is displayed using the means (209) and the definition of the component (311) is accepted (step 2106).

FIG. 22 is a flowchart showing the processing procedure of the component definition means (219).
First, the layer boundary object (310d) designated by the developer (110) is acquired using the selected object judgment unit (205), and the designated layer is discriminated (step 2201).
Next, an operation menu for the layer is displayed, and a developer's input of whether to newly create or select a component is accepted (step 2202).
When the developer (110) designates new creation (step 2203), a new creation screen for a component corresponding to the layer is displayed to accept input (step 2204). If the OK button is operated, a component (312) is generated based on the input content (steps 2205 and 2206), and its object ID (401) is acquired (step 2207).

Next, with reference to the calling sequence data (310d) being edited, it is determined whether the component (312) has already been defined in the designated layer (step 2208).
If the component (312) has already been defined, the call order data (310d) is newly created, and the data before the corresponding layer is duplicated (step 2209). Then, the object ID (401) of the newly created component (312) is stored in the corresponding layer (step 2210).
Then, the coordinate transformation matrix (404) of the existing component (312) and the newly created component (312) in step 2206 is updated using the component position determining means (215) (step 2211), and the newly created component A call line object (308d) for (312) is generated and the process ends (step 2212).

If the component (312) does not exist in the corresponding layer (step 2208), the object ID (401) of the component (312) newly created in step 2206 is stored in the corresponding layer of the calling sequence data (310d) being edited ( Step 2210).
Then, the coordinate transformation matrix (404) of the newly created component (312) is determined using the component position determining means (215) (step 2211), and a call line object (308d) for the newly created component is generated. The process ends (step 2212).

On the other hand, in step 2203, when the developer (110) chooses to select a component instead of creating a new one (step 2203), a selection screen for the corresponding layer is created from all the components (312), displayed, and selected. Is received (step 2213). If the component is selected and the OK button is operated (step 2214), the object ID (401) of the selected component (312) is acquired (step 2215).
Next, with reference to the calling order data (310d) being edited, it is determined whether the component (312) has already been defined in the designated layer (step 2216).

If the component (312) has already been defined, the call order data (310d) is newly created, and the data before the corresponding layer is duplicated (step 2217). Then, the object ID (401) of the component (312) selected in step 2215 is stored in the corresponding layer (step 2218).
Then, the calling sequence data (310d) including the selected component (312) is referred to, and the subsequent layers are copied (step 2219). Then, a call line object (308) for the updated call order data (310d) is generated and the process ends (step 2220).

  If the component (312) does not exist in the corresponding layer (step 2216), the object ID (401) of the selected component is stored in the corresponding layer of the calling order data (310d) (step 2218). Then, the call order data (310d) including the selected component (312) is referred to, and the subsequent layers are copied (step 2219). Then, a call line object (308d) is generated for the component (312) selected in step 2215 and the component (312) immediately before the corresponding layer, and the process ends (step 2220).

FIG. 23 is a flowchart showing details of a processing procedure for copying the calling sequence data of the corresponding layer and subsequent layers in step 2219 from the calling sequence data of the selection destination.
First, data including the object ID (401) of the component (312) selected in step 2215 is acquired from all the calling order data (310d) (step 2301).
Next, the object ID (401) after the corresponding layer is copied from the acquired call order data (310d) to the call order data being edited (step 2302).
Then, it is determined whether there is any other calling order data (310d) including the object ID of the selected component (312) (step 2303). If there is another calling order data (310d), the calling order data (310d) is newly created ( Steps 2304) and 2301 and 2302 are executed. When there is no remaining call order data (310d), the process ends (step 2303).

FIG. 24 is a flowchart showing the processing procedure of the component position determining means (220) executed in step 2211.
First, the component Cp of the previous layer is acquired from the calling order data (310d) being edited (step 2401). Next, the center position P in the global coordinate system of Cp is acquired from the coordinate transformation matrix (404) of the component Cp (step 2402).
Next, the center position L in the global coordinate system is acquired from the coordinate transformation matrix (404) of the selected layer boundary object (309d) (step 2403).
Next, it is determined whether or not the existing component (312) exists in the corresponding layer of the calling order data (310d) being edited (step 2404). If there is, the center position of Cp is set to (Px-α, Py). , Lz), the coordinate transformation matrix (404) is updated (steps 2405 and 2406).
Here, α is an arbitrary constant. Also, the coordinate transformation matrix (404) is calculated and stored with the center position of the newly created component Cn being (Px + α, Py, Lz) (steps 2407 and 2408).
If there is no existing component (312) in the corresponding layer of the calling order data (step 2404), the coordinate transformation matrix (404) is calculated with the center position of the newly created component Cn as (Px, Py, Lz). (Steps 2409 and 2408).

FIG. 25 is a flowchart showing details of the calling line object generation processing procedure in steps 2212 and 2220.
First, call order data (310d) being edited is acquired (step 2501).
Next, the object ID (0410) of the component Cp of the previous layer is acquired from the calling order data (310d) and stored in the start object (1301) (see FIG. 13) (step 2502).
Next, the object ID (410) of the component Cn of the corresponding layer is acquired from the call order data (310d) acquired in step 2501, and stored in the end object (1302) (see FIG. 13) (step 2503).
When the calling order data (310d) is newly created in step 2209 or step 2217, the same processing is performed for the calling order data (step 2504).

FIG. 26 is a flowchart showing the processing procedure of the screen transition defining means (208).
When the definition of the series of call order data (310d) is completed (step 2601), the screen ID (1402) and Action ID (1403) are acquired from the defined call order data (310d) (steps 2602 and 2603).
Next, the result ID (803) is acquired from the Action object (304d) referenced by the Action ID (step 2604).
Next, from all the screen transition objects (303d), it is confirmed whether there is a screen object obtained by the transition source screen (1201) and the result ID (1202), and there is no match with the result ID. (Step 2605) generates a screen transition object (303d) and stores it in the transition source screen (1201) and the result ID (1202), respectively (Step 2606).
The above processing is performed for all result IDs (803) (step 2607).
Next, the created screen transition object (303d) is displayed on the screen transition diagram (1502) (step 2608).
If there is a screen transition object (303d) whose transition destination screen (1203) is undefined (step 2609), the operation of the developer (110) is accepted (step 2610).
Then, according to the instruction from the developer (110), the object ID (0402) of the screen object (302d) corresponding to the transition destination screen (1203) is stored (step 2611).
The above processing is performed for all screen transition objects (303d) (step 2609).

27 to 59 show display examples of the processing flows described so far.
As shown in FIG. 27, the figure divided into four represents the relationship between the position of the three-dimensional object in the global coordinate system and the content displayed in the window (108), and 2702 is a front view of the global coordinate system. 2703 is a side view and 2704 is a top view. These contents are for explanation and are not displayed in the actual window (108). A drawing located at the upper right like 2701 shows a display example of the window (108).

FIG. 27 shows an example of an initial screen when a three-dimensional screen transition diagram is activated (step 1601) and three-dimensional screen transition diagram data is newly created (step 1602).
The developer (110) clicks an arbitrary part of the window (2701) to display an operation menu (2705).
In the operation menu, a figure name (2706) and a new screen object creation (2707) item are displayed. At this time, there is no three-dimensional object (0311) (2702, 2703, 2704). Note that the arrow (2708) of the window indicates the mouse cursor.
When a new screen creation is selected from the operation menu, a new screen creation window is displayed on the screen display device (103) (step 2003).

FIG. 28 shows an example of a new screen creation window.
The new screen creation window includes a field for inputting a path (2801), a field for inputting a screen name (2802), and an OK button (2803). When an OK button (2803) is pressed by a mouse operation, the input path (2801) is stored in (701) of FIG. 7 constituting the screen object data, and the input screen name (2802) is stored in (702). Stored (step 2006).
When a screen object is generated by pressing the OK button (2803), the three-dimensional screen transition diagram editing program (106) draws the screen object in the window (108) according to step 1702 of the screen transition diagram display means (209).

FIG. 29 shows a state after a new screen is created, and 2904 shows an example of a screen object displayed in a window. Reference numerals 2901, 2902, and 2903 denote positions of the generated screen object (302) in the global coordinate system.
When the created screen object is selected by a mouse operation, a screen object operation menu is displayed (step 2102).

FIG. 30 shows an example of the operation menu of the screen object. The operation menu (3001) of the screen is obtained by selecting the screen name (3002), creating a new calling order (3003), and selecting the calling order (3004). Composed. At this stage, since the calling order data has not yet been created, the calling order selection (3004) is inactive and cannot be selected.
When a new call order creation (3003) is selected, steps 2204 to 2206 are performed, and a component call diagram (1503) is displayed by the component call diagram display means (0209).

FIG. 31 shows a display example immediately after designating a new call order (3003), and displays the screen object (3101) and the side surface of the layer boundary object (3102).
When a layer boundary is selected in the component call diagram (1503), an operation menu corresponding to the layer is displayed.

FIG. 32 shows an example of an operation menu for the Action layer (3202). The operation menu (3202) includes a layer name (3203), a new Action object creation (3204), and an Action object selection (3205). The
Since no other Action object is defined at this stage, the Action object selection (3205) is inactive and cannot be specified.
When a new action object creation (3204) is selected, a new action object creation window is displayed according to step 2204 to accept the input from the developer.

FIG. 33 shows an example of a new action object creation window, a column for inputting a class name (3301), a column for specifying an argument (3302), a column for specifying a result ID (3303), and an OK button (3304). ).
When necessary information is input and the OK button (3304) is pressed, an Action object is newly generated in accordance with Step 2206, and the Action object generated in accordance with the component call diagram display means (209) is displayed.

  In FIG. 34, 3401, 3402, and 3403 indicate positions of the created Action object in the global coordinate system, and 3404 indicates a display example of the Action object.

FIG. 35 shows an example of the BL layer operation menu. The BL layer (3501) operation menu (3502) includes a layer name (3503), a new BL object creation (3504), and a BL object selection (3505). Consists of
Since no other BL object is defined at this stage, BL object selection (3505) is inactivated and cannot be specified.
When a new BL object creation (3504) is selected, a new BL object creation window is displayed according to step 2204 to accept the input of the developer.

FIG. 36 shows an example of a new BL object creation screen. A field for inputting a class name (3601), a field for inputting a method name (3602), a field for specifying an argument (3603), and a return value are specified. Column (3604) and an OK button (3605).
When necessary information is input and the OK button (3605) is pressed, a BL object is newly generated according to step 2206, and the generated BL object is displayed according to the component call diagram display means (209).

  37, 3701, 3702, and 3703 in FIG. 37 indicate positions of the created BL object in the global coordinate system, and 3704 indicates a display example of the BL object.

FIG. 38 shows an example of the DAO layer operation menu. The BAO layer (3801) operation menu (3802) includes a layer name (3803), a new DAO object creation (3804), and a DAO object selection (3805). Consists of
Since no other DAO object is defined at this stage, the DAO object selection (3805) is inactivated and cannot be specified.
When a new DAO object creation (3804) is selected, a new DAO object creation window is displayed in accordance with step 2204 to accept developer input.

FIG. 39 shows an example of a new DAO object creation screen. A class name input field (3901), a method name input field (3902), an argument specification field (3903), and a return value are specified. Column (3904) and an OK button (3905).
When necessary information is input and the OK button (3905) is pressed, a DAO object is newly generated in accordance with step 2206, and the DAO object generated in accordance with the component call diagram display means (209) is displayed.

  In FIG. 40, 4001, 4002, and 4003 indicate the positions of the created DAO objects in the global coordinate system, and 4004 indicates a display example of the DAO objects.

FIG. 41 shows an example of a DB layer operation menu. The operation menu (4101) of the DB layer (4102) includes a layer name (4103), a new DB object creation (4104), and a DB object selection (4105). Consists of
Since no other DB object is defined at this stage, DB object selection (4105) is inactivated and cannot be specified.
When a new DB object creation (4104) is selected, a new DB object creation window is displayed according to step 2204 to accept input from the developer.

FIG. 42 shows an example of a new DB object creation screen. A DB name input field (4201), a URL input field (4202), a table name specification field (4203), and a column name are specified. Column (4204) to perform and an OK button (4205).
When necessary information is input and the OK button (4205) is pressed, a DB object is newly generated according to step 2206, and the DB object generated according to the component call diagram display means (209) is displayed.

  In FIG. 43, 4301, 4302, and 4303 indicate positions of the created DAO object in the global coordinate system, and 4304 indicates a display example of the BL object.

FIG. 44 and FIG. 45 are diagrams showing a process in the case where a new component is created when there is an existing component in the corresponding layer of the call order data in step 2209.
In the situation shown in FIG. 44, when new creation of BL object (4401) is selected from the operation menu of the BL layer (4401), call order data is newly created in steps 2209 and 2210, and one layer before the corresponding layer. The data up to is copied to the newly created call order data. Further, the three-dimensional position is updated by the component position determining means (215).

  FIG. 45 shows a display example after new creation, in which the positions of the components 4501 and 4504 are updated. In the component call diagram, the three-dimensional object included in the newly created call order data is drawn, and the components 4501, 4502, and 4503 indicated by diagonal lines in the diagram are not displayed in the window.

46 to 47 show a process in the case where selection is instructed in the operation menu of each layer.
In the situation shown in FIG. 46, since other DAO objects exist, DAO object selection (4602) can be designated from the operation menu of the DAO layer (4601).
If DAO object selection (4602) is designated here, a component selection window is displayed in accordance with step 2213.

FIG. 47 shows an example of a component selection window, which includes a list (4701) of created three-dimensional objects and an OK button (4702). In the list (4701) of the created three-dimensional object, labels of all components of the corresponding layer are displayed in a list.
If a component is selected here and the OK button (4702) is pressed, the calling order data including the selected component is duplicated after the corresponding layer of the calling order data according to step 2219, and a new calling line object is generated. .

  FIG. 48 shows a display example of the result of selecting the DAO object (4801) whose label is UserDAO # getUser. Since 4801 is included in the call order data for calling the DB object 4802, the content is duplicated and displayed as shown in 4803 and 4804.

  FIGS. 49 and 50 are diagrams showing a process in the case where the selection of the calling order is instructed in Step 2103. When the designated key is pressed in the component call diagram (1503), the window display returns to the screen transition diagram. At this time, a screen transition object (0303) is generated and displayed by the screen transition definition means 0218.

FIG. 49 is a display example when the display is returned to the screen transition diagram from the situation of FIG. 48, and screen transition objects 4901 and 4902 are displayed. When the operation menu on the screen is displayed under this circumstance, since the calling order is already defined, selection of the calling order (4903) can be specified.
When selection of calling order (4903) is designated, a calling order selection window is displayed according to step 2107.

FIG. 50 shows an example of a call order selection window, which includes a list (5001) of call order data and an OK button (5002).
When the calling order is selected here and the OK button (5002) is pressed, the display is switched to the component calling diagram (1503), and the selected calling order is displayed.
In the examples so far, the components called by the same screen are displayed, so the components in the component call diagram are arranged in a horizontal row, but when calling order data is defined by selecting components to be called by screens with different vertical positions May not be in a horizontal row.

FIG. 51 and FIG. 52 are diagrams illustrating a process when components included in the calling order of different screens are selected.
When the BL object shown in 5103 is selected using the BL object selection (5102) in the operation menu in the layer shown in 5101, a call line object (5204) is generated as shown in FIG. 5203 components are displayed.

53 and 54 show a process in the case where a component already exists in the newly created corresponding layer in step 2208 and the existing component is defined by selection.
The component 5301 in FIG. 53 defines the calling order to the component 5302 by selection. Under such circumstances, when a new component is created at the position indicated by 5303, the selected component is executed by the component position determining means (220) at step 2211 as indicated by 5401, 5402, and 5403 in FIG. 54. The position is updated.

FIG. 55 and FIG. 56 show a process in the case where the calling order is defined by selecting a component when the selected component is included in a plurality of calling orders shown in Step 2301.
55. In FIG. 55, 5502 is included in the calling order data including 5502, 5503, 5504, and 5505 and the calling order data including 5502, 5506, 5504, and 5505.
When 5501 to 5502 are selected under this situation, call order data consisting of 5501, 5502, 5506, 5504, and 5505 and call order data consisting of 5501, 5502, 5503, 5504, and 5505 are generated.

  FIG. 56 shows an example of the screen display after selection, and any one of the newly created call order data is displayed in the component call diagram. FIG. 56 displays call order data including 5601, 5602, 5603, and 5604.

FIGS. 57 and 58 show display examples of designation of the transition destination in step 2610.
FIG. 57 shows a state before designating the transition destination, and the developer (110) designates the end point of the screen transition object by mouse operation in the screen transition diagram (5701).
FIG. 58 shows a state after the transition destination is designated. When the transition destination screen 5801 is designated, the end point position of the screen transition object 5802 is updated and displayed.
When the designated key is pressed during display of the screen transition diagram, the display is switched to the overall component call diagram by the overall component call diagram display means (210).

  FIG. 59 shows a display example of an overall component call diagram, and the developer (110) can grasp the call relationship based on the contents shown in 5901. FIG.

FIG. 60 shows an application example of the display of the three-dimensional screen transition diagram data 0201.
This example is a display example in the free viewpoint mode when the gazing point is the center position of each three-dimensional object and the viewpoint is an arbitrary three-dimensional position determined by a mouse operation. In this example, the call position can be viewed even when the viewpoint position is rotated by dragging up / down / left / right and components overlap.

FIG. 61 shows an example of the source code generated by the source code generation unit (207). The source code is automatically generated together with information held by each three-dimensional object and call-related information held by the call order data. In this example, a class name 6001 is generated from a class name (901) of a BL object, and a method 6002 is generated from a method name (902), an argument (903), and a return value (904). In each method, a process (6003) for acquiring a call destination component from the call order data and calling the corresponding component is automatically generated. The developer (110) implements specific processing in the portion 6004.
In addition, since the generation process of the source code generation unit (207) can use a known process, detailed description thereof is omitted.

It is a system configuration diagram. It is a block block diagram of a three-dimensional screen transition diagram editing program. It is a block diagram of 3D screen transition diagram data. This is a common attribute of a three-dimensional object. It is explanatory drawing of a world coordinate system and a projection method. It is a block diagram of display control data. It is an example of the data structure of a screen object. It is an example of the data structure of Action object. It is an example of the data structure of BL object. It is an example of the data structure of a DAO object. It is an example of the data structure of DB object. It is an example of the data structure of a screen transition object. It is an example of the data structure of a call line object. It is an example of the data structure of call order data. It is a display example of a three-dimensional screen transition diagram editing program. It is the whole processing flow. It is a processing flow of a screen transition diagram display means. It is a processing flow of a component call figure display means. It is a processing flow of the whole component call figure display means. It is a processing flow of a screen definition means. It is a processing flow of a calling order definition means. It is a processing flow of a component definition means. It is a duplication flow of the calling order at the time of component selection. It is a processing flow of a component position determination means. It is a generation flow of a call line object. It is a generation flow of a screen transition definition means. This is a screen generation procedure. This is a new screen creation window. It is a display example after screen creation. This is a procedure for creating a calling sequence. This is the screen after creating a new calling sequence. This is a procedure for creating a new Action object. This is a new Action object creation window. This is the screen after creating a new Action object. This is a procedure for creating a new BL object. This is a new BL object creation window. This is the screen after creating a new BL object. This is a procedure for creating a new DAO object. This is a new DAO object creation window. This is the screen after creating a new DAO object. This is a procedure for creating a new DB object. This is a new DB object creation window. It is a screen after table creation. This is a procedure for adding a component. This is the screen after adding the component. This is a component selection procedure. This is a component selection window. It is a screen after component selection. This is a procedure for selecting the calling order. This is a call order selection window. This is a component selection procedure for different screens. This is a screen after selecting components of different screens. This is the procedure to add a component to the selected layer. This is the screen after adding a component to the selected layer. This is a procedure for selecting components included in a plurality of calling orders. It is a screen after selecting a component included in a plurality of calling orders. This is a procedure for determining a screen transition. It is the screen after the screen transition is determined. It is a screen after displaying the entire component call diagram. It is a free viewpoint mode. It is an example of the generated source code. It is an example of a general web application composition and a screen transition diagram.

Explanation of symbols

DESCRIPTION OF SYMBOLS 101 Keyboard 102 Mouse 103 Display apparatus 104 Computer 105 Operation system 106 Three-dimensional screen transition diagram editing program 107 Source code editing program 108 Window 201 Three-dimensional screen transition diagram data storage unit 202 Generation template storage unit 203 Display control data storage unit 204 Three-dimensional Screen transition diagram display unit 205 Selected object determination unit 206 3D screen transition diagram editing unit 207 Source code generation unit 311 3D object

Claims (2)

A system that displays a calling relationship between components and components across multiple hierarchies that define processing for operations on each screen in a screen transition diagram composed of a plurality of screens constituting an application,
For each screen constituting the screen transition diagram, screen definition information such as a screen name corresponding to an input operation on the screen transition diagram definition screen is received, and the position of the three-dimensional coordinate system corresponding to the input position on the definition screen as a display attribute Screen definition means for generating a screen object having information and a predetermined three-dimensional shape;
The component definition information such as the component name corresponding to the input operation on the component definition screen is received for the component across multiple layers for each generated screen, and the position of the three-dimensional coordinate system corresponding to the input position on the definition screen as a display attribute Component defining means for generating a component having information and predetermined three-dimensional shape information;
As for the calling order of the generated components, the calling order information from the input means on the calling order definition screen is accepted, and the position information of the three-dimensional coordinate system corresponding to the input position on the definition screen and the predetermined three-dimensional shape information as display attributes A component call order definition means for generating a call line object having
For the screen transition of each screen defined by the screen definition means, the screen transition definition information is received from the input means on the screen transition definition screen, and the position information of the three-dimensional coordinate system corresponding to the input position on the definition screen is displayed in advance as the display attribute. A screen transition defining means for generating a screen transition object having the defined three-dimensional shape information;
First storage means for storing the components and objects defined by the screen definition means, component definition means, component call order definition means, and screen transition definition means as three-dimensional screen transition diagram data;
The three-dimensional screen transition diagram data stored in the first storage means is read out, and the three-dimensional position information and 3 that each object and component holds as a display attribute the screen, the component, and the calling relationship defined by each means. A screen transition diagram display system comprising: display means for displaying on a display screen as a screen transition diagram that can be viewed from a specified viewpoint in a three-dimensional or three-dimensional space based on three-dimensional shape information. A program that causes a computer to function as a system that displays a calling relationship between a component and a plurality of hierarchies that define processing for operations on each screen in a screen transition diagram that includes a plurality of screens constituting an application,
Computer
For each screen constituting the screen transition diagram, screen definition information such as a screen name corresponding to an input operation on the screen transition diagram definition screen is received, and the position of the three-dimensional coordinate system corresponding to the input position on the definition screen as a display attribute Screen definition means for generating a screen object having information and a predetermined three-dimensional shape;
The component definition information such as the component name corresponding to the input operation on the component definition screen is received for the component across multiple layers for each generated screen, and the position of the three-dimensional coordinate system corresponding to the input position on the definition screen as a display attribute Component defining means for generating a component having information and predetermined three-dimensional shape information;
As for the calling order of the generated components, the calling order information from the input means on the calling order definition screen is accepted, and the position information of the three-dimensional coordinate system corresponding to the input position on the definition screen and the predetermined three-dimensional shape information as display attributes A component call order definition means for generating a call line object having
For the screen transition of each screen defined by the screen definition means, the screen transition definition information is received from the input means on the screen transition definition screen, and the position information of the three-dimensional coordinate system corresponding to the input position on the definition screen is displayed in advance as the display attribute. A screen transition defining means for generating a screen transition object having the defined three-dimensional shape information;
First storage means for storing the components and objects defined by the screen definition means, component definition means, component call order definition means, and screen transition definition means as three-dimensional screen transition diagram data;
The three-dimensional screen transition diagram data stored in the first storage means is read out, and the three-dimensional position information and 3 that each object and component holds as a display attribute the screen, the component, and the calling relationship defined by each means. A program for displaying a screen transition diagram, which functions as a display means for displaying on a display screen as a screen transition diagram viewed from a specified viewpoint in a three-dimensional or three-dimensional space based on the three-dimensional shape information.

Images