Merise Method for Process Modeling
Merise Method for Process Modeling
MERISE -> study and realization method for enterprise systems, design method
information system and software project development
Provides complete separation of data and processes
Data: static aspect / Processing: dynamic aspect
Approach in 3 axes -> in 3 cycles
o1- life cycle -> breaking down the development process into a certain number of steps
o2- decision cycle -> linked to the life cycle as it defines the results to be produced at the end of each stage an
deadlines imperatives
o3- abstraction cycle -> is based on perception at 3 levels of the company to take into account the fact
that IT maintenance does not necessarily require questioning the entire system
models and depending on the type of problem to be solved, one can intervene at 3 levels:
1) Conceptual level -> definition of the business objectives described by management rules.
répond aux 2 questons : Quoi ? et Pourquoi ?
2) Organizational level (or logical level) -> take into account the state of the art technology
(advanced) and the actors and their constraints > deduce the organization that needs to be implemented
To achieve the targeted objectives: When? Who? and Where?
3) Physical level (or operational level) -> implement the technical tools of
Software development: How to do it?
Each of the 3 levels will correspond to either 2 or 3 models:
A data model, processing, flow for levels 1 and 2
A data model, processing for level 3
Conceptual Level
Conceptual level 1 -> conceptual model of flow: MCF
Conceptual level 2 -> conceptual data model: CDM
Conceptual level 3 -> conceptual processing model: CPM
Organizational Level
Organizational level 1 -> flow organizational model: MOF
Organizational level 2 -> logical data model: LDM
Organizational level 3 -> organizational processing model: MOT
Physical level
Physical level 1 -> physical data model: PDM
Physical level 2 -> operational processing model: MOPT
We start by creating the MCF and, in parallel, a share of the raw MCD and on the other hand the MCT. We will then continue
compare the raw conceptual data model (MCD) with the object model (MOT) to verify if there are no unnecessary data in the treatments in the MCD
or conversely, if it will not lack essential data.
When the modifications have been made, we obtain the validated MCD, then we develop the MLD and in parallel the
MPD and the MOPT.
In the MERISE method: describing treatment means describing the processes. This description involves the realization of
MCF, of the MCT and of the MOT.
Exercise 3:
Regulation
Management of the
Client Invoice invoicing
Purchase order
Delivered products
Good delivery
Delivery completed
Delivery management
Level 1 MCF
Decompose the studied domain into a number of activities
We then connect each of the flows to one of the activities and potentially add additional flows.
interns between activities
Activity -> rectangular shape
C. The conceptual model of processing
The processes describe the activities to be carried out on the data to obtain the expected results.
the company.
They are only the active translation of the management rules that make up the company's activity.
An order is only fulfilled if the quantity in stock is greater than or equal to the quantity.
requested. This rule translates into 4 actions:
Enter the requested quantity
2- Compare the ordered quantity with the quantity in stock
3- If the quantity ordered is greater than the quantity in stock, then the order is rejected.
If the ordered quantity is less than or equal to the quantity in stock, then we record the order.
The MCT is the model that allows representing all the actions taken by the company to achieve these.
objectfs.
A process involves a significant number of features that we group into larger sets.
elementary operations that we qualify as operations. Each operation constitutes a sequence of actions executed
without interruption. An operation is triggered to respond to a request for one/multiple
elements and produce one/multiple results conditioned by [...]
3 concept -> l’évènement
th
The event is a new fact for the information system which will react with: several
repeated actions can be internal, external, or temporal.
4ème concept -> la synchronisaton
It is a condition for executing an operation, its symbol always appears before an operation.
but it only includes elements when multiple events trigger the initiation of
the operation.
When there are several triggering events, the synchronization indicates how the event
they combine with each other, each event is assigned a letter and we express the operations.
5ththe results
An operation can generate one or several results that are potentially produced based on
qualified emission rules. If there are no emission rules, the label is entered in place.
always.
Deposit
file 14
OP1
Reception folder
Always
File
examinable 15 juin
(B)
A and B
OP2
Exam file
Sufficient file Insufficient file
Student Student
Admission not admitted
Exercise 5:
The text
OP1
Stock verification
OP2
Verification of pending order
Nothing to do Order
Reminder sent exceptional
to the supplier carried out
Order
canceled
possibilities:
o1ermanual: a process in which computing is not used at all
o2th-> interactf: all processes where a computer is used but on the condition that there is a
dialogue man-machine via the keyboard and mouse either to enter new data or to
query the database
o3 -> automatic: these are collective processes, referred to as batch processing or
th
batch processing, which is generally carried out in deferred mode without any human intervention, except
possibly the triggering, based on data already contained in the system
information. This type of processing always corresponds to a workstation that is named
computer
3thConcept: realization procedure -> It corresponds to the temporal conditions for the realization of a
activity. It can either be a time period or a frequency
4thConcept: the functional procedure -> It corresponds to a set of actions performed without
interruption by the same workstation during a well-defined period and with means of
treatments of a single type. It is represented exactly in the same way as an MCT operation,
the numbering simply starts with PF (functional procedure). The WORD will therefore correspond to a
sequence of functional procedures that will be represented in a table. In this table there is
always a first column corresponding to the period of realization and then there are as many columns
What workstations are involved in the process and finally there is always a type of processing column.
Each functional procedure must be placed in the column corresponding to the workstation.
that he executes. It must correspond to a period and a type of treatment. A workstation
It is something that is internal to the organization for which we are making the model.
Cf. photo: shape of the WORD
Its purpose is to show all the possibilities of interaction between the system and actors; It
therefore determine all the functionalities that the system will have to provide. We first represent some
use case.
A use case is represented in an oval shape; it corresponds to a need for interaction with the
system from the user's perspective. We also represent actors that correspond to
typical users who will always have the same behavior with respect to the use case. The same
An individual can correspond to several different actors depending on the role they will play in relation to the system.
We identify 2 types of actors:
the physical person that we represent via a stickman
Organizational roles of computers that are represented in a rectangular form.
We also have interactions that are represented as a line indicating that the actor participates in
the use.
Example: We consider a bank's ATM that allows cash withdrawals, cash deposits, and the
Consultation of account information.
Withdraw money
Cardholder
Deposit money
Consult
informations
of the account
Bank client
It is possible to define relationships between use cases that may eventually allow for their reuse.
there are 3 different relationships:
- The extension relationship, a use case A is a use case B if case A can be executed in
Course of the execution of B. It is therefore an optional relationship that often only occurs under a certain
condition. It is represented by a dotted arrow labeled 'extend' that goes from the case
extended towards the departure cases;
Example: In the case of a cash withdrawal, there is a balance verification if the withdrawal exceeds €30.
If amount > 30 €
Withdraw money
extend
Cardholder
Check the balance Deposit money
Consult
informations
of the account
- The inclusion relationship. We say that an use case A includes a use case B if the execution of A leads to
automatically the execution of B. This relationship is represented by a dotted arrow on which is
inscribed "include" and oriented from the including case to the included case.
-
-
- If amount > 30 €
-
- Withdraw money
extend
-
Check the balance
Cardholder
- Deposit money
includ include
Consult
Identify include information
of the account
Retrieving dollar
Return Euro
If amount > 30 €
-
-
extend Withdraw money
- balance
Check the
Cardholder
- Deposit money
include
include
Consult
To identify information
include of the account
B. The sequence diagram
Its purpose is to represent the interactions between objects involved in a use case by indicating the
Chronology of exchanges. All the actors identified in relation to a CU will therefore be found in the diagram.
of sequence corresponding to this CU. A sequence diagram is read from top to bottom, it formalizes all exchanges
qualified messages that occur between actors or objects. There are synchronous messages for which the sender
await the receiver's response to continue its actions. And asynchronous messages for which the sender
continues its actions without waiting for a response, which means that the recipient can reply at any time or then
ignore the message. Messages can sometimes be reflexive if they concern the same actor or
the same object. The order of sending a message is determined based on its position on the vertical axis of the diagram
that is referred to as a lifeline. The diagram also represents through rectangular shapes the
period of activity of different objects or different actors.
C. Activity diagram
Allows for the representation of activities that describe the execution of functionality or behavior, each activity
is composed of a certain number of actions that we will represent sequentially between a start and
une/plusieurs fins et en les reliant par des transitons. A l’issue d’une acton il est possible qu’il y ai plusieurs choix
possible, in this hypothesis we use a decision. It may happen that an action is only possible when
several other actions are completed and we formalize this through a synchronization bar. We use
this same synchronization bar to express the fact that the end of one action triggers several others. There
Two possible forms for this activity diagram: in its simplest form, only the actions are represented.
carried out by the organization for which we are making the diagram, and in its most complete form that we qualify as
activity diagram with lane identifies all the actors involved in the process whether internal or
external and we represent all their respective activities.
Start
Acton
Transiton
Decision
Synchronization
End
The MCT's construction rules are designed to establish a sequence for operations that must proceed without interruption. As such, interruptions between actions of significant duration lead to a segmentation of the operation. For instance, an operation cannot be interrupted by the intervention of an external actor, to maintain internal continuity. This ensures a rational breakdown of operations where only homogenous treatments are grouped, preventing intermediary results from halting operational progress .
The MCF in its level 0, known as the context model, highlights exchanges between a studied management domain and external stakeholders through distinct shapes. External actors are represented by oval shapes, while the studied domain and related areas are shown as rectangular shapes. The model identifies two types of flows: those related to the studied domain represented by solid arrows, and those that do not directly involve the external actors or the related domain, represented by a dotted line .
Sequence diagrams are significant because they show the interactions between objects in a use case by indicating the order of message exchanges and the chronology of events. These diagrams are read from top to bottom, displaying the interaction flow between actors or objects with messages marked on a vertical lifeline. They distinguish between synchronous (await for response) and asynchronous (continue without waiting) messages, providing a visual depiction of how processes are executed over time and aiding in understanding the sequence of operations .
Operations from the MCT can be translated into the MOT through three possibilities: as a single functional procedure when actions are performed by the same workstation in real-time, as multiple functional procedures if different workstations are involved or treatments are automated or deferred, and rarely as a single functional procedure if operations concern the same workstation and are minimal. The factors guiding this translation include the number and type of workstations, automation levels, and the complexity of operations .
Synchronization is a condition necessary for executing an operation within the MCF. It involves multiple triggering events that determine the start of an operation. Synchronization indicates how events are combined and the sequence in which operations are executed. Each event is assigned a letter, and operations are expressed by these combinations, ensuring they're only initiated when specific synchronicities are met .
The process conceptual model describes the activities necessary to process data to achieve desired results in a company. These processes translate management rules into actions that form the company's operations. For example, an order is only fulfilled if the stock quantity is sufficient. This rule is operationalized by four actions: entering the requested quantity, comparing it with the stock, rejecting the order if stock is insufficient, or recording the order if it is adequate .
In a UML use case diagram, use cases are represented using oval shapes indicating system interactions from a user's perspective, while actors, which can be individuals or roles, are depicted as stick figures or rectangular forms for organizational roles. Interactions are shown with lines connecting actors and use cases. These diagrams detail the functionalities the system provides by mapping actor-system interactions and highlighting different ways the system can be utilized, such as through extension, inclusion, and generalization relationships between use cases .
UML diagrams, including static and dynamic diagrams, are used in process modeling to provide various views of system interactions. Static diagrams represent the system's physical structure, while dynamic diagrams illustrate system functionality and interactions over time, like sequence diagrams showing message exchanges and activity diagrams depicting process flows. These diagrams help in visualizing system processes, interactions among components, and the overall functional setup, promoting a comprehensive understanding of how the system operates .
The WORD describes the organization necessary for executing treatments detailed by the MCT. Unlike the MCT, which focuses on treatment processes themselves, the WORD addresses who performs the treatments (workstation), how they are implemented (type of automation), and when (time period). It answers key questions about the execution of processes by situating them in a broader organizational and procedural framework .
The organizational model defines three processing types: manual (no computing), interactive (computer-assisted with human interaction), and automatic (batch processing without human intervention). Manual processes involve no automation, interactive processes require dialogue between human and computer via input devices, and automatic processes execute automatically on predefined schedules without manual input. The level of automation impacts efficiency, speed, and error rate, with higher automation generally offering increased process efficiency .