Software Requirements Specification Document part 2 Instructions

Assignment due at the end of the fourth week. Location to be specified by your group's designated TA/instructor. Develop a software requirements specification document (SRS part 2) for your game. PLEASE NOTE: It is common for group members to do some risk reduction activities. Students sometimes experiment with the programming language that they have chosen for their project. They will do a 'quick and dirty' coding of some of the functions specified in their requirements specification. This activity is called a 'proof of concept' and can save time later in the quarter.

• SRS. There are numerous formats to use. See the TA's Information Page for templates. In addition, available from campus IP's, see IEEE Standard 830-1993 Recommended Practice for Software Requirements Specifications. Whichever format you use, please pay particular attention to the following material to be included in your SRS part 2:
  • SRS part 1 was due at the end of week two.
  • External interfaces (user manual and paper prototype) were due at the end of week three.
  • Consistency with earlier milestones. (15)
  • Sequence diagrams. (30)
  • Classes. (30)
  • Performance requirements. (5)
  • Design constraints.
  • Software system attributes. (5)
• Group time recording log. (5)
• Group meeting notes. As a reminder, place them in a section at the back of the notebook. Include in these notes: agenda of meeting, members present, discussion summary, time of meeting, location of meeting, members' roles (moderator, notetaker, time keeper) during meeting. (5)
• Presentation (5)