Instructor: Dr. Melissa Danforth
Office: Sci III 319, 654-3180
Office Hours: MTuWThF 11:30am - 12:30pm and by appointment
Email: melissa@cs.csub.edu

Course website: http://www.cs.csub.edu/~melissa/ under Teaching menu
Moodle website: https://moodle.cs.csub.edu/moodle/course/view.php?id=107

Course meets Mondays 5:15 to 7:45pm in Sci III 311

This is the completion phase of the project. The student(s) will present a project report to the entire class, explaining the nature of the work, the finished product, and its relationship to the field. Prerequisites: CMPS 490A and upper-division standing. Completion of multiple upper-division CMPS courses
Project selection, design, and beginning implementation in CMPS 490A 3 quarter units. 3 units lecture (150 minutes). Required for CS. None. None. Huaqing Wang CMPS 490B is the second course of a 2-quarter senior programming project sequence, and will complete the implementation phase of the project. This course continues to emphasize application of computer science knowledge to design solutions, and additionally emphasizes code documentation. In this course, students will do the following:

• Work as teams on a team-chosen design problem, which will result in a substantial software project at the end of the 2-course sequence. (continued from CMPS 490A)
• Continue implementation of the project, including updating the timeline, individual responsibilities, and milestones of the project as needed in response to project changes. (continued from CMPS 490A)
• Meet regularly outside of class with their team to work on their project. (continued from CMPS 490A)
• Present their implementation difficulties/problems, solutions, and experiences to the class, and listen for suggestions from others in the class. (continued from CMPS 490A)
• Fully document the code for their project through a detailed final report, as well as present the code to the class with an end-of-term project presentation which is required to contain a demo of the project.

Specific requirements for this course are:

• Orally present to the class at least 3 times. Each team will be assigned a regular presentation time once every two weeks. Every member of the team is expected to present during these times.
• Orally present the finished project to the class at the end of the term.
• Write a final project report that fully documents the code for the project. This report will consist of three parts: an executive summary, a detailed code description, and invidual code diaries.
• Write a personal code diary that documents what each member of the team is doing for the project on a week-by-week basis.
• Complete teamwork evaluations.

Presentations and reports will be evaluated using the oral and written communication rubric posted on Moodle. The course maps to the following performance indicators for Computer Science (CAC/ABET):

3b. An ability to analyze a problem, and identify and define the computing i requirements and specifications appropriate to its solution.

3c. An ability to design, implement and evaluate a computer-based system, process, component, or program to meet desired needs.

3d. An ability to function effectively on teams to accomplish a common goal.

3h. Recognition of the need for and an ability to engage in continuing professional development.

3k. An ability to apply design and development principles in the construction of software systems of varying complexity.

Since this is a very large class, teams will be broken into two groups: Group A and Group B. On presentation weeks, only teams from the scheduled group will present. So each week, about half of the class will present.

Please be present in class when it is NOT your team's week to present, as feedback from class participants is part of the project development process.

Week 1	Monday March 28th	Second Term Requirements and Syllabus
Week 2	Monday April 4th	Group A Progress Presentations
Week 3	Monday April 11th	Group B Progress Presentations
Week 4	Monday April 18th	Group A Progress Presentations
Week 5	Monday April 25th	Group B Progress Presentations
Week 6	Monday May 2nd	Group A Progress Presentations
Week 7	Monday May 9th	Group B Progress Presentations
Week 8	Monday May 16th	Group A Progress PresentationsReport Requirements Q&A
Week 9	Monday May 23rd	Group B Progress PresentationsMajor Field Test for CS and IS concentrations
Week 10	Monday May 30th	Holiday - Memorial Day - Campus Closed
Week 10	Friday June 3rd	Final Project Report due from All Teams
Week 11	Monday June 6th	Last Day of Class: Group A End of Project Presentations
Week 11	Tuesday June 7th	Study Day: Group B End of Project Presentations

The CEE/CS Tutoring Center in Sci III 324 is available for use by students in this course outside of class time on a first come, first serve basis. Priority in the lab is given to students who are completing assignments for CEE/CS courses. See the schedule on the door for hours the lab will be open.

There are also computers available in the CEE/CS Major Study Lounge in Sci III 341 (formerly the CEE/CS Library). This room is only open when faculty members are on campus, e.g. approximately 8am to 5pm on weekdays. If the door is currently locked, see Steve, Erika, myself, or another faculty member to unlock it.

Presentations	40%
Final Project Report	50% (40% team report, 10% for individual code diary)
Teamwork and Participation	10%

Grades are posted on Moodle. Note: Moodle shows your "current" overall class percentage based off the classwork graded to-date. This will update as every grade posts.

It is your responsibility to check Moodle for grades and any comments on assignments. If you believe you submitted your assignment on time but the comment field says "assignment not submitted", contact the instructor.

Students will be expected to give regular oral presentations to the class throughout the quarter. Students will be graded individually based on their part of the team presentation. A presentation rubric will be posted on Moodle, although progress presentations will not always have all the features listed on the rubric. This report will consist of three parts: an executive summary, a detailed code description, and invidual code diaries. The executive summary should give a brief overview of the project problem and design (from the proposal), a brief overview of the development process (key changes made from design and justification for those changes), and an overview of the final project, including screenshots. The detailed code description should fully document and describe the code. Every student should maintain a code diary while working on their portion of the project. This diary should contain the highlights of the research, coding, and troubleshooting done during the term, but does not need to go into deep detail. It should be kept on a week-by-week basis. This portion of your grade will be based on your attendance, on your completion of a teamwork evaluation form, and on your participation in the team. There is no final exam for this class. Your final project presentation and report takes the place of the final exam. Since the final exam is on the same day as Commencement, Group B teams will be presenting on Study Day (June 7th) instead of the final exam day. Melissa Danforth on March 27, 2016 Effective Spring 2016