Brains Post Graduate College Chitral Sports Complex Management System

BRAINS POST GRADUATE COLLEGE
Chitral Sports Complex Management System
Submitted by
Zahir Shah
&
Syed Adnan Shah
Supervised by
Mr. Mir Salam
Master of Sciences (Computer Science)

Session 2016-2018
Department of computer science
Brains P.G. College
BRAINS
Opening Minds, Building Futures
Department of computer science

Brains Post Graduate College Peshawar
Affiliated with University of Peshawar
Final year project proposal

Chitral Sports Complex Management System
By:
Name: Zahir Shah
E-mail: peshawarview1@gmail.com
Cell#: 03481942569
Name: Syed Adnan Shah
E-mail: syedaadnanshah1@gmail.com
Cell#: 03469565506
Phase 3 Chowk, Jamrud Road, Peshawar KPK, Ph: 091-5611637, 0336-5700036

www.brains.edu.pk email: info@brains.edu.pk
ABSTRACT
We want to develop a Chitral Sports Complex Management System, where all the data related to
employees, Players are kept centralized and produced to management on demand. All the
requisite reports are electronically.
TOOLS USED
Oracle 11g Database.
Oracle 10g forms builder
1. Forms Builder.
2. Report Builder
3. Developer for interface design
4. Report Converter
5. SQL/SQL Plus
6. Adopted Photoshop.
MS Paint
MS Word for documentation
Operating system: Windows 8.1
Signatures of Candidates:
1: Name: Zahir Shah
Signature: ________________
2: Name: Syed Adnan Shah

Signature: ________________
Recommendation and Signature of Head of the Department:

Name__________________________________________________
Sign & Date_____________________________________________
Recommendation and Signature of the Supervisor:

Name__________________________________________________
Sign & Date_____________________________________________
Recommendation and signature of External Examiner:
Name__________________________________________________
Sign & Date_____________________________________________

PROJECT IN BRIEF
Project Title: Chitral Sports Complex Management System
Undertaken By: Zahir Shah and Syed Adnan Shah
Supervised By: Sir Mir Salam
Starting Month: September 2018
Ending Month: December 2018

DEDICATION
We dedicate our project to our beloved parents who provide us support for surviving
In this world with confidence after almighty Allah. What we are right now, we could never
Be without the love, care and guidance of our parents.
At this moment of time we are very grateful to our entire faculty especially Mr. Mir Salam
Whose teaching, training and guidance helped us gain a lot of knowledge?
Our heartiest gratitude to all the family members and friends who offered us their
Enlightened encouragement and help.
ACKNOWLDEGEMENT
The whole praise is to almighty Allah, the creator of the universe, who made us the super
Creatures, blessed us with knowledge and enabled us to accomplish this work. We feel great
Pleasure in expressing our deepest appreciation and heartiest gratitude to my supervisor, Sir
Mir Salam for his guidance during all the phases of this project.
For his invaluable assistance checking the detail of the material presented in the report and
giving us the vital instruction.
In this regard, we wish to extend the special thanks to him, had he not render his valuable
Technical help and adequate guidance at the most appropriate occasions it would have been
Very difficult for us to achieve this end. We are thankful to Sir Mir Salam their assistance and
Support. We would not be able to complete so nicely and accurately our project without any of
These. At the end we are honored to thank once again Sir Mir Salam.
Table of Contents
CHAPTER 01 .............................................................................................................................................. 1
INTRODUCTION....................................................................................................................................... 1
CHITRAL SPORTS COMPLEX MANAGEMENT SYSTEM ............................................................. 1
CHAPTER 01 .............................................................................................................................................. 2
1.1 Introduction ........................................................................................................................................... 2
1.2 Problem Definition ................................................................................................................................ 2
1.3 Objectives............................................................................................................................................... 3
1.3.1 General Objectives ......................................................................................................................... 3
1.3.2 Specific Objectives ......................................................................................................................... 3
1.4 Project Scope ......................................................................................................................................... 3
1.5 Proposed System ................................................................................................................................... 4
1.5.1 Objectives of the Proposed System ........................................................................................ 4
CHAPTER 02 .............................................................................................................................................. 5
REQUIREMENT ELICITATION ............................................................................................................ 5
CHAPTER 02 .............................................................................................................................................. 6
2.1 Feasibility study .................................................................................................................................... 6
2.1.1 Economic feasibility study ............................................................................................................. 6
2.1.2 Technical feasibility study ............................................................................................................. 6
2.1.3 Logical feasibility study ................................................................................................................. 6
2.2 Functional Requirements ..................................................................................................................... 6
2.2.1 Primary Features .................................................................................................................... 6
2.2.2 Project in Brief ............................................................................................................................... 7
2.2.3 User Interface ................................................................................................................................. 7
2.2.4 Updating.......................................................................................................................................... 7
2.2.5 Reports ............................................................................................................................................ 7
2.2.6 Simple to Use .................................................................................................................................. 7
2.2.7 Deletion ........................................................................................................................................... 7
2.2.8 Storage of Records ......................................................................................................................... 7
2.2.9 Data Integrity ................................................................................................................................. 8
2.2.10 Search Facility .............................................................................................................................. 8
2.3 Non-Functional Requirements ............................................................................................................. 8
2.3.1 Reliability ........................................................................................................................................ 8
2.3.2 Availability...................................................................................................................................... 8
2.3.3 Usability .......................................................................................................................................... 8
2.3.4 Efficiency ........................................................................................................................................ 8
2.3.5 Security ........................................................................................................................................... 8
CHAPTER 03 .............................................................................................................................................. 9
SYSTEM DESIGN ...................................................................................................................................... 9
CHAPTER 03 ............................................................................................................................................ 10
3.1 Introduction ......................................................................................................................................... 10
3.2 Conceptual Design .............................................................................................................................. 10
3.3 Entity Relationship Diagram ............................................................................................................. 10
3.3.1 Basic Constructs or Symbols in ERD ......................................................................................... 10
3.4 Entity Attributes ................................................................................................................................. 12
3.4.1 Users .............................................................................................................................................. 12
3.4.2 Players Registration: ................................................................................................................... 13
3.4.3 Admission...................................................................................................................................... 14
3.4.4 Employee....................................................................................................................................... 15
3.4.5 Coach............................................................................................................................................. 16
3.4.6 Games ............................................................................................................................................ 16
3.4.7 Expenses ........................................................................................................................................ 17
3.4.8 Salary ............................................................................................................................................ 18
3.4.9 Players Account ............................................................................................................................ 19
3.4.10 Players Payment: ....................................................................................................................... 20
3.5 Levels of DFD .................................................................................................................................. 21
3.5.1 Level-0 ........................................................................................................................................... 21
3.5.2 DFD (DATA FLOW DIAGRAM) .............................................................................................. 21
3.5.3 LEVEL-1....................................................................................................................................... 21
3.5.4 DFD (DATA FLOW DIAGRAM) .............................................................................................. 22
3.6 Logical Database Design..................................................................................................................... 22
3.7 Physical Database Design ................................................................................................................... 23
3.8 Tabular Definition of Relation ........................................................................................................... 23
3.8.1 USERS........................................................................................................................................... 23
3.8.2 PLAYERS_REGISTRATION .................................................................................................... 23
3.8.3 ADMISSION ................................................................................................................................ 24
3.8.4 EMPLOYEE................................................................................................................................. 24
3.8.5 COACH......................................................................................................................................... 25
3.8.6 GAMES ......................................................................................................................................... 25
CHAPTER 04 ............................................................................................................................................ 25
TESTING AND IMPLEMENTATION .................................................................................................. 25
3.8.7 EXPENCES .................................................................................................................................. 25
3.8.8 SALARY ....................................................................................................................................... 26
3.8.9 PLAYERS_ACCOUNT ............................................................................................................... 26
3.8.10 PLAYERS_PAYMENT ............................................................................................................. 27
CHAPTER 04 ............................................................................................................................................ 28
TESTING AND IMPLEMENTATION .................................................................................................. 28
CHAPTER 04 ............................................................................................................................................ 29
4.1 SYSTEM TESTING ........................................................................................................................... 29
4.2 TYPES OF TESTING ........................................................................................................................ 29
4.5 TESTING OUR SOFTWARE PERFORMANCE ........................................................................... 29
4.6 STEPWISE TESTING ....................................................................................................................... 30
4.7 COMPLETE PROGRAM TESTING ............................................................................................... 30
4.8 INTERFACE ....................................................................................................................................... 30
4.9 SYSTEM IMPLEMENTATION ....................................................................................................... 30
4.10 INSTALLATION PHASE................................................................................................................ 30
4.11 SYSTEM MAINTENANCE............................................................................................................. 31
4.13 Mapping ERD into Relations ........................................................................................................... 31
4.14 Login Page ......................................................................................................................................... 33
4.15 Main Page .......................................................................................................................................... 34
4.16 Players Registration and Admission Page ...................................................................................... 35
4.17 Game, Coach and Players Account Page ........................................................................................ 35
4.18 Expenses Page.................................................................................................................................... 36
4.19 Employees Form and Salary Page ................................................................................................... 36
4.20 Players Payment Page ....................................................................................................................... 37
4.21 Backup Page ...................................................................................................................................... 37
4.22 Reports Page ...................................................................................................................................... 38
4.23 Admission Fee Detail Report Page .................................................................................................. 38
4.24 Players and Game Detail Report Page ............................................................................................ 39
4.25 Coach Detail Report Page ................................................................................................................ 39
4.26 Salary Detail Report Page ................................................................................................................ 40
4.27 Game and Players Report Page ....................................................................................................... 40
4.28 Expenses Detail Report Page ........................................................................................................... 41
4.29 Single Players Report Page .............................................................................................................. 42
CHAPTER 05 ............................................................................................................................................ 43
CONCLUSION ......................................................................................................................................... 43
CHPATER 05 ............................................................................................................................................ 44
5.1 CONCLUSION ................................................................................................................................... 44
5.2 REFENRECES .................................................................................................................................... 45
CHAPTER 01
INTRODUCTION
CHITRAL SPORTS COMPLEX MANAGEMENT
SYSTEM
CHITRAL SPORTS COMPLEX MANAGEMENT SYSTEM 1

CHAPTER 01 INTRODUCTION
CHAPTER 01
1.1 Introduction
The Chitral Sports Complex is a complex that deals to manage the various sports activities
related to different games like cricket, hockey, squash, gym etc. Its main purpose is to promote
the sports activities in the region and gives a positive environment to the interested sports men.
Chitral Development Authority (CDA) has constructed the Chitral Sports Complex Management
System at the cost of Rs.162.19 million, spread out over a large area 696,960 square feet. The
Chitral Sports Complex Management System (CSCMS) is a desktop application developed for
the Chitral Sports Complex Management System to provide the valuable information about
different entities like Players record, Team management, games schedule, sports expenses etc.
This application covers all the activities performed at sports complex and so can be easily
implemented by any sports complex with minor changes. Any sport complex has yet never used
a Database Management System for managing their data and information. Till now, they rely on
traditional ways for storing and retrieving important data. Designing a Database Management
System for the sports would bring an effective change in the managing system of the sports. It is
an effort for the complex to keep the up to date record of all the going-on and past activities of
different sports. In this project, we have made our best efforts to incorporate all the activities and
processes that are related to different sports, players, games schedules, achievements, teams and
their expenses also. We hope it will be very beneficial for the Chitral Sports Complex and even
for any other Sport Complex.
1.2 Problem Definition

The aim of this stage is to identify and describe the problems. The problems can appear in two
ways.
 First, the organization or department find out itself and also request to analysts to solve
out the solution of this problem.
 Second, the department faces with the system problem such as incorrect reports, delay in
searching a record, and security issue for keeping data.
Other problems related to present playing system are, Second Verifying a player manually is
time consuming.
 Slow process of present system consume a lot of time.
 Preparing final report is not easy.
 Players outside the country or city cannot play using the present system.
 Possibilities of Fraud in present playing system.

1.3 Objectives
Computer is the intense need of today’s modern world. Computer helps us in every sphere of life
from very large scale. In order to meet the needs of the day, it is wished to computerized
systems.
1.3.1 General Objectives

General objective of our project is to change the current manual system of Chitral Sports
Complex into computerized one. This project would be very useful for any sports complex where
they like to keep the players data, team’s data, expenses on player and staff, team’s competition
and their achievements etc.
1.3.2 Specific Objectives

Our project has the following specific objectives.
 To provide fast and in time retrieval of information related to various entities.
 To provide well organized and accurate information about players, games etc.
 To provide information to the management and sports men about games and competitions
 To provide games schedule about various sports
 To provide player information related to various sports
 To provide statistics about games from different area
 To keep the record of achievements
 To keep the expenses record
 To provide an easy interface for the data entry
1.4 Project Scope

The scope of this system comprises of:
1. The main users of the system will be the Chitral Sports Complex Management and
staff to record their sports activities.
2. The players related to different sports will make registration with Chitral Sports
Complex.

3. Latest and updated information will us available for sports managers that will be
communicated to the players in time.
4. Its implementation will enhance the performance of the Sports Complex by having in
time and updated information.
5. The system will solve the problems related to the sports management and players by
providing accurate and reliable reports.
6. The system incorporates the information related to all kinds of sports like Cricket,
Hockey etc.
1.5 Proposed System

After the detailed study of the current system, the next step is to propose a new system. Now a
day’s computer is a leading technology, so we proposed a computerize-based system for the Chitral
Sports Complex, which fulfills all the requirements of the complex easily and solve the problems
faced by the manual system.
The propose system will enhance the efficiency, accuracy, timelessness, security and economy.
This system will help the management to take effective and timely decisions regarding various
sports activities.
1.5.1 Objectives of the Proposed System

 The proposed system is the replacement of the existing system, which is
conventionally effective and useful than the existing manual system.
 The proposed system should be more effective and useful than existing manual
system.
 It should minimize the time involved in processing and retrieval of information.
 It should be error free and provide accurate information.
 The new system should be simple so that its structure, operation and procedure should
be maintained easily.
 The system should be sufficiently flexible, i.e. system should support large amount of
data.
 The system should be user friendly.
 The proposed system should minimize the data redundancy.

CHAPTER 02
REQUIREMENT ELICITATION

CHAPTER 02 REQUIREMENT ELICITAION
CHAPTER 02
2.1 Feasibility study
The following feasibility studies were carried out:
 Economic feasibility study.
 Technical feasibility study.
 Logical feasibility study.
2.1.1 Economic feasibility study

The Feasibility Study provides clients with an extremely detailed, comprehensive analysis of
project feasibility. The study includes a description of the project plan, methodology and
background, products and services offered by the facility, strategic partnerships, a detailed
market analysis, an analysis of comparable facilities, an overview of financial projections, and
recommendations for project development. The Feasibility Study is used by clients seeking the
support of outside funding sources who require a detailed and comprehensive analysis of project
feasibility. The best feasibility advisors leave “no stone unturned” to provide a full feasibility
analysis, arming clients with all the relevant information needed to acquire funding.
2.1.2 Technical feasibility study

Technical feasibility of the system is analyzed and the technical requirements such as software
facilities, procedure, inputs are identified.
2.1.3 Logical feasibility study

Logical possibility, that which is achievable. Feasible region, a region that satisfies mathematical
constraints. Feasibility study, a preliminary study to determine a project's viability
2.2 Functional Requirements

Functional requirements are the product features or its functions that must be designed directly for
the users and their convenience. They define the functionality of the software, which the software
engineers have to develop so that the users could easily perform their tasks up to the
business requirements.
2.2.1 Primary Features

 To develop user friendly system.

 To have the latest and updated data

 To minimize the possibility of data redundancy.
 To facilitate the process of insertion, updating of data files.

 To provide fast searching.
2.2.2 Project in Brief

Sports Complex is located in Chitral. In sports complex players are played different games
Such as football, cricket, hockey, squash and also indoor games. The requirements in sports hall
should relate to level of play categories for the particular activities. Some games are required
more space for safety of zones and other margins around the playing area and some games are
required a minimum space area for playing games.
2.2.3 User Interface

We have made our efforts to provide user-friendly interfaces to end-users in our proposed system
so that the users interact with the system without any problems. For this purpose, interactive input
screens are designed. It will make data entry session simple and attractive
2.2.4 Updating
The system allows the user to make any kind of updating in data or records.
2.2.5 Reports
The proposed system will produce different reports, which will be helpful to the
stakeholders.
2.2.6 Simple to Use

The proposed system required little training or no training for its operation, because it is user
friendly.
2.2.7 Deletion
The system also provide facility for deleting a record.
2.2.8 Storage of Records

The system can store much data as computer memory allows. Once the record is entered, it will
remains there forever until user removes it.

2.2.9 Data Integrity

There is a great chance of errors in present system, which results data inefficiency. In the
proposed system data validation checks and constraints eliminate the chances of errors and
enhances the level of data integrity.
2.2.10 Search Facility

In proposed system different search facilities are provided such as search by name, search by
CNIC and search by contact number.
2.3 Non-Functional Requirements

A non-functional requirement is a requirement that specifies criteria that can be used to judge the
operation of a system, rather than specific behaviors. They are contrasted with functional
requirements that define specific behavior or functions.
2.3.1 Reliability
The new system will be more reliable than existing system. Due to its accurate, security.
2.3.2 Availability
In the context of a computer system, refers to the ability of a user to access information or
resources in a specified location and in the correct format.
2.3.3 Usability
The extent to which a product can be used by specified users to achieve specified goals with
effectiveness, efficiency and satisfaction in a specified context of use.
2.3.4 Efficiency
Efficiency is defined as the economic utilization of available resources for achieving a desired
objective so that proposed system is more efficient that existing one.
2.3.5 Security
Data security refers to the process of protecting data from unauthorized access and data corruption
throughout its lifecycle. Data security includes data encryption, tokenization, and
key management practices that protect data across all applications and platforms. Data is
recognized as an important corporate asset that needs to be safeguarded. Loss of information can
make is in danger. Data security is that why very important.

CHAPTER 03
SYSTEM DESIGN

CHAPTER 03 SYSTEM DESIGN
CHAPTER 03
3.1 Introduction
In this chapter we are going describe the Logical Database design and then Physical design. Local Database
design is the process of converting conceptual data model into logical model. Once we succeeded in
designing logical database design, then we will proceed for Physical design.
3.2 Conceptual Design

After collecting the database requirements in the elicitation, the conceptual design phase starts. It
takes the requirements and produces high-level data model of the database structure. It is the
abstract representation of data needed for business process or project or organization.
The conceptual model of database provides an external or user view of the organization’s data in
terms of entities and relationship among them. This user view is very helpful in designing the
logical and physical models of the database. The most common standard for conceptual model is
entity relationship diagram.
3.3 Entity Relationship Diagram

An ER-diagram is a visual representation of data that describes how data is related to each other.
In this diagram, we depict that how the entities are related to each other, showing different types
Of relationships visually. It provides a relational schema of database in graphical form that can
serve as a road-map or foundation for developing relational database.
3.3.1 Basic Constructs or Symbols in ERD
 Entity
Strong Entity
Weak Entity
 Relationship

Associated Entity
One to One relationship
One to Many relationships
Many to Many relationships
Optional Mandatory
 Attributes
Single Value Attribute
Multi Value Attribute
Primary Key Primary key

3.4 Entity Attributes

3.4.1 Users
User Name Password
Users
Figure 3.4.1 Entity of Users
User Name and User Password

3.4.2 Players Registration:
Father Name CNIC Cell NO
Address
Name Picture
Player_ID Emp_ID
Players Registration
Figure 3.4.2 Players Registration
Players Registration information with their entity and attributes.

3.4.3 Admission
Security Date of Admission Security Refundable
Discount
Admission fee
Net amount
Player_id
Remarks
Admission
.
Figure 3.4.3 Admission
Admission information with their entity and attributes.

3.4.4 Employee
CNIC Job Hiredate
SAL
Emp_nam
e
COMM
Emp_id
Employee
Figure 3.4.4 Employee
Employee information with their entity and attributes.

3.4.5 Coach
Emp_Id
Joining date
Leaving Date
Game_Id
Coach
Figure 3.4.5 Coach
Coach information with their entity and attributes.
3.4.6 Games Game_id Games Name
Games
Figure 3.4.6 Games
Game information with their entity and attributes.

3.4.7 Expenses
Expenses information with their entity and attributes.
Expenses Date
Amount Expenses Type
Title
Emp_Id
Expences_Id
Expenses
Figure 3.4.7 Expenses

3.4.8 Salary
Salary information with their entity and attributes.
Month of Year
Payment Date Medical Allowance

Basic Pay
SALARY_ID
Transport Allowance
EMP_ID
Salary
Figure 3.4.8 Salary

3.4.9 Players Account

Player Account information with their entity and attributes.
Monthly Payment
Account Status
Starting Date
Game_Id
Ending Date
Player_Id
Remarks
Players Account
Figure 3.4.9 Players Account

3.4.10 Players Payment:

Players Payment information with their entity and attributes.
On Account Payment Date
Amount
Receip_Id Month of Year
Player_Id
Gam_ Id
Players Payment
Figure 3.4.10 Players Payment

3.5 Levels of DFD

3.5.1 Level-0
 This is also called functional model. In this level we define the following.
 All external entities.
 All I/O data.
 The system is represented as one process in a bubble.
 No data store
3.5.2 DFD (DATA FLOW DIAGRAM)
Login Form Software System

And
Entities/Search
Internal
Backup Operation
Reports
3.5.3 LEVEL-1
In this to extend the below processes.
o All external entities.
o All I/O data
o More processes.
o All data store.

3.5.4 DFD (DATA FLOW DIAGRAM)

Main Page
Yes Authentication Login
Entries Section
NO
Reject
Players Registration
Admission
Employee
Save, Delete
Coach
And
Games
Insert, Update
Expenses
Salary
Players Account
Players Payment
3.6 Logical Database Design

Logical Database design is the process of converting the conceptual schema into a logical schema.
This model adds more detail to the conceptual model but it is still generic as it is not bound to a
specific platform or DBMS. This process involves translating ER diagrams into relations, adding
primary and foreign keys accordingly. The process of normalization is also performed in this
model.

The main emphasis in this phase is to ensure data consistency and remove anomalies in the
database to be developed. This model accurately renders a visual representation of the activities
and data relevant to a particular business. It is used to determine whether the requirements of the
project have been completely gathered or not?
3.7 Physical Database Design

Physical database design is used to translate the logical schema into the technical specifications
for storing and retrieving data. It adds platform-specific detail to the logical model of database.
The main emphasis of this design is to create tables, indexes and snapshots. Constraints are also
defined, including primary keys, foreign keys, Null constraint, default constraints etc. The goal
of physical database design is to create such a design of data that will provide adequate
performance and ensure database integrity, security etc. Further it will meet all the demands of
end-users.
3.8 Tabular Definition of Relation

We can describe the tabular definition of relations as given the following in figures.
3.8.1 USERS
Field Name Data type Size Description Constraint
User Name Varchar2 30 User Name
User_Password Varchar2 30 User_Password PK
3.8.2 PLAYERS_REGISTRATION
Player_Id Number PLAYER_ID PK
Name Varchar2 40 Name
Father Name Varchar2 40 Father Name
CNIC Varchar2 16 CNIC
Address Varchar2 40 Address
Cell No Varchar2 20 Cell No
Picture Long Raw Picture

Emp _d Number Emp_Id FK
3.8.3 ADMISSION
Player_Id Number Player_Id FK
Admission Fee Number Admission Fee
Discount Number Discount
Security Number Security
Date of Varchar2 20 Date of

Admission Admission
Net Amount Number Net Amount
Remarks Varchar2 40 Remarks
Security Varchar2 20 Security

Refundable Refundable
3.8.4 EMPLOYEE
EMP_ID NUMBER EMP_ID PK
EMP_NAME VARCHAR2 40 EMP_NAME
CNIC VARCHAR2 16 CNIC
JOB VARCHAR2 20 JOB
HIREDATE DATE HIREDATE
SALARY NUMBER SALARY
COMMITION NUMBER COMMITION

3.8.5 COACH
Game_Id Number Game_Id FK
Emp_Id Number Emp_Id FK
Joining Date Date Joining Date
Leaving Date Date Leaving Date
3.8.6 GAMES
Game_Id Number Game_Id PK
Game Name Varchar2 30 Game Name
3.8.7 EXPENCES
Expences_Id Number Expences_id PK
Title Varchar2 40 Title
Amount Number Amount
Expense Date Date Expense Date
Expense Type Varchar2 20 Expense Type

3.8.8 SALARY
SALARY_ID Number SALARY_ID PK
Basic_Pay Number Basic_Pay
Payment date Date Payment Date
Month of Year Varchar2 20 Month of Year
Medical Varchar2 20 Medical

Allowance Allowance
Transport Varchar2 20 Transport

Allowance Allowance
3.8.9 PLAYERS_ACCOUNT
Account Status Varchar2 40 Account status
Monthly Varchar2 20 Monthly

Payment Payment
Starting Date Date Starting Date
Ending Date Date Ending Date
Remarks Varchar2 40 Remarks

3.8.10 PLAYERS_PAYMENT
Receipt_Id Number Receipt_Id PK
Amount Number Amount
On Account Varchar2 20 On Account
Payment Date Date Payment Date
Month of Year Varchar2 20 Month of Year

CHAPTER 04
TESTING AND IMPLEMENTATION

CHAPTER 04 TESTING AND IMPLEMENTATION
CHAPTER 04
4.1 SYSTEM TESTING

During this phase it is tested that whether system works properly or not. This phase is also done
to check whether there is any errors in the system. Here the performance, quality, work, are
checks. Testing is very important phase because it is done to make a software workable and
acceptable to user.
4.2 TYPES OF TESTING

There are two types of testing.
 BLACK BOX TESTING
In the black box testing we test the external behavior of the software to ensure that the
software we developed fulfill all the requirement of the customer. Thus in this testing the
software is tested by inputting some data and outputs are checked.
 WHITE BOX TESTING
In this testing, we test the internal of the software by examining the control structure such
as loops, action paths etc.
4.5 TESTING OUR SOFTWARE PERFORMANCE

The following test in our software.
 First of all we tested the functions of each individual button in different forms, this type of
testing id known as unit testing
 After this we checked and tested the functions of each forms in our software, and then after
that we tested all the software for function by providing different types of input data and
we got the correct result. This type of testing is known as integration testing.
In these two type of testing we used both techniques that are white box testing and black box
testing.

4.6 STEPWISE TESTING

In stepwise testing each module, used in the program is tested with the dummy values as well as
the original data. It will ensure that the selected module is free of errors.
4.7 COMPLETE PROGRAM TESTING

After testing each module individually, it has necessary to test the whole program.
So after completing the program each form is tested completely by applying the pretend
Data to it. All the controls, options and menus have been tested separately and they are working
correctly and there is no error in these controls. Now, the program is in position to implement.
4.8 INTERFACE
Interface is a medium that is use to import master data like players, games from external system
into internal system tables. Also to retrieve data from table into forms. For this oracle provide
these flexible tools. In interface we are trying to build the software from those data that we have
collected from analysis.
4.9 SYSTEM IMPLEMENTATION

Implementation is a process of converting a new or revised system design into an operational one.
Implementation allows user to take over its operation for user and evaluation. It involves training
The user to handle system and plan for a smooth conversion. The purpose of implementation phase
is to smoothly convert from the old system to new system.
Implementation has the following phases.
4.10 INSTALLATION PHASE

Most of the soft wares require that first to install them on computer. It is an act to make a program
ready for execution.
The following are the principle objectives of the installation phase.
 Existing system is prepared with the new, tested and documented system. This replacement
assumes user acceptance and ongoing user responsibilities for the system.
 Second to maximize the potential benefits of the new system.

4.11 SYSTEM MAINTENANCE

Maintenance is very important for a software because it make a software more flexible. It is a
process that is use to update a software to its new version. Adding new feature to software for
user. Maintenance is also use to correct errors.
4.12 Tool used in Project

 Oracle 11g
 Oracle 10g
 SQL
 SQL PLUS
 Window 8.1
 Form Builder
 Reporter Builder
 Report Converter
 Case Studio
4.13 Mapping ERD into Relations

In this step, the Entity Relationship Diagram constructed in chapter 2 from the requirements
elicitation is converted into relations, showing the primary keys and foreign keys and relationships
among them. Once this schema is obtained, then it can easily be converted into physical database
design

Figure of Entity Relationship Diagram

4.14 Login Page
Figure 4.14 Login Page

4.15 Main Page
Figure 4.15 Main Page

4.16 Players Registration and Admission Page
Figure 4.16 Players Registration and Admission Page
4.17 Game, Coach and Players Account Page

Figure 4.16 Game, Coach and Players Account Page
4.18 Expenses Page
Figure 4.18 Expenses Page
4.19 Employees Form and Salary Page

Figure 4.19 Employees Form and Salary Page
4.20 Players Payment Page
Figure 4.20 Players Payment Page
4.21 Backup Page

Figure 4.21 Backup Page
4.22 Reports Page
Figure 4.22 Reports Page
4.23 Admission Fee Detail Report Page

Figure 4.23 Admission Fee Detail Report Page
4.24 Players and Game Detail Report Page
Figure 4.24 Players and Game Detail Report Page
4.25 Coach Detail Report Page

Figure 4.25 Coach Detail Report Page
4.26 Salary Detail Report Page
Figure 4.26 Salary Detail Report Page
4.27 Game and Players Report Page

Figure 4.27 Game and Players Report Page
4.28 Expenses Detail Report Page
Figure 4.28 Expenses Detail Report Page

4.29 Single Players Report Page
Figure 4.29 Single Player Detail Report Page

CHAPTER 05
CONCLUSION

CHAPTER 05 CONCLUSION
CHPATER 05
5.1 CONCLUSION
We made this project for Chitral Sports Complex Management System. It is a desktop application
software. This project has incorporated all the features to meet the demands of management and
sportsman.
Similarly on this project, the stack holder can search and view for the desired information about
chitral sports complex management system. Admin can add, delete and update the details of chitral
sports complex management system. Our project is useful project like the others project and we
are trying to make this project more advance for the features.
We are in confident that our system is efficient, reliable and responsive while performing the
routine business process. However, it is universal truth that none of the system is perfect. Our
system also has some limitations, one of which is that it does not provide online facility to the
sportsmen. In future, it can be made as online application that will be very helpful for the players
to apply for online registration.

5.2 REFENRECES
 Kevin, L., & Bob, B. (2010). Oracle Database 10g: the Complete Reference. The
McGraw2Hill Companies Inc., US, 423, 457.
 Gould, H. (2015). Database design and implementation: A practical introduction
using Oracle SQL.
 https://www.google.com
 https://www.youtube.com
 https://www.wikipedia.com
 https://www.techopedia.com
 https://www.w3schools.com/sql/


Brains Post Graduate College Chitral Sports Complex Management System

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Brains Post Graduate College Chitral Sports Complex Management System

Uploaded by

Copyright:

Available Formats

BRAINS POST GRADUATE COLLEGE

Chitral Sports Complex Management System

Master of Sciences (Computer Science)

Department of computer science

Final year project proposal

Phase 3 Chowk, Jamrud Road, Peshawar KPK, Ph: 091-5611637, 0336-5700036

2: Name: Syed Adnan Shah

Recommendation and Signature of Head of the Department:

Sign & Date_____________________________________________

Recommendation and Signature of the Supervisor:

Sign & Date_____________________________________________

Recommendation and signature of External Examiner:

Sign & Date_____________________________________________

Project Title: Chitral Sports Complex Management System

Undertaken By: Zahir Shah and Syed Adnan Shah

Supervised By: Sir Mir Salam

Starting Month: September 2018

Ending Month: December 2018

CHITRAL SPORTS COMPLEX MANAGEMENT SYSTEM 1

1.2 Problem Definition

CHITRAL SPORTS COMPLEX MANAGEMENT SYSTEM 2

1.3.1 General Objectives

1.3.2 Specific Objectives

1.4 Project Scope

CHITRAL SPORTS COMPLEX MANAGEMENT SYSTEM 3

1.5 Proposed System

1.5.1 Objectives of the Proposed System

CHITRAL SPORTS COMPLEX MANAGEMENT SYSTEM 4

CHITRAL SPORTS COMPLEX MANAGEMENT SYSTEM 5

2.1.1 Economic feasibility study

2.1.2 Technical feasibility study

2.1.3 Logical feasibility study

2.2 Functional Requirements

2.2.1 Primary Features

CHITRAL SPORTS COMPLEX MANAGEMENT SYSTEM 6

 To have the latest and updated data

 To facilitate the process of insertion, updating of data files.

2.2.2 Project in Brief

2.2.3 User Interface

2.2.6 Simple to Use

2.2.8 Storage of Records

CHITRAL SPORTS COMPLEX MANAGEMENT SYSTEM 7

2.2.9 Data Integrity

2.2.10 Search Facility

2.3 Non-Functional Requirements

CHITRAL SPORTS COMPLEX MANAGEMENT SYSTEM 8

CHITRAL SPORTS COMPLEX MANAGEMENT SYSTEM 9

3.2 Conceptual Design

3.3 Entity Relationship Diagram

3.3.1 Basic Constructs or Symbols in ERD

CHITRAL SPORTS COMPLEX MANAGEMENT SYSTEM 10

One to One relationship

One to Many relationships

Many to Many relationships

Single Value Attribute

Multi Value Attribute

Primary Key Primary key

CHITRAL SPORTS COMPLEX MANAGEMENT SYSTEM 11

3.4 Entity Attributes

User Name Password

Figure 3.4.1 Entity of Users

User Name and User Password