DSF : Modeling financial processes and information systems

Catalogue des cours de Institut Mines-Télécom Business School

Code

MGFE MIS 6201

Niveau

M2

Discipline

Systèmes d’information

Langue

Anglais/English

Crédits ECTS

3

Heures programmées

24

Charge totale étudiant

60

Coordonnateur(s)

Département

  • Data analytics, Économie et Finances

Equipe pédagogique

Introduction au module

This course introduces students to the modelling of financial processes and information systems. It focuses on the design of conceptual data models, class diagrams, state diagrams, sequence diagrams, activity diagrams and workflow models applied to financial products and front-to-back market processes. Students learn how to model financial products, generated payments, accounting automation rules, audit concepts and trading room workflows in order to support the design and implementation of financial information systems.

Bloc de compétences

  • 2. Produire et mobiliser des savoirs hautement spécialisés, issus d’une réflexion critique, et dans un champ d’expertise

Compétences du bloc

  • 2.3 - Conduire une analyse réflexive et distanciée prenant en compte les enjeux, les problématiques et la complexité d'une demande ou d'une situation afin de proposer des solutions adaptées et/ou innovantes en respect des évolutions de la règlementation.

Objectifs d'apprentissage du cours

By the end of this PGE M2 course, students will be able to:

Apply the main rules for designing conceptual data models and class diagrams to financial information system problems.
Model the structure and behaviour of a financial product by identifying its key entities, attributes, relationships and constraints.
Analyse the payments generated by a financial product and model their processing within an information system.
Design rules for the automatic generation of legal accounting entries linked to financial product events.
Explain and model the audit trail of a financial product in order to ensure traceability, control and system reliability.
Apply state, sequence and activity diagrams to represent financial product lifecycles and operational processes.
Model front-to-back processes in a trading room, from transaction initiation to processing, control, accounting and reporting.
Design workflow models that support the specification, implementation and control of financial information system processes.

Contenu : structure du module et agenda

Conceptual and Object-Oriented Modelling
1.1 Rules for designing a conceptual data model
1.2 Rules for designing a class diagram
1.3 Modelling entities, attributes, relationships and constraints
1.4 Application to a financial product currently being studied
Financial Product Modelling
2.1 Structural representation of financial products
2.2 Product events and lifecycle modelling
2.3 Payments generated by financial products
2.4 Processing of payments in financial information systems
Accounting Automation and Auditability
3.1 Rules for automatically generating legal accounting entries
3.2 Links between product events, payments and accounting treatment
3.3 Concept of auditing a financial product
3.4 Traceability, control and audit trail in financial systems
System Integration of Financial Concepts
4.1 Modelling financial product concepts for system integration
4.2 Translating business rules into system models
4.3 Aligning financial product design, processing and accounting requirements
4.4 Preparing models for implementation in financial market software packages
Dynamic Modelling Techniques
5.1 Rules for state diagrams
5.2 Rules for sequence diagrams
5.3 Rules for activity diagrams
5.4 Application to financial processes and product lifecycles
Front-to-Back Processes in Trading Rooms
6.1 Front-office, middle-office and back-office functions
6.2 Transaction initiation, validation, confirmation and settlement
6.3 Processing, control, accounting and reporting flows
6.4 Modelling front-to-back market processes
Workflow Design and Implementation
7.1 Concept of workflow
7.2 Workflow modelling for process design
7.3 Workflow modelling for system implementation
7.4 Control points, responsibilities and operational continuity

Contribution à l'atteinte des ODD (Objets du Développement Durable)

SDG 9 – Industry, Innovation and Infrastructure: This course contributes to SDG 9 by developing students’ ability to model robust financial information systems and workflows that support reliable, innovative and efficient digital infrastructure in financial organisations.

Nombre d'ODD abordés parmi les 17

1

Apprentissage

Mixte

Méthode pédagogique

The teaching approach is based on practical knowledge of financial market software packages and real-world applications of financial product design, development and implementation. The course also relies on standard front-to-back market processes to help students connect modelling techniques with operational financial systems. Students progressively apply modelling rules and diagrams to concrete financial products, payment processes, accounting automation rules and trading room workflows.

Système de notation et modalités de rattrapage

The assessment evaluates students’ ability to analyse financial product processes and translate them into structured information system models. It measures their capacity to design conceptual data models, class diagrams and dynamic diagrams, represent financial product lifecycles, model payment and accounting processes, and apply workflow modelling to front-to-back market operations.

A mark out of 20 will be awarded at the end of the course after a two-hour written examination. The examination consists of short questions and design exercises similar to those completed during the course.

Unexcused absences will result in a penalty equal to 20% of the module mark.

The second-chance assessment, CF2, consists of a written examination.

Règlement du module

1. Professor–Student Communication

The professor will communicate with students through their institutional school email address (IMT-BS/TSP) and/or the Moodle portal. No communication will be sent to personal email addresses. Students are responsible for regularly checking their IMT-BS/TSP mailbox and Moodle announcements.

Students may contact the professor by email using the professor’s institutional email address. When necessary, students may meet the professor during office hours or by appointment.

2. Students with Accommodation Needs

Students who have a disability or any specific accommodation need that may affect their ability to complete the required work must inform the professor during the first class, in order to facilitate the necessary arrangements in accordance with the school’s applicable procedures.

3. Class Attendance and Behaviour

Students are expected to attend class, arrive on time and behave respectfully throughout the session.

Unless explicitly authorised by the professor, the use of electronic devices, including computers, mobile phones and tablets, is prohibited during class. Students are not allowed to take photos, videos or audio recordings in the classroom without the professor’s explicit consent.

Students must avoid disruptive or disrespectful behaviour, including arriving late, leaving early, sleeping, reading non-course material, using inappropriate language, speaking over others, eating or drinking during class, or engaging in any behaviour that disturbs the class. A warning may be given for a first violation. Repeated violations may lead to penalties, exclusion from the class and/or disciplinary proceedings.

A delay of up to 10 minutes is tolerated at the beginning of class. Attendance will be recorded on Edusign during this 10-minute period using a QR code provided by the professor at the start of each session.

Leaving the classroom before the end of the session without the professor’s approval will be considered an absence.

In the case of remote learning, students must keep their camera on unless instructed otherwise by the professor.

4. Exams and Assessments

Students must arrive on time for exams and other assessments. A delay of up to 10 minutes is tolerated.

No student may continue the exam once the allocated time is over. No student may leave the room during an examination unless they have finished the exam and handed in all required documents.

Only the following items are allowed during exams:

pens;
student card;
a non-programmable calculator, or a programmable calculator with activated EXAM mode.

All other items are prohibited.

Possession of any unauthorised electronic device, even if turned off, will be considered cheating.

Possession of a programmable calculator without activated EXAM mode, even if turned off, will be considered cheating.

A random check may be carried out after students are instructed to activate EXAM mode. Failure to prove that EXAM mode has been activated after this instruction will be considered cheating.

Students are responsible for knowing how to activate EXAM mode on their calculator before the exam.

Any violation of the instructions given by the professor or the examination supervision team will be reported to the Discipline Committee.

Références obligatoires et lectures suggérées

Fowler, M., UML Distilled: A Brief Guide to the Standard Object Modeling Language.
Booch, G., Rumbaugh, J. and Jacobson, I., The Unified Modeling Language User Guide.
Larman, C., Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development.
Fowler, M., Analysis Patterns: Reusable Object Models.
Fowler, M., Patterns of Enterprise Application Architecture.
Gamma, E., Helm, R., Johnson, R. and Vlissides, J., Design Patterns: Elements of Reusable Object-Oriented Software.
Laguna, M. and Marklund, J., Business Process Analytics: Modeling, Simulation and Design.
Dumas, M., La Rosa, M., Mendling, J. and Reijers, H. A., Fundamentals of Business Process Management.

Mots-clés

Financial process modelling; information systems; conceptual data model; class diagram; UML; state diagram; sequence diagram; activity diagram; workflow; financial products; payment processing; accounting automation; audit trail; front-to-back process; trading room; system integration; business rules.

Prérequis

None