Instructor: Dr. Albert Cruz
Office Hours (Discord): MTuW 9:50-11:05am, Th 2:15-3:30pm, or email for a
Instructor: Dr. Melissa Danforth
Office Hours (Discord): MTuWThF Noon to 1:00pm or email for a Zoom
Moodle page: https://moodle3.cs.csub.edu/course/view.php?id=51
Section 60: Fridays 1:00 to 2:40pm
Section 61: Fridays 4:00 to 5:40pm
Team check-in times will be scheduled individually between each team and the
instructor for their section.
General Class Structure:
- First Day: Attendance required for class overview and setting up
team check-in times for the remainder of the semester.
- Speaker / Informational Days: Attendance required. These days are noted
in the class schedule.
- Team Check-Ins: All team members are required to attend team check-ins
with the instructor. Teams will individually schedule check-in times
with the instructor. Teams should select a time where everyone on the
team is available.
- Individual Work and Team Work: Self-scheduled individual work and team
work is also expected for this course. Students should plan to spend
about 8 to 10 hours a week (on average) working on their Senior Project
and coordinating with their team.
Contact your instructor as soon as possible if you have any issues with
attending required sessions, such as Internet issues, rotating power outages,
technical difficulties, work conflicts, or other university excused absences.
Students will be required to work in teams in this class. All team work must
be completed virtually, with no face-to-face meetings. Use virtual
collaboration tools such as git, Slack, Discord, Zoom, MS Teams, etc. to manage
your group work and team work.
Note: While the Senior Project is a team project, the course grade for CMPS
4928 will depend heavily on each individual's ability to carry out their share
of the team's tasks, as defined in CMPS 4910 Senior Project I, and to
participate effectively on the team with good teamwork and interpersonal
communication skills. Any changes in assignment of tasks from the CMPS 4910
end-of-term report should be discussed with the instructor during the team
CMPS 4928 - Senior Project II (2)
This is the completion phase of the project. Students will present a project
report to the entire class, explaining the nature of the work, the finished
product, and its relationship to the field. Students will demonstrate
proficiency in critical thinking, information literacy, written communication,
and quantitative reasoning in their written project report. Additionally,
students will demonstrate an understanding of their academic pursuits by
reflecting on their studies of the arts, humanities, natural sciences,
behavioral sciences, and social sciences.
Prerequisites: CMPS 4910, At least 90 semester units, and GE JYDR.
Q2S Transitional Prerequisites for Students on Quarter-System Catalog
(2013-15 or earlier): Senior status and either CMPS 4910 or 490A
Senior status (90+ semester units completed)
Completion of the first course of the Senior Project sequence
Completion of most upper-division General Education requirements, particularly
Junior-Year Diversity Reflection (or approved add slip by instructor)
2 semester units. 2 units lecture (100 minutes).
Required for CS.
All tenured and tenure-track Computer Science faculty members.
AY 2020/21 Coordinators are Albert Cruz and Melissa Danforth.
The course maps to the following ABET Criterion 3 student learning outcomes for
Computer Science (CAC/ABET):
- 2. Design, implement, and evaluate a computing-based solution to meet a
given set of computing requirements in the context of the program's
- 3. Communicate effectively in a variety of professional contexts.
- 4. Recognize professional responsibilities and make informed judgements
in computing practice based on legal and ethical principles.
- 5. Function effectively as a member or leader of a team engaged in
activities appropriate to the program's discipline.
- 6-CS. Apply computer science theory and software development fundamentals
to produce computing-based solutions.
- Goal 1. Students will articulate how their foundational skills, other
General Education coursework, and other major and minor coursework has
prepared them for their career and will help or has helped them achieve
other life goals.
- Outcome 1A. Students will articulate how their foundational skills and
other General Education coursework has prepared them for their career
and will help or has helped them achieve other life goals.
- Outcome 1B. Students will articulate how their major and minor coursework
has prepared them for their career and will help or has helped them
achieve other life goals.
- Goal 2. Students will demonstrate proficiency in critical thinking,
information literacy, oral communication, written communication, and
- Outcome 2A. Students will demonstrate critical thinking, information
literacy, oral communication, written communication, and quantitative
reasoning skills appropriate for a bachelor degree.
- Outcome 2B. Students will create and deliver an effective oral
presentation in a professional manner using information and techniques
appropriate for the subject and audience.
CMPS 4928 is the second part of the two-semester senior design project
sequence, and will complete the project implementation, emphasizing the
problem analysis and problem-solving abilities. In CMPS 4910, teams looked
for a problem, analyzed the problem, and applied their knowledge of computer
science to propose solutions (ABET CAC SLO 1).
In this class, students will do the following:
- Implementation of the project: Teams implement their final solutions and
discuss their projects with the instructor and the class. The project will
be completed during this semester of the course sequence. (ABET CAC
SLOs 2 and 6-CS)
- Teamwork: Teams will be expected to apply appropriate teamwork skills
(interpersonal communication, sharing of project duties, project timeline
and milestones, assignment of tasks to individuals, completion of assigned
tasks, group troubleshooting of issues, etc.), and may be asked to
complete peer evaluations of teamwork skills and efforts at the end of the
term, in addition to the evaluation of teamwork skills by the instructor.
(ABET CAC SLO 5)
- Career seminars: The instructor may invite local professionals to give
seminars during some class meeting times on specific topics in software
design and implementation. There may also be additional career
development opportunities outside of the scheduled class time that will
be announced to the class. (ABET CAC SLO 4)
- Progress reports: Teams will be expected to meet with the course instructor
regularly throughout the semester at established team check-in times to
orally report on their progress in implementing the project. (GE SLO
Cap-2; ABET CAC SLO 3)
- Code repository: Each team will maintain a GitHub or Git repository
for their project. All commits to the repository should clearly identify
the feature implementation / improvement / fix that is being added to the
code base. Individual contribution to the project will be HEAVILY graded
based on the contents of the code repository. (ABET CAC SLOs 2, 5, 6-CS)
- Senior Design Expo: Each team will prepare an entry for their project to
be displayed at the Virtual Design Design Expo, advertised to the campus
in early May. Specific requirements will be posted on the course website.
(GE Cap-2; ABET CAC SLO 3)
- Project Report: Each team will prepare a final written report that fully
documents the project, including both group and individual writing
assignments. Specific report guidelines will be posted on the course
website. (GE-Cap 2; ABET CAC SLO 2, 3, 6-CS)
- Reflection: Each student will be required to complete written reflection
assignments that combine the GE Capstone requirements with computing
ethics. ((GE SLO Cap-1; ABET SLO 4)
The rough weekly schedule is as follows:
|Week 1 (Friday January 29th)
||Term overview and Setting up team check-in times
|Week 2 (February 1st to 5th)
||Team check-ins to update instructor on team's progress since December
|Week 3 (Friday February 12th)
|Hold for speaker Graduation application review (swap weeks 3 and 5)
|Week 4 (February 15th to 19th)
|Week 5 (Friday February 26th)
|Graduation application review Hold for speaker (swap weeks 3 and 5)
|Week 6 (March 1st to 5th)
|Week 7 (Friday March 12th)
||Hold for speaker
|Week 8 (March 15th to 19th)
|Week 9 (Friday March 26th)
||Required class meeting to discuss Virtual Senior Design Expo requirements and deliverables
|Spring Break (March 29th to April 2nd)
||Holiday - Campus Closed
|Week 10 (April 5th to 9th)
||Team check-ins - Special focus on Virtual Senior Design Expo
|Week 11 (Friday April 16th)
||Required class meeting to discuss Final Project Report requirements and deliverables
|Week 12 (Friday April 23rd)
||Deadline for Virtual Senior Design Expo deliverables (poster and video). Class session for teams that need instructors' assistance in recording videos.
|Week 13 (April 26th to 30th)
||Team check-ins - Special focus on any late Expo deliverables and on the final project report, including a review of the team's GitHub or git repository
|Week 14 (May 3rd to 7th)
||No class meeting: Work on reports. Instructor reserves option to schedule a team check-in with any team(s) that appear to be behind on the end-of-project deliverables
|Week 15 (May 10th to 14th)
||Team check-ins - Special focus on final project report, including a review of the team's GitHub or git repository
|Finals Week (Monday May 17th)
||Final Project Report Deliverables and Peer Evaluations Due [edit: typo fix, deliverables are due Monday of Finals Week]
Note: The instructor may require further team check-ins beyond those listed
above on an as-needed, team-by-team, basis. The instructor will email teams
about any additional required check-ins.
All work completed by the teams is expected to be done by the individual team
members, or public code that is used with appropriate instructor approval
and with appropriate citation and documentation. Any public code that is
not appropriately documented and cited in the git repository and the reports
will be considered plagiarism.
Examples of violations of the Academic Integrity policy include, but are not
limited to, the following:
- Submitting junk work to give the appearance of effort. Work submitted
to the team git repository should be relevant to the code, research,
or documentation components of the project. Example: Submitting a
substantial amount to the code base that does not contribute to a
- Submitting an iteration or copy of public code as your own work.
As noted above, public code must be approved by the instructor and
appropriately documented and cited. Example: Most of your contribution
to your group's project is a modification of an online tutorial on
web app games.
- Most of your code base has been reused from an assignment or project
from another class. Example: Iterating your CMPS 3350, 3420, or 3680
- Copying, paraphrasing, or quoting text in your reports or
documentation without proper citation. If you need assistance with
proper citations, the
Writing Resource Center
has resources available to help you. Example: Cutting and pasting
a guide from a manufacturer into your software requirements.
Violations will result in consequences, either to a specific assignment grade
or to the overall course grade. Lack of knowledge is not a reasonable
explanation for a violation.
Refer to the Academic Integrity policy in the campus catalog and class
schedule for more details. You can also refer to the Academic Integrity
policy at the Office of Student Rights and Responsibilities at
To request academic accomodations, please contact the Office of Services
for Students with Disabilities (SSD) and email your instructor an
accomodations letter from
the SSD Office. Policies from the SSD Office relating to accomodations, such
as scheduling policies for using their testng center, must also be followed.
For more information about the services and policies of the SSD Office, contact
their staff by email and/or visit their website at
If you are experiencing challenges related to basic needs, such as food
insecurity, housing insecurity, or other challenges, there are resources
available to you. The campus Food Pantry, located next to the Student
Union, is open with reduced hours during Spring 2021. The Food Pantry also
has information about services and monthly food distributions. Please visit the
website for hours and information. For housing concerns and other basic
needs, please contact the Campus Advocate at 654-6210 or Jason Watkins,
Assistant Director for Basic Needs, at 654-3360.
|Virtual Senior Design Expo||30% (50% individual effort, 50% group effort)
|Final Project Report||55% (85% individual effort, 15% group effort)
|Teamwork and Participation||10% (entirely individual effort)
|Reflection Assignments||5% (entirely individual effort)
Grades are posted on Moodle. 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 for your section.
The goal of the Virtual Senior Design Expo is to showcase your team's project
to the department, campus, and community. Teams will prepare a poster and video
on their project that will be posted to the Virtual Senior Design Expo website.
Specific requirements for those deliverables will be posted to Moodle and
discussed during a mandatory class session. The team's entry in the Virtual
Senior Design Expo will be evaluated using the modified communication rubrics
from CMPS 4910. Each individual on the team is also expected to clearly
identify to the instructor their individual contributions to the entry on the
Moodle assignment for the Expo.
The report will completely document the team's project and each individual's
contributions to the project. The instructor will evaluate the project looking
primarily at the quality of each individual's contributions (85% of the grade
for the final report), along with the complexity and completeness of the
project. This will include an evaluation of the GitHub or git code repository,
in additional to all required written reports. Details will be posted on Moodle.
This portion of the grade will be based on each individual's attendance at
mandatory class meetings, active participation in team check-ins, and the
instructor's evaluation of each person's teamwork skills.
Reflection assignments are individual assignments, not team assignments.
The assignments and their due dates will be posted to Moodle. Every
student is responsible for completing their own reflection assignments and
submitting them through Moodle.
There is no final exam for this class. Your submissions for the Virtual
Senior Design Expo and Final Project Report will take the place of a final
exam in this course.
Melissa Danforth on January 24, 2021
Effective Spring 2021