Test Usability (Activity)

From Foss2Serve
(Difference between revisions)
Jump to: navigation, search
 
(17 intermediate revisions by 5 users not shown)
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?
+
|title=
 +
An HFOSS Learning Module for a CS2 Course or a Software Engineering Course
 +
|overview=  
 +
Students will  learn HFOSS concepts and principles,
 +
as well as the principles of usability design and evaluation.
 +
Then, students will perform and document usability tests of the OpenMRS user interface,
 +
or other HFOSS user interface.
  
−
Are there other activities the student should have done first?
+
|prerequisites=
 +
Students should be familiar with:
 +
* Principles of usability testing.
 +
* Techniques or methods of usability testing.
  
−
What is the rationale for this activity?
+
|objectives=
 +
* Contribute to open source communities.
 +
* Do usability tests for a given HFOSS.
 +
* Understand the relationship between user interfaces and underlying objects.
  
−
Include helpful hints to faculty here.
+
|process skills=
 +
[[:Category:Critical_Thinking|Critical Thinking]],
 +
[[:Category:Communication|Communication]],
 +
[[:Category:Teamwork|Teamwork]]
 +
}}
  
 +
=== Background ===
  
−
=== Directions: ===
+
''Is there background reading material?''
−
What should the student do?
+
  
 +
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:
 +
'''Background of HFOSS'''
 +
* 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)
  
−
=== Deliverables: ===
+
'''Background of Software Usability and Usability Evaluation'''
−
What will the student hand in?
+
* Eight golden rules of UI design
 +
* Principles, rules, and methods of UI evaluation
  
 +
''Are there other activities the student should have done first?''
  
−
=== Assessment: ===
+
Students will not have to do any activities prior to the assigned ones.
−
How will the activity be graded?
+
−
+
−
How will learning will be measured?
+
  
−
Include sample assessment questions/rubrics.
+
''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.
 +
 
 +
(Update for Software Engineering course) <br>
 +
Usability testing and evaluation is a very important step in software development lifecycle (SDLC). Giving students an opportunity to apply the principles, rules, and methods of UI design and evaluation to actually testing the UI of a project is a very promising in-class or after class activity in Software Engineering course.
 +
 
 +
 
 +
=== Directions ===
 +
 
 +
''What should the student do?''
 +
 
 +
1. Rank the three crucial usability criteria below, and justify.
 +
* Time to learn
 +
* Speed of performance
 +
* Avoiding user errors
 +
 
 +
=== 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.
  
 
{| border="1" class="wikitable"
 
{| border="1" class="wikitable"
Line 58: Line 97:
 
|}
 
|}
  
−
=== 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, Marco Gerosa, Lin Deng
 +
|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]
+
[[Category:OpenMRS]]
−
 
+
[[Category:Critical Thinking]]
−
[[File:CC_license.png]]
+
[[Category:Communication]]
−
 
+
[[Category:Teamwork]]
−
[[Category: Learning_Activity]]
+
[[Category:Minimal Sketch]]
−
[[Category: LEARNING_ACTIVITY_SUBCATEGORY]]
+

Latest revision as of 16:27, 7 September 2018


Title

An HFOSS Learning Module for a CS2 Course or a Software Engineering Course

Overview

Students will learn HFOSS concepts and principles, as well as the principles of usability design and evaluation. Then, students will perform and document usability tests of the OpenMRS user interface, or other HFOSS user interface.

Prerequisites

Students should be familiar with:

  • Principles of usability testing.
  • Techniques or methods of usability testing.
Learning
Objectives 		After successfully completing this activity, the learner should be able to:
  • Contribute to open source communities.
  • Do usability tests for a given HFOSS.
  • Understand the relationship between user interfaces and underlying objects.
Process Skills
Practiced

Critical Thinking, Communication, Teamwork


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: Background of HFOSS

  • 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)

Background of Software Usability and Usability Evaluation

  • Eight golden rules of UI design
  • Principles, rules, and methods of UI evaluation

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.

(Update for Software Engineering course)
Usability testing and evaluation is a very important step in software development lifecycle (SDLC). Giving students an opportunity to apply the principles, rules, and methods of UI design and evaluation to actually testing the UI of a project is a very promising in-class or after class activity in Software Engineering course.


Directions

What should the student do?

1. Rank the three crucial usability criteria below, and justify.

  • Time to learn
  • Speed of performance
  • Avoiding user errors

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, Marco Gerosa, Lin Deng

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.

Retrieved from "http://www.foss2serve.org/index.php?title=Test_Usability_(Activity)&oldid=12590"
Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox