Models for supporting the redesign of organizational work
COCS '95 Proceedings of conference on Organizational computing systems
ACM Transactions on Information Systems (TOIS)
Business Process Management: The Third Wave
Business Process Management: The Third Wave
ER '02 Proceedings of the 21st International Conference on Conceptual Modeling
Goal-Oriented Requirements Engineering: A Guided Tour
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Modelling strategic relationships for process reengineering
Modelling strategic relationships for process reengineering
Specifying and analyzing early requirements in Tropos
Requirements Engineering
Process Aware Information Systems: Bridging People and Software Through Process Technology
Process Aware Information Systems: Bridging People and Software Through Process Technology
Agent-based prototyping of web-based systems
IEA/AIE'06 Proceedings of the 19th international conference on Advances in Applied Artificial Intelligence: industrial, Engineering and Other Applications of Applied Intelligent Systems
A declarative foundation of process models
CAiSE'05 Proceedings of the 17th international conference on Advanced Information Systems Engineering
Business process management with the user requirements notation
Electronic Commerce Research
Validation of user intentions in process models
CAiSE'12 Proceedings of the 24th international conference on Advanced Information Systems Engineering
Business process design from virtual organization intentional models
CAiSE'12 Proceedings of the 24th international conference on Advanced Information Systems Engineering
Investigating Goal-Oriented Requirements Engineering for Business Processes
Journal of Database Management
Hi-index | 0.00 |
The premise behind ‘third wave' Business Process Management (BPM1) is effective support for change at levels. Business Process Modeling (BPM2) notations such as BPMN are used to effectively conceptualize and communicate process configurations to relevant stakeholders. In this paper we argue that the management of change throughout the business process model lifecycle requires greater conceptual support achieved via a combination of complementary notations. As such the focus in this paper is on the co-evolution of operational (BPMN) and organizational (i*) models. Our intent is to provide a way of expressing changes, which arise in one model, effectively in the other model. We present constrained development methodologies capable of guiding an analyst when reflecting changes from an i* model to a BPMN model and vice-versa.