Capstone, Dickinson, Braught

From Foss2Serve
(Difference between revisions)
Jump to: navigation, search
 
(25 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== 0. Overview ==
+
{{Category:Courses}}
  
{| border="1"
+
=== Overview ===
|-
+
! style="text-align:right;"| Course Name
+
| Computer Science Senior Seminar (COMP491/492)
+
|-
+
! style="text-align:right;"| Course Overview
+
| A two-semester required senior capstone including perspective on and experience with H/FOSS projects. In the first semester students will complete readings, exercises and activities that familiarize them with H/F/OSS philosophy/community/tools, select a project in which to participate and produce a plan for their second semester.  During the second semester students will work on their selected H/F/OSS project according to their plans while also completing readings on contemporary and ethical issues in computing.
+
|-
+
! style="text-align:right;"| Instructor Contact Info
+
| Grant Braught, Dickinson College
+
|-
+
! style="text-align:right;"| Student Characteristics
+
| Typically offered to 10-15 senior computer science majors per year.
+
|-
+
! style="text-align:right;"| Prerequisites
+
| This course was designed for use in the final year of a Computer Science major at a small liberal arts college. Students having completed the first three years of an undergraduate CS curriculum should be well prepared for this course.  Our students typically have completed the core courses and are competent in: Object Oriented Programming (2 courses in Java), Data Structures (in Java), Analysis of Algorithms, Programming Languages (including C/C++, Python, Scheme, Prolog), Organization and Architecture.  They may also have completed additional electives (e.g. Operating Systems, Networking, AI, Databases) and other core courses (e.g. Theory of Computation).
+
|-
+
! style="text-align:right;"| Infrastructure
+
| The course outlined below assumes 14 2-hour course meetings (1 per week) per semester, plus a 3-hour final exam period.  Students are expected to average between 8 and 12 hours of work outside of class per week.
+
  
Many of the activities and assignments rely on the use of particular technologies. These can be substituted with equivalent technologies but are currently:
+
{{Course Overview
 +
|course=
 +
Computer Science Senior Seminar
 +
|institution=
 +
Dickinson College
 +
|instructors=
 +
Grant Braught, Dickinson College
 +
|offerings=
 +
First offered as COMP491/492 in Academic Year 2016-17 at Dickinson College.  Revised for the 2017-18, and 2018-19 Academic Years.
 +
|overview=
 +
A two-semester required senior capstone including perspective on and experience with H/FOSS projects. In the first semester students complete readings, exercises and activities that familiarize them with H/F/OSS philosophy/community/tools. They complete exercises to help them select an H/FOSS project in which to participate and form teams. They then begin a series of exercises that include: Installing the project as a user; Installing the project as a developer; Rebuilding the project from source; Running the test suite; Verifying bugs from the issue tracker (Bug Gardening); and Fixing bugs. During the second semester students continue work on their selected H/F/OSS project fixing bugs and proposing additional contributions to the project that have value both to them and their H/FOSS community.  Students also complete readings on contemporary and ethical issues in computing and participate in class discussions on these topics.
 +
|courselength=
 +
Two 14-week semesters.
 +
|students=
 +
Typically offered to 10-20 senior computer science majors per year.
 +
|prerequisites=
 +
This course was designed for use in the final year of a Computer Science major at a small liberal arts college. Students having completed the first three years of an undergraduate CS curriculum should be well prepared for this course.  Our students typically have completed the core courses and are competent in: Object Oriented Programming (2 courses in Java), Data Structures (in Java), Analysis of Algorithms, Programming Languages (including C/C++, Python, Scheme, Prolog), Organization and Architecture.  They may also have completed additional electives (e.g. Operating Systems, Networking, AI, Databases) and other core courses (e.g. Theory of Computation).
 +
|infrastructure=
 +
The course outlined below assumes 28 75-minute course meetings (2 per week) per semester, plus a 3-hour final exam period.  Students are expected to average between 8 and 12 hours of work outside of class per week.
 +
 
 +
Many of the activities and assignments rely on the use of particular technologies.
 +
These can be substituted with equivalent technologies but are currently:
 
* Virtual Box
 
* Virtual Box
 
* Ubuntu 16.04
 
* Ubuntu 16.04
 
* Slack
 
* Slack
 
* Moodle (Wiki/Forums)
 
* Moodle (Wiki/Forums)
|-
+
}}
! style="text-align:right;"| Offerings
+
| To be offered AY 2016-17 at Dickinson College
+
|-
+
|}
+
  
== 1. Learning Objectives ==
+
=== Complete Course Materials and User Guide ===
*Students will:
+
:1. Recognize the ethical, legal and social implications of computing.
+
:2. Be exposed to H/F/OSS and Software Engineering topics.
+
:3. Improve their ability to work (reading/modifying/testing) within a substantial existing code base.
+
:4. Interact with a community of developers and users.
+
:5. Deepen their ability to write clearly and develop their mastery of specific forms of disciplinary writing.
+
:6. Be prepared for graduate study or a professional career in computing.
+
  
== 2. Methods of Assessment ==
+
Complete details of this course including all materials, a guide to use and adaptation of the materials, analysis of student survey data and a discussion of ongoing improvements can be found in the following GitHub Repository:
  
The following assessment mechanisms will be used:
+
[https://github.com/braughtg/DickinsonHFOSS-SFC-Materials COMP491/492 at Dickinson College]
 
+
*Forum Postings: Students will post (in Moodle) discussion questions based on reading assignments to guide the subsequent in-class discussion. [LO: 1,2,6]
+
*Wiki Reflections: Students will complete reflective writings on a wiki (in Moodle):
+
**Following each discussion; clarifying and/or expanding their understanding of the material. [LO: 1,2,5,6]
+
**Each week of project work; summarizing actions, accomplishments, existing challenges and proposing work for the following week. [LO: 3,4,5,6]
+
*Live-Texting: Students will live-text (using Slack) while working on the projects as documentation of their efforts. [LO: 3,4]
+
*Standup Meetings: During project work, each class meeting will begin with each group giving 1-2 minute summary of their work from the prior week and highlighting current challenges. [LO: 5,6]
+
*Homework: Early course meetings (during project selection) specific homework assignments are given, each with its own deliverable. [LO: 2,3,4]
+
*Project Checkpoint Presentations: Project teams will schedule presentations for each of the project check points.  These will be 10 minute, in-class presentations with content dependent upon the specific check point. [LO: 2,3,4,5,6]
+
 
+
== 3. Course Outline ==
+
*[http://users.dickinson.edu/~braught/courses/cs491f16/cs491f16.html COMP491 at Dickinson College Fall 2016]
+
 
+
== 4. Notes to Instructor ==
+
*''Will fill in as first course offering progresses''
+
 
+
== 5. Moving Forward ==
+
*''Will fill in as first course offering progresses''
+
  
 
--------------------
 
--------------------
This work is licensed under a  
+
<!-- this license is for the FORMAT - remove it for a new activity, and add the license for the activity -->
[http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]
+
For this blank '''format''': {{License CC BY SA}}.
 
+
[[File:CC_license.png]]
+
 
+
Materials linked to by this page may be governed by other licenses.
+
  
[[Category: Course]]
+
[[Category:Courses]]
[[Category: WorkInProgress]]
+
<!-- add appropriate subcategory(s) for a new course - e.g. CS1, CS2, Capstone -->
 +
[[Category:Capstone]]

Latest revision as of 13:56, 18 October 2019

A Course is an actual academic course that involves HFOSS, typically by using Pathways and Learning Activities.

Overview

Course Computer Science Senior Seminar
Institution Dickinson College
Instructor(s) Grant Braught, Dickinson College
Term First offered as COMP491/492 in Academic Year 2016-17 at Dickinson College. Revised for the 2017-18, and 2018-19 Academic Years.
Course Overview A two-semester required senior capstone including perspective on and experience with H/FOSS projects. In the first semester students complete readings, exercises and activities that familiarize them with H/F/OSS philosophy/community/tools. They complete exercises to help them select an H/FOSS project in which to participate and form teams. They then begin a series of exercises that include: Installing the project as a user; Installing the project as a developer; Rebuilding the project from source; Running the test suite; Verifying bugs from the issue tracker (Bug Gardening); and Fixing bugs. During the second semester students continue work on their selected H/F/OSS project fixing bugs and proposing additional contributions to the project that have value both to them and their H/FOSS community. Students also complete readings on contemporary and ethical issues in computing and participate in class discussions on these topics.
Course Length Two 14-week semesters.
Student Characteristics Typically offered to 10-20 senior computer science majors per year.
Prerequisites This course was designed for use in the final year of a Computer Science major at a small liberal arts college. Students having completed the first three years of an undergraduate CS curriculum should be well prepared for this course. Our students typically have completed the core courses and are competent in: Object Oriented Programming (2 courses in Java), Data Structures (in Java), Analysis of Algorithms, Programming Languages (including C/C++, Python, Scheme, Prolog), Organization and Architecture. They may also have completed additional electives (e.g. Operating Systems, Networking, AI, Databases) and other core courses (e.g. Theory of Computation).
Infrastructure The course outlined below assumes 28 75-minute course meetings (2 per week) per semester, plus a 3-hour final exam period. Students are expected to average between 8 and 12 hours of work outside of class per week.

Many of the activities and assignments rely on the use of particular technologies. These can be substituted with equivalent technologies but are currently:

  • Virtual Box
  • Ubuntu 16.04
  • Slack
  • Moodle (Wiki/Forums)


Complete Course Materials and User Guide

Complete details of this course including all materials, a guide to use and adaptation of the materials, analysis of student survey data and a discussion of ongoing improvements can be found in the following GitHub Repository:

COMP491/492 at Dickinson College


For this blank format: This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License

CC license.png .

Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox