13 interface, functional, performance, design constraint, and software |
13 interface, functional, performance, design constraint, and software |
14 system requirements. |
14 system requirements. |
15 |
15 |
16 EXTERNAL REQUIREMENTS |
16 EXTERNAL REQUIREMENTS |
17 |
17 |
|
18 #R.01 Proportions and graphic accuracy is maintained on |
|
19 a variety of mobile devices and screen sizes. |
|
20 |
18 FUNCTIONAL REQUIREMENTS |
21 FUNCTIONAL REQUIREMENTS |
19 |
22 |
20 #R.01 Two opponents use the chess clock to help judge the chess match. |
23 #R.02 Two opponents use the chess clock to help judge the chess match. |
21 #R.02 Functions and UI are configurable, persistent in user's homedir. |
24 #R.03 Functions and UI are configurable, persistent in user's homedir. |
22 #R.03 Each opponent can choose their name, shown on their clock. |
25 #R.04 Each opponent can choose their name, shown on their clock. |
23 #R.04 Names of well known chess strategists are offered as examples. |
26 #R.05 Names of well known chess strategists are offered as examples. |
24 #R.05 The subclock positions can be swapped at any time. |
27 #R.06 The subclock positions can be swapped at any time. |
25 #R.06 Each opponent can choose one of eight colours for their clock. |
28 #R.07 Each opponent can choose one of eight colours for their clock. |
26 #R.07 Each opponent can choose how many minutes to allocate for their match. |
29 #R.08 Each opponent can choose how many minutes to allocate for their match. |
27 #R.08 Display of the hour hand is optional. |
30 #R.09 Display of the hour hand is optional. |
28 #R.09 Display of the second hand is optional. |
31 #R.10 Display of the second hand is optional. |
29 #R.10 Display of numbers on the clockfaces is optional. |
32 #R.11 Display of numbers on the clockfaces is optional. |
30 #R.11 Optional audio output indicates which subclock is running. |
33 #R.12 Optional audio output indicates which subclock is running. |
31 #R.12 The complete configuration state can be stored and given a name. |
34 #R.13 The complete configuration state can be stored and given a name. |
32 #R.13 The complete configuration can be restored from several stored states. |
35 #R.14 The complete configuration can be restored from several stored states. |
33 #R.14 The initial state optionally restores the last known configuration. |
36 #R.15 The initial state optionally restores the last known configuration. |
34 #R.15 Times of well known chess game types (blitz) are offered as examples. |
37 #R.16 Times of well known chess game types (blitz) are offered as examples. |
35 #R.16 Static text of the interface is adapted to the user's current locale. |
38 #R.17 Static text of the interface is adapted to the user's current locale. |
36 #R.17 The locale used in translating static text can be chosen in the GUI. |
39 #R.18 The locale used in translating static text can be chosen in the GUI. |
37 #R.18 A well visible timer flag falls to indicate each opponent's expiration. |
40 #R.19 A well visible timer flag falls to indicate each opponent's expiration. |
38 #R.19 Both subclocks can be paused at the same time during the match. |
41 #R.20 Both subclocks can be paused at the same time during the match. |
39 #R.20 All user interaction is limited to basic operation for ease of use. |
42 #R.21 All user interaction is limited to basic operation for ease of use. |
40 #R.21 Features can be learned quickly by those knowlegable with game clocks. |
43 #R.22 Features can be learned quickly by those knowlegable with game clocks. |
41 #R.22 Online and offline documentation describes the application. |
44 #R.23 Online and offline documentation describes the application. |
42 #R.23 Built in help aides the user as well as a traditional manpage. |
45 #R.24 Built in help aides the user as well as a traditional manpage. |
43 #R.24 Routinely released updates distribute new features and correct flaws. |
46 #R.25 Routinely released updates distribute new features and correct flaws. |
44 |
47 |
45 PERFORMANCE REQUIREMENTS |
48 PERFORMANCE REQUIREMENTS |
46 |
49 |
47 DESIGN CONSTRAINTS |
50 DESIGN CONSTRAINTS |
48 |
51 |
|
52 #R.26 UI consists of a vertical titlebar and two clockfaces with text labels. |
|
53 |
49 SOFTWARE SYSTEM ATTRIBUTES |
54 SOFTWARE SYSTEM ATTRIBUTES |
50 |
55 |
51 OTHER REQUIREMENTS |
56 OTHER REQUIREMENTS |