Views

InformationTechnology:Modeling:Business

Contents

Navigation



Related categories

UML · Database · Resources ·

About the Business Process Modeling page

Globalization, outsourcing, synchronous and JIT manufacturing, process reengineering, all are factors increasing complexity of interactions between business processes in curent enterprise environments. Consequently organizations across the world invested into solutions to formalize and eventually automate all the phases of the process, from the analysis to the implementation, through modeling and formalization. We apologize for the little information we provide, this page is still under construction. Please stay tuned.

Image:Construction_worker.gif

Structured Analysis modeling approach

The Structured Analysis was pioneered in the 80's, by ED Yourdon, with a methodology and notation to facilitate the analysis and modeling of business processes and information flows by Business Analysts and other non-technical users.
  • Entity-relationship diagrams [1]
  • Comparison of Diagramming Methods [2]
  • Ed Yourdon's "Structured Analysis" online [3]
  • DFD chapter in Ed Yourdon's "Structured Analysis" [4]
  • Data Flow Diagrams (DFD) [5]
  • Data Flow Diagrams (DFD) explained [6]
  • Data Flow Diagrams Tutorial [7]
  • Introduction to Data Flow Diagrams (DFD) [8]
  • Business drawing tool [9]


Business Modeling & Integration (BMI) Domain Task Force (DTF)

Business Modeling & Integration (BMI) Domain Task Force (DTF) is the result of the merger, in June of 2005, of their Business Process Management (BPM) activities, between the Business Process Management Initiative (BPMI) and the Object Management Group (OMG). The BMI DTF mission is to develop specifications of integrated models to support management of an enterprise, through Business Process Management and Business Process Modeling, based on OMG's Model Driven Architecture (MDA). Following the merger the names of the BPMN/BPML standards might have changed but the principle stay the same. Historically, two methodologies are applied in business modeling:
  • Business use case, a new approach, rooted in UML use-case methodology.
  • Business process-centred architecture, traditional, focused on identifying and desctibing the business processes.


BPML/BPMN/BPMI Resources

  • Business Process Modeling Language (BPML) introduction [10]
  • Introduction to Business Process Modeling Notation (BPMN) [11]
  • Business Process Modeling and Standardization [12]
  • Introduction to BPMN [13]
  • Business Process Modeling Notation [14]
  • Business Process Modeling Language [15]
  • Business Process Modeling and Service Oriented Architecture [16]
  • BPMN resources and Visio stencils [17]


Specifications

The BPML specification provides an abstract model and XML syntax for expressing executable business processes and supporting entities, creating a base for automation of workflows. The Business Process Execution Language (BPEL) is an XML-based, executable business process and workflow modeling language, without a graphical notation. The BMI has recently abandoned BPML in favor of BPEL, already supported by a large number of manufacturers [18]. BPEL is supported by Oracle, SAP, Sun, BEA, IBM, Microsoft and other manufacturers. The BPMN specification provides a graphical, UML-base notation, easily understandable by business analysts, system architects and implementers. One of the intents of the two standards is to allow automatic generation of web-services and associated "orchestration" services to implement the workflows directly from the model.

Comparison points between BPML and BPEL4WS

  • BPML is a superset of BPEL4WS, by supporting, among other features representation of process nesting.
  • Both are based on very similar representations, idioms and syntaxes, both being block-structured languages.
  • Both are based on a logical process model, representing complex business processes with concurrent, repeating, and dynamic tasks.
  • Since 2002 most software vendors dropped support for BPML and supported BPEL. BPML is de-facto dead today with no serious process engines supporting it.


More resources and information on the various Business Process Modeling

  • ebPML, a site dedicated to the standards, technologies and products of Service Oriented Computing, Business Process Management and Model Driven Architectures.
  • And Your Future BPMS Is? Microsoft Office [19]


BPMN/BPEL tools



Workflow Management Coalition (WfMC)

WMC was founded in 1993 as a global organization of industry, university and research groups aiming to develop standards and solutions for workflow and business-process modeling and automation. WfMC is a pre-SOA initiative, and it seems that BPMI was created just because WfMC was not doing much to evolve its standard in the modern world of e-business XPDL is focused on "manual" Workflow processes only and not an executable programming language like BPEL XPDL is specifically a process design format that literally represents the "drawing" of the process definition. By contrast, BPEL is an "execution language" designed to provide a definition of web services orchestration.

References:
  • A comparison of XPDL, BPML and BPEL [20]
  • A comparison of the 5 major business modeling languages [21]
  • XPDL overview [22]


OPEN Process Framework

The ("Object-oriented Process, Environment, and Notation") OPEN Process Framework is a predecessor to the BMI/OMG Business Process Modeling initiative. It is essentially a metamodel based on a large library of Business Process Components, available as a free, public domain, industry-standard approach for the production of development methods OPEN was originally created in the mid-1990s as a merger of several earlier object-oriented software development methods, especially MOSES by Brian Henderson-Sellers, SOMA by Ian Graham, ADM3 by Firesmith, and Synthesis by Meilir Page-Jones. Since then, OPEN has grown and evolved to support the development, sustainment, and retirement of software-intensive systems as well as to support business [re]engineering. The OPEN Process Framework, having been developed before the advent of Service Oriented Architectures, lacks the web-service based process automation capability of BPEL and the support of large enterprise-solutions providers.

RosettaNet

RosettaNet is esentially a technology allowing automation of complex supply-chain B2B transaction. It provides:
  • A business-process modeling methodology for B2B transactions, with a specific notation, dictionary and XML encoding schema
  • RosettaNet Implementation Framework (RNIF), defining B2B transactions, transport and security mechanisms, using schema-compliant, XML-encoded messages, exchanged between cooperation processes according to sequences defined in PIPs..
  • RosettaNet Partner Interface Processes (PIPs), which are XML-based protocols defining B2B business-process interactions, modeled through specific vocabularies and business-process choreography diagram of the message exchanges.


RosettaNet was developped in the pre-SOA era of the 90's by large manufacturers (e.g. Intel, Fujitsu, Sony, Fairchild) with global supply chains, interested in efficient logistics and operations through automation of their supply chains and trading operations. Today RosettaNet is being used to automate the supply chains of more than 400 member-corporations and large software vendors have been supporting and still support RosettaNet with their business integration suites:

Here are some more resources about RosettaNet:
  • RosettaNet technology report [27]
  • Introduction to RosettaNet, courtesy of BEA Systems [28]
  • Tutorial - Building RosettaNet Solutions, courtesy of BEA Systems [29]
  • RosettaNet information from "The European B2B Forum for the Electronics Industry" [30]
  • RosettaNet Software Vendors Interoperability report [31]
  • QPR Software QPR ProcessGuide for RosettaNet, a Business Process Modeling toolset.


Other Business Modeling Resources