Proposal and Feasibility Presentation

SPORTS HUB
Group Members
Muhammad Khezar (SP16-BSE-026)
Shahroom Khan (SP16-BSE-029)
Aamir Sadiq (SP16-BSE-012)
Supervisor
Mr. Sumair Khan

Department of Computer Science

COMSATS University Islamabad, Abbottabad Campus
Agenda of the Presentation
■ Motivation
■ Brief Introduction
■ Scope
■ Functionalities
■ Proposed Tools/Platform
■ Feasibility
■ Technical Feasibility
■ Financial Feasibility
■ Resource Feasibility
■ Operational Feasibility
■ Schedule
■ Tasks for 1st Iteration (or 30%)
■ Conclusion

3
Motivation
These days sports club and local sports event uses paper work for scoring.
We will discuss some of the drawbacks of the current system.
■ Paper Work: The complexity of Paper work increases as the data increases. Paper
work is also not environment friendly.
■ Remembering: Due to complexity of data it’s difficult to remember the status of
every match.
■ Management of records: It’s become very difficult to manage the records after
the match or even during the match.
■ Search Difficulty: When a participant want to search record of any event, so it is
very tedious task to do.

4
Brief Introduction
■ We introduce a new system for sports events.
■ There is a need to replace manual work to get benefit from technology by
using mobiles device with internet functionality.
■ Sports Hub is a social media application.
– The main idea of the project is to organize the sports events. Then any
person can participate in the event, participant can create groups and
chat, application show live score ,results of past sporting events .
■ The application will provide the serving activity in quick and easy manner.

5
Scope
Sports Hub is a social media application. That
includes
• User can first sign up than he/she can sign in , User Account Management will
provide user account modification.
• Sports Events Management will provide management of three different sport
categories like Invasion games, Net/wall/racket games, Fielding/striking games.
• User can send friend request the other user either accept or reject the request. And
they can also unfriend and block.
• When event is created ,the participants can chat in group or in private message
• Event Manager will updated the score.
• Results and Match Analysis Reporting

6
Functionalities
■ User Accounts Management Module
– This Module will get user information using for sign up , after successful sign up, user
can visit login page and enter their credential then user will have access to main
dashboard. User can also update their profile.
■ Sporting Event Management Module
– Authentic user can create an event with specific categories of Invasion games,
Net/wall/racket games, Fielding/striking games. Once the event is created other
user can join.
– Invasion games
■ Football
■ Hockey
– Net/wall/racket games
■ Tennis
■ Badminton
– Fielding/striking games
■ Cricket

7
Functionalities(cont.)
■ Friends List Management Module
– User can send friend request targeted user either accept or reject ,user can see all
friends and user can also unfriend or block specific friend.
■ Groups Management and Chatting Module
– User can create group ,user can add and remove members from the group ,all
members of group can chat, and group member can also chat privately with
specific member of the group
■ Live Score Module
– An event creator will update the status of the event , and this status will shows
on main dashboard to those who participate in this event on priority basis , and
user can also see the ongoing events status by visiting Live Score of All ongoing
events.

Page 8 of 20
Non-Functional Requirements
 Non-functional requirements of Sports Hub are as follows:
 Performance Requirements:
■ Storing huge amount of data will not affect system performance.
■ Applying query in such a way that performance will improve.
■ The server will be able to handle multiple requests at a time.
■ Delay time will not be more than 10 seconds.

 Safety and Security Requirements:

■ The system will be able to secure the personal information of
users.
■ The system will be made secure from hackers.
■ Passwords will be secure by not display while typing.

Page 9 of 20
Non-Functional Requirements(cont.)
 Software Quality Attributes:
■ Portability:
This Android App will run in all Android Operating Systems.
■ Availability:
The Application should be available at any time when the user wants to use it.
■ Maintainability:
While using the Application, the Application will make sure that the user is getting an
online experience and should not be corrupt so that Application data is maintainable,
well organized and easily accessible.

Page 10 of 20
Proposed Tools/Platform
Proposed Tools/Platform to be used:
Tools Version Rationale

Android Studio 3.3.2 IDE

Tools MS Word 2019 Documentation
And
Technologies MS Power Point 2019 Presentation

Pencil 2.0.5 Mockups Creation

Star UML 2.8.1 UML Diagrams

Technology Version Rationale

Java 3.6 Programming language

MySQL 2013 Query Language

Php 7.1 Back end Development

Proposed Hardware tools to be used:

– Smartphones (internet Connectivity)

11
Technical Feasibility

■ Android Studio for development.

■ Java will be used as programming language.
■ Firebase Realtime Database for data storing at backend .
■ Php will be use for sever side.

12
Financial Feasibility
Technologies to be used in the system
Resource Name Edition Source
Android Studio Open Source https:developer.android.com/studio

Firebase Realtime Open Source https://firebase.google.com/realtime/database

database
Xampp Open Source https://www.apachefriends.org/
SQLite Open Source https://www.sqlite.org/
Star UML $89 https://staruml.io
Google Chrome Open Source https://www.google.com/
Browsers
Funding Self
13
Resource Feasibility
■ Human Resource
■ Hardware Resource
– Minimum System Requirement for Development:
■ Microsoft® Windows® 7/8/10 (32- or 64-bit)
■ 3 GB RAM minimum, 8 GB RAM recommended; plus 1 GB for the Android Emulator
■ 2 GB of available disk space minimum,
4 GB Recommended (500 MB for IDE + 1.5 GB for Android SDK and emulator
system image)
■ 1280 x 800 minimum screen resolution

■ All resources which lead the foundation of our product will be available and
also can accommodate when needed.
■ All the funds which are required in the development and deployment of the
system will be paid by the project group members.

14
Operational Feasibility
■ Final version will be available as a complete Android App.
■ App will work as a online application.
■ User will install the application
■ After successful sign up user can organize, participate and join the
sporting events.

15
Schedule

16
Tasks for 1st Iteration (or 30%)
■ SRS Document
■ User Account management
■ Event Creation
■ Layouts of all module

17
Conclusion
■ The technologies we will use are paid and open source..
■ This product will overcome the manual process workload.
■ This product will increase social interaction.
■ On successful completion of this project the resultant product gives solution of real
world problem.
■ A user-friendly application will be developed.

18
Any Questions?
Thank You!