Rea, Yeates (Proposal)
(→Contact Information) |
m (moved ReaYeatesProposal to Rea, Yeates (Proposal)) |
||
| (8 intermediate revisions by 3 users not shown) | |||
| Line 9: | Line 9: | ||
===Participants=== | ===Participants=== | ||
| − | * Alan Rea, Western Michigan University | + | * '''Alan Rea''', Western Michigan University |
| − | * Nick Yeates, Red Hat Incorporated | + | * '''Nick Yeates''', Red Hat Incorporated |
| − | * Student Intern, Western Michigan University. | + | * '''Student Intern''', Western Michigan University. |
| − | + | ||
Alan and Nick would work with a student intern to prepare all materials and processes. The student intern would be a student who was a team leader during the Fall 2015 project. | Alan and Nick would work with a student intern to prepare all materials and processes. The student intern would be a student who was a team leader during the Fall 2015 project. | ||
| Line 22: | Line 21: | ||
These deliverables will include: | These deliverables will include: | ||
| − | * Assignments used to help student teams move through the project and acquire knowledge and skills. Setting up OpenShift accounts and installing cartidges for testing, using Gimp to create sample rich wireframes, and helping them master using the myriad of Google offerings (Hangouts, etc.). | + | * '''Assignments''' used to help student teams move through the project and acquire knowledge and skills. Setting up OpenShift accounts and installing cartidges for testing, using Gimp to create sample rich wireframes, and helping them master using the myriad of Google offerings (Hangouts, etc.). |
| − | * Guides for approaching and implementing a similar FOSS or HFOSS project. | + | * '''Guides''' for approaching and implementing a similar FOSS or HFOSS project. |
| − | * Rubrics used to evaluate progress and deliverables. | + | * '''Rubrics''' used to evaluate progress and deliverables. |
===Process and Procedures=== | ===Process and Procedures=== | ||
| Line 37: | Line 36: | ||
We will discuss how one might best provide feedback to students in this agile collaborative environment as well as encourage students to provide feedback to their team. | We will discuss how one might best provide feedback to students in this agile collaborative environment as well as encourage students to provide feedback to their team. | ||
| + | |||
| + | Rubrics used to evaluate deliverables will be crafted to help instructors apply them to their projects. | ||
===Suggestions for Implementation=== | ===Suggestions for Implementation=== | ||
| − | Here we will generalize the frameworks and processes we used to create and guide this collaborative process. | + | Here we will generalize the frameworks and processes we used to create and guide this collaborative process. |
| + | |||
| + | This will foster collaboration among instructors and open source communities. | ||
==Target Venue== | ==Target Venue== | ||
| Line 58: | Line 61: | ||
===Assignments=== | ===Assignments=== | ||
| − | We used many assignments such as Site Specification, Information Architecture analysis, large-scale software research and recommendations (e.g., CMS), Prototype building, and actual | + | We used many assignments such as Site Specification, Information Architecture analysis, large-scale software research and recommendations (e.g., CMS), Prototype building, and actual deployments. |
We will re-craft these assignments so that instructors can adopt them for their own uses whether these be for Web, mobile, or desktop development. | We will re-craft these assignments so that instructors can adopt them for their own uses whether these be for Web, mobile, or desktop development. | ||
| Line 69: | Line 72: | ||
We will outline and discuss the processes we used making sure to note what worked well as well as flags of which one should be aware. For example, in our enthusiasm for the project we permitted too much scope creep. There are various reasons why this happened and we will put forth the warning signs. | We will outline and discuss the processes we used making sure to note what worked well as well as flags of which one should be aware. For example, in our enthusiasm for the project we permitted too much scope creep. There are various reasons why this happened and we will put forth the warning signs. | ||
| − | |||
==Evaluation== | ==Evaluation== | ||
| Line 77: | Line 79: | ||
==Schedule== | ==Schedule== | ||
| − | Spring 2016: Work with student intern to develop materials. | + | '''Spring 2016''': Work with student intern to develop materials. Materials deployed on the wiki. |
| − | Summer 2016: | + | '''Summer 2016''': Finalize all materials as well as the TeachingOpenSource.org Website. |
==Budget== | ==Budget== | ||
| Line 85: | Line 87: | ||
===Student Intern (Spring 16)=== | ===Student Intern (Spring 16)=== | ||
| − | $1500: This will provide a stipend of 10 hours a week @ $10 for the student's work. | + | '''$1500''': This will provide a stipend of 10 hours a week @ $10 for the student's work. |
===Alan Rea (Summer 16)=== | ===Alan Rea (Summer 16)=== | ||
| − | $1500: Summer Stipend for finlizing all materials and sections on the new site. | + | '''$1500''': Summer Stipend for finlizing all materials and sections on the new site. |
| − | ===SIGCSE Travel=== | + | ===SIGCSE Travel and Expenses=== |
| − | Alan Rea ($1000 | + | Alan Rea ('''$1000''') |
To present the White paper at the POSSE workshop as well as work with faculty who are interested in implementing a project such as this one. | To present the White paper at the POSSE workshop as well as work with faculty who are interested in implementing a project such as this one. | ||
| − | |||
==Contact Information== | ==Contact Information== | ||
| − | *Alan Rea (<rea> at <wmich> dot <edu>) | + | *'''Alan Rea''' (<rea> at <wmich> dot <edu>) |
| − | *Nick Yeates (<nyeates> at <redhat> dot <com>) | + | *'''Nick Yeates''' (<nyeates> at <redhat> dot <com>) |
| + | |||
| − | [[Category: | + | [[Category:Proposals]] |
Latest revision as of 19:55, 5 February 2017
Contents |
Summary
Project Dissemination
This resource will enable instructors to implement large-scale software implementation or rennovation projects in their classes using open source approaches, concepts, technologies, as well as agile development to analyze, develop, and implement successful collaborative projects between academia and industry.
The transition from http://teachingopensource.org/ to https://prod-openitup.rhcloud.com/
Participants
- Alan Rea, Western Michigan University
- Nick Yeates, Red Hat Incorporated
- Student Intern, Western Michigan University.
Alan and Nick would work with a student intern to prepare all materials and processes. The student intern would be a student who was a team leader during the Fall 2015 project.
Teaching Resource
Ultimately, we see a combination of deliverables for this project residing on this Wiki, as well as the Teacher's Guide that will be present on the new TeachingOpenSource.org site.
These deliverables will include:
- Assignments used to help student teams move through the project and acquire knowledge and skills. Setting up OpenShift accounts and installing cartidges for testing, using Gimp to create sample rich wireframes, and helping them master using the myriad of Google offerings (Hangouts, etc.).
- Guides for approaching and implementing a similar FOSS or HFOSS project.
- Rubrics used to evaluate progress and deliverables.
Process and Procedures
We will put forth guides to help craft deliverables and move student teams through a large scale open source project.
For example, in order to ensure success we built in smaller deliverables and revisions of these deliverables as well as weekly check-in’s with the client and flexible objectives to keep the team moving forward on the established project critical path.
Feedback and Rubrics
We will discuss how one might best provide feedback to students in this agile collaborative environment as well as encourage students to provide feedback to their team.
Rubrics used to evaluate deliverables will be crafted to help instructors apply them to their projects.
Suggestions for Implementation
Here we will generalize the frameworks and processes we used to create and guide this collaborative process.
This will foster collaboration among instructors and open source communities.
Target Venue
CIS3900: Business Web Architecture
This course applies human computer interaction theories, principles, and techniques to develop effective and usable Web applications for the business environment. Topics include WWW architecture, modern web-based languages, search engines, interactive content, multimedia, and other technologies for the WWW. Students will evaluate the effectiveness of various websites and develop Web applications to support Internet commerce.
TeachingOpenSource.org Project
Target Student Audience
WMU routinely offers a Web Design and Development class for juniors and seniors at least once a year. Other than students specializing in electronic business marketing, this course is an elective for information systems majors. The course stresses client-side scripting (HTML5, CSS3, and JavaScript) as well as design theory. As part of the course requirements, students must work on a semester-long project to develop a website for either a business or a nonprofit client.
Learning Activities
Assignments
We used many assignments such as Site Specification, Information Architecture analysis, large-scale software research and recommendations (e.g., CMS), Prototype building, and actual deployments.
We will re-craft these assignments so that instructors can adopt them for their own uses whether these be for Web, mobile, or desktop development.
Rubrics
Throughout the course we routinely provided feedback to teams on initial drafts of deliverables, the deliverables themselves, and also many revisions. We will refine and share the rubrics that were used.
Processes
We will outline and discuss the processes we used making sure to note what worked well as well as flags of which one should be aware. For example, in our enthusiasm for the project we permitted too much scope creep. There are various reasons why this happened and we will put forth the warning signs.
Evaluation
We would supply the rubrics used for the class. Client feedback in terms of success or failure would also be used.
Schedule
Spring 2016: Work with student intern to develop materials. Materials deployed on the wiki.
Summer 2016: Finalize all materials as well as the TeachingOpenSource.org Website.
Budget
Student Intern (Spring 16)
$1500: This will provide a stipend of 10 hours a week @ $10 for the student's work.
Alan Rea (Summer 16)
$1500: Summer Stipend for finlizing all materials and sections on the new site.
SIGCSE Travel and Expenses
Alan Rea ($1000)
To present the White paper at the POSSE workshop as well as work with faculty who are interested in implementing a project such as this one.
Contact Information
- Alan Rea (<rea> at <wmich> dot <edu>)
- Nick Yeates (<nyeates> at <redhat> dot <com>)
