CIS 400 is the beginning of a two-course "capstone" to your undergraduate Computer Science education in which you will have the opportunity to identify, plan, design, implement, and evaluate a computing-based solution to a real-world problem.
In completing this course and the subsequent follow-on course (CIS 401), you will gain experience in:
Information about office hours will be available in Piazza.
In order to achieve the educational objectives listed above, you will work on a group project during the Fall and Spring semesters. The focus of the Fall semester is on identifying and scoping out a problem to address, designing and refining a solution, implementing a prototype, and improving teamwork and communication skills.
Each project team should consist of 4-5 students who are currently registered for CIS 400. Smaller teams will not be permitted without supporting documentation from a CIS faculty member and approval of the CIS 400 instruction staff. If you need help finding teammates, please use the "Search for Teammates!" post in Piazza.
Each team must be advised by a CIS faculty member. Students are expected to meet with their advisor at least four times during the semester, and are responsible for scheduling meetings and keeping their advisor up to date.
The due date for forming teams, writing a short project prospectus, and having it approved by a faculty advisor is 6:00pm on Thursday, September 21. Information about the prospectus, as well the project schedule milestones and deliverables, will be available to registered students via Canvas and discussed at the first class meeting on Tues, Sept 5 (see below).
Your project this semester will consist of three phases as you get your project ramped up, with an eye toward the overall goal of finishing during the Spring semester.
Phase 1: Proposal
Phase 2: Requirements & Design
Phase 3: Prototype
More details for each deliverable will be made available in Canvas.
Students are expected to check in with a TA sometime between their presentations, and should be meeting their faculty advisor regularly.
In addition to the deliverables identified above, all students need to complete an "initial thoughts & observations" document at the start of the semester, and an individual final report at the end.
Last, there will likely be a public demo session for the entire class in early December; details will be made available in Piazza and Canvas.
Instead of regularly scheduled lectures, class meeting times will be used for presentations to and meetings with the instruction staff, and students are only expected to attend on the days when they are presenting.
However, there are two class meetings that are mandatory for all students, even if they are registered for another course that meets at the same time:
Tues, Sept 5: Course overview and logistics (this will be the first class meeting of the semester)
These class meetings will be held from 4:30-5:50pm; the location of each meeting will be posted in Piazza.
If you cannot attend a mandatory class meeting because of a time conflict with another class that regularly meets at that time, please have the instructor of that class contact Prof. Murphy. However, instructors of other classes (e.g. CIS 502, EAS 203, ENM 213, NETS 212, etc.) have been notified of this schedule and have approved CIS 400 students to miss class meetings for those other classes on those dates.
All students must attend and participate in at least one of the three presentation meetings, even if they are registered for another course that meets at the same time. However, students are not required to attend presentations or class meetings on dates when their team is not presenting. But you're always welcome to if you'd like, of course!
Information about grading and other course policies will be made available to registered students in Canvas and at the first mandatory class meeting on Tuesday, Sept 5.