WO2006033159A1 - 業務モデル図作成支援プログラム、方法、 及び装置 - Google Patents
業務モデル図作成支援プログラム、方法、 及び装置 Download PDFInfo
- Publication number
- WO2006033159A1 WO2006033159A1 PCT/JP2004/013942 JP2004013942W WO2006033159A1 WO 2006033159 A1 WO2006033159 A1 WO 2006033159A1 JP 2004013942 W JP2004013942 W JP 2004013942W WO 2006033159 A1 WO2006033159 A1 WO 2006033159A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- verification
- rail
- business model
- diagram
- business
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
Definitions
- the present invention relates to a business model diagram creation support program, a business model diagram creation support method, and a business model diagram creation support device for verifying the validity of a created diagram when a business model is represented by a diagram, and in particular, a verification result
- the present invention relates to a business model diagram creation support program, a business model diagram creation support method, and a business model diagram creation support device.
- a business model diagram is created to model customer requirements.
- the business model diagram is composed of a business flow diagram and a data structure diagram.
- the business flow diagram is a graphic and text representation of the work procedures that occur and the information that should be passed between the work.
- the data structure diagram is a diagram showing a relationship between data.
- the creation of a business model diagram may be performed by using general-purpose drawing software or by using dedicated software for drawing a special diagram such as a business model diagram.
- general-purpose drawing software or by using dedicated software for drawing a special diagram such as a business model diagram.
- dedicated software for drawing a special diagram such as a business model diagram.
- the branch condition may not be entered even though there is a diagram showing the conditional branch in the business flow.
- the dedicated software is called a modeling editor, and is a dedicated editor for creating models such as business model diagrams.
- the dedicated software is a function that retains the model structure information in the software only by editing functions that use formats such as business flow diagrams and data structure diagrams.
- the model structure is represented in a tree structure and edited in the tree structure. It has a function.
- the modeling editor analyzes the created business model diagram in order to represent the model structure in a tree structure. At that time, if the transition is correctly connected to the business process and there is an error such as V, NA, etc., the business model cannot be analyzed. Therefore, some modeling editors have a function to verify the correctness of the model.
- Patent Document 1 Japanese Patent Laid-Open No. 2002-133051 (FIG. 8)
- the conventional dedicated software only displays the occurrence of a verification error, and there is a problem that the location where the error occurs is not easily divided.
- model structure information may not be named by the user.
- the model components that appear in the workflow diagram are used for transitions, judgments, parallel branches, etc. Does not name it.
- Many transitions and decision condition branches often appear in one business flow. Therefore, when a verification error related to transition or decision condition branching occurs, it is difficult for the user to visually find out which of the many verification errors occurred.
- the identifier of the model element or diagram element in which the verification error has occurred is shown to the user, but it is difficult to identify the figure corresponding to the identifier from the workflow diagram. .
- the present invention has been made in view of these points, and it is possible to verify a business model created by general-purpose drawing software and to create a business model diagram that can notify a business model creator of the location of a defect.
- An object is to provide a support program, a business model diagram creation support method, and a business model diagram creation support device.
- the present invention provides a business model diagram creation support program for realizing the functions shown in FIG. 1 on a computer.
- This business model diagram creation support program is intended to support the creation of business model diagram 1 that represents the structure of a user's business model, and implements the following functions.
- the model structure analysis means 3 analyzes the business model diagram 1 having figures and lines as constituent elements, determines the types of the constituent elements constituting the business model diagram 1, and indicates the relationship between the constituent elements. Generate a model structure.
- Verification means 4 is a verification target element 1 at least part of the constituent elements. Select as a and extract the test iE / rail corresponding to the type of the selected verification target element la from the test IE / rail in which the conditions to be satisfied by the components of the business model diagram 1 are set in advance. Verify whether the verification target element la is compatible with the extracted check IE / rail.
- the verification result display means 5 displays the position to be operated in order to eliminate the nonconformity of the verification target element la to the inspection SE / rail when the verification means 4 determines that it is nonconforming.
- the model structure analysis means 3 analyzes the business model diagram 1, and the types of components constituting the business model diagram 1 are analyzed. And a model structure showing the relationship between the components is generated. Next, at least a part of the component is selected as the verification target element la by the verification means 4, and the conditions to be satisfied by the component of the business model diagram 1 are selected from the verification SE / rails set in advance. The verification iE / rail corresponding to the type of the verification target element la is extracted, and it is verified whether the selected verification target element la is compatible with the extracted verification IE / rail. If the verification unit 4 determines that the test is not compliant, the verification result display unit 5 displays the position to be operated to eliminate the non-conformity of the verification target element la to the test iE / rail.
- the type of each component constituting the business model diagram 1 is determined, and verification is performed by the inspection iE / rail corresponding to the type. If it is determined as non-conforming, the non-conformance is resolved. The position that should be operated is displayed. As a result, the user can easily correct defects in the business model created with general-purpose drawing software.
- FIG. 1 is a conceptual diagram of an invention applied to an embodiment.
- FIG. 2 is a diagram illustrating a hardware configuration example of a computer used in the present embodiment.
- FIG. 3 is a functional block diagram of the first embodiment.
- FIG. 8 is a diagram showing an example of a model structure display screen.
- FIG. 9 UML class diagram showing a part of model structure definition.
- FIG. 10 is a diagram showing an example of model structure information.
- FIG. 11 A diagram showing an example of inspection SE / rail coping information.
- FIG. 12 is a sequence diagram showing a procedure of a business model verification process according to the first embodiment.
- FIG. 13 is a diagram showing an example of a verification result list.
- FIG. 14 is a sequence diagram showing a procedure for displaying a verification error location on the model structure display screen.
- FIG. 15 is a diagram showing an example of a screen showing a verification result of the first exemplary embodiment.
- FIG. 16 is a functional block diagram of the second embodiment.
- FIG. 17 is a diagram showing an example of inspection SE / rail handling information according to the second embodiment.
- FIG. 18 is a sequence diagram showing a procedure for displaying verification error locations on the business flow display section.
- FIG. 19 is a diagram showing an example of a screen showing a verification result of the second embodiment.
- FIG. 20 is a functional block diagram of the third embodiment.
- ⁇ 21 It is a sequence diagram showing the procedure of the business model verification process according to the third embodiment.
- FIG. 22 is a functional block diagram of the fourth embodiment.
- FIG. 23 is a diagram showing an example of diagram information.
- FIG. 24 is a sequence diagram showing a procedure of a business model verification process according to the fourth embodiment.
- FIG. 25 is a functional block diagram of the fifth embodiment.
- FIG. 26 is a diagram showing an example of the data structure of test SE / rail and coping information.
- FIG. 27 is a diagram showing an example of a verification result list to which a time stamp is assigned.
- FIG. 28 is a diagram showing a first example of a progress status display screen.
- FIG. 29 is a diagram showing a second example of the progress status display screen.
- FIG. 30 is a diagram showing a third example of the progress status display screen.
- FIG. 31 is a functional block diagram of a sixth embodiment.
- FIG. 32 is a diagram showing an example of test iE / rail • measure information with verification timing set.
- FIG. 33 is a diagram showing an example of an iE / rail to be arbitrarily set.
- FIG.34 This is a diagram showing an example of test / rail action information in which model patterns before and after the action are registered.
- FIG. 1 is a conceptual diagram of the invention applied to the embodiment.
- the present invention has coping information 2, model structure analysis means 3, verification means 4, and verification result display means 5 to support the creation of a business model diagram 1 representing the structure of the user's business model. ing.
- the model structure analysis means 3 analyzes a business model diagram 1 having figures and lines as constituent elements. Then, the model structure analysis means 3 determines the type of each constituent element constituting the business model diagram 1 and generates a model structure indicating the relationship between the constituent elements. For example, the correspondence between the figures that make up the business model Figure 1 and the types of elements in the model structure should be defined in advance. Then, the model structure analysis means 3 determines the type of each component in the business model diagram 1 based on the defined correspondence.
- the verification unit 4 selects at least a part of the constituent elements as the verification target element la.
- the verification means 4 uses a component arbitrarily designated by the user as the verification target element la.
- the verification means 4 selects the verification iE / relevant corresponding to the type of the verification target element la from the verification iE / rails in which conditions to be satisfied by the components of the business model diagram 1 are set in advance. Extract the tool. For example, if the type of the verification target element la is “start”, the test SE / rail related to the start is extracted. Then, the verification means 4 verifies whether or not the selected verification target element la is compatible with the extracted inspection SE / rail.
- the verification result display means 5 is determined to be nonconforming (verification error) compared to the verification means 4, the position to be operated in order to eliminate the nonconformity of the verification target element la to the inspection iE / rail. Is displayed. For example, a graphic 6 indicating the defect position is displayed at the location where an error occurs on the business model diagram 1. At this time, the location of the error can be specified by the identifier of the verification target element.
- the verification result display means 5 refers to the countermeasure information 2 and displays an error message 7 and countermeasure 8 corresponding to the detected SE / rail determined to be nonconforming.
- the model structure analysis means 3 analyzes the business model diagram 1 and classifies each component constituting the business model diagram 1 And a model structure showing the relationship between the components is generated.
- the verification means 4 extracts the verification SE / rail corresponding to the type of the selected verification target element la from the verification iE / rail in which the conditions to be satisfied by the components of the business model diagram 1 are set in advance. . Then, the verification means 4 verifies whether or not the selected verification target element la is compatible with the extracted inspection SE / rail.
- the verification result display means 5 should be operated to eliminate the nonconformity of the verification target element la to the inspection iE / rail (error occurrence location).
- Figure 6, indicating error message 7, and action 8 are displayed.
- the verification target element la means “start” on the model structure.
- the inspection SE / rail that “there is one or more transitions from the beginning” is applied.
- the line representing the transition of the verification target element la is not connected to the verification target element la. Therefore, a verification error is detected based on the applied inspection SE / rail.
- a cross-shaped figure 6 is displayed on the verification target element la, and an error message 7 and countermeasure 8 are displayed.
- the location where the error occurred can be displayed on the business model diagram 1 or on the tree structure showing the model structure. It is also possible to specify in advance for each test tE / rail which figure is displayed. If an error occurrence location is displayed on the tree structure indicating the model structure, elements that do not appear on the business model diagram 1 are error occurrence locations, such as information indicating the transition of the business flow diagram and the relationship of the data structure diagram. However, the elements to be corrected can be displayed in an easy-to-understand manner.
- the verification process can be automatically executed at a preset timing. For example, verification can be performed when saving a file that stores a business model or when closing a file. For example, even if the business model diagram 1 is being edited, it is possible to perform sequential processing on important tE / rails. This allows for immediate correction when a very important error occurs, even during editing.
- a verification SE / rail where conflicting scenes often occur during editing can prevent the error message from being displayed excessively by performing verification processing when closing the file. As a result, the editing efficiency of the business model creator can be improved.
- the severity of errors can be set for each inspection SE / rail, and when a verification error occurs, the severity can be displayed along with an error message. For example, due to the difference in the severity of verification errors that have occurred, the user needs to check the force that is serious and must be corrected. You can know the key.
- inspection SE / rail it is possible to register the inspection SE / rail by the operation input from the user.
- a plurality of inspection SE / rails can be registered in advance, and only the verification rule selected by the user can be used for the verification process. This allows, for example, the test SE / rail to be dynamically and easily recombined for each project.
- the business model diagram 1 can be modified based on the revised plan.
- the business model revision proposal is shown, and when the revision proposal is accepted, it is actually revised, thereby reducing the burden of modification on the user.
- FIG. 2 is a diagram illustrating a hardware configuration example of a computer used in this embodiment.
- the entire computer 100 is controlled by a CPU (Central Processing Unit) 101.
- a random access memory (RAM) 102, a hard disk drive (HDD) 103, a graphics processing device 104, an input interface 105, and a communication interface 106 are connected to the CPU 101 via a bus 107 !,
- the CPU 101 Central Processing Unit 101.
- RAM random access memory
- HDD hard disk drive
- At least a part of an OS (Operating System) program application program to be executed by the CPU 101 is temporarily stored in the RAM 102.
- the RAM 102 stores various data necessary for processing by the CPU 101.
- the HDD 103 stores an OS application program.
- a monitor 11 is connected to the graphic processing device 104.
- the graphic processing device 104 displays an image on the screen of the monitor 11 in accordance with a command from the CPU 101.
- a keyboard 12 and a mouse 13 are connected to the input counter face 105.
- the input interface 105 transmits a signal sent from the keyboard 12 or mouse 13 to the CPU 101 via the bus 107.
- the communication interface 106 is connected to the network 10.
- the communication interface 106 transmits / receives data to / from other computers via the network 10.
- FIG. 3 is a functional block diagram of the first embodiment.
- the work flow diagram creation support device includes: model structure information 111, inspection SE / rail application unit 112, inspection SE / rail and coping information 113, model structure editing unit 114, verification control unit 115, verification execution unit 116, verification result It has a list 117 and a verification result display control unit 118.
- the model structure information 111 holds the structure information of the business model diagram 200 drawn by the user.
- the model structure information 111 represents the structure of the business model diagram 200 in a tree structure.
- the business model diagram 200 includes a business flow diagram and a data structure diagram.
- the inspection SE / rail application unit 112 holds a plurality of inspection SE / rails related to the elements (such as objects representing business process condition branching) constituting the business model diagram 200.
- elements such as objects representing business process condition branching
- iE / Rail for example, it is defined that a branch condition (a condition for transitioning to a branch destination must be set for each branch destination must be set in a conditional branch).
- Inspection iE / Rail ⁇ Corrective action information 113 is an error message that is displayed to the user when an error occurs during verification, and information that is effective to correct the error (the corrective action). Keep associated.
- the model structure editing unit 114 edits the model structure from the business model diagram 200 drawn by the user.
- the identification number of the element in the business model diagram 200 corresponding to the component is associated with the component (node, etc.) of the model structure.
- the model structure editing unit 114 accepts designation of a part to be verified (verification part) in the model structure by an operation input from the user.
- the model structure editing unit 114 receives the user capability verification instruction, the model structure editing unit 114 passes the verification portion specification and the verification request to the verification control unit 115.
- the verification part is designated by, for example, an identification number set for each element in the business model diagram 200.
- the model structure editing unit 114 displays a figure representing the verification error at the location.
- the verification control unit 115 When the verification control unit 115 receives the verification request, the verification control unit 115 passes information indicating the verification portion specified by the model structure editing unit 114 to the verification execution unit 116 and instructs verification processing of the verification target. In addition, when receiving the notification of the end of the verification process from the verification execution unit 116, the verification control unit 115 instructs the verification result display control unit 118 to display the verification result.
- the verification execution unit 116 acquires the verification target from the model structure information 111 based on the information indicating the verification part passed from the verification control unit 115. Then, the verification execution unit 116 issues a verification SE / rail application instruction to the verification IE / rail application unit 112 to verify whether the acquired verification target conforms to the verification SE / rail. . Further, the verification execution unit 116 registers the verification result in the verification result list 117. When the verification process for the verification target is completed, the verification execution unit 116 notifies the verification control unit 115 to that effect.
- the verification result list 117 stores the verification results output from the verification execution unit 116.
- the verification result display control unit 118 When the verification result display control unit 118 receives the verification result display instruction from the verification control unit 115, the verification result display control unit 118 acquires the verification result from the verification result list 117, and extracts the verification result that is regarded as an error by the verification process. Further, the verification result display control unit 118 refers to the inspection / rail 'countermeasure information 113, and determines the location where the verification error occurs, the error message, and the countermeasure for the verification error. Then, the verification result display control unit 118 displays an error message and a countermeasure against the verification error as a verification result, and notifies the model structure editing unit 114 of the location where the verification error has occurred. The location of the verification error is specified by the identification number of the verified element, for example.
- the business model diagram 200 is composed of a business flow diagram and a data structure diagram.
- Figure 4 is a business flow diagram.
- business processes 213a, 213b, 213c, 213d, branches 214a, 214b, and form 222 force S from start 211 to end 212 are provided.
- Start 211, end 212, business processes 213a, 213b, 213c, 213d, and branches 214a, 214b are connected by transition lines 215a-215h.
- the form 222 is connected to the business processes 213a and 213b by input / output lines 217a and 217b.
- a start 211 indicates a start position of the business flow.
- End 212 indicates the end position of the business flow.
- Business process 213a, 213b, 213c, 213di business flow Shows the work to be performed.
- Branches 214a and 214b indicate branching of the work procedure by the conditional branch.
- Transition lines 215a to 215h indicate transition relationships between business processes. Transition lines 215a to 215h indicate a transition source and a transition destination by arrows. The transition lines 215d and 215e having the branch 214 as a transition source are set with conditions for causing the corresponding transition.
- the input / output lines 217a and 217b indicate data output of business process power and data input to the business process by arrows. Specifically, the input / output line 217a indicates that the form indicated by the form 222 is output when the work indicated by the work process 213a is performed. Further, the input / output line 217b indicates that the input is made to the business process indicated by the form power business process 213b indicated by the form 222.
- FIG. 5 is a data structure diagram.
- a document 221, a form 222, 223, and a screen 225 represent data included in the business model. Then, it is shown by the relational force line 224 of the document 221 and the forms 222 and 223f3 ⁇ 4!
- the business model diagram 200 including the business flow diagram 210 shown in FIG. 4 and the data structure diagram 220 shown in FIG. 5 can be edited by the model structure editing unit 114.
- the model structure editor 11 4 displays the model structure on the screen as a tree structure.
- the model structure editing unit 114 When the business model diagram 200 having the contents as shown in FIGS. 4 and 5 is input to the model structure editing unit 114, the model structure is analyzed by the model structure editing unit 114. Specifically, the model structure editing unit 114 has structure definition information that defines in advance the correspondence between the figures that make up the workflow diagram 210 and the data structure diagram 220 and the elements that make up the model structure. Yes. The model structure editing unit 114 analyzes the structure of the input business model diagram 200 based on the structure definition information.
- FIG. 6 is a diagram illustrating an example of the structure definition information.
- the structure definition information 20 shows the correspondence between the figure in the business model and the element type in the model structure.
- the correspondence 21 at the top indicates that the black circle in the business model corresponds to the start of the model structure.
- Correspondence 22 indicates that the double circle in the business model (inside the black circle) corresponds to the end of the model structure.
- Correspondence 23 indicates that it corresponds to the judgment of the diamond-shaped force model structure painted in black in the business model.
- Correspondence 24 indicates that it corresponds to a solid arrow force model structure transition (control flow) in the business model.
- Correspondence 25 indicates that the dotted arrows in the business model correspond to the object flow of the model structure.
- Correspondence 26 indicates that a circular figure described as "business process" in the business model corresponds to a business process having a model structure.
- Correspondence 27 indicates that it corresponds to the object of the double-line square force model structure in the business model.
- Correspondence 28 indicates that the two types of figures representing "terminals" in the business model do not correspond to the element type of the model structure.
- Correspondence 29 indicates that the graphic described as “screen” and the graphic described as “form” in the business model correspond to the data of the model structure.
- the correspondence 20a indicates that there is no figure in the business model corresponding to the model of the model structure.
- Correspondence 20b indicates that there is no figure in the business model corresponding to the package of the model structure.
- Correspondence relationship 20c indicates that it corresponds to a business flow diagram of one page force model structure constituting the business model.
- Correspondence 20d indicates that there is no figure in the business model corresponding to the business flow of the model structure.
- Correspondence 20e indicates that it corresponds to one page power S that composes the business model, and the business data diagram of the model structure.
- FIG. 7 is a diagram illustrating an example of a business flow diagram using terminals. As shown in Figure 7, a single business flow diagram may be created across multiple pages 41 and 42. At this time, terminal 41a on page 41 indicates transition to terminal 42a on page 42! /.
- the terminals 41a and 42a in such a business flow diagram only indicate the connection between the pages 41 and 42, and do not indicate the structure of the business model. Therefore, the terminal 41a, 42a The components in the corresponding business model are not required.
- the model structure editing unit 114 analyzes the model structure of the business model diagram 200.
- the analyzed model structure is displayed on the screen in a tree structure.
- a figure is drawn on a drawing page in order to display business process or data properties (information held by the business process or data).
- the figure corresponds to the object property in the model structure information, not the object. Therefore, when the model structure information 111 is displayed in a tree format, there is no node (icon) corresponding to the data property.
- FIG. 8 is a diagram showing an example of the model structure display screen.
- the data structure of the business model diagram 200 is displayed in a tree structure.
- the user can specify the verification target position on the model structure display screen 300. For example, specify the element to be specified as the verification target position with the mouse cursor, etc., and display the menu screen (context menu, pull-down menu, etc.). Then, by selecting the verification execution command provided in the menu screen, verification execution for the verification target position can be instructed.
- the model structure information created from the business model diagram 200 is created according to a certain model structure definition.
- the model structure definition defines what types of elements can be connected to what types of elements.
- the model structure definition can be expressed, for example, in a UML class diagram.
- FIG. 9 is a UML class diagram showing a part of the model structure definition.
- the model structure definition 31 can be expressed using a class diagram.
- Model structure definition 31 shows the connection relationship between type 31a-311 and type 31a-311. Model structure information is created in accordance with such model structure definition31.
- FIG. 10 is a diagram illustrating an example of model structure information.
- the model structure information 32 the connection relationship between the model components 32a-32u is shown in a tree structure.
- Fig. 11 shows an example of test tE / rail response information.
- the inspection / rail 'countermeasure information 113 includes columns for verification ID, inspection SE / rail, error message, and countermeasure, and the information arranged in the horizontal direction of each column is associated with each other.
- the identification number set for the test SE / rail, error message, and countermeasure group is set.
- the contents of the inspection SE / rail defined in the inspection iE / rail application unit 112 are set in the inspection iE / rail column.
- the error message column the message when an error occurs as a result of applying the corresponding SE / Rail is set.
- the countermeasure column the countermeasure when an error occurs as a result of applying the corresponding inspection SE / rail is set.
- FIG. 12 is a sequence diagram illustrating a procedure of the business model verification process according to the first embodiment.
- the model structure editing unit 114 designates a part of the model structure to be inspected (verification target position) from the model structure information 111, and performs verification target acquisition processing (step S11).
- the inspection target position is determined in accordance with, for example, a user operation input for the model structure displayed on the screen.
- the model structure to be verified is taken out from the model structure information 111 and passed to the model structure editing unit 114 (step S12).
- the model structure editing unit 114 instructs the verification control unit 115 to execute verification on the verification target (step S 13).
- the verification control unit 115 passes the verification target to the verification execution unit 116, and executes the verification process (step S14).
- the verification execution unit 116 creates a verification result list 117 whose contents are empty (step S15). Then, a verification result list 117 is created in the memory space used by the verification execution unit 116 (step S16). Processing such as adding data to the migration verification result list 117 is performed in the memory space used by the verification execution unit 116.
- the verification execution unit 116 refers to the test iE / rail application unit 112 and acquires a test SE rail to be applied to the verification target (step S17). Then, the verification execution unit 116 performs verification. The verification target and the verification result list are passed to the rule application unit 112, and the application of the verification rail to the verification target is instructed (step S18).
- the verification execution unit 116 issues a test iE / rail application instruction to the test iE / rail application unit 112 for all test iE / rails.
- the verification execution unit 116 outputs all inspection iE / rail application instructions with the lower structure as the verification target.
- the inspection iE / rail application unit 112 receives an inspection iE / rail application instruction from the verification execution unit 116, the inspection iE / rail application unit 112 applies the inspection SE / rail to the verification target and creates a verification result 116a ( Step S19).
- the verification iE / rail application unit 112 acquires the verification result 116a (step S20), and adds the verification SE / rail application result to the verification result list 117 (step S21).
- the added application results include the verification target, iE / rail, and verification results.
- the verification execution unit 116 passes the verification result list 117 after the addition of the application results to the verification control unit 115 (Step S22).
- the verification control unit 115 passes the verification result list to the verification result display control unit 118 to instruct display (step S23).
- the verification result display control unit 118 displays a verification result list dialog. Then, the verification result display control unit 118 refers to the verification iE / rail and countermeasure information 113, acquires the verification rail and the countermeasure for each verification result stored in the verification result list, and displays it in the dialog. Display (Step S24).
- the verification result display control unit 118 designates the ID of the verification target in which an error has occurred and transmits an error location display instruction to the model structure editing unit 114 (step S25). Then, the model structure editing unit 114 displays a screen indicating the verification target determined as an error by applying the inspection SE / rail. For example, the model structure editing unit 114 displays a cross mark on the error part.
- FIG. 13 is a diagram showing an example of the verification result list.
- the verification result list 117 verification results are registered.
- the verification result consists of a target element ID, a test SE / rail, and a result set.
- the target element ID uniquely identifies the figure (verification target) to be verified in the business model. This is identification information.
- the inspection SE / rail is the identification information of the inspection SE / rail applied to the verification target.
- the result is information indicating whether or not the verification target satisfies the applied check IE / rail.
- “ ⁇ ” is set for the result when the test / rail conforms to the test
- “X” is set for the result when the test IE / rail fails (verification error).
- FIG. 14 is a sequence diagram showing the procedure for displaying the verification error location on the model structure display screen.
- the verification result display control unit 118 outputs a display request specifying the ID of the element in which the verification error is detected to the model structure editing unit 114 (step S41).
- the model structure editor 114 accesses the parent model structure information 11 la to obtain the ID of the model (step S42). Thereby, the model structure editing unit 114 acquires the model ID from the model structure information 11 la (step S43). Then, the model structure editing unit 114 compares the ID passed in the display request with the model ID. In this example, it is assumed that the ID is not correct.
- the model structure editing unit 114 refers to the parent model structure information 11 la and performs access for acquiring model information of the child (lower structure) (step S44). As a result, the model structure editing unit 114 acquires a child model information list from the model structure information 11 la (step S45).
- the model structure editing unit 114 refers to the child model structure information 11 lb, and acquires the ID of the model (step S46). Thereby, the model structure editing unit 114 acquires the model ID from the model structure information 11 la (step S47). Then, the model structure editing unit 114 compares the ID passed in the display request with the model ID. In this example. It is assumed that the ID is correct.
- the model structure editing unit 114 sets a display color for highlighting the child model structure information 11 lb. Thereafter, the model structure editing unit 114 redraws the model structure display information 310 related to the parent model structure information 11 la displayed on the model structure display screen 300 (step S49).
- the model structure of the parent substructure Since the highlight color is set in, the color of the node where the verification error occurred changes to the highlighted color.
- FIG. 15 is a diagram illustrating an example of a screen showing a verification result according to the first embodiment.
- a verification result screen 410 is displayed beside the model structure display screen 300.
- a verification result display unit 411 On the verification result screen 410, a verification result display unit 411, a countermeasure display unit 412, a display button 413, and an end button 414 are provided.
- the verification result display unit 411 displays an error message of the verification process that resulted in an error.
- the coping method display unit 412 displays the coping method of the verification process selected in the verification result display unit 411.
- a display button 413 is a button for displaying a countermeasure for the error message for which the verification result power is also selected.
- An end button 414 is a button for closing the verification result screen 410.
- the node in which the error has occurred is highlighted in the model structure in the model structure display screen 300.
- a check mark is displayed at the node 311 where the error is detected.
- the countermeasure against the model structure verification error and the location where the error occurred are displayed on the screen, so that the user can easily correct the mistake in the business model diagram 200.
- FIG. 16 is a functional block diagram according to the second embodiment. Since many functions of the second embodiment are the same as those of the first embodiment, components having the same functions as those of the first embodiment shown in FIG. The description is omitted.
- the difference from the first embodiment is that the figure editing unit 121 is added, and the functions of the inspection / rail action information 113a and the verification result display control unit 118a are changed. That is.
- the diagram editing unit 121 creates a business flow diagram and a data structure diagram in response to an operation input by the user. The created diagram is input to the model structure editing unit 114 as a business model.
- Inspection tE / rail ⁇ Corrective action information 113a has information on the display location in addition to error messages and countermeasures for the inspection SE / rail.
- the display location is information that specifies a figure for displaying the error location. If the model structure editor 114 is a display location, an error location is displayed on the diagram showing the model structure. If the diagram editing unit 121 is a display location, an error location is displayed on the diagram showing the business model.
- the verification result display control unit 118a corresponds to the display location information set in the test / rail 'countermeasure information 113a. , And a function of determining a partner to instruct to display an error part. That is, if the display location is the model structure editing unit 114, an instruction to display an error location is output to the model structure editing unit 114. If the display location is the diagram editing unit 121, an error location display instruction is output to the diagram editing unit 121.
- FIG. 17 is a diagram showing an example of the iE / rail handling information according to the second embodiment.
- the verification / rail 'countermeasure information 113a of the second embodiment includes columns for verification, verification SE / rail, error message, countermeasure, and display location.
- the display location column an error display location (display function) when an error occurs in the verification process based on the associated inspection rail is set.
- FIG. 18 is a sequence diagram showing a procedure for displaying a verification error location on the workflow display unit.
- a display request specifying the ID of an element in which a verification error is detected is output from the verification result display control unit 118a to the diagram editing unit 121 (step S51).
- the diagram editing unit 121 accesses the diagram information 121a in order to acquire the ID of the diagram (step S52).
- the diagram editing unit 121 acquires a diagram ID from the diagram information 121a (step S53).
- the diagram editing unit 121 compares the ID passed in the display request with the model ID. If the IDs do not match, the diagram editing unit 121 repeats the processing of steps S52 and 53 until they match.
- the diagram editing unit 121 accesses the diagram information 121a to acquire the display position of the graphic corresponding to the matched ID (step S55).
- the figure editor 12 1 obtains the position (X coordinate and y coordinate) of the figure where the error occurred from the diagram information 121a (step S55).
- the diagram editing unit 121 performs an editing operation on the diagram information 121a, and places an error location display graphic (for example, a cross mark) at the position acquired in step S55 (step S56).
- an error location display graphic for example, a cross mark
- the display location of the error it is possible to display an error that can be easily visually divided. For example, if the location where an error has occurred is displayed in the workflow diagram being edited by the diagram editor 121, the user can immediately recognize the data to be edited in order to eliminate the error.
- FIG. 19 is a diagram illustrating an example of a screen indicating a verification result of the second embodiment.
- the example in Figure 19 shows the display screen when an error is detected on the SE / Rail that there is at least one transition from the start! / Speak.
- the error display location of this test / rail is the diagram editor 121. Therefore, a graphic 216 indicating the occurrence of an error is displayed at the start position of the business flow diagram 210 displayed by the diagram editing unit 121.
- the location where the error has occurred can be displayed on the business flow diagram 210 being created.
- general-purpose drawing software can be used as the diagram editing unit 121, and a business model diagram can be created using software familiar to the user.
- a third embodiment will be described.
- a plurality of inspection iE / rails can be selectively applied.
- FIG. 20 is a functional block diagram of the third embodiment. Since many functions of the third embodiment are the same as those of the second embodiment, components having the same functions as the components of the second embodiment shown in FIG. The description is omitted.
- the inspection SE / rail holding unit 122 stores a plurality of inspection iE / rails 122a.
- the test IE / rail application unit 112a is pre-installed with an applicable test SE / rail based on user input. Specified. Then, the inspection SE / rail application unit 112a applies only the applicable inspection SE / rail to the verification target and performs the verification process.
- test / rail 122a can be implemented in, for example, an object-oriented programming language.
- an interface for applying the test SE / rail 122a is defined in the super class, and the test SE / rail is created as a subclass. If implemented in this way, any test SE / rail can be called from the test SE / rail application unit 112a using the iterator using the same interface. Therefore, it is easy to mount the inspection SE / rail application unit 112a and to add or delete the inspection SE / rail 122a.
- an iterator is an abstraction of iterative processing for each element of a list or similar data structure. In actual programming languages, it appears as an object or grammar. It is translated as an iterator in the sense of iterating.
- FIG. 21 is a sequence diagram illustrating a procedure of the business model verification process according to the third embodiment. Since this process is almost the same as the process of the first embodiment shown in FIG. 12, the same process is given the same step number and the description thereof is omitted. Hereinafter, the processing different from that of the first embodiment will be described.
- step S11 to step S17 The processing from step S11 to step S17 is the same as in the first embodiment. Thereafter, the verification execution unit 116 passes the verification target and the verification result list to the verification SE / rail holding unit 122, and instructs the verification SE / rail to be applied to the verification target (step S18a).
- the verification execution unit 116 when a plurality of inspection SE / rails are acquired, the verification execution unit 116 outputs all acquired inspection IE / rail application instructions to the inspection iE / rail application unit 112. In addition, if the acquired verification target has a lower structure, the verification execution unit 116 outputs the application instructions for all the inspection SE / rails as the verification target.
- the inspection iE / rail holding unit 122 applies the inspection SE / rail to the verification target (step S18b).
- the test SE / rail described by the program is activated, and the verification target is passed to the process of executing the test SE / rail.
- the verification target is determined by the process of executing the inspection SE / rail.
- the test SE rails to be applied are sequentially applied to the verification target. Then, by applying the inspection SE / rail (process description by the program) held in the inspection SE / rail holding unit 122, a verification result 116a is created by the inspection SE / rail (step S19a).
- step S20 to step S24 is the same as in the first embodiment.
- the verification result display control unit 118a determines whether the display target is the model structure editing unit 114 or the diagram editing unit 121. If the display target is the model structure editing unit 114, the verification result display control unit 118a specifies the ID of the verification target in which an error has occurred and transmits an instruction to display the error location to the model structure editing unit 114. (Step S25a). In this case, the model structure editing unit 114 displays the error occurrence location on the model structure display screen 300.
- the verification result display control unit 118a designates the ID of the verification target in which an error has occurred to the diagram editing unit 121, and displays the error location.
- Send an indication step S25b.
- the diagram editing unit 121 displays the error occurrence location in the workflow diagram 210.
- the figure shape method to be displayed in the figure editing unit is held separately as figure information, and the figure information power can directly verify the model structure.
- FIG. 22 is a functional block diagram of the fourth embodiment. Since many functions of the fourth embodiment are the same as those of the third embodiment, components having the same functions as those of the third embodiment shown in FIG. The description is omitted.
- the difference from the third embodiment is that the figure information 123 is added and the function of the inspection / rail application unit 112a is changed.
- the figure information 123 stores graphic data included in a figure representing a business model.
- the model structure editing unit 114a analyzes the graphic data included in the diagram information 123 and creates model structure information 111.
- FIG. 23 is a diagram showing an example of diagram information.
- the figure information 123 includes a plurality of graphic data 123a and 123g.
- the graphic data 123a-123g is associated with the tree structure to form the figure information 123.
- each figure is named a shave.
- the transition graphic data 123g includes information of the source connection shape ID and the target connection shape ID.
- the model structure editing unit 114a generates model structure information 111 based on the diagram information 123 as shown in FIG.
- a rule using data included in the figure information 123 can be defined. For example, if the source side connection destination shape ID or the target side connection destination shape ID is set in the transition graphic data 123g, the verification SE / rail 122a may be defined so that a verification error occurs. it can.
- FIG. 24 is a sequence diagram illustrating a procedure of the business model verification process according to the fourth embodiment. Note that the processing of the fourth embodiment is almost the same as the processing of the third embodiment shown in FIG. 21, and therefore only the different parts are shown.
- the model structure editing unit 114a designates a part of the model structure to be inspected (verification target position) from the model structure information 111, and performs a verification target acquisition process (step S31). Then, the model structure (verification—model information) to be verified is extracted from the model structure information 111 and passed to the model structure editing unit 114a (step S32).
- the model structure editing unit 114a performs a verification target acquisition process by designating the portion of the graphic information to be inspected (verification target position) from the graphic information 123 (step S33). Then, the verification target graphic information (verification—diagram information) is extracted from the graphic information 123 and passed to the model structure editing unit 114a (step S34).
- the model structure editing unit 114a instructs the verification control unit 115 to execute a verification process on the verification target (step S35).
- the verification target passed to the verification control unit 115 includes verification—model information and verification—diagram information. Subsequent processing is This is the same as the processing after step S15 shown in FIG.
- verification can be performed based on the data in the diagram information, detailed verification can be performed. For example, verification can be performed based on data that is not reflected in the model structure information 111.
- a verification result list for each of a plurality of verification processes with different conditions such as execution time is held, and the progress of creation of a business model can be measured.
- the importance is set for the test IE / rail, and when a verification error occurs, the weight is displayed together with the error message.
- FIG. 25 is a functional block diagram of the fifth embodiment. Since many functions of the fifth embodiment are the same as those of the fourth embodiment, components having the same functions as those of the components of the fourth embodiment shown in FIG. The description is omitted.
- the difference from the fourth embodiment is that a plurality of verification result lists 117a, 117b, and 117c can be held, and the functions of the verification execution unit 116a and the verification result display control unit 118a are changed. And the contents of the inspection / rail action information 113b have been changed.
- the verification execution unit 116a performs a verification process and assigns a time stamp (information indicating the current time) when creating the verification result list.
- a time stamp information indicating the current time
- the verification result display control unit 118a uses the plurality of verification result lists 117a, 117b, and 117c to create statistical data indicating the progress of the work model creation work and displays it on the screen.
- FIG. 26 is a diagram showing an example of the data structure of the inspection / rail 'countermeasure information.
- This SE / Rail 'Solution Information 113b has columns for Verification ID, Error Z Warning, SE Rail, Error Message, Countermeasure, and Display Location. Compared to the SE / Rail information 113a shown in Fig. 17, an error Z warning column is added.
- the error Z warning column shows the importance of the error when the element being verified does not meet the test / rail.
- FIG. 27 is a diagram illustrating an example of a verification result list to which a time stamp is assigned.
- the verification result list 117a the time stamp 117aa and the verification result 117ab are registered!
- the time stamp 117aa indicates the creation date and time of the verification result list 117a.
- a target In the verification result 117ab, a target, a target element ID, a test iE / rail, and a result set are registered.
- the target indicates whether the verification target is the model structure information 111 or the diagram information 123 (represented simply as “figure” in the verification result list 117a).
- the target element ID, the inspection SE / rail, and the result are the same as those in the first embodiment shown in FIG.
- the number of errors and the number of warnings can be aggregated as statistical information.
- the total results are displayed on the screen as progress status.
- FIG. 28 is a diagram showing a first example of the progress status display screen.
- the progress status display screen 51 has columns for verification date and time, the number of errors, and the number of warnings, and the verification results are displayed in time series.
- the progress of the work model creation work can be estimated by referring to the transition of the number of errors and warnings. For example, if the number of errors and warnings is decreasing, it can be determined that the work model creation work has entered the final stage (error correction stage) and the work is proceeding smoothly.
- FIG. 29 is a diagram showing a second example of the progress status display screen.
- This progress status display screen 52 has columns for verification date and time, number of newly added errors Z warnings, number of remaining cases from previous verifications, and number of corrections Z number of deleted places where verification results are displayed in chronological order.
- the number of newly added errors Z warnings is the number of new errors and warnings not detected in the previous verification process.
- the remaining number from the previous verification is the number of unprocessed errors and warnings detected in the previous verification process.
- Number of corrections The number of deleted Z locations is the number of errors and warnings that were corrected or deleted during the current verification process.
- Whether the error or warning detected in the previous verification process was detected in the current verification process is whether the target, target element ID, and test SE / rail in the verification result list match. Judgment can be made by comparing powers.
- FIG. 30 is a diagram showing a third example of the progress status display screen. This progress status display screen 5
- 3 includes a verification result display section 53a, a countermeasure display section 53b, a display button 53c, and an end button 53d.
- the verification result display section 53a displays a list of verification errors (errors and warnings) detected so far.
- a mark indicating a new error (“New!” In the example of FIG. 30) is given to the verification error newly detected in the last verification process.
- the user can select a verification error whose detailed contents should be referred to from within the verification result display section 53a. Errors and warnings that have already been corrected are displayed in gray, for example, and cannot be selected.
- the coping method display unit 53b displays a coping method of the verification error selected by the verification result display unit 53a.
- the display button 53c is a button for displaying the location where the verification error is selected, which is selected in the verification result display section 53a.
- the end button 53d is a button for closing the progress status display screen 53.
- a sixth embodiment will be described.
- a plurality of test iE / records are recorded. Use the information to specify the test tE / rail to be applied and the test SE / rail in the test rule. Use the test rail registered in the rail setting file and use the test iE / rail during the verification process. By selecting the setting file, the inspection SE / rail to be applied is specified.
- FIG. 31 is a functional block diagram according to the sixth embodiment. Since many functions of the sixth embodiment are the same as those of the fifth embodiment, components having the same functions as the components of the fifth embodiment shown in FIG. The description is omitted.
- the use inspection SE rail configuration file 124 describes the inspection SE / rail numbers selected by the business model creator, separated by commas.
- the verification execution unit 116a uses only the test SE / rail with the number described in the use test SE / rail setting file 124 from the test SE / rail 122a held by the test iE / rail holding unit 122. The verification process is executed.
- a plurality of use inspection SE / rail setting files 124 can be prepared.
- the verification execution unit 116a has a function of setting the name of the usage inspection iE / rail setting file 124. Then, the verification execution unit 116a outputs a verification processing instruction to the verification iE / rail application unit 112a based on the usage verification SE / rail setting file 124 corresponding to the preset name.
- the business model creator can set a setting file according to the purpose from a plurality of setting files and execute verification.
- the timing of the verification process is defined in advance, and the verification process is automatically performed at that timing.
- the verification timing is set in the inspection / rail 'countermeasure information 113b, and the verification control unit 115 refers to the inspection SE / rail and countermeasure information 113b to check each inspection SE / rail. Manage the verification timing.
- FIG. 32 is a diagram showing an example of the inspection / rail 'coping information with the verification timing set.
- This iE / Rail 'coping information 113c includes columns for verification ID, error Z warning, test rail, error message, coping method, display location, and verification timing. Compared with the inspection information 113b shown in FIG. 26, the verification timing column is added.
- the verification timing indicates the application timing of the corresponding inspection SE / rail. If it is “Verification time verification”, the verification process of the corresponding test SE / rail is executed when an intentional operation input by the user is performed.
- the verification timing is "when editing"
- each time a figure is entered in the diagram editing unit 121 while the user or business model is being edited the corresponding verification iE / rail Verification processing is executed. Specifically, when a figure is input by the figure editing unit 121 and the setting of the position of the figure is fixed, the information is passed to the model structure editing unit 114a. For example, it is assumed that the settings of a previously operated figure have been confirmed when moving to another figure operation.
- the verification timing can be set, for example, to be verified at regular intervals, or to be verified when a file is saved or closed.
- the model structure editing unit 114a updates the model structure information 111 each time a new figure is input, and notifies the verification control unit 115 that the model structure information has been updated. Then, the verification control unit 115 outputs a verification instruction for the newly input element to the verification execution unit 116a.
- the verification execution unit 116a refers to the inspection SE / rail and coping information 113c, and identifies the inspection SE / rail that can be applied to the input element and the verification timing is "when editing". To do. Then, the verification execution unit 116a outputs the inspection SE / rail application instruction to the inspection SE / rail application unit 112a.
- the verification process can be automatically executed.
- the user can immediately know the presence of an error when an incorrect figure is placed.
- the second application example allows the user to define an arbitrary iE / rail.
- a new test rail reading unit for reading a test rail stored at an arbitrary location is added to the work flow diagram creation support device. Add.
- the user inputs the file name storing the test SE / rail to be applied to the test SE / rail reading unit.
- the inspection SE / rail reading unit registers the inspection iE / rail in the specified file in the inspection iE / rail holding unit 122.
- OCL Object Constraint Language
- FIG. 33 is a diagram showing an example of a test SE / rail to be arbitrarily set.
- This test SE / rail 122b has a power of more than 0 coming out of the element indicated by “context BusinessProcess inv”.
- Such an iE / rail 122b is an element that can generally connect a large number of wires, but if the number is too large, the structure of the business flow and the like becomes too complicated. Used to limit the number of possible lines.
- the third application example automatically handles when an error occurs.
- the model pattern before the countermeasure and the model pattern after the countermeasure are registered in the inspection iE / rail / remedy information 113b.
- FIG. 34 is a diagram showing an example of test / rail 'coping information in which model patterns before and after coping are registered.
- this inspection / rail 'coping information 113d columns of a pre-treatment business model pattern and a post-treatment business model pattern are provided in association with the inspection SE / rail.
- the business model pattern that causes the error is set in the pre-action business model pattern.
- the business model pattern that can resolve the error is set in the post-response business model pattern.
- the name of the business process at the transition destination is automatically set as the guard condition.
- the user determines that another guard condition is appropriate, the user can input an operation to the diagram editing unit 121 and set an arbitrary guard condition.
- the verification result display control unit 118a refers to the detection / rail 'countermeasure information 113d, and if the pre-response business model pattern and the post-response business model pattern are set, An instruction to change the model according to the setting contents is output to the diagram editing unit 121.
- the diagram editing unit 121 edits a diagram such as a workflow diagram according to the instruction.
- the edited diagram may be finalized after an operation input indicating confirmation from the user. it can. This can prevent the diagram from being changed without the user's knowledge.
- the processing functions described above can be realized by a computer.
- a program that describes the processing contents of the functions that the business model diagram creation support device should have is provided.
- the program describing the processing contents can be recorded on a computer-readable recording medium.
- the computer-readable recording medium include a magnetic recording device, an optical disk, a magneto-optical recording medium, and a semiconductor memory.
- Magnetic recording devices include hard disk drives (HDD), flexible disks (FD), and magnetic tape.
- Optical discs include DVD (Digital Versatile Disc), DVD—RAM (Random Access Memory), CD—ROM (Compact Disc Read Only Memory), and CD—R (Recordable) ZRW (Rewritable).
- DVD Digital Versatile Disc
- RAM Random Access Memory
- CD—ROM Compact Disc Read Only Memory
- CD—R Recordable
- ZRW Rewritable
- MO magneto-optical recording media
- the computer that executes the program stores, for example, a program recorded on a portable recording medium or a server computer-powered program in its own storage device. Then, the computer reads its own storage device power program and executes processing according to the program. The computer can also read the program directly from the portable recording medium and execute processing according to the program. In addition, the review The data can also be executed sequentially according to the received program each time the program is transferred to the server computer.
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2006536290A JP4667386B2 (ja) | 2004-09-24 | 2004-09-24 | 業務モデル図作成支援プログラム、業務モデル図作成支援方法、および業務モデル図作成支援装置 |
PCT/JP2004/013942 WO2006033159A1 (ja) | 2004-09-24 | 2004-09-24 | 業務モデル図作成支援プログラム、方法、 及び装置 |
US11/726,384 US20070214173A1 (en) | 2004-09-24 | 2007-03-21 | Program, method, and apparatus for supporting creation of business process model diagram |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2004/013942 WO2006033159A1 (ja) | 2004-09-24 | 2004-09-24 | 業務モデル図作成支援プログラム、方法、 及び装置 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/726,384 Continuation US20070214173A1 (en) | 2004-09-24 | 2007-03-21 | Program, method, and apparatus for supporting creation of business process model diagram |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2006033159A1 true WO2006033159A1 (ja) | 2006-03-30 |
Family
ID=36089926
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2004/013942 WO2006033159A1 (ja) | 2004-09-24 | 2004-09-24 | 業務モデル図作成支援プログラム、方法、 及び装置 |
Country Status (3)
Country | Link |
---|---|
US (1) | US20070214173A1 (ja) |
JP (1) | JP4667386B2 (ja) |
WO (1) | WO2006033159A1 (ja) |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2008018132A1 (fr) * | 2006-08-09 | 2008-02-14 | Fujitsu Limited | programme d'édition d'organigramme d'entreprise et procédé d'édition d'organigramme d'entreprise |
JP2008077208A (ja) * | 2006-09-19 | 2008-04-03 | Fujitsu Ltd | 業務フロー編集プログラム、業務フロー編集装置および業務フロー編集方法 |
JP2008257645A (ja) * | 2007-04-09 | 2008-10-23 | Toyota Motor Corp | 業務プロセス設計支援システム |
JP2008276394A (ja) * | 2007-04-26 | 2008-11-13 | Nippon Telegr & Teleph Corp <Ntt> | プロセスモデル作成システム、方法及びそのプログラム |
WO2009144826A1 (ja) * | 2008-05-30 | 2009-12-03 | 富士通株式会社 | 検査用ファイル生成プログラム、検査用ファイル生成装置および検査用ファイル生成方法 |
JP2010086066A (ja) * | 2008-09-29 | 2010-04-15 | Internatl Business Mach Corp <Ibm> | モデルの品質を検証するためのコンピュータ・システム、並びにその方法及びコンピュータ・プログラム |
JP2011503680A (ja) * | 2007-09-28 | 2011-01-27 | マイクロソフト コーポレーション | リレーショナルモデルのインテリジェントな編集 |
JP2011209839A (ja) * | 2010-03-29 | 2011-10-20 | Fuji Electric Co Ltd | プログラム自動生成装置 |
JP2011232874A (ja) * | 2010-04-26 | 2011-11-17 | Fujitsu Ltd | 情報セキュリティ管理支援方法及び装置 |
JP2015018557A (ja) * | 2013-07-15 | 2015-01-29 | ゼネラル・エレクトリック・カンパニイ | データ損失防止のためのシステムおよび方法 |
JP2015041285A (ja) * | 2013-08-22 | 2015-03-02 | 三菱電機株式会社 | 整合性検証装置、整合性検証方法及び整合性検証プログラム |
WO2016208073A1 (ja) * | 2015-06-26 | 2016-12-29 | 株式会社日立製作所 | モジュール再利用判定装置、モジュール再利用判定方法、及びモジュール再利用判定プログラム |
JP2019164671A (ja) * | 2018-03-20 | 2019-09-26 | 東京電力ホールディングス株式会社 | 事例分析支援システム、事例分析支援方法およびプログラム |
CN113010930A (zh) * | 2021-04-15 | 2021-06-22 | 北京航空航天大学 | 一种数字孪生模型多维多尺度验证方法 |
Families Citing this family (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7542980B2 (en) | 2005-04-22 | 2009-06-02 | Sap Ag | Methods of comparing and merging business process configurations |
US20060293935A1 (en) * | 2005-04-22 | 2006-12-28 | Igor Tsyganskiy | Methods and systems for incrementally exposing business application errors using an integrated display |
US7702638B2 (en) * | 2005-04-22 | 2010-04-20 | Sap Ag | Systems and methods for off-line modeling a business application |
US20060293934A1 (en) * | 2005-04-22 | 2006-12-28 | Igor Tsyganskiy | Methods and systems for providing an integrated business application configuration environment |
US20060242174A1 (en) * | 2005-04-22 | 2006-10-26 | Igor Tsyganskiy | Systems and methods for using object-oriented tools to debug business applications |
US20060242177A1 (en) * | 2005-04-22 | 2006-10-26 | Igor Tsyganskiy | Methods of exposing business application runtime exceptions at design time |
US8539003B2 (en) * | 2005-04-22 | 2013-09-17 | Sap Ag | Systems and methods for identifying problems of a business application in a customer support system |
US20060242188A1 (en) * | 2005-04-22 | 2006-10-26 | Igor Tsyganskiy | Methods of exposing a missing collection of application elements as deprecated |
US7958486B2 (en) * | 2005-04-22 | 2011-06-07 | Sap Ag | Methods and systems for data-focused debugging and tracing capabilities |
US20060242194A1 (en) * | 2005-04-22 | 2006-10-26 | Igor Tsyganskiy | Systems and methods for modeling and manipulating a table-driven business application in an object-oriented environment |
US20060242197A1 (en) * | 2005-04-22 | 2006-10-26 | Igor Tsyganskiy | Methods of transforming application layer structure as objects |
US7877731B2 (en) * | 2007-02-12 | 2011-01-25 | Microsoft Corporation | Formatting and viewing source objects |
US8126693B2 (en) * | 2008-01-15 | 2012-02-28 | International Business Machines Corporation | Method and system for modeling, validating and automatically resolving goals and dependencies between elements within a topology |
US8126692B2 (en) * | 2008-01-15 | 2012-02-28 | International Business Machines Corporation | Method and system for modeling, validating and automatically resolving goals and dependencies between elements within a topology |
US20090271229A1 (en) * | 2008-04-23 | 2009-10-29 | C/O Outperformance, Inc. | Method for generating a flexible model for joint profit and environmental optimization |
US8140581B2 (en) * | 2008-05-15 | 2012-03-20 | Microsoft Corporation | Configurable view on data models |
US8140593B2 (en) | 2008-05-15 | 2012-03-20 | Microsoft Corporation | Data viewer management |
GB0817197D0 (en) * | 2008-09-19 | 2008-10-29 | Walsh Jason J | Process development system |
US20100161524A1 (en) * | 2008-12-19 | 2010-06-24 | International Business Machines Corporation | Method and system for identifying graphical model semantics |
US20100162208A1 (en) * | 2008-12-19 | 2010-06-24 | International Business Machines Corporation | Modeling tool builder - graphical editor construction |
JP5188421B2 (ja) * | 2009-02-27 | 2013-04-24 | 株式会社日立製作所 | ソースコード解析方法およびソースコード解析支援システム |
US20110184882A1 (en) * | 2010-01-25 | 2011-07-28 | International Business Machines Corporation | Social modeling of processes |
US8719191B2 (en) * | 2010-03-01 | 2014-05-06 | International Business Machines Corporation | Training and verification using a correlated boosted entity model |
US8578346B2 (en) * | 2010-09-10 | 2013-11-05 | International Business Machines Corporation | System and method to validate and repair process flow drawings |
US10755208B2 (en) * | 2012-08-15 | 2020-08-25 | Sap Se | Methods, apparatus and system for mediating services |
CN106445506A (zh) * | 2016-09-06 | 2017-02-22 | 北京恒华伟业科技股份有限公司 | 一种业务流程图生成方法、装置和系统 |
CN116627664B (zh) * | 2023-07-26 | 2024-03-29 | 中信证券股份有限公司 | 业务校验方法、装置、电子设备和计算机可读介质 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH08287157A (ja) * | 1995-04-07 | 1996-11-01 | Hitachi Ltd | 業務プロセス定義方法 |
JPH10198708A (ja) * | 1997-01-08 | 1998-07-31 | Zuken:Kk | 図面検証システム |
JP2004171365A (ja) * | 2002-11-21 | 2004-06-17 | Hitachi Ltd | 図面検証システム |
Family Cites Families (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH07101383B2 (ja) * | 1987-05-02 | 1995-11-01 | 日本電気株式会社 | 図式プログラムエディタエラ−表示方式 |
EP0525258A1 (en) * | 1991-07-29 | 1993-02-03 | International Business Machines Corporation | Generation of rules-based computer programs |
JPH05274179A (ja) * | 1992-03-25 | 1993-10-22 | Mitsubishi Electric Corp | コンパイル処理装置 |
JPH06230955A (ja) * | 1993-02-05 | 1994-08-19 | Toshiba Corp | タイムチャート編集装置 |
US5848393A (en) * | 1995-12-15 | 1998-12-08 | Ncr Corporation | "What if . . . " function for simulating operations within a task workflow management system |
JPH09231061A (ja) * | 1996-02-20 | 1997-09-05 | Fuji Xerox Co Ltd | プログラミング支援装置および方法 |
US5801942A (en) * | 1996-04-12 | 1998-09-01 | Fisher-Rosemount Systems, Inc. | Process control system user interface including selection of multiple control languages |
JPH10187424A (ja) * | 1996-12-25 | 1998-07-21 | Nec Corp | 図式編集プログラムにおける正誤判定結果表示方式 |
US6637020B1 (en) * | 1998-12-03 | 2003-10-21 | International Business Machines Corporation | Creating applications within data processing systems by combining program components dynamically |
US7458013B2 (en) * | 1999-05-12 | 2008-11-25 | The Board Of Trustees Of The Leland Stanford Junior University | Concurrent voice to text and sketch processing with synchronized replay |
US6754885B1 (en) * | 1999-05-17 | 2004-06-22 | Invensys Systems, Inc. | Methods and apparatus for controlling object appearance in a process control configuration system |
AU5025600A (en) * | 1999-05-17 | 2000-12-05 | Foxboro Company, The | Process control configuration system with parameterized objects |
US7315826B1 (en) * | 1999-05-27 | 2008-01-01 | Accenture, Llp | Comparatively analyzing vendors of components required for a web-based architecture |
US7139999B2 (en) * | 1999-08-31 | 2006-11-21 | Accenture Llp | Development architecture framework |
US6981207B1 (en) * | 2000-01-11 | 2005-12-27 | Ecora Software Corporation | Automatic documentation of configurable systems by outputting explanatory information of configuration parameters in a narrative format and configuration parameters differences |
US7334216B2 (en) * | 2000-04-04 | 2008-02-19 | Sosy, Inc. | Method and apparatus for automatic generation of information system user interfaces |
US8176563B2 (en) * | 2000-11-13 | 2012-05-08 | DigitalDoors, Inc. | Data security system and method with editor |
US6725229B2 (en) * | 2000-12-29 | 2004-04-20 | Bellsouth Intellectual Property Corp. | Configuration utility |
US20040027398A1 (en) * | 2001-02-15 | 2004-02-12 | Denny Jaeger | Intuitive graphic user interface with universal tools |
US7082386B2 (en) * | 2001-02-21 | 2006-07-25 | International Business Machines Corporation | Generalized software modeling tool |
US7136082B2 (en) * | 2002-01-25 | 2006-11-14 | Xerox Corporation | Method and apparatus to convert digital ink images for use in a structured text/graphics editor |
US7139004B2 (en) * | 2002-01-25 | 2006-11-21 | Xerox Corporation | Method and apparatus to convert bitmapped images for use in a structured text/graphics editor |
US7366678B2 (en) * | 2002-04-12 | 2008-04-29 | International Business Machines Corporation | Facilitating error checking of service elements |
US7440902B2 (en) * | 2002-04-12 | 2008-10-21 | International Business Machines Corporation | Service development tool and capabilities for facilitating management of service elements |
US20040019875A1 (en) * | 2002-04-29 | 2004-01-29 | Welch Keith C. | Masked edit control for use in a graphical programming environment |
WO2003096147A2 (en) * | 2002-05-06 | 2003-11-20 | Zoot Enterprises, Inc. | System and method of application processing |
US7251787B2 (en) * | 2002-08-28 | 2007-07-31 | Siebel Systems, Inc. | Method and apparatus for an integrated process modeller |
US7257818B2 (en) * | 2002-08-29 | 2007-08-14 | Sap Aktiengesellschaft | Rapid application integration using functional atoms |
US7237225B2 (en) * | 2002-08-29 | 2007-06-26 | Sap Aktiengesellschaft | Rapid application integration using reusable patterns |
US20050034083A1 (en) * | 2003-08-05 | 2005-02-10 | Denny Jaeger | Intuitive graphic user interface with universal tools |
US7454377B1 (en) * | 2003-09-26 | 2008-11-18 | Perry H. Beaumont | Computer method and apparatus for aggregating and segmenting probabilistic distributions |
US7543274B2 (en) * | 2003-12-22 | 2009-06-02 | The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration | System and method for deriving a process-based specification |
-
2004
- 2004-09-24 JP JP2006536290A patent/JP4667386B2/ja not_active Expired - Fee Related
- 2004-09-24 WO PCT/JP2004/013942 patent/WO2006033159A1/ja active Application Filing
-
2007
- 2007-03-21 US US11/726,384 patent/US20070214173A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH08287157A (ja) * | 1995-04-07 | 1996-11-01 | Hitachi Ltd | 業務プロセス定義方法 |
JPH10198708A (ja) * | 1997-01-08 | 1998-07-31 | Zuken:Kk | 図面検証システム |
JP2004171365A (ja) * | 2002-11-21 | 2004-06-17 | Hitachi Ltd | 図面検証システム |
Cited By (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4893741B2 (ja) * | 2006-08-09 | 2012-03-07 | 富士通株式会社 | 業務フローチャート編集プログラムおよび業務フローチャート編集方法 |
WO2008018132A1 (fr) * | 2006-08-09 | 2008-02-14 | Fujitsu Limited | programme d'édition d'organigramme d'entreprise et procédé d'édition d'organigramme d'entreprise |
US8630887B2 (en) | 2006-08-09 | 2014-01-14 | Fujitsu Limited | Business process flowchart editing program and business process flowchart editing method |
JP2008077208A (ja) * | 2006-09-19 | 2008-04-03 | Fujitsu Ltd | 業務フロー編集プログラム、業務フロー編集装置および業務フロー編集方法 |
JP2008257645A (ja) * | 2007-04-09 | 2008-10-23 | Toyota Motor Corp | 業務プロセス設計支援システム |
JP2008276394A (ja) * | 2007-04-26 | 2008-11-13 | Nippon Telegr & Teleph Corp <Ntt> | プロセスモデル作成システム、方法及びそのプログラム |
JP2011503680A (ja) * | 2007-09-28 | 2011-01-27 | マイクロソフト コーポレーション | リレーショナルモデルのインテリジェントな編集 |
WO2009144826A1 (ja) * | 2008-05-30 | 2009-12-03 | 富士通株式会社 | 検査用ファイル生成プログラム、検査用ファイル生成装置および検査用ファイル生成方法 |
GB2472944A (en) * | 2008-05-30 | 2011-02-23 | Fujitsu Ltd | Verification file generating program, verification file generating device, and verification file generating method |
JP5246258B2 (ja) * | 2008-05-30 | 2013-07-24 | 富士通株式会社 | ファイル生成プログラム、ファイル生成装置およびファイル生成方法 |
US8103914B2 (en) | 2008-05-30 | 2012-01-24 | Fujitsu Limited | Test file generation device and test file generation method |
JP2010086066A (ja) * | 2008-09-29 | 2010-04-15 | Internatl Business Mach Corp <Ibm> | モデルの品質を検証するためのコンピュータ・システム、並びにその方法及びコンピュータ・プログラム |
JP2011209839A (ja) * | 2010-03-29 | 2011-10-20 | Fuji Electric Co Ltd | プログラム自動生成装置 |
JP2011232874A (ja) * | 2010-04-26 | 2011-11-17 | Fujitsu Ltd | 情報セキュリティ管理支援方法及び装置 |
JP2015018557A (ja) * | 2013-07-15 | 2015-01-29 | ゼネラル・エレクトリック・カンパニイ | データ損失防止のためのシステムおよび方法 |
JP2015041285A (ja) * | 2013-08-22 | 2015-03-02 | 三菱電機株式会社 | 整合性検証装置、整合性検証方法及び整合性検証プログラム |
WO2016208073A1 (ja) * | 2015-06-26 | 2016-12-29 | 株式会社日立製作所 | モジュール再利用判定装置、モジュール再利用判定方法、及びモジュール再利用判定プログラム |
JPWO2016208073A1 (ja) * | 2015-06-26 | 2017-06-29 | 株式会社日立製作所 | モジュール再利用判定装置、モジュール再利用判定方法、及びモジュール再利用判定プログラム |
JP2019164671A (ja) * | 2018-03-20 | 2019-09-26 | 東京電力ホールディングス株式会社 | 事例分析支援システム、事例分析支援方法およびプログラム |
JP7192228B2 (ja) | 2018-03-20 | 2022-12-20 | 東京電力ホールディングス株式会社 | 事例分析支援システム、事例分析支援方法およびプログラム |
CN113010930A (zh) * | 2021-04-15 | 2021-06-22 | 北京航空航天大学 | 一种数字孪生模型多维多尺度验证方法 |
Also Published As
Publication number | Publication date |
---|---|
US20070214173A1 (en) | 2007-09-13 |
JPWO2006033159A1 (ja) | 2008-05-15 |
JP4667386B2 (ja) | 2011-04-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP4667386B2 (ja) | 業務モデル図作成支援プログラム、業務モデル図作成支援方法、および業務モデル図作成支援装置 | |
US8327333B2 (en) | Apparatus, method, and system of assisting software development | |
US7908564B2 (en) | Copying and pasting a plurality of data items as a group | |
US7096421B2 (en) | System and method for comparing hashed XML files | |
AU4098700A (en) | Circuit arrangement for measuring the resistances of a pressure-sensitive resistance mat | |
US20040205509A1 (en) | System and method for comparing parsed XML files | |
JP2004118403A (ja) | ソフトウェア機能テストデータ生成プログラムおよびソフトウェア機能テストデータ生成方法 | |
WO2010044150A1 (ja) | プログラム変更管理装置、プログラム変更管理プログラムおよびプログラム変更管理方法 | |
JPH08241191A (ja) | Gui自動評価装置 | |
JP4215255B2 (ja) | デグレード確認検査方法、デグレード確認検査システム、およびそのためのプログラム | |
US20100095279A1 (en) | Method for automatically testing menu items of application software | |
JP4484791B2 (ja) | 検証データ生成装置および検証データ生成プログラム、検証データ生成方法 | |
KR101534493B1 (ko) | 구조 변환에 기초한 소스코드 보안 약점 탐지 장치 및 방법 | |
JP5123337B2 (ja) | 検証データ生成装置、検証データ生成プログラム及び検証データ生成方法 | |
JP3464159B2 (ja) | テスト仕様書作成装置およびそのプログラムを格納した記憶媒体 | |
JP5808264B2 (ja) | コード生成装置及びコード生成方法及びプログラム | |
JP2011204069A (ja) | テスト方法およびテスト仕様書テストデータ自動生成装置 | |
JP5799589B2 (ja) | 検証方法及び検証プログラム | |
US8839097B2 (en) | System and method for information encapsulation for providing multiple deliverable formats from one information source | |
JP6739599B1 (ja) | 情報処理プログラム、情報処理方法、及び情報処理装置 | |
JP6419902B1 (ja) | プログラム比較方法、プログラム比較装置およびプログラム比較プログラム | |
JP4113652B2 (ja) | 住宅開発設計システム | |
JP3417318B2 (ja) | ドキュメント作成管理方法及びその装置並びにプログラムを記録した機械読み取り可能な記録媒体 | |
CN117434883A (zh) | 一种plc程序版本的可视化管理方法及装置 | |
CN117215552A (zh) | 交互组件的生成方法、装置、存储介质及计算机设备 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2006536290 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 11726384 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWP | Wipo information: published in national office |
Ref document number: 11726384 Country of ref document: US |
|
122 | Ep: pct application non-entry in european phase |