2010 Eighth ACIS International Conference on Software Engineering Research, Management and Applications 2010
DOI: 10.1109/sera.2010.16
|View full text |Cite
|
Sign up to set email alerts
|

Representing Unique Stakeholder Perspectives in BPM Notations

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
7
0

Year Published

2011
2011
2019
2019

Publication Types

Select...
3
3
1

Relationship

2
5

Authors

Journals

citations
Cited by 7 publications
(7 citation statements)
references
References 36 publications
0
7
0
Order By: Relevance
“…Accidental difficulties: − Inadequate requirements elicitation practices, when the customers cannot articulate requirements or they are not involved enough in the requirements engineering process. − Rework and miscommunications due to many notations that are utilized by different stakeholders, like BPMN and UML [8] − Deficiencies in backward traceability make it difficult to keep consistency between documentation and the underlying information system [9,10] 3. Challenges:…”
Section: Essential Difficultiesmentioning
confidence: 99%
“…Accidental difficulties: − Inadequate requirements elicitation practices, when the customers cannot articulate requirements or they are not involved enough in the requirements engineering process. − Rework and miscommunications due to many notations that are utilized by different stakeholders, like BPMN and UML [8] − Deficiencies in backward traceability make it difficult to keep consistency between documentation and the underlying information system [9,10] 3. Challenges:…”
Section: Essential Difficultiesmentioning
confidence: 99%
“…One has to think that the understanding should take into consideration the target audience of the artefact and not always something that offers lots of information helps. There has been several business process modeling notations over the years as discussed (Monsalve et al 2010) -however, till date there is not one notation to satisfy all.…”
Section: Research Objectivementioning
confidence: 99%
“…In the next part of this paper, we propose a solution to this problem in the form of a multiperspective graphical representation that combines as many different control perspectives as possible. The proposed approach builds on the concepts published by Monsalve, April, and Abran [1], who proposed a multiperspective BPM notation that identifies the specific BPM constructs preferred by stakeholders. Before describing the proposed multiperspective framework in more detail, a synthesis is required of the many different approaches currently used to graphically represent hierarchical information (such as internal controls).…”
Section: Existing Internal Control Approachesmentioning
confidence: 99%
“…Despite awareness of the importance of internal controls and recent research proposals in the field of multiperspective business process analysis [1], there is currently no methodology that helps with the implementation of internal controls that consider more than one perspective in a business process representation. Today, internal control representation is often too specific and only oriented toward one perspective (e.g.…”
Section: Introductionmentioning
confidence: 99%