1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
|
---
title: Design Document
author: [ Nathaniel Foy, Guntas Grewal, Tomer Kimia, Andrew Murrell, Luke Shumaker, Davis Webb ]
---
Version 1.0 – 2014.02.10
Created 2014.02.09
# Purpose
The purpose of this document is to outlay the desgin, intent, and structure of
the Project Leaguer tournament organizing software.
Released under an open license, Project Leaguer leverages powerful web
technologies to provide everything needed to organize an online tournament.
Whether it's League of Legends, Chess, Poker, or more, Project Leaguer provides
tournament organizers, participants, and spectators with an online
interface to keep up with the score. Even better Project Leaguer offers scoring
features and options which would be very difficult to implement with traditional
tournament organizing practices such as peer review and team-independent
individual scoring.
The software itself operates as a stand-alone background server application
accessible and configurable though its web interface which reveals to users a
sleek web application which manages tournaments.
#Non-Functional Requirements
TODO Guntas. Email dunsmore and marco about this, then fill it out.
# Design Outlines
## Design Decisions and Components
Project Leaguer is written on the Ruby on Rails platform and will use the Model 2 (MVC) design pattern/architecture. This architecture is comprised of three interacting components: Controllers, Views, and Models.
Controllers
: Requests received by the server are processed by a routing
subroutine and directed to a controller responsible for handling
them. Controllers accept these requests and manage any logic
necessary to obtain the correct content for display, retrieving
and updating information from the Model as needed. It then
creates a new request, places the content from the model in the
request (if applicable), decides which view it will be passed to,
and passes on the request.
Models
: In Ruby on Rails, models are usually implemented as an interface
to a table in the database and a Ruby file which queries this
table and interacts with the other components. For example, a
"user" model would be connected to the "user" table and a file
"user.rb" in the app/models directory would provide an interface
to interact with the "user" controller.
Views
: Views will primarily be dynamically generated HTML pages and will
display the users desired content inside of the web browser. These
may be implemented with inline Ruby scripts and tags within
traditional HTML.
## Component Interaction
Controllers will be used to run all of the background work of Leaguer. They will fetch the necessary data and will tell the view what to do. We will be implementing seven controllers into Leaguer. Those will be:
i. PM & Alerts – This controller will be used for sending and receiving private messages to and from the host. Players will be able to message the host in order to inform him/her of anything during the tournament. This will also allow the host to post any notifications he or she desires that will be displayed for all to see.
ii. Homepage – Used to handle the homepage. This will be the first web page seen by any user of the application.
iii. Login – This controller will be used when a user attempts to sign in to their profile on Leaguer.
iv. Search – This controller will be used to search the web-base for on going tournaments, players and past tournaments.
v. Tournament – Used for setting up a tournament. This will be restricted to the host of the tournament.
vi. User – The controller that will take each user to their own profile.
vii. Match/Peer Review – used for gather game statistics and the separate player reviews.
Each of these controllers will fetch the data specified by its separate section. The view will then be used to display all of this information, so Login will take the user to a login page, search will take the user to a search page and so on.
The Model will be the data section that will map all of the information to their proper locations in the data base.
# Design Issues
## Scoring Algorithm
In an effort to keep our system broad, one of our requirements is that Leaguer is adaptable to many competitions, not just League of Legends. How do we assure that the different scoring systems of different sports are represented in Leaguer?
Option 1
: One of our interfaces could be “Scoring System” which will be
implemented by many classes with common scoring systems. For
example there would be a implementing class in which the highest
score wins, and one in which the lowest score wins. This is likely
to be the winning option, as there are not too many obscure
scoring systems that we could not think of.
Option 2
: We could design an API in which the host writes a method to update
the scoring. This is pretty complex, and while it would allow more
customization, it is hard to imagine completing this task without
first completing option 1.
## Offline Data Management
TODO – Nathniel write this
## Fetching Data from Games
TODO – Nathaniel write this.
# Design Details
## Class Descriptions and Interactions
### MODELS
ActiveRecord::Base (abstract)
: The abstract model that all other models inherit from.
User
: This model represents all types of users; hosts, players, and
spectators. These roles are identified by a “role” attribute.
### VIEWS
layouts/application.html (abstract)
: An abstract HTML file, all entries below are webpages (we
represent them as subclasses of the abstract “Webpage” class. All
webpages will send HTTP requests to the server. Most of the visual
effects and update the display with Javascript methods. Each page
will have a login dialogue which will POST to the login controller
or the logged in user’s page.
main/homepage.html
: This page has 3 basic options. Visually simple – two large buttons
on a white screen, and a search bar above them. The search bar
will cause a POST requeest to the search controller. Log in (which
will cause a POST to the login controller) and “Go to Tournament”
in which you enter a tournament title. This interacts with the
Homepage Controller.
login/form.html
: Page with form entries for username, password. If user clicks “new
user” more forms entries will appear. One for repeating the
password, and one for email. This POST to the Login controller.
tournaments/new.html
: A form that interacts with users who are either hosts or becoming
hosts. This interacts with tournament controller.
tournaments/index.html
: A tree-like display of matches, where each match consists of a
pair of teams. All users can click on a match to go to that
match’s page. Host can see a gear on top left corner that
represents tournament settings, it will GET the edit Tournament
view. There will be an end button that will redirect to back to
the homepage after posting to the tournament controller. The
tournament will POST to the tournament controller.
tournaments/edit.html
: This view is a list of settings. Some are form entries, and some
are checkboxes. More settings will be added later in
develpment. This view interacts with the tournament controller.
matches/show.html
: A display of both teams. Each team's players are clickable which
causes a GET for the player's profile HTML. A link above both
teams will GET the tournament the match belongs to. This will POST
its actions to the Match controller.
search/form.html
: A page with a searchbar and a list of searchable tournaments that
match the search query. The searchbar causes a POST to the search
controller. Each entry is clickable and causes a GET to the
enrry's tournament.
users/show.html
: A page with the user's information. One can view the player's
reviews. If the user is viewing his/her own profile, they can edit
it causing a POST to the userProfile controller.
### CONTROLLERS
HomepageController
: This is the main controller. It has methods showHomepage() which
renders the homepage view. It has editSettings() method, that gets
the current settings of the entire server, provided that the host
is viewing the homepage.
LoginController
: This has doLogin() and doLogout(). Both have access to the HTTP
requrest. It will interact with the Users model to validate
passwords and usernames.
TournamentController
: This controller will have methods: newTorunament(),
getTournament(), editTournament(), and endTournament(). All of
these methods will interact with the Tournament model, and all of
its fields including users matches and TournamentSettings. And all
will interact with their tournament view, for example,
newTournament() will render newTorunament.
Server
: Rails’ Server class handles all HTTP events. Our Server class is
the class that is the main program. It instantiates other classes,
manages requests from Views, and runs static methods.
User
: A class that represents someone using the Views (HTML, javascript)
the user is in competitions and
## UML Diagram of Classes
TODO – I’m working on this – see images.pptx ~ Tomer
So am I: ~ Luke
\
|
