Articles and Links
Articles (Written / Cowritten)
Keith D Swenson - The Key to SOA Governance: Understanding the Essence of Business, Cutter IT Journal, Vol. 20, No. 6, June 2007
Keith D Swenson, The Business Value of Workflow and BPM, Workflow Handbook, 2007
Keith D Swenson - Streamline Your XML Searches - An index-free approach to managing data - XML Journal - Jun. 2, 2004
Michael zur Muehlen, Jeffrey V. Nickerson, Keith D. Swenson - Developing Web Services Choreography Standards – The Case of REST vs. SOAP - Decision Support Systems 37 (2004), Elsevier, North Holland.
Presentation: Worldwide Interoperability Demonstration of ASAP & Wf-XML 2.0. - Brainstorm BPM Conference June 2004 - the first interoperability demonstration. (Powerpoint slides: “Connecting Systems With ASAP.“) June 23, 2004
Keith D Swenson, Jeffrey Ricker, Asynchronous Web Services Protocol (AWSP), work in progress April 2002 (site, pdf)
Keith D Swenson, Workflow for the Information Worker, Chapter 2 in The Workflow Handbook 2001, Workflow Management Coalition, 2001, (toc, html)
Keith D Swenson, Michael zur Muehlen, XML-based Standards for B2B Process Integration, Tutorial at XML World 2001 San Francisco, Nov 26, 2001, (abstract)
Keith D Swenson, Michael Marin, Business Process Integration Seminar: XML-Based Standards for Process Integration, Special session at e-Businesses Integration San Francisco 2001, (abstract)
James G. Hayes, Effat Peyrovian, Sunil Sarin, Marc-Thomas Schmidt, Keith D. Swenson, Rainer Weber, Workflow Interoperability Standards for the Internet, IEEE Internet Computing, May/June 2000 (Vol. 4, No. 3), pp. 37-45 (abstract)
Keith D Swenson, Internet Scale Workflow: Standards for Cross-Enterprise Business Processes, A tutorial session at Work Activities Coordination and Collaboration Conference (WACC’99), San Francisco, Feb 22, 1999 (abstract)
Keith D Swenson, Simple Workflow Access Protocol (SWAP), Workshop on Internet Scale Event Notification, Irvine California, July 1998, (notes)
Keith D Swenson, Workflow Management Standards and Interoperability, Chapter 2 of New Tools for New Times: The Workflow Paradigm, Second Edition, ISBN 0-9640233-2-6, Future Strategies Inc, 1995 (toc)
Keith D Swenson, Robin Maxwell, Toshi Matsumoto, Bahram Saghari, Kent Irwin, A Business Process Environment Supporting Collaborative Planning, Collaborative Computing Journal, March 1994, page 15
Jun. 2, 2004 - “Streamline Your XML Searches - An index-free approach to managing data” - XML Journal - A review of the Shunsaku XML search product.
Jun 2004 - “Developing Web Services Choreography Standards – The Case of REST vs. SOAP” - Michael zur Muehlen, Jeffrey V. Nickerson, Keith D. Swenson, Decision Support Systems 37 (2004), Elsevier, North Holland. (also here)
Presentations
Oct 2007, Paris France, Paris La Défense • WfMC Tutorial, a full day tutorial with 4 other presenters.
Oct 2007, Poznan, Poland, WfMC Forum Poland 2007, BPM In Practice, a full day tutorial with 4 other presenters.
May 2007, Washington DC, BPM in Practice: Understanding and Implementing Workflow and Business Process Management, a full day tutorial with 5 other presenters.
Feb 2007, Santa Clara California, BPM in Practice: Understanding and Implementing Workflow and Business Process Management, a full day tutorial with 4 other presenters.
Nov 2006, Taipei Taiwan, Following BPM Giant’s Steps WfMC Standards Tutorial Day, a full day tutorial with 4 other presenters.
Nov 2006, Singapore, WfMC Standards Tutorial Day, a full day tutorial with 4 other presenters.
Oct 2006, Tokyo Japan, WfMC Standards Tutorial Day Japan BPM Association 3rd BPM Forum, a full day tutorial with 4 other presenters.
Sept 2006, Mainz Germany, WfMC Standards Tutorial Day, Part of BPM2006 CONFERENCE, a full day tutorial with 4 other presenters.
June 23, 2004 - Worldwide Interoperability Demonstration of ASAP & Wf-XML 2.0.) - Brainstorm BPM Conference June 2004 - the first interoperability demonstration. (Powerpoint slides: “Connecting Systems With ASAP.“)
Feb 22, 1998 - “Internet Scale Workflow: Standards for Cross-Enterprise Business Processes” - Work Activities Coordination and Collaboration (WACC’99) Conference - A tutorial on the OMG workflow RFP, and the IETF SWAP protocol, and other early SWAP things.
April 3, 1998 - “Web Based Distributed Workflow” - Bay Area Roundtable (BART) Scaling for the Internet series - Actually this is an early proposal for the concept of a “web service”.
Feb 1998 - Keynote Speech at JavaAUS’98. Sydney Australia.
Related Articles (Quoted)
July 17, 2006 - “SOA solution offers free management options” - Jason Turcotte, Application Development Trends.
April 21, 2006 - “Fujitsu aims for higher North American profile, profits” - Network World - A quote about Fujitsu’s vision of SOA.
June 2005 - “Data Centers Move Front and Center into the Middleware Revolution” - Joe McKendrick, Database Trends and Applications. A quote about how SOA is transforming data centers.
Oct 1, 2004 - “XML lets loose the data stream” - Application Development Trends - A short quote near the end about XML search capabilities.
June 23, 2004 - “Workflow Management Coalition Hosts ASAP and Wf-XML 2.0 Interoperability Demo” - OASIS Cover Pages - a compendium of several articles about that time on the subject of the interoperability test.
June 23, 2004 - “New ASAP standard takes programming out of the picture” - Mark Brunelli, Search Web Services
June 22, 2004 “New Web services standards connect competing systems ASAP” - Search Web Services
June 21, 2004 - “Fujitsu, WfMC To Demo Business Process Interoperability” - GRID Today, Vol. 3 No. 25
June 14, 2004 - “ASAP spec proposed for delayed Web services” - ComputerWeekly.com - A short discription of the Asynchronous Service Access Protocol (ASAP).
March 9, 2004 - “Fujitsu Chief Architect Recognized for Outstanding Contribution to the Field of Workflow” - Press Release from Fujitsu
Oct 22, 2003 - “Oasis builds asynchronous web services spec” - ComputerWeekly.com - A short discription of the Asynchronous Service Access Protocol (ASAP).
Nov 10, 2003 - “OASIS Advances Protocol for Asynchronous Web Services” - ebizQ
Bio Links
2004 @ XML Journal
How to model any business process in BPM (Various means i mean BPEL , BPMN)
b) How to take the BPM model and do the development?
c) For development, what will be structure? What are the types of UI, Batch jobs, Database connections, file readings, integrations to existing systems etc.
d) What is the deployment model of this solution. E.g If some process is developed using ALBPM, how can I deploy that application. What will i have to do?
What happens if i have to change the process and then redeploy. How easy/difficult is it? What is FBL, scripting language. Where do i use a java implementation and how from fuego. E.g i have a expense validation subprocess and i have the code in java (either EJB / Web service), how can i call from Fuego. Do i have to do scripting etc?
e) What do we mean when we say long running transactions? How does ALBPM stores informations for such a long time. What happens if i shut down the BPM Server and start it back? Does LRT still remains or it closes? What does process instance handle this information.
Hi,
Saw this question from loooong ago. I have some recent posts that might answer them. See A Methodology for Human Process Development which should cover the standards and questions (a), (b), and (c).
For (d) it will be proprietary for most engines, but there is a protocol Wf-XMl which would handle this.
Change and redeploy is very important. Interstage BPM allows multiple versions of the process to be running at the same time. It has a “migrate” capability that will allow running processes to changed to a new version of the process while they are running.
For (e) LRT is an interesting and much misunderstood subject. Implementation is very much vendor dependent. I can say that the Interstage BPM system is very clean in this regard: you can shut off a server at any time, and any transaction you received a completion notice for will be preserved without harm. Transactions that are not completed will of course be rolled back, and you will receive an error message at that time telling you it failed.