Systems and methods for modeling business processes

• US 20070005618A1
• Filed: 06/07/2006
• Published: 01/04/2007
• Est. Priority Date: 06/07/2005
• Status: Abandoned Application

• Current Assignee: Software AG
• Original Assignee: Software AG
• Inventors: Ivanov, Konstantin, Reul, Dagmar Emma Anneliese
• Application Number:
  US11/447,790
• Publication Number:
  US 20070005618A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/00 Administration; Management
• CPC Class Codes: G06Q 30/00 Commerce

Abstract

Methods and systems are provided for modeling business information and providing navigation between business information models. An exemplary method for modeling business information uses integrated model data, and includes the steps of storing a first business information model and second business information model written in description notations, and assigning the second business information model to an object, wherein the object is represented by a symbol in the first business information model. An exemplary method for providing navigation between business information models includes displaying a graphical representation of an object in a first business information model, and providing an interface for navigating to display a second business information model, where the step of providing the interface includes providing the interface with the graphical representation of the object.

Claims

1. A method for modeling business information with integrated model data, the method comprising the steps of:

storing a first business information model, the first business information model comprising a first description notation;

storing a second business information model, the second business information comprising a second description notation, the second description notation not necessarily being different from the first description notation; and

assigning the second business information model to an object, the object being represented by a symbol in the first business information model;

wherein at least one of the first description notation and the second description notation is an execution language description notation.

2. The method according to claim 1, wherein a description notation of the first description notation and the second description notation is one from the group comprising:

an event-driven process chain notation, XML, BPEL-compliant XML, BPEL represented as graphical symbols, UML component diagram notation, value-added chain notation, BPMN, ERM, UML, IDEFX, BSC, XSD, DTD, SAP-SERM, OMT, SeDaM, PROMET, a program flow chart, and a process support map.

3. The method according to claim 1, wherein at least one of the first description notation and the second description notation includes one or more symbols that can be used to generate executable code.

4. The method according to claim 3, wherein the executable code is a BPEL-compliant XML code.

5. The method according to claim 1, wherein at least one of the first business information model and the second business information model is a business process model.

6. A method for modeling business information with integrated model data, the method comprising the steps of:

storing a first business information model, the first business information model being written in a first description notation;

storing a second business information model, the second business information model being written in a second description notation, the second description notation not necessarily being different from the first description notation; and

storing occurrence information for an object indicating that the object is represented by both a symbol in the first business information model and a symbol in the second business information model,

wherein at least one of the first description notation and the second description notation is an execution language description notation.

7. The method according to claim 6, wherein a description notation of the first description notation and the second description notation is one from the group comprising:

an event-driven process chain notation, XML, BPEL-compliant XML, BPEL represented as graphical symbols, UML component diagram notation, value-added chain notation, BPMN, ERM, UML, IDEFX, BSC, XSD, DTD, SAP-SERM, OMT, SeDaM, PROMET, a program flow chart, and a process support map.

8. The method according to claim 6, wherein at least one of the first description notation and the second description notation includes one or more symbols that can be used to generate executable code.

9. The method according to claim 8, wherein the executable code is a BPEL-compliant XML code.

10. The method according to claim 6, wherein at least one of the first business information model and the second business information model is a business process model.

11. A method of providing navigation between business information models, comprising the steps of:

displaying a graphical representation of an object in a first business information model, the first business information model comprising a first description notation; and

providing an interface for navigating to display a second business information model, the second business information model comprising a second description notation, the second description notation not necessarily being different than the first description notation;

wherein the step of providing an interface includes providing the interface with the graphical representation of the object, and further wherein at least one of the first description notation and the second description notation is an execution language description notation.

12. The method according to claim 11, wherein a description notation of the first description notation and the second description notation is one from the group comprising:

an event-driven process chain notation, XML, BPEL-compliant XML, BPEL represented as graphical symbols, UML component diagram notation, value-added chain notation, BPMN, ERM, UML, IDEFX, BSC, XSD, DTD, SAP-SERM, OMT, SeDaM, PROMET, a program flow chart, and a process support map.

13. The method according to claim 11, wherein the first description notation and the second description notation includes one or more symbols that can be used to generate executable code.

14. The method according to claim 13, wherein the executable code is a BPEL-compliant XML code.

15. The method according to claim 11, wherein the interface for navigating includes one or more of:

an expansion icon;

double clicking on a symbol;

shading, coloring, or otherwise altering the appearance of a symbol when the symbol can be used to navigate to a business information model; and

shading, coloring, or otherwise altering the appearance of the cursor when it is near a symbol that can be used to navigate to a business information model.

16. A system for modeling business information with integrated model data, the system comprising:

a processor,

a computer-readable medium containing instructions to configure the processor to perform a method comprising the steps of;

storing a first business information model, the first business information model being written in a first description notation;

storing a second business information model, the second business information model being written in a second description notation, the second description notation not necessarily being different from the first description notation; and

assigning the second business information model to an object, the object being represented by a symbol in the first business information model,

wherein at least one of the first description notation and the second description notation is an execution language description notation.

17. The system according to claim 16, wherein a description notation of the first description notation and the second description notation is one from the group comprising:

an event-driven process chain notation, XML, BPEL-compliant XML, BPEL represented as graphical symbols, UML component diagram notation, value-added chain notation, BPMN, ERM, UML, IDEFX, BSC, XSD, DTD, SAP-SERM, OMT, SeDaM, PROMET, a program flow chart, and a process support map.

18. The system according to claim 16, wherein at least one of the first description notation and the second description notation includes one or more symbols that can be used to generate executable code.

19. The system according to claim 18, wherein the executable code is a BPEL-compliant XML code.

20. The system according to claim 16, wherein at least one of the first business information model and the second business information model is a business process model.

21. A system for providing navigation between one or more business information models, the system comprising:

a processor,

a computer-readable medium containing instructions to configure the processor to perform a method comprising the steps of;

displaying a graphical representation of an object in a first business information model, the first business information model being written in a first description notation; and

providing an interface for navigating to display a second business information model, the second model being written in a second description notation, the second description notation not necessarily being different than the first description notation;

wherein the step of providing an interface includes providing the interface with the graphical representation of the object, and further wherein at least one of the first description notation and the second description notation is an execution language description notation.

22. The system according to claim 21, wherein a description notation for the first description notation and the second description notation is one from the group comprising:

an event-driven process chain notation, XML, BPEL-compliant XML, BPEL represented as graphical symbols, UML component diagram notation, value-added chain notation, BPMN, ERM, UML, IDEFx, BSC, XSD, DTD, SAP-SERM, OMT, SeDaM, PROMET, a program flow chart, and a process support map.

23. The system according to claim 21, wherein at least one of the first description notation and the second description notation includes one or more symbols that can be used to generate executable code.

24. The system according to claim 23, wherein the executable code is a BPEL-compliant XML code.

25. The system according to claim 21, wherein the interface for navigating includes one or more of:

an expansion icon;

double clicking on a symbol;

shading, coloring, or otherwise altering the appearance of a symbol when the symbol can be used to navigate to a business information model, and

shading, coloring, or otherwise altering the appearance of the cursor when it is near a symbol that can be used to navigate to a business information model.