/*Milestone2.txt*/
  1  
  2  Software Requirements Document (SRD)
  3  ------------------------------------
  4  
  5  We will do the Requirements in 2 parts:  User Requirements and Engineering Requirements
  6  
  7  User Requirements - remember this is totally from the users perspective:
  8                      and only addresses 'WHAT' the system does
  9  
 10     Create a document with the following sections:
 11  
 12        Product Description - brief description of the system
         
 14        Features :
 15          Numbered list of the functional requirements as the user
 16              understands them. 
 18  
 19          Numbered list of the non-functional requirements - typically constraints
 20             (e.g., performance, platform/computer resource, portability, 
 21              security)
 22  
 23        Description of the users of the system (including admin users)
             ** Include here any usage scenarios for these users, ie
                how they interact with the system.  This is often referred
                to as "Use Cases".

           UI pictures so it it is clear what the system will look like
 13  
 24  
 25        Credits:  Who did what in this team effort (be specific please)
 26  
 27        Appendix 1:  Show the major subsystems (Configuration Items)
 28           in the system.  These are the major building blocks of the system.
 29           It is desireable if the # of building blocks = # of people working

DUE IN DRAFT FORM:  Sept. 14

Technical Review:  Sept. 16

DUE IN FINAL FORM (on website):  Sept. 21