2012
DOI: 10.1007/978-3-642-29133-3_8
|View full text |Cite
|
Sign up to set email alerts
|

Modeling Business Objectives for Business Process Management

Abstract: Abstract. For application scenarios such as the management of business process variants or business process quality, business objective models assume the role of formal requirements definitions as in software engineering. However, effective concepts in this area still constitute a gap in the presently available array of business process management methods. To address this issue, this paper develops and shortly evaluates a refined business objective modeling approach. Our approach builds on use case-based effec… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
5
0
1

Year Published

2012
2012
2020
2020

Publication Types

Select...
6
2

Relationship

4
4

Authors

Journals

citations
Cited by 13 publications
(6 citation statements)
references
References 23 publications
0
5
0
1
Order By: Relevance
“…It addresses the handling of incoming job applications to fill open positions in a professional services firm. Figure 1 describes the business objective of this process according to a notation we developed in [14]. The objective of the process is to achieve one of two states for each job application: Either the application is refused, or a job offer is sent to the applicant.…”
Section: Sample Case: Applications Management Processmentioning
confidence: 99%
“…It addresses the handling of incoming job applications to fill open positions in a professional services firm. Figure 1 describes the business objective of this process according to a notation we developed in [14]. The objective of the process is to achieve one of two states for each job application: Either the application is refused, or a job offer is sent to the applicant.…”
Section: Sample Case: Applications Management Processmentioning
confidence: 99%
“…Usually, there exists a multitude of variants of a particular process model, whereby each of these variants is valid in a specific scenario or in the context of a particular business objective (Lohrmann and Reichert 2012); i.e., the configuration of a particular process variant depends on concrete requirements building the process context (Hallerbach et al 2008b;vom Brocke 2007). Regarding release management, for example, we have identified more than 20 process variants depending on the considered product series, involved suppliers, or development phases.…”
Section: Introductionmentioning
confidence: 99%
“…Variant management can be individually performed or through a group mechanism by means of an integration process [5]. However, not all variants can support the propagation of changes due to following issues: (a) their close relationship with the domain, (b) the execution in a specific context, and (c) the associated events that generated the variant [6].…”
Section: Introductionmentioning
confidence: 99%