NAFscore Specification

Specification for NAF tournament scoring Software (NAFscore)

The NAF are commissioning some new software to facilitate a Tournament Organiser (TO) being able to run a tournament, showing live results, and uploading results to the NAF database. This document details the specification for that tournament software. NAFscore is meant to be an upgrade to Score, the “market leader” in BB tournament scoring software. Score will be the starting point for any development, in that the new software needs to do everything that Score does, but more.
1. The software should have access to the NAF database of members, with their NAF numbers and the ranking for each race. This
is probably best done via an import at the moment, e.g. a button that says “import NAF database”.
2. The TO can then choose those people from the list who are taking part in the tournament, using appropriate lookup functions. There will also need to be the option to add new coaches who are not in the NAF database.
3. The TO can then choose which scoring option they want to use. See Appendix 1.
4. The TO then chooses the race, team name, group, and stunty eligibility. Group is kept as the name for team tournaments, to differentiate from a BB team. Stunty eligibility is for those teams who are eligible for particular prizes, stunty is the most common of these.
5. The first round is produced, usually randomly, but there also need to be options for those from the same group not playing each other. Manual adjustments also need to be a possibility.
6. Round administration refers to printing the draw, match sheets on paper, but also publishing the information to the internet in some form (either a webpage or an app). See Appendix 2.
7. The results are entered – Touchdowns for and against, Casualties for and against, any tournament-specific bonus points, being able to tab through, ideally with a choice of methods.
8. Produce next round (usually) based on the Swiss system, where those on the same points play each other, with the caveat that you can’t play someone you have played before.
9. Final standings include winning individual player, winning group, most Touchdowns, most Casualties, plus “highest rise” (e.g. on day 2). These will however usually mirror the round administration, so is covered in Appendix 2.
10. The results need to be uploaded to the current NAF site, which is currently done via an xml output (though if this could be automated that would be ideal) and to a new area of the NAF website to say who was awarded first, second, third, wooden spoon, most TD, most Cas, stunty cup. These choices would need to be made by the TO, as there are sometimes quirks of the individual tournament.

Appendix 1 – Scoring Options

As in Score, there needs to be the ability to combine at least the following scoring options. This is done by an equation in Score, but a series of boxes would probably be easier.

1. Customisable points for a win, draw or loss
2. Bonus points for TD, Cas, scored or net or suffered
3. Tournament and round-specific bonus points, for example sendings off, crowd surfs
4. Automatically calculated points for a group win

Appendix 2 – Round Administration

At any point, the following items need to be able to be produced:

Customisable printable documents of:

• The draw
• Match report cards, showing who is playing who, which can be filled in with results
• Group report cards, same as the above but with whole groups on each sheet
• Current standings of various kinds (points, group points, TD, Cas)

Web publishing, which can be accessed by participants and those interested around the world. Many venues will not have internet access, so this step is optional (e.g. “publish to web” button).

• The draw for each round
• Current standings of various kinds (points, group points, TD, Cas)

Appendix 3 – Other Functionality

It also needs to be possible to:

• Remove a player from a particular round
• Replace a player midway through a tournament
• Have an odd number of groups, if possible (i.e. a 3-way fixture at the bottom)
• Work on Apple Macs and ideally other operating systems

Other development comments:

• Players to be able to submit their own results
• Players register themselves for the tournament, putting in team name etc
• The option for more than one person to be able to enter results to a tournament at the same time