CS 146: Project Phase 2 – Submission Instructions.

Please follow the instructions below. Failure to follow these instructions may result in your project not being graded completely.

• You are required to submit your source code and report using blackboard.
• The report must be submitted as a PDF file and is due April 9th 3pm.
• The report must describe your system (the workflow, the tables, and your application logic). You must clearly specify the roles of the team members -- i.e., specify who did what (which modules were implemented by whom etc.).
• If you have made any assumptions not listed in the project details page we posted, then clearly list these assumptions in your report in a section titled Assumptions.
• Note: This is not the formal design report that you will submit April 15^th – instead, it is a purely technical document that we want for our reference so we can grade your project.
• For your source code create one zip file and submit the zip file.
• In addition to the report, you must submit a one page document during the demo (April 9^th) that provides the following information (which we will need to conduct our testing):

• Set up your fully functional project and provide us with the URL.
• Provide us with the usernames and passwords for the different users in the system (i.e., the Grad Sec –GS  role, faculty reviewer, faculty advisor, instructor,  chair, sys admin, applicants, students, alumni.)
• Your main page must have a “RESET” button.
• The reset will bring your database to a starting state (i.e., erase all the data and populate it with the data specified below and any other test data that you wish to add). The reset is nothing but a bunch of delete statements followed by insert statements.
• Database Starting state – this is the state that you must get to after a Reset operation. If you have other data that you wish to populate the database with, then feel free to include that but let us know what the data is. Since each team is assigned a specific “project”, not all the data listed below will apply to all projects.
• Unused IDs: Regardless of which system your team is developing, make sure the following names and IDs are not used in your sample data. (The names are listed as Last name, First name and the ID is the SSN)
• Coltrane, John 111-22-3333
• Davis, Miles 222-22-3333
• Monk, Thelonius 333-22-3333
• Getz, Stan 444-22-3333

• RES System. Course schedule: your course registration schedule must be exactly as we specified in the project http://www.seas.gwu.edu/~bhagiweb/cs146/project/course-list.html
• RES System. Current students in system. There must be these two students entered in the system with the data specified below:
• Diana Krall, 666-11-1111. Has registered and completed the following courses:
• CS 210: A, CS211: A, CS232: A
• Stevie Nicks, 777-11-1111. Has registered and completed some courses and is currently registered in some courses.
• completed courses: CS210: A, CS211:A, CS212:A. Currently enrolled in CS232 and CS283
  
• APS System. Applicants: There must be these two applicants entered into the system with the student numbers and other data as specified below:

• John Lennon, 111-11-1111, and application is complete but no reviews.
• Ringo Starr, 222-11-1111, application is incomplete.
• ADS System. Students: There must be these two students entered into the system with the student numbers and other data as specified below:
• Paul McCartney, 333-11-1111. Has registered and completed the 10 courses  (CS210, CS211, CS212, CS241, CS242, CS232, CS233, CS283, CS286, CS220) and received 5 A’s and 5 B’s on these courses. They have NOT applied for graduation.
• George Harrison, 444-11-1111. Has registered and completed the 9 courses and received the grades in the list below:
• CS210: B, CS211: B, CS212:B, CS 232:B, CS233:B, CS 241: B, CS242: B, EE244: C, CS283:B (i.e., all B’s except for a C in EE244).
• ADS System. Alumni: There must be one alumni entered into the system with the student numbers and other data as specified below
• Eric Clapton, 555-11-1111. Has completed 10 courses and received grades in the list below, and graduated 2006 with a Masters degree
• CS210: B, CS211: B, CS212:B, CS 232:B, CS233:B, CS 241: B, CS242: B, CS 283: A, CS 286:A, CS254: A.
• General (users list: Create Grad Secretary (GS), Faculty reviewer named Narahari, Faculty advisor named Price-Jones, Instructor (whatever names you have, but give us their info), database admin.
• Schedule and Evaluation of Demos: Your demos are scheduled for April 9th. The demos will be conducted during the lecture session. ALL team members have to be present for the demo -- questions will be asked of all team members. Failure to attend the demo will result in a grade of zero for Phase 2 -- no exceptions.
• The project testing/demo will require you to go through the entire workflow of your system, and we will be testing it for correctness and completeness.
• We will take you through specific steps and you are required to follow our directions. (This implies that you cannot come up with your own "script" for demo-ing your system.)
• Your system must work correctly, and must meet all the workflow requirements that we posted. Anything less will be considered a sub-standard product. So make sure you get the system working correctly and make sure you do a lot of error checking and testing.
• Bells and whistles are not required at this point in the project; but we will consider these for the final project demo. So focus on getting the basic applications working for now, and if time permits you can work on providing bells&whistles. The final demo (Phase 3) will have a competetive component -- i.e., teams with more bells&whistles (implying a product with more functionality) will earn more points.