Introduction Architecture des systèmes d'information (1) PDF

# 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 d...

# 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:** conserve in a secure and accessible way - **Disseminate:** make the right information available at the right time - **Protect:** guarantee confidentiality and integrity Information necessary for the functioning of the company. # Les Composants d'un Système d'Information ## Users - Clients - Employees - Partners ## Applications - ERM - CRM - Métier ## Infrastructure - Servers - Networks - Security ## Process métier - Sale - Production - Support ## Data - Reference data - Transactions - Documents # Le SI, Créateur de Valeur Business ## Business - Objectives - Strategy ## Data - Raw data - Information ## Feedback - Useful information ## Decisions - Business choices ## Examples - Customer data -> Personalization - IoT data -> Predictive maintenance - Analytics -> Stock optimization # Anatomie d'un SI Bancaire Moderne ## Front office - Clients - Web - Mobile - Agency - Partners - API Gateway ## Middle office - Control - Risks - Fraud - Limits - Services ## Back office - Processing - Accounting - Treasury - Reporting - Batch - Organization by functional area - Specific constraints per functional area - Criticality of data ## Data center - Clients - Accounts - Transactions # Les Flux d'Information dans le SI Moderne ## Sources of data - Clients - Partners - Internal - IoT/Sensors ## Processing - Real-time - APIs - Batch - Stream ## Storage - Operational database - ETL - Data Warehouse - Data Lake ## Usage - KPIs - Dashboards - BI - ML/AI - Analytics - Applications # Enjeux des SI en 2024 ## Past - Legacy - Monolithic applications - On-premise infrastructure - Long cycles (V) - Siloed teams ## Present - Transformation - Coexistence of old and new - Hybrid cloud - Agility/DevOps - APIs/Microservices ## Future - Digital - Cloud native - Serverless - Event-Driven ## Challenges ### Past: - Maintenance - Costs - Rigidity ### Present: - Time to market - Cloud & hybridation - Cybersecurity - FinOps ### Future: - IA - Edge computing - Green IT - Talents # Urbanisation des SI - Principes et Méthode ## System architecture - Strategy - Business processes - Functional mapping - Application Architecture - Technical infrastructure ## City view Starting from the real world, layers of information are added to the city: - Real world - Land use - Services - Parcels - Streets - Customers # Architecture logicielle ## Evolution of software architecture ### 1990s - Spaghetti-oriented architecture (aka copy and paste) ### 2000s - Lasagna-oriented architecture (aka layered monolith) ### 2010s - Ravioli-oriented architecture (aka microservices) ### What's next? - Pizza-oriented architecture # End-to-End Feature Stack ## 2010s - Monolith ## 2015s - Monolith frontend - Monolith backend ## 2020s - Monolith frontend - App shell - Microservices ## Empowered Product Teams - Engineering + product + design + data + QA # Application monolithique - One page = one file - Strong coupling of functionalities - Business rules scattered in the code ## 1990's - Spaghetti-oriented architecture (aka copy and paste) ## Challenges - What are the drawbacks? # Application monolithique en couches - Use of Design Patterns - Object-oriented programming language - Separation of responsibilities - Centralization of business rules ## 2000's - Lasagna-oriented architecture (aka layered monolith) ## Challenges - What are the limitations? ## Examples - Examples of Design Patterns? # Application en micro-services - Each feature is independent - Different technologies coexist in the same application - Loose coupling based on a defined data format ## 2010's - Ravioli-oriented architecture (aka microservices) ## Challenges - What are the advantages? - What are the organizational constraints? # Méthode d'Urbanisation ## I. Mapping AS-IS - Processes - Data - Applications - Documentation - Interview - Analysis ## II. Analysis - Weak points - Opportunities - Constraints - Diagnostic - Prioritization - Roadmap ## III. Target TO-BE - Architecture - Service - Governance - Vision - Standard - Guidelines ## IV. Convergence Plan - Trajectory - Projects - Quick wins - Planning - Budget - Organization