Test Usability (Activity)
| (5 intermediate revisions by one user not shown) | |||
| Line 5: | Line 5: | ||
An HFOSS Learning Module for a CS2 Course or a Software Engineering Course | An HFOSS Learning Module for a CS2 Course or a Software Engineering Course | ||
|overview= | |overview= | ||
| − | Students will learn HFOSS concepts and principles, as well as the principles of usability design and evaluation. | + | Students will learn HFOSS concepts and principles, |
| − | Then, students will perform and document usability tests of the OpenMRS user interface, or other HFOSS user interface. | + | 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= | |prerequisites= | ||
| Line 19: | Line 21: | ||
|process skills= | |process skills= | ||
| − | + | [[:Category:Critical_Thinking|Critical Thinking]], | |
| − | + | [[:Category:Communication|Communication]], | |
| − | + | [[:Category:Teamwork|Teamwork]] | |
}} | }} | ||
| Line 30: | Line 32: | ||
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: | ||
| + | '''Background of HFOSS''' | ||
* what open source is | * what open source is | ||
* the concept of community | * the concept of community | ||
| Line 35: | Line 38: | ||
* the concepts of issues, bugs, and tickets | * the concepts of issues, bugs, and tickets | ||
* (maybe other things we will discover as we work this out) | * (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?'' | ''Are there other activities the student should have done first?'' | ||
| Line 44: | Line 51: | ||
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. | ||
| − | + | (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 === | === Directions === | ||
| Line 50: | Line 59: | ||
''What should the student do?'' | ''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 === | === Deliverables === | ||
| Line 110: | Line 123: | ||
[[Category:CS2]] | [[Category:CS2]] | ||
[[Category:OpenMRS]] | [[Category:OpenMRS]] | ||
| + | [[Category:Critical Thinking]] | ||
| + | [[Category:Communication]] | ||
| + | [[Category:Teamwork]] | ||
[[Category:Minimal Sketch]] | [[Category:Minimal Sketch]] | ||
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:
|
| Learning Objectives |
After successfully completing this activity, the learner should be able to:
|
| 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: 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
|
Suggestions for Open Source Community
Suggestions for an open source community member who is working in conjunction with the instructor.
