CMPS 4910 Senior Project I
CMPS 4910 Syllabus
CMPS 4910 Oral Communication Rubric
CMPS 4910 Written Communication Rubric
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 | 8/29 | Class Overview and Begin Team Selections |
| Week 2 | 9/5 | Finalize Team Selections and Begin Problem Selection |
| Week 3 | 9/12 | Discuss the Topics Details and Finalize the Topic for Each Team |
| Week 4 | 9/19 | Project Proposal Paper due from All Teams <--******--- |
| Week 5 | 9/26 | Presentations on Project Proposal |
| Week 6 | 10/3 | Personal Statement, Appendix A, Appendix B due
<-------******-------- |
| Week 7 | 10/10 | Demonstrations on Project Required Resources & Development Environment |
| Week 8 | 10/17 | Demonstrations on Project Required Resources & Development Environment |
| Week 9 | 10/24 | Individual Code Diary due <-------******-------- |
| Week 10 | 10/31 | Presentations on Project Progress Report Presentation |
| Week 11 | 11/7 | Presentations on Project Progress Report Presentation |
| Week 12 | 11/14 | Updated Individual Code Diary due <-----******--- |
| Week 13 | 11/21 | First-half End of Term Status Presentations |
| Week 14 | 11/28 | No Class - Holiday (Thanksgiving Break) |
| Week 15 | 12/5 | Second-half End of Term Status Presentations |
| Week 15 | 12/5 | Project Intermediate Report, Completed Individual Code Diary, End of Term Group Statement due from All Teams<-----******----- |
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)