This repository describe the architecture, classes/modules and design decisions of Quake 3 Report.
The system is about the game Quake 3. The systema will be able to get the system log and plot information to the admin. The system should be able to read a text file containing the games log of a Quake 3 server. The log aggregates information about kills, deaths, suicides and player names ordered by time.
Actor: Server admin
Flow of events:
- As a Quake 3 server admin I'd like to feed a command line app with my server log and obtain a summary of all games present in the log file.
- The command line application should output a summary with the following informations (for each game match):
- player names
- total number of kills
- total kills by players
Precondition:
- A game would have to have happened.
- The actor should enter with the command line.
Postcondition:
- The actor must to have the summary information.
Actor: Server admin
Flow of events:
- Feed a command line application with my server log.
- Obtain a ranking of all players ordered by the number of kills of each player.
- The command line application should print the list of players with their kills.
Precondition:
Insert the command line.
Postcondition:
The list of player with the kills should be print.
Actor: Server admin
Flow of events: 1.Generate a web page with an user friendly output of command line rank command.
Precondition:
Acess the web page.
Postcondition:
Print the line rank command.
The system's architecture will be separated in just three parts, since the data of the system is taken from the game log. These parts are: domain, business and view.
Domain will be the system's class.
Business will be the classes who will process the information and give the answer to the users of the system.
View will be the graphic part of the system that will interact with the user
