JBoss.com - The State of Workflow by Tom Baeyens - The Diigo Meta page

• 02 Jan 10
  

  Kurt Laitner

  Business Process Management Workflow case Tom Baeyens Vendor Listing

• 18 Jul 08
  

  mcasoni76

  article bpel bpm workflow jbpm jboss workflowengine

• 08 May 08
  

  Pasquale Basile

  bpm xpdl

• 10 Apr 08
  

  leo foto

  jbpm workflow

• 13 Mar 08
  

  Rohit Srivastava

  bpm

• 22 Jan 08
  

  bpm business development reference programming workflow

• 23 Oct 07
  

  simonckenyon

  jboss jbpm

• 26 May 07
  

  Mehran Taherimoud

  JBPM Workflow Summary java opensource jboss delicious

• 10 May 07
  

  Ricardo Borillo

  workflow

• 25 Apr 07
  

  I would like to point out that workflow management systems are at the very initial phase of the technology hype curve

  workflow jboss hype bpm

• 05 Apr 07
  

  Bo Reid

  Workflow

• 20 Feb 07
  

  ellecer

  toread workflow bpm jboss article business

• 15 Dec 06
  

  Henry
  • In UML activity diagrams, no distinction is made between a state and an action (see 'Why the term 'activity' should be banned) They  are both modelled as activities. The lack of this distinction (referred to as the lack of a state concept) is the  most heard criticism by the academic community on UML activity diagrams. A second problem with UML activity diagrams  was introduced in UML version 2.0. When multiple transitions arrive in an activity (read state), previous versions specified a default merge interpretation. The 2.0 version changed this to a default join, which requires synchronization.
  • • in the diagram presentation of a business process, only model the state layer (states and control flow) and leave  the actions out of the diagram. This means that every rectangle in the diagram should be a state instead of an   activity 
     
    • if multiple transitions arrive in a state, define the default to be a default merge without synchronization
  • he content of a process definition can be sliced into 4 different layers: state, context, programming logic and user interface.
  • improved support for iterative development.
  • embed a workflow engine inside another application
  • where a WFMS delivers high added value is for the development of workflow software that  has a lot of people-related tasks.
  • use a WFMS as an enterprise application integration (EAI) platform
  • My  proposal is to avoid the term 'activity' and replace it by either 'state' or 'action'.
  • A nother important responsibility of a WFMS is maintaining context information for each process execution >. 

  7 more annotations...

• 02 Oct 06
  

  Francis Cook

  Workflow and an analysis of it's associated technologies.

  bpm workflow programming j2ee jboss java reference SOA

• 29 Aug 06
  

  Ulrich Kampffmeyer

  The State of Workflow; article by Tom Baeyens with a list of commercial and open source workflow/BPM products

  @DrUKff #PC_HH ECM Beratung DMS PROJECT CONSULT Ulrich Kampffmeyer delicious BPM Business_Process_Management Workflow Markt ITC-Market [EN] DrUKff

• 

  PROJECT CONSULT

  The State of Workflow; article by Tom Baeyens with a list of commercial and open source workflow/BPM products

  imported BPM Business_Process_Management Workflow Markt ITC-Market [EN]

• 02 Aug 06
  

  Serge Slipchenko

  java workflow engine

• 01 Aug 06
  

  Prasad

  bpm

• 17 Jul 06
  

  swwsman

  workflow bpm

• 26 Oct 05
  

  Leandro Rodrigo Saad Cruz

  workflow

Would you like to comment?

Join Diigo for a free account, or sign in if you are already a member.