Skip to end of metadata
Go to start of metadata

 

Instructions

 

 

All requirements marked as "must" must be implemented. If one ore more are not implemented, the software cannot be certified.

 

 

Requirements marked as "should" do not need to be implemented for a certification but are recommendations.

 

 

Requirements marked as "action" describe additional information that must be provided prior the certification.

 

 

 

 

No.

Description

Prio

1

Security

 

1.1

It must be possible to prevent the scrutineer to change markings

must

1.2

Only the chairman should be able to unlock the software to change markings by entering a PIN/Password

must

1.3

The chairman must be able to set the password before the event, the password might not be stored in clear letters

must

1.4

It must be possible to create a backup of all data during a competition (e.g. no files locked by the software)

must

1.5

Please provide information if any other security related features are implemented

action

 

 

 

2

Calculation / Skating

 

2.1

The software must proof to calculate the skating system correct. WDSF will provide test-cases for this

must

2.2

The software must implement skating rules 1-11

must

2.3

The software must support the WDSF rules, in specific Redance, Star-Couples, disqualification

must

2.4

Calculation of places must be according to the WDSF rules

must

2.5

The software must support an entry mode for marks "after each dance, single marking" where from each judge and dance the single marking per dance can be entered (not only the sum)

 

2.6

In WDSF competitions, only the marks enter mode single per dance should be allowed

should

 

 

 

3

Print-Outs

 

3.1

The software must be able to print out a list of couples dancing

must

3.2

The software must be able to print out the round drawing sorted by heats and then by numbers

must

3.3

The software should be able to print the round drawing ordered by couples showing what head of what dance they are dancing

 

3.4

The software must be able to print the markings of a round

must

3.5

The software must be able to print a list with names and places of couples dropped out (Ordered by place)

must

3.6

The software must be able to print empty judging sheets with the numbers of couples dancing

must

3.7

The number of couples must be in ascending order

must

3.8

the numbers can be sorted by heats (first heads, then numbers ascending)

should

3.9

All printouts must be in english language and in latin characters

must

3.10

The software must be able to print a list of officals (Adjudicator, Chairman, …)

must

3.11

The software must be able to print the results of the qualification rounds (places, marks)

must

3.12

The software must be able to print the results, calculation and skating table of a final

must

3.13

The software must be able to print a list of couples that are missing/excused

must

 

 

 

4

Data Export

 

4.1

The software must support the WDSF API for  result transmitting

must

4.2

The software should provide a functionality to export results as html

should

4.3

Missing Couples have to be transmitted using the API (see 5.11)

must

 

 

 

 

 

 

 

 

 

5

General

 

5.1

The software must be able to generate a round drawing random and seperated for every dance

must

5.2

The software must be able to generate a round drawing random but all dances the same

must

5.3

The software must be able to generate a round drawing in fixed heats sorted by numbers

must

5.4

The order of dances must be changeable for WDSF Solo finals

must

5.5

The software must be able to support the rules of all relevant WDSF competitions

must

5.6

The software must support a Redance

must

5.7

The software must support disqualification according to the WDSF rules

must

5.8

The software must support seeded (star) couples

must

5.9

The software must support to freely specify the number of marks for the next round. This number must be printed on judging sheets

must

5.10

The user interface must be in english language and latin characters

must

5.11

It must be possible to mark couples, that did not show up, as "missing" or "excused". Missing is a no-show without notice, excused is when the couple informed the scrutineer / organizer that they will not come

must

5.12

In WDSF International Open Competitions it must be possible to change the order of dances in the final (Solo dances)

must

5.13

A PDA solution is required for any WDSF competition

 

5.14The judges-signs (Typically A, B, C, ...) that are used in the competition and are printed on any document in the venue must correspondent to the the results transmitted to WDSF. To make this more understandable: At least one software uses letters A, B, C in all competitions as "internal" signs but sends the results with other signs "external signs". This might lead to confusion so the external and internal signs must be identically. 

 

 

 

6

New Judging System 2.1

 

6.1

The support of the new judging system is optional. If support is implemented, the following requirements should be fulfilled

should

6.2

The software should be able to write the relevant data (judges, couples, heats) in the format used by the official WDSF judging software. For information on the format please see https://bitbucket.org/signalkontor/wdsf-judging-client/wiki/Format_of_data

 

6.3The software should read back the results from the official WDSF judging software. The software should not calculate points itself but use the points and calculation provides by the WDSF software. This is because implementation details of the calculation might change in the future with short notice 
6.4The software should support JS 2.1 where each judge judges only one component per couple 
6.5The software should support JS 2.1 where each judge judges all components per couple (will be used in formation and show dance) 
6.6The software should be aware that the number of components might change (for example in lower classes the choreography might not be judges) 
   
   

7

Mobile Device Software

 

7.1

If the device  crashes, there must be a way to recover the data

must

7.2

The language of the PDA must be at least englisch. Other languages can be supported.

must

7.3

It is required to let the judge sign after the each round

must

7.4

The signature must be placed on the printed judging sheets

must

7.5

The signature can also be digital, if the infrastructure for this can be provided

optional

7.6

The software can support 'Helpmarks' to remember a  couple but not mark it

optional

7.7

If the mobile software supports helpmarks , those helpmarks must not be transformed to marks if the number of marked couples is lower than the requested number

must

7.8

The couples must be sorted by heats and then by numbers on the screen

must

7.9

The heats should be separated in pages to help the judge to find a couple. Moving from heat to heat has to be clear and easy

should

7.10

The judge must confirm his judgments after each dance

must

7.11

Once the judge has confirmed a dance he is not able to return to this dance

must

7.12

Until confirming the judge must be able to change any markings he set

must

7.13

Please provide information on how the system ensures that the complete markings are transferred to the PC

action

7.14

The user of a PDA has to be fixed by name or the using adjudicator has to select his name from the judges list. The competition being judges has to be identified by name at the screen

must

7.15

It must be possible to go back to previous heats within one dance

must

7.16

The screen must display information about the number of couples and the number of couples to bring back to the next round.

must

7.17

There has to be possibilities to give remember points if an adjudicator are not clear about the decision in the first moment

must

7.18

To go to the next dance shall be only possible if the right number of couples is selected to the next round

must

7.19

In a final to give one place more than one time must be clearly displayed as a mistake or disabled

must

7.20

In a final it must be possible to place more than one couple on the last place (if two or more couples stop dancing)

must

7.21

if a couple has to be added which was not registered but due to a fault of the organizer / scrutineer is not on the list, it must be possible to add this couple to the PDA's without any problems

must

7.22

the software must calculate a checksum of the markings of a round and display this checksum to the judge

 

  • No labels
Write a comment…