SFWR ENG 3MO4
Lab 7,8 and 9

• Due: (note the change) Lab 7 is in 2 parts, one due during the lab, the other due at 14:00, 1 week after your lab (ie right before your next lab), through WebCT. Lab 8 will be due Monday Nov. 29th at 11am for everyone. Lab 9 will be due Sunday Dec. 5th at 11pm for everyone.
• Goals
  • Implement, integrate and test your ABM.
• Details:
  • Sets of 4-5 groups will get together and agree to an interface to each of their modules (see list below). This agreement will be moderated by the TA, who will act as the bank 'owner'. This will be due during the lab.
  • For lab 7, each group will hand in a test suite (sets of calls to MIS functions) which will be used to validate the behaviour of all modules in the system. It is expected that each group will hand in a thorough test suite for their own modules, and a test suite for the other modules that is sufficient for the needs of their modules.
  • For lab 8, a complete implementation (in c) of all modules for each group will be done, as well as automated tests (from lab 7) for their own modules.
  • For lab 9, the sets of teams will get together and integrate both their modules and their test suites.
  The following groups will work together:
  • Team 1: 101,102,103,104,117
  • Team 2: 105,106,107,108,118
  • Team 3: 109,110,111,112
  • Team 4: 113,114,115,116
  • Team 5: 201,202,203,204,221
  • Team 6: 205,206,207,208
  • Team 7: 209,210,211,212
  • Team 8: 213,218,215,216 (note the odd pattern)
  • Team 9: 217,214,219,220 (note the odd pattern)
  If a group has been missed, please inform me or a TA as soon as possible.
  • You will need to work together in larger groups during this whole time. If you do not, you will find lab 9 to be very difficult.
  • Note: your lab mark will be computed as your best 7 of labs 1-8, plus the mark of lab 9.
• Deliverables
  
  1. Lab 7:
     • During lab: for each large team, a coherent set of module interfaces for the 4 top modules.
     • 1 week later: for each group, a test suite. Each test suite consists of test cases. A test case is made up of a sequence of calls to (exported) MIS functions and of expected behaviour (final state, output(s), exception(s)). All exported MIS functions of that group should be thoroughly tested. The top-level exported MIS functions of the other groups' top-level module should be tested as well [according to the needs of your own module(s)]. This can be done abstractly (ie like a simulation); however I highly recommend that you instead 'code up' your test suite in C, as this is needed for lab 8 anyways. One file per module is customary. Should be handed in as one .zip file.
     • A log file, as usual (should be in .zip file)
  2. Lab 8:
     • Nov. 26: for each group, a complete implementation of their modules, along with an automated test suite, as designed in lab 7. All necessary files should be zipped up and handed in as one .zip file.
     • A log file, as usual (should be in the .zip file)
  3. Lab 9:
     • Dec. 3: for each team, an integrated implementation of the ABM project, and and integrated test suite. In other words, the work of all the groups making up a team from lab 8 needs to be made into 1 large program (and test suite). The complete implementation should be submitted as a .zip file. It is expected that each team will submit one integrated implementation. However, a team is allowed to decide to redo the work of (at most) one group, if necessary to properly complete this lab.
     • A log file, as usual (should be in .zip file)
  
  Back to main page