Overview
The City of Yokyo had won the bid to host the next FunOlympic Games in 2019/20 but this had
to be postponed due to a worldwide pandemic. During the build-up to the planned games in
2019/20 the city had already invested hugely in IT infrastructure and systems to make sure that
the games would have been well organised, staffed, attended, and accessible to everyone.
Due to the pandemic restrictions, the FunOlympic committee have decided to run the 2020/21
games without the public attending the site. So now they have a number of additional projects
which need to be completed before the delayed games start to ensure athletes remain healthy
while attending the games and also that worldwide audiences can enjoy the games online.
Product to be deliver to client
We have to build an online registration system for audiences to gain access to the proposed
broadcast platform. The system must allow users to register, login and logout when using it, and
make selections of broadcasts they wish to watch. There should also be an admin side to the
system to allow an admin user to view user interactions, reset passwords etc. Required functions
are to be explain in following sections.
Client requirements
What the client wishes to see in the final prototype system.
OVERALL GOAL
A user-friendly streaming website that audience gain acess to the proposed broadcast of
Yokyo Olympic Games.
A website that can be easily viewed on both PC and mobile platforms.
DESIGN PHASE
Design a new corporate identity to match the website.
Full design documentation of the website including wireframe design drawings of a
number of design ideas.
The design will incorporate client input/influence at regular periods.
Design to incorporate a user-friendly interface and a professional look.
BUILD & TESTING PHASE
a. Connectivity to a database and the insertion of data to that database, functions to include
Login/logout and register system.
Make selections of broadcasts they wish to watch.
An admin user to view user interactions, reset passwords etc.
b. Testing records to show the system is functional within the initial boundaries.
FUNCTIONAL & NON-FUNCTIONAL REQUIREMENTS
1. FUNCTIONAL: Ability to login, ability to view data from a database of web
development clients, ability for a client to add themselves to the database as long as they
meet a minimum requirement.
2. NON-FUNCTIONAL: Website must be clean and user-friendly.
Constraints: The limitations in the case of the developer mainly are due to time constraints
brought upon by two factors.
The first being other work commitments that will eat into potential development time and the
second is in terms of travel to and from the university to access the software needed to develop
the product.
There are other constraints regarding budget expenditure, problems that may occur during
development like encountering bugs that need fixing, code errors etc. and also any family and/or
work emergencies that may occur which could eat into development time.
Apart from these, I do not foresee any other constraint issues and as for what I have already
stated regarding time management, the schedule will be adapted to cater for these issues.
Resources
The resources at use to develop the prototype will be available at ISMT College as the prototype
system will be tested out using the universities own network. For the development of the
prototype system, the following software will be used.
The Microsoft Office Suite (mainly Word, Excel, Publisher & MS Paint)
The Adobe development suite (Photoshop, Illustrator, Dreamweaver.)
Plan for prototype to run on University's own network servers.
Notepad ++, Visual Studio IDE (Web development software) and WinSCP (fileupload
software.)
The relational web database service SQL Server, again for testing purposes.
The reasons for this are due to sufficient system permissions being readily accessible within the
university.
Evaluation
At the conclusion of the development of the prototype system. The aim is to be in a position to
present a final prototype (alpha build) of the proposed system to the client.
The prototype will be presented to the client with functionality described at each stage and how it
came about.
If there are any faults/bugs in the prototype that have not yet been ironed out at the time of the
project's conclusion, these will also be explained and that if the go ahead is given for full system
development, these will be rectified.
Full design documentation would also be provided both in an ePortfolio and also in physical
form. Everything will be part of a PowerPoint slideshow presentation.
