Integrating multi-perspective views into ontological analysis
ICIS '00 Proceedings of the twenty first international conference on Information systems
Guide to the Software Engineering Body of Knowledge - SWEBOK
Guide to the Software Engineering Body of Knowledge - SWEBOK
On the Challenges of Business Modeling in Large-Scale Reengineering Projects
ICRE '00 Proceedings of the 4th International Conference on Requirements Engineering (ICRE'00)
How Much Language Is Enough? Theoretical and Practical Use of the Business Process Modeling Notation
CAiSE '08 Proceedings of the 20th international conference on Advanced Information Systems Engineering
Guidelines for conducting and reporting case study research in software engineering
Empirical Software Engineering
Representing Unique Stakeholder Perspectives in BPM Notations
SERA '10 Proceedings of the 2010 Eighth ACIS International Conference on Software Engineering Research, Management and Applications
Process modeling for regional territorial planning
ECC'11 Proceedings of the 5th European conference on European computing conference
| Hi-index | 0.00 |
Business process models (BPM) can be useful for requirements elicitation, among other uses. Since the active participation of all stakeholders is a key factor for successful requirements engineering, it is important that BPM be shared by all stakeholders. Unfortunately, organizations may end up with inconsistent BPM not covering all stakeholders' needs and constraints. The use of multiple levels of abstraction (MLA), such as at the strategic, tactical and operational levels, is often used in various process-oriented initiatives to facilitate the consolidation of various stakeholders' needs and constraints. This article surveys the use of MLA in recent BPM research publications and reports on a BPM action-research case study conducted in a Canadian organization, with the aim of exploring the usefulness of the strategic level.