Know the software

All software has idiosyncrasies and understanding how they work will allow much better presentation within a ground.  There are two things that need to be looked into

What order do things happen in?

To make a seamless presentation inside the ground, it is important to understand when things happen and can be displayed.   For example, in cricket, understanding the order in which things happen when a wicket falls – which is a multiple step operation – will allow a seamless presentation.  When a batter is out, does the ‘how out’ update straight away?  Does it record the delivery as complete?  Where is the dismissed batter’s name put?  What happens when the new batter comes in?

What happens when the limits are reached?

Edge testing is vitally important for all software.  However unlikely it is, thought needs to be given to what happens when someone reaches those limits.

Here are three examples outlining the sort of questions that need to be asked in this are:

1. Although it is unlikely that a team will score ten goals, what happens when they do?  How does that get displayed?  What if all ten goals are scored by different people?  How does that fit onto the display?
2. It is unlikely that more than seven bowlers are used in a match – but what happens if eight are used?  Or more?  How can this be accommodated – or does it need to be?
3. What happens if someone with 8, 10 or 12 letters in their name is in a team?  What happens if someone with more than 12 is in the team?  How does the display look?