Toward an Integrated User Requirements Notation Framework and Tool forBusiness Process Management

Pourshahid, Alireza; Amyot, Daniel; Peyton, Liam; Ghanavati, Sepideh; Chen, Pengfei; Weiß, Michael; Forster, Alan J.

doi:10.1109/mcetech.2008.30

Cited by 22 publications

(24 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Yet, there exist a few studies that integrate process and requirements modeling [6] or derive requirements from process models [17]. Examples are goal modeling approaches utilized in early phases [18] and data-centric approaches [20]. The only study integrating problem frames and process modeling is tne by Cox et al, who link process models to problem frames via Role-Activity Diagrams [10].…”

Section: Related Workmentioning

confidence: 99%

Transforming Process Models to Problem Frames

Faßbender

Aysolmaz²

2016

Business Process Management Workshops

View full text Add to dashboard Cite

Abstract. An increase of process awareness within organizations and advances in IT systems led to a development of process-aware information systems (PAIS) in many organizations. UPROM is developed as a unified BPM methodology to conduct business process and user requirements analysis for PAIS in an integrated way. However, due to the purpose, granularity and form of UPROM artifacts, one cannot analyze the software requirements in detail with (semi-)formal methods for properties such as completeness, compliance and quality. In contrast, Problem Frames modeled using the UML4PF tool can be used for such analysis. But using the Problem Frames notation and corresponding methods alone does not cover a direct support for building a PAIS. Hence, in this work we propose to integrate UPROM and UML4PF using model transformation. We use eCompany, a project which is part of an e-government program, as running example.

show abstract

Section: Related Workmentioning

confidence: 99%

Transforming Process Models to Problem Frames

Faßbender

Aysolmaz²

2016

Business Process Management Workshops

View full text Add to dashboard Cite

show abstract

“…Performance indicators types are further visualized using a textual template. Pourshahid et al (2007Pourshahid et al ( , 2008 extend the User Requirements Notation (URN)-an ITU-T Recommendation incorporating two notations, the Goal-oriented Requirements Language (GRL) and Use Case Maps (UCM)-with concepts for indicator modeling. Their framework specifies a meta model in which the meta type ''Indicator'' is further refined by meta attributes including, e.g., ''isTimeMeasure'', ''isCostMeasure'', and ''isQualityMeasure'' (i.e.…”

Section: Related Workmentioning

confidence: 99%

“…6 summarizes key concepts in related work and identifies areas of improvement over existing approaches in the light of domain-specific requirements. Research on METRICM builds upon prior approaches in that earlier conceptualizations, in particular by Pourshahid et al (2007Pourshahid et al ( , 2008 and Popova and Sharpanskykh (2010), are reconceptualized and extended by further modeling concepts and a corresponding graphical notation.…”

Section: Related Workmentioning

confidence: 99%

MetricM: a modeling method in support of the reflective design and use of performance measurement systems

Strecker

Frank

Heise

et al. 2011

Inf Syst E-Bus Manage

View full text Add to dashboard Cite

Performance indicators play a key role in management practice. The existence of a coherent and consistent set of performance indicators is widely regarded as a prerequisite to making informed decisions in line with set objectives of the firm. Designing such a system of performance indicators requires a profound understanding of the relations between financial and non-financial metrics, organizational goals, aspired decision scenarios, and the relevant organizational context-including subtleties resulting from implicit assumptions and hidden agendas potentially leading to dysfunctional consequences connected with the ill-informed use of performance indicators. In this paper, we investigate whether a domainspecific modeling method can address requirements essential to the reflective design of performance measurement systems, and which structural and procedural features such a method entails. The research follows a design research process in which we describe a research artifact, and evaluate it to assess whether it meets intended goals and domain requirements. In the paper, we specify design goals, requirements and assumptions underlying the method construction, discuss the structural specification of the method and its design rationale, and provide an initial method evaluation.The results indicate that the modeling method satisfies the requirements of the Preliminary results of this research have been discussed in performance measurement domain, and that such a method contributes to the reflective definition and interpretation of performance measurement systems.

show abstract

“…Over the last decade, GRL and UCM have successfully been used for service-oriented, concurrent, distributed, and reactive systems such as telecommunications systems [9][12] [19][57], e-commerce systems [16], agent systems [46], operating systems [28], and health information systems [1][108]. Moreover, URN has been used for business process modeling, monitoring, and alignment [118][119] [121][147], for reverse engineering [15] [53], for tracking compliance with institutional and governmental policies, regulations, and legislation [48] [49], and for the formalization of patterns [89].…”

Section: User Requirements Notationmentioning

confidence: 99%

“…At first glance, UCM is very well suited to describe workflow. As a general scenario notation, the structure and intent are similar to workflow languages and UCM has already been used for business process modeling [118] [113], and the Business Process Execution Language for Web Services (BPEL4WS) [115]). The assessment also provides insight into how to evolve tool support and the traversal mechanism for UCM 2.0.…”

Section: Motivating the Need For Use Case Maps 20mentioning

confidence: 99%

The aspect-oriented user requirements notation

Mussbacher

2011

Proceedings of the Tenth International Conference on Aspect-Oriented Software Development Companion

View full text Add to dashboard Cite

Toward an Integrated User Requirements Notation Framework and Tool forBusiness Process Management

Cited by 22 publications

References 9 publications

Transforming Process Models to Problem Frames

Transforming Process Models to Problem Frames

MetricM: a modeling method in support of the reflective design and use of performance measurement systems

The aspect-oriented user requirements notation

Contact Info

Product

Resources

About