A Modeling Approach for Collaborative Business Processes based on the UP-ColBPIP Language
|
|
- Beverley Norton
- 6 years ago
- Views:
Transcription
1 A Modeling Approach for Collaborative Business Processes based on the UP-ColBPIP Language Pablo David Villarreal 1, Ivanna Lazarte 1, Jorge Roa 1, Omar Chiotti 1,2 1 CIDISI, Universidad Tecnológica Nacional - Facultad Regional Santa Fe, Lavaisse 610, S3004EWB, Santa Fe, Argentina {pvillarr, ilazarte, jroa}@frsf.utn.edu.ar 2 INGAR-CONICET, Avellaneda 3657, S3002GJC, Santa Fe, Argentina {chiotti}@santafe-conicet.gov.ar Abstract. The modeling of collaborative business processes is an important issue in order to allow enterprises to implement B2B collaborations with their business partners. We have proposed an MDA-based methodology for the modeling, verification and implementation of collaborative processes. Since collaborative process models are the main artifacts in this MDA-based methodology, a suitable modeling approach is required to design collaborative processes. In this work we describe a modeling approach for collaborative processes based on the UP-ColBPIP language, which is oriented to support the model-driven development of collaborative processes and B2B information systems. The behavior of collaborative processes is modeled through interaction protocols. Enhances to the control flow constructors of interaction protocols are introduced. In addition, we describe an Eclipse-based tool that supports this language. Keywords: Collaborative Business Process, Business-to-Business, Model- Driven Development, UML Profile, Interaction Protocol 1 Introduction The modeling of collaborative business processes is an important issue in order to allow enterprises to implement B2B collaborations. Business-to-Business collaborations entail a process-oriented integration among heterogeneous and autonomous enterprises at a business level and a technological level. At the business level, enterprises focus on the design of collaborative processes to define and agree on the behavior of the inter-enterprise collaboration. A collaborative business process defines the global view of the interactions between enterprises to achieve common business goals [20]. Through these processes, partners agree to jointly carry out decisions, coordinate their actions, and exchange information through B2B systems. At the technological level, enterprises focus on the implementation, integration and interoperability of their B2B information systems to execute collaborative processes. This implies the generation of B2B specifications, i.e. interfaces of the partners systems and business process specifications based on a B2B standard, required by
2 each enterprise to execute the role performed in a collaborative process and implement it in a business process management system (BPMS). In previous works, a methodology for the modeling, verification and implementation of collaborative processes was proposed [16, 17, 20]. This methodology uses techniques, languages and methods that exploit the principles of the model-driven architecture (MDA) [13] to guarantee the alignment between the business solution and the technological solution of a B2B collaboration. This MDAbased methodology enables both the design of collaborative processes independent of the idiosyncrasies of particular B2B standards, and the automatic generation of B2B specifications based on a B2B standard from conceptual collaborative process models. The main benefits of this methodology are: (1) the increase of the abstraction level because the main development artifacts are the technology-independent collaborative process models; (2) the reduction of development time and costs along with the guarantee of alignment of the business solution with the technological solution, since process specifications are generated automatically from collaborative process models; and (3) the independence of collaborative process models from B2B standards. Since collaborative process models are the main artifacts in this MDA-based methodology, a suitable modeling approach is required for collaborative processes. A collaborative process model should be independent of the implementation technology, understandable and easy to read by business analysts and system developers. Besides, the modeling approach should fulfill the capabilities required by B2B interactions [20, 22]: global choreography of B2B interactions, enterprise autonomy, decentralized management, peer-to-peer interactions and representation of complex negotiations. In this work we describe a modeling approach for collaborative business processes based on the UP-ColBPIP language (UML Profile for Collaborative Business Processes based on Interaction Protocols). This is oriented to support the modeldriven development of collaborative processes and B2B information systems and fulfill the requirements mentioned above. The behavior of collaborative processes is modeled through interaction protocols, which are focused on the representation of the communicative aspects of B2B interactions. Enhances to this language are introduced to provide a complete set of control flow constructors to model collaborative processes. In addition, a case tool that supports the UP-ColBPIP language is presented, which is built on the Eclipse open development platform [3]. This paper is organized as follows. Section 2 describes the MDA-based methodology for collaborative processes. Section 3 describes the modeling approach for collaborative processes based on the UP-ColBPIP language. Section 4 presents the Eclipse-based tool that supports this language. Section 5 discusses related work and Section 6 presents conclusions and future work. 2 MDA-based Methodology for Collaborative Business Processes The model-driven architecture (MDA) [13] was identified as a key enabler to support the development of collaborative processes [17]. An MDA-based approach was proposed to support the modeling of collaborative processes and the automatic generation of process specifications and partners system interfaces based on a B2B
3 standard [20]. Also, an MDA-based approach was proposed to generate formal specifications of collaborative processes and verify if they are well-formed [21]. Both approaches make up the MDA-based methodology for collaborative processes [17], which consists of three phases: analysis and design of collaborative processes, verification of collaborative processes and generation of B2B specifications. The analysis and design of collaborative processes is about the modeling of these processes from a business perspective, i.e. using concepts that are less bound to the implementation technology and are closer to the B2B collaboration domain. To support this phase, the UP-ColBPIP language [16, 20] is used in order to enable the modeling of technology-independent collaborative processes. The second phase consists of verifying the correctness of collaborative processes defined in a UP-ColBPIP model. The purpose is to support the verification of these processes at an early stage of the development, when most of the fundamental decisions of a B2B collaboration are carried out, i.e. previous to the generation of the technological solution. The verification is essential to allow partners to make sure the behavior of collaborative processes is well-defined. To support this, the MDA-based approach for generating Petri Net specifications from a UP-ColBPIP model is applied [21] (see Figure 1.a). Interaction protocols are formalized, transformed and mapped into Colored Petri Net [7] specifications, which are then verified with CPN Tools [2]. Fig. 1. MDA-based approaches for Collaborative Business Processes Finally, the third phase consists of selecting the target implementation technology (i.e. the B2B standards) and generating the B2B specifications (i.e. the business process specifications and interfaces of the partners systems) that fulfill the collaborative processes defined in the first phase. Figure 1.b shows the MDA-based approach that supports this phase. The input is a UP-ColBPIP model that contains collaborative processes based on interaction protocols and partners business interfaces. From this model, technology-specific business process models and technology-specific partners interface models are made. Then, B2B specifications are generated. In previous work we described the application of this MDA approach to generate technological solutions based on the widely used B2B standards: ebxml [20], WS-BPEL [18] and WS-CDL [19]. We showed how UP-ColBPIP models can be used to generate technological solutions with these standards.
4 3 Modeling Collaborative Processes with the UPColBPIP Language The UP-ColBPIP language extends the UML2 semantics to model technologyindependent collaborative processes [16, 20]. The language was defined as a UML Profile in order to provide well-known graphical notations for modeling collaborative processes that were easy to understand by business analysts and system designers. This language encourages a top-down approach to model collaborative processes and provides the conceptual elements to support the modeling of five views: The B2B Collaboration View defines the participants (partners and their roles) of a B2B collaboration with their communication relationships. UP-ColBPIP extends the semantics of UML2 collaborations to represent B2B Collaborations. This view also describes the hierarchy of common business goals that partners agree on. To represent it, UP-ColBPIP extends the semantics of UML classes and objects. The Collaborative Business Process View is concerned with the identification of collaborative processes required to achieve the agreed business goals. Current management principles suggest a business process should achieve a business goal. Key performance indicators can be associated with business goals to allow the evaluation of collaborative processes for their redesign or improvement. UP- ColBPIP extends the semantics of use cases to define collaborative processes as informal specifications of a set of actions performed by partners to achieve a goal. The Interaction Protocol View defines the behavior of collaborative processes through the definition of interaction protocols. This view is described below. The Business Document View focuses on representing business documents to be exchanged in collaborative processes. Business documents and their types are represented in class diagrams, and they are referenced in collaborative processes and interaction protocols. UP-ColBPIP does not provide any particular concepts to define the syntactic and semantics structure of business documents. To do that, other suitable languages can be used, such as the approach proposed in [1]. The Business Interface View describes the interfaces of each role performed by partners. A business interface (service) contains business operations that support the asynchronous message exchange of interaction protocols. To represent it, UP- ColBPIP extends the semantics of the UML2 composite structures and interfaces. Due to space limitations, in this work we only describe the Interaction Protocol View in order to present the modeling approach we propose to model the behavior of collaborative processes. More details about this language can be found in [20]. 3.1 Interaction Protocol View One of the main purposes of this language is to fulfill the requirements for the conceptual modeling of collaborative processes and B2B collaborations [20, 22]: global view of the interactions between partners, enterprise autonomy, decentralized management, peer-to-peer interactions and representation of complex negotiations. To fulfill these requirements, the UP-ColBPIP language incorporates the interaction protocol concept to define the behavior of collaborative processes. An interaction protocol describes a high-level communication pattern through a choreography of business messages between partners who play different roles.
5 Modeling interaction protocols focus on representing the global view of the interactions between partners. The message choreography describes the global control flow of peer-to-peer interactions between partners as well as the responsibilities of the roles they fulfill. This also enables the representation of the decentralized management of the interactions between partners. Interaction protocols focus on the exchange of business messages representing interactions between partners, preserving the enterprise autonomy. Internal activities of the partners cannot be defined in protocols and hence, they are hidden to partners. In addition, B2B interactions should not only represent the information exchange but also the communication of actions between partners. Coordination and communication aspects of B2B interactions are represented in interaction protocols through the use of speech acts. In an interaction protocol, a business message has an associated speech act, which represents the intention the sender has with respect to the business document exchanged in the message. Thus, decisions and commitments between partners can be known from the speech acts. This enables the definition of complex negotiations and avoids the ambiguity in the semantics and understanding of the business messages of collaborative processes. UP-ColBPIP extends the semantics of UML2 Interactions to model interaction protocols. Hence, they are defined using UML2 Sequence Diagrams. Following we describe the main conceptual elements used to define interaction protocols. Partners and the Role they fulfill are represented through lifelines. The basic building blocks of an interaction protocol are the business messages. A business message defines a one-way asynchronous interaction between two roles, a sender and a receiver. It contains a business document (the exchanged information) and its semantics is defined by the associated speech act. In this way, a business message expresses that the sender has done an action that generates the communication of a speech act representing the sender s intention with respect to the exchanged business document. Also, the message indicates the sender s expectation is that the receiver acts according to the semantics of the speech act. A Protocol Reference represents a sub-protocol or nested protocol. When the subprotocol is called, the protocol waits until the sub-protocol ends. Protocols have an implicit termination. A Termination represents an explicit end event of a protocol. Termination events are: success, which implies the successful termination; and failure, which implies the protocol business logic ends in an unexpected way. A Time Constraint denotes a deadline associated with messages, control flow segments or protocols; i.e. the available time limit for the execution of such elements. A time constraint can be defined using relative or absolute date and time. A Control Flow Segment (CFS) represents complex message sequences. It contains a control flow operator and one or more interaction paths. An interaction path contains a ordered sequence of protocol elements: messages, termination events, protocol references and nested control flow segments. The semantics of a CFS depends on the operator used. Some control flow operators of exception handling were adapted and other advanced synchronization and multiple instance operators were introduced in order to provide a complete set of control flow constructors to model collaborative processes. The aim is to fulfill the main workflow patterns [14] for the modeling of collaborative processes. The control flow operators of the UP-ColBPIP language are:
6 The And operator (Table 1.a) represents the parallel execution of paths. The thread of control is passed to the next protocol element when all paths are completed. The Xor operator represents that only one path can be executed from a set of alternative paths. A data-based Xor contains conditions on the paths to be evaluated to select the execution path (see Table 1.b). An event-based Xor is based on the occurrence of the sending event of the first message of each path to select the execution path. Paths have no associated conditions. A timer can also be defined on a path to represent the execution of the path when a time event occurs. The Or operator represents two or more alternative paths that can be executed. Path conditions must be evaluated to allow the execution of each path. Four types of path synchronization can be defined, which are denoted by the corresponding label at the top-left of the CFS (see Table 1.c). (1) Synchronizing Merge (<<Sync- Merge>>): the thread of control is passed to the next protocol element when each enabled path is completed. (2) Discriminator (<<Disc>>): the thread of control is passed to the next protocol element when the first interaction path is completed. (3) N out of M (<<N out of M>>) represents the convergence of two or more paths (say M) into a single subsequent path. The synchronization event must be enabled once N paths are completed. The remaining paths (M-N) are ignored. (4) Multimerge (<<Multi-Merge>>): for each completed path there is a thread of control which is passed to the next protocol element. The Loop operator represents a path that is executed several times while its condition is satisfied. An Until loop has the condition (1, n) so that the path is executed at least once; a While loop has the condition (0, n) and it means that the execution of the path is performed zero or more times (see Table 1.d). The Exception defines the path to be followed after an exception takes place, which is identified at design time. A CFS with the Exception operator consists of one path that encloses the scope of the exceptions (for all protocol element involved in the path) and other exception handler paths, one for each exception to be caught and managed. An exception handler path has an exception condition to determine when the exception is raised. After an exception handler path is completed, the protocol continues with its normal execution. Two types of exception can be managed: time and logical. (see Table 1.e). The Cancel operator defines the path to be followed after an exception takes place. The difference between Cancel and Exception operators is that the former finalizes the execution of the protocol when the path that handles the exception is completed. A control flow segment with a Cancel operator is used to finalize a protocol in a coherent and consistent way after an exception. The Multiple Instances operator is used to represents multiple instances of an interaction path. Four types of synchronization of multiple instances can be defined, which are denoted by a label at the top-left of the CFS (see Table 1.f). The number of instances can be defined: (1) at design-time (<<DT>>); (2) at run-time (<<RT>>), where the variable that contains the number of instances is indicated; (3) without a priori run-time knowledge (<<WRTK>>), where the expression condition that enables the creation of new instances is indicated. Multiple instances without synchronization are denoted by the <<WS>> label. The If operator represents a path which is enabled when its condition is evaluated to True. Else, a path with the Else condition is executed if it is defined.
7 Table 1. Graphical notations of the control flow segments of an interaction protocol Enterprise X :Role A Xor SpeechAct(BusinessDocument) Enterprise Y :Role B [Var1=True] SpeechAct(BusinessDocument) SpeechAct(BusinessDocument) [Var2=True] Enterprise X :Role A a) SpeechAct(BusinessDocument) Enterprise Y :Role B b) c) Loop [(0,n), Var1=True] SpeechAct(BusinessDocument) SpeechAct(BusinessDocument) d) f) e) As an example, Figure 2 shows a sequence diagram of the Collaborative Demand Forecast protocol, which describes a collaborative process to be carried out as part of a Collaborative Planning, Forecasting and Replenishment (CPFR) business model [15]. This protocol defines a simple negotiation process between a customer and a supplier to collaborate and agree on a demand forecast of products to be exchanged. Figure 2. Collaborative Demand Forecast protocol. The process begins with the customer who requests for a demand forecast. The request message conveys the data to be considered in the forecasting (e.g.: products,
8 forecast time-frame). The supplier handles the request and should respond by accepting or rejecting it. If it is accepted, the supplier undertakes to realize the required forecast, as it is indicated by the agree speech act; otherwise, the process finishes with a failure. If the supplier accepts the request, the customer informs in parallel a sales forecast of its points of sales (POS) and its planned sale policies. With this information, the supplier then generates a demand forecast, informs it to the customer and the process ends. The response messages that the supplier sends and the information messages the customer sends have defined time constraints with relative times that represent the deadline for the sending and reception of these messages. As an example, the deadlines of the agree and refuse messages indicate these messages have to be sent two days in advance, after the occurrence of the first message. In order to handle time exceptions on these messages, the control flow segment cancel is added. It contains an interaction path that spans the messages with time constraints, and it also contains two other exception paths that handle the time exceptions defined in the above messages. In both paths, the exception handling consists of the sending of a cancel message. 4 Eclipse-based Tool for Modeling Collaborative Processes In order to provide a development environment for the MDA-based methodology for collaborative business processes and support the modeling approach based on the UP- ColBPIP language, we have developed a tool that supports this language and the model transformations proposed in this methodology. Several requirements were considered in the development of the tool: implementation of visual editors to support the UP-ColBPIP language, implementation of the metamodel of this language to manipulate and validate the constraints of UP-ColBPIP models, extension mechanisms to allow the addition of new editors and model transformation machines, management of B2B collaboration projects, and separation of UP-ColBPIP model and diagram files to facilitate model-to-model and model-to-code transformations. The developed tool is based on the Eclipse open development platform [3]. There are several tools for modeling business processes that are based on this platform. Thus, we take advantage of a well-known development environment and we can also make a reuse and integration of other Eclipse-based tools with our tool. The Architecture of the Eclipse-based Tool for Modeling Collaborative Processes consists of the following components (Figure 3): A set of Eclipse-based plug-ins, which are graphical editors that support the definition of UP-ColBPIP diagrams and models. They were built with the Graphical Modeling Framework (GMF) [5], which provides an infrastructure for developing visual editors based on the Eclipse Modeling Framework (EMF) [4] A Transformation Machine for Petri Net specifications, which was built using the Eclipse Java Emitter Templates (JET) [9] to carry out model-to-code transformations. This machine takes a UP-ColBPIP model as input and produces a Petri Net specification for each interaction protocol defined in the input model. A Transformation Machine for BPEL specifications that is built using the ATL [10]. It takes a UP-ColBPIP model as input, and by means of model
9 transformations [18] it produces BPEL specifications of partner roles for each protocol of the input model, as well as a WSDL specification for each partner. Fig. 3. Architecture of the Eclipse-based Tool for Collaborative Processes The Eclipse plug-ins for the UP-ColBPIP language were developed by means of GMF and support the UP-ColBPIP language. The UP-ColBPIP metamodel was implemented by means of EMF. In order to define a B2B Collaboration and its collaborative processes it is necessary to create a new UP-ColBPIP project. A UP- ColBPIP model is created when a new B2B Collaboration diagram is generated with the B2B Collaboration Editor plug-in. Then, collaborative processes and interaction protocol diagrams can be created by using the Collaborative Business Process Editor and the Interaction Protocol Editor. An interaction protocol diagram is created when a new collaborative process is defined. Each diagram is stored in a file separated from the file containing the UP-ColBPIP model. Thus the model is clearly separated from its graphical representation. Figure 4 shows the Eclipse-based tool with the example described in section 3.1. The organization of the UP-ColBPIP project is shown in the Project Explorer view. It consists of a folder for the UP-ColBPIP model and a folder for each view of the UP- ColBPIP model with their corresponding diagrams. The main edition area shows tabs that contain the editors. In particular, the Interaction Protocol editor with the interaction protocol Collaborative Demand Forecast is shown. In the right side of Figure 4 is the tool palette with the elements to model an interaction protocol. A protocol can be defined and modified through the drag and drop of the palette s elements into the diagram. On the bottom side, the property view is used to set attributes of the model elements defined in the diagrams. 5 Related Work Several modeling languages allow the representation of B2B business processes. However, it is necessary to highlight what kind of B2B processes they support. Modeling interaction protocols focus on representing the global control flow of interactions between partners, required to model collaborative processes. Instead, activity-oriented business process languages such as UML2 Activity Diagrams or the Business Process Modeling Notation (BPMN) [12] are more suitable to model interface or private processes from the viewpoint of a partner. Although BPMN allows the definition of B2B processes by representing the message exchange among
10 interface processes of the partners (BPMN pools), it does not provide the semantics to describe the dependencies of the global control flow of the message exchange. Fig. 4. A B2B Collaboration project created with the Eclipse plug-ins for UP-ColBPIP The UN/CEFACT modeling methodology (UMM) [8] is a UML modeling approach for global choreographies of B2B scenarios. It is a top-down approach that makes use of worksheets to capture domain requirements. UMM encourages the definition of the global choreography of a collaborative process in a hierarchy of views. A business collaboration view represents a collaborative process described by a choreography of business transactions, which are its basic construction blocks. The partner actions and exchanged business documents are described in each business transaction view, according to a business transaction pattern. This hierarchical approach makes it difficult to model and understand the interactions between partners in a high abstraction level along with the global choreography of a collaborative process. Thus, to identify these interactions into a business collaboration, the knowledge of each business transaction, which is modeled in a separate way of the choreography of the business collaboration, is required. This also results in a higher complexity to model negotiations in collaborative processes. In [11], a UML2 modeling approach that supports platform independent modeling of Web Service collaboration protocols was proposed. This approach uses a hierarchy of views similar to the approach proposed by UMM to model collaborative processes. Another modeling approach to describe global choreographies is Let s Dance [23]. This is an independent-technology language, although it focuses on the modeling of Web Services choreographies that support service interaction patterns.
11 A survey of business process modeling methodologies based on UML has shown that the MDA-based methodology for collaborative processes, which uses the modeling approach based on the UP-ColBPIP language, is comprehensive enough to address most of the required aspects for collaborative processes [6]. In interaction protocols, business messages describing interactions between partners are the basic construction blocks. The global choreography of a protocol defines the message sequences. In addition, the use of speech acts associated with messages and the types of control flow segments allow the representation of complex negotiations. 6 Conclusions and Future Work In this work we have presented a modeling approach for collaborative business processes based on the UP-ColBPIP language. This is oriented to be used in a MDAbased methodology for collaborative processes. This language enables the design of technology-independent collaborative process models, which are the main development artifacts in order to generate formal specifications and B2B specifications for the verification and implementation of collaborative processes. Through the use of interaction protocols to model collaborative processes, the language uses suitable abstractions to represent the features of B2B collaborations and fulfill the modeling requirements of collaborative processes. Interaction protocols allow describing the commonly agreed global choreography of interactions between partners. Modeling interaction protocols focus not only on information exchange, but also on the coordination and communicative aspects of B2B interactions. Business messages based on speech acts allow representing intentions that partners have when they exchange information in collaborative processes. By means of speech acts, parties can create, modify, cancel or fulfill commitments. This enables the definition of complex negotiations as well as provides a suitable semantics without ambiguity to achieve a common understanding of the meaning of each message. In this work we have provided a complete set of control flow operators to model the message choreography of interaction protocols, based on the workflow patterns, in order to model complex control flow structures in collaborative processes. Through the use of this UML Profile, business analysts and system developers can apply well-known notations for modeling collaborative processes and can also use existing UML2 case tools to model these processes. However, in order to provide a tool that can enforce the metamodel of the UP-ColBPIP language and enable the automatic generation of formal specifications and B2B specifications, we have introduced a case tool based on the Eclipse platform. This tool consists of visual editors implemented as Eclipse plug-ins that support the UP-ColBPIP language. Future work is aimed at providing a verification and validation methodology for collaborative processes. To enhance the support for verification, the new control flow constructors of interaction protocols will be formalized by using Colored Petri Nets and the model transformations that generate CPNs will be updated. The validation will be done through an ontology-based semantics analysis of the speech acts used in the messages of a protocol.
12 References 1. Caliusco, M.L., Galli, M.R., Chiotti O.: Technologies for Data Semantic Modeling. International Journal of Metadata Semantics and Ontology. Vol 1(4), (2006) 2. CPN tools Eclipse Org. Eclipse Platform Eclipse Org. Eclipse Modeling Framework Eclipse Org. Graphical Modeling Framework Folmer, E., Bastiaans, J.: Methods for Design of Semantic Message-Based B2B Interactions Standards. In: Enterprise Interoperability III, pp Springer London (2008) 7. Girault, C., Valk, R.: Petri Nets for System Engineering: A Guide to Modeling, Verification, and Applications, Springer-Verlag New York, Inc (2001) 8. Huemer, C., Liegl, P., Motal, T., Schuster, R., Zapletal, M.: The Development Process of the UN/CEFACT Modeling Methodology. In: Int. Conf. on Electronic Commerce 2008 (2008) 9. Java Emitter Templates Jouault, F, and Kurtev, I: Transforming Models with ATL. In: Satellite Events at the MoDELS LNCS, vol. 3844, pp Springer, Heidelberg (2006) 11. Kramler, K., Kapsammer, E, Kappel. G., Retschitzegger, W.: Towards Using UML 2 for Modelling Web Service Collaboration Protocols. In: First International Conference on Interoperability of Enterprise Software and Applications (2005). 12. OMG. BPMN V1.1 (January 2008), OMG. MDA Guide V1.0.1 (2003), van der Aalst, W.M.P, ter Hofstede, A.H.M., Kiepuszewski, B., Barros, A.P. Workflow Patterns. J. Distributed and Parallel Databases, 14(3), (2003) 15. VICS. An Overview of Collaborative Planning, Forecasting and Replenishment (CPFR) Villarreal, P.: Method for the Modeling and Specification of Collaborative Business Processes. PhD Thesis. National Technological University, Santa Fe, Argentina (2005) 17. Villarreal, P., Salomone, E, Chiotti O.: A MDA-based Development Process for Collaborative Business Processes. In: European Workshop on Milestone, Models and Mappings for Model-Driven Architecture (3M4MDA), Bilbao, España (2006) 18. Villarreal, Salomone, Chiotti: MDA Approach for Collaborative Business Processes: Generating Technological Solutions based on Web Services Composition. In: 9th Ibero- American Workshop of Requirements Engineering and Software Environments (2006) 19. Villarreal, P., Salomone, H.E. and Chiotti, O.: Transforming Collaborative Business Process Models into Web Services Choreography Specifications. In: Lee, J., Shim, J., Lee, S., Bussler, C., (eds.) DEECS 2006, LNCS, vol. 4055, pp Springer, Heidelberg (2006) 20. Villarreal, P., Salomone, H.E. and Chiotti, O.: Modeling and Specifications of Collaborative Business Processes using a MDA Approach and a UML Profile. In: Rittgen, P. (eds): Enterprise Modeling and Computing with UML. Idea Group Inc (2007) 21. Villarreal, P., Roa, J., Salomone, H.E. and Chiotti, O.: Verification of Models in a MDA Approach for Collaborative Business Processes. In: 10th Ibero-American Workshop of Requirements Engineering and Software Environments, Venezuela (2007) 22. Weske, M.: Business Process Management: Concepts, Languages, Architectures. Springer Press, Heidelberg (2007) 23. Zaha, J.M., Barros, A., Dumas, M., ter Hofstede, A.H.M.. Let's Dance: A Language for Service Behavior Modeling. In: 14th Int Con on Cooperative Information Systems, France (2006)
A Methodology for the Design, Verification, and Validation of Business Processes in B2B Collaborations
A Methodology for the Design, Verification, and Validation of Business Processes in B2B Collaborations Student: Jorge M. Roa 1 Supervisors: Pablo Villarreal 1, Omar Chiotti 1,2 1 CIDISI, Universidad Tecnológica
More informationPossibilities for Modeling and Integration of Business Processes*
BULGARIAN ACADEMY OF SCIENCES CYBERNETICS AND INFORMATION TECHNOLOGIES Volume 5, No 1 Sofia. 2005 Possibilities for Modeling and Integration of Business Processes* Hristina Daskalova, Vladislava Grigorova,
More informationA MODEL BASED SYSTEMS ENGINEERING PROCESSES DEPLOYMENT FRAMEWORK
A MODEL BASED SYSTEMS ENGINEERING PROCESSES DEPLOYMENT FRAMEWORK Clémentine Cornu, Bernard Chiavassa Eurocopter, ETZP, Aéroport International Marseille Provence 13725 Marignane Cedex France {Clementine.Cornu,
More informationBusiness Process Modeling
Business Process Modeling Jaelson Castro jbc@cin.ufpe.br Jaelson Castro 2016 1 Objectives Business processes Modeling concurrency and synchronization in business activities BPMN Diagrams Jaelson Castro
More informationALEM-T: A Modelling Tool for Autonomous Logistic Processes
ALEM-T: A Modelling Tool for Autonomous Logistic Processes B. Scholz-Reiter (2), T. Hildebrandt, J. Kolditz Planning and Control of Production Systems, University of Bremen, Germany Abstract Autonomous
More informationBPMN Guide Quick Start. by Bizagi BPM
BPMN Guide Quick Start by Bizagi BPM Recruitment and Selection 1 Table of Contents Scope... 2 BPMN 2.0 Business Process Modeling Notation... 2 Why Is It Important To Model With BPMN?... 2 Introduction
More informationInformation Technology to manage information exchange in a collaborative relationship between manufacturing enterprises
Information Technology to manage information exchange in a collaborative relationship between manufacturing enterprises PhD student: Ing. Caliusco María Laura. RESEARCH AREA Supply Chain Management, Agent-oriented
More informationBusiness Process Modeling Information Systems in Industry ( )
Business Process Modeling Information Systems in Industry (372-1-4207 ) Arnon Sturm The material of this presentation is adopted from various people including:, Pnina Soffer, Iris Reinhartz-Berger 1 Outline
More informationInterface Adaptation: Bridging Collaboration Agreements and Web Services
Interface Adaptation: Bridging Collaboration Agreements and Web Services Marlon Dumas Senior Lecturer Queensland University of Technology (QUT) Australia Visiting Researcher SAP Research Centre, Brisbane
More informationModeling Process Aware Information Systems with BPMN
Modeling Process Aware Information Systems with BPMN Fabrizio Maria Maggi Based on lecture material by Marlon Dumas (University of Tartu, Estonia) and Wil van der Aalst (Eindhoven University of Technology,
More informationService Engagements. The Evolution of IT
The Evolution of IT Applications: Control of computations hidden in code; integration a nightmare Workflows: Control abstracted out; integration still difficult Standards-driven orchestration: Integration
More informationPrerequisites It is recommended that the participants have a working knowledge of traditional Business Analysis tasks and techniques.
BA31 - Unified Modeling Language (UML) for Business Analysts This course will provide Business Analysts with new capabilities to improve their skills with using visual modeling techniques to document requirements.
More informationOrganizing the Business Process Management Space. Mathias Weske
Organizing the Business Process Management Space Mathias Weske People 2 Real-World Example FP6 IP on Service composition platform Detailed project plan Sub projects dealing with Architecture Case Studies
More informationPattern-based Analysis of the Controlflow Perspective of UML Activity Diagrams
Pattern-based Analysis of the Controlflow Perspective of UML Activity Diagrams Petia Wohed Wil M.P. van der Aalst Marlon Dumas Arthur H.M. ter Hofstede Nick ussell UHP (SU/KTH) TUE & QUT QUT QUT QUT Queensland
More informationModeling and Execution of Multienterprise Business Processes
Modeling and Execution of Multienterprise Business Processes Robert Singer FH Joanneum Dep. of Applied Computer Sciences Alte Poststraße 147 8020 Graz, Austria robert.singer@fh-joanneum.at Johannes Kotremba
More informationUsing UN/CEFACT S Modelling Methodology (UMM) in e-health Projects
Using UN/CEFACT S Modelling Methodology (UMM) in e-health Projects P. García-Sánchez, J. González, P.A. Castillo, and A. Prieto Department of Computer Architecture and Computer Technology, CITIC-UGR, University
More informationDYNAMIC CATENATION AND EXECUTION OF CROSS ORGANISATIONAL BUSINESS PROCESSES THE JCPEX! APPROACH
October 2010 DYNAMIC CATENATION AND EXECUTION OF CROSS ORGANISATIONAL BUSINESS PROCESSES THE JCPEX! APPROACH S-BPM ONE 2010 - Karlsruhe MOTIVATION I Globalization and increased market transparency Product
More informationSOA Enabled Workflow Modernization
Abstract Vitaly Khusidman Workflow Modernization is a case of Architecture Driven Modernization (ADM) and follows ADM Horseshoe Lifecycle. This paper explains how workflow modernization fits into the ADM
More informationWorkflow Model Representation Concepts
Workflow Model Representation Concepts József Tick Institute for Software Engineering, John von Neumann Faculty, Budapest Tech tick@bmf.hu Abstract: Workflow management and the possibilities of workflow
More informationSOP 4 EBPM: Generating Executable Business Services from Business Models*
SOP 4 EBPM: Generating Executable Business Services from Business Models* Rubén de Juan-Marín 1 and Rubén Darío Franco 2 1 Instituto Tecnológico de Informática Univ. Politécnica de Valencia, 46022 Valencia,
More informationLoosely-Coupled Process Automation in Medical Environments
CAiSE'06 DC 1185 Loosely-Coupled Process Automation in Medical Environments Jurate Vysniauskaite Departement of Informatics, University of Zurich, Binzmuhlestr. 14, 8050 Zurich, Switzerland jurate@ifi.unizh.ch
More informationFrom Service Conversation Models to WS-CDL
Association for Information Systems AIS Electronic Library (AISeL) AMCIS 2009 Proceedings Americas Conference on Information Systems (AMCIS) 2009 Karthikeyan Umapathy University of North Florida, k.umapathy@unf.edu
More informationInternational Journal of Computing and Business Research (IJCBR) ISSN (Online) :
International Journal of Computing and Business Research (IJCBR) ISSN (Online) : 2229-6166 Volume 3 Issue 2 May 2012 LATEST PROGRAMMING LANGUAGE TOOLS FOR BUSINESS PROCESS MODELLING Dr. Ram Shukla, Faculty
More informationBusiness Process Management (BPM) Lecture 2: Introduction to BPMN
MTAT.03.231 Business Process Management (BPM) (for Masters of IT) Lecture 2: Introduction to BPMN Marlon Dumas marlon.dumas ät ut. ee Process Modelling Management 2 What is a Model? Prepare shipment Ship
More informationBusiness Processes Modelling MPB (6 cfu, 295AA)
Business Processes Modelling MPB (6 cfu, 295AA) Roberto Bruni http://www.di.unipi.it/~bruni 21 - Event-driven process chains!1 Object Finish image f finish failed Start u V V Evaluate e V redo Create thumbnail
More informationSlide 1. Slide 2. Slide 3. Objectives. Who Needs Interoperability? Component 9 Networking and Health Information Exchange
Slide 1 Component 9 Networking and Health Information Exchange Unit 8 Enterprise Architecture Models This material was developed by Duke University, funded by the Department of Health and Human Services,
More informationMTAT Business Process Management (BPM) (for Masters of IT) Lecture 2: Introduction to BPMN
MTAT.03.231 Business Process Management (BPM) (for Masters of IT) Lecture 2: Introduction to BPMN Marlon Dumas marlon.dumas ät ut. ee Recap: BPMN Lifecycle Goal definition Process modelling (as-is) Process
More informationSoaML Introduction. SoaML history
Service-oriented Heterogeneous Architecture and Platforms Engineering SoaML Introduction SoaML history 2006, September OMG RFP 2007, June 3 initial submissions 2008 & 2009 Merge process 2009, December
More informationDE Services in Ecosystem Oriented Architectures
DE Services in Ecosystem Oriented Architectures Paul Malone Waterford Institute of Technology, Telecommunications Software & Systems Group (TSSG) http://www.tssg.org pmalone@tssg.org Introduction This
More informationGlobal Electronic Commerce through ebxml and Service Oriented Architectures
Lingnan University From the SelectedWorks of Prof. YEUNG Wing-lok December 4, 2008 Global Electronic Commerce through ebxml and Service Oriented Architectures W. L. Yeung, Lingnan University, Hong Kong
More informationProcesses in BPMN 2.0
Process Management Whitepaper Dipl.-Ing. Walter Abel Managing Director Dipl.-Ing. Walter Abel Management Consulting Karl Czerny - Gasse 2/2/32 A - 1200 Vienna Phone: (+43 1) 92912 65 Fax.: (+43 1) 92912
More informationEfficient Business Service Consumption by Customization with Variability Modelling
Efficient Business Service Consumption by Customization with Variability Modelling Michael Stollberg and Marcel Muth SAP Research, Chemnitzer Str. 48, 01187 Dresden, Germany (michael.stollberg,marcel.muth)@sap.com
More informationMethods for the specification and verification of business processes MPB (6 cfu, 295AA)
Methods for the specification and verification of business processes MPB (6 cfu, 295AA) Roberto Bruni http://www.di.unipi.it/~bruni 21 - Event-driven process chains 1 Object Finish image f finish failed
More informationUsing Patterns for Communicating About Flexible Processes
Using Patterns for Communicating About Flexible Processes 1 Ralf Laue 1 and Kathrin Kirchner 2 University of Applied Sciences of Zwickau, Department of Computer Science Dr.-Friedrichs-Ring 2a, 08056 Zwickau,
More informationA Semantic Service Oriented Architecture for Enterprise Application Integration
2009 Second International Symposium on Electronic Commerce and Security A Semantic Service Oriented Architecture for Enterprise Application Integration Liyi Zhang Center for Studies of Information Resources,
More informationModeling e-government processes with UMM
Modeling e-government processes with UMM Philipp Liegl 1, Robert Mosser 2, Rainer Schuster 1 and Marco Zapletal 3 1 Research Studios Austria, Austrian Research Centers GmbH - ARC 2 Institute for Distributed
More informationEXTENDING THE EPC AND THE BPMN WITH BUSINESS PROCESS GOALS AND PERFORMANCE MEASURES
EXTENDING THE EPC AND THE BPMN WITH BUSINESS PROCESS GOALS AND PERFORMANCE MEASURES Birgit Korherr, Beate List Women's Postgraduate College for Internet Technologies, Institute of Software Technology and
More informationComponent Based System Framework for Dynamic B2B Interaction
Component Based System Framework for Dynamic B2B Interaction Jinmin Hu Paul Grefen Department of Computer Science, University of Twente P.O. Box 217, 7500 AE Enschede, the Netherlands E-mail: {jimhu, grefen}
More informationAn Extension of Business Process Model and Notation for Security Risk Management
UNIVERSITY OF TARTU FACULTY OF MATHEMATICS AND COMPUTER SCIENCE INSTITUTE OF COMPUTER SCIENCE Olga Altuhhova An Extension of Business Process Model and Notation for Security Risk Management Master s thesis
More informationConceptual Process Modeling Language: Regulative Approach
Conceptual Process Modeling Language: Regulative Approach Oleg Svatoš Department of Information Technologies, University of Economics, W.Churchill sqr. 4,130 67 Prague 3, Czech Republic, Keywords: analysis
More informationBIAN with BPS Design Methodology
IBM Industry Models Development BIAN with BPS Design Methodology SOA Industry Models v.8.8 IBM Industry Models 4-13-2016 Table of Contents BIAN with BPS Design Methodology...2 1.1 BIAN...2 1.1.1 BIAN Service
More informationIBM Rational Systems Developer, Version 7.0
Simplify model-driven development for software products and systems IBM Rational Systems Developer, Version 7.0 Highlights Offers integrated design and development, accommodating visualization and editing
More informationModel-Based Development with SoaML
Model-Based Development with SoaML Brian Elvesæter, Cyril Carrez, Parastoo Mohagheghi, Arne-Jørgen Berre, Svein G. Johnsen and Arnor Solberg 1 Introduction and Overview Our MDSE methodology aims to integrate
More informationService-Oriented Computing
Service-Oriented Computing edited by Dimitrios Georgakopoulos and Michael P. Papazoglou The MIT Press Cambridge, Massachusetts London, England 2009 Massachusetts Institute of Technology All rights reserved.
More informationA Standards Framework for Value Networks in the Context of Industry 4.0
A Standards Framework for Value Networks in the Context of Industry 4.0 A. Mazak, C. Huemer Business Informatics Group, TU Vienna, Vienna, Austria {mazak,huemer}@big.tuwien.ac.at Abstract The German initiative
More informationBuilding Global Workflow From The Scratch An Approach Based On Integration of Heterogenic Workflows by Mediators
Building Global Workflow From The Scratch An Approach Based On Integration of Heterogenic Workflows by Mediators Mayyad Jaber 1, Youakim Badr 1, Frederique Biennier 1 1 INSA-Lyon, National Institute of
More informationTeaching Business Processes Effectively using Business Process Management System
Teaching Business Processes Effectively using Business Process Management System 1 Putu Wuri Handayani, 2 Stéphane Bressan, 3 Omar Boucelma 1 Faculty of Computer Science, University of Indonesia 2 School
More informationEnterprise Application Integration using MQSeries and Web services
Enterprise Integration using MQSeries and Web services Evan Mamas emamas@ca.ibm.com IBM Toronto Lab Definitions A Forrester report defines EAI as the integration of multiple, independently developed, managed
More informationSBVR based Business Contract and Business Rule IDE
RuleML-2010 Challenge, at the 4th International Web Rule Symposium M. Palmirani, O. Safiq, E. Francesconi, F. Vitali (eds) CEUR Workshop Proceedings 649 SBVR based Business Contract and Business Rule IDE
More informationTHE BPMN GRAPHIC HANDBOOK
THE BPMN GRAPHIC HANDBOOK Copyright 2015 by Esteban Herrera All rights reserved. No part of this book may be reproduced in any form by any electronic or mechanical means including photocopying, recording,
More informationFrom e3-value to REA: Modeling multi-party ebusiness Collaborations
From e3-value to REA: Modeling multi-party ebusiness Collaborations Rainer Schuster, Thomas Motal Institute of Software Technology and Interactive Systems Vienna University of Technology Vienna, Austria
More informationMethods for the specification and verification of business processes MPB (6 cfu, 295AA)
Methods for the specification and verification of business processes MPB (6 cfu, 295AA) Roberto Bruni http://www.di.unipi.it/~bruni 04 - Models and Abstraction 1 Object Overview of the conceptual models
More informationThe Development Process of the UN/CEFACT Modeling Methodology
The Development Process of the UN/CEFACT Modeling Methodology Christian Huemer Business Informatics Group TU Vienna huemer@big.tuwien.ac.at Rainer Schuster Electronic Commerce Group TU Vienna schuster@ec.tuwien.ac.at
More informationMethods for the specification and verification of business processes MPB (6 cfu, 295AA)
Methods for the specification and verification of business processes MPB (6 cfu, 295AA) Roberto Bruni http://www.di.unipi.it/~bruni 04 - Methodology 1 Objective Coarse-grained methodology for developing
More informationTemporal Verification of Business Processes Using BPMN
Information Engineering Express International Institute of Applied Informatics 2017, Vol.3, No.4, P.105-113 Temporal Verification of Business Processes Using BPMN and CPN Ryoya Shiraki Yoshiyuki Shinkawa
More informationAgent-Based Electronic MarketPlace System Design Document
A Project Report for SENG 609.22 Agent Based Software Engineering Course Instructor: Dr. Behrouz H. Far Agent-Based Electronic MarketPlace System Design Document Page 0 Table of Contents Table of Contents...1
More informationAnalyzing IT Supported Production Control by Relating Petri Nets and UML Static Structure Diagrams
Analyzing IT Supported Production Control by Relating Petri Nets and UML Static Structure Diagrams Henk Jan Pels Technische Universiteit Eindhoven h.j.pels@tue.nl Abstract. A method to model the interaction
More informationShort introduction to business process modelling
Prof. Dr.(PL) Michael Unterstein Short introduction to business process modelling 1. Business process vs. traditional functional business organisation 2. What is a business process? 3. Elements of business
More informationType-based Validation and Management of Business Service Interoperability
Type-based Validation and Management of Business Service Interoperability Toni Ruokolainen Dept. of Computer Science P.O. Box 68 (Gustaf Hällströmin katu 2b) FI-00014 UNIVERSITY OF HELSINKI, FINLAND Toni.Ruokolainen@cs.Helsinki.FI
More informationInformation Systems Architecture and Enterprise Modeling. Prof. Dr. Knut Hinkelmann
Information Systems Architecture and Enterprise Modeling Chapter 1: Introduction to Enterprise Architecture Motivation: Business IT Alignment Challenge: Agility Approach Enterprise Architecture Transparency
More informationMethods for the specification and verification of business processes MPB (6 cfu, 295AA)
Methods for the specification and verification of business processes MPB (6 cfu, 295AA) Roberto Bruni http://www.di.unipi.it/~bruni 20 - Event-driven process chains 1 Object Finish image f finish failed
More informationModel-Driven Architecture, Processes and Methodology from the Perspective of the Modeling Discipline
Processes and Methodology from the Perspective of the Modeling Discipline MDA Implementers Workshop: Succeeding with Model Driven Systems May 12 th 2003 Orlando, Florida Background for Mathet Consulting,
More informationBusiness Process Service Oriented Methodology (BPSOM) with Service Generation in SoaML
Business Process Service Oriented Methodology (BPSOM) with Service Generation in SoaML Andrea Delgado 1, Francisco Ruiz 2, Ignacio García-Rodríguez de Guzmán 2, and Mario Piattini 2 1 Computer Science
More informationDefinition and Execution of Multiple Viewpoints in Workflow Processes
Definition and Execution of Multiple Viewpoints in Workflow Processes Dario Correal University of Los Andes / LICEF TELUQ UQAM Department of Systems and Computer Engineering Cra 1E No 18A 10 Bogota D.C.,
More informationRigorous Business Process Modeling with OCL
Rigorous Business Process Modeling with OCL Tsukasa Takemura 12 and Tetsuo Tamai 2 1 Software Development Laboratory, IBM Japan, Ltd., Yamato-shi, Kanagawa-ken, Japan, tsukasa@jp.ibm.com 2 Graduate School
More informationCollaborative e-business Process Modelling: Transforming Private EPC to Public BPMN Business Process Models
Collaborative e-business Process Modelling: Transforming Private EPC to Public BPMN Business Process Models Volker Hoyer, Eva Bucherer, and Florian Schnabel SAP Research CEC St. Gallen, Switzerland Institute
More informationModeling Multi-party Web-based Business. Collaborations
Modeling Multi-party Web-based Business Collaborations Lai Xu and Sjaak Brinkkemper Institute of Information and Computing Sciences, Utrecht University, 3584CH Utrecht, The Netherlands email: {L.Xu,S.Brinkkemper}@cs.uu.nl
More information<Insert Picture Here> Oracle Business Process Analysis Suite: Overview & Product Strategy
Oracle Business Process Analysis Suite: Overview & Product Strategy Devesh Sharma Dec, 2006 Oracle BPA/BPM Product Management Agenda 1 2 3 4 5 Need for Business Process Management
More informationMDA Overview Applied MDA
IBM Software Group MDA Overview Applied MDA Jim Amsden Senior Software Engineer IBM Rational Software jamsden@us.ibm,com Tutorial: MDA, UML, and applicability to SOA (C) IBM Corporation March 2006 Agenda!
More informationOrder only PROFILE DESCRIPTION
CEN/ISSS WS/BII03 Order only PROFILE DESCRIPTION Business Domain: Post award procurement Business Process: Ordering Document Identification: CEN/ISSS WS/Profile BII03 Version: 1.0 Release: 2009-11-05 Date
More informationA method for B2B process design and implementation. Heikki Rauhala Jouni Lähteenmäki
A method for B2B process design and implementation Heikki Rauhala Jouni Lähteenmäki Overview Business Theories BPM with Workflow Tradition Business Background Business Strategy: Growth Multi-channel Services
More informationTDT Model-driven Development of Information Systems, Autumn Service-oriented architecture (SOA)
TDT4250 - Model-driven Development of Information Systems, Autumn 2008 Service-oriented architecture (SOA) 1 SOA definition Service-oriented architecture (SOA) A set of components which can be invoked,
More informationExtending UML Activity Diagrams for Workflow Modelling with Clinical Documents in Regional Health Information Systems
1160 Extending UML Activity Diagrams for Workflow Modelling with Clinical Documents in Regional Health Information Systems Stergiani Spyrou, Panagiotis Bamidis, Kostas Pappas, Nikos Maglaveras Lab of Medical
More informationA Framework to Support the Assignment of the Active Structure and Behavior in Business Process Modeling
A Framework to Support the Assignment of the Active Structure and Behavior in Business Process Modeling Rômulo H. Arpini and João Paulo A. Almeida Ontology and Conceptual Modeling Research Group (NEMO),
More informationOMG SoaML Service Oriented Architecture Modeling Language - UML Profile and Metamodel for Services
OMG SoaML Service Oriented Architecture Modeling Language - UML Profile and Metamodel for Services NASA/JPL Web conference, November 4th, 2008 Dr. Arne J. Berre, SINTEF, Jim Amsden, IBM, Cory Casanave,
More informationDeriving executable BPEL from UMM Business Transactions
Deriving executable BPEL from UMM Business Transactions Birgit Hofreiter 1, Christian Huemer 2, Philipp Liegl 3, Rainer Schuster 3 and Marco Zapletal 2 1 University of Technology Sydney, Australia 2 Institute
More informationDeliverable Number: D.A2.1
Programme Integrating and Strengthening the European Research Strategic Objective Networked businesses and governments Integrated Project / Programme Title Advanced Technologies for Interoperability of
More informationRAL Solver: a Tool to Facilitate Resource Management in Business Process Models
RAL Solver: a Tool to Facilitate Resource Management in Business Process Models Cristina Cabanillas, Adela del-río-ortega, Manuel Resinas, and Antonio Ruiz-Cortés Universidad de Sevilla, Spain {cristinacabanillas,
More informationFrameworx 13.0 Product Conformance Certification Report
Frameworx 13.0 Product Conformance Certification Report Aggaros STICK&PLAY Version 3 Satuna March 2014 Version 1.0 Table of Contents List of Figures... 4 List of Tables... 5 1 Introduction... 6 1.1 Executive
More informationChapter 1 Introduction
Chapter 1 Introduction Wil van der Aalst, Michael Adams, Arthur ter Hofstede, and Nick Russell 1.1 Overview The area of Business Process Management (BPM) has received considerable attention in recent years
More informationModel based Approaches for Service Oriented Architectures. Mel Greer
Model based Approaches for Service Oriented Architectures Mel Greer Bob Epps Report Documentation Page Form Approved OMB No. 0704-0188 Public reporting burden for the collection of information is estimated
More informationSOA in the Enterprise: A Survey of the Technical Landscape Introduction
SOA in the Enterprise: A Survey of the Technical Landscape by Cyrille Thilloy Published: August 28, 2006 (SOA Magazine Issue I: September/October 2006, Copyright 2006) Download this article as a PDF document.
More informationBusiness Process Modeling
Software Services for WebSphere Updated June 15, 2005 Agenda Software Services for WebSphere Business Process Management (BPM) Understand the BPM Lifecycle Overview Why is important? What is a Business
More informationBusiness Process Service Oriented Methodology (BPSOM) with Service generation in SoaML
Business Process Service Oriented Methodology (BPSOM) with Service generation in SoaML Andrea Delgado 1, Francisco Ruiz 2, Ignacio García-Rodríguez de Guzmán 2, Mario Piattini 2 1 Computer Science Institute,
More informationA Framework for Integrating Business Processes and Business Requirements
A Framework for Integrating Business Processes and Business Requirements Raman Kazhamiakin, Marco Pistore, Marco Roveri {raman,pistore}@dit.unitn.it roveri@itc.it DIT, University of Trento, Italy ITC-irst,
More informationIBM Business Process Manager Telecom Pack version 7.5. Order Handling How To Guide
IBM Business Process Manager Telecom Pack version 7.5 Order Handling How To Guide Note Before using this information and the product it supports, read the information in Notices at the end of this book.
More informationIntelligent Decision Support through Synchronized Decomposition of Process and Objectives Structures
Intelligent Decision Support through Synchronized Decomposition of Process and Objectives Structures Dina Neiger, Leonid Churilov School of Business Systems, Monash University {dina.neiger, leonid.churilov}@infotech.monash.edu.au
More informationBPMI.org Phase 2.0. Insight, Innovation, Interoperability. BPMI.org Board of Directors June 9, Copyright 2004 BPMI.org
BPMI.org Phase 2 Insight, Innovation, Interoperability BPMI.org Board of Directors Why BPM? Source: Driver for BPM: 11 Money-Relevant Reasons to Start Jim Sinur, Gartner Headlines from Philip Lee, BPMI.org
More informationEnterprise Process Integration
Enterprise Process Integration Janne J. Korhonen What is a process? A process is a coherent set of activities carried out by a collaborating set of roles to achieve a goal. Ould: Business Process Management:
More informationModeling dynamic interactions in supply chains using agentbased
Modeling dynamic interactions in supply chains using agentbased simulations Mariana Dorigatti, Omar Chiotti, Héctor E. Salomone INGAR-CONICET, Avellaneda 3657, S3002GJC Santa Fe, Argentina {marianadorigatti,chiotti,salomone}@santafe-conicet.gov.ar
More informationModeling Suspension and Continuation of a Process
Modeling Suspension and Continuation of a Process Oleg Svatos Department of Information Technologies, University of Economics, Prague, Czech Republic svatoso@vse.cz Abstract: This work focuses on difficulties
More informationExperimental Platform for Model-Integrated Clinical Information Systems
Experimental Platform for Model-Integrated Clinical Information Systems Janos Mathe, Jan Werner, Yonghwan Lee, Akos Ledeczi, Bradley Malin #, Janos Sztipanovits Department of Electrical Engineering and
More informationSupporting Healthcare Processes with YAWL4Healthcare
Supporting Healthcare Processes with YAWL4Healthcare Ronny S. Mans 1,3, Nick C. Russell 2, Wil M.P. van der Aalst 1, Arnold J. Moleman 3, Piet J.M. Bakker 3 1 Department of Information Systems, Eindhoven
More informationAutomated Adaptation of Business Process Models Through Model Transformations Specifying Business Rules
Automated Adaptation of Business Process Models Through Model Transformations Specifying Business Rules Roman Popp and Hermann Kaindl Vienna University of Technology, Vienna, Austria {roman.popp, hermann.kaindl}@tuwien.ac.at
More informationSOA Concepts. Service Oriented Architecture Johns-Hopkins University
SOA Concepts Service Oriented Architecture Johns-Hopkins University 1 Lecture 2 Goals To learn the basic concepts behind SOA The roots of SOA: the history from XML to SOA, and the continuing evolution
More informationThe ArchiMate modelling structures
The ArchiMate modelling structures Monica Scannapieco ESTP Training Course Enterprise Architecture and the different EA layers, application to the ESS context Advanced course Rome, 11 14 October 2016 THE
More informationData intensive flows. November 2013 Alberto Abelló & Oscar Romero 1
Data intensive flows November 2013 Alberto Abelló & Oscar Romero 1 Knowledge objectives 1. Recognize the importance of usability and taking a user-centered approach 2. Remember BPMN elements regarding
More informationLecture 3 Process Modeling I
MTAT.03.231 Business Process Management Lecture 3 Process Modeling I Marlon Dumas marlon.dumas ät ut. ee 1 Business Process Lifecycle 1. Introduction 2. Process Identification 3. Essential Process Modeling
More information1. Introduction. URDAD for System Design. Table of Contents. Dr. Fritz Solms. Abstract. Use-Case Responsibility Driven Analysis and Design
Solms Training, Consulting and Development Physical: 113 Barry Hertzog Ave, Emmarentia, Johannesburg, South Africa Postal: PostNet Suite no 237, Private Bax X9, Melville 2109, South Africa Phone: +27 (11)
More informationWSDL 2.0 Message Exchange Patterns: Limitations and Opportunities
WSDL 2.0 Message Exchange Patterns: Limitations and Opportunities Jörg Nitzsche, Tammo van Lessen, and Frank Leymann Institute of Architecture of Application Systems, University of Stuttgart Universitätsstraße
More information