Chapter 3: the MERISE method

Iman EL MIR
[Link]@[Link]

A.U: 2019/2020
Contents of the chapter
General introduction to the MERISE method
The advantages and disadvantages of MERISE
The MERISE approach (life cycle of an IS)
Levels of abstraction
The MERISE models

2
Introduction

The study methods of information systems aim to

the objective is to describe these systems using models, then to
realize the computerized systems that result from it. MERISE
is one of these methods.
MERISE: Method of Study and Computer Implementation
Enterprise Systems

3
The MERISE method

MERISE is a method that allows for the construction of a system

automated information that is effective, flexible, and tailored to
the company. It is a method that was born in 1976.

4
The MERISE method
MERISE is an analysis method specifically designed for
management information systems. Managing information technology a
The company consists of computerizing representation as much as possible.
often in the form of databases and software of
management, the company's information system.
The information system is the set of data and of
treatments that are important for management of
the company.
Data can be, for example, information about the
clients, on the products sold or manufactured, on the employees of
the company, etc... This data is generally stored in
one (or more) database(s).

5
The MERISE method
The treatments consist of updating the (or the)
databases based on events
producing in the life of the company.
MERISE allows for both data modeling and
the treatments of an information system, from a point
from a conceptual point of view.

In this course, we introduce the model

conceptual data, which must ultimately lead to
the design of a company database.

6
MERISE: The strengths
The method is based on a systemic approach: it is therefore
a global approach.
It is highly suited for large computerization projects.
of SI.
The concepts are few and simple.
She is very independent with regard to technology.
It remains a de facto standard in French-speaking countries in
the fields of management.
It serves as a reference for teachings on methods.

7
MERISE: the weaknesses
She doesn't take care of the user interface.
It is very suitable for an application development context.
but not necessarily to a maintenance problem or to
second computerization.
It does not allow for quick validation from the
users.
It is more intended for central sites rather than for
real-time developments, or on computer.
It is very difficult to validate treatments in relation to the
data and this at the conceptual or organizational level.

8
So why MERISE?
Today, three poles must be distinguished in the design of
Information systems:
Business processes
The software
The databases
If software design is dominated by object-oriented
UML-based methods), databases remain they
strongly relational.
Moreover, database design is becoming increasingly
en plusindépendantede la conception du logiciel.

9
What to do then?

A blend of the two: an approach based on methods

traditional, such as MERISE for the conceptual aspect, and
more modern, like UML for producing prototypes,
is a favorable compromise for application design
informatics.

10
The components of MERISE
Models (concepts, representation rules)
A language (vocabulary, syntax rules)
An approach
Tools (software such as AMC Designor, Win Design,
AnalyseSI)
They allow to represent the components of an IS (the
actors, the data, the processes, the procedures, the positions
of work, etc.)
This is to design, implement and set up a
new computerization.

11
 The ongoing validation of the study by individuals
concerned ensures that the system in progress
of construction in accordance with the objectives. If we do not
not following the validation steps may risk
produce applications far from the initial demand
what is called 'the tunnel effect'. Not to mention that
the developed applications are intended for
users and not at the pleasure of IT professionals.

12
Basic Principles of Merise
From abstraction to the realization of a System
information, we will have to observe under several
perspectives on the organization we are studying.
These angles of view are called cycles.
MERISE presents in its analysis approach three
fundamental cycles:
. the cycle of abstraction,
. the life cycle
. the decision cycle.

13
 The MERISE approach (life cycle of an IS)
Global approach to IS Master Plan
Study of the different possible solutions and then choice Preliminary study
Supplement of domain specifications (file of Detailed study
functional specifications or specifications document
users)
Complete technical specifications (file of Technical study
technical specifications or specifications document of
realization)
Writing programs Software production
Tests, trials, user training Commissioning
Corrections and adaptations of the software Maintenance
Conformity control of results with respect to Quality control,
requests recipe

14
Master Plan
Global study of the Information System: Division into areas

Buts:
Define the major political and strategic directions of
the company
Define the information system needs according to the company's strategy
Set the budgetary frameworks, the strategy for staffing needs
and the various constraints related to the environment
Set the guidelines for IT developments
Define the necessary projects for the development or evolution of the IS.
Produced documents:
The master plan
The IT development plan

15
Preliminary study
Behave
A critical analysis of the existing system (physical, organizational,
conceptual)
The objectives of the new system (conceptual, organizational),
Les différents scénarios de solutions informatiques,
An assessment of the costs and means required,
A plan for implementation
Translated
Through a preliminary study file or selection file.
About it
By the choice of a solution by management.

16
Detailed study
Permit
To specify the detailed organization of the chosen solution,
To logically define data and computer processes
of the solution,
To define the interfaces: screens, exit states,
To build the implementation schedule.
This translates to
A specifications document for the application (contract regarding the
users),
A detailed study file for analyst-programmers,
A specifications document for hardware/software for a call for tenders.

17
Detailed study: design
Two phases follow one another during the design:
The general design providing a complete description of the future
information system
General design file
The detailed design providing a complete description (and
verified) of the future information system in the environment
target
Detailed Design Document

18
The Technical Study
Make
The technical specification (physical level):
Physical structure of data
Decomposition of the application into programs
Draw screens and output states
The production of programs
Provides
Technical documentation (program maintenance)
A user documentation (application user manual)
Operating manual for the operations service on large sites
informatics).

19
Software production
She describes a project in a form interpretable by the
machine.
She understands:
The generation of files or databases
Writing programs
The development tests.

20
The MERISE method
The treatments consist of updating the (or the)
databases based on events
producing in the life of the company.
MERISE allows for both data modeling and
the treatments of an information system, from a point
from a conceptual point of view.

In this course, we introduce the model

conceptual data, which must ultimately lead to
the design of a company database.

6
The maintenance
Maintenance of SI which consists of adapting to the changes of
the environment: correction of anomalies, improvements,
evolutions.
It is the consideration of the developments that appear after the
operational launch.
It includes:
The study of the impact of changes
The specification of modifications
The realization
The commissioning
It can sometimes lead to a reassessment of the solution.
previously set up.

22
The global life cycle of Merise

23
Data-Processing-Flow
The MERISE method is based on the separation of data and
treatments to be carried out:
On dirastatiqueen parlant des données etdynamique pour les
treatments.
The MERISE method also deals with the information flows of the IS.

24
The levels of abstraction

LEVEL DATA TREATMENT

Conceptual MCD MCT

Conceptual Model of Conceptual Model of
Data Treatments

Organizational MLD MOT

Logical Model of Organizational Model of
Data Treatments

Physique MPD MOPT

Physical Model of Operational Model of
Data Treatments

25
MERISE Method: Conceptual Level
Answer to the question: WHAT?

What are we going to manage? What are we going to achieve?

as data, how as treatment
Are they organized?

Conceptual Model Conceptual Model of

of Data (MCD) Traitements (MCT)

The semantic definition of -Recognition of

data allows understanding fundamental treatments
complete information highlights the objectives of
system
26
MERISE Method: Logical Level
Réponse à la question:QUI ? QUAND ? OU ?

System description, Independent description

regardless of the software of the machine
DBMS Structuring into procedure
Automatic passage to
relational model

Logical Model of Logical Model of

Data (MLD) Treatments (MLT)

Validation and Optimization of the LDM in relation to the treatments

27
MERISE Method: Physical Level
Réponse à la question :COMMENT ?,AVEC QUOI

Internal description of data Description of the architecture

depending on the DBMS software treatments
Definition of constraints Detailed specifications of the
access structures, etc.. programming (Algorithms)

Physical Model of Physical Model of

Data (MPD) Treatments (MPT)

28
 The levels of abstraction
LEVEL QUESTION PROCESSING DOMAIN
Conceptual What to do? manipulated data Management
management rules
sequence of treatments
Organizational Who does what? - sharing of tasksOrganisation
When? - treatment mode
Where? geographical distribution of
treatments
data organization
Physics How? -programs Technique
software
materials

29
The MERISE models
Data Treatments Flux

MCD meaning of MCT activity of

MCF : relationships
information without domain without specifying the
between the domain
and the
technical constraints or resources or their remaining of the SI
economic organization

MOD meaning of MOT operation

information with of the domain with the MOF : relations
technical constraints or resources used and their among the actors
economic organization

MLT operation of the

MLD description of
domain with the MLF : relations
data taking into account
resources used and their between the systems
their conditions and of
organisation IT
memory techniques
computer science
MPD description of where MPT Architecture
MPF : supports
of BD in the syntax of technique of
flow techniques
SGF or DBMS programs

30
Merise level models

31
Conclusion
The learning of Merise, like that of any other
method can only be done through practice. This
practice must also be done through
of Software Engineering Workshops (AGL) that constitute
a true help for the designer. These AGL do not
do not replace man and require from him
de ceux qui les utilisent, une connaissance suffisante
of the method.

32