05/23/2009 06:15:07 AM EST
Neither BPMN or BPEL fully describe all the necessary entities for process management and what they describe is way to rigid. Those who believe that BPMN can be executable must be blind or ignorant. All the key definitions of what makes the process alive are missing. The 'data and content artefacts' are what makes a process a process, not just an add-on. The rules are hidden inside some silly 'gateway' and there is no definition whether an activity is executing some method, something that a user does or wheter it is a state change in an entity. There are no definitions of goals, rules, content and user presentation. It is simply unusable. Therefore BPMN 2.0 is still incredibly ambiguous and it is left to the (jBPEL) programmer to make it work. When he leaves, you have the same maintenance issue as with any othe program. How will that increase the mouch vounted agilty? Get real, please!
United StatesMax Pucher
Subscribe today and you'll receive 24 free issues of SD Times!
Dear Software Professional,
I’d like to invite you to subscribe to SD Times, the newspaper of the software development industry. The newspaper is free, and it will only take a moment to subscribe!
SD Times covers the fast-paced world of software and application development. The twice-monthly newspaper helps software architects, project leaders, analysts and development managers make the proper decisions about products, methodologies and practices that can affect their development teams and efforts.
Each year, we offer only a limited number of complimentary subscriptions to software development professionals!
It only takes moment to sign up. Don't delay, subscribe today!
Sincerely,
David Lyman Publisher SD Times