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