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