+

EP1588349A1 - Procede et appareil pour un modelisateur de processus integre - Google Patents

Procede et appareil pour un modelisateur de processus integre

Info

Publication number
EP1588349A1
EP1588349A1 EP03814581A EP03814581A EP1588349A1 EP 1588349 A1 EP1588349 A1 EP 1588349A1 EP 03814581 A EP03814581 A EP 03814581A EP 03814581 A EP03814581 A EP 03814581A EP 1588349 A1 EP1588349 A1 EP 1588349A1
Authority
EP
European Patent Office
Prior art keywords
modeler
business
processes
user
design
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP03814581A
Other languages
German (de)
English (en)
Other versions
EP1588349A4 (fr
Inventor
Issac Stephen Levin
Jon Rexford Degenhardt
Atul Suklikar
Peter A. Thorson
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Siebel Systems Inc
Original Assignee
Siebel Systems Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US10/334,953 external-priority patent/US7251787B2/en
Application filed by Siebel Systems Inc filed Critical Siebel Systems Inc
Publication of EP1588349A1 publication Critical patent/EP1588349A1/fr
Publication of EP1588349A4 publication Critical patent/EP1588349A4/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B17/00—Systems involving the use of models or simulators of said systems
    • G05B17/02—Systems involving the use of models or simulators of said systems electric
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/10—Requirements analysis; Specification techniques

Definitions

  • the present invention relates to modeling, and more particularly to modeling a complex process.
  • a business analyst may create a process flow for a business process using tools such as Nisio and iGrafx.
  • tools such as Nisio and iGrafx.
  • BizTalk or similar tools.
  • An end-to-end process modeler comprising a vertically integrated process modeler to provide a design aspect for a non-technical user and an implementation aspect for a technical user, the vertically integrated process modeler designed to create a complete executable process.
  • Figure 2 is an overview flowchart of one embodiment of using the integrated process modeler.
  • Figures 3 A and 3B are a flowchart of one embodiment of the business analyst using the process modeler to create a new process.
  • Figure 4 is a flowchart of one embodiment of the responsibility transfer from the business analyst to the implementing engineer.
  • Figure 5 is a flowchart of one embodiment of the implementing engineer using the process modeler to enable to the process created by the business analyst.
  • Figure 6 illustrates one embodiment comparison between business analyst and developer features.
  • Figure 7 illustrates one embodiment of a user interface presented to a business analyst.
  • Figures 8 A and 8B illustrate embodiments of a user interface showing the drilldown process.
  • Figures 10A-10D illustrate embodiments of a user interface for an implementation engineer.
  • Figure 11 A and 1 IB illustrate embodiments of an integration view.
  • Figure 12 is a block diagram of one embodiment of a network that may be used with the present invention.
  • Figure 13 is a block diagram of one embodiment of a computer system that may be used with the present invention.
  • a method and apparatus for an integrated process modeler provides a single tool for designing, debugging and deploying an end-to-end business process.
  • a business process in this context is a structured series of documented activities organized to achieve a specific business objective. The structure of a particular business process may vary by company, as there are multiple practices for executing any specific objective.
  • Business processes which can be comprised of multiple sub-processes, are graphically represented in flow diagrams and can span third-party applications.
  • An end-to-end business process is a major business process for the company, one that may span multiple divisions or organizations within as well as outside the company's legal boundaries.
  • An end-to-end business process also can involve interaction with multiple interconnected computer systems executing either autonomously or with end users.
  • the end-to-end business process is typically a long running process occurring over hours, days, weeks or months rather than minutes or seconds. The present system permits the design of such an end-to-end business process, as well as the simpler basic business processes.
  • the modeler spans multiple process types (e.g. enterprise, Siebel, Integration, task), as well as multiple roles (e.g. business analyst, developer), and allows for seamless transition between these components.
  • process types e.g. enterprise, Siebel, Integration, task
  • roles e.g. business analyst, developer
  • the process modeler is capable of designing process flows involving user interaction (e.g. the create call list task).
  • the user interaction design includes the design of a user interface, as well as process steps that require waiting for particular types of inputs from particular users. For one embodiment, both the non-technical and technical user can design these user interaction flows.
  • the process modeler includes the ability to create user interaction as well as integration with other applications.
  • FIG. 1 is a block diagram of one embodiment of an integrated process modeler.
  • the process modeler 100 includes a user identification logic 110, which determines what type of interface is presented to the user.
  • the business analyst interface 130 permits the design of new processes as well as the editing of existing processes.
  • the developer interface 160 permits the implementation and integration of the process designed by the analyst.
  • user identification logic 110 uses the login and group association of the user to identify the user type.
  • the user may select his or her preferred interface.
  • each user that has access to the modeler 100 may be specified to the user identification logic 110.
  • user identification logic 110 may provide security functions. This prevents unauthorized users from altering any processes, or creating new and incorrect processes.
  • the business analyst interface 130 permits a business analyst or equivalent individual to create a process.
  • This interface 130 may also be referred to as the "editor” since it permits the user to edit or create a process.
  • the term "business analyst” refers to an individual who is empowered to create processes for use by the corporation. In general, such a person need not be an engineer or programmer, and will therefore be referred to as a non-technical user. However, a business analyst may, of course, be a programmer or technically knowledgeable.
  • the term “non-technical user” is simply used to define the fact that the business analyst need not know programming in order to create or edit processes.
  • This process is designed to automate certain procedures inside or outside the company.
  • the process may, for example, be the process of fulfilling a trade request.
  • This example will be used throughout the present specification. However, it is to be understood that any procedures may be automated.
  • the modeler 100 provides access to a library of best practice processes 135.
  • Best practice processes are pre-defined processes.
  • a company such as Siebel provides a plurality of predefined best practice processes to its clients. These clients can then use the business analyst interface 130 to customize and change the best practice processes, or may choose to adopt the best practice processes as-is.
  • the library 135 is available to the business analyst interface 130.
  • the business analyst may pick subprocesses from the library 135.
  • a subprocess may be "confirm with supervisor.”
  • a subprocess may have multiple steps in it. For example, confirming may include sending an email, waiting for a response, and if the proper response is received, noting the confirmation.
  • the drill-down logic 120 permits the business analyst to go from subprocess to steps.
  • the process is shown as a series of steps. Each step may have one or more steps, or sub-steps.
  • the business analyst may use business analyst interface 130 to drill-down from process to subprocess, and from subprocess to atomic steps. The various user interfaces shown to the business analyst are described below.
  • Validation logic 145 verifies that the process meets certain basic criteria. For example, the validation logic 145 may verify that each element is connected to at least one other element. The validation logic 145 may also verify that there are no connectors that have no defined end-points. Furthermore, for one embodiment, validation logic 145 may verify that any "decision element" has two out-going connectors, one for each possible result. If the validation logic 145 determines that there are some errors, it passes the process back to the business analyst interface 130, alerting the business analyst to correct the indicated errors. For one embodiment, the validation logic 145 may flag any errors, or otherwise provide indication on what needs to be done.
  • validation logic 145 determines that there are no errors, it passes the process to the transfer and flagging logic 150.
  • the transfer and flagging logic 150 transfers the process to the collection of processes in progress 155.
  • processes which have not completed implementation are stored in a collection 155.
  • This collection is accessible to developers, for implementation, and for one embodiment accessible to the business analyst for further editing.
  • these processes in progress 155 are not available to the company in general, and may not be used.
  • the transfer and flagging logic 150 for one embodiment further flags the process. Flagging marks each element and/or each connector that requires work for implementation. For one embodiment, there are multiple types of flags, each flag indicating the type of work that needs to be done. For example, a flag may indicate that insufficient detail has been provided for executable meaning. Alternatively, a flag may indicate that a particular communication needs to be defined. For example, the business analyst may define an element as "contact supervisor" but may not provide the definition of how to accomplish this task. This flag is then used by the developer to work on the proper elements and connectors. This flagged version of the process is then stored in the collection 155.
  • the developer may, through developer interface 160 pick up a process in progress from the collection 155.
  • the term "developer” is used for simplicity here.
  • the "developer” may be any user who is able to create executable processes. In general, the developer is a technical user, such as a programmer.
  • the developer interface 160 may also be referred to as the implementation interface 160 since it is used to implement the process into an executable process.
  • processes may be assigned to a particular developer or team of developers for implementation.
  • user identification logic 110 controls whether the developer may access/work on a particular process.
  • the developer 160 may edit the process to make it executable. Furthermore, developer may use drill-down logic 120 to see the elements and subprocesses that are used. For one embodiment, developer may further access the exiting processes or subprocesses defined in the library 135. This enables reuse of previously defined steps and subprocesses.
  • the process is available for use.
  • a business analyst or supervisor must do a final approval.
  • a quality assurance team may further perform testing on the process.
  • the process Once the process has been approved, it may be implemented within the corporation. This means the process is made available to various users.
  • such processes are further put into the library 135, to permit reuse of various steps within the process.
  • the present integrated process modeler 100 permits a business analyst to create a process, and allows the developer to make the process executable.
  • the resulting process may be used throughout the company.
  • Figure 2 is an overview flowchart of one embodiment of using the integrated process modeler.
  • the sequence starts at block 210.
  • the best practices processes are made available.
  • the best practices are stored in a library, and are available for use, editing, or extracting steps.
  • the sequence determines whether the user selected a best practices process to edit. If so, the selected process is shown to the user, at block 225, and editing is enabled. For one embodiment, a high level diagram of the selected process is displayed. The user may then edit any of the steps of the process, or any of the subprocesses within the process. If the user did not select a best practices process, the sequence continues to block 230.
  • the system permits the creation and editing of the various procedures and subprocesses embodied within the process. If no process was selected, the user may choose to create an entirely new process at this point. The user in this instance need not be a programmer or technical user. Rather, the user may be a business person or manager who knows what types of procedures are being used in the company.
  • the sequence determines whether the user checked in the process. Checking in indicates that the user has completed editing the process, and the process may be handed off. For one embodiment, the user may indicate this by storing the process in a special location, such as the "to be enabled" directory. If the user has not yet checked in the process, the sequence returns to block 230, permitting further editing. Of course, the user may temporarily store an incomplete process, and access it at a later time.
  • the sequence continues to block 240.
  • the sequence identifies and flags connectors and steps that are nonexecutable, or not sufficiently defined.
  • the implementer, or technical user is prompted to complete each flagged item. Note that the implementer generally checks out the process from the collection of processes in progress. The flags prompt the implementer to complete the process, and for one embodiment identify the type of work that needs to be done for completion.
  • the sequence determines whether the user has checked in the process. For one embodiment, once the technical user completes the implementation, he or she checks the process back in. For one embodiment, in this instance checking in further includes performing quality assurance/testing on the process, and getting a final sign-off from an appropriate individual, such as a manager. If the process has not yet been checked in the sequence returns to block 245, permitting further edits.
  • Figures 3 A and 3B are a flowchart of one embodiment of the business analyst using the process modeler to create a new process. The sequence starts at block 310, when a business analyst or authorized employee logs into the system.
  • the best practices processes are made available to the user.
  • This library is accessible to the business analyst to permit tweaking of existing processes, creation of new processes based on existing processes, or simply to use steps or subprocesses from existing processes. By permitting such recycling, the creation of a new process is significantly simplified.
  • the sequence determines whether the user selected a process to edit, and if so, at block 325, the selected process is displayed to the user.
  • the selected process for one embodiment, shows the high level process, and may include multiple subprocesses which may be reached by drilling down.
  • the sequence then continues to block 330. If the user did not select a process to edit, the sequence continues directly to block 330.
  • the user interface including executable shapes is displayed to the user.
  • An exemplary embodiment of such a display is shown in Figure 7.
  • the toolbox 710 presents a set of processes and connectors.
  • the toolbox 710 further permits the creation of additional swim lanes.
  • Swim lanes 720 provide a differentiation between various actors or various systems. In this role-based view, the swim lanes 720 define the actors such as customer, broker, accounting, etc.
  • the business analyst may add additional swim lanes 720 using toolbox 710.
  • the process 730 includes a starting point, a number of elements 740 and connectors 750 between the elements 740.
  • the various types of functions or elements that may be added to the process have different shapes. For one embodiment, shape and color may be used to identify various types of functions.
  • the user is permitted to select an existing subprocess or step from the existing list of subprocesses in the library of processes. This simplifies implementation, since the user can simply insert a fully functional process, instead of designing it anew. If the user did not select a subprocess for insertion, the sequence continues to block 355. Otherwise, the sequence continues to block 345.
  • the user is prompted to make any connections needed to properly connect the inserted subprocess.
  • Each process and step has one or more connections, to provide a flow of the process.
  • An inserted subprocess will generally have at least one, and may have any number of connectors.
  • the user is prompted to connect each of these connectors.
  • the connectors include a tag or flag indicating the type of connection being made.
  • the sequence then continues to block 355.
  • the user is permitted to edit one or more steps, connections, processes, subprocesses - or steps - in the process.
  • Figure 8 A illustrates one embodiment of the process configuration interface reached by drilling down the "create call list” process step, shown in Figure 7.
  • the properties dialog box 810 enables the business analyst to provide a description/definition of the task.
  • the general tab 820 provides a basic description of the task.
  • the assignment tab 830 defines who should be assigned to perform this task. For one embodiment, this indicates which swim lane the task inhabits.
  • the notification tab 840 indicates whether anyone should be notified when this task is performed, while the pages tab indicates where in the process this task should occur. This indicates on which pages, and under what conditions, the task is exposed.
  • the thread bar 860 indicates where in the process the business analyst is.
  • Figure 8B illustrates one embodiment of the configuring of the task.
  • the configuration interface includes the toolbox 710 including two tabs, one for the business process 870, shown also in Figure 8A above, and one for the user interface (UI) process 875, shown here.
  • the task process configuration window 880 is the interface for configuring a task process
  • the UI configuration window 890 is the interface for configuring a page. This is the page that would be displayed to a user who is using the process, once implemented.
  • the business analyst can create the UI, and specify any aspects. For one embodiment, the business analyst can preview the user interface created in this way, and step through it.
  • the sequence continues to block 375.
  • the sequence determines whether all blocks are logically connected, e.g. all blocks have at least one connector attached to them, and all connectors are coupled to a block, e.g. there are no dangling connectors.
  • the system further verifies that the process is started and terminated properly. If any of these conditions is not met, the sequence continues to block 380, where the user is prompted to correct these errors. For one embodiment a flag or tag may indicate each of the errors that should be corrected. The sequence then returns to block 355, permitting the user to edit and correct the process.
  • Figure 4 is a flowchart of one embodiment of the responsibility transfer from the business analyst to the implementing engineer.
  • the sequence starts at block 410.
  • the checked-in completed process is received from the business analyst.
  • the present sequence may be executed at any time.
  • the sequence is automatically initiated when a completed but not yet implemented process is received from the business analyst.
  • the sequence determines whether there are elements that are not from a best practices process.
  • the checked in process may be identical to a best practices process. In that instance, no implementation is needed, since the best practices process by definition is already implemented.
  • the sequence at block 425 determines whether any of the connections have been changed. Each process consists of a plurality of elements interconnected by connectors. If neither the elements nor the connectors have changed, no implementation is required. Thus, the sequence proceeds directly to block 460, and ends.
  • the sequence determines whether there are any portions or logical steps missing.
  • a business analyst may fail to think of steps such as error checking or data validation. If there are such steps missing, the sequence continues to block 440 to identify the missing elements and flag them for the developer. For one embodiment, a general note may be attached to the process, identifying the portions/logical steps that are missing. Alternatively, the sequence may add a flag at the location where such portions/logical steps are to be inserted. If there are no portions/steps missing, the sequence continues to block 445.
  • the sequence determines whether the step/connection require additional work. For one embodiment, the sequence identifies whether the step or connection is imported from an existing best practice process. If so, the sequence determines that no additional work is required. If the step/connection is newly created, it is identified, for one embodiment as requiring additional work. For another embodiment, the system may perform further analysis to determine whether the newly created connection/step requires work. For one embodiment, the system may attempt to execute the step to determine whether additional work is required. Alternative methods of identifying whether a particular step/connection is functional implemented may be used. If the step requires work, at block 465, the step or connection is flagged. For one embodiment, the flag may specify the type of work required to implement the step/connection. For example, the flag may identify that the connection requires integration with an external service, such as a web service.
  • the sequence determines whether there are any further steps/connections that should be analyzed. If there are further steps, the sequence returns to block 445, to identify the new step/connection. If there are no further steps, the flagging sequence is completed and the sequence ends at block 460.
  • Figure 9 illustrates one embodiment of the process after the flagging is completed.
  • a number of the elements 740 and elements 750 are flagged 910-950.
  • the icons 910-950 provide visual feedback to the developer signifying the different types of work that need to be done.
  • any shape can potentially have icons next to it.
  • the icons 910-950 are designated with various shapes.
  • colors, symbols, or other differentiators may be used instead of, or in conjunction with, using different shapes.
  • Figure 5 is a flowchart of one embodiment of the implementing engineer using the process modeler to enable to the process created by the business analyst.
  • the sequence starts at block 510.
  • this sequence is available any time there is a process checked in by the business analyst that has not yet been implemented.
  • the flagged process is received from the system.
  • the developer may select a process for implementation.
  • a process may be assigned to a particular developer.
  • each process may have a priority stamp or similar indication of priority. Thus, the developer may be prompted to implement the most urgent or highest priority process.
  • the developer checks out a process for implementation.
  • FIG. 10A illustrates one embodiment of the systems view of the process, as shown to the developer.
  • the swim lane labels change, to correspond to the Systems that handle each of the processes.
  • the process modeler automatically derives the technical interface display, where each swim lane identifies a system, through a transformation of the non-technical interface display, where each swim lane identifies an actor.
  • This derivation process uses the functional blocks in the non-technical interface, which are flagged (by color, shape, etc.) identifying the system with which they are associated.
  • the designer may set his or her preference on whether to display the portions of the flow that go through the integration server.
  • the system automatically generates the integration steps from the basic data provided by the business analyst. The system can automatically infer where an integration server is needed between two steps.
  • the system may further display synchronization steps. Synchronization steps indicate where the integration server synchronizes the data in various systems, to keep a consistent status.
  • the "customer" swim lane may be differentiated to indicate that it is a different type of "system,” e.g. not one under the control of the designer.
  • the "systems” are logical system types, rather than actual systems.
  • the actual system e.g. server, Siebel system, SAP, etc.
  • the separate swim lanes do not necessarily indicate a particular instance of a system.
  • the CRM (Customer Relationship Management) system may be two separate systems, a Call Center and a Service Organization. The developer may, at his or her option, separate the CRM swim lane into multiple lanes. This type of logical separation into systems illustrates to the developer the system interface elements that will be required to implement the process defined by the business analyst.
  • the systems view of the process shows, in each swim lane, a different system.
  • the systems may include: a Siebel system, a third party system, and external systems such as the Internet.
  • the systems view provides for each step and connection an identification of which system performs the step/connection.
  • the sequence determines whether any items need to be added. As noted above, the transfer/flagging sequence may have added one or more flags indicating that logical processes/steps are missing. Additionally, the developer may determine in reviewing the process that additional elements are needed. If so, at block 530, the developer is prompted to add additional elements. The additional elements may be error correction, checking, authentication, or any other required elements.
  • Figure 10B illustrates one embodiment of a potential interface for a developer browsing through a library of available processes. The process tree 1030 illustrates the various processes available, and the subprocesses and tasks/steps available within each process. The preview window 1040 permits the developer to see the process, and drill down to see additional details if necessary.
  • the developer may use the entire process or subprocess, or may simply mine the process or subprocess for ideas, or for particular details.
  • the process list 1035 provides a list of processes that are available at the current branch of the tree 1030, including the current location(s) of the process, and any comments.
  • the sequence permits the developer to add details and implement elements and connectors defined by the business analyst.
  • the skill of implementing an element to perform an identified function or step is one known by developers.
  • the present system assures that the function/step definition transfer between the business analyst and the developer is perfect.
  • Figure 10C illustrates one embodiment of the user interface configuration window for the developer.
  • the toolbox 1050 includes, in addition to the business process 1060, and user interface controls 1065, data binding 1070.
  • Figure 10D illustrates one embodiment of the data binding.
  • the data mapping interface 1080 allows drag and drop data binding of business objects to page objects (controls).
  • the various page objects may have flags 1090, indicating as above, that further work is needed in defining the particular page object.
  • the sequence determines whether external services are used. External services are those provided by other software applications or by services accessible over a network, such as the Internet. If there are no external services being used by the process, the sequence terminates at block 555. Otherwise, the sequence continues to block 545.
  • the integration sequence is enabled.
  • the integration sequence permits a connection between the software application running the process and external services.
  • FIG 11 A illustrates one embodiment of the integration sequence.
  • the integration sequence receives messages from an external system, transforms them into common objects, and then transforms them into another system representation and sends them out.
  • the integration sequence may include conditions, forking, looping, and similar software constructs.
  • the swim lines 1110 illustrate the three active systems in this instance. They include an external service provider 1120, the integration server 1130, and the process provider 1140.
  • the external market data feed sends market events to the integration server periodically.
  • the integration server 1130 filters the data, for one embodiment using an expression filter, and transforms the data into the proper form to be received by the process provider 1140.
  • the developer is prompted to define source, formats, and transforms to integrate the external source with the present process.
  • the source defines the location and access mode for the external process.
  • the format identifies the formats for addressing the external source, and the format in which data is received from the external source.
  • the transform creates a transformation from the native format of the process to the format of the external source, and vice versa.
  • Figure 1 IB illustrates one embodiment of the export option.
  • the integration sequence export wizard exports process definitions and related meta-data in standard formats for consumption by third parties.
  • the dialog box 1160 identifies the integration sequence being exported, and permits the specification of the format for export. This is useful because it makes the integration sequence available to external programs and parties.
  • a quality assurance (Q&A) procedure may validate the process as implemented by the developer.
  • the business analyst may be given one or more opportunities to review the implemented process and verify it. Once the process is completely verified, it is made available to the employees who will use it.
  • the process is put into the library of processes that are available for use in building future processes.
  • Figure 6 illustrates one embodiment comparison between business analyst and developer features.
  • the purpose of the modeler is different.
  • the purpose of the modeler is to create and edit customized business processes.
  • the purpose of the modeler is to implement/enable the business processes created by the business analyst.
  • modeler is an integrated modeler means that the communication of the process and the elements is perfect between the business analyst and developer. Furthermore, the developer need not recreate the work of the business analyst. In prior systems, the business analyst often created the process in a visual program, which could not be used for implementation. This created a communication gap as well as duplication of labor between the business analyst and the developer.
  • the view of the enterprise process also differs between the business analyst and the developer.
  • the business analyst sees a role-based view, in which each actor has a swim lane, and each element or subprocess is associated with an actor or actors. This permits the business analyst to clearly visualize who performs each action.
  • the developer sees the process from a system-based view.
  • the system based view shows each system in a separate swim lane, and illustrates to the developer each connection between the systems that will have to be implemented.
  • the business analyst's toolset is a simplified, easy to use toolset, with more abstraction and reduced complexity.
  • the developer's toolset is a full toolset allowing modification of elements, and integration with external systems. Those systems may be external systems, or systems integrated with the software application providing the business process.
  • the business analyst need not concern himself or herself with integration of external services. Rather, the business analyst may assume that all services are available, and can be accessed by the process.
  • the developer receives a full set of integration tools, to enable the integration of the process with external systems including the Internet.
  • the integrated process modeler provides different interfaces for the business analyst and the developer.
  • the use of a single process modeler provides significant advantages to both the business analyst and the developer, building a more efficient team to create and implement business processes.
  • the best practice processes are available in a master process repository 155.
  • the processes in the master process repository 155 are, for one embodiment, processes that were pre-created.
  • the best practice processes may further include processes created by business analysts that have been implemented. When the business analyst checks in a process, it is stored in the collection of processes in progress 135. These processes are waiting for implementation by the developer, on the developer's system 1220. The developer retrieves one or more processes from the collection 135, and implements them.
  • the developer 1220 may have a local copy of the processes 1225 being edited, or may also use a separate sandbox 1255, connected to the Siebel system 1250.
  • quality assurance system 1230 permits the testing of the implemented process. Once the developer, Q&A, and the business analyst all approve of a process, it can be made available by being placed into the available processes collection 1250. These available processes 1250 are used by process users 1260 throughout the company to automate certain processes, and to create uniformity of response throughout the corporation. [0099] Note that although the above elements are described as "systems" they may be implemented on a single computer system. Alternatively, a single system may be distributed over multiple computers.
  • Figure 13 is one embodiment of a computer system that may be used with the present invention. It will be apparent to those of ordinary skill in the art, however that other alternative systems of various system architectures may also be used.
  • the data processing system illustrated in Figure 13 includes a bus or other internal communication means 1315 for communicating information, and a processor 1310 coupled to the bus 1315 for processing information.
  • the system further comprises a random access memory (RAM) or other volatile storage device 1350 (referred to as memory), coupled to bus 1315 for storing information and instructions to be executed by processor 1310.
  • Main memory 1350 also maybe used for storing temporary variables or other intermediate information during execution of instructions by processor 1310.
  • the system also comprises a read only memory (ROM) and/or static storage device 1320 coupled to bus 1315 for storing static information and instructions for processor 1310, and a data storage device 1325 such as a magnetic disk or optical disk and its corresponding disk drive.
  • Data storage device 1325 is coupled to bus 1315 for storing information and instructions.
  • the system may further be coupled to a display device 1370, such as a cathode ray tube (CRT) or a liquid crystal display (LCD) coupled to bus 1315 through bus 1365 for displaying information to a computer user.
  • a display device 1370 such as a cathode ray tube (CRT) or a liquid crystal display (LCD) coupled to bus 1315 through bus 1365 for displaying information to a computer user.
  • An alphanumeric input device 1375 including alphanumeric and other keys, may also be coupled to bus 1315 through bus 1365 for communicating information and command selections to processor 1310.
  • cursor control device 1380 such as a mouse, a trackball, stylus, or cursor direction keys coupled to bus 1315 through bus 1365 for communicating direction information and command selections to processor 1310, and for controlling cursor movement on display device 1370.
  • Another device which may optionally be coupled to computer system 1300, is a communication device 1390 for accessing other nodes of a distributed system via a network.
  • the communication device 1390 may include any of a number of commercially available networking peripheral devices such as those used for coupling to an Ethernet, token ring, Internet, or local or wide area network.
  • the communication device 1390 may further be a null-modem connection, a wireless connection mechanism, or any other mechanism that provides connectivity between the computer system 1300 and the outside world. Note that any or all of the components of this system illustrated in Figure 13 and associated hardware may be used in various embodiments of the present invention.
  • control logic or software implementing the present invention can be stored in main memory 1350, mass storage device 1325, or other storage medium locally or remotely accessible to processor 1310.
  • the present invention may also be embodied in a handheld or portable device containing a subset of the computer hardware components described above.
  • the handheld device may be configured to contain only the bus 1315, the processor 1310, and memory 1350 and/or 1325.
  • the present invention may also be embodied in a special purpose appliance including a subset of the computer hardware components described above.
  • the appliance may include a processor 1310, a data storage device 1325, a bus 1315, and memory 1350, and only rudimentary communications mechanisms, such as a small touch-screen that permits the user to communicate in a basic manner with the device.
  • the more special-purpose the device is the fewer of the elements need be present for the device to function.
  • a machine-readable medium includes any mechanism for storing or transmitting information in a form readable by a machine (e.g. a computer).
  • a machine readable medium includes read-only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory devices, electrical, optical, acoustical or other forms of propagated signals (e.g. carrier waves, infrared signals, digital signals, etc.).

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Automation & Control Theory (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention concerne un modélisateur de processus de bout en bout qui comprend un modélisateur de processus à intégration verticale qui permet de produire un aspect de conception pour un utilisateur non technique (520) et un aspect de mise en oeuvre pour un utilisateur technique et le modélisateur de processus à intégration verticale conçu pour créer un processus exécutable complet (160).
EP03814581A 2002-12-31 2003-08-12 Procede et appareil pour un modelisateur de processus integre Withdrawn EP1588349A4 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US10/334,953 US7251787B2 (en) 2002-08-28 2002-12-31 Method and apparatus for an integrated process modeller
US334953 2002-12-31
PCT/US2003/025312 WO2004061815A1 (fr) 2002-12-31 2003-08-12 Procédé et appareil pour un modélisateur de processus intégré

Publications (2)

Publication Number Publication Date
EP1588349A1 true EP1588349A1 (fr) 2005-10-26
EP1588349A4 EP1588349A4 (fr) 2008-06-18

Family

ID=32655210

Family Applications (1)

Application Number Title Priority Date Filing Date
EP03814581A Withdrawn EP1588349A4 (fr) 2002-12-31 2003-08-12 Procede et appareil pour un modelisateur de processus integre

Country Status (4)

Country Link
EP (1) EP1588349A4 (fr)
JP (1) JP2006512670A (fr)
AU (1) AU2003259807A1 (fr)
WO (1) WO2004061815A1 (fr)

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2035600A (en) 1998-11-30 2000-06-19 Siebel Systems, Inc. Development tool, method, and system for client server appications
US7051319B1 (en) 2001-03-27 2006-05-23 Siebel Systems, Inc. Method, system, and product for upgrading software objects using inherency
US7117449B1 (en) 2002-12-31 2006-10-03 Siebel Systems, Inc. Method and apparatus to present an integrated process modeler
US7665063B1 (en) 2004-05-26 2010-02-16 Pegasystems, Inc. Integration of declarative rule-based processing with procedural programming
US8335704B2 (en) 2005-01-28 2012-12-18 Pegasystems Inc. Methods and apparatus for work management and routing
US8924335B1 (en) 2006-03-30 2014-12-30 Pegasystems Inc. Rule-based user interface conformance methods
JP4907322B2 (ja) * 2006-12-01 2012-03-28 三菱電機株式会社 ワークフロー生成装置及びワークフロー生成方法及びプログラム
US8250525B2 (en) 2007-03-02 2012-08-21 Pegasystems Inc. Proactive performance management for multi-user enterprise software systems
US8843435B1 (en) 2009-03-12 2014-09-23 Pegasystems Inc. Techniques for dynamic data processing
US8468492B1 (en) 2009-03-30 2013-06-18 Pegasystems, Inc. System and method for creation and modification of software applications
US8880487B1 (en) 2011-02-18 2014-11-04 Pegasystems Inc. Systems and methods for distributed rules processing
US9195936B1 (en) 2011-12-30 2015-11-24 Pegasystems Inc. System and method for updating or modifying an application without manual coding
US10469396B2 (en) 2014-10-10 2019-11-05 Pegasystems, Inc. Event processing with enhanced throughput
US10698599B2 (en) 2016-06-03 2020-06-30 Pegasystems, Inc. Connecting graphical shapes using gestures
US10698647B2 (en) 2016-07-11 2020-06-30 Pegasystems Inc. Selective sharing for collaborative application usage
US11048488B2 (en) 2018-08-14 2021-06-29 Pegasystems, Inc. Software code optimizer and method
US11567945B1 (en) 2020-08-27 2023-01-31 Pegasystems Inc. Customized digital content generation systems and methods

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH04372686A (ja) * 1991-06-21 1992-12-25 Toyo Tanso Kk 膨張黒鉛シートの製造法
US6684388B1 (en) * 2000-08-22 2004-01-27 International Business Machines Corporation Method for generating platform independent, language specific computer code

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
See also references of WO2004061815A1 *
The technical aspects identified in the present application (Art. 92 EPC) are considered part of common general knowledge. Due to their notoriety no documentary evidence is found to be required. For further details see the accompanying Opinion and the reference below. XP002456252 *

Also Published As

Publication number Publication date
JP2006512670A (ja) 2006-04-13
WO2004061815A1 (fr) 2004-07-22
EP1588349A4 (fr) 2008-06-18
AU2003259807A1 (en) 2004-07-29

Similar Documents

Publication Publication Date Title
US7251787B2 (en) Method and apparatus for an integrated process modeller
US7117449B1 (en) Method and apparatus to present an integrated process modeler
US9632768B2 (en) Exchanging project-related data in a client-server architecture
US7493591B2 (en) Methods and systems for animating a workflow and a project plan
US8302096B2 (en) Methods and systems to perform individual tasks as a composite task
US7836103B2 (en) Exchanging project-related data between software applications
WO2004061815A1 (fr) Procédé et appareil pour un modélisateur de processus intégré
US20050235061A1 (en) Opportunity tracking information system
US20010052108A1 (en) System, method and article of manufacturing for a development architecture framework
US20060106846A1 (en) Cross-context task management
WO2004010354A2 (fr) Gestion de solutions d'affaires (bsm)
US20080270477A1 (en) Workflow method, system, and data structure
US8589306B1 (en) Open source license management
WO2019062673A1 (fr) Procédé et système de mise en œuvre de gestion reposant sur des informations sur la base de sémantisation d'entrée et de sortie
US7877283B2 (en) Multi-perspective business process configuration
Mendonca et al. A process-centric approach for coordinating product configuration decisions
US7707017B2 (en) System modeling facilitating method and apparatus
Christie A practical guide to the technology and adoption of software process automation
AU2001253522A1 (en) Method for a health care solution framework
EP1272945A2 (fr) Procede destine a une structure de soins de sante
Gould Systems analysis and design
Rodríguez et al. Model‐based assisted migration of oracle forms applications: The overall process in an industrial setting
Mounla Microsoft Dynamics 365 Extensions Cookbook
US12164934B1 (en) Robotic process automation system with advanced combinational triggers
Heaton Business intelligence cookbook: A project lifecycle approach using Oracle technology

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20050727

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL LT LV MK

DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20080519

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN

18W Application withdrawn

Effective date: 20080714

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载