Chapter 3

Design Phase: EIS Business Infrastructure

Olfa GADDOUR

April, 2025
 Course Outline

2
 Business Infrastructure
Business View

Descending or “Top-Down” Approach

Business process

Functional View

Job
Functions & Flows

Application View
Technology

Applications & Software

Physical View
Hardware Infrastructure

Technical Infrastructure

3
 Concept of Process in
general

4
 Procedure vs Process

I
Describes the successive steps
S Procedure necessary to carry out a
O specific activity
- Procédé
9
0 Describes the sequence of
0 Process activities leading to a
result
1
5
 Inputs Sequence of
Outputs
activities

• A Process is an ordered set of

interrelated and interacting activities
or sub-processes that transform inputs
into outputs.
6
 Constraints
ent
onm
nvir
E Sequence of
Inputs Outputs
activities

Human
Ressources Methods
Tools
Resources
Processes

• A Process operates in a specific environment, is

subject to constraints, and consumes
resources.
• A Process is triggered by at least one event.

7
 Entreprise Business Process

8
E X A M P L E P R O C E SS : L E AV E
P R O C E SS ( 1 )

Text description of the Employee Leave Request

Process in a Company

• The request is submitted by the employee

to their department manager, who signs it
and forwards it to the HR department.
• The HR department approves or rejects the
request, calculates leave for the approved
request, and makes the payment.
• Finally, the HR department forwards the
new change to the security department to
update the employee's access.

9
EXAMPLE PROCESS:
L E AV E P R O C E S S ( 1 )
Leave Request Process

Actors

Application
Employee Entry

He ad of
Sending the
D e part m en t
Request

No
HR Department Receipt of the Request Ye s Vacation
Request validation Countdown Payment

Security Access
Service Update

10
 MADE-TO -ORDER
PROCESS

Purchases Production Design Client

office
Technical Call for
Studies Tenders

Quote Response to
Delivery the Call for
time Tenders

Material Manufacturing
Requirements planning Order
Purchase Order

11
Processing of Purchase Orders from Production Planning

Supplier(s) Accounting
Department Reception Purchases
Request for Price
Consultation and Delivery
Time

Choice of
Offers Supplier

Placing an
Order
Order

Receiving slips
Shipping
Stock entries

Invoice
Invoice
Control

Payment of the
Regulations
Invoice

12
Trigger(s)
Activity Chains

Inputs

Actor 1
Outputs
Actor 2
Result(s):
Products or
Actor 3 Services

• A Business Process is a sequence of

activities linked to each other to
collectively achieve a business objective by
defining roles and functional interactions
within an organizational structure.

13
C O N C E P T I O N SIE : NIVEAU M É T I E R
INTEGRITY – INTEROPERABILITY –
•FLEXIBILITY
Integrity
– The EIS must cover all of the business processes
operated by the company
• Interoperability
– The EIS must ensure communication between
the different Business Processes of the
Company
– Example: The “Customer Order” Business Process can
automatically trigger another “manufacturing” Business Process
• Flexibility
– The EIS must update the Business Processes
already defined and possibly extend them as
needed with new Processes.
14
 Why model a process?

15
 POURQUOI
M O D É L I S E R LES
PROCESSUS
• Process Execution
MÉTIER ?
 This requires collaboration between
stakeholders from different departments,
both within and between companies.
• Process Evolution
 This requires some updating compared to
its previous versions.
• Process Standardization and Normalization
 This is the current and major concern of
various stakeholders in the business world.

16
 M O D É L I S AT I O N PROCESSUS M É T I E R
INTEGRITY – INTEROPERABILITY – FLEXIBILITY

• Integrity
 Modeling must cover all of the company's business
activities.
• Interoperability
 The chosen Modeling Language must be a standard
and must support intra- and inter-process
collaboration
• Flexibility
 The chosen Modeling Language must facilitate
updates, extensions, and evolution of different
Process versions 17
 C H O I C E O F B U S I N E SS P R O C E SS
MODELING LANGUAGE (1)

• Business Process Modeling Languages

• Existence of Several Languages
• We are interested in formalisms that offer graphical notations (Business
Process Diagram)

• Business analysts (business teams) who define the Processes are not
necessarily IT specialists

• Graphical notation is highly recommended

• it facilitates readability and therefore understanding of
the Process

18
C H O I C E O F B U S I N E SS P R O C E SS
MODELING LANGUAGE (2)

• UML 2.0 (Unified Modelling Language)

– UML is a standard proposed by the OMG
(Object Management Group).
– UML offers its users the ability to
perform graphical modeling through a
set of 9 diagrams.
– The UML Activity Diagram allows you to
model business processes.

19
 C H O I C E O F B U S I N E SS P R O C E SS
MODELING LANGUAGE (3)

• YAWL (Yet Another Workflow Language)

– YAWL is an extension of Petri nets.
– YAWL is equipped with an execution engine
– enabling the simulation of processes.

20
 C H O I C E O F B U S I N E SS P R O C E SS
MODELING LANGUAGE (4)

• BPMN (Business Process Modeling

Notation)
– B P M N is a g ra p hi ca l s ta nda rd f o r B u s i ne s s
P ro ce s s M o d e l i ng .
– B P M N a l lows yo u to d e s cr i be a B u s i ne s s
P ro ce s s th a t i s u nd e r s ta nd a b le to a ll
s ta ke ho l de r s ( bu s ine s s a na lys ts a nd
d eve lo p e r s ) .
– B P M N a l lows yo u to d i s ti ng u i s h b u s i ne s s
i nfo r m a ti o n fro m te chni ca l i nfo r m a tio n a nd
p rov i de s a m a p p ing to exe cu ti o n la ng u a g e s .

21
• BPMN (Business Process
Modeling Notation)

22
C H O I X DU L A N G A G E D E M O D É L I S AT I O N DES
PROCESSUS M É T I E R (6)
[Z AHAF , 2014]
U M L 2.0 B P M N 2.0 YAWL
Functional + ++ +
Behavioral + ++ ++
INTEGRITY
Informational ++ ++ -
Organizational + ++ -
Operational + ++ +
Design + ++ +
FLEXIBILITY Change - - -
Extension ++ ++ -
Intraprocess + ++ -
INTEROPERABILITY
Interprocess - + -

23
 BPMN : STANDARD BUSINESS
PROCESS MODELING LANGUAGE
(BUSINESSSTANDARD
PROCESSB PMODELING
MN

NOTATION)

Need: Standard Notation Chart for

Modeling Business Processes

Solution : Standard BP M N 2.0 (January

Standard for 2011)
Proposed par
O M G (Object Semantic Execution
Graphic
Management Standard standard
Elements
Group)

25
MODELING TOOLS B P M N 2.0 :
BIZAGI PROCESS MODELER

26
EXAMPLE OF MODELING WITH
BPMN 2.0
 Sequence Flow Message Flow Association
Start Intermediate End
Events Connectors

Exclusive Parallel Inclusive

Task Sub- Connection Connection Connection
Process
Activities Bridges

Data Data Store Annotation Group

Object

Process / Actors Artefacts

 B A S I C S Y M B O L S ( 1 ) : F LO W
OBJECTS

Symbols
Departure Event / Trigger
Example: Supplier Invoice arrives

End Event / Result

Example: Supplier Invoice paid

Intermediate Event
Example: Wait 1 hour, Arrival of an
Order cancellation

29
 B A S I C S Y M B O L S ( 2 ) : F LO W
OBJECTS

Symbols
Exclusive Connection
Example: Yes/No Decision

Parallel Branching
Example: Mandatory launch of all
parallel tasks
Inclusive Branching
Example: Possible Launch of Parallel
Tasks

30
 B A S I C S Y M B O L S ( 3 ) : F LO W O B J E C T S

Symbols
Activity / Task / Elementary Activity
Example: Checking the receipt of goods

Sub-Process / Composite Activity

Represents a set of Tasks or even a
Process that does not need to be
detailed in the current Process
The "+" symbol indicates the presence of
a Sub-Process

31
 S Y M B O L E S D E BASE (4) :
CONNECTION OBJECTS:
SEQUENCE FLOWS
Symbols
Sequence Flow
Determines the execution order of
Activities
Default Sequence Flow Determines
the default execution order of
Activities

32
 S Y M B O L E S D E BASE (5) :

CONNECTION OBJECTS: MESSAGE FLOW

Symbols
MESSAGE FLOW
Collaborative Model (exchange of
Information between Processes)

33
 S Y M B O L E S D E BASE (6) :
ORGANIZATION OBJECTS:
SWIMLANES
Symbols
Process (Grouping - Pool)
Specifies the limits of the Process

Corridors / Bands
Defines the Actors

34
 S Y M B O L E S D E BASE (7) :
ORGANIZATION OBJECTS: SWIMLANES

Symbols
Milestone

35
 B A S I C S Y M B O L S ( 8 ) : D ATA
OBJECTS

Symboles
Data Objects
Describes the user manual of documents
(electronic or not), data and possibly other
objects that are necessary during the
execution of the Process

Data Stores
Describes the databases (workbooks, etc.)
used in Read/Write modes by the Process
participants. The contents of these databases
persist even after the Process ends.

36
 BASIC RULES
Reading/Writing Direction

• Read/Write Direction
• Left -> Right
• Only one "Blank" Start event per Process
• Multiple Start events can be used if their type is specified
• One (or more) End(s)
• Each Branch of the Flow ends with an End event
• Token Principle
37
 BASIC RULES: TOKEN
PRINCIPLE

Token

• The Start event issues a token

38
 BASIC RULES: TOKEN
PRINCIPLE

Token

• The Start event issues a token

• A Task executes when it receives a token

39
 BASIC RULES: TOKEN
PRINCIPLE

Token

• The Start event issues a token

• A Task executes when it receives a token
• Once the Task completes its execution, it
releases the token.
• Special cases:
Parallel Branching
Intermediate Events
40
 BASIC RULES: TOKEN
PRINCIPLE

Token

• The Start event issues a token

• A Task executes when it receives a token
• Once the Task completes its execution, it releases the
token.
• Special cases:
• Parallel Branching
• Intermediate Events
• The End event absorbs the token(s)
41
 B A S I C R U L E S : B R A N C H I N G O U T:
INTEREST?

• Connection Symbols:
• The Branch (Gateway) symbol is used to control
divergences and convergences at the sequential activity
flows in a Process.
• Branch: Indicates that there is a mechanism that allows or
denies the passage of the Token at the Gateway level.
• – If the flow does not need to be controlled, then there is
no need to use a Branch.

divergence convergence 42
 Thank you!
Questions?

43