Gabriel

Monday
8:30 AM – 10:30 AM: Advanced Software Architecture
10:45 AM – 12:45 PM: Object-oriented design and design patterns
2:00 PM – 5:00 PM: Software Engineering Lab (team project)
Tuesday
8:30 AM – 10:30 AM: Advanced Databases
10:45 AM – 12:45 PM: SQL Optimization and Transactional Systems
2:00 PM – 4:00 PM: System programming (memory, processes)
4:15 PM – 6:00 PM: System Programming Lab
Wednesday
9:00 AM – 11:00 AM: Computer Security
11:15 AM – 12:30 PM: Cryptography and Application Security
2:00 PM – 5:00 PM: Final year project (supervised)
THURSDAY
8:30 AM – 10:30 AM: Advanced Web Development
10:45 AM – 12:45 PM: REST APIs and client-server architectures
2:00 PM – 5:00 PM: Web/Software Development Lab
Friday
9:00 AM – 11:00 AM: IT Project Management
11:15 AM – 12:45 PM: Agile Methods and Collaborative Tools
2:00 PM – 4:00 PM: Interim presentations / project meetings
4:15 PM – 5:30 PM: Technological monitoring and professional development

Condition and branch management
It is used to check the game variables to guide the player to the correct scene or route. This ensures the logical consistency of the scenario.
Average time: 2 to 4 days.
Programming multiple endings
This step determines the possible outcomes of the game based on the player's actions. It enhances replayability and gives weight to the decisions made.
Average time: 2 to 5 days.
Backup and progress management
It allows the player to stop and resume their game without losing their progress. It also includes tracking of routes and endings already unlocked.
Average time: 1 to 2 days.
User interface programming
This step concerns menus, dialogue history, relationship screens, and statistics. A clear interface greatly improves the gaming experience.
Average time: 3 to 7 days.
Integration of music and sounds
It serves to enhance the atmosphere and emotions. The music and effects are triggered according to the scenes and events.
Average time: 1 to 2 days.
Adding optional systems
This step allows for the addition of depth to the gameplay, such as a calendar, special events, mini-games, or timed choices.
Average time: 2 to 6 days (depending on the complexity).
Testing, debugging and balancing
It serves to correct errors, check routes, balance affection, and prevent blockages. It is a critical step for the stability of the game.
Average time: 5 to 10 days.
Game preparation and export
The final step involves compiling the project for the chosen platforms and verifying that everything works in the final version.
Average time: 1 to 2 days.

Game engine selection
This step serves to define the programming tools, the language used, and the technical limitations of the project. An engine adapted to visual novels saves a great deal of time by already integrating the dialogue, choice, and save systems.
Average time: 1 to 2 days.
Installation and implementation of the project
It involves installing the engine, creating the project, and organizing the files (scripts, images, sounds, interface). Good organization prevents errors and facilitates code maintenance.
Average time: 1 day.
Character definitions (code)
This step allows you to define the characters, their names, text colors, and visual states. It is essential for correctly displaying dialogues and sprites throughout the game.
Average time: 1 to 2 days.
Dialogue system programming
It is used to ensure the smooth flow of narrative scenes. The dialogues are programmed to appear in the correct order, with the right sets and characters visible on screen.
Average time: 3 to 7 days (depending on the length of the game).
Setting up player choices
This step allows for interactivity. Each choice influences the course of the story or relationships with characters, which is central to an otome game.
Average time: 2 to 5 days.
Creation of the affection system
It serves to quantify the relationship between the player and each love interest. Affection values ​​are modified by choices and used to unlock routes, scenes, and endings.
Average time: 1 to 3 days.
Character route programming
This step allows the story to be separated into distinct paths according to the player's preferences. Each route contains its own exclusive scenes, choices, and events.
Average time: 4 to 10 days by road.

Programming - weight training - boxing - cooking

1.80m tall, blond hair, slightly tanned complexion, green eyes, lean and slightly muscular physique, pierced ears with small black jewelry, wears a few simple bracelets, always wears basic and very understated clothing.

Calm, responsible, persevering, hardworking, studious, reserved, combative, confident in himself and his abilities, arrogant, teasing, cynical

Name: Soran
First name: Gabriel
Age: 23
Study: Final year of programming at university.
Family:
Soran Georges (father) 52 years old, good relationship - Works in construction.
Soran Miriam (mother) 54 years old, good but neutral relationship - Manager of her clothing store.
Soran Émilie (little sister) 14 years old, very good relationship - Is in 4th year at Lycée.