documentation (2)
documentation (2)
Soccer
Club
"Club thrives, uniting fans with passion and victories."
www.soccerclub.com
DESIGN AND DEVELOP BY
Table of
Content
02 12
Diagarm
Acknowledgement
03 23
Introduction Project Allocation
04 24
PROJECT
Background
DELIVERABLES:
06 26 FUNCTIONAL
Scope RERUIEMENTS
08 29
CONSTRAINTS NON-FUNCTIONAL
RERUIEMENTS
09 30 8. Hardware and
PROBLEM
STATMENT Software
Requirements
11 02
PURPOSED screenshot
SOLUTION
01
Acknowledgement
I would like to acknowledge all those who have given moral support
and helped us make the project a success.
And finally, I would like to offer many thanks to my colleagues for their
valuable suggestions and constructive feedback.
02
1 INTRODUCTION
Our mission is to create a user-centric hub where fans can access live
match updates, delve into player profiles, track top scorers, and engage
with customized content. By harnessing technology, we aim to redefine
the soccer experience, providing enthusiasts with an immersive space to
connect, celebrate, and engage with the sport they love.
03
2 BACKGROUND
04
2.8 Live Match Commentary:
Offer real-time match commentary, analysis, and
insights to provide fans with an immersive and informative experience
even if they are unable to watch the game live.
05
3 SCOPE
3.1 Responsive and Engaging User Interface:
·The web application will prioritize a user-centric design, ensuring
responsiveness and optimal display on various devices, including
desktops, tablets, and smartphones.
·Emphasis will be placed on creating an engaging visual interface that
enhances user interaction and encourages extended engagement.
06
3.6 Advanced Search and Filtering Capabilities:
Effortless Data Retrieval: Users will benefit from an advanced
search and filtering system, allowing them to quickly locate
specific game information, player profiles, and relevant content.
Customizable Views: The application will provide options for
users to customize their browsing experience, tailoring search
parameters to their preferences.
07
4. CONSTRAINTS
4.1 Timely Data Updates:
Dependence on external data sources for live scores, player
statistics, and match schedules may result in delays or
inaccuracies.
08
5. PROBLEM STATMENT
5.1 Problem Definition:
"Development of an Immersive Soccer Club Web Application"
09
5.7 User Management and Roles:
The system should support different user roles, such as users and
admins. Admins should have the ability to manage user accounts,
roles, and permissions within the system.
10
6. PURPOSED SOLUTION:
6.1 Project Report:
Problem Definition:
Clear description of the project's purpose and goals
Design Specifications:
Detailed explanation of the application's architecture, features,
and functionalities
Flowcharts and Diagrams:
Visual representations of system processes, user interactions,
and data flows
Data Flow Diagrams illustrating how data moves within the
application
Database Design:
SQL database scripts to create necessary tables and
relationships
12
Data Flow Diagram
Figure 1.2 display the context level diagram of the application
13
Data Flow Diagram
Figure 1.3 display the First level diagram of Data Flow Diagram
Login Dfpd
14
Data Flow Diagram
Figure 1.4 display the context level diagram of the application
15
FLOW CHART
Figure 1.5 display the Flow chart for user Journey
18
Figure 1.8 display the Flow chart for Feedback Submission Flowchart
19
Figure 1.9 display the MVC Class Diagram
ERD DIAGRAM
22
8. TASK ALLOCATION
9.6 Documentation:
Comprehensive documentation covering all aspects of the project
Clear explanations of design decisions, methodologies, and
technologies used
9.7 ReadMe.doc:
List of assumptions made during the project's development
Port settings and other relevant details for running the application
Contact information for support or inquiries
9.9 Screenshots:
Screenshots of working pages, especially if local servers like
XAMPP were used for testing
25
10. FUNCTIONAL RERUIEMENTS
Following list are the major features expected from Soccer Club:
For Users:
10.3 Login:
It will allow successfully registered users to login to the Soccer Club
application and access various features of the application through menus
or sidebars.
10.4 Settings:
Users will be able to manage their accounts by using sub options such as
Create, Update, and Delete Profile. Users can also add addresses using
this option.
10.6 Matches:
This will showcase a list of upcoming matches with essential details such
as date, time, teams, and competition (World Cup, champions’ league
and so on). It should allow users to click a match to access more
information or set reminders.
26
10.7 Players’ Gallery:
This will include the players (categorized by teams). It should provide
player profiles, career statistics, images, and remarkable achievements
by the player.
10.8 Statistics:
This option will display comprehensive statistics for teams, players, and
matches.
10.11 Merchandise:
This option should display various merchandise such as Jerseys/soccer
shoes/Posters of the players and so on and enable user to purchase
them through Add to Cart feature.
10.12 Checkout:
This should show the shopping cart contents and total bill based on
merchandise price and quantity of merchandise purchased. You do not
have to implement payment functionality, just list the cart contents, and
compute the bill.
27
10.14 View Cart:
Users can view their cart through this option.
10.17 Sitemap:
To understand the flow of SoccerClub Web application, you
will have to create a Sitemap and add it to the home page
of your application.
For Admin:
10.18 Login:
It will allow Admin to login to the Web Application.
10.19 Add/Modify/Delete:
It will allow Admin to perform these operations on match
schedules, player details, statistical data, accessories,
orders, and other related information.
10.21 Search/Filter:
These options enable search or filter for a particular
player/match and so on based on specific criteria.
10.22 Sort:
This option enables sorting of data based on specific
criteria.
28
11. Non-Functional Requirements
There are several non-functional requirements that should be fulfilled by the
application.
11•2 Accessible:
The application should have clear and legible fonts, user-interface
elements, and navigation elements.
11•3 User-friendly:
The application should be easy to navigate with clear menus and other
elements and easy to understand.
11•4 Operability:
The application should operate in a reliably efficient manner.
11•5 Performance:
The application should demonstrate high value of performance through
speed and throughput. In simple terms, the application
11•6 Scalability:
The application architecture and infrastructure should be designed to handle
increasing user traffic, data storage, and feature expansions.
11•7 Security:
The application should implement adequate security measures such as
authentication. For example, only registered users can access certain
features.
11•8 Capacity:
The application should support large number of users. • Availability:
The application should be available 24/7 with minimum downtime.
11•9 Compatibility:
The application should be compatible with latest browsers.
29
12. Hardware and Software Requirements
There are several hardware and software requirements that should be fulfilled by the application.
12.1 Hardware
Intel Core i5 Processor or higher
8 GB RAM or higher
Color SVGA
500 GB Hard Disk space
Mouse
Keyboard
12•2 Software:
Technologies to be used
Fronted:
HTML5, CSS3, Bootstrap (optional), JavaScript, Figma Toolkit, jQuery,
AngularJS/Angular 9/ReactJS, and XML
OR C# 7.0 with Visual Studio IDE 2019 or higher, ASP.NET MVC and
Core, and related libraries
Data Store:
MySQL 5.7 or higher/SQL Server 2016 or higher
30
SCREEN SHOT
31
SCREEN SHOT
32
SCREEN SHOT
33
SCREEN SHOT
34
SCREEN SHOT
35
SCREEN SHOT
36
SCREEN SHOT
37
SCREEN SHOT
38
SCREEN SHOT
39
SCREEN SHOT
40
SCREEN SHOT
41
SCREEN SHOT
42
SCREEN SHOT
43
SCREEN SHOT
44
SCREEN SHOT
45
SCREEN SHOT
46
SCREEN SHOT
47
SCREEN SHOT
48
SCREEN SHOT
49
SCREEN SHOT
50
SCREEN SHOT
51
SCREEN SHOT
52
SCREEN SHOT
53
SCREEN SHOT
54
SCREEN SHOT
55
SCREEN SHOT
56
SCREEN SHOT
57
SCREEN SHOT
58
SCREEN SHOT
59
SCREEN SHOT
60
8. TASK ALLOCATION
61
SCREEN SHOT
62
SCREEN SHOT
63
SCREEN SHOT
64
SCREEN SHOT
65
SCREEN SHOT
66
SCREEN SHOT
67
SCREEN SHOT
68
SCREEN SHOT
69
SCREEN SHOT
70
SCREEN SHOT
71
SCREEN SHOT
72
SCREEN SHOT
73
SCREEN SHOT
74
SCREEN SHOT
75
SCREEN SHOT
76
SCREEN SHOT
77
SCREEN SHOT
78
SCREEN SHOT
79
SCREEN SHOT
80