docs/requirements.txt@f83d5d4b7088 (annotated)
docs/requirements.txt
Sun, 10 Jul 2011 10:44:49 +0200
- author
- Michael Schloh von Bennewitz <michael@schloh.com>
- date
- Sun, 10 Jul 2011 10:44:49 +0200
- changeset 11
- f83d5d4b7088
- parent 0
- ff1b43f833a9
- permissions
- -rw-r--r--
Modify icon to be square as most windowing systems expect icons to be.
| michael@0 | 1 | ____ _ _ _ _ _ |
| michael@0 | 2 | / ___| ___ | |__ __ _ ___ | |__ | | | || |__ _ __ |
| michael@0 | 3 | \___ \ / __|| '_ \ / _` | / __|| '_ \ | | | || '_ \ | '__| |
| michael@0 | 4 | ___) || (__ | | | || (_| || (__ | | | || |_| || | | || | |
| michael@0 | 5 | |____/ \___||_| |_| \__,_| \___||_| |_| \___/ |_| |_||_| |
| michael@0 | 6 | |
| michael@0 | 7 | Europalab SchachUhr - Game clock graphical user interface client |
| michael@0 | 8 | |
| michael@0 | 9 | REQUIREMENTS (IEEE 830-1998) |
| michael@0 | 10 | |
| michael@0 | 11 | The SchachUhr application provides an electronic representation of |
| michael@0 | 12 | a traditional game clock and specifies its logic by means of external |
| michael@0 | 13 | interface, functional, performance, design constraint, and software |
| michael@0 | 14 | system requirements. |
| michael@0 | 15 | |
| michael@0 | 16 | EXTERNAL REQUIREMENTS |
| michael@0 | 17 | |
| michael@8 | 18 | #R.01 Proportions and graphic accuracy is maintained on |
| michael@8 | 19 | a variety of mobile devices and screen sizes. |
| michael@8 | 20 | |
| michael@0 | 21 | FUNCTIONAL REQUIREMENTS |
| michael@0 | 22 | |
| michael@8 | 23 | #R.02 Two opponents use the chess clock to help judge the chess match. |
| michael@8 | 24 | #R.03 Functions and UI are configurable, persistent in user's homedir. |
| michael@8 | 25 | #R.04 Each opponent can choose their name, shown on their clock. |
| michael@8 | 26 | #R.05 Names of well known chess strategists are offered as examples. |
| michael@8 | 27 | #R.06 The subclock positions can be swapped at any time. |
| michael@8 | 28 | #R.07 Each opponent can choose one of eight colours for their clock. |
| michael@8 | 29 | #R.08 Each opponent can choose how many minutes to allocate for their match. |
| michael@8 | 30 | #R.09 Display of the hour hand is optional. |
| michael@8 | 31 | #R.10 Display of the second hand is optional. |
| michael@8 | 32 | #R.11 Display of numbers on the clockfaces is optional. |
| michael@8 | 33 | #R.12 Optional audio output indicates which subclock is running. |
| michael@8 | 34 | #R.13 The complete configuration state can be stored and given a name. |
| michael@8 | 35 | #R.14 The complete configuration can be restored from several stored states. |
| michael@8 | 36 | #R.15 The initial state optionally restores the last known configuration. |
| michael@8 | 37 | #R.16 Times of well known chess game types (blitz) are offered as examples. |
| michael@8 | 38 | #R.17 Static text of the interface is adapted to the user's current locale. |
| michael@8 | 39 | #R.18 The locale used in translating static text can be chosen in the GUI. |
| michael@8 | 40 | #R.19 A well visible timer flag falls to indicate each opponent's expiration. |
| michael@8 | 41 | #R.20 Both subclocks can be paused at the same time during the match. |
| michael@8 | 42 | #R.21 All user interaction is limited to basic operation for ease of use. |
| michael@8 | 43 | #R.22 Features can be learned quickly by those knowlegable with game clocks. |
| michael@8 | 44 | #R.23 Online and offline documentation describes the application. |
| michael@8 | 45 | #R.24 Built in help aides the user as well as a traditional manpage. |
| michael@8 | 46 | #R.25 Routinely released updates distribute new features and correct flaws. |
| michael@0 | 47 | |
| michael@0 | 48 | PERFORMANCE REQUIREMENTS |
| michael@0 | 49 | |
| michael@0 | 50 | DESIGN CONSTRAINTS |
| michael@0 | 51 | |
| michael@8 | 52 | #R.26 UI consists of a vertical titlebar and two clockfaces with text labels. |
| michael@8 | 53 | |
| michael@0 | 54 | SOFTWARE SYSTEM ATTRIBUTES |
| michael@0 | 55 | |
| michael@0 | 56 | OTHER REQUIREMENTS |
