Introduction Architecture des Systèmes d'Information PDF

# Architecture des Systèmes d'Information ## 2025-2025 - ESIEA - 4ème année ## Tanguy GITON - ESIEA Alumni - Promo 2018 - SKEMA - Ms Project & Program Management - CTO - IKNO - software editor - Freelance IT consultant - [email protected] ## Système d'Information A system organized to:...

# Architecture des Systèmes d'Information ## 2025-2025 - ESIEA - 4ème année ## Tanguy GITON - ESIEA Alumni - Promo 2018 - SKEMA - Ms Project & Program Management - CTO - IKNO - software editor - Freelance IT consultant - [email protected] ## Système d'Information A system organized to: - **Collect**: capture information where it originates - **Process**: transform data into useful information - **Store**: store information in a secure and accessible manner - **Disseminate**: make the right information available at the right time - **Protect**: ensure confidentiality and integrity The information necessary for the operation of the business. ### System Components - **Users:** Clients, Employees, Partners - **Applications:** ERM, CRM, Business - **Infrastructure:** Servers, Networks, Security - **Business Processes:** Sales, Production, Support - **Data:** References, Transactions, Documents ## Le SI, Créateur de Valeur Business - **Business:** Goals, Strategy - **Data:** Raw data, Useful information, Decisions, Business choices **Examples:** - Customer data -> Personalization - Data IoT -> Predictive maintenance - Analytics -> Stock optimization ## Anatomie d'un SI Bancaire Moderne - **Front Office:** Clients (Web, Mobile, Agency, Partners) - **Middle Office:** Control (Risk, Fraud, Limits) -> API Gateway -> Services - **Back Office:** Processing (Accounting, Treasury, Reporting) -> Batch **Characteristics:** - Organization in functional areas - Specific constraints per functional area - Data criticality **Centralized Data:** Clients, Accounts, Transactions ## Les Flux d'Information dans le SI Moderne - **Data Sources:** Clients, Partners, Internal, IoT/Sensors - **Processing:** API Gateway (real-time), Batch Processing, Stream Processing - **Storage:** Operational Base, Data Warehouse, Data Lake - **Usage:** KPIs, Tableu de bord (BI), Analytics (ML/AI), Applications ## Enjeux des SI en 2024 **Past (Legacy):** - Monolithic applications - On-premise infrastructure - Long cycles - Siloed teams **Present (Transformation):** - Coexistence old and new - Hybrid Cloud - Agility/DevOps - APIs/Microservices **Future (Digital):** - Cloud-native - Serverless - Event-Driven ### Key Issues **Past:** - Maintenance - Cost - Rigidity **Present:** - Time to Market - Cloud & Hybridization - Cybersecurity - FinOps **Future:** - AI - Edge Computing - Green IT - Talents ## Urbanisation des SI - Principes et Méthode - **Strategy** - **Business Process** - **Functional Mapping** - **Application Architecture** - **Technical Infrastructure** **System Elements:** - **Data Flow** - **Functional Areas** - **Applications** - **Infrastructure** **Illustration:** - Real World - Land Usage - Services - Parcels - Streets - Customers ## Méthode d'Urbanisation **1. AS-IS Mapping:** - Define processes - Identify data - List applications **2. Analysis:** - Identify weaknesses - Discover opportunities - Gather constraints **3. TO-BE Target:** - Design architecture - Define services - Organize governance **4. Convergence Plan:** - Set trajectory - Plan projects - Identify Quick Wins **Tools:** - Documentation - Interview - Analysis - Diagnostics - Prioritization - Roadmap - Vision - Standard - Guidelines - Planning - Budget - Organization ## Architecture logicielle ### The Evolution of Software Architecture - **1990s**: Spaghetti-oriented architecture (aka Copy & Paste) - **2000s**: Lasagna-oriented architecture (aka Layered Monolith) - **2010s**: Ravioli-oriented architecture (aka Microservices) - **Next**: Pizza-oriented architecture? ## Application monolithique - One page = one file - Tight coupling of functionalities - Business rules dispersed in the code **What are the drawbacks?** ## Application monolithique en couches - Use Design Patterns - Object-oriented language - Separation of responsibilities - Centralization of business rules **What are the limitations?** **Examples of Design Patterns?** ## Application en micro-services - Each functionality is independent - Different technologies coexist within the same application - Loose coupling based on defined data format **What are the advantages? What are the organizational constraints?** ## Monolith to Microservices Evolution - **2010s:** Monolith application - **2015s:** API gateway with monolith backend - **2020s:** End-to-end feature stack with microservices **Empowered Product Teams:** Engineering, product, design, data, QA **Source:** @benorama