This Assignment is due by noon on Tuesday, Feb. 28.
Please make sure you have read the general
Assignment Policies
for
CISC 323 before beginning this assignment. Please note the following especially:
Please print out a copy of the assignment cover sheet (Word or PDF), fill out the information, and attach it to your assignment.
Overview: You have now spent a lot of time thinking about the requirements for the CorTrap program. We hope the exercise has convinced you that gathering requirements is not a quick or simple task! The Q&A process has built up a huge number of requirements. In the real world, you'd have to carry these requirements through to a design and then an implementation. For a 323 assignment, the requirements for CorTrap are too extensive to be the basis for your design. We expected that this would happen, but it was important to go through the exercise of gathering those requirements.
For this assignment, you must create design documents for a simplified version of CorTrap (called SCorTrap, for Simplified Corrosion Tracking program). Your reference will be the SCorTrap Program Requirements.
Task 1: User Interface Pictures
Think through the user interface for SCorTrap. You have been told what the program must do. What should it look like? What will be user see as it navigates through the program? What actions will it have to take (for example, clicking buttons, typing text into boxes, etc.)? Draw a picture of each of the different windows your program will use. We don't care at this point about fonts, colours, exact proportions, or any such details. We want to know what components the user will see (buttons, text fields, labels, etc.) and their approximate layout. We will be talking soon in class about the different kinds of GUI components you might want to use.
Give each of your windows a name, so you can refer to it in later tasks. Include a short (1-2 sentence) description of what each window is used for. You may include any other notes you feel are necessary for helping the reader understand what you have in mind.
Task 2: Activity Diagrams
Create one or more activity diagrams showing all the possible sequences of events through ScorTrap. You will probably not be able to fit everything onto one page, so we suggest breaking things up into a hierarchy of diagrams, as discussed in class.
Task 3: Test Plan
Creating a detailed test plan for the whole program would be a good idea in real life, but too much for this assignment. You must create a detailed test plan for just a subset of the requirements: the core requirement of entering the 7 items of a data from a researcher's card and receiving either an error message or a short report of the researcher's status. The relevant requirements in the SCorTrap Program Requirements document are highlighted in red. You may have to use other functionality to set up the tests -- for example, you might need to create a researcher before you can test the effect of entering data for the researcher -- but these highlighted requirements are the only ones you must test thoroughly.
Click here for more details about what we want for the test plan.
To tell the tester what output to expect, you need some way to know what answers to expect from the calculation engine. Here is an oracle that gives you some sample inputs and the corresponding oxygen exposure.
You don't have to worry about all of the requirements for a formal test plan as discussed in class (the IEEE standard). What we want is a detailed testing script aimed at a tester who is computer literate but may not know anything about the ScorTrap program. Your script should detail each action the tester should take -- push this button, enter this value in this box, check report to make sure exposure value for Worf is 972 BTUs, etc. The tester will give you a report detailing anything that didn't go according to plan. You should test this functionality as thoroughly as possible. Consider legal values, error values, and boundary values for each input. For example, the legal range for O2 content is 0 to 100. You should be trying values inside and outside this range (on both sides of the range), and the boundary values of 0 and 100. You should be making sure the operator can correct its erroneous input or cancel the input operator with no effect on the database.
You may have to use other functionality to set up the tests (for example, create a researcher or ask for a report from the database), but the test plan only needs to do a thorough test of the highlighed requirements.
Samples From An Old Assignment:
You may find it helpful to refer to the sample solution from a similar design assignment from CISC 323 given last winter. It will give you a good idea of the kind of pictures we're after, plus an example of a hierarchy of activity diagrams. Ignore "Task 1" in this assignment; it's a UML use case diagram and we've decided to leave use case diagrams out of this year's version of 323. You get to do the test plan instead.
Formatting:
You may draw your GUI pictures and activity diagrams by hand or use any sort of drawing program that you find convenient. (The diagrams in the sample referenced above were generated using Powerpoint. Powerpoint's "connector" shapes are particularly convenient for activity diagrams.) We're not expecting works of art. The only requirement is that your work be neat and legible.