Systèmes d'Information - Concepts et Composants

Tanguy Giton Profile

• Tanguy Giton is an ESIEA 2018 alumnus.
• He holds a Master's degree in Project & Program Management from SKEMA.
• He is a software editor for IKNO.
• He works as a freelance IT consultant.
• His email address is [email protected].

Information Systems (IS) Concepts

• An IS is an organized system designed to collect information where it originates, process this information into usable data, store it securely, make it accessible and distribute it when needed, and protect its confidentiality and integrity.
• The IS supports an organization's functions by providing necessary information.

Components of an Information System

• Users: Clients, employees, and partners.
• Applications: Examples include ERP (Enterprise Resource Planning), CRM (Customer Relationship Management), and the like.
• Infrastructure: Servers, networks, and security measures. The data is integral to the system.

The IS as a Business Value Creator

• Raw data is transformed into useful information.
• This useful information leads to business decisions.
• Feedback loops are crucial to continuously improve the process.
• Examples include personalization based on client data, predictive maintenance using IoT data, and stock optimization using analytics.

Modern Banking Information System Anatomy

• Front Office: Clients, web, mobile, agencies, and partners.
• Middle Office: Control, risks, fraud, and limits.
• Back Office: Processing, accounting, treasury, reporting and batch processing.
• Central Data: Clients, Accounts, Transactions, critical information.

Information Flows in a Modern IS

• Sources of data include clients, partners, internal systems (IoT/sensors), etc.
• Data is processed using APIs (Application Programming Interfaces) and real-time or batch processing.
• Processed data is stored in operational databases (bases opératonnelles), data warehouses and lakes.
• Processed data is analysed.
• The results are used, and reports disseminated via dashboards.

IS Challenges in 2024

• Legacy Systems: Monolithic applications, on-premise infrastructure, long development cycles, and siloed teams. These present maintenance, cost, and rigidity challenges.
• Transformational Systems: Hybrid cloud approaches, Agile/DevOps, APIs, and microservices address legacy issues but create their own challenges (time to market, cloud and hybrid integration, cybersecurity, and FinOps).
• Digital Systems: Cloud-native, serverless, event-driven architectures, and AI-driven solutions (IA, edge computing, green IT, and attracting talent). The future of IS in 2024 revolves around these elements.

System Modernization Principles and Methods

• Strategy: The foundation for all IS modernization. Involves alignment of business goals with business processes
• Business Processes: Operational processes support strategic goals.
• Functional Mapping: Shows how IT supports business goals through functions.
• Application Architecture: Applications are tailored to support processes and business goals.
• Technical Infrastructure: The technical backbone to ensure smooth operation of the entire systems

Evolution of Software Architecture

• 1990s: Spaghetti-oriented architecture (copy and paste)
• 2000s: Lasagna-oriented architecture (layered monoliths)
• 2010s: Ravioli-oriented architecture (microservices)
• The current and future possibilities suggest a pizza-oriented approach

Monolithic Applications

• A single, large application containing all functionality.
• Tight coupling of functions.
• Rules are scattered in code.

Layered Monolithic Applications

• Design patterns are utilized.
• Object-oriented languages are employed.
• Responsibilities are separated.
• Rules are centralized.

Micro-service Applications

• Independent functionalities.
• Different technologies can coexist in a single application.
• Loose coupling between services.
• Defined data formats.

IS Modernization Methodology

• AS-IS Mapping: Current state assessment, Documenting the current processes, data, and applications.
• TO-BE Definition: Defining the desired future state, focusing on architecture, service, and governance.
• Analysis Phase: Identifying weaknesses, opportunities, and constraints. This includes prioritizing changes, estimating the effort and time needed, and determining realistic schedules, and potentially the cost of implementation.
• Convergence Plan: Creating a roadmap with projects, planning for time to market, quick wins (low-hanging fruit), and financial budgeting. This plan should consider critical elements and the organizational aspects of change management.