diff -r 000000000000 -r ff1b43f833a9 docs/requirements.txt --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/docs/requirements.txt Fri Jul 08 21:05:20 2011 +0200 @@ -0,0 +1,51 @@ + ____ _ _ _ _ _ + / ___| ___ | |__ __ _ ___ | |__ | | | || |__ _ __ + \___ \ / __|| '_ \ / _` | / __|| '_ \ | | | || '_ \ | '__| + ___) || (__ | | | || (_| || (__ | | | || |_| || | | || | + |____/ \___||_| |_| \__,_| \___||_| |_| \___/ |_| |_||_| + + Europalab SchachUhr - Game clock graphical user interface client + + REQUIREMENTS (IEEE 830-1998) + + The SchachUhr application provides an electronic representation of + a traditional game clock and specifies its logic by means of external + interface, functional, performance, design constraint, and software + system requirements. + + EXTERNAL REQUIREMENTS + + FUNCTIONAL REQUIREMENTS + + #R.01 Two opponents use the chess clock to help judge the chess match. + #R.02 Functions and UI are configurable, persistent in user's homedir. + #R.03 Each opponent can choose their name, shown on their clock. + #R.04 Names of well known chess strategists are offered as examples. + #R.05 The subclock positions can be swapped at any time. + #R.06 Each opponent can choose one of eight colours for their clock. + #R.07 Each opponent can choose how many minutes to allocate for their match. + #R.08 Display of the hour hand is optional. + #R.09 Display of the second hand is optional. + #R.10 Display of numbers on the clockfaces is optional. + #R.11 Optional audio output indicates which subclock is running. + #R.12 The complete configuration state can be stored and given a name. + #R.13 The complete configuration can be restored from several stored states. + #R.14 The initial state optionally restores the last known configuration. + #R.15 Times of well known chess game types (blitz) are offered as examples. + #R.16 Static text of the interface is adapted to the user's current locale. + #R.17 The locale used in translating static text can be chosen in the GUI. + #R.18 A well visible timer flag falls to indicate each opponent's expiration. + #R.19 Both subclocks can be paused at the same time during the match. + #R.20 All user interaction is limited to basic operation for ease of use. + #R.21 Features can be learned quickly by those knowlegable with game clocks. + #R.22 Online and offline documentation describes the application. + #R.23 Built in help aides the user as well as a traditional manpage. + #R.24 Routinely released updates distribute new features and correct flaws. + + PERFORMANCE REQUIREMENTS + + DESIGN CONSTRAINTS + + SOFTWARE SYSTEM ATTRIBUTES + + OTHER REQUIREMENTS