OpenMRS-CS2-Activity

Group Participants

• Stewart Weiss
• Lori Postner

Planning an Initial HFOSS Learning Activity

Please discuss and record your group's approach for an initial learning activity. When you have a good draft description of the learning activity using the sections below, you could create a learning activity page for it by copying the template here: Activity Template

Course targeted for the activity

Computer Science 2

Brief description of the activity

Homework assignment where the students will assess the interface usability and record problems, suggestions for improvement, etc. Pre-req:

• need an introductory understanding of FOSS
• limited knowledge of electronic medical records

Outcome:

• provide feedback on the usability of the interface to the community

Time you expect the HFOSS activity to take

e.g. # classes, # homework assignments, # lab activities, etc.

• 1 homework - usability tests (presumes a 1-hour description of problem and requisite knowledge)

Whether the activity will be completed in class or out of class

• out of class activity

Relationship of this activity to course goals/objectives

• improve technical communication skills (both oral and written)
• enhance the ability to assess software quality
• understand the relationship between user interface and underlying objects and methods
• understand the difficulty of designing and implementing robust user interfaces and methods of handling errors.

What students will submit upon completion of the activity

Students will submit:

• summary of bugs, enhancements, features (with the intent of contributing back to the community)
• description of the process they used to test the interface
• feedback on what they learned from completing the exercise

Approach for assessing the student work

• based upon the process and the ability to communicate the process in a written form
• not based upon the number of bugs, enhancements, etc. found or suggested
• not a large percentage of the course grade

Questions or concerns you have about implementing your activity

• what is going to motivate students to test thoroughly?
• how much domain knowledge is necessary?
• much time will it take to thoroughly test?

Support you will need to implement your activity

• documentation on the product
• community support to answer questions regarding the intended use - contact person if person
• departmental buy-in

Planning Stage 3 Activities

Meetings

The two members of our group will communicate by various electronic media to make progress on planning the activities and fleshing out all details. We have not worked out specific meeting times. The goal is to be prepared for the fall 2016 semester, so the goal is to continue discussions over the next two months.

Specific Tasks

Tasks include:

• defining the exact set of readings, all available online.
• defining the exact set of "field trips" to HFOSS websites in order to learn about how open source communities are organized
• deciding which version of OpenMRS to install on lab machines and having them installed
• testing the installations and trying to find some interesting bugs to use for later exercises.
• creating a spreadsheet template that students will use for documenting their "tickets".
• writing the tutorials to augment the CS2 curriculum related to FOSS.
• writing tutorials about approaches to usability testing
• deciding exactly which parts of the OpenMRS client code the students should test an explore
• writing the exercises
• writing the grading rubric

Resources

There are various resources on the web to facilitate our work. Some include

• http://teachingopensource.org/index.php/How_to_start_contributing_to_or_using_Open_Source_Software
• https://www.gnu.org/philosophy/free-sw.html
• https://opensource.org/faq
• https://icontribute.wordpress.com/how-to-contribute-to-open-source-without-coding/
• http://blog.smartbear.com/programming/14-ways-to-contribute-to-open-source-without-being-a-programming-genius-or-a-rock-star/

Other Notes

Prior related POSSE groups, if any: