Integrating conflicting requirements in process modeling: a survey and research directions

https://doi.org/10.1016/S0950-5849(96)01135-4Get rights and content

Abstract

Requirements in process modeling have traditionally been collected separately for different business functions and then integrated into an overall specification. The recent orientation to a process perspective in managing business activities has emphasized early integration, by concurrently analyzing business processes and requirements. Accordingly, requirements analysis methodologies should take into account these new demands. In the paper, we discuss these new integration needs. Traditional methods for requirements integration from database design are analyzed and unfulfilled integration needs are highlighted. Then, other research fields are surveyed that deal with problems similar to integration and offer interesting results: recent developments in database design, software engineering and requirements reuse. Finally, we compare the different contributions and indicate open research directions.

References (49)

  • S. Easterbrook

    Handling conflicts between domain descriptions with computer-supported negotiation

    Knowledge Acquisition

    (1991)
  • H. Mintzberg

    Structure in fives: designing effective organizations

    (1979)
  • R.L. Nolan

    Managing the computer resource: a stage hypothesis

    Communications of the ACM

    (July 1973)
  • C. Batini et al.

    A comparative analysis of methodologies for database schema integration

    ACM Computing Surveys

    (Dec. 1986)
  • N. Venkatraman

    IT-enabled business transformation: from automation to business scope redefinition

    Sloan Management Review

    (Winter 1994)
  • M. Hammer et al.

    Reengineering the Corporation

    (1993)
  • T.H. Davenport et al.

    Reengineering: business change of mythic proportions?

    MIS Quarterly

    (1994)
  • F. Cattaneo et al.

    An experience in process assessment

  • H.H. Baligh

    Decision rules and transactions, organizations and markets

    Management Science

    (1986)
  • T.W. Malone

    Modeling coordination in organizations and markets

    Management Science

    (Oct. 1987)
  • C. Francalanci et al.

    IT architectures and organizational information processing capacity: A synthesis and illustration

    Harvard Business School Int. Rep. n 96-002

    (July 1995)
  • J.D. Ullman

    Principles of database systems

    (1982)
  • C.J. Date

    Relational database: selected writings

    (1986)
  • C. Batini et al.

    Conceptual database design

    (1991)
  • S. Al-Fedaghi et al.

    Mapping considerations in the design of schemas for the relational model

    IEEE Trans. on Software Engineering

    (Jan. 1981)
  • S.B. Yao et al.

    View modeling and integration using the functional data model

    IEEE Trans. on Software Engineering

    (June 1982)
  • M. Casanova et al.

    Towards a sound view integration methodology

  • C. Batini et al.

    A methodology for data schema integration in the entity-relationship model

    IEEE Trans, on Software Engineering

    (Nov, 1984)
  • U. Dayal et al.

    View definition and generalisation for database integration in a multidatabase system

    IEEE Trans. on Software Engineering

    (1984)
  • P.P. Chen

    The entity-relationship model-toward a unified view of data

    ACM Trans. on Database Systems

    (March 1976)
  • K.D. Mackenzie

    Virtual positions and power

    Management Science

    (May 1986)
  • P. Bolton et al.

    The firm as a communication network

    Quarterly Journal of Economics

    (Nov. 1994)
  • R. Carzo et al.

    Effects of flat and tall organization structure

    Administrative Science Quarterly

    (June 1969)
  • M. Kochen et al.

    Note on hierarchy and coordination: an aspect of decentralization

    Management Science

    (Sept. 1974)
  • Cited by (7)

    • Structuring requirement specifications with goals

      2001, Information and Software Technology
    • Dynamic partitioning of complex process models

      2000, Information and Software Technology
      Citation Excerpt :

      Indeed, the E3 p-draw mechanisms take full advantage of the knowledge and semantics associated to the pre-defined E3 classes and associations (e.g. the Responsible association). This observation is valid also for several other approaches on integrating conflicting requirement in process modeling [8]. In general, while most process modeling environments support some modularization feature at the language level (i.e. some module-like construct [7]), E3 p-draw makes it possible to select dynamically the amount of information that the process engineer wants to see and analyze at any stage of his/her work.

    • Requirements Interaction Management

      2003, ACM Computing Surveys
    View all citing articles on Scopus

    Tel: +39-2-23993540; Fax:+39-2-23993411.

    View full text