Independent Capstone Project Design
m |
|||
| (15 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
| − | {| | + | {{Course Overview |
| − | + | |course= | |
| − | + | Independent Capstone Project | |
| − | | | + | |institution= |
| − | | | + | |instructors= |
| − | + | |offerings= | |
| − | + | |overview= | |
| − | + | The student will create a detailed plan for an independent capstone project in an HFOSS community. | |
| − | + | This will demonstrate the totality of skills required by a CS graduate. | |
| − | |} | + | |students= |
| + | |prerequisites= | ||
| + | Basic knowledge of software development skills | ||
| + | |infrastructure= | ||
| + | }} | ||
=== Background === | === Background === | ||
| − | At many institutions, students often enroll in a "capstone" course which requires a completion of a "big" project: a project that requires months rather than weeks to perform. | + | At many institutions, students often enroll in a "capstone" course which requires a completion of a "big" project: a project that requires months rather than weeks to perform. Often this project involves teams of students rather than individuals, but might be performed as individuals. Often, the project is chosen arbitrarily by the instructor, and results in an artificial academic artifact at the end of the project. |
| − | Students and/or faculty who desire a project with a greater practical impact might be interested in joining an HFOSS community and choosing a project that would ultimately be submitted to that community. | + | Students and/or faculty who desire a project with a greater practical impact might be interested in joining an HFOSS community and choosing a project that would ultimately be submitted to that community. This activities outlines a potential path to planning such a project. |
| − | The project could be appropriate for individuals or teams; it could be appropriate for upper-division or lower-division students; it could be appropriate for projects of various time lengths. | + | The project could be appropriate for individuals or teams; it could be appropriate for upper-division or lower-division students; it could be appropriate for projects of various time lengths. The plan gives room for individual faculty to customize to meet their needs. |
=== Directions === | === Directions === | ||
| Line 24: | Line 28: | ||
==== Step One: Learn about HFOSS ==== | ==== Step One: Learn about HFOSS ==== | ||
| − | Complete the following | + | Complete the following foss2serve learning activities: |
| − | # [[Intro to FOSS Activity]] | + | # [[Intro to FOSS (Activity)]] |
| − | # [[Project Anatomy Activity]] | + | # [[Intro to FOSS Project Anatomy (Activity)]] |
| − | # [[FOSS Field Trip Activity]] | + | # [[FOSS Field Trip (Activity)]] |
| − | # [[Project | + | # [[Evaluate a Project (Activity)]] |
# As needed, activities to learn about contemporary tools commonly used in FOSS communities: | # As needed, activities to learn about contemporary tools commonly used in FOSS communities: | ||
| − | ## | + | ## [[Intro to Wiki (Activity)]] |
| − | ## | + | ## [[Intro to IRC (Activity)]] |
| − | ## | + | ## [[Blog Activity]] |
| − | ## | + | ## [[Intro to Bug Trackers (Activity)]] |
| − | ## | + | ## [[Intro to GitHub (Activity)]] |
At the conclusion of Step One, the student will meet with the academic advisor to discuss the material covered and answer any questions. | At the conclusion of Step One, the student will meet with the academic advisor to discuss the material covered and answer any questions. | ||
| Line 43: | Line 47: | ||
The student should investigate and a select an HFOSS community in which this capstone project will be performed. | The student should investigate and a select an HFOSS community in which this capstone project will be performed. | ||
| − | After selection, the student should complete | + | After selection, the student should complete [[Evaluate a Project (Activity)]], in order to ensure that the HFOSS project is mature enough to support the capstone project. |
| − | Upon completion of the [[Project | + | Upon completion of the [[Evaluate a Project (Activity)]], the student will meet with the academic advisor to discuss the results and ensure that the selected community is mature enough to support the capstone project. |
| Line 52: | Line 56: | ||
First, the student should complete the following activities in order to identify possible concrete tasks and/or deliverables that could be used within the selected HFOSS community: | First, the student should complete the following activities in order to identify possible concrete tasks and/or deliverables that could be used within the selected HFOSS community: | ||
| − | # [[FOSS | + | # [[FOSS in Courses 1 (Instructors)]] |
| − | # [[FOSS in Courses 2]] | + | # [[FOSS in Courses 2 (Instructors)]] |
Finally, in consultation with the academic advisor, the student should prepare the '''Final Capstone Project Design Document'''. The format for this will depend upon the particular institution, but may include many of the following items: | Finally, in consultation with the academic advisor, the student should prepare the '''Final Capstone Project Design Document'''. The format for this will depend upon the particular institution, but may include many of the following items: | ||
| Line 82: | Line 86: | ||
=== Additional Information: === | === Additional Information: === | ||
| − | {| | + | |
| − | + | {{Learning Activity Info | |
| − | + | |acm unit= | |
| − | | | + | various |
| − | + | |acm topic= | |
| − | | | + | various |
| − | + | |difficulty= | |
| − | | | + | medium to challenging, depending upon the project selected |
| − | + | |time= | |
| − | | | + | several weeks |
| − | + | |environment= | |
| − | | | + | Internet access, possibly access to various common FOSS tools (outlined below) |
| − | + | |author= | |
| − | | | + | Jim Huggins (jhuggins@kettering.edu) |
| − | + | |source= | |
| − | | | + | Based on the September 2015 POSSE workshop [[POSSE 2015-09]] |
| − | + | |license= | |
| − | + | {{License CC BY SA}} | |
| + | }} | ||
=== Suggestions for Open Source Community: === | === Suggestions for Open Source Community: === | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[[Category:Learning Activity]] | [[Category:Learning Activity]] | ||
[[Category:Specification and Design]] | [[Category:Specification and Design]] | ||
[[Category:Capstone]] | [[Category:Capstone]] | ||
| + | [[Category:Good Draft]] | ||
Latest revision as of 13:21, 8 September 2018
| Course | Independent Capstone Project |
|---|---|
| Institution | |
| Instructor(s) | |
| Term | |
| Course Overview | The student will create a detailed plan for an independent capstone project in an HFOSS community.
This will demonstrate the totality of skills required by a CS graduate. |
| Course Length | {{{courselength}}} |
| Student Characteristics | |
| Prerequisites | Basic knowledge of software development skills |
| Infrastructure |
Background
At many institutions, students often enroll in a "capstone" course which requires a completion of a "big" project: a project that requires months rather than weeks to perform. Often this project involves teams of students rather than individuals, but might be performed as individuals. Often, the project is chosen arbitrarily by the instructor, and results in an artificial academic artifact at the end of the project.
Students and/or faculty who desire a project with a greater practical impact might be interested in joining an HFOSS community and choosing a project that would ultimately be submitted to that community. This activities outlines a potential path to planning such a project.
The project could be appropriate for individuals or teams; it could be appropriate for upper-division or lower-division students; it could be appropriate for projects of various time lengths. The plan gives room for individual faculty to customize to meet their needs.
Directions
Step One: Learn about HFOSS
Complete the following foss2serve learning activities:
- Intro to FOSS (Activity)
- Intro to FOSS Project Anatomy (Activity)
- FOSS Field Trip (Activity)
- Evaluate a Project (Activity)
- As needed, activities to learn about contemporary tools commonly used in FOSS communities:
At the conclusion of Step One, the student will meet with the academic advisor to discuss the material covered and answer any questions.
Step Two: Select and Investigate an HFOSS Community
The student should investigate and a select an HFOSS community in which this capstone project will be performed.
After selection, the student should complete Evaluate a Project (Activity), in order to ensure that the HFOSS project is mature enough to support the capstone project.
Upon completion of the Evaluate a Project (Activity), the student will meet with the academic advisor to discuss the results and ensure that the selected community is mature enough to support the capstone project.
Step Three: Prepare The Capstone Plan
First, the student should complete the following activities in order to identify possible concrete tasks and/or deliverables that could be used within the selected HFOSS community:
Finally, in consultation with the academic advisor, the student should prepare the Final Capstone Project Design Document. The format for this will depend upon the particular institution, but may include many of the following items:
- Project title
- Faculty members involved in final review of the project
- Description of the work to be performed, including:
- Value of the project to the HFOSS community
- Relationship of the project to institutional capstone goals
- Expected deliverables
- Project timeline
- Relationship to the overall HFOSS project, including dependencies (if any)
- Prerequisite skills needed
- Literature review (if needed)
- Facilities and/or equipment required
Deliverables
The only deliverable is the Final Capstone Project Design Document, outlined in Step Three above.
Assessment
The project is successful if the student's department accepts the project proposal and allows the student to begin work on the capstone project.
Comments
Additional Information:
| ACM BoK Area & Unit(s) |
various |
|---|---|
| ACM BoK Topic(s) |
various |
| Difficulty |
medium to challenging, depending upon the project selected |
| Estimated Time to Complete |
several weeks |
| Environment / Materials |
Internet access, possibly access to various common FOSS tools (outlined below) |
| Author(s) |
Jim Huggins (jhuggins@kettering.edu) |
| Source |
Based on the September 2015 POSSE workshop POSSE 2015-09 |
| License |
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License
|
