The groups consist of three people all of whom are supposed to be attending the same recitation section. If for some reason, you are not attending that particular recitation section, please let me know (IMMEDIATELY) and we can adjust groups. In some cases, there are groups of two. Special instructions are given for the groups of two in the description below.
Tuesday Recitation Groups
Group Number | Names | UBIT Names |
1 | Anthony Dalfonso Brian Gould Ryan Riegel |
ajd28 bjgould2 rdriegel |
2 | Bryan Krol Cory Sandor Jason Sheehy |
bmkrol cjsandor jtsheehy |
3 | Steven Bennett Alex Weidber |
smb36 aweidner |
4 | Jessica Rzeszut Eric Schmidt Jennifer Sylka |
jrzeszut eas5 jsylka2 |
5 | John Deluca Matthew Harkins |
cconlee jdeluca2 harkins3 |
6 | John Driscoll Michael Gilbert |
jfd3 mg76 |
7 | Kailu Hu Donald McArdle |
khu3 dmcardle |
8 | JacobKohane Nicholas Malovich Alexander Sunga |
jhkohane nam8 apsunga |
Wednesday Recitation Groups
Group Number | Names | UBIT Name |
9 | Zachary Bergquist |
zmb cercone7 bdessoye |
10 | Matthew General Regina May Fahad Sherwani |
mgeneral remay sherwani |
11 | Sirak Gizaw Joshua Long Daniel Mulhisen |
sgizaw jlong6 mulhisen |
12 | Richard Carpenter Thomas Driscoll Yingrui Liu |
rdc4 tjd23 yl76 |
13 | Anthony Consiglio Saleh Sayad Sergey Yagunov |
amc62 ssayad syagunov |
14 | Haiku Chandna Jordan Oppenheimer Brandon Pearson |
hchandna jo38 bmp9 |
15 | Jacob Karl Matthew Lehner Dipan Shah |
jrkarl mclehner dmshah |
16 | Matthew Helmbrecht Srinivasan Manoharan |
mjh35 sm346 |
17 | Bhumi Bhagat Ajay Iyer |
bvbhagat |
Thursday Recitation Groups
Group Number | Names | UBIT Names |
18 | Keith Hellerman Chien-Chung Huang Donald Lloyd |
kmh36 cchuang2 djlloyd |
19 | Arslan Afzal Michael Tipton Josh Yagy |
afzal2 mvtipton joshyagy |
20 | John Longanecker William Winnie |
jl353 wmwinnie |
21 | Nicholas Cottrell Adam Matthews Evan Morien |
njc25 amm83 etmorien |
22 | John Barker Jeffrey Becker Nichola Byrne |
jbarker2 jbecker6 nrbyrne |
23 | Narayanan Aswin Keith Baran Thomas Sheeha |
an46 kbaran2 tws5 |
24 | Yu Chang Robert Lockhart |
yuchang rjl9 |
In the course of the next four weeks, each group member will complete each of the following tasks:
Each week, there is a new part of the assignment to be completed. Assume that you have one week for each part of the assignment. That is, do your assignment as though it is due the following week in recitation. Use recitation time to discuss issues and concerns related to the part you just completed or the part upcoming this week, and then use the last week of the assignment due dates to clean things up and submit. All of the submissions are due the Friday before spring break. However, you could realistically be finished almost a week before that if you complete the assignments on the schedule I'm suggesting.
Meet your group members - talk to them prior to recitation - email, exchange other contact information. Meet face to face in recitation and discuss the assignment and any other details. For this first week, you should not meet as a group to discuss the coding that you are doing. Each group member should work independently on this stage. You will bring the results of this week together next week and begin some of the group discussion.
There are three members of your group listed in the charts in a particular order, consider that group member 1 is the first member, group member 2 the second and group member 3 is the third. (If you only have two members, then you only have group member 1 and group member 2 - you do not need to complete the work for group member three). The assigments for each group member this week are as follows.
You are to complete the implementation of a circular, doubly-linked list. The header file that includes the functions you are to implement is available here (Node.h here). Put the header file with your implementation into a directory named CircleDoubleList
. You will zip up this directory and create a CircleDoubleList.zip
and submit it by the due date. You are responsible for the submission of this part of the data structures project.
You should not create any testing code for you implementation and you should not test your implementation in any significant way. If you want to test out the idea for an algorithm in a main function, that is fine, but do not attempt to uncover errors or omissions in the code you wrote. That is the job of another person in your group.
You are to complete the implementation of an array-based binary search tree. The header file that includes the functions you are to implement is available here. Put the header file with your implementation into a directory named BinarySearchTree
. You will zip up this directory and create a BinarySearchTree.zip
and submit it by the due date. You are responsible for the submission of this part of the data structures project.
You should not create any testing code for you implementation and you should not test your implementation in any significant way. If you want to test out the idea for an algorithm in a main function, that is fine, but do not attempt to uncover errors or omissions in the code you wrote. That is the job of another person in your group.
You are to complete a testing program for a circular, doubly-linked list. The header file that includes the functions that you are to test is available here (Node.h here). Your testing program should be named CircleDoubleListTest.cpp
. Your program should ensure that all of the functions outlined in the header file work properly. This program MUST NOT be interactive. The testing that the list goes through is to be outlined in the series of function calls in the program.
You are to complete a report about the test cases for the functions and put it in a file named CircleDoubleListTestPlan.txt
. This report should outline what cases are tested in the testing program and what the expected results are if the list code that it is tested upon is properly implemented.
You will place your C++ file and the test plan file in a directory named CircleDoubleListTest
. You will zip up this directory and create a CircleDoubleListTest.zip
and submit it by the due date. You are responsible for the submission of this part of the data structures project.
For each member of the group, what needs to be submitted is outlined in the description above. Make sure that the submissions contain the appropriate files.
You need to submit your files using the Web-CAT system. For more information about using Web-CAT, please see: http://www.cse.buffalo.edu/faculty/adrienne/SP2009/cse250/Lectures/SubmissionUsingWeb-CAT.ppt
All three data structures assignments are due to be turned in by 11:59:59pm on Friday, March 6th.
Page maintained by Adrienne Decker
Contact: adrienne@cse.buffalo.edu | 130 Bell Hall | (716)645-3180 x 161