WIDE workflow development methodology

ABSTRACT

The development of workflows (WFs) for complex organizations to be interfaced with existing information systems requires a specific methodological approach to guarantee benefits and effectiveness of the final results. In fact, the WF should be well integrated in the organization both from the technical and the organizational point of view. While the characteristics of the Workflow Management System (WFMS) platform adopted in the implementation are relevant to establish the boundary between the workflow system and other related applications, it is also important that the analysis and design phases are developed independently of those characteristics.The WF development methodology proposed in this paper starts with an analysis phase based on UML, adopted for business process descriptions and business goals. The design phase proposes a pattern-based approach to workflow schemas design, based on the WIDE WF model. This model allows a flexible representation of the exceptions which may occur during WF execution. It also considers the interaction of the WF with external applications and information systems. Finally, the paper briefly discusses the mapping to commercial and prototype WFMSs.

REFERENCES

• 1: Jim Arlow , Wolfgang Emmerich , John Quinn, Literate Modelling - Capturing Business Knowledge with the UML, Selected papers from the First International Workshop on The Unified Modeling Language «UML»'98: Beyond the Notation, p.189-199, June 03-04, 1998
• 2: Annie I. Antón , W. Michael McCracken , Colin Potts, Goal decomposition and scenario analysis in business process reengineering, Proceedings of the 6th international conference on Advanced information systems engineering, p.94-104, June 1994, Utrecht, The Netherlands
• 3: Victor R. Basili , Lionel C. Briand , Walcélio L. Melo, How reuse influences productivity in object-oriented systems, Communications of the ACM, v.39 n.10, p.104-116, Oct. 1996 [doi>10.1145/236156.236184]
• 4: Y. Bernard, A. Canals. Use of Cisi UML development process on GEDYS Project. UML 98, Toulouse, France. 1998.
• 5: Cosa Reference Manual, Software-Ley GmbH, September 1996.
• 6: R. Flores. The Value of a Methodology for Workflow, Action Technologies, Inc, 1997 Available from http://www.actiontech.com/market/marketingdocs/meth od5.html.
• 7: Paul Grefen , Barbara Pernici , Gabriel Sanchez, Database Support for Workflow Management: The Wide Project, Kluwer Academic Publishers, Norwell, MA, 1999
• 8: Object-oriented strategies, the monthly newsletter for managers and developers of object-oriented systems. Vol. VII, No. 12. P. Harmon Ed. Dec. 1997.
• 9: Hewlett Packard. Changengine Admin. Edition (AdminFlow) Process Design Guide. Edition 1 .O. 1998.
• 10: IBM FlowMark - Modeling Workflows, IBM Corporation, 1996.
• 11: H. Stark, L. Lachal. Ovum Evaluates: Workflow, Ovum Ltd., 1995.
• 12: A. G. Sutcliffe , N. A. M. Maiden, Bridging the requirements gap: policies, goals and domains, Proceedings of the 7th international workshop on Software specification and design, December 06-07, 1993, Redondo Beach, California
• 13: Unified Modeling Language summary, version 1.1, September 1997. Rational Software Corporation.
• 14: UML Extension for Business Modeling, vers. 1.1, Sept. 1997, www.rational.cornluml.
• 15: 0. Wiegert. Business process modeling and workflow definition with UML. Working paper. SAP AG 1998.
• 16: D. Hollingsworth, Workflow management Coalition, the 1994 Workflow Reference Model, Technical Report n. TCOO-1003, November 1994.

INDEX TERMS

Primary Classification:
  H. Information Systems
  H.2 DATABASE MANAGEMENT

Additional Classification:
  D. Software
  D.3 PROGRAMMING LANGUAGES
      D.3.2 Language Classifications

          Nouns: UML

  H. Information Systems
  H.2 DATABASE MANAGEMENT
      H.2.1 Logical Design
          Subjects: Schema and subschema

  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.1 Project and People Management
          Subjects: Systems development

General Terms:
Design, Languages, Management, Performance, Theory

Keywords:
exceptions, patterns, triggers, workflow design