• Join over 1.2 million students every month
  • Accelerate your learning by 29%
  • Unlimited access from just £6.99 per month
Page
  1. 1
    1
  2. 2
    2
  3. 3
    3
  4. 4
    4
  5. 5
    5
  6. 6
    6
  7. 7
    7
  8. 8
    8
  9. 9
    9
  10. 10
    10
  11. 11
    11
  12. 12
    12
  13. 13
    13
  14. 14
    14
  15. 15
    15
  16. 16
    16
  17. 17
    17
  18. 18
    18
  19. 19
    19
  20. 20
    20
  21. 21
    21
  22. 22
    22
  23. 23
    23
  24. 24
    24
  25. 25
    25
  26. 26
    26
  27. 27
    27
  28. 28
    28
  29. 29
    29
  30. 30
    30
  31. 31
    31
  32. 32
    32
  33. 33
    33
  34. 34
    34
  35. 35
    35
  36. 36
    36

Creating a computer system for Wooten Basset Rugby Club

Extracts from this document...

Introduction

1 Analysis 1.1 Introduction Wooten Basset Rugby Club, are a rugby club in the Swindon area, whom play 15 a side rugby union. They put out a numbers of teams each week ranging from junior levels, senior teams and women's rugby. Of my concern is the U-16s, whom would like to computerise a number of tasks and have a reference for relevant data including player and parent information. In any particular season there will be between 20 and 30 players at the club. These players are trained by the head coach and around three other coaches all of whom are made up of parents of the players. The head coach is responsible for much of the current administrative work. 1.2 Current System Currently all tasks for the club are carried out manually. For example when organising a match against a rival team a letter is written specifically for each player. With as many as 30 players at the club, this is tiring and tedious work. Data is currently stored in files kept at the head coach's house. This system of holding information has become unreliable as over the history of the team players have moved on or changed their details. When this occurs due to time constraints, addresses for example are often added to rather than modified creating two distinct addresses complicating matters when important letters need to be sent. In the past when players have left their file has not been removed leaving large amounts of useless information. All of this complicates matters when searching for data making the process longer and increasingly unreliable. Among the squad of players, each player has his own specific needs. For example different players require different training methods such as fitness or tactics. With many players and few coaching staff it becomes difficult to organise. Currently this is organised through memory which is difficult due to the above reasons. ...read more.

Middle

1. Leading Drop Kick Scorers, Leading Penalty Kickers, Leading Try Scorers and Leading Points Scorers Each of these reports will present in order the leaders for each respective statistic. For example the Leading Drop Kicks reports will be grouped Player's name but will also hold data on the player's membership number and the number of drop kicks scored. The leading drop kicker comes first and the report will be in descending order downwards. This will be similar for the Leading Penalty Kickers and Leading Try Scorers reports. The Leading Points Scorer report will not only show membership number, name and the descending order of leading points scorers but also display the amount of drop kicks, tries, and penalties scored by that player. The source of this data will be the queries, qryTotalPoints, qryTotalDropKicks, qryTotalPenalties and qryTotalTries. 2. Disciplinary Record The Disciplinary report will present information form qryDisciplinary. It will be grouped by the player's name and display each player's disciplinary record for that season up until that point. This means each yellow or red card received and the match they receive it in will be shown. 3. Season Overview The Season Overview report will be based on the query, qrySeason. It will display all the matches of that season and their scores in chronological order. 2.6 Letter Design Vital to the user's requirements for the system was the facility to create standardised letters. There are three letters the system will provide, one that informs players of outstanding fees and another that informs players of fixture information. The outstanding fees letter will be based on the query, qryFees. The letter relating to fixture information will be based on the qryOrganiserAway and qryOrganiserHome queries. 2.7 Menu Design In order to comply with user requirements the system must be as simple and user friendly as possible. Therefore the menu must be kept simple to avoid confusion. The system will open in a main menu offering the user three options: Add/Delete Data, Reports and Letters. ...read more.

Conclusion

The Add/Delete button has a macro called mcrCloseRivals that closes the form, frmRivals and opens the form, frmAdd/Delete. There is a combo box allowing the user to choose a team name and navigate records this way. frmfixtures This form has a combo box where by choosing a FixtureCode navigates through the records. The Add/Delete Data Button is controlled by the macro, mcrCloseFixtures which closes frmFixtures and opens frmAdd/Delete. The Add Fixture button loads a blank record and the Delete Fixture button deletes the current record. frmTournament This form has a drop down menu where a TournamentCode can be chosen. The Delete Tournament button deletes the current record and the Add Tournament loads a blank record. a macro applied The Add/Delete Button has mcrCloseStats which closes the form, frmStatistic and opens the form, frmAdd/Delete. frmStatistics This form has a sub form called frmPlayers-Fixtures which lists all the records matching a given FixtureCode. To view the record the combo box View Fixture allows the user to choose a precise fixture. The Add/Delete Button has a macro applied mcrCloseStats which closes the form, frmStatistic and opens the form, frmAdd/Delete. 6.2 Queries Queries are all described in the 2.4 Design section. 6.3 Macros Macros described under 6.1Forms. 6.4 Reports Reports are described under the 2.5 Report Design. Rugby Club System 1 Analysis 1 1.1 Introduction 1 1.2 Current System 1 1.3 Interview Summary 2 1.4 Data Requirements 2 1.5 Entity Relationship Diagram 2 1.6 Data Flow Diagrams 2 2 Design 2 2.1 System Design 2 2.2 Attribute Design 2 2.3 Form Design 2 2.4 Query Design 2 2.5 Report Design 2 2.6 Letter Design 2 2.7 Menu Design 2 2.8 Macro Design 2 3 Testing 2 3.1 Testing Strategy 2 Test No. 2 Test 2 Expected Result 2 3.2 Test results 2 4 Appraisal 2 5 User Manual 2 5.1 Adding and Deleting Data 2 5.2 Reports 2 5.2 Letters 2 6 System Maintenance 2 6.1 Forms 2 6.3 Macros 2 6.4 Reports 2 1 Gareth Moore - 4524 New College - 66528 ...read more.

The above preview is unformatted text

This student written piece of work is one of many that can be found in our AS and A Level Computer Science section.

Found what you're looking for?

  • Start learning 29% faster today
  • 150,000+ documents available
  • Just £6.99 a month

Not the one? Search for your essay title...
  • Join over 1.2 million students every month
  • Accelerate your learning by 29%
  • Unlimited access from just £6.99 per month

See related essaysSee related essays

Related AS and A Level Computer Science essays

  1. Marked by a teacher

    LAN & Topologies & Data Flow

    3 star(s)

    * There is a limited amount of cable and workstations that can be used and connected. * If the network is cable is broken it can cripple the whole network, the computer will be functioning but cannot communicate with each other.

  2. Peer reviewed

    Networking Diagrams and Case Study

    3 star(s)

    If any previous network is set up on the individual premises, I would recommend taking it apart, and starting from scratch to ensure that everything is following the new network solution. 2. Check that every workstation is clean from viruses/non-corrupted and doesn?t have data that the entire future network should have access to.

  1. Identify the constituent parts of a total computer system.

    Main store consists of a large number of electronic circuits and all data and information that is processed by the computer has to go through main store. When a sequence of instructions (program) is being executed by the computer system the control unit ensures that the data that is used

  2. Business blue print document for the implementation of SAP R/3 (4.6B) payroll at Mastek ...

    Hence the payroll area defined in the SAP R/3 system for MSI is: - 02 - Semi Monthly - USA PAY SCALE GROUP The Pay Scale Group will be in terms of grades in the organization. The list of Pay Scale Group that is to be customized as under: - 1.

  1. Different ways of data capture

    is loaded * Software is upgraded when necessary and when users are kept informed of changes * A system of regular backups is adhered to. * Network security is maintained. Types of Networks: * Peer to Peer * Server client Server Based Peer to Peer Central backing store available to

  2. ICT Sample Work Welcome Centre Requirements

    of Delegates, Total Room Costs, Total Equipment Costs, Total Beverage Costs, Total Food Costs, Net Amount, VAT Amount, Gross Amount The data can be kept for up to 2 years before being archived. HARDWARE AND SOFTWARE REQUIRMENTS FOR THE USER HARDWARE The Welcome Centre has a variety of different hardware available to be used.

  1. Smart Card System

    damaged in transmit, or it could send a message to the wrong place. It is both more efficient and safer to have TCP compute a separate checksum for the TCP header and data. IP addresses are used to deliver packets of data across a network and have what is termed end-to-end significance.

  2. Security Issues of E-Commerce

    Online Banking and Ebay Online banking is one of the more popular choices of online activities that have migrated from the typical high street chore. Now days more and more people tend to use this type of e-commerce than the traditional shop (bricks and mortar stores).

  • Over 160,000 pieces
    of student written work
  • Annotated by
    experienced teachers
  • Ideas and feedback to
    improve your own work