Business process management with the user requirements notation

被引:0
|
作者
Alireza Pourshahid
Daniel Amyot
Liam Peyton
Sepideh Ghanavati
Pengfei Chen
Michael Weiss
Alan J. Forster
机构
[1] University of Ottawa,School of Information Technology and Engineering (SITE)
[2] IBM,Department of Systems and Computer Engineering
[3] Carleton University,Department of Medicine
[4] Research In Motion,Ottawa Health Research Institute, Clinical Epidemiology Program
[5] University of Ottawa,undefined
[6] Ottawa Hospital,undefined
来源
关键词
Business process management; Business process model; Goal-oriented business process monitoring; Performance management; User requirement notation;
D O I
暂无
中图分类号
学科分类号
摘要
A number of recent initiatives in both academia and industry have sought to achieve improvements in e-businesses through the utilization of Business Process Management (BPM) methodologies and tools. However there are still some inadequacies that need to be addressed when it comes to achieving alignment between business goals and business processes. The User Requirements Notation (URN), recently standardized by ITU-T, has some unique features and capabilities beyond what is available in other notations that can help address alignment issues. In this paper, a URN-based framework and its supporting toolset are introduced which provide business process monitoring and performance management capabilities integrated across the BPM lifecycle. The framework extends the URN notation with Key Performance Indicators (KPIs) and other concepts to measure and align processes and goals. An example process for controlling access to a healthcare data warehouse is used to illustrate and evaluate the framework. Early results indicate the feasibility of the approach.
引用
收藏
页码:269 / 316
页数:47
相关论文
共 50 条
  • [31] Combined Goal and Feature Model Reasoning with the User Requirements Notation and jUCMNav
    Liu, Yanji
    Su, Yukun
    Yin, Xinshang
    Mussbacher, Gunter
    [J]. 2014 IEEE 22ND INTERNATIONAL REQUIREMENTS ENGINEERING CONFERENCE (RE), 2014, : 321 - 322
  • [32] An automated change impact analysis approach for User Requirements Notation models
    Alkaf, Hasan
    Hassine, Jameleddine
    Binalialhag, Taha
    Amyot, Daniel
    [J]. JOURNAL OF SYSTEMS AND SOFTWARE, 2019, 157
  • [33] A Digital Business Analysis Method A Business Requirements Engineering Process by the Cooperation of Management, Business Operation and IT Department
    Yamaguchi, Ichiro
    Furukawa, Masanobu
    Aoyama, Mikio
    Kikushima, Yasuhiro
    [J]. REQUIREMENTS ENGINEERING TOWARD SUSTAINABLE WORLD, 2016, 671 : 123 - 131
  • [34] Business Process Model and Notation: The Current State of Affairs
    Kocbek, Mateja
    Jost, Gregor
    Hericko, Marjan
    Polancic, Gregor
    [J]. COMPUTER SCIENCE AND INFORMATION SYSTEMS, 2015, 12 (02) : 509 - 539
  • [35] Towards Traceability Metamodel for Business Process Modeling Notation
    Pavalkis, Saulius
    Nemuraite, Lina
    Mileviciene, Edita
    [J]. BUILDING THE E-WORLD ECOSYSTEM, 2011, 353 : 177 - +
  • [36] Financial Risk Management in e-commerce Using Executable Business Process Modeling Notation
    Iyer, Ramkumar
    Moorthy, Sanjeevi
    [J]. DISTRIBUTED COMPUTING AND INTERNET TECHNOLOGY, ICDCIT 2015, 2015, 8956 : 233 - 238
  • [37] Business Process Modelling Notation from the Methodical Perspective
    Repa, Vaclav
    [J]. TOWARDS A SERVICE-BASED INTERNET: SERVICEWAVE 2010 WORKSHOPS, 2011, 6569 : 160 - 171
  • [38] A Business Process Modeling Notation Extension for Risk Handling
    Marcinkowski, Bartosz
    Kuciapski, Michal
    [J]. COMPUTER INFORMATION SYSTEMS AND INDUSTRIAL MANAGEMENT (CISIM), 2012, 7564 : 374 - 381
  • [39] Extending the Multiple Domain Matrix by Using Business Process Model and Notation for Business Process Analysis
    Lee, Wen-Tin
    Ma, Shang-Pin
    Lee, Shin-Jie
    Law, Po-Jen
    Chang, Ting-Shao
    [J]. 2015 IEEE 12TH INTERNATIONAL CONFERENCE ON E-BUSINESS ENGINEERING (ICEBE), 2015, : 311 - 318
  • [40] Business implications on the requirements process
    Miller, B
    [J]. FIFTH IEEE INTERNATIONAL SYMPOSIUM ON REQUIREMENTS ENGINEERING, PROCEEDINGS, 2001, : 274 - 274