Test Usability (Activity)

(Difference between revisions)
Jump to: navigation, search
(Suggestions for Open Source Community:)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
{| border="1"
 
|-
 
|'''Title''' || An HFOSS Learning Module for a CS2 Course
 
|-
 
|'''Overview''' || Students will  learn HFOSS concepts and principles and then perform and document usability tests of the OpenMRS user interface
 
|-
 
|'''Prerequisite Knowledge''' || All prequisite knowledge will be provided within the module itself
 
|-
 
|'''Learning Objectives''' || Students will understand how to contribute to open source communities, to do usability tests, to understand the relationship between interfaces and underlying objects
 
|}
 
  
=== Background: ===
+
{{Learning Activity Overview
Is there background reading material?<br />
+
|title=
 +
An HFOSS Learning Module for a CS2 Course
 +
|overview=
 +
Students will  learn HFOSS concepts and principles and then perform and document usability tests of the OpenMRS user interface.
 +
|prerequisites=
 +
|objectives=
 +
* Contribute to open source communities.
 +
* Do usability tests.
 +
* Understand the relationship between user interfaces and underlying objects.
 +
|process skills=
 +
}}
 +
 
 +
=== Background ===
 +
 
 +
''Is there background reading material?''
 +
 
 
Because we assume students know nothing about HFOSS, we will provide a sequence of readings to give them background knowledge.  
 
Because we assume students know nothing about HFOSS, we will provide a sequence of readings to give them background knowledge.  
 
The background reading will start with articles describing:
 
The background reading will start with articles describing:
Line 21: Line 26:
 
* (maybe other things we will discover  as we work this out)
 
* (maybe other things we will discover  as we work this out)
  
Are there other activities the student should have done first?<br />
+
''Are there other activities the student should have done first?''
 +
 
 
Students will not have to do any activities prior to the assigned ones.
 
Students will not have to do any activities prior to the assigned ones.
  
What is the rationale for this activity?<br />
+
''What is the rationale for this activity?''
Students in a typical CS2 course have little or no knowledge of FOSS or HFOSS and only elementary coding and software design ability, and do not necessarily know the programming languages in which various (H)FOSS projects are written, but we would like to give them a sufficiently interesting and productive experience in HFOSS so that they will be motivated to become more active in HFOSS projects as they progress in their careers. We believe that introducing HFOSS in a CS2 course  
+
 
is beneficial because they will then be prepared and hopefully motivated in more advanced courses to contribute in more advanced ways.
+
Students in a typical CS2 course have little or no knowledge of FOSS or HFOSS and only elementary coding and software design ability, and do not necessarily know the programming languages in which various (H)FOSS projects are written, but we would like to give them a sufficiently interesting and productive experience in HFOSS so that they will be motivated to become more active in HFOSS projects as they progress in their careers. We believe that introducing HFOSS in a CS2 course is beneficial because they will then be prepared and hopefully motivated in more advanced courses to contribute in more advanced ways.
  
 
Include helpful hints to faculty here.
 
Include helpful hints to faculty here.
  
=== Directions: ===
+
=== Directions ===
What should the student do?
+
  
 +
''What should the student do?''
  
=== Deliverables: ===
 
What will the student hand in?
 
  
 +
=== Deliverables ===
  
=== Assessment: ===
+
''What will the student hand in?''
How will the activity be graded?
+
+
How will learning will be measured?
+
  
Include sample assessment questions/rubrics.
+
 
 +
=== Assessment ===
 +
 
 +
* How will the activity be graded?
 +
* How will learning will be measured?
 +
* Include sample assessment questions/rubrics.
  
 
{| border="1" class="wikitable"
 
{| border="1" class="wikitable"
Line 67: Line 74:
 
|}
 
|}
  
=== Comments: ===
+
=== Comments ===
What should the instructor know before using this activity?
+
  
What are some likely difficulties that an instructor may encounter using this activity?
+
* What should the instructor know before using this activity?
 +
* What are some likely difficulties that an instructor may encounter using this activity?
  
 +
{{Learning Activity Info
 +
|acm unit=
 +
|acm topic=
 +
|difficulty=
 +
|time=
 +
|environment=
 +
|author=
 +
Stewart Weiss
 +
|source=
 +
|license=
 +
{{License CC BY SA}}
 +
}}
  
=== Additional Information: ===
+
=== Suggestions for Open Source Community ===
{| border="1"
+
|-
+
|'''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''' || Is this activity easy, medium or challenging?
+
|-
+
|'''Estimated Time to Completion''' ||  How long should it take for the student to complete the activity?
+
|-
+
|'''Materials/Environment''' || What does the student need?  Internet access, IRC client, Git Hub account, LINUX machine, etc.?
+
|-
+
|'''Author''' || Who wrote this activity?
+
|-
+
|'''Source''' || Is there another activity on which this activity is based?  If so, please provide a link to the original resource.
+
|-
+
|'''License''' || Under which license is this material made available? (http://creativecommons.org/licenses/)
+
|}
+
  
=== Suggestions for Open Source Community: ===
 
 
Suggestions for an open source community member who is working in conjunction with the instructor.
 
Suggestions for an open source community member who is working in conjunction with the instructor.
  
  
--------------------
+
[[Category:Learning Activity]]
This work is licensed under a
+
[[Category:CS2]]
[http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]
+
 
+
[[File:CC_license.png]]
+
 
+
[[Category: Learning Activity]]
+
 
+
[[Category: CS2]]
+

Revision as of 11:31, 8 February 2017


Title

An HFOSS Learning Module for a CS2 Course

Overview

Students will learn HFOSS concepts and principles and then perform and document usability tests of the OpenMRS user interface.

Prerequisites
Learning
Objectives
After successfully completing this activity, the learner should be able to:
  • Contribute to open source communities.
  • Do usability tests.
  • Understand the relationship between user interfaces and underlying objects.
Process Skills
Practiced


Background

Is there background reading material?

Because we assume students know nothing about HFOSS, we will provide a sequence of readings to give them background knowledge. The background reading will start with articles describing:

  • what open source is
  • the concept of community
  • the various ways in which one can contribute
  • the concepts of issues, bugs, and tickets
  • (maybe other things we will discover as we work this out)

Are there other activities the student should have done first?

Students will not have to do any activities prior to the assigned ones.

What is the rationale for this activity?

Students in a typical CS2 course have little or no knowledge of FOSS or HFOSS and only elementary coding and software design ability, and do not necessarily know the programming languages in which various (H)FOSS projects are written, but we would like to give them a sufficiently interesting and productive experience in HFOSS so that they will be motivated to become more active in HFOSS projects as they progress in their careers. We believe that introducing HFOSS in a CS2 course is beneficial because they will then be prepared and hopefully motivated in more advanced courses to contribute in more advanced ways.

Include helpful hints to faculty here.

Directions

What should the student do?


Deliverables

What will the student hand in?


Assessment

  • How will the activity be graded?
  • How will learning will be measured?
  • Include sample assessment questions/rubrics.
Criteria Level 1 (fail) Level 2 (pass) Level 3 (good) Level 4 (exceptional)
The purpose of the project
Why the project is open source

Comments

  • What should the instructor know before using this activity?
  • What are some likely difficulties that an instructor may encounter using this activity?
ACM BoK
Area & Unit(s)
ACM BoK
Topic(s)
Difficulty
Estimated Time
to Complete
Environment /
Materials
Author(s)

Stewart Weiss

Source
License

This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License

CC license.png


Suggestions for Open Source Community

Suggestions for an open source community member who is working in conjunction with the instructor.

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