Practical experiences and requirements on workflow

  • Kwang-Noon Kim
  • Su-Ki Paik
Workflow and Coordination
Part of the Lecture Notes in Computer Science book series (LNCS, volume 1364)


The purposes of this paper are to describe practical experiences on a business process(Hiring Process) automation by a workflow automation approach, and to point out the limitations of current business process automation from the workflow application developer's point of view. The limitations may be caused from the lack of human coordination, collaboration, group-decision, interoperability, scalability, correctness/reliability of workflow applications, exception handling, and a dynamic reflex of the organizational changes in current workflow modeling methodologies and workflow management systems.

By pointing out the insufficiencies through the practical experiences, we derive some requirements for workflow modeling methodologies and workflow management systems. We believe that those requirements are key infrastructures and research issues to successfully implement business process automation.

Finally, workflow application developers should carefully consider the business process modeling methodology as well as the workflow management system when they automate their corporate processes to avoid 1119 1686 V 3 mismatches.


Business Process Business Process Modeling Process Instance Hiring Process Computer Science Technical Report 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Kenneth R. Abbott and Sunil K. Sarin, “Experience with Workflow Management: Issues for the next Generation”, Proceedings of ACM 1994 Conference on CSCW, pp.113 120, Oct. 1994Google Scholar
  2. 2.
    Doug Barrholomev, “Workflow Software: A Better Way to Work”, Cover Story of Information Week, Sept. 1995Google Scholar
  3. 3.
    Nina Burns, “Ebb and Flow”, LAN Magazine, May. 1993Google Scholar
  4. 4.
    Bull L.P.M., “FlowWorks: The BULL Workflow Product — Architectural Design and Functional Specification”, Revision C, 1992Google Scholar
  5. 5.
    Diimitrios Georgakopoulos, Mark Hornick, “An Overview of Workflow Management: From Process Modeling to Workflow Automation Infrastructure”, Distributed and Parallel Databases, 3, pp. 115–153, 1995CrossRefGoogle Scholar
  6. 6.
    Clarence A. Ellis, J. Gibbs, and G.L. Rein, “Groupware: Some issues and Experiences”, Communication of the ACM, Vol. 34, No. 1, Jan. 1991Google Scholar
  7. 7.
    Clarance A. Ellis, “Workflow Technology”, Tutorial Notes, 1995Google Scholar
  8. 8.
    Clarence A. Ellis, “Formal and Informal Models of Office Activity”, Information Processing 83, IFIP, Paris, 1983Google Scholar
  9. 9.
    Clarence A. Ellis, Robert Gibbons and Peter Morris, “Office Streamlining”, In N. Naffah (ed.) Integrated Office Systems — Burotics, North Holland, Amsterdam, 1980Google Scholar
  10. 10.
    Clarence A. Ellis, Carlos Maltzahn, “The Chautauqua Workflow System, 30th Hawaii International Conference on System Sciences, Information System Track, Wailea, Maui, Hawaii, January 7–10, 1997Google Scholar
  11. 11.
    Clarence A. Ellis and Gary J. Nutt, “Workflow: The Process Spectrum”, Proceedings of NSF Workshop on Workflow and Process Automation in Information Systems: State-of-the-Art and Future Directions, May 1996Google Scholar
  12. 12.
    Clarence A. Ellis, Gary J. Nutt, “The Modeling and Analysis of Coordination Systems”, University of Colorado/Dept. of Computer Science Technical Report, CU-CS-639-93, Jan. 1993Google Scholar
  13. 13.
    “Managing Your Workflow”, IBM FlowMark, Version 2 Release 2, 1996Google Scholar
  14. 14.
    “Modeling Workflow”, IBM FlowMark, Version 2.1, 1996Google Scholar
  15. 15.
    “Programming Guide”, IBM FlowMark, Version 2.1, 1995Google Scholar
  16. 16.
    “The Business Imperative for Workflow & Business Process Reengineering”, A Special Advertising Section, Fortune, Feb. 1996Google Scholar
  17. 17.
    Jonathan Grudin, “Groupware and Social Dynamics: Eight Challenges for Developers”, Communications of the ACM, Vol. 37, No. 1, January 1994Google Scholar
  18. 18.
    Stefan Jablonski, “On the Complementarity of Workflow Management and Business Process Modeling”, SIGOIS Bulletin, Vol. 16, No. 1, Aug. 1995Google Scholar
  19. 19.
    Stefan Jablonski, “MOBILE: A Modular Workflow Model and Architecture”, Informatik: Database Support for Open Workflow Management Systems, Band 29, No. 5, May 1996Google Scholar
  20. 20.
    Dimitris Karagiannis, “Special Issue on Business Process Reengineering”, ACM SIGOIS Bulletin, Vol. 16, No. 1, Aug.Google Scholar
  21. 21.
    Kwang-Hoon Kim, “Groupware”, University of Colorado at Boulder, Computer Science Master's Thesis, 1994Google Scholar
  22. 22.
    “IBM LOVEM/Business Process Modeler (ProModeler)”, Tutorial Notes for The Basic Course, 1996Google Scholar
  23. 23.
    Ronni T. Marshak, “IBM's Business Modeling Tool: BPR Methodology from the Customer Point of View”, Workgroup Computing Report, Vol. 18, No. 6, Jun. 1995Google Scholar
  24. 24.
    Ronni T. Markshak, “Buyer's Guide: Taking the Mystery Out of Workflow Automation”, Virtual Workgroups Magazine, May/June 1996Google Scholar
  25. 25.
    Gary J. Nutt, “Using Workflow in Contemporary IS Applications”, University of Colorado/Dept. of Computer Science Technical Report, CU-CS-663-93, Aug. 1993Google Scholar
  26. 26.
    Christine Perey, “Stop Communicating and Start Collaborating!”, Virtual WorkGroup Magazine, Sept./Oct. 1996Google Scholar
  27. 27.
    Heikki Saastamoinen, “Exceptions: Three Views and a Taxonomy”, Proceedings of COOLS, 1995Google Scholar
  28. 28.
    Amit Sheth, “Workflow Automation: Applications, Technology and Research”, Tutorial Notes, SIGMOD Conference, May 1995Google Scholar
  29. 29.
    Kelly Trammell, “Work Flow Without Fear”, BYTE, April 1996Google Scholar
  30. 30.
    Venkatraman, “IT-Enabled Business Transformation: From Automation to Business Scope Redefinition”, Sloan Management Review, Winter 1994Google Scholar
  31. 31.
    “VX-Rexx Programmer's Guide”, Watcom International Corp., Version 1, 1996Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1998

Authors and Affiliations

  • Kwang-Noon Kim
    • 1
  • Su-Ki Paik
    • 2
  1. 1.Department of Computer ScienceUniversity of Colorado at BoulderBoulder
  2. 2.Department of Computer ScienceKyonggi UniversitySuwon-Si, Kyonggi-DoSouth Korea

Personalised recommendations