1. SWE 205 Software Usability Analysis and Design
Welcome to
SWE 205
Software Usability
Analysis and Design

2. Learning Objectives
Students will learn knowledge of what constitutes a usable human-computer interface
Students will learn quantitative engineering principles for designing usable human-computer interfaces
Students will learn that usability is key to modern software success
Students will learn how to evaluate the usability of human-computer interfaces
Students will develop :
Critical thinking skills
Divergent, creative, problem solving skills
Collaboration skills
4-Dec-18
© Offutt

3. Class Overview Class URL : http://www.cs.gmu.edu/~offutt/classes/205/
Contact info, TA
Objective : How to build software for people
Readings : Posted in schedule
Exams : Midterm and final, closed-book, in class
Evaluations : User interfaces—short written reports
Participation : 25% of the grade!
Class structure :
Tuesdays will usually be lecture
Thursdays will often be group exercises or discussion
4-Dec-18
© Offutt

4. Goal : How to design interfaces for users’ needs
Class Structure
Books :
The Design of Everyday Things, Don Norman
Don’t Make Me Think: A Common Sense Approach to Web Usability, Steve Krug
Lots of examples in class – not just software
Why my PPT clicker is so cool
Why my stovetop encourages me to turn on the wrong burner
Why my car key is stupid
Why my portable mouse is brilliant
Written evaluations of user interfaces (critical thinking)
NO programming
Goal : How to design interfaces for users’ needs
4-Dec-18
© Offutt

5. View Syllabus Online Participation … Homework … Collaboration …
In-class computer use …
4-Dec-18
© Offutt

6. Class Participation
You must be engaged with the class throughout the semester
You must contribute to the class—we all want to learn from YOU
Ways to participate :
Attend class—attendance will be monitored
Must make at least 25 class meetings to earn a C
Speak up during class discussion periods
If you are shy, more posts on the class forum can make up for being quiet in class
Bring UI examples to class
Post substantial comments to the class forum
Must average about one post per week to earn a C
4-Dec-18
© Offutt

7. Homework Assignments
We will have around 10 homework assignments—not quite one per week
None will be hard or time-consuming
Evaluations : Analyze some user interface, use a form to prepare a short written report
1 or 2 pages
About 30 minutes
Hopefully these will be fun !
Bring examples of UPs (usability problems) to class
Other small exercises
4-Dec-18
© Offutt

8. Schedule URL : http://www.cs.gmu.edu/~offutt/classes/205/sched.html
Please read before class
Slides and assignments posted before class
If I update something, I will add a “new” image to the schedule web page
Handouts and notes are there for your benefit and entertainment
4-Dec-18
© Offutt

9. Readings Most chapters in the books are short
The reading should make you think, but the concepts are not hard
Examples are real and simple
No math to work through
It is very important to keep up with the reading—reading before class will prepare you to :
Understand what I’m talking about
Join the discussion
4-Dec-18
© Offutt

10. I expect more than half the class to earn an A
Grading Policy
20% : Assignments
25% : Class participation
25% : Midterm
30% : Final – closed book, in-class, comprehensive
> 90% : definitely an A or A-
> 80% : definitely a B or A
> 70% : definitely a C, B or A
Only one A+ — the top grade in the class
I expect more than half the class to earn an A
4-Dec-18
© Offutt