/*Milestone2.txt*/
  1  
  2  Software Requirements Document (SRD)
  3  ------------------------------------
  4  
  5  As we discussed in class, the Requirements are often done
  6  in 2 parts:  User Requirements and Engineering Requirements
  7  
  8  User Requirements - remember this is totally from the user's perspective:
  9  
 10     Create a document with the following sections:
 11  
 12        Product Description - brief description of the system
 13  
 14        Features :
 15          Numbered list of the functional requirements as the user
 16              understands them
 17  
 18          Numbered list of the non-functional requirements - typically constraints
 19             (e.g., performance, platform/computer resource, portability, 
 20              security)
 21  
 22        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".

           User Interface Pictorials
               
 23  
 24        Credits:  Who did what in this team effort (be specific please)
 25  
 26        Appendix 1:  Show the major subsystems (Configuration Items)
 27           in the system.  These are the major building blocks of the system.
 28           It is desireable if the # of building blocks = # of people working
 29           on the project.
 30  
      DUE IN DRAFT FORM:   9/8

      PEER REVIEW:   9/10

      DUE IN FINAL FORM (on website):   9/13