Learning Portfolio

Competency 1: Develop an Application

#

Critical Learning Outcomes and Evidence

#

CL1 - Choose and implement appropriate architectures

#

Concrete evidence:

• 3-tier architecture (presentation / business / data) of the Hub ECO-MED, with an abstraction layer to isolate external systems (SX Everwin, ArcGIS, Azure AD)
• Service-oriented architecture for RaTouf: AuthService, ApiService, ChiroptereService, ReferentialService, DataProcessor, ActivityLevelCalculator, SessionValidator
• Documented justification of Node.js + Express + MongoDB choices against constraints: schema flexibility (evolving regulations), learning curve for project handover, performance on limited workstations
• Application of SOLID principles and OWASP recommendations across all ECO-MED projects

CL2 - Develop applications on specific platforms

#

Concrete evidence:

• PetalPatrol — field interface designed for tablets in real conditions: large buttons, full-sun readability, intermittent connectivity support
• EcoSur — deferred synchronization for offline use in low-coverage areas, with automatic conflict resolution on reconnection
• Multi-projection conversion (Lambert 93, UTM, WGS84) via Proj4js in-browser to support national and international contexts

CL3 - Audit an application

#

Concrete evidence:

• IT fleet audit at ECO-MED carried out during the internship: renewal analysis, hardware inventory, costed recommendations
• Automated Jest tests on critical components: RaTouf CSV parser, chiroptera activity computations, geographic coordinate conversions
• Implementation of a centralized logging system (user actions, external API calls, errors) for production audit and diagnostics
• Code instrumentation for fine behavior analysis (large CSV processing optimization in RaTouf)
• OWASP security audit carried out on the ECO-MED applications (confidential report, not published)

CL4 - Integrate solutions in a production environment

#

Concrete evidence:

• Production deployment of the Hub and business apps on Debian Linux VM + NGINX at ECO-MED, with sizing co-defined with the IT provider
• Full GitFlow: main / dev / feature/* branches, mandatory Pull Requests before merge, dedicated server-config branch
• GitHub continuous integration: tests run automatically on each push to detect regressions
• JWT + Azure AD SSO integrated with ECO-MED’s existing infrastructure, with periodic token validity check and automatic reconnection

Competency 2: Optimize Applications

#

Critical Learning Outcomes and Evidence

#

CL1 - Choose appropriate complex data structures for the problem

#

Concrete evidence:

• Trie implementation for autocompletion in Hub ECO-MED - instant search among 5000+ species
• Graph structures for matching algorithm in Eco-Carpooling
• Skip List implemented in lab work for optimized ordered data management

CL2 - Use appropriate algorithmic techniques for complex problems

#

Concrete evidence:

• Genetic algorithm for route optimization in PetalPatrol - 40% distance reduction
• A* implemented for navigation in mobile app SkyFuel
• Dynamic programming applied to knapsack problem in SAÉ (grade: 18/20)

CL3 - Understand issues and means of securing data and code

#

Concrete evidence:

• Complete security for BlackArsenal: XSS, CSRF, SQL injection protection
• AES-256 encryption of sensitive data in Hub ECO-MED database
• Security challenges creation for YGGAME CTF Platform: buffer overflow, SQL injection, reverse engineering
• Security audit report performed with OWASP ZAP on my projects

CL4 - Evaluate environmental and societal impact of proposed solutions

#

Concrete evidence:

• Energy optimization of SkyFuel: 60% battery consumption reduction
• Carbon impact analysis documented for Hub ECO-MED deployment
• Lazy loading and pagination implemented to reduce bandwidth by 70%

Competency 3: Administer Complex Communicating Computer Systems

#

Critical Learning Outcomes and Evidence

#

CL1 - Design and develop communicating applications

#

Concrete evidence:

• Complete REST API for Hub ECO-MED with OpenAPI documentation
• WebSockets implemented in PetalPatrol for real-time synchronization
• Microservices architecture with Docker Compose to decouple services
• Discord Bot and CTFd API integrated in YGGAME CTF Platform for real-time notifications

CL2 - Use virtualized servers and network services

#

Concrete evidence:

• Complete Dockerization of all projects with optimized docker-compose.yml files
• Kubernetes deployment for Hub ECO-MED with auto-scaling
• Containerized CTF infrastructure in YGGAME CTF Platform: 8 Docker challenges + Dockge
• Terraform used to provision cloud infrastructure in a reproducible way

CL3 - Secure system services and data

#

Concrete evidence:

• Multi-layer security: Cloudflare WAF + fail2ban + audit logs for BlackArsenal
• SSL/TLS certificates with Let’s Encrypt and automatic renewal
• Penetration testing documented with remediation of identified vulnerabilities

Competency 4: Manage Information Data

#

Critical Learning Outcomes and Evidence

#

CL1 - Optimize enterprise data models + CE4.03 (mathematical foundations)

#

Concrete evidence:

• Complete refactoring of BlackArsenal database: 3NF + optimized indexes = 80% gain
• Mathematical modeling for Hub ECO-MED with cardinality calculations
• Optimized complex queries: 7-table joins went from 12s to 0.3s

CL2 - Ensure data confidentiality + CE4.01 (privacy respect)

#

Concrete evidence:

• Complete GDPR module for Eco-Carpooling: consent, portability, forgetting
• AES-256-GCM encryption of sensitive data with automatic key rotation
• Blockchain audit logs for unalterable traceability in PetalPatrol

CL3 - Organize data restitution + CE4.02 (ecological stakes)

#

Concrete evidence:

• Real-time dashboards for RaTouf with Chart.js and WebSockets
• Redis cache system reducing database queries by 90% and server consumption
• Progressive archiving: hot data SSD → warm HDD → cold S3

CL4 - Manipulate heterogeneous data + CE4.04 (consistency and quality)

#

Concrete evidence:

• Python ETL pipeline to integrate CSV, JSON, XML in Hub ECO-MED
• Multi-layer validation: JSON schemas, DB constraints, unit tests = 99.9% integrity
• Universal API supporting REST, GraphQL and multi-format export

Competency 5: Lead a Project

#

Critical Learning Outcomes and Evidence

#

CL1 - Measure the economic, societal and technological impacts of an IT project

#

Concrete evidence:

• Detailed budget study for the production of connected entomological traps: costed Li-Ion (€1,379 for 30 units) vs LiFePO4 (€1,415) comparison, with performance / autonomy / cost criteria
• IT fleet renewal analysis at ECO-MED with costed recommendations delivered to management
• Time savings measurement through automation of data transmission to INPN: removal of the manual Excel → SIN process, reduced data-entry error risk
• Documented societal impact: GDPR, French Environmental Code (article L411-1A), INSPIRE directive, SINP protocol compliance

CL2 - Integrate an IT project into the IS of an organization

#

Concrete evidence:

• Integration of the Hub ECO-MED with the existing ecosystem: SX Everwin ERP (administrative management), SIN ArcGIS (naturalist data), Azure AD (identities)
• Abstraction layer isolating external systems: eases maintenance, unit testing, and replacing a system without impacting the rest
• Custom HTTP module for SX Everwin (which lacks a complete REST API), with smart caching to limit server load
• EcoSur automatically retrieves projects from SX Everwin → eliminates re-entry and ensures cross-app consistency
• PetalPatrol and RaTouf push validated data to the SIN ArcGIS, which then forwards them to INPN through the established institutional flow

CL3 - Adapt an information system

#

Concrete evidence:

• Monolithic → modular architectural evolution: choice of a federating Hub rather than a single application, to allow incremental addition of business apps without redesign
• Progressive migration of safety sheets from Excel to EcoSur without disrupting the field process: versioning, automatic risk-level computation, advanced search
• MongoDB vs SQL Server choice justified by the need to adapt the IS to fast-evolving regulatory schemas (safety sheets, INPN formats)
• Deferred synchronization introduced specifically to adapt the IS to the mobile/field context with variable connectivity
• Systematic technical documentation of architectural choices and integrations, in a context without IT department: essential to ensure IS sustainability beyond my work-study contract

Competency 6: Work in a Computing Team

#

Critical Learning Outcomes and Evidence

#

CL1 - Organize and share technological and informational watch

#

Concrete evidence:

• 4-month active watch on three complementary themes (Large Language Models, cybersecurity, planned obsolescence), with iterative source mapping: companies (Anthropic, Meta), specialized media (BleepingComputer, Dark Reading, Help Net Security), institutional bodies (ARPP, HOP), academic (IEEE, MIT, Univ. Chicago)
• Discord RSS bot developed to automate collection and sharing: continuous feed monitoring, thematic-channel publishing, preliminary summary generation, on-demand deep analysis via Gemini API (translation, key-point extraction, relevance scoring)
• 6 articles published on the educational Moodle forum: Anthropic-Iceland AI education partnership, Lazarus group attack on European defense industry, Meta’s Mango/Avocado models, Microsoft conviction over Windows 11 obsolescence, WiFi sensing & privacy (IEEE 802.11bf), WhatsApp API flaw — with active participation in discussions
• Technical watch in a corporate setting: official documentation, forums and exploration before each major technical choice (ArcGIS API, Proj4js, JWT, Azure AD, MongoDB, alternative Go/Gin stack)
• Reasoned use of AI tools (Claude for source identification, Gemini for article analysis), with systematic critical review

CL2 - Identify the stakes of innovation economics

#

Concrete evidence:

• Comparative analysis Li-Ion (INR18650-25R) vs LiFePO4 (JGCFR18650-2200) for entomological traps: autonomy, cost, durability, safety — with costed budgeting for 30 units
• Open-source choice (Node.js, Express, MongoDB, Leaflet, Proj4js) over proprietary solutions to reduce vendor lock-in and total cost of ownership
• Watch on planned obsolescence (tracking Microsoft Windows 11 condemnation by the JDP, monitoring the 2026 ADEME budget for circular economy) → awareness of eco-design and software-durability stakes
• Continuous evaluation of the AI ecosystem (LLMs, Meta models, Anthropic research) to spot integration opportunities for ECO-MED tools

CL3 - Guide IT change management within an organization

#

Concrete evidence:

• Introduction of agile practices at ECO-MED (Kanban, GitFlow, Pull Requests, CI) in an organization previously running in a V-cycle — pedagogical effort with the tutor and stakeholders
• Regular demos of progress to key users to create a continuous feedback loop and foster ownership
• EcoSur requirement reframing: shifting from a simple data-entry form initially requested to a complete solution (versioning, risk scoring, advanced search) after user dialogue — solution ultimately praised for addressing needs the users hadn’t explicitly formulated
• Systematic documentation of technical choices and features to ensure continuity after my departure
• Widespread adoption of the applications (Hub, PetalPatrol, RaTouf, EcoSur) by ECO-MED teams, with regular constructive feedback from users feeding into successive iterations