OpenMRS-CS2-Activity

(Difference between revisions)
Jump to: navigation, search
(Questions or concerns you have about implementing your activity)
(Support you will need to implement your activity)
Line 45: Line 45:
  
 
=== Support you will need to implement your activity ===
 
=== 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 ==
 
== Planning Stage 3 Activities ==

Revision as of 20:06, 16 June 2016

Contents

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: Learning 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

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

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

<Identify meeting times. Find out HFOSS project meeting times.>

Specific Tasks

<What will various group members do.>

Resources

<List any resources that you find>

Other Notes

Prior related POSSE groups, if any:

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