Contact Information
My office hours, phone number and e-mail address are available on my home page.
Course Description
The Senior Seminar (COMP491/492 combined) has three main components:
Course Schedule
Assignment details including due dates and topics are indicated on the Course Home Page.
Textbook
Reading materials for COMP491/492 will be provided via links on the course schedule or via Moodle.
Learning Goals
Students will:
491 Grade Determination
Preparation/Attendance/Engagement (PAE) (3) | 15% |
Blog / Reflective Writing (3) | 20% |
HW Exercises (5) | 10% |
Project/Community Selection or Research Proposal | 10% |
Project Checkpoint #1 | 15% |
Project Checkpoint #2 | 30% |
492 Grade Determination
Preparation/Attendance/Engagement (PAE) (3) | 15% |
Leading a Discussion | 10% |
Blog / Reflective Writing (2) | 15% |
Code Review | 05% |
Poster | 15% |
Project Checkpoint #1 | 15% |
Project Checkpoint #2 | 25% |
Course Components
PAE is assessed for each individual during each class period. Preparation includes completion of any reading, tutorials, exercises or activities assigned in the "Reading & Preparation" row of the "Class Detail". Attendance is your presence in class during our scheduled meetings. Engagement combines participation in discussion and activities with with a demonstrated investment both in the material and the betterment of the class for everyone.
PAE scores will be assigned according to the rubric below. The standard score in each category, and what you should generally expect to receive, is a ✓. Something exceptionally notable is required to move either up to a ✓+ or down to 0 or ✓-.
If you find PAE challenging, some good advice on increasing or improving class participation can be found at:
Posts will typically be 200-400 words. You are given wide latitude for the content of your posts. The best posts will:
I will assess blog posts at random during the semester. When you are selected to have your blog assessed, I will review all of your blog posts since the prior assessment using the rubric below. The standard score, and what you should generally expect to receive, is a ✓. Something exceptionally notable is required to move either up to a ✓+ or down to 0 or ✓-.
If you find writing blog posts challenging, some good advice on writing effective blog entries can be found at:
Tutorials and homework exercises will be assessed largely on completion and effort as documented by the associated Slack live-logs according to the rubric below. The standard score, and what you should generally expect to receive, is a ✓. Something exceptionally notable is required to move either up to a ✓+ or down to 0 or ✓-.
Additional assignment details will be posted on the course schedule.
Project Checkpoints will be scored using the rubric below. The standard score, and what you should generally expect to receive, is a ✓. Something exceptionally notable is required to move either up to a ✓+ or down to 0 or ✓-.
Time & Effort Documentation Tools
A Slack Live-Log is just a series of messages posted to a Slack channel as you work. The messages should paint a rough picture of what you are doing, when you did it and any other interesting/useful tidbits to be remembered while you are working. Ideally, when working in a pair, one partner will be controlling the machine where the project work is happening and the other will be live-logging on another machine. These roles should be swapped regularly. It is not necessary to document every tiny thing, and you don't have to use polished language, grammar and punctuation. You can see a sample live-log in the sample-live-log channel in the COMP491 Slack team.
For homework assignments the Slack Live-Log will be used to demonstrate that you have worked through the appropriate exercises, tutorials and assignments.
For FOSS Project work the Slack Live-Log will be used to demonstrate an appropriate investment of time and quality effort in the project work, as well as to document your progress through the project guides. Each of you has different experience and every FOSS project has different technical challenges. Thus, some tasks will be easier (or harder) than others and what is accomplished will vary between teams, from week-to-week and between projects. Thus, rather than relying solely on final products for credit teams will be expected to invest an appropriate amount of time and effort on their project work each week. Slack Live-Logs provide the mechanism for documenting the time and effort invested in the project.
In addition to keeping a record of what a team has done and how long it has worked, these live-logs are intended to encourage teams to practice and demonstrate that they are working via steady, sustained engagement rather than in long irregular bursts. Working via steady, sustained engagement is more effective, more productive and less frustrating than working in long irregular bursts. It allows time to process information, generate new ideas, communicate with faculty, peers and the project's development community.
A five-fifteen report is a short weekly templated report that is designed to enhance communication, reflection, prioritization, goal setting and time management without being time consuming. The name five-fifteen reflects that the report should take no more than five minutes to read and no more than fifteen minutes to write.
We will use three types of 5-15 reports to reflect on your accomplishments, your self and your team, and to identify and plan future work. H/FOSS project students will complete Individual 5-15s and Team 5-15s. Honor's student's will complete a 5-15 tailored for individual research projects.
All 5-15's will be maintained as a Wiki page with the most recent entry at the top. Individual 5-15's will be linked with your personal information on the course Wiki (i.e. on the page with your blog and git links). Team and Honor's 5-15's will be linked from the project Wiki page.
Academic Integrity
Please take the time to read the Academic Misconduct section of Dickinson's Community Standards. Violations of this policy are considered serious transgressions, so you should be especially certain that you understand your rights and responsibilities under it. Students suspected of academic dishonesty will be subject to the process outlined in the Student Conduct pages. The specific collaboration policies for each component of this course are detailed in the assignments. If you are unsure about whether or not certain kinds of collaboration are permissible on an assignment or in this course, ask your instructor.
Intellectual Property Rights
Audio or video recording of class meetings, lectures or discussions is prohibited without explicit permission of the instructor. Photographic records of whiteboards, projected slides or other visual media is also prohibited without explicit permission of the instructor. In any case where permission is given for audio/video/photographic records to be made they are for personal use only. They may not be shared or redistributed and must be destroyed at the end of their usefulness or within one week following the termination of this course, whichever comes first. Similarly, any redistribution of sample code, homework solution sets or provided lab code is prohibited. Please note that all outside materials used in the course (readings/tutorials/assignments/projects/etc) are also be governed by their own licensing agreements.
Accommodations for Disabilities
Dickinson values diverse types of learners and is committed to ensuring that each student is afforded an equal opportunity to participate in all learning experiences. If you have (or think you may have) a learning difference or a disability - including a mental health, medical, or physical impairment - that would impact your educational experience in this class, please contact the Office of Disability Services (ODS) to schedule a meeting with Director Marni Jones. She will confidentially discuss your needs, review your documentation, and determine your eligibility for reasonable accommodations. To learn more about available supports, go to www.dickinson.edu/ODS, email DisabilityServices@dickinson.edu, call (717) 245-1734, or go to ODS in 106 Dana Hall.
If you've already been granted accommodations at Dickinson, please let me know as soon as possible so that we can meet to review your Accommodation Letter and complete your Access Plan. If you will need test proctoring from ODS, remember that you will need to provide them with at least one week's notice.