Business process modeling and analysis system Modelowanie

Scientific Journals
Zeszyty Naukowe
Maritime University of Szczecin
Akademia Morska w Szczecinie
2010, 24(96) pp. 59–62
2010, 24(96) s. 59–62
Business process modeling and analysis system
Modelowanie procesów biznesowych i analiza systemowa
Elżbieta Milewska
Silesian University of Technology, Faculty of Organisation and Management
Institute of Production Engineering
Politechnika Śląska w Gliwicach, Wydział Organizacji i Zarządzania, Instytut Inżynierii Produkcji
41-800 Zabrze, ul. Roosevelta 26, e-mail: [email protected]
Key words: business model, BPMN, UML, information system
Abstract
The paper is characterized by efforts to create a business model of enterprise software and technical
documentation. The author points out that the overriding factor is to identify actions to modeling, which
defines the scope of the project. In mapping the organization and construction of scenarios of business
processes is of paramount importance dictionary of phrases and descriptions of domain rules of correctness
for the recording and processing. The author describes the key process models, partial (procedures) and
elementary (the workflow map.) This indicates the suitability of BPMN and UML notation in the record of
the mapping rules and modalities for the functioning of the organization and in the description of static and
dynamic structure of the system. Pointing to the integration of business process management system
architecture author assesses the suitability of the chosen modeling notation.
Słowa kluczowe: model przedsiębiorstwa, BPMN, UML, system informatyczny
Abstrakt
Artykuł charakteryzuje działania mające na celu utworzenie biznesowego modelu przedsiębiorstwa oraz dokumentacji technicznej oprogramowania. Autor dowodzi, że nadrzędnym czynnikiem działań jest określenie
celu modelowania, który definiuje zakres projektu. W odwzorowaniu organizacji i budowie scenariuszy procesów biznesowych fundamentalne znaczenie ma słownik zwrotów dziedzinowych i opis reguł poprawności
dotyczących zapisu i przetwarzania danych. Autor opisuje modele procesów głównych, cząstkowych (procedury) oraz elementarnych (mapę przepływu pracy). Wskazuje na przydatność notacji BPMN i UML w zapisie
odwzorowującym zasady i sposoby funkcjonowania organizacji oraz w opisie statycznej i dynamicznej struktury systemu informatycznego. Wskazując na integrację procesu zarządzania biznesowego z architekturą systemu informatycznego, autor dokonuje oceny przydatności wybranych notacji w zakresie modelowania.
Introduction
Our objectives
The gain a competitive edge are increasingly
choosing ability to manage the entire chain of value
creation and use of enterprise information technology organization. The way to learn tasks and rules
of the organization, and identification and documentation of information and decision-making
process is the company's business process modeling. It shall apply during the implementation of
specific projects, the IT industry in the deployment
and production management support tools.
The purpose of business process modeling
projects are not only the IT industry. The effect of
process approach can be flexible flow control and
processing of information in economic organization, to increase the efficiency and responsiveness to changes in market, implemented to
eliminate unnecessary steps in business processes,
to increase the flexibility of work and reduce costs.
The confirmation of the need to orient sustainable
enterprises in the business processes are ISO
Zeszyty Naukowe 24(96)
59
Elżbieta Milewska
9000:2000, in which the process approach and
partnership of all inquirers is the starting point of
construction quality management system.
The purpose of modeling is the overriding
factor, defining the scope of work (Fig. 1).
Estimating the needs of the organization is to:
 designation of areas to be analyzed,
 determining the scope of activities in the current
and future iterations,
 and identify the expected effects modeling.
• definition – describing the properties of the
object;
• fact – indicating the presence of an object in the
system;
• formula – responsible for processing the data,
illustrating the manner in which the calculations;
• limitation – a condition for the presence of
particular value in the system.
Taking into account the requirements and specification of information systems as an objective
modeling, one can distinguish two stages of creation of documentation (Fig. 1):
• Business model – which is a simplified representation of an isolated area of reality [1];
• Model system – understood as the implementation tools using the hardware infrastructure.
Range of solutions
Data of field
Business processes
Business rules
ORGANIZATION`S BUSINESS MODEL
Organizational
changes
Automation
Reorganization
process
Identification of business processes
SYSTEMS ANALYSIS
BUSINESS ANALYSIS
Project purpose
Because the expected outcome of modeling is
the identification and prioritization of business
processes together with an indication of the organizational units participating in the distinguished
process, and therefore the business model should
provide static and dynamic image of the organization in a selected area.
The basis for the construction of business model
is to interview an expert with stakeholders and
analysis of documentation (Fig. 2).
Result of the work is to give form of
documentation in the charts and diagrams showing
the business model of the enterprises which consist
of three elements:
 models the main processes,
 a sub-process models (procedures),
MODEL SYSTEM
specification, requirements and architecture implementations
Fig. 1. The computer system as an object of analysis
Rys. 1. System informatyczny jako przedmiot analizy
Rating organization, for the selection process to
be modeled, we need to develop a list of used terms
and phrases of domain and presentation rules for
the recording and accuracy of data processing
which are the foundation for business process
scenarios. There are four types of rules:
DATA COLLECTION
ANALYSIS AND MODELING
SPECIFYING
Patterns
documents
Map business
processes
List
of use cases
Organizational
structure
Model of the
system architecture
List of constraints
and interfaces
Designs
reports
Model
of the field
Data
model
Fig. 2. Stages of development of technical documentation software
Rys. 2. Etapy tworzenia dokumentacji technicznej oprogramowania
60
Scientific Journals 24(96)
Business process modeling and analysis system
 models of elementary processes (workflow
map).
Master process model as a simplified description
of reality, aimed to illustrate the method of building
goodwill in the market. Is described and defined by:
 sources of supply,
 sales channels,
 the impact of competition,
 the main source of profit margin (profit),
 sources of danger.
Analysis of business and market environment
allows for display of relevant information regarding
current and future competitiveness of the company
is evaluating the potential for business growth,
increase market share, identify priorities for action
with the customers, market news feeds Business
and perceived use value of products offered.
Map of sub-processes is a picture showing all
the features that are implemented within the
organization in order to produce finished products.
It allows you to manage projects, the detailed
definition of resources and processes to describe the
correlation with the procedures. A characteristic
feature is their uniqueness.
An important element in the identification
process is to identify critical paths, which is made
mandatory steps to preserve data integrity and
accuracy of results. Identification of processes
allows for better understanding the business and
technology.
• Notation BPMN (Business Process called
Modeling Notation) – Used to record the results
of the analysis and mapping of business
processes [2];
• Notation of UML (Unified Modeling Language)
– Documenting the specification, design requirements and system architecture [3, 4];
• Description of the verbal patterns.
The choice was dictated by the compatibility of
these ideas and notation of their mutual
complementarity. The model describes the process
using BPMN notation is a logical representation of
rules and practices of the organization. Maps of the
business, showing the picture of the course work
and becoming a tool for the business analyst. UML
is the tool for architectural design and documentation systems, supporting the software production
process – from design to implementation.
It should be noted that the clarification of the
record in the form of UML behavioral models
applies only to projects requiring automation of
business processes that are carried out mainly in the
IT industry.
Since the choice of notation used in the
modeling is of paramount importance for the
integration process, business process management
architecture system, which is why the article has
evaluated the suitability of BPMN and UML
notation by the below criteria (Tab. 1). To
determine the compatibility of the following
symbols are used: “+” meets the criterion “–” does
not meet the criterion and partial “+/–” criterion.
Language selection record
Table 1. Evaluation of the usefulness notation
and UML
Tabela 1. Ocena przydatności notacji BPMN i UML
Understanding the essence of business processes
is the foundation of software engineering, acting in
the first stage incremental life-cycle system. Since
the analysis system is to determine the desired
action or course of action by identifying and
considering the options available and compare their
predicted consequences, and therefore requires
a clear definition of the limits of the test system and
its components. Complexity of requirements and
design specifications to present architecture of
forces the necessity of system models using languages and modeling. Usefulness of the description
of static and dynamic structure of the system taking
into account the reconfiguration of the system over
time, changes in the set of components and a set of
defining relations and the dynamics of interaction,
communication and data control messages depends
on the extent of the syntax and semantics of
language. Previous experience of the author’s
creation described in the documentation indicate
the use of the following standards:
Zeszyty Naukowe 24(96)
No.
Criterion choreography
1
Data flow
2
3
4
Description of the policy / business rules
5
BPMN
BPMN UML
–
+
Processing documents
–
+
Event description
+
+
+/–
+
Description of special events
–
+
6
Process transactions (distributed, compensatory, synchronous and asynchronous)
+
+/–
7
Display hierarchical data (inheritance,
structure)
–
+
Conclusions
Documentation of processes allows for continuous improvement of business organization, faster
response to changes in business environment and
familiarize staff with the functions performed by
them in the context of business value chain.
61
Elżbieta Milewska
References
Technical documentation software allows the
estimation of the viability of implementing an IT
solution to be analyzed, justifying any restriction
system, and provide possible areas of application
development.
Projects implemented by the above assumptions
are classified into a coherent, open solutions, allowing simple of the field extend their functionality.
1. BOJARSKI W.: Podstawy analizy i inżynierii systemów.
PWN, Warszawa 1984.
2. Business Process Modeling Notation Version 1.0, May
2004 (http://www.bpmn.org).
3. OMG Unified Modeling Language Specification Version
1.5, March 2003 (http://www.omg.org/technology/documents/formal/uml.htm).
4. PENKER M., ERIKSSON H.E.: Business Modeling With
UML: Business Patterns at Work. Addison-Wesley (2000).
Recenzent:
prof. dr hab. inż. Krzysztof Chwesiuk
Akademia Morska w Szczecinie
62
Scientific Journals 24(96)