Capstone, Dickinson, Braught
| Line 40: | Line 40: | ||
!'''Readings for this Class''' | !'''Readings for this Class''' | ||
!'''In-Class Activities''' | !'''In-Class Activities''' | ||
| − | !'''Homework | + | !'''Homework''' |
|- | |- | ||
| 1 | | 1 | ||
| Line 72: | Line 72: | ||
*Extended Git/GitHub Activity ''(CHRIS?)'' | *Extended Git/GitHub Activity ''(CHRIS?)'' | ||
*Project Selection pt. 3 | *Project Selection pt. 3 | ||
| + | |- | ||
| + | |} | ||
| + | |||
| + | Topics: | ||
| + | |||
| + | Bug Reporting | ||
| + | Software Testing | ||
| + | Software Reviews | ||
| + | Software Processes | ||
| + | Software Architectures | ||
| + | Patterns 1 | ||
| + | Patterns 2 | ||
| + | FOSS Business Models | ||
| + | FOSS Success Stories | ||
| + | FOSS Criticisms | ||
| + | |||
| + | |||
| + | | 4 | ||
| + | |'''Bug Reporting''' | ||
| + | | | ||
| + | |||
|- | |- | ||
| 4 | | 4 | ||
| Line 98: | Line 119: | ||
|- | |- | ||
| 10 | | 10 | ||
| − | | | + | | Bug Reporting |
|- | |- | ||
| 11 | | 11 | ||
| − | | | + | | FOSS Success Stories |
|- | |- | ||
| 12 | | 12 | ||
| − | | | + | | |
|- | |- | ||
| 13 | | 13 | ||
Revision as of 12:24, 16 August 2016
NOTE: THIS IS CURRENTLY A WORK IN PROGRESS!!
NOTE: COURSE WILL BE OFFERED AY16-17. THE MATERIALS HERE WILL BE REFINED THROUGHOUT THAT PERIOD.
| Title | Syllabus for 2-Semester Senior Capstone Course |
| Overview | Students will gain 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 according to their plans while also completing readings on contemporary and ethical issues in computing. |
| Prerequisite Knowledge | 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 (Java), Data Structures (Java), Analysis of Algorithms, Programming Languages (C/C++, Scheme, Prolog), Organization and Architecture. They may also have completed electives (Operating Systems, Networking, AI, Databases). |
| Learning Objectives |
|
Background:
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:
- Virtual Box
- Ubuntu 16.04
- Slack
- Moodle (Wiki/Forums)
Directions:
| Meeting | Topic | Summary | Readings for this Class | In-Class Activities | Homework |
|---|---|---|---|---|---|
| 1 | Course Introduction | Overview of course goals, expectation and structure and pre-survey. Introduction to Wiki, Slack and Virutal Box. Students begin the process of project selection. | None |
|
|
| 2 | H/F/OSS Philosophy & Structure | Discussion of the history and philosophy of open source software. Identification of the major OSS project components. Collaborative development of ranking rubric for project selection pt. 2 homework. | TBA |
|
|
| 3 | H/F/OSS Licensing & Tools | Discussion of licensing issues in open source. Introduction to Git/GitHub/GitFlow. | TBA |
|
|
Topics:
Bug Reporting Software Testing Software Reviews Software Processes Software Architectures Patterns 1 Patterns 2 FOSS Business Models FOSS Success Stories FOSS Criticisms
| 4
|Bug Reporting
|
|- | 4 |Software Process | Discussion of software development processes (waterfall / agile / etc). Student groups give short presentation on the projects that they have selected. | TBA |
- Project presentations
|
- Build/Instal/Demo Checkpoint
|- | 5 | Software Architectures |- | 6 | Software Patterns 1 |- | 7 | Software Patterns 2 |- | 8 | Software Flaws |- | 9 | Software Testing |- | 10 | Bug Reporting |- | 11 | FOSS Success Stories |- | 12 | |- | 13 | |- | 14 | |}
Deliverables:
Each week students will complete some or all of the following:
- Post to course forum discussion questions based on the reading that will form the basis for the in-class discussion.
- Add to wiki a reflective writing following on from readings and course discussion.
- Add to wiki a reflective writing discussing project accomplishments, challenges and planning tasks for the following week.
- Have live-texted their project work using Slack.
Early course meetings will have homework assignments with specific deliverables.
Project checkpoints will have specific deliverables.
Assessment:
Each homework assignment and project checkpoint will provide a specific rubric for its assessment.
Comments:
What should the instructor know before using this activity?
What are some likely difficulties that an instructor may encounter using this activity?
Additional Information:
| ACM Knowledge Area/Knowledge Unit | What ACM Computing Curricula 2013 knowledge area and units does this activity cover? ACM_Body_of_Knowledge |
| ACM Topic | What specific topics are addressed? The Computing Curriucula 2013 provides a list of topics - https://www.acm.org/education/CS2013-final-report.pdf |
| Level of Difficulty | Challenging |
| Estimated Time to Completion | 2 Semesters |
| Materials/Environment | GitHub Account / Slack Account / Machine running Virtual Box |
| Author(s) | Grant Braught |
| Source | Many... all linked above. |
| License | Creative Commons Attribution-ShareAlike 4.0 International License |
Feedback:
Feedback to the author(s) of the activity regarding usage or suggestions for enhancements can be included via the discussion tab.
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License
