A unified framework for modeling cooperative design processes and cooperative business processes

Looks at any cooperative design process as a decision-making process, i.e. as a non-deterministic process. The process is performed by responsible agents having the freedom to decide how to proceed according to their assessment of the situation they are faced to. However, the cooperative design process cannot be an ad-hoc and chaotic process. We look at it as a repeatable process made of steps resulting each of the application of the same pattern for decision making. The pattern views a decision as a choice of the way to proceed in a given situation to achieve an intention. An intention can be fulfilled in different ways depending on the situation being considered. We propose a process meta-model for describing such a pattern of decision making. This meta-model can also be used for modeling cooperative business processes, whether well-structured or ill-structured. In order to deal with a wide range of cooperative processes, we propose a single-process meta-model which provides the structuredness of predefined models and the flexibility of ill-structured processes.

[1]  Judy L. Wynekoop,et al.  System Development Methodologies: Unanswered Questions and the Research-Practice Gap , 1993, ICIS.

[2]  Matthias Jarke,et al.  DAIDA: an environment for evolving information systems , 1992, TOIS.

[3]  Henderson-SellersBrian,et al.  The object-oriented systems life cycle , 1990 .

[4]  Göran Goldkuhl,et al.  Generic business frameworks and action modeling , 1996 .

[5]  Colin Potts A generic model for representing design methods , 1989, ICSE '89.

[6]  Colette Rolland,et al.  ALECSI: An Expert System for Requirements Engineering , 1991, CAiSE.

[7]  Martin Fowler,et al.  Analysis patterns - reusable object models , 1996, Addison-Wesley series in object-oriented software engineering.

[8]  Kevin Crowston,et al.  Toward a handbook of organizational processes , 2000 .

[9]  W BoehmBarry A Spiral Model of Software Development and Enhancement , 1988 .

[10]  WinogradTerry A language/action perspective on the design of cooperative work , 1987 .

[11]  H E Solberg,et al.  Object-oriented methods. , 1993, Clinica chimica acta; international journal of clinical chemistry.

[12]  Annie I. Antón,et al.  Goal-based requirements analysis , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[13]  James Martin,et al.  Object-oriented methods : a foundation , 1995 .

[14]  Colette Rolland,et al.  Understanding and guiding requirements engineering processes , 1996, IFIP World Conference on IT Tools.

[15]  Reidar Conradi,et al.  Software process modeling and evolution in EPOS , 1992, Proceedings Fourth International Conference on Software Engineering and Knowledge Engineering.

[16]  Colette Rolland,et al.  An Approach for Defining Ways-of-Working , 1995, Inf. Syst..

[17]  Terry Winograd A Language/Action Perspective on the Design of Cooperative Work , 1987, Hum. Comput. Interact..

[18]  W. W. Royce,et al.  Managing the development of large software systems , 1970 .

[19]  Michael L. Begeman,et al.  gIBIS: a hypertext tool for exploratory policy discussion , 1988, CSCW '88.

[20]  Terry Winograd,et al.  The action workflow approach to workflow management technology , 1992, CSCW '92.

[21]  Mark Dowson,et al.  Towards Requirements for Enactment Mechanisms , 1994, EWSPT.

[22]  Colette Rolland,et al.  Guiding the Participative Design Process , 1997 .

[23]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[24]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[25]  Jon Atle Gulla,et al.  Modeling Cooperative Work for Workflow Management , 1994, CAiSE.