Scribd
Upload
5 views4 pages

Chapter IV-Part 1 - 2

Chapter IV outlines the methodology for developing an information system (IS) using the MERISE method, detailing the structured activities involved in the IS development process, including requirement specification, design, implementation, testing, installation, and maintenance. It describes the software life cycle and various IS development models, emphasizing the advantages of MERISE, which provides a comprehensive approach to data and processes with standardized formalism. The chapter also highlights the three levels of abstraction in MERISE—conceptual, organizational, and operational—along with a phased breakdown of the project into preliminary study, detailed study, implementation, deployment, and maintenance.

Uploaded by

katiavilma97
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
5 views4 pages

Chapter IV-Part 1 - 2

Chapter IV outlines the methodology for developing an information system (IS) using the MERISE method, detailing the structured activities involved in the IS development process, including requirement specification, design, implementation, testing, installation, and maintenance. It describes the software life cycle and various IS development models, emphasizing the advantages of MERISE, which provides a comprehensive approach to data and processes with standardized formalism. The chapter also highlights the three levels of abstraction in MERISE—conceptual, organizational, and operational—along with a phased breakdown of the project into preliminary study, detailed study, implementation, deployment, and maintenance.

Uploaded by

katiavilma97
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Chapter IV: Methodology for Developing an Information System (MERISE)

1. Information System Development Process

The development process of an information system (IS) is a structured set of activities aimed at achieving
the objectives of an IS project defined by the organization. These activities vary according to the type of
organization, the type of project, and the type of system to be developed. This process must be clearly
described in order to be properly managed.

2. Software Life Cycle


The life cycle of an information system (IS) succinctly describes the phases through which an
information system goes, from the initial need to the system's retirement.

3. IS Development Activities
The development of an information system (IS) involves several activities that vary depending on the
type of project and the organization. The essential activities include:

 Specification of system requirements and constraints, and the preparation of a requirements


document
 Design of the solution, including the creation of a model for the system to be developed
 Implementation of the system
 System testing, to verify the alignment between the system's implemented properties and the
specified requirements
 System installation at the client's site and verification of its proper functioning
 System maintenance, including fault repair

4. IS Development Models
There are various models used for software development. These models aim to implement the
development activities mentioned above with a certain level of organization among these activities. The
most well-known models include the Waterfall model, the V-model, the Spiral model, and the
Incremental model. The application of these models often involves the use of an analysis and design
method. Each method has its advantages and disadvantages and is suited to a specific type of project
(industrial, management, scientific, etc.). Some of the existing methods include MERISE, SADT,
SART, OMT, and UML (although UML is not a method but a unified modeling language).

5. The MERISE Method (in French Méthode d'Étude et de Réalisation Informatique


pour les Systèmes d'Entreprise)
MERISE is a systemic method that emerged in 1979 following a project initiated in 1977 by the French
Ministry of Industry. The goal was to provide companies with a design method that would enable them
to successfully complete their IT projects within the planned budget and timeline.

5.1. Characteristics of Merise


The major advantages of Merise are:

1. A comprehensive approach to the IS conducted simultaneously on data and processes.


2. A description of the IS using a simple and rigorous formalism standardized by ISO for data
representation (Entity-Relationship Model).
3. Separation of data and processes.

5.2. Levels of Abstraction in Merise

5.2.1. Conceptual Level


The conceptual level aims to answer the question WHAT? In other words, what needs to be done and with
what data, without considering work organization or the hardware used. The two resulting models at this
level are:

 Conceptual Data Model (CDM)


 Conceptual Process Model (CPM)

5.2.2. Organizational Level


The organizational level seeks to answer the questions WHO? WHERE? and WHEN? At this level, the
organizational criteria of work are integrated. It considers (or proposes) the distribution of processes
between humans and machines, as well as the mode of operation (real-time, batch processing). The
resulting models at this level are:
 Logical Data Model (LDM)
 Organizational Process Model (OPM)

5.2.3. Operational (Physical) Level


This level focuses on implementing the results of technical decisions based on objectives and technical
constraints. It answers the question HOW?
At this stage, technical solutions are studied (e.g., data storage methods, program segmentation for
processes). The resulting models at this level are:

 Physical Data Model (PDM)


 Physical Process Model (PPM)

The levels of abstraction and their resulting models are summarized in the following table:

LEVEL DATA TREATMENTS


Conceptual Conceptual Data Model Conceptual Model of
(CDM)
Management choice: What? Treatments (CTM)

Organizational Logical Data Model (LDM) Organizational Model of


Organizational choice: Treatments (OMT)
Who? Where? When?
Physical Physical Data Model (PDM) Physical Model of Treatments
Technical choices: How? (PMT)

5.3. Phased Breakdown


MERISE recommends dividing the project into four phases. This division is not specific to the Merise
method but is generally advised for the execution of any IT project. Each phase corresponds to a level
of abstraction. The phases are as follows:

1. Preliminary Study / Master Plan


2. Detailed Study
3. Implementation
4. Deployment
5. Maintenance
Breakdown of the MERISE method into stages
Master plan / Preliminary study (study of the existing)
Detailed study (in parallel by two teams if possible)
CDM: Conceptual Data Model

CTM: Conceptual Treatment Model OMT: Organizational Model of


Treatment
External views / Validation
MLD: Logical Data Model
Realization(together)
PDM: Physical Data Model
PMT: Physical Model of Treatment
Implementation
Maintenance

You might also like