2847586,2863164,2845679 .pdf

File information


Original filename: 2847586,2863164,2845679.pdf
Author: Louise O'Reilly

This PDF 1.4 document has been generated by Writer / OpenOffice 4.0.1, and has been sent on pdf-archive.com on 27/03/2015 at 21:50, from IP address 86.43.x.x. The current document download page has been viewed 361 times.
File size: 704 KB (6 pages).
Privacy: public file


Download original PDF file


2847586,2863164,2845679.pdf (PDF, 704 KB)


Share on social networks



Link to this file download page



Document preview


Assignment Cover Sheet
Student name:

Thomas Hood, Alex Vodnev, Rostislav Panin

Student number:

2847586, 2863164,
2845679

Faculty:

Computing Science

Course:

BScH Computing

Subject:

Server Side Web Design

Study Mode:

Full time

Lecturer Name:

Alan Hannaway

Assignment Title:

Initial Design Document

No. of pages:

6

Disk included?

Yes

Additional
Information:

(ie. number of pieces submitted, size of assignment, A2, A3 etc)

Date due:

27th March 2014

Date submitted:

27th March 2014

X

Stage/year:

Year II, Semester II

Part-time

No

X

Plagiarism disclaimer:
I understand that plagiarism is a serious offence and have read and understood the college policy on
plagiarism. I also understand that I may receive a mark of zero if I have not identified and properly attributed
sources which have been used, referred to, or have in any way influenced the preparation of this
assignment, or if I have knowingly allowed others to plagiarise my work in this way.
I hereby certify that this assignment is my own work, based on my personal study and/or research, and that
I have acknowledged all material and sources used in its preparation. I also certify that the assignment has
not previously been submitted for assessment and that I have not copied in part or whole or otherwise
plagiarised the work of anyone else, including other students.

Signed: _____________________

Date: 27th March 2015

Please note: Students MUST retain a hard / soft copy of ALL assignments as well as a receipt issued and
signed by a member of Faculty as proof of submission.

pg.1

Clubber
A Brief Overview of the Site
Clubber is a web application focused heavily on nights out and having a good time. It can be
divided into 2 parts. User’s point of view and bar’s/club’s point of view. Both average joe
and a busy nightclub can register as a user. 

( How far down the rabbit hole of event management will you go? )

During registration, a user can select whether he is a person or a bar/club.
An average user will be able to see bars/clubs with special promotions that are currently 
available. These promotions are called events (for example; 'Beer Pong' in Arthur's Bar). 
Bars/clubs themselves will have ratings similar to imgur or Reddit.
Each bar displayed on a main page will also have 2 latest events displayed next to it for a 
user friendly experience. There is also a rating displayed next to bar’s/club’s name. An 
average user can like/dislike a bar, changing its rating. Users will also be able to search for 
bars/events.
Every bar/club will have its own page, on that page there will be general info about the place,
google map’s API and a picture, along with the opening hours. There also will be list of 
current events and a section for comments. User can add a new comment or view existing 
comments. Each user will have a favourites list. Any events he/she browses can be added to 
the favourites list and then displayed. 
Both bar and average user will have an ability to change their details after registration
(address, opening hours, etc.). 

pg.2

Page Design

This is our initial concept for how the main page, and subsequent pages should look. At the
top of the site the user will have some navigation buttons as well as a logout option and
events will be displayed from top to bottom on the page. All pages will follow this design
layout.

pg.3

Sitemap/Wireframe

This is a rough wireframe/sitemap of the website. This may expand as we add functionality
but this is what we aim to implement at the least. The mainpage is the core of the website.
NB: At any stage the user will ofcourse be able to logout.
Favourites will pull a list of the users favourite events and display them in a manner similar
to the mainpage. Comments will likely be displayed on a separate page for now, and bars
will be able to submit events through the submitevent page. Both normal users and bars will
have their own profile pages.

pg.4

Functionality
1. Registration ­ A user can register on the site. There will be a general registration form 
with radio buttons where a user can select person/bar. Depending on his choice, the 
rest of registration will look different for both.
Email has to be a valid email. A username has to be unique and will be checked. 
If it is a bar/club, then valid opening times, and an address must be provided.
2. Login / Logout functions ­ When a user logs in, a session starts. When he logs out, a 
session ends. 
3. Editing Personal Info ­ A user, whether it is a bar or a person will have an option to 
change their address, opening hours, etc… after registration if they so wish.
4. Rating System ­ Each bar will have a rating. A user can like/dislike a bar,
increasing or decreasing the rating. 
5. Event ­ Every bar will have running events. An event is a special deal/promotion. A 
list of events will be displayed on the main page and the bar’s page.  
Note ­ When event reaches its date, it still will stay stored in the database, but won’t 
be displayed. 
6. Editing Event ­ After an event is created, a bar will be able to modify any info needed.
7. Adding an Event to Favourites ­ Every user will have a favourites list with all the 
events he/she likes. They will be displayed on the user’s favourites page.
8. Comments ­ Every bar/event wille have two buttons for comments. A user can “Add a 
comment”, where a new form will appear and he can type the comment then save it. 
“View comments”, where all comments will be displayed for that bar/event.
9. Edit/Delete Comment ­ Advanced feature! ­ A user will have an option to view all the 
comments he left and edit/delete them.
10. Search Option ­ Advanced feature! ­ A user can search for a specific bar or an event.
11. Forgotten Password – Very Advanced feature! ­ Email the user their fogotten 
password.

pg.5

Database Design

It's possible we may need to add more to this as we add functionality to the website, 
but as a basic offering this is what we need from a database.
Each table is typically linked by a unique username or eventid. 

pg.6


Related documents


2847586 2863164 2845679
vmsc supp regs eliminator
terms and conditions
ascii ep02
prt3 ei02
june 5 sc endless summer social media contest rules regs

Link to this page


Permanent link

Use the permanent link to the download page to share your document on Facebook, Twitter, LinkedIn, or directly with a contact by e-Mail, Messenger, Whatsapp, Line..

Short link

Use the short link to share your document on Twitter or by text message (SMS)

HTML Code

Copy the following HTML code to share your document on a Website or Blog

QR Code

QR Code link to PDF file 2847586,2863164,2845679.pdf