CMPS 4928 Senior Project II
CMPS Syllabus
CMPS 4910 Oral Communication Rubric
CMPS 4910 Written Communication Rubric
Poster Template for Poster Presentation Day
Templates & Forms
Templates & Forms are "borrowed" from Cal State LA for academic purposes only.Appendix A : Team Members & Assignments. (Individual responsibilities)
Appendix B : *Estimated* Timeline. (Plan the project implementation, including the timeline through May 2020, and milestones of the project.)
Teams and Projects
Class Schedule
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 | 1/23 | Term Overview and Team Check-in with Instructor |
Week 2 | 1/30 | No class meeting. Teams continue to work on projects on own. |
Week 3 | 2/6 | Disscussion & Set Your Goals |
Week 4 | 2/21 | Professional Development Opportunity: Faculty Candidate Presentation (Ashraf Gaffar) |
Week 5 | 2/24 | Professional Development Opportunity: Faculty Candidate Presentation |
Week 6 | 2/26 | Professional Development Opportunity: Faculty Candidate Presentation |
Week 7 | 2/27 | Progress Presentation |
Week 8 | 3/2 | Professional Development Opportunity: Faculty Candidate Presentation |
Week 9 | 3/19 | Progress Presentation |
Week 10 | 3/26 | Professional Development Opportunity: Faculty Candidate Presentation |
Week 11 | 4/2 | Professional Development Opportunity: Faculty Candidate Presentation |
Week 12 | 4/9 | Progress Presentation |
Week 13 | 4/16 | Spring Break / Holiday - Campus Closed |
Week 14 | 4/23 | Expo presentation(Poster based) rehearsal and final product demonstration |
Week 15 | 4/30 | "Virtual Senior Design Expo" follow up |
Week 16 | 5/7 | End of Semester Presentation and Achievement Discussion |
Week 17 | 5/14 | Final Project Reports and Documentation/Peer Evaluations Due |
Personal Statement for the Proposal:
•How do you choose the problem, and what is your analysis of the problem
•Analyze the possible solutions and describe why the team has chosen the approach it is taking.
•Describe the programming tools, developer kits, servers, etc. that the team anticipates it will use to implement the project.
Individual Code Diary:
The code diary is a record of the work each team member had done through the term. It should be organized by week (e.g. Week 1) and summarize the main tasks you completed for the project in that week or the main issues you were researching in that week (even if you could not resolve them until a future week).
End of Term Group Statement:
•What did the team plan to have completed by now? (e.g. summarize plan from proposal)
•What does the team actually have completed now?
•What major changes have been made to your project plan? (e.g. using different tools, changing Tier 1 vs. Tier 2 requirements, adding/removing/changing features, etc.)
•Why were the changes made?
•What is your project plan and timeline for Spring term? (should clearly define the feature status and timeline for Spring term)
•What is your team member responsibilities for Spring term? (should clearly define the feature status and timeline for Spring term)