Course Syllabus
Below is a syllabus template that includes WSU's required syllabus elements. Please complete all items highlighted in yellow.
Software Design Project II
CS 421
Semester and Year [tbd]
3 Credit Hours of Lecture (No Lab)
Prerequisites: CS 420, Senior Standing
Course Details
Day and Time: [tbd]
Meeting Location: [tbd]
Instructor Contact Information
Instructor Name: [tbd]
Instructor Contact Information: [office location, phone, email] [tbd]
Instructor Office Hours: [click here for best practices] [tbd]
TA Name: [tbd]
TA Contact Information: [office location, phone, email]: [tbd]
TA Office Hours: [click here for best practices] [tbd]
Course Description
Large-scale software development in a team environment; software design and implementation,
project management, testing and integration; teamwork skills, communication, source code
management, documentation and presentations. Continuation and completion of CS 420 project.
Course Materials
None
|
Course Learning Outcomes (students will be able to:) |
Activities Supporting the Learning Outcomes | Assessment of the Learning Outcomes |
|---|---|---|
| Implement a solution design through proficient use of software frameworks or tools. | Completion of Capstone project | Direct examination of student work, peer evaluations, evaluation by project sponsor. |
| Verify and validate a software solution against design specifications and project requirements, respectively. | Testing of Capstone project, along with feedback from project sponsor | Direct examination of student work, peer evaluations, evaluation by project sponsor. |
| Communicate effectively in writing with the project sponsor. |
Communication via email and text-based chat (Discord, Slack, Teams, etc) |
Evaluation by project sponsor. |
| Deliver a well-organized presentation to the project sponsor. |
Periodic meetings with sponsors, along with a final presentation at the end of the semester. |
Direct grading of presentation, along with evaluation by project sponsor. |
| Interact with team members and the project sponsor (and staff) in a professional manner. |
Completion of Capstone project |
Peer and sponsor evaluations. |
| Define project goals and tasks as a team. |
Completion of Capstone project |
Peer and sponsor evaluations. |
| Share responsibilities and information on schedule with others on a team. |
Completion of Capstone project |
Peer and sponsor evaluations. |
| Make effective contributions to the design, testing, or integration of a computing solution as a team member. |
Completion of Capstone project |
Peer and sponsor evaluations. |
| Dates | Lesson Topic | Assignment | Assessment |
|---|---|---|---|
|
Week 1 |
Presentation of syllabus, establishing meeting times | Groups schedule meetings with instructor. | |
| Week 15 [dates] |
Final project presentations | Grading of final presentations, with feedback from project sponsors. |
Expectations for Student Effort
Students are expected to work on their projects for an average of six to nine hours per week. This time includes direct work, along with meetings with their teammates, sponsors, and the instructor. Further, it is expected that all group members contribute approximately equal effort to the overall success of the project.
These expectations apply to average over the entire semester. Fluctuations in individual weeks (e.g. due to illness, other coursework, or external forces) are to be expected, and will not be held against students unless they represent a trend.
Grading [add more lines if necessary]
| Type of Assignment (tests, papers, etc) | Percent of Overall Grade |
|---|---|
| Team Collaboration | 20% |
| Final Presentation | 15% |
| Deliverables | 40% |
| Sponsor Evaluation | 20% |
| Professionalism / Discretionary | 5% |
| Grade | Percent | Grade | Percent |
|---|---|---|---|
| A |
>= 93% |
C | 73% - 77% |
| A- | 90% - 93% | C- | 70% - 73% |
| B+ | 87% - 90% | D+ | 67% - 70% |
| B | 83 - 87% | D | 67% - 70% |
| B- | 80% - 83% | F | < 60% |
| C+ | 77% - 80% |
Final grades (but not assignment grades) are rounded to the nearest whole number. Thus, a grade of 89.5%
Attendance and Make-Up Policy
Students are expected to attend their group's scheduled meetings (team, sponsor, and instructor). It is understood that this will not always be possible, and in the event that a student cannot attend they should make an effort to contact their group members in advance. Repeated absences, especially those that are avoidable or interfere with the student's ability to contribute to the project, may affect team collaboration or professionalism scores. Excessive absences may also result in a lower sponsor evaluation if the sponsor notes it.
Academic Integrity Statement
You are responsible for reading WSU's Academic Integrity Policy, which is based on Washington State law. If you cheat in your work in this class you will:
-Receive a 0 on any and all affected work, up to a 0 in the course overall
-Be reported to the Center for Community Standards
-Have the right to appeal my decision
-Not be able to drop the course of withdraw from the course until the appeals process is finished
If you have any questions about what you can and cannot do in this course, ask me.
If you want to ask for a change in my decision about academic integrity, use the form at the Center for Community Standards website. You must submit this request within 21 calendar days of the decision.