IDEAS home Printed from https://ideas.repec.org/a/scn/025686/16532915.html
   My bibliography  Save this article

Designing executable business processes as a programming paradigm

Author

Listed:
  • MIKHEEV ANDREY G.
  • PYATETSKIY VALERIY E.

Abstract

This article discusses techniques used to design business processes that are directly executable on the computer system of an enterprise (executable business processes). It also describes the experience of teaching the elements of this technology. This experience was accumulated within two years of teaching process disciplines to bachelors and masters in National University of Science and Technology MISiS and Moscow State University of Economics, Statistics and Informatics (MESI). One of the reasons to choose the process way of enterprise automation is reducing the cost of automation. In traditional automation, at first the business analyst describes the functionality of the designed system in the form of text, then the programmer translates it into code. The use of executable business processes would make it possible to avoid duplication of work in many ways. In this case the business analyst with the customer uses visual graphic software to develop the business processes of automated functionality which will then be executed directly in the computer environment. Schemes of executable business processes are the human-readable graphical description of the corresponding functionality and it’s not necessary to translate them into code. Therefore, the cost of analytical work in this case is the same while the cost of programming is significantly lower. If the business environment changes, the business analyst can quickly change the schemes of business processes accordingly without involving the programmer. In addition, in many cases, the business analyst can independently (without programmer) develop new business processes. Therefore, the cost of development, maintenance and support of such IT-solutions is significantly lower than the cost of traditional solutions, while the speed of development, implementation and subsequent changes is significantly higher. These advantages (faster, cheaper, easier to maintain and support) are the same advantages the paradigm of object-oriented programming has over the procedural programming paradigm. By analogy, we can call the development of software solutions based on executable business processes a new programming paradigm with respect to the traditional approach. Process automation based on executable business processes requires process thinking from business analysts that differs from the thinking of IT specialists in the traditional enterprise automation. In addition to knowledge of business process notations, business analysts should be able to implement the typical situations in enterprise business in the form of executable business processes. This article presents the methodology that was used to teach students the process thinking.

Suggested Citation

  • Mikheev Andrey G. & Pyatetskiy Valeriy E., 2016. "Designing executable business processes as a programming paradigm," Бизнес-информатика, CyberLeninka;Федеральное государственное автономное образовательное учреждение высшего образования «Национальный исследовательский университет «Высшая школа экономики», issue 1 (35), pages 45-56.
  • Handle: RePEc:scn:025686:16532915
    as

    Download full text from publisher

    File URL: http://cyberleninka.ru/article/n/designing-executable-business-processes-as-a-programming-paradigm
    Download Restriction: no
    ---><---

    Corrections

    All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:scn:025686:16532915. See general information about how to correct material in RePEc.

    If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.

    We have no bibliographic references for this item. You can help adding them by using this form .

    If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.

    For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: CyberLeninka (email available below). General contact details of provider: http://cyberleninka.ru/ .

    Please note that corrections may take a couple of weeks to filter through the various RePEc services.

    IDEAS is a RePEc service. RePEc uses bibliographic data supplied by the respective publishers.