And since most of the coaches in NAME OF SCHOOL are teachers, it would be likely that they would have something else to worry about other then football which means they could forget how some players had perform in certain match. They usually just jot down some notes about the player on a piece of scrap paper which (usually) won’t be kept for very long. But having a system means that the coaches can store the information onto the computer and well organised at the same time.
Important information about the players such as their contact details or any medical problem (e.g. Asthma) which are usually hold by either their house master or the school bursar, this could be tricky and time consuming for the coaches to find out. Having a new system could save a lot of trouble for them since they could access to the information whenever they want from their own computer.
Ways to tackle the problem
The best solution for would be create creating a system that monitor pretty much every aspect of NAME OF SCHOOL Football on a database system. It will be well adapted as it is created especially for that purpose.
I can even buy a system, which was made by professional. It will obviously be better but it will be too expensive for the budget that had given by the school and the system won’t be adapt to use by our school as it will be too advance or complicated
Or we could keep using the old method, which was doing everything manually using pen and notepad. But that method is unreliable as information written on paper could be lost and hard to alter the information once it is written on paper and lastly it is easier to organise and sort masses of information on computer.
Sub Problems
Mr Carrington, the Master in charge of football has asked me specifically to include these fields for Fixtures: Name of School, Master in Charge, Teams run, Term played, Address, Phone and e-mail and these fields for Players: Name, Date of Birth, Position, and probably some text on targets/areas to improve etc. And I have decided to include the follow tables and fields as well as those Mr Carrington had requested.
Homepage- As well as the links to other layout in the system, it shows basic information and date so that the system will look more professional and making it more convenient
-Output
The User’s name, for example A.Kon10
The current time
The current date
-Input
N/A
Players Profile – the table that contain all the information about the player such as the position they prefer to play, their phone number and their availability. This layout should be for entering data rather than presenting the data which is the function of a related report that I will create in addition to this layout.
-Output
Photo of the player
Note about the player
-Input
All the information about the player such as his phone number and his age would be input as this is information that is being entered. However it can also be classified as out, should the user decide to look at the fields in the record.
Match Report – as the name suggest, this table contain all the information about the fixture, such as the venue or the time of the fixture. Coaches can review and analysis all the reports throughout the season and evaluate how the team had perform. Moreover the coaches can reflect this back on team and shows them what they have been doing well or bad at.
Input
- Information about the fixture e.g. the time and the venue
-The actual Match Report
Output
-All the information especially the match report, should the coaches decide to go over them again
Team selection – the table that allow the user to pick the best team for the oncoming fixture and be printed off as a team sheet to remind the player what position they are playing.
Output
-Some important details about the fixture, the time, the venue and the players who are involve with the match and the position they are playing. I will include a space on the team sheet to show the positions of the players.
- I will also provide an area for coaches to include any additional information about the fixture such as what the player should be wearing etc.
Input
- The Data that are being entered to the database and in this case, which will be the information mentioned in Output in this table.
Training – The layout that should allow the user to create new training programme.
Output- The print out of the training programme which should also include the data of which training programme valid for. The training programme should inform the players when and what sort of training e.g. fitness or shooting practise, will take place
Input – Before the training programme could be printed out and be uses as a form of output, the user will have to enter information about the training first, which will be the input of this layout.
Injuries and Unavailability - This table will include all the information regarding to the injuries that would prevent the player from participating in the match
Output- details about a player’s injury, such as Day of the injury and expected return date. I will create a related report for this table so that the coaches can check out the injuries within a glance
Input- data that are being entered for this table which are mention above; details about the injury.
Since not every coach is familiar with complicated system, I had to make sure that mine is easy to use + navigate around. I will also create a team selection system where coaches can select the suitable player for the match. It should filter out all the players who don’t meet the criteria. This should make life so much easier for Coaches who just uses the pen and paper for their team selection. As well as that I am going to create a calendar that shows where and when the next fixture will be
Links
Player Profile & Stats will obviously be linked together with team selection to help coaches find the right players. And ‘Fixture & Result’ will be linked with ‘schedule’ it will show what date match or training will happen.
All the related report will be linked to the table obviously. Data will be stored in one place to reduce duplication and save time for the user as they won’t need to enter the same information again.
The related report in this system will be
Players Profile – Players Profile List View
Match Report – Result Overview
Injuries and Unavailability – Injury Table.
Reusability
There will be a password for the system so that only the coaches could edit the information in the database whilst still letting the players access to the system
All tables will be linked to the homepage, and all the related report will be obviously related to its associated report, for example changes made in the table ‘Match Report’ will also causes changes the
Data in ‘Match Report’ will have to be updated after matches, such as the match report and the score. And new fixture can be added onto the database once they have been arranged by the school.
Player will continue to progress and improve their football skill and also some of their personal details might need to be changed (e.g. their phone number); those stats in Player profile will have to be changed. And as pupil will leave or join the school every year, some of their profile will have to be added/ removed from the database.
Homepage will always be different; date changes every day, Daily notice will always are different everyday and ‘next fixture’ will have to be changed every time the next match has been played.
Training Programme could changes as the team progress and new weakness or strength could be discovered, that coaches might decide to design a training programme especially for that area. Training Programme could also changes simply because of the different date.
Team selection could be used over and over again as some of the players might be injured and needed to replace by someone else or other players are more suitable for one particular match
New record could be added to the Injuries and Unavailability Table when player are getting injured
Desired Outcome
The system should be professionally personated, using font that is easy to read and in an appropriate size.
The system should be easy to use and navigate around.
The system should be well structured; some of the table should be linked together using hyperlinks or buttons.
Using colour where it is appropriate to make certain fields’ standout and makes the system looks more attractive
No fields in the database should be left blank
Each Player should have their own unique ID in case the system mixed up player that has the same name.
All the scripts and calculation must work.
Some of the fields could be linked between tables to reduce duplication..
