docs/requirements.txt

changeset 8
6fe6d3548766
parent 0
ff1b43f833a9
     1.1 --- a/docs/requirements.txt	Sat Jul 09 09:48:07 2011 +0200
     1.2 +++ b/docs/requirements.txt	Sat Jul 09 19:14:03 2011 +0200
     1.3 @@ -15,37 +15,42 @@
     1.4  
     1.5    EXTERNAL REQUIREMENTS
     1.6  
     1.7 +  #R.01 Proportions and graphic accuracy is maintained on
     1.8 +        a variety of mobile devices and screen sizes.
     1.9 +
    1.10    FUNCTIONAL REQUIREMENTS
    1.11  
    1.12 -  #R.01 Two opponents use the chess clock to help judge the chess match.
    1.13 -  #R.02 Functions and UI are configurable, persistent in user's homedir.
    1.14 -  #R.03 Each opponent can choose their name, shown on their clock.
    1.15 -  #R.04 Names of well known chess strategists are offered as examples.
    1.16 -  #R.05 The subclock positions can be swapped at any time.
    1.17 -  #R.06 Each opponent can choose one of eight colours for their clock.
    1.18 -  #R.07 Each opponent can choose how many minutes to allocate for their match.
    1.19 -  #R.08 Display of the hour hand is optional.
    1.20 -  #R.09 Display of the second hand is optional.
    1.21 -  #R.10 Display of numbers on the clockfaces is optional.
    1.22 -  #R.11 Optional audio output indicates which subclock is running.
    1.23 -  #R.12 The complete configuration state can be stored and given a name.
    1.24 -  #R.13 The complete configuration can be restored from several stored states.
    1.25 -  #R.14 The initial state optionally restores the last known configuration.
    1.26 -  #R.15 Times of well known chess game types (blitz) are offered as examples.
    1.27 -  #R.16 Static text of the interface is adapted to the user's current locale.
    1.28 -  #R.17 The locale used in translating static text can be chosen in the GUI.
    1.29 -  #R.18 A well visible timer flag falls to indicate each opponent's expiration.
    1.30 -  #R.19 Both subclocks can be paused at the same time during the match.
    1.31 -  #R.20 All user interaction is limited to basic operation for ease of use.
    1.32 -  #R.21 Features can be learned quickly by those knowlegable with game clocks.
    1.33 -  #R.22 Online and offline documentation describes the application.
    1.34 -  #R.23 Built in help aides the user as well as a traditional manpage.
    1.35 -  #R.24 Routinely released updates distribute new features and correct flaws.
    1.36 +  #R.02 Two opponents use the chess clock to help judge the chess match.
    1.37 +  #R.03 Functions and UI are configurable, persistent in user's homedir.
    1.38 +  #R.04 Each opponent can choose their name, shown on their clock.
    1.39 +  #R.05 Names of well known chess strategists are offered as examples.
    1.40 +  #R.06 The subclock positions can be swapped at any time.
    1.41 +  #R.07 Each opponent can choose one of eight colours for their clock.
    1.42 +  #R.08 Each opponent can choose how many minutes to allocate for their match.
    1.43 +  #R.09 Display of the hour hand is optional.
    1.44 +  #R.10 Display of the second hand is optional.
    1.45 +  #R.11 Display of numbers on the clockfaces is optional.
    1.46 +  #R.12 Optional audio output indicates which subclock is running.
    1.47 +  #R.13 The complete configuration state can be stored and given a name.
    1.48 +  #R.14 The complete configuration can be restored from several stored states.
    1.49 +  #R.15 The initial state optionally restores the last known configuration.
    1.50 +  #R.16 Times of well known chess game types (blitz) are offered as examples.
    1.51 +  #R.17 Static text of the interface is adapted to the user's current locale.
    1.52 +  #R.18 The locale used in translating static text can be chosen in the GUI.
    1.53 +  #R.19 A well visible timer flag falls to indicate each opponent's expiration.
    1.54 +  #R.20 Both subclocks can be paused at the same time during the match.
    1.55 +  #R.21 All user interaction is limited to basic operation for ease of use.
    1.56 +  #R.22 Features can be learned quickly by those knowlegable with game clocks.
    1.57 +  #R.23 Online and offline documentation describes the application.
    1.58 +  #R.24 Built in help aides the user as well as a traditional manpage.
    1.59 +  #R.25 Routinely released updates distribute new features and correct flaws.
    1.60  
    1.61    PERFORMANCE REQUIREMENTS
    1.62  
    1.63    DESIGN CONSTRAINTS
    1.64  
    1.65 +  #R.26 UI consists of a vertical titlebar and two clockfaces with text labels.
    1.66 +
    1.67    SOFTWARE SYSTEM ATTRIBUTES
    1.68  
    1.69    OTHER REQUIREMENTS

mercurial