This Assignment is due by noon on Thursday, Feb. 2.
Please make sure you have read the general Assignment Policies for CISC 323 before beginning this assignment. Please note the following especially:

• you must hand in your assignments to the CISC 323 assignment box on the second floor of Goodwin Hall
• we do not accept late assignments
• you may work alone or with one partner
• we take academic dishonesty very seriously

Please print out a copy of the assignment cover sheet (Word or PDF), fill out the information, and attach it to your assignment.

Overview: By now, all of you should be familiar with the basic description of the CorTrap program. This is a fairly general, vague description and leaves a lot of questions unanswered. In real life, the software team would need to formulate questions, ask the stakeholders, and organize the answers into a precise set of requirements. In this assignment, we will be simulating such a process. You will play the part of Swifp, the software team leader.

As you think of questions about exactly what CorTrap must do, you may find the answers in the basic description or in the additional material we are providing below. If not, you need to take your questions to the stakeholders and engage in a dialog until you understand exactly what they need. Profs. Kelly and Lamb will play the part of Commander Grog, Hobs, and any other stakeholders. Ask your questions via the WebCT forum (Assignment 2 topic) and we will answer them. We promise to check the forum topic at least once a day. We will not answer questions in class, during office hours, or via private e-mail; the reason is that we want to make sure that everyone shares the same same set of questions and answers.

Task: Specify a list of requirements for the user interface part of CorTrap.

Method:

• Create a table with the following information:
  • the list of qualities that you considered
  • the list of questions you considered for each quality (some qualities may not need any questions - the requirement may be immediately obvious)
  • the requirement statements (phrased as testable statements) associated with each quality
  • any comments you consider important about any of your requirements statements
  You should pattern your table after the one used in class. If you want to use Word, here is a Word file containing the blank table used as a starting point in class. If you prefer to use a different program, that's okay too; just create your own table using the same general format. Handwritten tables are acceptable, but only if they are very legible.
• Each requirement statement should be phrased so that it is testable.
• Hand in a hardcopy of your table. Remember that the requirements need to be readable and understandable to the software designer who will be designing CorTrap.
• Also hand in a description of the Problem to be solved, the Stakeholders, and Goals of CorTrap.