Course Syllabus

cs467banner (1).png

Note to screen reader users. This page contains interactive tabs. Screen reader will read through each tab in order, regardless of whichever one is currently being displayed. Please contact me if you need assistance.

Click here to download a pdf version of the syllabus

Click here to download a pdf version of the weekly schedule

Please note that some content linked on this page may only be available to registered students.

General Course Description

At this point in your CS education, you are getting very close to graduating. Congratulations! As part of showing what you've learned, this course will give you an opportunity to take a software project from start to finish. The instructor will play two roles in this course: the facilitator for course work, and the "Client" for your projects.

As a member of a 3-person "Development Team", you will gather requirements from the Client, propose a development plan, and then begin work. Over the course of the term you will be submitting Progress Reports to show what you have been doing. At the end of the term, you will submit a final report and showcase your projects!

You are expected to spend roughly 100 hours total in the assignments for this course, the bulk of which are authoring your Team's software project. Remember that, as in a workplace environment, you will probably be unequally yoked, and you each will have different abilities and skills. Some of you may be more capable programmers than the other members of your group! Remember to communicate frequently and honestly to keep each other appraised of your efforts. Failure to do so has caused many issues in the past!

There are no tests, midterms, or finals in this course


Instructor and TA Information

The instructor for the course is Bill Pfeil.

The GTA(s) for the course are:

Your work may be graded by the instructor or one of the TAs, according to the table below:

Assignment Bill Pfeil Yichuan Yin Iman Aminzahed
Choose Your Project All Dev Teams
Meet Your Team All Dev Teams
Create Project Plan All Dev Teams
Weekly Progress Reports Groups A* - K* Groups L* - Z*
Mid-Point Project Check Groups A* - K* Groups L* - Z*
Create Poster All Dev Teams
Create Final Report Groups A* - K* Groups L* - Z*
Demonstrate Project Groups A* - K* Groups L* - Z*

Career Showcase

Just after Fall and Spring terms end, we hold Career Showcases where you can come hear from companies looking to hire graduates from our program. If you're available, come network with these businesses and sign up for a few time slots to speak directly with them. It's a tremendous opportunity you won't want to miss. The students who attend always rave about it - many of them get jobs and internships as a result. These events are typically held in Portland, OR.

If you would like to attend (attendance is entirely optional, of course), you may share the project you complete in this class at the Showcase using the poster you prepare at the end of this course. Simply let me know you're coming, and that you would like to use your poster, and I'll get it printed and brought with me to the Showcase. Attendance at the Showcase will be required to produce a poster; i.e., I won't print a poster if you're not there.

As part of your poster presentation, the attending employers have a dedicated time where they come by and talk to you about what you're displaying. You don't give a public speech: instead, the employers come to you and ask you about what you're showing. Past attending employers have included Intel, IBM, Mentor Graphics, Ideal-Logic, Columbia Sportswear, HP, Garmin, Daimler Trucks, CBT Nuggets, and tons more! Travel grants are available to get you to Portland, too.

If you have questions, please ask them in our discussion board.


Letters of Recommendation

As much as I enjoy having you in the class, I am generally unable to provide you with a letter of recommendation. I will only be able to write letters for students I know. If you're interested and think I know you well enough, feel free to ask!


About the Instructor

My name is Bill Pfeil and I’ll be your instructor for the Capstone course. I have a M.S. in Math Education from OSU. I did my undergrad at the University of Arizona in Applied Math and ECE. In between my two degrees I spent 25 years as a software engineer, and have worked on everything from client-server apps to games. I am excited to work with all of you as you complete your projects!

Course Name: Online Capstone Project
Course Number: CS 467
Credits: 4
Instructor Name: Bill Pfeil
Instructor Email: pfeilw@oregonstate.edu
Teaching Assistant name and contact info:

This syllabus describes the administrative parts of the course and serves as a contract between student and instructor. Remaining in this course indicates acceptance of these rules.

Remember that in this Capstone course, you are expected to behave professionally. Please use this document throughout the course.


Table of Contents


Course Description

Real-world team-based experience with the software engineering design and delivery cycle, including requirements analysis and specification, design techniques, and requirements and final project written documentation. For students in the online CS double-degree program only.

Prerequisites: CS 344 with C or better and CS 361 [C] and CS 362 [C]


Communication

If I need to contact you, I will email you directly (or via the class mailing list).

Here are the two preferred ways to contact me:

Message me directly on Slack. Note that I cannot answer any grading/personal questions on the osu-cs workspace because it isn't "authenticated". You must use the official OSU workspace for these questions.

Email me directly at pfeilw@oregonstate.edu (If I don't respond in 24 hours please email me again)

Note:  Messaging me on Canvas is an unreliable and indirect way to send me an email that I am less likely to notice in the sea of Canvas notification and daily digest spam from several courses I am subscribed to.

 

We are not Debuggers, Programmers, or Architects — that's your job! Do not send the instructor or TAs any code except what is required for your assignment submissions.

Don't expect the instructor or the TAs to see comments left with assignment submissions. Canvas allows us to download the entire class's submissions as one .zip file, which does not include these comments. If you need to make a meta-comment about your submission, add it to the submission or email the person grading that submission directly.


Course Credits

This course is online only, and requires approximately 100 hours of student work on their capstone projects for a total of 4 credits. Time spent interacting with course content outside of the project, itself, is minimal.


Technical Assistance

If you experience any errors or problems while in your online course, contact 24-7 Canvas Support through the Help link within Canvas.  If you experience computer difficulties, need help downloading a browser or plug-in, or need assistance logging into a course, contact the IS Service Desk for assistance. You can call (541) 737-8787 or visit the IS Service Desk online.


Learning Resources

All class materials can be found on the course web-page. There is no textbook; students are expected to source their own learning resources to accomplish the goals of their projects. A microphone and screen-recording device is required, for submitting weekly project update videos.

Note to prospective students: Please check with the OSU Beaver Store for up-to-date information for the term you enroll (OSU Beaver Store Website or 800-595-0357). If you purchase course materials from other sources, be very careful to obtain the correct ISBN.


Measurable Student Learning Outcomes

After completion of this course, students will have demonstrated an ability to:

  • Outline project requirements.
  • Design a project plan.
  • Summarize and explain their progress.
  • Appraise a project, by authoring a final report.
  • Demonstrate their final product.

Evaluation of Student Performance

    • Syllabus Quiz and Project Choice - 20 points
    • Project Planning Stage - 70 points
    • Weekly Progress Reports - 100 points
    • Midpoint Progress check - 30 points
    • Final Report Documents - 80 points
    • Final Demonstration - 200 points
    • Total - 500 points

Letter Grade

Grading responsibilities are shared between the instructors and the TAs. The Course Introduction tab details who grades which assignment, and which groups each person will grade.

You are expected to spend at least 100 hours on the course. Projects that do not reflect this investment will be graded accordingly

Your group will not create your grade for you. You need to accomplish the goals you sign off on by submitting your Project Plan. In this course, failure to communicate with your team, or to provide reasonably working code compatible with the project per the specification may result in you receiving a non-passing grade while the rest of your group passes. You may be removed from your team if you are found to no be putting in the required amount of work.

Total Percentage vs. Letter Grade

 100 ╺┓
      ┣╸A
92.95╺┫ 
      ┣╸A-
89.95╺┫ 
      ┣╸B+
86.95╺┫ 
      ┣╸B
82.95╺┫ 
      ┣╸B-
79.95╺┫ 
      ┣╸C+
76.95╺┫ 
      ┣╸C
72.95╺┫ 
      ┣╸C-
69.95╺┫ 
      ┣╸D+
66.95╺┫ 
      ┣╸D
62.95╺┫ 
      ┣╸D-
59.95╺┫ 
      ┣╸F
   0 ╺┛


Course Policies

Discussion Participation

Students are expected to participate in all graded discussions. While there is great flexibility in online courses, this is not a self-paced course.

Late Work Policy

Most assignments allow submissions up to two days after the due date for a reduced maximum score. Each assignment has a due date listed on Canvas. Assignments that may be submitted late also have an available until date, which is 48 hours after the initial due date. For these assignments, the following policy applies:

  • Assignments submitted on the day after the due due date will be graded normally and then any points past a 90% point total will be lost.
  • Assignments submitted on the second day after the due date will be graded normally and then any points past a 75% point total will be lost.

Note that, unlike in other courses, late assignment grades will not be scaled by some factor; any points above a threshold (90% or 75%) will simply be discarded.


Makeup Exams

This course has no tests or exams.


Incompletes

Incomplete (I) grades will be granted only in emergency cases (usually only for a death in the family, major illness or injury, or birth of your child), and if the student has turned in 80% of the points possible (in other words, usually everything but the final paper). If you are having any difficulty that might prevent you completing the coursework, please don’t wait until the end of the term; let me know right away.


Guidelines for a Productive and Effective Online Classroom

Students are expected to conduct themselves in the course (e.g., on discussion boards, email) in compliance with the university’s regulations regarding civility. Civility is an essential ingredient for academic discourse. All communications for this course should be conducted constructively, civilly, and respectfully. Differences in beliefs, opinions, and approaches are to be expected. In all you say and do for this course, be professional. Please bring any communications you believe to be in violation of this class policy to the attention of your instructor.

Active interaction with peers and your instructor is essential to success in this online course, paying particular attention to the following:

  • Unless indicated otherwise, please complete the readings and view other instructional materials for each week before participating in the discussion board.
  • Read your posts carefully before submitting them.
  • Be respectful of others and their opinions, valuing diversity in backgrounds, abilities, and experiences.
  • Challenging the ideas held by others is an integral aspect of critical thinking and the academic process. Please word your responses carefully, and recognize that others are expected to challenge your ideas. A positive atmosphere of healthy debate is encouraged.

Statement Regarding Students with Disabilities

Accommodations for students with disabilities are determined and approved by Disability Access Services (DAS). If you, as a student, believe you are eligible for accommodations but have not obtained approval, please contact DAS immediately at 541-737-4098 or at http://ds.oregonstate.edu. DAS notifies students and faculty members of approved academic accommodations and coordinates implementation of those accommodations. While not required, students and faculty members are encouraged to discuss details of the implementation of individual accommodations.


Accessibility of Course Materials

All materials used in this course are accessible. If you require accommodations please contact Disability Access Services (DAS).

Additionally, Canvas, the learning management system through which this course is offered, provides a vendor statement certifying how the platform is accessible to students with disabilities.


Expectation for Student Conduct

Student conduct is governed by the university’s policies, as explained in the Student Conduct Code. Students are expected to conduct themselves in the course (e.g., on discussion boards, email postings) in compliance with the university's regulations regarding civility.


Academic Integrity

Students are expected to comply with all regulations pertaining to academic honesty. For further information, visit Student Conduct and Community Standards, or contact the office of Student Conduct and Mediation at 541-737-3656.

OAR 576-015-0020 (2) Academic or Scholarly Dishonesty:

  1. Academic or Scholarly Dishonesty is defined as an act of deception in which a Student seeks to claim credit for the work or effort of another person, or uses unauthorized materials or fabricated information in any academic work or research, either through the Student's own efforts or the efforts of another.

  2. It includes:

    1. CHEATING - use or attempted use of unauthorized materials, information or study aids, or an act of deceit by which a Student attempts to misrepresent mastery of academic effort or information. This includes but is not limited to unauthorized copying or collaboration on a test or assignment, using prohibited materials and texts, any misuse of an electronic device, or using any deceptive means to gain academic credit.

    2. FABRICATION - falsification or invention of any information including but not limited to falsifying research, inventing or exaggerating data, or listing incorrect or fictitious references.

    3. ASSISTING - helping another commit an act of academic dishonesty. This includes but is not limited to paying or bribing someone to acquire a test or assignment, changing someone's grades or academic records, taking a test/doing an assignment for someone else by any means, including misuse of an electronic device. It is a violation of Oregon state law to create and offer to sell part or all of an educational assignment to another person (ORS 165.114).

    4. TAMPERING - altering or interfering with evaluation instruments or documents.

    5. PLAGIARISM - representing the words or ideas of another person or presenting someone else's words, ideas, artistry or data as one's own, or using one's own previously submitted work. Plagiarism includes but is not limited to copying another person's work (including unpublished material) without appropriate referencing, presenting someone else's opinions and theories as one's own, or working jointly on a project and then submitting it as one's own.

  3. Academic Dishonesty cases are handled initially by the academic units, following the process outlined in the University's Academic Dishonesty Report Form, and will also be referred to SCCS for action under these rules.


Tutoring and Writing Assistance

NetTutor is a leading provider of online tutoring and learner support services fully staffed by experienced, trained and monitored tutors. Students connect to live tutors from any computer that has Internet access. NetTutor provides a virtual whiteboard that allows tutors and students to work on problems in a real time environment. They also have an online writing suite where tutors critique and return essays within 24 to 48 hours. Access NetTutor from within your Canvas class by clicking on the Tools button in your course menu.

The Oregon State Online Writing Suite is also available for students enrolled in Ecampus courses.


TurnItIn

Your instructor may ask you to submit one or more of your writings to Turnitin, a plagiarism prevention service. Your assignment content will be checked for potential plagiarism against Internet sources, academic journal articles, and the papers of other OSU students, for common or borrowed content. Turnitin generates a report that highlights any potentially unoriginal text in your paper. The report may be submitted directly to your instructor or your instructor may elect to have you submit initial drafts through Turnitin, and you will receive the report allowing you the opportunity to make adjustments and ensure that all source material has been properly cited. Papers you submit through Turnitin for this or any class will be added to the OSU Turnitin database and may be checked against other OSU paper submissions. You will retain all rights to your written work. For further information, visit Academic Integrity for Students: Turnitin – What is it?


Student Evaluation of Courses

The online Student Evaluation of Teaching system opens to students during the week before finals and closes the Monday following the end of finals. Students receive notification, instructions and the link through their ONID. They may also log into the system via Online Services. Course evaluation results are extremely important and used to help improve courses and the online learning experience for future students. Responses are anonymous (unless a student chooses to “sign” their comments, agreeing to relinquish anonymity) and unavailable to instructors until after grades have been posted. The results of scaled questions and signed comments go to both the instructor and their unit head/supervisor.  Anonymous (unsigned) comments go to the instructor only.

Course Outline By Week

Week 1
  1. Read the Syllabus and complete the Syllabus Quiz.
  2. Familiarize yourself with the available projects on the EECS Project Portal.
  3. Email the instructor with your own project idea or project preferences. (Optional)
  4. Complete the Choose Your Project assignment.
Week 2
  1. Go to your group's discussion board and make a post in the Our Team Introductions topic.
  2. Draft your Team Standards.
  3. Work with your group to Create a Project Plan.
Week 3
Begin working on your project, once your project plan is approved.
Week 4
Submit your week 4 progress report (2-5 minute show-and-tell).
Week 5
Submit your week 5 progress report (2-5 minute show-and-tell).
Week 6
Submit your team's midpoint project report.
Week 7
Submit your week 7 progress report (2-5 minute show-and-tell).
Week 8
Submit your week 8 progress report (2-5 minute show-and-tell).
Week 9
Submit your week 9 progress report (2-5 minute show-and-tell).
Week 10
Week 11
Nothing — Congratulations, you're done!

Please post all course-related questions in the Q&A Discussion Forum so that the whole class may benefit from our conversation. Please contact me privately for matters of a personal nature. I will reply to course-related questions within 24 hours. I will strive to return your assignments and grades for course activities to you within five days of the due date.

For questions about grading, contact the person responsible for grading that assignment.

To contact me directly, please email me at pfeilw@oregonstate.edu. I strongly suggest tagging your email with "[CS 467]" in the subject line. If you do not receive a response within one business day, feel free to send a follow-up email. Sometimes we miss things!

We are not Debuggers, Programmers, or Architects — that's your job! Do not send the instructor or TAs any code except what is required for your assignment submissions.

Don't expect the instructor or the TAs to see comments left with assignment submissions. Canvas allows us to download the entire class's submissions as one .zip file, which does not include these comments. If you need to make a meta-comment about your submission, add it to the submission or email the person grading that submission.

This page describes where to find the available Software Projects and how to choose your project.

Please note the following: 

  • There are no solo projects with RARE exceptions. Occasionally we may approve cross-disciplinary projects with a single Capstone student and students from other colleges. Occasionally we may approve individual research projects with a lot of lead time and strong references from other OSU faculty.
  • You may propose your own project. Just send an email to the instructor, and if your project is approved, we will put it up in the project portal if need be.
  • You may form your own team and choose your own project IF you propose a project of your own and it is accepted or IF you choose a project that your instructor is sponsoring. The choose your project survey will make this clear.

Choosing a project

  1. Here is the link to the OSU EECS Capstone Project Portal. Visit anytime to see available projects.
  2. You will want to read and understand the steps outlined in the Choose Your Project assignment.

Propose Your Own Project

Do you have an idea for a project that you'd really like to execute? If so, send an email to the instructor(s) asap. We will help you fine-tune your idea and post the project to the Portal. Note that there may not be time to add your project, so get your ideas in as early as possible.

If you choose to work on your own idea, you may not re-use extensive amounts of code from previous projects and get credit for them as part of this course: your programming and design efforts must be new. However, if you have an existing project that you want to put 300 more hours into, you can use that project as a starting point for your team.

Evaluation Environment

In general, your instructor(s) and TAs will not have time to re-create your development environment in order to test. You should plan ahead to submit the following:

  • Web Project - Link to hosted website
  • iOS - Use TestFlight (preferred) or Ad-hoc deployment
  • Android - Submit an apk
  • School Computers (Cent OS or Windows) - Ok to submit c or c++ code and compilation instructions IF no dependencies to install. Python and Java are fine also.
  • Unity projects - Prefer WebGL hosted on website (Can host on Amazon S3 static website). Otherwise, contact the instructor(s). We may be able to load your project in our Unity environment, or may require a demonstration video.

Project Selection Considerations

Since this final project you create will be amazing, please consider using it as part of your portfolio to help get jobs. To this end, consider selecting a project that might appeal to your potential employers.

Welcome to CS 467 Capstone! This course is very different from previous courses in the program. This is where you get to decide what you want to do with your term, with very little input or guidance from the instructor. Some students choose to do a pure coding project where they have an idea and run with it -- others choose to dive into hours of research on a new topic they have no experience with, trading final polish for novelty. It's up to you what you want to do. Many students have told me this was the most fun course they have taken in the program.

In past terms, more than 99% of the class finishes with an A. Failing grades are rare, but can happen. In an effort to avoid this, here are a few very important things we all need to keep in mind as we go through this term:

The best way to be successful in this course is to start working with your team early on to develop a realistic plan for your project. This will lay the foundation for the rest of the term, so put serious thought into what you are committing to! Don't worry too much though -- one goal of the course is for you to practice planning a project and estimating time and research requirements -- if you over-commit I'm not going to force you to suffer, but you will have to revise your project plan half way through the term which is not very fun. Have real milestones and keep track of them. The sooner you realize you're going off track, the earlier we can work together to fix it.

For research heavy projects, there must be a final deliverable that represents a significant level of mastery of computer science. When grading final projects, the TAs and I take into account the difficulty and novelty of the project when evaluating the deliverables. However, there must still be actual deliverables. Telling me you have done a lot of research, but have nothing to show for it is not a way to pass the class.

You absolutely must keep in regular contact with your team. I know that many of you have jobs and lives outside of this program, and we try to be as flexible as possible. However, this isn't a weekend-only class. You need to communicate with your team and agree on a schedule for regular meetings and progress updates. Having a busy work/school/personal life is not an excuse for disappearing on your group. If your group has gone more than a week without hearing from you, you will be removed from your group. Even excused absences can result in removal from your group if they significantly impact the group's ability to finish the project.

You are responsible for notifying me about absent/under-performing group members. Even though I can see if a student has stopped submitting progress updates or is not showing appropriate progress, I cannot contact the other members of the group to investigate because of academic records privacy regulations. If you have not heard from a group member in more than a week, it is your responsibility to contact me. Waiting until a few days before the final project is due is not an appropriate time to send me an email about how you're the only one that has contributed anything to the project all term.

At the midpoint project check, dysfunctional groups may be broken up and students will be assigned individual projects to complete. These projects are often more difficult than working together as a group, and there is less time to complete them. In general, students that start individual projects have tended to not pass the class. Where possible, if only one group member is not contributing, I will try to preserve the group for the remaining students, adjusting the project requirements as necessary. If a student is removed from a group after the midpoint project check has passed, they may not be given the option for a solo project, and will need to retake the course.

On your weekly progress reports, scrolling quickly up and down and clicking through different source file tabs in your IDE while talking vaguely about your "progress" is a fantastic way to earn a 0 for that week. If there is code on your screen and you say anything to the effect of "this is my code", "I did this", or "this is my work for the week", and that code is something that I find out came from some other source like a book, or another person's GitHub, or one of your group members, you will not only receive 0 points, but I will file a plagiarism case with the college. Several grades of 0 points for weekly progress reports can result in removal from your group.

In any circumstance, I will do everything I can to make sure that students are not unfairly punished for the actions of their group member(s). Because many students plan to use the final deliverable in their professional portfolios, I take non-participation and under-performance very seriously. Please keep in mind the effects that your choices can have on the other people in your group who have all invested a significant amount of time and money into this program and want to have the best final product to show for it that they can.

Course Summary:

Date Details