Sport.net(2).doc

1
A
Project Report
On
Project Title
Sport Management System
Submitted in partial fulfillment of their requirements for
the award of the Three-Year Diploma in
Computer Science
Under the supervision of
Er. Akash Datt Pathak
Arcane Programming Infotech (p) Ltd.
Lucknow (up)
Submitted By:-
Name………
Submitted To:-
Government Polytechnic Madhogarh

2
PREFACE
“Necessity is Mother of All Inventions”
Online training is an important part of the engineering curriculum. The Diploma
course Online training helps a student in getting acquainted with the manner in
which his/her knowledge is being practically used outside his/her institute and this
is normally different from what he/she has learnt from books. Hence, when the
student switches from the process of learning to that of implementing his/her
knowledge, he/she finds an abrupt change. This is exactly why online training
session during the B.E curriculum becomes all the more important. Online training is
prescribed for the student of Technical College as a part of the four-year degree
course of engineering by the AICET. We are required to undergo online training for
a period of 45 days after the completion of the 2nd year.
This training report describes in detail the training after the 3rd year session, which I
completed at the Arcane Programming Infotech (P.) Ltd. This report also gives the
information about the organization and it’s working along with the project
undertaken in the training period.
The fundamental step used in SDLC process is based on the ISO 9001 guidelines.
My aim was to follow the ISO guidelines and develop a perfect system.
The system development was organized into 5 major parts:
1. Requirement Gathering
2. Documentation/Design
3. Development
4. Coding
5. Testing

3
Candidate Declaration
I hereby certify that the work which is being presented in the project entitled “Sport
Management System ” in partial fulfilment of the requirement for the award of the diploma
Government Polytechnic Madhogarh is an authentic record of my own work carried out
under the supervision Er. Akash Datt Pathak, Lecturer (IT), Department of
…………………...
The matter presented in this report has not been submitted by me for the award of any
other diploma of this or any other institute /university.
Name…………..
This is to certify that the above statement made by the candidate is correct to the best of
my knowledge.
Date: Er. Akash Datt Pathak
(Project Supervisor)
The Diploma in Computer Science Viva-Voice examination of Name…. Polytechnic
students, has been held on ……………………………………..
Signature of Supervisor Signature of HOD (IT) Signature of External
Examiner

4
Certificate
This is to certify that the project report entitled “Sport Management System”
submitted by Name…….. in partial fulfillment of the requirements for the award of Diploma
in Government Polytechnic Madhogarh is an authentic work carried out by her under my
supervision and guidance.
Date: Er. Akash Datt Pathak
(ProjectSupervisor)
To the best of my knowledge, the matter embodied in the project report has not been
submitted to any other university / institute for the award of any Diploma.
Date: Name……
Acknowledgement
I would like to express my deep and sincere gratitude to my supervisor Er. Akash Datt
Pathak (Arcane Programming Infotech (p) Ltd.) who gave me his full support and
encouraged me to work in an innovative and challenging project for Educational field. His
wide knowledge and logical thinking gave me right direction all the time. I am deeply
grateful my project coordinator for his/her help and support provided at every step of the
project. Last but not the least, I thank to all employees of Arcane Programming Infotech
(p) Ltd. for their support and co-operation.
Name……..

5
Enrollment No: API/VT20/11 Certificate No:11
COMPLETION CERTIFICATE
This is to certify that Mr/ Miss. Name……. of Diploma (Information
Technology) from Government Polytechnic Madhogarh was working on the
project entitled “Sport Management System” in Arcane Programming
Infotech (P.) Ltd. He/She was engaged with us during 25 May to 10 July for a
period of 45 days.
He/She has done an excellent job during his/her engagement with the Software
Development & Testing Division of the company. He/She has completed
his/her project during the training tenure. His/her performance has been good
and satisfactory.
I would like to take this opportunity to express my appreciation to Mr/Miss
Name……. for his/her work and wish him/her all the very best for his/her
future endeavours.
Regards:
Er. Akash Datt Pathak
Project Manager
Arcane Programming Infotech
Lucknow(U.P.)
arcanepinfotech@gmail.com
Apinfotech.org

6
INDEX
1. Introduction………………………………………………………………………
2.
1.1 Overview of Organization
1.2 Objectives
1.3 Existing System Description
1.4 Proposed System
1.5 Tools Used
2. System Analysis…………………………………………………………………
2.1 Objective
2.2 SDLC Phases
2.2.1 Feasibility Study
2.2.2 Report Approval
2.2.3 System Analysis
2.2.4 System Design
2.2.5 Coding
2.2.6 Testing
2.2.7 Implementation
2.2.8 Maintenance
2.3 Process Description
2.4 Project Model Used
2.5 ER-Diagram
2.6 Data Flow Diagram
3. Software Requirement Specification………….………………………………
3.1 Hardware Requirement

7
3.2 Software Requirement
3.3 Support Maintenance
4. System Design
Approach…………………………………………………………
4.1 Top-Down Designing
4.2 Bottom –Up Designing
4.3 Following Approach
5. Low Level Design…………………………………………………………………………
5.1 Description of Classes and Methods
6. Data Modeling……………………………………………………………………
6.1 List of Tables
6.2 Structure of Tables
7. Testing………………………………………………………………………………
8. Input-Output Forms………………………………………………………………
8.1 Modularization Details
8.2 User Screenshots
8.3 Admin Screenshots

8
9. Future Scope………………………………………………………………………
10. Conclusion……………………………………………………………………….

9
CHAPTER: INTRODUCTION
Main aim in developing Sport Management System is to provide an easy way not only to
automate all Functionalities of a college, but also to provide full functional reports to top
management of college with the finest of details about any accept of college. Sport
Management System deals with all kinds of students details, academic related reports,
college details, game details, curriculum, batch details and other resource related details
too. It tracks all the details of a student from the day one to the end of each of course which
can be used for all reporting purpose, tracking of attendance, progress in the course,
completed semester years, coming semester years curriculum details, exam details, project
or any other assignment details, final year exam result; and all these will be available for
future references too. Our program will have the database of Courses offered by the college
under all levels of graduation or main streams, teacher or batch execution details, student
details in all aspect.
This program can facilitate us explore all the activities happening in the college, even we can
get to know which teacher/faculty is assigned to which batch, the current status of a batch,
attendance percentage of a batch and upcoming requirement of a batch. Different reports
and Queries can be generated best of vast option related to students, batch, game,
teacher/faculty, exams, semester, certification and even for the entire college.

10
OBJECTIVES

The main objective of Consultancy is to make easy for Students to get all the
information about college. It acts as a mediator between the Students and
Teachers/Faculty.

The objective of the application is to develop a system using which Students and
Teachers/Faculty can communicate with each other.
➢ Username and password is given for each Students and teacher so that the
messaging servlet recognizes them as user. Multiple logins with same identity is not
allowed.
➢ Students can search for information by the help of this website any time anywhere
and also apply If user complaint is reasonable, we will attempt to secure a
satisfactory resolution for user.
➢ Easily accessible from any corner of the world if you have internet connection.
PROBLEM DEFINITION
In this section we shall discuss the limitation and drawback of the existing system that forced us to
take up this project. Really that work was very typical to manage the daily errors free records and
adding or removing any node from server. This problem produces a need to change the existing
system. Some of these shortcomings are being discussed below: -
 Low Functionality
With the existing system, the biggest problem was the low functionality. The
problem faced hampered the work. For small task like adding any new node to

11
server or deleting a node or keeping daily record we have to appoint minimum two
or three employee.
 Erroneous Input and Output
In the existing system, humans performed all the tasks. As in the human tendency,
error is also a possibility. Therefore, the inputs entered by the Students who is
Studying in the College, in the registers may not be absolutely foolproof and may be
erroneous. As a result of wrong input, the output reports etc. Will also be wrong
which would in turn affect the performance.
 Portability Problem
System that existed previously was manual. As a result, the system was less portable.
One has to carry the loads of many registers to take the data from one place to
another. A big problem was that the system was less flexible and if we wanted to
calculate yearly or monthly maintenance report or efficiency report, then it was a big
headache.
 Security-
Security concerns were also one of the motives of the College for the need of
software. In the registers, the data is not secure as anybody can tamper with the
data written in the registers. While in this software, just a password makes it
absolutely secure from the reach of unauthorized persons.
 Data Redundancy
In the case of manual system, the registers are maintained in which, a lot of data is
written.
• Processing Speed
In manual system maintaining a register and performing the necessary calculation
has proved to be troublesome Information, which takes a lot of time and may affect
the performance of the College. But with this software we can have all the tasks

12
performed in a fraction of second by a single click thus making the troublesome job
much easier.
• Manual Errors
When a number of tough tasks are prepared by the humans like preparation of
reports, performing long calculation then some human error are obvious due to a
number of factors like mental strain, tiredness etc. But as we all know that computer
never get tired irrespective of the amount of work it has to do. So this software can
nullify the probability of manual error that improve the performance.
 Complexity in Work
In manual system whenever a record is to be updated or to be deleted a lot of cutting
and overwriting needs to be done on the registers that are concerned that are deleted
or updated record, which makes the work very complex.
EXISTING SYSTEM DESCRIPTION
The existing system of Government Polytechnic Madhogarh is to manage the relationship
with User members by storing the user data in registers. The existing system has following
drawbacks:
Time Consuming
Manual Errors
Complexity
Low Security
Data Redundancy
Portability
No more helpful to improve business.
PROPOSED SYSTEM
The proposed system of Government Polytechnic Madhogarh can also be known as Non-
governmental Organization website, because we will use the new technology for managing
the relationship with user’s , like as web technology.

13
We proposed complete website solution for the application to create a “User
Relationship Management” website. The iterative, time bound approach adopted by
Government Polytechnic Madhogarh address the client requirements that are as follows:
 Define To- Be processes

i. Come up with the solution of the existing problem
ii. Go through the regressive reviews by different business process
iii. Prepared user interface requirements
 Develop High Level Design and Low Level Design before Execution
iv. Built and design all the processes required by Client
v. Conducted survey of all Courier services Dealing Websites and
documented realities
vi. Developed the architecture of the Software Solution
vii. Developed the project design in detail for the software developer in company
SYSTEM ANALYSIS
OBJECTIVE:
➢
The main objective of Consultancy is to make easy for Students to get all the
information about the college.. It acts as a mediator between the Students and
Teachers/faculty.
➢
The objective of the application is to develop a system using which Students and
Teachers/Faculty can communicate with each other.
➢
Username and password is given for each user so that the messaging servlet recognizes
them as user. Multiple logins with same identity is not allowed.
➢
User can search Information by the help of this website any time anywhere and also
apply.

14
➢
If user complaint is reasonable, we will attempt to secure a satisfactory resolution for
user.
➢
Easily accessible from any corner of the world if you have internet connection.
1 `
Phases:
System Development Life Cycle (SDLC) mainly consists of the following 7 phases which can
be detailed:-
Preliminary Investigation: -
This is the first phase of the system development life cycle. In this phase we tend to find
out the needs of the client –what exactly does the client want? Before the development of
any system the important point is to know the needs, objectives and scope of the system
Feasibility Study:-
Feasibility study is the second step of the system development life cycle. Things are always
easy at the beginning in any software process. In fact nothing is in feasible with unlimited
time and resources. But it is not the fact. So, practically we have to do in limited resources in
a restricted time margin. So for the system to be feasible, following points we have to
consider.
The feasibility study is conducted to check whether the candidate system is feasible. The
system which is selected to be the best against the criteria is there after designed and
developed. The feasibility study takes in to consideration, the risks involved in the project
development beforehand. Therefore in this phase we have to do feasibility study which is
the test of the website according to its work ability, impact on the organization, ability to
meet user need and effective use of resources. We do the feasibility study for website to
analyze the risks, costs and benefits relating to economics, technology and user organization.
There are several types of feasibility depending on the aspect they cover. Import of these
includes:
Technical Feasibility:

15
This is an important outcome of preliminary investigation. It comprise of following
questions:-
 Can the work of project bed one with the current equipment, existing software and
available man power resource?

 If Technology is required what are the possibilities that it can be developed?
Economic Feasibility:
It deals with question related to the economy. It comprise of the following questions:-
 Are there sufficient benefits in creating the system to make the cost acceptable?

 Are the costs of not creating the system so great that the project must be undertaken?
Legal Feasibility:
It deals with the question related to the legal issues. It comprise of the following questions: -
 Contract Signing

 Software License agreement

 Issues related to cyber laws.

 Legal issues relating to the man power contract.
Operational Feasibility:
The operational feasibility consists of the following activity: -
 Will the system be useful if it is developed &implemented?
 Will there be resistance from employee?
Social & Behavioral Feasibility:
It deals with the various issues related to the human behavior like: -
 Whether the user be able to adapt a new change or not?
 Whether the ambiance we are providing suits the user or not?

16
Request Approval: -
Request approval is the third phase of system development lifecycle. Request approval is
the phase in which all the requirements which would be provide in the system are stated.
The request approval is a sort of agreement between the client and the company which is
building this software. Both the parties should be mutually agreed on the stated
requirements.
System Analysis:-
System analysis is the phase following the phase of the request approval. In this phase we
tend to analyze the overall system which we have to build. System analysis is the crucial
part in SDLC.
System Design:-
System design means the designing of the system. The System can be done in either of the
following two ways:-
 Logical System Design

 Physical System Design
Coding:-
Coding is the phase in which a developer codes using any programming languages. Coding
constitutes only20 % of the whole project and which is easier to write. The coding work is also
done in the teams; development of the system is usually done under the modular programming
style, which can be either top-down approach or bottom-up approach.
Testing:-
Testing is the phase in which the system that has been developed is tested. Testing
comprises of the 60%ofthe overall development of the system. Testing of the system is
important because testing aims to uncover the different errors in the system. There are
various different testing techniques that can be used for the testing of the system.
Implementation:-
Implementation process involved the installation of software on user’s side.
Implementation process actually depends on type of a system & various. Opting for

17
suitable conversion approach is a step implementation. The conversion processes are as
follows:-
 Parallel Conversion
 Direct Conversion Approach
 Pilot Conversion Approach
 Phase In Conversion Approach
Maintenance: -
Merely developing the system is not important but also maintenance is important.
The company that has built the system provides for some time free of cost
maintenance to the client and after that period it is usually a paid service.

18
Process Description
Gantt charts mainly used to allocate resources to activities. The resources allocated to
activities include staff, hardware, and software. Gantt charts (named after its developer Henry
Gantt) are useful for resource planning. A Gantt chart is special type of bar chart where each
bar represents an activity. The bars are drawn along a timeline. The length of each bar is
proportional to the duration of the time planned for the corresponding activity.
Gantt chart is a project scheduling technique. Progress can be represented easily in a Gantt
chart, by coloring each milestone when completed. The project will start in the month of
January and end after 4 months at the beginning of April.
PROJECT MODEL USED
Iterative Enhancement Model
➢ This model has the same phases as the waterfall model, but with fewer restrictions.
Generally the phases occur in the same order as in the waterfall model, but they may
be conducted in several cycles.
➢
Useable product is released at the end of the each cycle, with each release providing
additional functionality. Customers and developers specify as many requirements as
possible and prepare a SRS document. Developers and customers then prioritize these
requirements. Developers implement the specified requirements in one or more cycles
of design, implementation and test based on the defined priorities.
➢
The procedure itself consists of the initialization step, the iteration step, and the
Project Control List. The initialization step creates a base version of the system. The
goal for this initial implementation is to create a product to which the user can react.
It should offer a sampling of the key aspects of the problem and provide a solution
that is simple enough to understand and implement easily. To guide the iteration
process, a project control list is created that contains a record of all tasks that need to
be performed. It includes such items as new features to be implemented and areas of
redesign of the existing solution. The control list is constantly being revised as a
result of the analysis phase.

19
The iteration involves the redesign and implementation of iteration is to be simple,
straightforward, and modular, supporting redesign at that stage or as a task added to the
project control list. The level of design detail is not dictated by the iterative approach. In a
light-weight iterative project the code may represent the major source of documentation of
the system; however, in a critical iterative project a formal Software Design Document may
be used. The analysis of an iteration is based upon user feedback, and the program analysis
facilities available. It involves analysis of the structure, modularity, usability, reliability,
efficiency, & achievement of goals. The project control list is modified in light of the analysis
results.
PHASES:
Incremental development slices the system functionality into increments (portions). In each
increment, a slice of functionality is delivered through cross-discipline work, from the requirements to
the deployment. The unified process groups increments/iterations into phases: inception, elaboration,
construction, and transition.
• Inception identifies project scope, requirements (functional and non-functional) and risks at a
high level but in enough detail that work can be estimated.
• Elaboration delivers a working architecture that mitigates the top risks and fulfills the non-
functional requirements.
• Construction incrementally fills-in the architecture with production-ready code produced from
analysis, design, implementation, and testing of the functional requirements.
• Transition delivers the system into the production operating environment.

20
ER-Diagram
Introduction: -
In software engineering, an entity-relationship model (ERM) is an abstract and
conceptual representation of data. Entity-relationship modeling is a database
modeling method, used to produce a type of conceptual schema or semantic data
model of a system, often a relational database, and its requirements in a top-down
fashion. Diagrams created by this process are called entity-relationship diagrams, ER
diagrams, or ERDs. ER Diagrams depicts relationship between data objects. The
attribute of each data objects noted in the entity-relationship diagram can be
described using a data object description. Entity relationship diagram is very basic,
conceptual model of data and it is fundamental to the physical database design. This
analysis is then used to organize data as relations, normalizing relations, and
obtaining a Relational database.
The entity-relationship model for data uses three features to describe data. These are:
1. Entities which specify distinct real-world items in an application.
2. Relationship, which connect entities and represent meaningful dependencies
between them.
3. Attributes which specify properties of entities & relationships.
E-R Diagram

21
Data Flow Diagram
Introduction: -
DFD is an acronym for the word Data Flow Diagram. DFD is pictorial representation of the
system. DFD is a graphical representation of the ―flow of data through the information
system. DFD are also used for the visualization of data processing (structured design). ADFD
provides no information about the timings of the process, or about whether process will
operate in parallel or sequence. DFD is an important technique for modeling a system’s high-
level detail by showing how input data is transformed to output results through sequence of
functional transformations. DFD reveal relationships among between the various components
in a program or system. The strength of DFD lies in the fact that using few symbols we are
able to express program design in an easier manner. A DFD can be used to represent the
following: -
Process that change the data.
Flow of data with in the system.
Data Storage locations.
Uses of DFD:-
The main uses of data flow diagrams are as follows: -
DFD is a method of choice for representation of showing of information through a
system because of the following reasons: -
 DFDs are easier to understand by technical and non-technical audiences.

 DFDs can provide high level system overview, complete with
boundaries and connections to other system.

 DFDs can provide a detailed representation of system components.


22
0 Level DFD
Student Reg./login Reg./login
Admin
Accept/ Reject Accept/ Reject
SOFTWARE REQUIREMENT SPECIFICATION
A requirements specification for a software system is a complete description of the
behavior of a system to be developed and it includes a set of use cases that describe

23
all the interactions the users will have with the software. In addition to use cases,
the SRS also contains non-functional requirements.
Non-functional requirements are requirements which impose constraints on the
design or implementation (such as performance engineering requirements, quality
standards, or design constraints). Requirements are a sub-field of software
engineering that deals with the elicitation, analysis, specification, and validation of
requirements for software.
The software requirement specification document enlists all necessary requirements for
project development. To derive the requirements, we need to have clear and thorough
understanding of the products to be developed. This is prepared after detailed
communications with project team and the customer.
Software Specification: -
Programming Language Support
• .Net with MVC
 Java Script for client-side validation
 jQuery
Server-side Software Requirement
• IDE- Visual studio
• Ms SQL

24
Client-side Software Requirement
• Google Chrome Browser
• Operating System
Front-end Tool
• User friendly
• Low cost solution
• GUI feature
• Better designing aspects
Back-end Tool: -Ms SQL
• Security
• Portability
• Quality
Platform:
Windows platform like: 2000 Server, Professional, XP & Vista
Hardware Specification:
• Intel Pentium and Celeron class processor
• RAM – 2 G.B. (min)
• HDD - 40 GB

25
• Monitor-14” SVGA
• Printer – Dot Matrix /Inkjet /Laser Printer
• Mouse & Keyboard- Normal
For Client side: Web browser- IE 7 or above, Google chrome, Safari.
Platform: Windows platform like: windows 98 or above higher version.
SUPPORT AND MAINTENANCE: -
One-year free support for rectifying system bugs including front end and beck end will be
Provided . During warranty period Software Engineers will be responsible for removing
bugs and improving it. After one-year support can be extended @ 20% of the total product
deployment cost.
SYSTEM DESIGN APPROACH
Top – Down designing:
The top - down designing approach started with major components of the system. It is a
stepwise refinement which starts from an abstract design, in each steps the design is refined
two or more concrete levels until we reach a level where no – more refinement is possible or
not needed.
Bottom – Up designing:
In bottom – up designing the most basic and primitive components are designed first, and

26
we proceed to higher level components. We work with layers of abstractions and abstraction
are implemented until the stage is reached where the operations supported by the layer is
complete.
Approach we are following:
In this project we are following Mixed Approach i.e. a combination of top – down and
bottom – up. We are developing some of the components using top – down designing
approach (e.g. the Web Pages) and the some components in bottom – up designing approach
(e.g. the middle tier classes).
DATA MODELING
LIST OF TABLES:
1. Tbl_Contect Us
2. Tbl_Registration
3. Tbl_Login
4. Tbl_Feedback
5. Tbl_Notification

27
Tbl_Contect Us
Tbl_Registration
Tbl_Feedback

28
Tbl_login
Tbl_Notification
Low Level Design
Description: Low Level Design creation is one of the most important activities in the development
of any software product. The low-level design document gives the design of the actual software
application. Low level design document is based on High Level Design document. It defines internal
logic of every sub module. A good low-level design document will make the application very easy to
develop by the developer. An effective design document results in very low efforts in developing a
Software product.

29
Each project's low-level design document should provide a complete and detailed
specification of the design for the software that will be developed in the project, including the classes,
member and non-member functions, and associations between classes that are involved.
The low-level design document should contain a listing of the declarations of all the classes,
non-member-functions, and class member functions that will be defined during the subsequent
implementation stage, along with the associations between those classes and any other details of those
classes (such as member variables) that are firmly determined by the low-level design stage. The low-
level design document should also describe the classes, function signatures, associations, and any
other appropriate details, which will be involved in testing and evaluating the project according to the
evaluation plan defined in the project's requirements document.
TESTING:
Testing is the integral part of any System Development Life Cycle insufficient and interested
application tends to crash and result in loss of economic and manpower investment besides user’s
dissatisfaction and downfall of reputation.
Software Testing includes selecting test data that have more probability of giving errors.” The first
step in System testing is to develop the plan that all aspect of system. Complements, Correctness ,
Reliability and Maintainability.
Software is to be tested for the best quality assurance, an assurance that system meets the
specification and requirement for its intended use and performance.
System Testing is the most useful practical process of executing the program with the
implicit intention of finding errors that makes the program fail.
Types of Testing:
Black Box (Functional) Testing:
Testing against specification of system or components. Study it by examining its inputs and
related outputs. Key is to devise inputs that have a higher likelihood of causing outputs that
reveal the presence of defects. Use experience and knowledge of domain to identify such test
cases. Failing this a systematic approach may be necessary. Equivalence partitioning is where

30
the input to a program falls into a number of classes, e.g. positive numbers vs. negative
numbers. Programs normally behave the same way for each member of a class. Partitions
exist for both input and output. Partitions may be discrete or overlap. Invalid data (i.e. outside
the normal partitions) is one or more partitions that should be tested. Internal System design
is not considered in this type of testing. Tests are based on requirements and functionality.
This type of test case design method focuses on the functional requirements of the software,
ignoring the control structure of the program. Black box testing attempts to find errors in the
following categories:
➢
Incorrect or missing functions.
➢
interface errors.
➢
Errors in data structures or external database access.
➢
Performance errors.
➢
Initialization and termination errors.
White Box (Structural) Testing:
Testing based on knowledge of structure of component (e.g. by looking at source code). Advantage is
that structure of code can be used to find out how many test case need to be performed. Knowledge of
the algorithm (examination of the code) can be used to identify the equivalence partitions. Path testing
is where the tester aims to exercise every independent execution path through the component. All
conditional statements tested for both true and false cases. If a unit has no control statements, there
will be up to 2n possible paths through it. This demonstrates that it is much easier to test small
program units than large ones. Flow graphs are a pictorial representation of the paths of control
through a program (ignoring assignments, procedure calls and I/O statements). Use flow graph to
design test cases that execute each path. Static tools may be used to make this easier in programs that
have a complex branching structure. Tools support. Dynamic program analyzers instrument a
program with additional code. Typically, this will count how many times each statement is executed.
At end print out report showing which statements have and have not been executed. Problems with
flow graph derived testing:

31
❖
Data complexity could not take into account.
❖
We cannot test all paths in combination.
❖
In really only possible at unit and module testing stages because beyond that
complexity is too high.
This testing is based on knowledge of the internal logic of an application’s code. Also known as a
Glass Box Testing. internal software and code working should be known for this type of testing. Tests
are based on coverage of code statements, branches, paths, conditions.
Unit Testing:
Unit testing concentrates on each unit of the software as implemented in the code. This is done to
check syntax and logical errors in programs. At this stage, the test focuses on each module
individually, assuring that it functions properly as a unit. In our case, we used extensive white-box
testing at the unit testing stage.
A developer and his team typically do the unit testing do the unit testing is done in parallel with
coding; it includes testing each function and procedure.
Incremental integration Testing:
Bottom up approach for testing i.e. continuous testing of an application as new functionality is added;
Application functionality and modules should be independent enough to test separately done by
programmers or by testers.
Integration Testing:
Testing of integration modules to verify combined functionality after integration. Modules are
typically code modules, individual applications, client and server and distributed systems.
Functional Testing:
This type of testing ignores the internal parts and focus on the output is as per requirement or not.
Black box type testing geared to functionality requirements of an application.
System Testing:
Entire system is tested as per the requirements. Black box type test that is based on overall
requirement specifications covers all combined parts of a system.
End-to-End Testing:

32
Similar to system testing, involves testing of a complete application environment in a situation that
mimics real-world use, such as interacting with a database, using network communications, or
interacting with hardware, applications, or system if appropriate.
Regression Testing:
Testing the application as a whole for the modification in any module or functionality. Difficult to
cover all the system in regression testing so typically automation tools are used for these testing types.
Acceptance Testing:
Normally this type of testing is done to verify if system meets the customer specified requirements.
User or customers do this testing to determine whether to accept application.
Performance Testing:
Term often used interchangeably with “stress” and “load” testing, To check whether system meets
performance requirements, Used different performance and load tools to do this.
Alpha Testing:
In house virtual user environment can be created for this type of testing. Testing is done at the end of
development. Still minor design changes may be made as a result of such testing.
Description of Classes and Methods:
Datamanager class and Method:
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Data;
using System.Data.SqlClient;
using System.Configuration;
namespace crud.Models
{
public class ConnectionManager

33
{
SqlConnection con = null;
SqlCommand cmd = null;
public ConnectionManager()
{
con =new
SqlConnection(ConfigurationManager.ConnectionStrings["mycon"].ConnectionString);
}
//this function are used to insert,delete,update commands.
public bool InsertUpdateDelete(string command)
{
cmd=new SqlCommand(command,con);
if(con.State==ConnectionState.Closed)
{
con.Open();
}
int n = cmd.ExecuteNonQuery();
if(n>0)
return true;
else
return false;
}
//this command used for select query return data with datatable
public DataTable Display_All_Records(string Command)
{
cmd=new SqlCommand(Command,con);
DataTable dt=new DataTable();

34
SqlDataAdapter sa=new SqlDataAdapter(cmd);
sa.Fill(dt);
return dt;
}
public int GetCount(string command)
{
cmd=new SqlCommand(command,con);
int n=(Int32)cmd.ExecuteScalar();
if(n>0)
{
return n;
}
return n;
}
}
} User Screenshots
Index

38
ViewAddEvents
View Notification

39
Index.net
Index
<!DOCTYPE html>
<html lang="en">
<head>
<style>
.top
{
background:#66bb6a;
font-size:20px;
color:white;
}
.top1
{
font-size:14px;
}
.top2
{
font-family:'Pristina';
font-size:16px;
color:white;
}
.top3
{
font-size:14px;
color:white;
}
#header{
min-height: 100px;

40
}
#logo{
height: 100px;
/* margin-top: 10px;*/
}
h1{
font-size: 28px;
color:#66bb6a;
}
h1:after{
content: "SPORTS MANAGEMENT SYSTEM";
display: block;
}
h2{
font-size: 28px;
color:brown;
}
#btn
{
color:white;
font-size:15px;
}
#btn:hover
{
background-color: aliceblue;
color:black;
}
label{
color:#66bb6a;
}
.footer

41
{
min-height:300px;
background: #66bb6a;
font-family:Ebrima;
color:white;
}
.footer1
{
background:black;
color:white;
font-size:16px;
text-align:center;
font-weight:bold;
padding-top:1%;
padding-bottom:1%;
}
</style>
</head>
<body>
<div class="container-fluid">
<div class="row panel panel-heading top" style="background:#66bb6a;min-
height:40px;color:white">
<div class="col-sm-12 top1" style="min-height:1px;padding:.5%">
<div class="col-sm-4">
<span class="fa fa-phone sphead1"> 7388442188</span>
</div>
<span class="text text-center top2"><font color="teal"><b>SPORT</b></font><b>
MANAGEMENT SYSTEM</b></span>

42
</div>
<div class="col-sm-4" style="text-align:right">
<span class="top3"> 10/07/2020</span>
</div>
</div>
</div>
</div>
<div class="container-fluid" style="height:400px;width:100%;">
<div class="row">
<div class="col-sm-12" id="header">
<img src="govlogo.png" id="logo"/>
</div>
<h1>स्पोर्ट्स मैनेजमेंर् (खेल प्राधिकरण)</h1>
</div>
<a href="#"><span class="fa fa-facebook-square" style="font-size:40px; margin-top:30px; color:
#227fd4">
</span></a>
<a href="#"><span class="fa fa-whatsapp" style="font-size:40px; margin-top:30px;
color:green;
margin-left:10px;"></span></a>
<a href="#"><span class="fa fa-twitter" style="font-size:40px; margin-top:30px; margin-
left:10px;
color:skyblue"></span></a>
<a href="#"><span class="fa fa-instagram" style="font-size:40px; margin-top:30px; color:red;
margin-left:10px;"></span></a>
</div>
</div>
</div>

43
<div class="row" style="background:black;min-height:50px;color:white">
<nav class="navbar navbar-default" >
<div class="container-fluid " style=" background: #66bb6a; margin-bottom:-2.1%">

<div class="navbar-header">
<button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-
target="#bs-example-navbar-collapse-1" aria-expanded="false">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
</button>
</div>

<div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1" style="margin-
left:200px;">
<ul class="nav navbar-nav">
<li><a href="home" id="btn">HOME<span class="sr-only"></span></a></li>
<li><a href="Aboutus" id="btn">ABOUTUS<span class="sr-only"></span></a></li>
<li><a href="Gallery" id="btn">GALLERY</a></li>
<li><a href="Gnotification" id="btn">NOTIFICATION</a></li>
<li><a href="Winner_list" id="btn">WINNER</a></li>
<li><a href="index" id="btn">REGISTRATION</a></li>
<li><a href="contactus" id="btn">CONTACTUS</a></li>
<li><a href="login" id="btn">LOGIN</a></li>
</ul>
</div>
</div>
</nav>

44
</div>
<div class="row" style="min-height:300px; background:#f0f0f0">
@yield('content')
</div>
<div class="row">
<div class="col-sm-12 footer">
<div class="col-sm-3" style="font-size:17px">
<h3>Importance Links</h3>
<span class="text-responsive spf"style="margin-left:9%"><i
style="color:black;">→</i>Aktu.ac.in</span><br/>
style="color:black;">→</i>Bteup.in</span><br >
style="color:black;">→</i>up.gov.in</span><br/>
style="color:black;">→</i>apinfotech.org</span><br/>
</div>
<iframe
src="https://www.google.com/maps/embed?pb=!1m18!1m12!1m3!1d3558.2758959299854!2d80.
95136231452024!3d26.
894737767339393!2m3!1f0!2f0!3f0!3m2!1i1024!2i768!4f13.1!3m3!1m2!1s0x399957162f9814a1%3A0xcf1a2
d0fc9abd3c7!2s
Arcane%20programming%20infotech!5e0!3m2!1sen!2sin!4v1595698710448!5m2!1sen!2sin"
width="600"
height="300"
frameborder="0" style="border:0;" allowfullscreen="" aria-hidden="false"
tabindex="0">
</iframe>

45
</div>
</div>
<div class="col-sm-2"></div>
<span class="fa fa-phone" style="font-size: 16px; margin-top: 120px;"> 0512-
2451245</span>
<br/>.
<span class="fa fa-envelope" style="font-size: 16px; margin-top: 30px;">
apinfotech.org</span>
<br/>
<span class="fa fa-home" style="font-size: 16px; margin-top: 20px"> mm 45,Sector-
L,Aliganj</span>
Lucknow-226024.
<address>
</address>
</div>
</div>
<div class="row">
<div class="col-sm-12 footer1">
Copyright©By Arcane Programming Infotech Lucknow
</div>
</div>
</div>
</div>
</body>
</html>
Registration
@model SportManagementSystem.Models.Register

46
@{
ViewBag.Title = "Registration";
Layout = "~/Views/Shared/GeneralMaster.cshtml";
}
<style>
.panel-body {
border: 2px solid darkred;
margin-top: 2%;
}
.panel-heading {
color: white;
font-size: 20px;
font-family: 'Times New Roman';
background: darkred;
text-align: center;
}
label {
color: maroon;
font-size: 15px;
font-family: 'Times New Roman';
margin-left: 0%;
}
.form-control, .btn {
height: 40px;
border-radius: 3px;
}

47
.btn {
width: 135px;
color: white;
text-align: center;
font-size: 15px;
border-radius: 3px;
margin-left: 100px;
}
span {
color: red;
}
</style>
@using (Html.BeginForm("Registration", "Home", FormMethod.Post, new { enctype = "multipart/form-data"
}))
{
@Html.ValidationSummary(true)
<div class="col-sm-9 panel panel-body">
<div class="col-sm-12 panel panel-heading">REGISTRATION FORM</div>
<div class="row">
@Html.LabelFor(model => model.Name)
@Html.TextBoxFor(model => model.Name, new { @class = "form-control", type = "text",
placeholder = "Enter Name Here" })
@Html.ValidationMessageFor(model => model.Name)<br />
@Html.LabelFor(model => model.Father_Name)
@Html.TextBoxFor(model => model.Father_Name, new { @class = "form-control", type = "text",
placeholder = "Enter Father_Name Here" })
@Html.ValidationMessageFor(model => model.Father_Name)<br />

48
@Html.LabelFor(model => model.Gender)
@Html.DropDownListFor(model => model.Gender, new List<SelectListItem>(){
new SelectListItem(){Text="---Select Gender---",Value="---Select Gender---"},
new SelectListItem(){Text="Male",Value="Male"},
new SelectListItem(){Text="Female",Value="Female"},
}, new { @class = "form-control" })
@Html.ValidationMessageFor(model => model.Gender)<br />
@Html.LabelFor(model => model.Branch)
@Html.DropDownListFor(model => model.Branch, new List<SelectListItem>(){
new SelectListItem(){Text="---Select Branch---",Value="---Select Branch---"},
new SelectListItem(){Text="Information Technology",Value="Information Technology"},
new SelectListItem(){Text="Civil Engineering",Value="Civil Engineering"},
new SelectListItem(){Text="Computer Science And Engineering",Value="Computer Science And
Engineering"},
@Html.ValidationMessageFor(model => model.Branch)<br />
</div>
@Html.LabelFor(model => model.Year)
@Html.DropDownListFor(model => model.Year, new List<SelectListItem>(){
new SelectListItem(){Text="---Select Year---",Value="---Select Year---"},
new SelectListItem(){Text="1st year",Value="1st year"},
new SelectListItem(){Text="2nd year",Value="2nd year"},
new SelectListItem(){Text="3rd year",Value="3rd year"},
@Html.ValidationMessageFor(model => model.Year)<br />
@Html.LabelFor(model => model.Email)

49
@Html.TextBoxFor(model => model.Email, new { @class = "form-control", type = "email",
placeholder = "Enter Email Here" })
@Html.ValidationMessageFor(model => model.Email)<br />
@Html.LabelFor(model => model.Password)
@Html.TextBoxFor(model => model.Password, new { @class = "form-control", type = "password",
placeholder = "Enter Password Here" })
@Html.ValidationMessageFor(model => model.Password)<br />
@Html.LabelFor(model => model.Confirm_Password)
@Html.TextBoxFor(model => model.Confirm_Password, new { @class = "form-control", type =
"password", placeholder = "Enter Password Here" })
@Html.ValidationMessageFor(model => model.Confirm_Password)<br />
</div>
@Html.LabelFor(model => model.Mobile)
@Html.TextBoxFor(model => model.Mobile, new { @class = "form-control", type = "number",
placeholder = "Enter Number Here" })
@Html.ValidationMessageFor(model => model.Mobile)<br />
@Html.LabelFor(model => model.Sport_Type)
@Html.DropDownListFor(model => model.Sport_Type, new List<SelectListItem>(){
new SelectListItem(){Text="Select Sport type"},
new SelectListItem(){Text="badminton",Value="badminton"},
new SelectListItem(){Text="race 300m",Value="race 300m"},
new SelectListItem(){Text="race 400m",Value="race 400m"},
@Html.ValidationMessageFor(model => model.Sport_Type)<br />
@Html.LabelFor(model => model.Address)
@Html.TextBoxFor(model => model.Address, new { @class = "form-control", type = "text",
placeholder = "Enter Address Here" })
@Html.ValidationMessageFor(model => model.Address)<br />

50
@*@Html.LabelFor(model => model.Image)
<
@Html.TextBoxFor(m => m.Image, new { type = "file", @class = "form-control" })
@Html.ValidationMessageFor(model => model.Image)<br />*@
<label>Image</label>
<input type="file" name="Image" class="form-control"/>
<input type="submit" class="btn btn-success" value="Register Now" /><br />
</div>
</div>
</div>
</div>
}
Login
@extend('GeneralMaster')
@section('content')
<h2 class="text-center text-success text-uppercase" >Login</h2>
<div class="col-sm-4 panel panel-body"style="border:1px solid #66bb6a;box-shadow: 2px 2px 12px
12px gray;margin-bottom: 40px;">
<form action="logincode" method="post">
<label for="Email">Email</label>
<input type="text" class="form-control" data-val-required="Please Enter Email" name="txtname"
required="required"/>
<span class="field-validation-valid" data-valmsg-for="Email" data-valmsg-replace="true"></span>
<label for="Password">Password</label>
<input type="password" class="form-control" data-val-required="Please Enter Password"
name="txtpass" required="required" />
<span class="field-validation-valid" data-valmsg-for="Password" data-valmsg-
replace="true"></span><br/>
<div style="height:50px;">

51
<input type="submit" value="Sign Up" class="btn btn-success"/>
</div>
</form>
</div>
</div>
@endsection
Userhome
<!DOCTYPE html>
<html>
<head>
<meta name="viewport" content="width=device-width" />
<title>@ViewBag.Title</title>
<style>
#btn:hover {
background: darkred;
font-size: 15px;
color: black;
}
</style>
</head>
<body>
<div class="row">
<div class="col-sm-12" style="min-height:50px;

52
font-size:50px;color:black;
font-weight:bolder;text-shadow:1px 2px 2px darkred;font-family: 'Algerian'">
<img src="~/Content/Profile/@ViewBag.im" style="height:50px;width:50px" />Welcome!
 
@ViewBag.name
<span>Sport</span>
<span>Management</span>
<span>System</span>
<hr style="background-color:black;min-height: 10px;">
</div>
</div>
<div class="row">
<div class="col-sm-12" style="padding:0px;">
<nav class="navbar navbar-default" style="background:teal; ">
</button>
</div>
<div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1">

53
<li><a href="/User/Index" style="color:white; font-size:17px; font-
weight:bold;">Home</a></li>
<li><a href="/User/MyProfile" style="color: white; font-size: 17px" font-
weight:bold;">My Profile</a></li>
<li><a href="/User/Complain" style="color: white; font-size: 17px" font-
weight:bold;">Complain</a></li>
<li><a href="/User/Change_Password" style="color: white; font-size: 17px" font-
weight:bold;">Change Password</a></li>
<li><a href="/User/Logout" style="color: white; font-size: 17px" font-
weight:bold;">Logout</a></li>
</ul>
</nav>
</div>
</div>
<div >
@RenderBody()
</div>
</body>
</html>
Feedback
<div class="col-sm-4 panel panel-body" style="margin-top:2%">
<h3>Your Valuable Feedback</h3>
<hr>
Rating Here
<br>

54
<form action="feedback" method="Post" id="frm">
<span class="fa fa-star" id="s1" style="font-size:35px"></span>
<span class="fa fa-star" id="sp1" style="font-size:35px"></span>
<span class="fa fa-star" id="s5" style="font-size:35px"> </span>
<br>
Write Your Reviews here..
<textarea class="form-control" style="height:140px;" id="txtmsg"></textarea>
<br>
<input type="submit" class="btn btn-success" value="Submit Review"/>
</form>
</div>
</div>
AdminHome
<!DOCTYPE html>
<html>
<body>
<div class="row">
<div class="col-sm-12" style="min-height:50px;

55
font-size:50px;color:black;
font-weight:bolder;text-shadow:1px 2px 2px darkred;font-family: 'Algerian'">
<span>Welcome To Admin Master</span>
<hr style="background-color:black;min-height: 10px;">
</div>
</div>
<div class="row">
<div class="col-sm-12" style="padding:0px;">
<nav class="navbar navbar-default" style="background:darkred; ">
</button>
</div>
<div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1">

56
<li><a href="/Admin/Index" style="color:white; font-size:17px; font-
weight:bold;">Home</a></li>
<li><a href="/Admin/ViewRegistration" style="color: white; font-size: 17px" font-
weight:bold;">View Registration</a></li>
<li><a href="/Admin/AddEvents" style="color: white; font-size: 17px" font-
weight:bold;">Add Event</a></li>
<li><a href="/Admin/Notification" style="color: white; font-size: 17px" font-
weight:bold;">Notification</a></li>
<li><a href="/Admin/Change_Password" style="color: white; font-size: 17px" font-
weight:bold;">Change Password</a></li>
<li><a href="/Admin/Logout" style="color: white; font-size: 17px" font-
weight:bold;">Logout</a></li>
</ul>
</nav>
</div>
</div>
<div>
@RenderBody()
</div>
<div class="row">
<div class="col-sm-12 footer">
<div class="col-sm-3 foot1" style="font-size:17px">
<h3>Importance Links</h3>
<span class="text-responsive spf" style="margin-left:9%"><i
style="color:black;">→</i>Aktu.ac.in</span><br />
style="color:black;">→</i>Bteup.in</span><br />
style="color:black;">→</i>up.gov.in</span><br />
style="color:black;">→</i>apinfotech.org</span><br />

57
</div>
<div class="col-sm-4 foot2">
<div class="col-sm-12" style="margin-top:20px">
<iframe class="col-sm-12" height="260px"
src="https://www.google.com/maps/embed?pb=!1m18!1m12!1m3!1d3503.244207985481!2d77.51644351
45587!3d28.59244979264582!2m3!1f0!2f0!3f0!3m2!1i1024!2i768!4f13.1!3m3!1m2!1s0x390cecf7a68d2c29%
3A0x8b7f05bb75abda9b!2sKm.%20Mayawati%20Govt.%20Girls%20Polytechnic!5e0!3m2!1sen!2sin!4v
1583561109276!5m2!1sen!2sin" frameborder="0" style="border:0;" allowfullscreen=""></iframe>
</div>
</div>
<div class="col-sm-3 foot3">
<h3> Address</h3>
<address>
Km Mayawati Govt.<br />
Girls Polytechnic<br />
Badalpur Gautam Budh Nagar<br />
pincode:-203207s
</address>
</div>
</div>
</div>
<div class="row">
</div>
</body>
</html>
View Registration
@model SportManagementSystem.Models.Registration
@{
ViewBag.Title = "ViewRegistration";

58
Layout = "~/Views/Shared/AdminMaster.cshtml";
}
@using System.Data;
@using System.Data.SqlClient;
@using crud.Models;
<h2 class="text-center text-success">View Registration</h2>
@{
ConnectionManager db = new ConnectionManager();
string query = "select*from Tbl_demo2";
DataTable dt = db.Display_All_Records(query);
if(dt.Rows.Count>0)
{
<table class="table table-responsive" style="border:2px solid maroon">
<tr
style="background:maroon;color:white"><th>Name</th><th>Email</th><th>Mobile</th><th>Address<
/th><th>Date</th><th>Delete</th></tr>
@for(int i=0;i<dt.Rows.Count;i++)
{
<tr>
<td>@dt.Rows[i]["Name"]</td>
<td class="td1">@dt.Rows[i]["Email"]</td>
<td>@dt.Rows[i]["Mobile"]</td>
<td>@dt.Rows[i]["Address"]</td>
<td>@dt.Rows[i]["RDt"]</td>
<td><span class="fa fa-trash"></span></td>
</tr>
}
</table>
}
}
<script>

59
$(document).ready(function(){
$(".fa-trash").click(function(){
var email = $(this).closest("tr").find(".td1").text();
$.getJSON("/Admin/Delete", { Email: email }, function success(data) {
alert(data);
})
$(this).closest("tr").remove().fadeOut(2222);
})
})
</script>
Changepassword
@model SportManagementSystem.Models.ChangePassword
@{
ViewBag.Title = "Change_Password";
Layout = "~/Views/Shared/AdminMaster.cshtml";
}
<h2 class="text-center text-uppercase text-success">Change_Password</h2>
<hr style="min-height:2px;background:teal;width:40%" />
@using (Html.BeginForm())
{
@Html.ValidationSummary(true)
<label>Enter Old password</label>
@Html.TextBoxFor(model => model.OldPassword, new { @class = "form-control", type = "password" })

60
@Html.ValidationMessageFor(model => model.OldPassword)
<label>Enter New password</label>
@Html.TextBoxFor(model => model.NewPassword, new { @class = "form-control", type = "password" })
@Html.ValidationMessageFor(model => model.NewPassword)
<label>Enter Confirm password</label>
@Html.TextBoxFor(model => model.ConfirmPassword, new { @class = "form-control", type =
"password" })
@Html.ValidationMessageFor(model => model.ConfirmPassword)
<br />
<input type="submit" value="ChangePassword" class="btn btn-success" />
}
</div>
</div>
Logout
public ActionResult Logout()
{
mySession();
Session.Abandon();
Session.Clear();
Session.RemoveAll();
Response.Write("<script>window.location.href='/home/login'</script>");
// Response.Redirect("/Home/Login");
return View();
}

61
FUTURE SCOPE
Following modification or upgrades can be done in system.
1. More than one Student can be integrated through this software.
2. Students can check their application status online.
CONCLUSION:
At last it can be concluded that the Sport Management System was a real learning experience.
The principles of software production were well implemented throughout the system. The
whole project undergoes with full of enthusiasm and with full of joyous moments. The
project has been made as per as the given specification. Working on the Project was really a
learning experience and we have come a long way in building our concepts of Software
engineering. The “Sport Management System “developed by us is purely based on .Net . The
overall purpose of this system is to computerized the whole process and thus prevent the
intervening errors. During the course of this assignment we have gone through many
obstacles which made us to research and though increased our knowledge. After applying all
the data modeling, object modeling and process modeling techniques now we are very well
clear with all these concepts and fundamentals which will be going to help us in the future.

Sport.net(2).doc

More Related Content

Similar to Sport.net(2).doc (20)

Recently uploaded (20)

Sport.net(2).doc