Plan

Modeling and information systems

• Information systems
• Process modeling
• Processes and typology of processes
• Process modeling approach
• Model and metamodel
• Notion of well-structured process
Process modeling languages
• Petri net
• SADT
• MERISE
• UML
• BPMN

ARIS language and platform

1
Process modeling languages
7 functions
o Modeling o Pilot
. languages, syntax... . track activity, performance
o Publish o Evaluate
. static, dynamic... . measuring performance, the
o Simulate resource consumption, time
. calculate, dimension... planned/actual...
o Execute o Integrate
. orchestrate services . organize the exchanges

Process modeling languages

o Petri net (PN)
o Merise
o UML
o SADT
o BPMN
o Aris
o … 2
Petri net (Pn)

Petri Network (Pn): Modeling language represented in the form of a directed bipartite graph
(places and transitions).
The places are represented by circles (the states).
Transitions are represented by lines (events).
Each place contains a whole number of marks (or tokens) to model the
system dynamics.
A place is active when it has at least 1 token.

P0
Place
Transition
Correct
Mark (or Token) P1 P2
Arc
False condition Incorrect
P3
True condition

3
Petri net (Pn)

A transition is passable = All upstream positions are active.

Crossing:
o remove the upstream brands and introduce the downstream brands
o 1 crossing by step of the system

P0 P0

P1 P1

Franchisable transition non-franchisable transition

P0 P0
P3 P3
P1 P1
Places Among Avales Places

Crossing a transition
4
Petri net (Pn)

Etat = vector of the number of brands

(P0, P1, P2, P3, P4): let (1, 1, 0, 0, 0) then (0, 0, 1, 1, 1)

P2 P2
P0 P0
P3 P3
P1 P1
P4 P4

5
Petri Net (Exercise)

Custom wood cutting workshop

o The workshop includes only one cutting machine.
o Orders are delivered as soon as they are cut.
Conditions (Places)
o The cutting machine is idle (inactive workshop)
o An order is pending
o The order is being cut.
o The order is complete.
The events that constitute a 'change of state' (Transitions)
o An order is arriving
o The machine starts the order
o The machine completes the order
o The order is sent for delivery.

2013 Modeling Course 3IF. Pierre-Alain MILLET 6

Petri Net (Example)

Wood cutting workshop

Stock of
boys?
Priorities?

7
Petri net and Process

A single model with two elements: places and transitions.

No obvious representation.

Main usage: to study the possible states of a system and to size it

for a certain characteristic of the flow (simulations).

Used as a formalism by the DEM modeling tool.

8
 Structured Analysis and Design Technique (SADT)

SADT is a graphical method particularly well suited for a description

functional of the IS.
Actigrams and datagrams do not have the same level of granularity (the datagram
is more detailed).

Actigram Datagram

Control data Constraints

(comment?)

Input data Activity Output data Entry activity Outdoor activity

Data
(on what?) (What to do?) (why) (generator) (user)

Support mechanisms Mechanisms of

(With what?) support

(Henry Baccon, Urbanization of Information Systems)

9
 Structured Analysis and Design Technic (SADT)

Hierarchy of diagrams: parent-child diagrams (3 to 6 boxes max per diagram)

. The description of a system is done in the form of a coherent sequence of diagrams.
. The highest-level diagram represents the purpose of the system (A-0) (overall function).

10
Structured Analysis and Design Technic (SADT)

Actigram and datagram (example)

Actigram

Printing order Box: action verb

Flèches: nom

White paper Print a Printed PDF

PDF

Printer

Datagram
Boite: nom
Follow the instructions Arrows: action verb

Provide of Print
white paper White paper PDF

Supplier
11
 Structured Analysis and Design Technique (SADT)
Woodcutting workshop (Actigram)

Order
received Record
Order
Available Workshop
Order recorded
Lancer Cutting voucher
Order

Cut out Piece

Wood
Order

Cut
Deliver Delivery
Order

A0 Cutting workshop
12
SADT and Process

Analysis and understanding of complex systems

Communication tool for:

. Team (analysts)
. Clients (expression of needs)
. Hierarchy (management and monitoring of the project)

Viewpoints
. Data and activities
. No organizational view

Main usage
. Analyse de système

13
 MERISE
MERISE: Method of Study and Computer Realization for Business Systems

Conceptual Level Data Processing

. What? Conceptual MCD MCT
. What the company does
Logic MLD MLT
Organizational Level / Logic Organizational (MOT
. Who? organizational
Physical / operational level
. How? With what? Physical MPD MOT
. The technical and material means Operational (Operational MOT)
and software

Conceptual model of processes = CMP

. A process is a view of the MCT corresponding to a relevant sequence.
operations from the perspective of analysis.
Logical model (organizational) of treatments = MLT (MOT)
. describe in detail the organization to be set up to achieve
14
MERISE

Flow diagram: graphical representation of actors and flows

Example: Claims management in an insurance company

15
 MERISE

The conceptual data model (CDM):

Static representation of the information system

Representation of data that is easily understandable: 'entity-relationship'

. Entities (with attributes and primary key)

. Relations between entities (binary, ternary...)
. Cardinalities (min, max)

Person Car
possesses
ID-Person 0:n 1:1 Car ID
Name brand
First name date color
Date of birth acquisition

16
 MERISE
Conceptual Model of Treatments (CMT)

Sequence of operations triggered by contributory events, producing others

event results. Event:
o Collection of facts, likely
to trigger an operation
under the conditions specified by
the synchronization.
o The intervention of time (date /
hour) is an event
outside.

Synchronization:
o Logical proposition (AND, OR).

Actors are optional

17
 MERISE
Conceptual Treatment Model (CTM)
Example: Claims management in an insurance company

18
 MERISE
Organizational Model of Treatments (OMT)

Breaking down the MCT operations into functional procedures: a succession of

treatments
Taking into account the organization of the company
. Each procedure is assigned to a workstation.
. Additional indications
o Resources used
o Manual or automatic tasks
o Real time or delayed time (automatic case)
o Duration
o Place
Table of functional procedures
Weather Workstation
Procédure Début Durée Lieu Ressource Responsible

19
 MERISE
Organizational Treatment Model (OTM)

MCT + ... = MOT

. Resources
. Actors
R1
R2 . Functional procedure number
in the operation
No. . Type T:
T
o Real-time automatic (TR)
o deferred (TD)
o manual (MA)

20
 MERISE
Organizational Model of Treatments (OMT): Example

1
TR

2
MA

21
MERISE and Process

Business Process
o No explicit modeling of objectives, decisions other than
as information

Points of view
o Data and processing
o No resource views (only mentioned in the MOT)

Main use
o Management Information System Design

22
Unified Modeling Language (UML)
UML: convergence of efforts in object-oriented software design
o Semi-formal language
o Standardized by the OMG
o Not a method, a notation independent of any language...
Modeling levels
o System: in its environment and interactions with users
o Sub-systems: hierarchical structural decomposition of the system
o Entity: detailed modeling at the object level
Usage modes
o « spécification »: (analyse de besoins, comprendre les fonctionnalités du
system...)
o "Outline": (to generate a skeleton...)
o « développement »: générer du code à partir des modèles
Everything is an object

o Processes, actors, information -> class diagram

o Fundamentally describe the information associated with objects and constitutes
thus an 'informational view' of objects.
23
Unified Modeling Language (UML)

14 diagrams allow for the visualization and manipulation of modeling elements.

3 axes of modeling:

. The functional axis describes what the system does. Functional

Use case diagram
. The static axis describes the structure of the system.

. The dynamic axis that is related to construction

system features.

Dynamic
State diagram
Activity diagram
Static Sequence diagram
Class diagram
Object diagram
Deployment diagram

24
Unified Modeling Language (UML)

The process approach with UML

Use case diagrams
o Interaction situation between system and actors
o Functional scenarios
o Reference in the development cycle (from requirements to testing)
o Use case diagram (overview of interactions).

Interaction diagrams
o Case scenarios (interactions between objects)
o Sequence diagram (temporal interaction)

Activity diagrams
o Simplified state-transition diagram (flow between activities)
o Equivalent to the MOT of MERISE

25
Unified Modeling Language (UML)

Use case diagram

Definitions
o Sequence of activities or actions
in response to a request
of an actor
Why?
o Collect, analyze, and organize
the needs of users
o Review the great ones
system features
o Define:
o functional needs
o the functional perimeter

. Inclusion : X « includes » Y X implies Y

. Extension: X extends Y X can be caused by Y

26
Unified Modeling Language (UML)
Use case diagram (example)

Management of orders for store X

Log in

includes Send
Order
includes includes
Commander Seller
Prepare
Client extends includes Order

Add a
product Payer

27
Unified Modeling Language (UML)

Collaboration diagram

Definitions
o Diagram of objects and actors 1: message
with sending messages Object 1 Object 2
o Order of interaction (arrows
numbered)
2: message
Why?
o Describe the interactions and the links
among the objects making up the
système. Object 3

28
Unified Modeling Language (UML)

Collaboration diagram (example)

Submit CV
Cabinet
recruitment
Person in
research 3: Propose Candidate
employment

5: Pass the interview

2: Propose Position
4: To summon

Company

29
Unified Modeling Language (UML)

Sequence diagram

Chronological representation of
message exchanges between the
different objects of the system. System
Describe the sequence of interactions between
Actor 1 Actor 2
the system and its actors.
Message1()

The objects are columns of the Message2()

diagram.
Message3()
Arrow between two objects: message.
Rectangular bands: periods Message4()
of the activity of objects.
Chronology of interactions: from above
down.

30
Unified Modeling Language (UML)
Sequence Diagram
Company system
Bank
aerial
Client
Enter destination (departure, arrival, date)

List of possible flights

Choose outbound flight

Choose return flight

Show total price

Enter client (identity, passport number)

Enter credit card (number, validity, code)

Card debit request

Debit confirmation

Reservation confirmed
Display flight ticket

31
8QLILHG
0RGHOLQJ
/DQJXDJH
80/

7KHSURFHVV
DSSURDFK
ZLWK
80/
8VHFDVHGLDJUDPV
R ,QWHUDFWLRQ
VLWXDWLRQ
EHWZHHQ
V\VWHPDQG
DFWRUV
R )XQFWLRQDO
VFHQDULRV
R 5HIHUHQFH
LQWKH
GHYHORSPHQW
F\FOH
IURP UHTXLUHPHQWV
WR
WHVWLQJ
R 8VHFDVHGLDJUDP
RYHUYLHZ
RILQWHUDFWLRQV

,QWHUDFWLRQ
GLDJUDPV
R &DVH
VFHQDULRV
LQWHUDFWLRQV
EHWZHHQ
REMHFWV
R 6HTXHQFH
GLDJUDP
WHPSRUDO
LQWHUDFWLRQ

$FWLYLW\
GLDJUDPV
R 6LPSOLILHG
VWDWHWUDQVLWLRQ
GLDJUDP
IORZ EHWZHHQ
DFWLYLWLHV
R (TXLYDOHQW
WR
WKH
027 RI0(5,6(
Unified Modeling Language (UML)
Activity diagram
(example)

33
 Unified Modeling Language (UML)
Insert card

Activity diagram (example)

Enter code
Invalid code

Activity diagram modeling the operation Cancellation

Valid code
from a banking terminal: Choose operation

. Insert map...
Enter amount
. Enter amount
Choose account
. …
Request
withdrawal authorization

unauthorized

authorized

Distribute tickets

Restore
map

34
Unified Modeling Language (UML)
State-transition diagram

Describe the dynamic aspects of the objects in a system (behavior of

objects).

Event 1 Event 2
State 1 State 2

State
Initial state Final state
intermediate

35
Unified Modeling Language (UML)
State Transition Diagram

Describe the dynamic aspects of the objects in a system (behavior of

objects).

36
UML and Processes

The business dimension of the process

. No separation between business/technical (System / subsystem?)

. Use case: scenario
. Activity diagram

Points of view
. Everything is an object

. No organizational view, resources...

37
BPMN: a process-oriented standard

Standard language to graphically model any type of process.

BPMI (Business Process Management Initiative) initiative then supported by
the OMG (Object Management Group).
A standard notation easily understandable by users:
. Business analysts who create and refine processes.
. Developers who implement the processes.
. Directors who follow and manage the processes
. External speakers, etc.

Sequence flow
Activity
Sequence flow
Event Event
at the beginning of end

38
BPMN: Graphical representation

Flow objects
. Task, connection, event

Connection objects
activity chains, messages and associations

Grouping (pool) and lines (swimlanes)

. The groups define a process scope and can be divided
in 'lines' (actors, organizational boundaries)
. A series of activities cannot take place between 2 groupings.
. a message can only be between 2 groupings.
. Orchestration = internal sequences within a grouping (process)
. Choreography = communications between processes

Artefacts
. data objects, groups, annotations.
BPMN: Graphic representation

Graphical representation Description

Sequence (order of activities)
Message (between two processes)
Association (data flow...)
Gateway (connection)

Activity

Sub-process
+
BPMN: Example

41
BPMN: Example

42
 BPMN: Exercise

The applicant wishing to obtain a blue card must apply to the

Bank. The blue card is not accepted if the applicant is not a client of the
bank. Every day, the bank forwards its customers' credit card requests to
Card Management Center. As soon as the bank has received the credit card in
origin of the credit card management center, it sends the customer a notice of
annual membership fee deduction. If after two months the credit card has not been
retired, it is destroyed.

Work to be done: Represent this use case with a BPMN diagram.

43
BPMN and process

The business dimension of the process

. A mixed business/technical model

Viewpoints
. Processes/functions

Advantages of the BPMN standard

. Clear and visual notation
. Automatable common format
. Understandable formalism even for external stakeholders
. Reference notation

44
Thank you for your
attention!

45