Lab06, CISC105, Fall 2004

NOTE: Part of this lab (the test plan part) must be completed IN LAB this week. It is a part of the lab where you may collaborate, but it must be completed IN LAB before you leave lab if you are to be assured of being able to complete the lab on time. If you leave lab without that part done, neither I nor the TAs can be responsible for any delays that may result.

Step 1: Understanding the "tables.c" program: working with arrays, working with fgets, menu-driven structure

In the lab06 directory, there is a program called "tables.c". Your instructor will review this program in lecture (if he/she hasn't already). A list of items to be reviewed appears in the top of this program.

Look over that list of items, and make sure you are comfortable with each of the items indicated there. If not, ask your instructor or TA any questions you have.

Once you are comfortable with the code that is there, you will copy the program to a file called "lab06.c", and make the following modifications:

1. Add an option S to "select" a particular table that the customer wants to reserve (instead of just choosing the first available table.
2. Add an option T to print the total number of guests in the restaurant at any given time.

However, before you get started on that, look at the next step. You really need to get this next step done BEFORE you leave lab today.

Step 1: What you must do IN LAB before you leave: a test plan

Before scripting your results for this program, write a "test plan". A test plan is a essentially the "users" side of the script, and a rough description of what you expect the results of the program to be. That is, you will essentially write a "mock up" of what you expect the final script file to look like, using the text editor (emacs or vi) to create it. You do not have to produce the output exactly in your mock up; a rough description is enough. For example, here's a start for your test plan.

1. Start the program
2. Enter P. It should show all tables empty
3. Enter R, then 4. Then do P again. It should show a table reserved for four people
4. Enter R, then 5. It should reject the 5. Enter 3. Then enter P. You should see one table for four people, and another for 3.
5. Continue reserving tables until all tables are full. Then, try entering one more table. You should see an appropriate error message.
6. etc ...

Your test plan should continue in this fashion until tests for all program features have been included. When you submit your test plan to the TA, he/she will tell you either that it is "complete", or that it is "incomplete". If it is incomplete, you should figure out which feature has not yet been included and add new tests.

If you get the feedback that your test plan is "incomplete", your TA might or might not give you a hint about which feature is not being tested. Note that he/she can't just "tell you" what's missing... your TA would be writing the test plan for you if your TA did that. So, as frustrating as it may be, you'll just have to figure it out. But if you ask nicely for a hint, one might be provided if you are really stuck.

You must work independently on the actual assignment, but you are permitted to collaborate on the test plan part only. You may work in groups of up to four students: indicate in your submission who you worked with. My advice is that you each write your own test plan independentl first, then discuss your plans as a group and merge them into one. Another way is to write the plan as a group, in "brainstorming mode", with one group member acting as secretary. In any case, you must ultimately each submit a copy of your test plan to WebCT along with your submission for this assignment.

Use emacs to create a text file called lab06_test.txt and put your test plan in that file (in plain english). Your test plan should indicate exactly what items you think need to be tested to ensure that all the functionality of your program has been demonstrated—not just your modificaitons, but the basic functionality given in the sample code as well.

Before proceeding to the final script of your work, get your TA or instructor to approve your test plan. At your TAs discretion, one of two methods may be used (follow your TAs instructions as to which one is acceptable:)

• Put your test plan in a directory called ~/public_html/cisc105/lab06/lab06_test.txt, and send email to your TA asking him to sign off. He/she will return email to you indicating that your test plan is acceptable.
• Print a copy of your test plan, and have him/her sign off on paper.

Only one email or print out per group please; use "cc" to include the names of the other folks in your group on the email or printout.

To be sure of being able to complete the lab on time, you should get your test plan approved during the lab session where this assignment is made. If you don't complete the test plan during the lab session, you need to get it done within 48 hours of when the lab is first given out. Your TA is not responsible for any delays that may result from your submitting a test plan for approval later in the week. You should expect anywhere from 24 hours up to 72 hours turnaround time from submission of a test plan to a "yes/no" decision.

Step 2: Make the changes to your program and submit

Once your test plan is written and approved, you are now ready to start coding. See Step 0 above for instructions on what do to.

Step 3: Thinking about enhancements.

The following is a list of additional options that one could consider adding to this program to make it more useful. As your second project, we may assign some or all of the following as additional enhancements. Think about how you would implement each of these, and also about what other features might be useful.

• a feature that keeps track of which servers are assigned to which tables
• the ability to have tables with differing capacities: i.e. some tables can hold only 2 guests, whether other can hold up to 4, or 6 or 8, etc.
• the ability to read the table capacities, number of servers, etc from a file.
• a feature where a guest can choose a particular server, if that server has a free table
• a feature where if the guest doesn't choose a particular table or server, the program chooses a table from the server that currently is serving the fewest number of guests, if that server has an open table. If there is a tie for last place, an arbitrary choice is made to break the tie.
• a feature to keep track of how many guests are currently assigned to each server, and also to track how many guests are served by each server over the course of a day.
  

Now its your turn. Think of a least three other features that would be nice to have in a program of this sort. Then, create a directory ~/public_html/cisc105/lab06, and create a file in that directory called tableIdeas.txt. In that file, describe your three proposed new features. (This is another part of the lab where you may collaborate with up to three other students; if you do, list their names in your tableIdeas.txt file.)

If they are feasible, I'll consider the best ideas for incorporation into the project.

Finishing up and Submitting

1. Make a script that called lab06.txt that follows your test plan. Upload lab06.txt to WebCT and print a copy for your TA.
2. Submit lab06.txt and lab06.c to WebCT. (You don't have to submit your tablesIdeas.txt file to WebCT.)
3. Make sure your ~/public_html/cisc105/lab06/ directory is readable, and contains your tablesIdeas.txt files, and if your TA requests it, your lab06_test.txt file.

Grading: 100 points total

• lab06_plan.txt: 20 points for your test plan.
• lab06.c: 20 points for correctness of each of the two additional features you must add to the program,
  20 points for programming style, neatness of output.
• lab06.txt: 20 points for scripting according to your plan, and submitting and printing correctly.
• tablesIdeas.txt: 20 points for clear explanation of each of the three ideas (5 points for each of the three ideas, and 5 points for having a readable txt file with the correct name in the correct directory)