AUTOMATED FOOTBALL MANAGEMENT SYSTEM

System Development Methods Group Assignment Page 1 of 57
Level 2 Asia Pacific Institute of Information Technology 2014
SYSTEM DEVELOPMENT METHODS
MODULE CODE: CE00321-2
“BOCA JUNIORS MANAGEMENT SYSTEM”
Group Assignment (G2)
Level 2
Hand-in-Date: Hand-out-Date:
4th
February 2014 12th
April 2014
Submitted By: Submitted To:
Sumit Kumar Singh (PT1181104) Mr. Radha Krishna Rambola
Kumar Abhishek (PT1181106) (Module Lecturer)
Gautam Mishra (PT1181108)

CERTIFICATE
This is to certify that the following under mentioned students of APIIT SD INDIA, Level-2 CSE
have successfully completed their assignment of System Development Methods in the given span
of time and with full dedication from their side which they have implemented. They have
maintained all the guidelines set by “STAFFORDSHIRE UNIVERSITY”. The work in the
assignment doesn’t have any type of relation with the word PLAGIARISM.
I hereby declare that I have been handed over the project along with all necessary documents. I
wish them good luck in all their future projects.
Date: - 12th
April 2014
Submitted By: Submitted To:
Sumit Kumar Singh (PT1181104) Mr. Radha Krishna Rambola
Kumar Abhishek (PT1181106) (Module Lecturer)

ACKNOWLEDGEMENT
It was a great experience working on the project of System Development Methods on “BOCA
JUNIORS MANAGEMENT SYSTEM”. We express our gratitude towards those who were
constantly involved with us during our project. APIIT SD India, Panipat will always occupy a
special place in our heart, throughout our career, for both personal and professional reasons.
The phenomenon remains same that no project ever can be executed proficiently and efficiently
without sharing the particular ideas, technical expertise and innovative thoughts put forwarded by
the technical and non-technical experts.
We are also grateful to all the APIITIAN lecturers for being extremely friendly and co-operative
during the entire course of our project. Their continuous help and support made the project much
easy.
There are no exact words to express our regards and reasonable gratitude to one of our esteemed
techno personality, without him this project could not get an entrance towards the execution. Mr.
Mr. Radha Krishna Rambola is the pioneer who availed this magnificent option to us to move
ahead. He has always inspired and guided us for the right track to be followed for all the system
analysis section of this project. We are indebted to him for giving us this great opportunity to
pursue our sixth (6th
) semester project.
Lastly we would like to thank APIIT SD INDIA for giving us this opportunity to work in great
environment and also thank to all those whose names may not have appeared here but whose
contribution has not gone unnoticed. We would like to thank all of them, for their help in various
ways.
Submitted By:
Sumit Kumar Singh (PT1181104)
Kumar Abhishek (PT1181106)

Table of Contents
1.0 INTRODUCTION ....................................................................................................................... 6
1.1 Purpose ................................................................................................................................. 7
1.2 Objective............................................................................................................................... 7
1.3 Scope .................................................................................................................................... 8
1.4 Task ...................................................................................................................................... 8
2.0 Schedule Planning........................................................................................................................ 9
2.1 Feasibility Study....................................................................................................................... 9
2.1.1 Operational Feasibility ...................................................................................................... 9
2.1.2 Technical Feasibility........................................................................................................ 11
2.1.3 Economic Feasibility....................................................................................................... 13
2.1.4 Schedule Feasibility......................................................................................................... 16
3.0 Selection of Methodology.......................................................................................................... 20
3.1 Purpose ............................................................................................................................... 20
3.2 Structure.............................................................................................................................. 20
3.3 Scope .................................................................................................................................. 21
4.0 Problem Analysis....................................................................................................................... 22
5.0 Proposed System........................................................................................................................ 23
6.0 Investigation Techniques ........................................................................................................... 24
6.1 Questionnaire...................................................................................................................... 25
6.2 Interview............................................................................................................................. 25
7.0 Process Model............................................................................................................................ 28
7.1 Logical Process Model ....................................................................................................... 28
7.2 Process Specification.......................................................................................................... 32
8.0 Data Model................................................................................................................................. 33
8.1 Entity Relationship Diagram .............................................................................................. 33
9.0 Event Model............................................................................................................................... 35
9.1 Entity Life History.............................................................................................................. 35
10.0 Database Designs..................................................................................................................... 37
10.1 Registration Database....................................................................................................... 37
10.2 Sports-Apparels Database................................................................................................. 37

10.3 Payroll Database............................................................................................................... 38
10.4 Maintenance Database...................................................................................................... 38
11.0 Interactive Screen Designs....................................................................................................... 39
12.0 Programming Environment...................................................................................................... 47
12.1 Front End.......................................................................................................................... 47
12.2 Back End........................................................................................................................... 48
13.0 CONCLUSION........................................................................................................................ 49
14.0 Bibliography ............................................................................................................................ 50
15.0 Appendix.................................................................................................................................. 51

INTRODUCTION
Today is the modern era where we have the latest technology to assist us in every possible way. As
we have seen the transformation of the work which was manually executed and now by the
introduction of technology everything has changed around us, we are able to work efficiently and
within short span of time investing a little effort. The most amazing development has been in the
field of computers, it has made our life easy by automating the manual work.
In the given scenario, there is a football club Boca Juniors Football Club which was born on
Monday April 3rd, 1905, when five young boys who lived in the La Boca neighbourhood (Esteban
Baglietto, Alfredo Scarpatti, Santiago Sana and brothers Juan and Teodoro Farenga) got together at
Solís Square with the intention to form a football club.
The founders have decided to invest in a new information management system (called Boca
Juniors Management System – BJMS). The information system will have to manage the following
functions:
(i) Registration of new players
(ii) Purchase of sports apparels – shirts, shorts, boots, gloves, etc.
(iii) Maintenance of Stadium
(iv) Managing of players’ payroll
a. Match playing bonus
b. Goal bonus
c. Claims
d. Salary increments
e. Bonus for corner goal
The system will benefit the club in many ways; it will help to control the overall processes going
on in the club. The system will provide numerous facilities such as it will help to register new
players and it will manage the payroll of the particular players based on the certain criteria’s given
in the scenario. The system will manage the stock of the sports apparels in the inventory and it will
help in keeping the track of what the maintenance part is going on in the club. We are looking

forward to make a system using SDLC steps and using appropriate methodology which will be
best suited for the system after we will be done of the system analysis.
1.1 Purpose
The main purpose of designing this management system is to manage the whole system online so
that all the work goes in a very systematic manner. Earlier there was an account maintaining
technique or we can say that all the system was handled manually in which the administrator has to
maintain the register which leads to loss of data and security problem issue is also being faced. So
now keeping in mind, the management have decided to design an online system so that all the
things get automatically updated and kept safe in the database.
In this system, the main role is of players who can become the members of this club by doing
registration and then they can purchase the sports apparels. Players can view their profile and can
also see their payrolls if given.
Boca Juniors management system is prepared for providing all the necessary things which is
needed by the sports player. This system will also keep the online record of all the sold sports
apparels in their database so that there is no any loss of data take place. It will also keep the good
record of maintenance of the stadium.
1.2 Objective
The main objective of this application is to develop a system using which the players can easily
view their profile and can do the purchasing of the required sports apparels online. An online
football club is an application where the players can register themselves and can search or
purchase the sports apparels as per their need.
The online football management system is a complete package to be used by the club to improve
the efficiency of the business. The system to be developed is going to benefit greatly the members.
The system will contain all the information about the members regarding the sports apparels and
payrolls. Payrolls include match playing bonus, goal bonus, claims, salary increments of the
players, bonus for corner goal. The admin can keep the system updated all the time for the players
so that the players don’t have to face any problem while searching and purchasing of sports
apparels and can get the updated information all the time.

1.3 Scope
The Scope for the system can be as follows:-
 Registration of players
 Maintenance of Stadium
 Provide sports apparels to the players
 Maintenance of the database of the sports apparels
 Management of Payrolls for the players
1.4 Task
The application comprises the following major modules:
Players Task
In this, the players will get the unique ID which will be available while doing registration for this
club. The players can view their profile and also can search or purchase the sports apparels as per
their need. The players can also browse through the latest sports apparels available.
Administration Task
In this, the administrator will have the authority of the entire system. He will be handling all the
complete system related to stock maintenance of the sports apparels of the players, stadium
maintenance. The administrator will maintain the profile of the players and payrolls provided.

Schedule Planning
2.1 Feasibility Study
A feasibility study assesses the operational, technical and economic merits of the proposed project.
The feasibility study is intended to be an introductory review of the facts to see if it is worthy of
proceeding to the analysis phase. From the systems analyst perspective, the feasibility analysis is
the primary tool for recommending whether to proceed to the next phase or to discontinue the
project.
The feasibility study is a management-oriented activity. The objective of a feasibility study is to
find out if an information system project can be done and to suggest possible alternative solutions.
A feasibility study should provide management with enough information to decide:
 Whether the project can be done?
 Whether the final product will benefit its intended users and organization
 What are the alternatives among which a solution will be chosen
 Is there a preferred alternative
 How beneficial or practical the development of an information system would be to an
organization?
And for the system to be act as worth-while it should passed through some test that examine that it
should proceed further or not. This series of test is commonly known as feasibility study on the
system and it plays a very vital role for every system projects. Feasibility studies undergo four
major analyses to predict the system to be success and they are as follows:-
2.1.1 Operational Feasibility
Operational feasibility is a measure of how well a proposed system solves the problems, and takes
advantage of the opportunities identified during scope definition and how it satisfies the
requirements identified in the requirements analysis phase of system development .Operational
feasibility reviews the willingness of the organization to support the proposed system. In order to
determine this feasibility, it is important to understand the management commitment to the
proposed project. If the request was initiated by management, it is likely that there is management
support and the system will be accepted and used. The operational feasibility is the one that will be
used effectively after it has been developed. If users have difficulty with a new system, it will not

produce the expected benefits. It measures the feasibility of a system in terms of the PIECES
framework. The PIECES framework can help in identifying operational problems to be solved, and
their urgency:
Performance - Does current mode of operation provide adequate throughput and response time?
- In comparison of the earlier process of maintaining data in the written mode on that
contrast this system plays a very important role in maintain this management system and
makes the process of data entering so easier and user friendly.
Information - Does current mode provide end users and administrator with timely, relevant,
accurate and usefully formatted information?
- System provides end users and administrator with timely, relevant, accurate and usefully
formatted information. Since all the user related information is being stored in the database
against a unique user ID, it will provide for meaningful and accurate data to the admin. The
information handling in the current system is done manually. This results in scribbling of
data and loss of validity of data. The information handled in the proposed system will be
computerized and will get automatically updated. The human errors will be minimal. The
data can be easily updated, modified when required and will be validated before the data is
processed into the system.
Economy - Does current mode of operation provide cost-effective information services to the
business? Could there be a reduction in costs and/or an increase in benefits?
- Determines whether the system offers adequate service level and capacity to reduce the
cost of the business or increase the profit of the business. The deployment of the proposed
system, manual work will be reduced and will be replaced by an IT approach. Moreover, it
has also been shown in the economic feasibility report that the recommended solution is
definitely going to benefit the organization economically in the long run.
In the existing system, the data are stored in ledgers which require a lot of space and
maintenance. Access to certain data can be restricted by creating different levels of user
accessibility.
Control - Does current mode of operation offer effective controls to protect against fraud and to
guarantee accuracy and security of data and information?
- As its database does not contain any confidential information which can be misused so on
that contrast there should no use of any security corner for this system.

Efficiency - Does current mode of operation makes maximum use of available resources, including
people, time, and flow of forms?
- Efficiency work is to ensure a proper workflow structure to store patient data; we can
ensure the proper utilization of all the resources. It determines whether the system make
maximum use of available resources including time, people, flow of forms, minimum
processing delay. In the current system a lot of time is wasted on paper work like making
new records, updating records. The proposed system will be efficient in maintaining the
record and easily fetching out the required data.
Services - Does current mode of operation provide reliable service? Is it flexible and expandable?
- The system is desirable and reliable services to those who need it and also whether the
system is flexible and expandable or not. The proposed system is very much flexible for
better efficiency and performance of the organization. The existing system can provide
service only to a limited number of users. The scalability of the proposed system will be
unlimited as the storage capacity of the system can be increased as per requirement. This
will provide a strong base for expansion. The new system will provide a high level of
flexibility.
2.1.2 Technical Feasibility
A large part of determining resources has to do with assessing technical feasibility. It considers the
technical requirements of the proposed system. The technical requirements are then compared to
the technical capability of the organization. The systems project is considered technically feasible,
if the internal technical capability is sufficient to support the project requirements.
The analyst must find out whether current technical resources can be upgraded or added to in a
manner that fulfils the request under consideration. This is where the expertise of system analysts
is beneficial, since using their own experience and their contact with vendors they will be able to
answer the question of technical feasibility.
The essential questions that help in testing the operational feasibility of a system include the
following:
 Is the project feasible within the limits of current technology?
 Does the technology exist at all?
 Is it available within given resource constraints?
 Manpower- programmers, testers & debuggers

 Software and hardware
 Are the current technical resources sufficient for the new system?
 Can they be upgraded to provide the level of technology necessary for the new
system?
 Do we possess the necessary technical expertise, and is the schedule reasonable?
 Can the technology be easily applied to current problems?
 Does the technology have the capacity to handle the solution?
 Do we currently possess the necessary technology?
This management system deals with the modern technology that needs the well efficient technical
system to run this project. All the resource constrains must be in the favour of the better influence
of the system. Keeping all this facts in mind we had selected the favourable hardware and software
utilities to make it more feasible.
Recommended Hardware:-
S. No. Hardware used Specification
1. Monitor LCD 15” screen (HP)
2. Keyboard Intex Wired
3. Mouse Intex Wired
4. Hard drive 40GB(gigabyte) hard drive
5. Ram 512 MB(mega byte)
6. Processor 2.6 GHz Intel Pentium IV
7. Graphics On board graphics card, 8MB(Megabyte)
8. System type 1GHZ(gigahertz)32-bit(x86)

Recommended Software:-
Software plays an important role in any project development. One should understand which
software to use to develop the project. Windows 7 is used as an operating system as it is more
reliable and faster as compared to other operating system.
The software used for the development of the application:
1. Visual Studio 2010
2. Microsoft SQL Server
3. Microsoft Office Visio
4. Microsoft Office Word
2.1.3 Economic Feasibility
Economic analysis could also be referred to as cost/benefit analysis. It is the most frequently used
method for evaluating the effectiveness of a new system. In economic analysis, the procedure is to
determine the benefits and savings that are expected from a system and compare them with costs.
If benefits are more than costs, then the decision is made to design and implement the system. An
entrepreneur must accurately weigh the cost versus benefits before taking an action.
Possible questions raised in economic analysis are:
 Is the system cost effective?
 Do benefits outweigh costs?
 The cost of doing full system study
 The cost of business employee time
 Estimated cost of hardware
 Estimated cost of software/software development
 Is the project possible, given the resource constraints?
 What are the savings that will result from the system?
The concerned business must be able to see the value of the investment it is estimating before
committing to an entire system study. If short-term costs are not overshadowed by long-term gains
or produce no immediate reduction in operating costs, then the system is not economically
feasible, and the project should not proceed any further. If the expected benefits equal or exceed
costs, the system can be judged to be economically feasible. Economic analysis is used for
evaluating the effectiveness of the proposed system. The project costs will only be calculated as a

rough estimate. The exact costs are not required to determine economic feasibility. It is only
required to determine if it is feasible that the project costs will fall within the target budget or
return on investment. A rough estimate of the project schedule is required to determine if it would
be feasible to complete the system project within a required timeframe. The required timeframe
would need to be set by the organization.
Cost Benefits Analysis
It is the process of analyzing the financial facts associated with the system development projects
performed when conducting an opening investigation. The purpose of a cost/benefit analysis is to
answer questions, such as:
 Is the project justified (because benefits outweigh costs)?
 Can the project be completed, within given cost constraints?
 What is the minimal cost to attain a certain system?
 What is the preferred alternative, among system solutions?
Following is the figure showing the approx. amount of cost and benefit to the system:
TANGIBLE COST
DEVELOPMENT COSTS
Windows 7 INR 1500
Microsoft Office Word NA
Visual Studio NA
Monitor INR 4000
Key Board INR 450
Mouse INR 200
Bar Code Reader INR 2550
Hard Drive INR 2000
Ram INR 600

Graphics INR 1700
Processor INR 2000
TOTAL DEVELOPMENT COST INR 15000
INTANGIBLE COST
OPERATIONAL COSTS
Licensing for Software (After
1 year)
INR 10000
Software Upgrades INR 1000
Hardware Upgrades (1 PCs) INR 1000
User Training INR 1000
Network Technician +
Computer Operator
INR 50000
TOTAL OPERATIONAL COSTS INR 63000

2.1.4 Schedule Feasibility
We may have the technology, but that doesn't mean we have the skills required to properly apply
that technology. True, all information systems professionals can learn new technologies. However,
that learning curve will impact the technical feasibility of the project, distinctively, it will impact
the schedule.
 Gantt chart
 Week Distribution
 Workload Matrix
 Gantt chart

 Week Distribution
Deliverable: It is the term used in the project management as a result of the project delivered to the
users. It is the final output described in document or report of the overall project.
Milestone: A project milestone is a measurement of progress toward an outcome whereas the
deliverable is the result of the process. It is the intermediate output of the overall project.
S. No. Task Performed Week Milestone/Deliverable
1. Introduction Week 1
2. Schedule Planning Week 1-2 Feasibility Study, Gantt Chart, Week
Distribution, Workload Matrix
3. Selection of Methodology Week 2-3 SSADM used
4. Problem Analysis
Current System Analysis Week 4 Current System
Project Planning Week 4 Proposed System
5. Investigation Techniques Week 5 Questionnaire and Interview
6. Process Model
Logical Process Model Week 6 Context diagram, Level 0 DFD, Level DFD
Process Specification Week 6 Use Case diagram
7. Data Models
Logical Data Models Week 7 ERD (Entity Relationship Diagram)
8. Event Models Week 7 ELH (Entity Life History)
9. Database Designs Week 8 Design Screens of the database
10. Interactive Screen Designs Week 8 Screen shots of the pages designed
11. Programming Environment
Working with Front – End Week 9 ASP.NET
Working with Back – End Week 9 Microsoft SQL Server
12. Conclusion Week 9-10 Final Conclusion
13. Bibliography Week 10 Harvard Referencing
14. Appendix Week 10 Final Product

 Workload Matrix

Selection of Methodology
As per the project management there should be a proper selection of the methodology so on that
contrast we have to select the methodology for our project i.e. Boca Juniors Management System.
Basically there are two types of methodology used for the projects, Structured System Analysis
and Design Methodology and other is Object Oriented Methodology.
Upon analyzing and reviewing the system, the team have decided to select “Structured Systems
Analysis and Design Method” methodology for the development of Project Management
System, because the system is web-based. The method being used in developing the system is
the System Development Life Cycle (SDLC) which includes project identification and selection,
project introduction and planning, analysis, design, implementation and maintenance.
3.1 Purpose
 Firstly, it provides us with a framework for planning the project.
 Secondly, for the development of web-based projects a short term life-cycle is quite
common as compared to long term life-cycle because it helps in software development with
fewer errors and therefore provides less delivery time and better value.
 Thirdly, the quality of a software development effort is improved by using selected process
techniques.
 Finally, web-based development is a graphical user interface so is should be discussed
separately from the traditional system development.
3.2 Structure
General structure of Life-Cycle Model
Planning
Analysis Design
Implementation
Testing

Each phase produces deliverables required by the next phase in the life cycle. Some phases are also
inter-related with other phase. Planning is done in the first and analysis of the system is continued
after that. Analysis of the system is being translated into design. Code is produced during
implementation that is driven by the design. Testing verifies the deliverable of the implementation
phase.
Planning is the very first phase of the system, in which we decide what the task is for and what all
things we have to do for completion of the project.
Analysis is the second important phase of the life cycle model. In this phase, the research is done
on the existing system and then the alternatives are found for the proposed system.
Design is the phase where the work for system design is produced. The deliverables of design
phase consist of architecture which includes hardware, software and communication.
Implementation is the longest phase of the software development life cycle as the code is
produced from the deliverables of the design phase.
Testing is done on the implementation code to make sure that the product is actually solving the
needs addressed in the system and gathering the other information.
3.3 Scope
SSADM is used in the system as it saves time and also improves the quality of deliverables. It
covers almost each and every step required for website development that includes from
organizational analysis to work design and technical design. It ensures that we will be going
through HCI process which is beneficial and recommended for website design.
Description
SSADM is a method which deals with the information and system design. It is quite old system
design for large scale projects. SSADM is used to determine the information system possibility. It
used the combination of text and diagrams throughout the whole life cycle of a system design. This
method uses logical data modelling, entity event modelling and data flow modelling to determine
how a system must be created or updated. These are followed by requirements analysis, logical
system specification and a final system design.

Reasons for using SSADM
 It is best methodology for web based project management system as the resource
required to implement this model is minimal.
 Earlier this system was done manually and all the work is maintained on register.
 It is less expensive and also less time-consuming as compared to other methodology.
 SSADM reduces the error rate and risk by checking the system.
 SSADM makes the site easy to operate and understandable for the user.
 SSADM does not require very special skills and can easily be taught to the staff.
 This system model is developed and a comprehensive demand analysis is carried out by the
help of SSADM.
 SSADM improves the overall productivity of the specific project and the company.
Problem Analysis
After studying the system and by conducting the requirement analysis we encountered the
following problems in the current model of the system:-
There is no automated system to manage the working of the club.
The work is done manually so it created a lot of problems whether to maintain a large
amount of data or keep in track the records of the players.
The registration of player is done manually, as the number of player increases it is hard to
maintain the information about all the players.
The payroll of the players is maintained manually so there are more chances of errors
which may lead to a conflict.
The sports apparels which are ordered manually so to manage the record is a problem.
The maintenance of the stadium is also a problem which includes keeping the records of all
the chairs, staffs and other records.
There is more loss of data if you have to store a large amount of data manually.
The data loss is not recovered once it is stored manually.

Proposed System
The proposed system is a web based application which allows players to register their details. The
aim of this project is to develop a system that can handle and manage the activities involved in a
football club in an efficient and reliable way. It will help the administrator to do their work in
simple way without any trouble. On the basis of the drawbacks and shortcomings identified in the
present and existing Management system, the solutions have been provided for the better
management.
 The system contains unique user ID and password for both administrator and players.
 The system will allow the players to browse the system and can view their profile only by
using their unique ID.
 As earlier system no more paper work and does not need much man power because it is a
web-based application where all the data goes directly to the database and the admin can
easily retrieve the data according to the choice.
 Security problem issues are solved by this automated system.
 The system will be accessible from anywhere and at anytime. So the players can reach the
system very easily and gets the updated information all the time.
 The maintenance of the stadium can be easily being done as the system itself is a web-
based where data maintenance is not a big issue.
 After every match the players profile is being updated which automatically calculates the
payroll bonus for the players.
 The administrator can easily view the reports of the players just by going through the
system which will save his time as the database is centralized now.
 The administrator will also now can provide the payrolls to the players very easily.
 The computer database maintains players and sports apparels records which will be highly
beneficial for the admin.

Constraints
 The Interface is provided only in English. So, the players must know English language so
that he can easily interact with the system.
 Unique user ID and password is used for identification of players.
 Registered players only have the rights to access the facilities provided by the system.
 The players can access this Management System from any computer that has internet
connection and internet browsing capabilities.
Assumptions
The application is developed by the developers by assuming that:
 The players have sufficient knowledge of computers and interface designed.
 The computer must have internet connection and internet browsing capabilities.
 The players must know English as GUI has been provided in English.
Investigation Techniques
Only making the project is not only the task it requires removing the errors and making the project
more efficient and flexible. After throwing the project in the market, the information about
updating the software is only retrieved by following some investigation technique. The main
purpose of this technique is to collect sufficient, relevant and appropriate data to produce a set of
reliable requirements/ conclusions.
Mainly there are five techniques by which information can be gathered:
i. Questionnaires
ii. Interviews
iii. Focus Groups
iv. Naturalistic Observation
v. Studying Documentation
In the given scenario, we are only concerned with two main investigation techniques through
which we get accurate data most of the times i.e. questionnaires and interview.

6.1 Questionnaire
Questionnaires are a popular means of collecting data particularly when there is a big enquiry. In
this method a questionnaire is being sent to the concerned person (usually by post) with a request
to answer the question and return the questionnaire. In a questionnaire we have questions printed
or typed in a definite order on a form or set of forms which has to be answered by the respondent
who read and understand the questions and write down the reply in the space meant for the purpose
in the question itself.
The advantage of adopting Questionnaire methods are:-
 The cost for doing this research method is low even when there is widely spread
geographically.
 There is no biasness of the interviewer.
 Respondents get enough time to respond.
 Wide geographic area can be covered.
 No pre arrangements are required.
There are certain disadvantages of Questionnaire:-
 Low response rate.
 Questions have to be simple.
 Once questionnaire is sent control over it is lost.
 Slowest method of all methods.
6.2 Interview
Interview is a process where there is an interviewer and an interviewee. The interview method of
data collection involves presentation of oral-verbal stimuli and reply in terms of oral-verbal
responses. This method can be used through personal interview as well as telephonic interview as
per requirement. Here we are going to conduct personal interview. In a personal interview one
person is interviewer who generally asks questions in a face-to-face contact to other person or
persons.

Advantages of personal Interview:
 Good response rate
 they are useful to obtain detailed information about personal feelings,
perceptions and opinions
 respondents' own words are recorded
 interviewees are not influenced by others in the group
Disadvantages of personal Interview:
 they can be very time-consuming
 they can be very expensive method
 Different interviewers may understand and transcribe interviews in different
ways.
 Systematic errors may occur.
So among the following research methods we choose the Questionnaire as it is relatively cheap,
respondents will get time to think and respond. All players have their pre-arranged schedule so
they are so busy if we will conduct interview or observation method they would take much time
and more money would be spent. So we found questionnaire the best method for the survey to
know the requirement from the admin and the players to form the information management
system.
Questionnaires for Administrator:
1.) Do you want to automate the system which is manually now?
a) Yes b) No c) maybe
2.) Do you often do mistakes while calculating the payroll of players?
a) Yes b) No c) sometimes
3.) What do you want the system to be?
a) Accurate b) Fast c) Reliable d) Secure e) all of the above

4.) Do you want to improve the system?
a) Yes b) No
5.) Do you feel burden in maintaining so much of records
a) Yes b) No
6.) Data is lost while storing the records
a) Often b) Always c) Sometimes d) No
7.) Do you feel difficulty in searching the player details?
a) Yes b) No
8.) Do you feel like difficulty in updating the player details?
a) Yes b) No
9.) Do you want the system to keep the record of stadium maintenance?
a) Yes b) No
10.) Are you satisfy with this automated management system?
a.) Yes b.) No c.) Can’t say

Process Model
Process modelling aims to graphically represent the processes which capture, manipulate, store and
distribute data.
7.1 Logical Process Model
 Context diagram
Boca Juniors
Management System
Admin Registering players
Maintenance of stadium
Players
View the profile
View the payroll
Registration confirmation
Managing Player’s Payroll
Purchase Of sports Apparels
Login
Message of payroll update Login Response

 Level 0 DFD
1.0
Registration
Of players
Admin D1.PlayerEnter player details Save Player Details
Registration Confrimation
2.0
Purchase
Sports
Apparels
Selects the items to purchase
D2:Sports
Inventory
Updates the Inventory
3.0
Managing
Payroll
D3:PayrollUpdates the players payroll Updates data
4.0
Maintenance
of the stadium
Updation Confirmation
message
D4: Maintenacne
Updates the cost of
maintenance
Updates the records
Player
6.0
View Player
Details
Enters the player ID
Verifies the player ID
Retrieve the value of the playerDisplay the plyer details
7.0
View the
payroll
Enter the players ID
Verifies the player Id
Retrieves the payroll
detail of the player
Dispalays the payroll
detail
Displays the total
cost of the apparels
bought
5.0
Login
Enter the Id
and
password
D1:Player
Verifies
credentials
Provides
authentication if
Matched
Login successful message

 Level 1 DFD
For Admin
Admin
1.1
Checks player
availability
D1:Player
Asks for player
availability
Availiabiity
status
Returns Player
availability status
1.2
New
Registration
Enter the player
Details
Updates the
player Information
Registration
confirmation
1.3
Verifies old
player
Verifies the player is
old Returns the status
1.4
Renew
Player
Registration
Verification to upate the players record
Renew the players
account
Registration
renewal
confiramation

For Player
Player
5.1
Login
Credentials
D1:Player
Enter Id and
password
5.2
Verification
Of Fields
Checks the
authenticiy
Verifies and
return whether
the values
entered are right
or not
Login successful
message if fields
are right
5.3
Relogin
If the fields entered are wrong
Asks again to enter Id
and password
Re-renters the id and
password
Checks for the
accuracy of id and
password

7.2 Process Specification
 Use Case
BOCA JUNIORS MANAGEMENT SYSTEM
Admin
Login
-End1
*
-End2
*
Player Registration
-End3
*
-End4
*
Maintenance of
stadium
-End5
*
-End6
*
Purchasing Sports
Apparels
-End7
*
-End8
*
Update registraion
«extends»
Payroll Management
Claims by the
players
Bonuses offered
Goals by the player
includes
«uses»
includes
«uses»
inlcudes
«uses»
Cancel Registration
«extends»-End9
*
-End10
*
Player
Login
View Profile
View Payroll
Feedback
-End11
*
-End12
*
-End13
*
-End14
*
-End15
*
-End16
*
-End17
*
-End18
*
Placing order for
apparels
Player
authentication
«extends»
includes
«uses»

Data Model
A data model acts as a diagram or flowchart that illustrates the relationships between data. It is a
technique used for the formalization and documentation of existing processes and events that occur
during application software design and development. This technique captures and translates
complex system designs into easily understood representations of the data flows and processes,
creating a blueprint for construction. Well-documented models allow stakeholders to identify
errors and make changes before any programming code has been written.
8.1 Entity Relationship Diagram
An entity-relationship diagram is a data modelling technique that creates a graphical representation
of the entities, and the relationships between entities, within an information system.
There are basically three main components which we consider while making ERD.
 An Entity is something, real or abstract, about which we store information. It is represented
by a rectangle. For our system there are basically these three entities:
i. Admin
ii. Players
 A Relationship is an association that exists among entities. It is represented by a diamond
shape or by the line connecting the entities.
 The Cardinality defines the relationship between the entities in terms of numbers. The three
main cardinality relationships are: 1:1; 1: M; M: N.

 ERD
Admin
PK ID
Password
Payroll
PK Payroll ID
Player Id
Bonus
Claims
Apparels
PK Id
Quantity
Price
Updates
Manages
Maintenance
PK Maintenance ID
Repairing
M
aintains
Player1
PK Player Id
Name
Address
Registers
Views

Event Model
9.1 Entity Life History
Entity Life History provides us with the third view of the system. It shows the processing cycle of
an entity from creation to deletion. It is basically used to show sequencing, iteration and timing of
an entity. The life of an entity starts when it is created and it ends when it is deleted. Entity life
history shows the values of the attributes of the entity those changes during the life. ELH consists
of three main steps for drawing Entity life history diagram: Sequence, Selection and Iteration.
 ELH
For Admin
Admin
Registration
System
Management
Maintenance
of Stadium
Payroll
management
Purchase
Apparels
Player
Registration
Account
Deletion
Match playing
Bonus
Salary
Increment
Admin Life
Login

For Players
Player
Registration Player Life Account
Deletion
View
Profile
View
Payroll
Claims of
the player
Feedback

Database Designs
10.1 Registration Database
10.2 Sports-Apparels Database

10.3 Payroll Database
10.4 Maintenance Database

Interactive Screen Designs
The screen design for the system has been developed keeping in mind the principles and guidelines
of Human Computer Interaction. Effort has been taken to maintain consistency of design
without sacrificing on the learn ability and simplicity of the designs.
Here are some screen shots of the input/output screen designed for the system.
 Home Page: This is the first page appears on the screen.
Input: The home page will appear in the screen as the user opens the website.
Output: The page will appear “Welcome in the Boca Club” for both the admin as well as
players.
This is the first screen
that appears/Home
Page

 Login: User can choose the user-type and login for the same.
Input: After choosing the user-type i.e. admin or player, the user can login
Output: After clicking the submit button, it will directly take the user to the “Home Page”.
The user choose the
type i.e. Admin or Player
Every data must
be filled

 Registration of Players: This is the registration page of the players by which the
players can become the members of the club.
Input: Player have to fill all the necessary details asked in the registration page for becoming
the member of the club.
Output: After clicking on the register button, the player will become the member of the club
and then he can perform the task as given in the club by the admin.
All details of
players must be
filled
Details of last
club played

 Registration with Validation: Every textbox must be filled while doing registration
of the players, so that he can become the member of the club.
Input: All textbox must be filled with correct information.
Output: After clicking on the register button, if any textbox is left blank, player cannot
become the member of the club and so it will ask to fill the particular textbox.
Any textbox
cannot be left
blank

 Search by Player-Id: By entering the unique player-id, admin can get all the
information about the particular player.
Input: The above screen will appear when admin wants to view the players who all are
the member of the club.
Output: As soon as the player Id is entered by the admin, if it matches with the
database then all the details of that particular player will appear in the screen.
Unique
Player-Id
All the information of
player is fetched from
the database

 Payroll: In this, payroll of the player is being calculated as per the number of matches
and goals made by the player.
Input: Player Id is filled by the admin, if it matches with the database.
Output: After clicking the add button, the payroll will be calculated of that particular
player depending on the number of matches and goals made.

 Maintenance of the Stadium: It is managed by the admin of the club. The cost of
the following things done by the players is calculated.
Input: All the textbox should be filled by the admin, for the maintenance of the stadium.
Output: The cost will be calculated after clicking the add button and is maintained in the
database.

 Sports-Apparel: In this, the admin will purchase the sports-apparel for the players
who all are the members of the club.
Input: The data entry should be done by the admin of the sports-apparel for the club.
Output: After clicking the add button, the total cost of the sports-apparel for the players will be
calculated and also maintained in the database.

Programming Environment
In computer program and software product development, the development environment is the set
of process and programming tools used to create the program or software product. The term may
sometimes also involve the physical environment.
12.1 Front End
ASP .NET is an object-oriented computer programming language that can be viewed as an
evolution of the classic ASP, which is implemented on the .NET Framework. It is a web based
application with a centralized database. This programming language is used because it acts as
an integrated development environment. Our main objective is to make fault free software so
that the users can use it with ease.
 Development Tool- Microsoft Visual Studio 2010
Reasons for selecting ASP.Net as Front End:
 ASP.Net is more efficient and flexible language for writing the computer software. It
provides better performance by taking advantage of early binding.
 It is purely server-side technology so, ASP.NET code executes on the server before it is
sent to the browser.
 It is an object oriented programming language. It contains a systematic collection of
classes and objects.
 It is a framework which is complemented by a rich toolbox and designer in the Visual
Studio.
 It is easy to maintain and develop a system as the software provides most graphical
tools.
 The platform provides easy debugging of errors. So, the probability of errors
occurrence is automatically reduced.

12.2 Back End
SQL Server, the term back-end database is most widely used among developers using small
database programming systems which can contain the end-user application programming
within the database as a single item.
 Development Tool- Microsoft SQL Server 2008
Reasons for selecting Microsoft SQL Server 2008 as Back End:
 Create multiple reports with different views of the same information.
 Create tables quickly without worrying about database complexity
 It helps the developers in programming as it has error resistant SQL code with structured
exception handling.
 Performance of query execution is much faster as compared to SQL Server 2000.
 Documentation Tools
 Microsoft Word 2007: for writing the whole documentation including tables & screen-
shots.
 Microsoft Visio 2007: for making Gantt chart, context diagram, DFD’s, use case, ELH and
ER-diagrams.

CONCLUSION
Finally after the hard work and dedication of more than two months we have successfully
completed the assignment. We have automated the football management system as required by the
owners of the club. They wanted a system to manage the overall process which was done manually
within the club such as registration of the players, managing the payroll of the particular player,
even the maintenance of stadium such as seeding, chair maintenance, watering etc of the club.
We have done extensive research to gather the requirements of the management as how they want
a system that is within cost and time. We have done the analysis to identify the current problems in
the system and have proposed a solution. We have selected appropriate methodology to make the
software by following each of the phases of the methodology. We have the feasibility study of the
system and have opted for the proposal of the system which is feasible economically and
operationally. After that we have made the logical design of the system context diagram, data flow
diagram. We have drawn the ERD for data modelling. After that we have implemented design to
make the system.
It has been a great experience after doing the project we feel like we have learned a lot of things
related to software development. We have increased my knowledge and could further implement
what we have learnt through this project as now we are able to make a system based on the phases
of SDLC.

Bibliography
 Book Referencing
1. Cashman, S. 2002. 2nd ed. Sydney: Shelly Cashman Series.
2. Kendall, K. E. and Kendall, J. E. 1999. Systems analysis and design. Upper Saddle
River, N.J.: Prentice Hall.
3. Ian Sommerville, I. 2008. 7th ed. Software engineering. Delhi: Pearson Education Ltd.
4. Valacich, J. S., George, J. F. and Hoffer, J. A. 2005. Essentials of systems analysis and
design. Upper Saddle River, N.J.: Prentice Hall.
5. James Rook. (2010). DATA COLLECTION METHODS. Available:
http://people.uwec.edu/piercech/researchmethods/data%20collection%20methods/data
%20collection%20methods.htm. Last accessed 23rd March 2014.
6. Mc Fadden Fred R, Hoffer Jeffrey A., Prescott Mary B, Modern Database Management,
Fifth edition, 2001, Addison Wesley Company(Singapore) Pvt., Ltd.
7. Burke Rory, Project Management Planning and Control techniques, Fourth edition 2009,
Santee Offset Printers, Delhi.
 Website Referencing
1. Rouse, M. 2008. What is SSADM (Structured Systems Analysis & Design Method)? -
Definition from WhatIs.com. [online] Available at:
http://searchsoftwarequality.techtarget.com/definition/SSADM [Accessed: 8 March
2014].
2. Cohen, B. 2009. Advantages & Disadvantages of SSADM. [online] Available at:
http://www.ehow.com/list_6781448_advantages-disadvantages-ssadm.html [Accessed:
11 March 2014].
3. (2004). Asp.net and sql. Available:http://www.tutorialized.com/tutorial/Connecting-to-a-
SQL-database-from-ASP-.NET-II/5745.

Appendix
G2- Weekly Reports
Bi-Weekly Report 1
Dated: - 7th
March, 2014
Sir,
We have done the following report during our group project.
 What have we done?
We have studied the assignment and analyzed it extensively, discussed about various
aspects involved in the project of “BOCA FOOTBALL MANAGEMENT SYSTEM”. We had a
collection of ideas from the different group members.
 What are we doing?
We are working on the various ideas suggested by the group members and looking
forward to impose the most feasible idea to make our project a real success. We are also searching
for materials on the World Wide Web and comparing it with our project, to involve that thing in
our project.
 What are we planning to do?
Each individual member has started working on the areas given to him. We are doing
more of research work so that our project outshines the others.
Submitted by: Submitted to:
1) Sumit Kumar Singh PT1181104 Mr. Radha Krishna Rambola
2) Kumar Abhishek PT1181106 (Module Lecturer)
3) Gautam Mishra PT1181108

Bi-Weekly Report 2
Dated: - 14th
March, 2014
Group Members:
Sumit Kumar Singh PT1181104
Kumar Abhishek PT1181106
Gautam Mishra PT1181108
Sir,
Each individual member has started working on the areas given to him. We are doing
more of research work so that our project outshines the others.
We are working on the various ideas based on the research work done by our group
members.We have started with the feasibility report and the various aspects of it.We have also
completed the system analysis part and doing our work accordingly.
After completing the feasibility report we will discuss on the next topic i.e. Selection of
methodology. On the coming week, we will meet with different research done on this particular
topic so that we can enhance more on the same.

Bi-Weekly Report 3
Dated: - 21st
March, 2014
Group Members:
Sir,
We have completed with our feasibility report and the gantt chart and also given a
detailed presentation explaining all the necessary things.We also visited many websites to know
how things are done in the management system.We came across many interesting things which can
be included in our assignment for a realistic approach.
We are working on the various ideas based on the research work done by our group
members.We are working on the various drawbacks and loopholes that we found during our visit
and research. The topic on which we have done more research this days is on Selection of
methodology. We finalised the methodology on which we are going to work on. Side by side we
have started our documentation part.
Each individual member have decided to come prepare with the current problems being
faced by the system and also the proposed solution to overcome those problems.

Bi-Weekly Report 4
Dated: - 28th
March, 2014
Group Members:
Sir,
We completed our work of studying the various loopholes and provided a solution for
the same.We are trying to give the best possible solution for the problems found in the system.
We have started with the making of the DFD’s and other data flow diagrams.A detailed
study regarding the problems and their solutions is being done.Documentation is covered side by
side.
Each individual member have decided to come prepare with the investigation
techniques which we will be best for the system. Every group members are asked to make atleast
ten sample questionnaires for the system.

Bi-Weekly Report 5
Dated: - 4th
April, 2014
Group Members:
Sir,
We completed our work of DFD’s and data flow diagrams.We are now on the verge of
completion of our work.
We are doing the remaining part of the documentation so that we can complete our assignment
on time.Final touch up is given by all the group members so as to shape the assignment in best
possible way. The complete system is completed with all the functionalities working properly,
without any errors. The document part will also be completed in the coming two – three days.

MINUTES OF MEETING
MEETING 1:
VENUE Library
DATE AND TIME 7th
March. 2014,1:30 pm
MEMBERS PRESENT All
TOPIC DISCUSSED Read the assignment completely and divided our tasks
DECISION TAKEN Analysis of the given scenario is to be done
MEETING 2:
VENUE Syndicate Room
DATE AND TIME 14th
March 2014, 3:30 pm
MEMBERS PRESENT All
TOPIC DISCUSSED System design and feasibility study
DECISION TAKEN Feasibility study is to be done
MEETING 3:
VENUE Library
DATE AND TIME 21st
March 2014, 2:45pm
MEMBERS PRESENT Kumar Abhishek, Gautam Mishra
TOPIC DISCUSSED Selection of Methodology
DECISION TAKEN Problems in current scenario and their
recommendations
MEETING 4:
VENUE Syndicate Room
DATE AND TIME 28th
March,2014 , 3:00 pm
MEMBERS PRESENT Sumit Kumar Singh, Kumar Abhishek
TOPIC DISCUSSED Gantt charts, DFDs, ELH and ERD
DECISION TAKEN Data flow and data store concept based works should be
completed soon.

MEETING 5:
VENUE College library
DATE AND TIME 4th
April 2014, 3.30 pm
MEMBERS PRESENT All
TOPIC DISCUSSED Whole system in brief, works that are completed and
remaining topics that is to be covered including
conclusions
DECISION TAKEN By the next week, all topics should be covered and final
documentation will be started by Kumar Abhishek and
Gautam Mishra.

AUTOMATED FOOTBALL MANAGEMENT SYSTEM

More Related Content

What's hot (20)

Similar to AUTOMATED FOOTBALL MANAGEMENT SYSTEM (20)

Recently uploaded (20)

AUTOMATED FOOTBALL MANAGEMENT SYSTEM