diff -r 10758789e572 -r 6fe6d3548766 docs/requirements.txt
--- a/docs/requirements.txt	Sat Jul 09 09:48:07 2011 +0200
+++ b/docs/requirements.txt	Sat Jul 09 19:14:03 2011 +0200
@@ -15,37 +15,42 @@
 
   EXTERNAL REQUIREMENTS
 
+  #R.01 Proportions and graphic accuracy is maintained on
+        a variety of mobile devices and screen sizes.
+
   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.
+  #R.02 Two opponents use the chess clock to help judge the chess match.
+  #R.03 Functions and UI are configurable, persistent in user's homedir.
+  #R.04 Each opponent can choose their name, shown on their clock.
+  #R.05 Names of well known chess strategists are offered as examples.
+  #R.06 The subclock positions can be swapped at any time.
+  #R.07 Each opponent can choose one of eight colours for their clock.
+  #R.08 Each opponent can choose how many minutes to allocate for their match.
+  #R.09 Display of the hour hand is optional.
+  #R.10 Display of the second hand is optional.
+  #R.11 Display of numbers on the clockfaces is optional.
+  #R.12 Optional audio output indicates which subclock is running.
+  #R.13 The complete configuration state can be stored and given a name.
+  #R.14 The complete configuration can be restored from several stored states.
+  #R.15 The initial state optionally restores the last known configuration.
+  #R.16 Times of well known chess game types (blitz) are offered as examples.
+  #R.17 Static text of the interface is adapted to the user's current locale.
+  #R.18 The locale used in translating static text can be chosen in the GUI.
+  #R.19 A well visible timer flag falls to indicate each opponent's expiration.
+  #R.20 Both subclocks can be paused at the same time during the match.
+  #R.21 All user interaction is limited to basic operation for ease of use.
+  #R.22 Features can be learned quickly by those knowlegable with game clocks.
+  #R.23 Online and offline documentation describes the application.
+  #R.24 Built in help aides the user as well as a traditional manpage.
+  #R.25 Routinely released updates distribute new features and correct flaws.
 
   PERFORMANCE REQUIREMENTS
 
   DESIGN CONSTRAINTS
 
+  #R.26 UI consists of a vertical titlebar and two clockfaces with text labels.
+
   SOFTWARE SYSTEM ATTRIBUTES
 
   OTHER REQUIREMENTS