Representing unique stakeholder perspectives in BPM notations
Abstract:
Evidence shows that proposals for new modeling notations emerge and evolution of current ones are becoming more complex, often in an attempt to satisfy the many different modeling perspectives required by each stakeholder. This paper presents a method to identify the specific notation construct requirements, at multiple levels of abstraction, which satisfy the needs of a stakeholder when performing a specific task. Initially the focus is on two different stakeholders: software engineers (SE) and business analysts (BA), and one specific software engineering activity: requirements eliciting and analysis. The specific body of knowledge of the two stakeholders (Software Engineering Book of Knowledge (SWEBOK) for the SE, and Business Analysis Body of Knowledge (BABOK) for the BA) are used to identify each stakeholder specific notation construct requirements, at multiple levels of abstraction, in order to propose a simplification of their notation and constructs set. This paper presents solution avenues to simplify business process modeling notations by identifying the specific constructs preferred by different stakeholders. © 2010 IEEE.
Año de publicación:
2010
Keywords:
- levels of abstraction
- Business process modeling
- Software requirements
- System requirements
- Representational analysis
Fuente:
Tipo de documento:
Conference Object
Estado:
Acceso restringido
Áreas de conocimiento:
Áreas temáticas:
- Programación informática, programas, datos, seguridad
- Dirección general
- Interacción social