Development time: 90 days
- Leonel Bazán: Team, Broker, GameCard, GameBoy
- Ezequiel Laime: Team, Broker
- Diego Perez: Broker, GameCard, GameBoy
- Ezequiel Gauna: GameCard, GameBoy
>>>> Find the full software specifications here!. <<<<
Delibird is a distributed system that simulates the behavior of an operating system, covering topics such as memory management algorithms, process scheduling algorithms, file systems, kernels, etc. All modules work concurrently and must be able to pass 25 integration tests that simulate different behaviors based on different configurations.
The system components will be:
- A publisher process that inputs messages into the system (Game Boy).
- A Message Queue administrator process (Broker).
- Processes that retrieve messages and perform planning based on them (Team).
- Filesystem processes responsible for maintaining files over time (Game Card).
It is a process scheduler, where each process is a trainer that competes for CPU cycles. It supports several scheduling algorithms which are parametrizable, a state system, and a deadlock resolution manager.
The objective of a team is that all the trainers that are part of it, capture the Pokémon they need.
A team, in turn, competes with other teams for shared resources found in the gamecards. (Spoiler: The resources are the Pokémon!)
A Team module fulfills its objective when all its trainers have done so (Trainers fulfill their objective when they capture all the bugs Pokémon they need).
Supported scheduling algorithms: FIFO, Round Robin, and Shortest Job First with and without preemption.
It is the FileSystem, which stores and manages all the Pokémon in the map. It allows creating, editing, and deleting files. The files are made up of blocks (e.g., 1.bin, 2.bin, 3.bin) and represented by a metadata file just like in a real file system.
Sends messages to all modules (publisher), and is the system tester. It allows creating all the system messages: creating new Pokémon on the map, requesting captures, confirming captures, etc.
Receives and distributes messages among the different modules. It uses Message Queues (MQ) technology, in which there are subscriber modules waiting for specific messages. It supports and implements by parametrization the following memory management mechanisms:
- Dynamic partitions with compaction
- Buddy System
- Allows cache dump
- Install project
$ sh instalacion.sh-
Restart Terminal so that environment variables are applied (Just open another terminal)
-
Modules can be started individually (the executables are inside the 'module-name/Debug/module-name' folder) or run automated tests
Note: Link to the Testing Document
-
Install byexample: It is a tool that allows running bash commands and checking module logs, enabling the automation of executions and checks. You can see the following test example used to verify the integration between the Team and the Broker... => Installation guide
-
Run basic tests:
$ cd tests-de-integracion
$ sh broker.sh
$ sh team.sh
$ sh regresion.sh- Run tests:
$ cd test-catedra
$ sh <nombre-de-prueba>.sh