docs/requirements.txt@8e26151e6bd3 (annotated)
docs/requirements.txt
Fri, 08 Jul 2011 22:40:26 +0200
- author
- Michael Schloh von Bennewitz <michael@schloh.com>
- date
- Fri, 08 Jul 2011 22:40:26 +0200
- changeset 1
- 8e26151e6bd3
- child 8
- 6fe6d3548766
- permissions
- -rw-r--r--
Added tag SCHUR_GENESIS for changeset ff1b43f833a9
| 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@0 | 18 | FUNCTIONAL REQUIREMENTS |
| michael@0 | 19 | |
| michael@0 | 20 | #R.01 Two opponents use the chess clock to help judge the chess match. |
| michael@0 | 21 | #R.02 Functions and UI are configurable, persistent in user's homedir. |
| michael@0 | 22 | #R.03 Each opponent can choose their name, shown on their clock. |
| michael@0 | 23 | #R.04 Names of well known chess strategists are offered as examples. |
| michael@0 | 24 | #R.05 The subclock positions can be swapped at any time. |
| michael@0 | 25 | #R.06 Each opponent can choose one of eight colours for their clock. |
| michael@0 | 26 | #R.07 Each opponent can choose how many minutes to allocate for their match. |
| michael@0 | 27 | #R.08 Display of the hour hand is optional. |
| michael@0 | 28 | #R.09 Display of the second hand is optional. |
| michael@0 | 29 | #R.10 Display of numbers on the clockfaces is optional. |
| michael@0 | 30 | #R.11 Optional audio output indicates which subclock is running. |
| michael@0 | 31 | #R.12 The complete configuration state can be stored and given a name. |
| michael@0 | 32 | #R.13 The complete configuration can be restored from several stored states. |
| michael@0 | 33 | #R.14 The initial state optionally restores the last known configuration. |
| michael@0 | 34 | #R.15 Times of well known chess game types (blitz) are offered as examples. |
| michael@0 | 35 | #R.16 Static text of the interface is adapted to the user's current locale. |
| michael@0 | 36 | #R.17 The locale used in translating static text can be chosen in the GUI. |
| michael@0 | 37 | #R.18 A well visible timer flag falls to indicate each opponent's expiration. |
| michael@0 | 38 | #R.19 Both subclocks can be paused at the same time during the match. |
| michael@0 | 39 | #R.20 All user interaction is limited to basic operation for ease of use. |
| michael@0 | 40 | #R.21 Features can be learned quickly by those knowlegable with game clocks. |
| michael@0 | 41 | #R.22 Online and offline documentation describes the application. |
| michael@0 | 42 | #R.23 Built in help aides the user as well as a traditional manpage. |
| michael@0 | 43 | #R.24 Routinely released updates distribute new features and correct flaws. |
| michael@0 | 44 | |
| michael@0 | 45 | PERFORMANCE REQUIREMENTS |
| michael@0 | 46 | |
| michael@0 | 47 | DESIGN CONSTRAINTS |
| michael@0 | 48 | |
| michael@0 | 49 | SOFTWARE SYSTEM ATTRIBUTES |
| michael@0 | 50 | |
| michael@0 | 51 | OTHER REQUIREMENTS |
