It is easy to make things hard.
It is hard to make things easy.
—A. Chapanis, 1982
Syllabus Schedule GMU policies My home page
update: January 2023

SWE 205 : Software Usability Analysis and Design
Course Syllabus — Spring 2023

Professor: Jeff Offutt
Email: offutt@gmu.edu
URL: cs.gmu.edu/~offutt/
Office: 4302 Engineering Building
Office hours: Wednesdays 3:30-5:00
or by appointment
Class hours: MW noon-1:15
Class location: Horizon 1008
Prerequisites: ENGL 101 or ENGL 100
GTA:

UTA:

SWE 205 is required for BS ACSSoftware Engineering majors, and is suitable for all students interested in usable computing applications, including students in psychology, human factors, computer science, math, physics, and all engineering fields.


overview | grading | policies | miscellaneous

Overview

TEXTS

CATALOG DESCRIPTION
Principles of user interface design. Concepts for objectively and quantitatively assessing the usability of software user interfaces. Outcomes include knowledge of quantitative engineering principles for designing usable software interfaces and an understanding that usability is more important than efficiency for almost all modern software projects, and often the primary factor that leads to product success. Major topics include cognitive models for human perceptions and needs, which are used as a basis for analytical and critical thinking about user interfaces; specific engineering principles for designing usable menus, forms, command languages, web sites, graphical user interfaces and web-based user interfaces. Assessments will include written analytical evaluations of existing user interfaces, exams, and HTML-based design projects.

LEARNING OUTCOMES
  1. Knowledge of quantitative engineering principles for how to build software interfaces that are usable.
  2. Understanding that usability is more important than efficiency for almost all modern software projects, and often the primary factor that leads to product success.
  3. The ability to critically analyze existing user interfaces and express their positive and negative aspects in engineering terms, both verbally and written.

CONTENT & STUDENT RESPONSIBILITIES
After completing this course, students should understand how to design and evaluate software interfaces that are appropriate for the user. The class will rely on critical thinking to understand what makes a computer UI usable. We will look at many example UIs and discuss what they do right and what they do wrong. Grading will be based on a midterm, a final, several written usability assessments, and class participation. SWE 205 will not require programming.
overview | grading | policies | miscellaneous

Grading

GRADING FORMULA

GRADED ASSIGNMENTS
We will have around 10 assignments. Some will be usability evaluations of software interfaces and require a short written report, and some will require examples to be brought into class. Unless stated otherwise, you can collaborate with up to two partners—submit one solution and each person will get the same grade. Assignments will be posted on the class schedule page and clarifications and hints will be posted on the discussion board. You may discuss the assignments on the discussion board and share information, although not complete solutions. Unless stated otherwise, assignments should be submitted on paper and in class.
Timeliness: Assignments are due at the beginning of class (noon) on the stated due date. Submissions will be accepted after the due dates with the following deductions: (1) a maximum score of 80% for two weeks, (2) a maximum score of 50% from two weeks until the beginning of final exams. Per GMU policy, all assignments must be submitted before the beginning of final exams.
Note: You are NOT ALLOWED to include “guest names,” that is, every person listed as a collaborator must contribute. If someone is listed as a collaborator but did not contribute, all will be given a zero on the assignment and reported to the university honor committee.

PARTICIPATION
Students must be actively engaged with this class throughout the semester. Students must attend class, participate in classroom discussions, and participate in the online bulletin board (Piazza). This is an easy, but essential part of your grade.

You earn participation points in three ways: (1) attending class (1 point for each class meeting), (2) submitting in-class exercises (1 or 2 points for each exercise), and (3) contributing to discussions on the discussion board (1 point for each meaningful contribution). The exact number of total points possible will depend on the number of in-class exercises. I will calculate the total number of points that could be earned if you only miss one week of class (two meetings) and submit every in-class exercise, and define that to be 100% participation. Students with more points will be ceilinged at 100%.

EXAMS
There will be a midterm and a final exam, both closed-book in class. The final will not be cumulative.

IN-CLASS EXERCISES
I strongly believe that active exercises during class meetings enhance learning. Dr. Ammann posted a good summary of why. Thus, we will have in-class exercises every class meeting. Some will be done in small groups, and a few may be individual exercises. They count towards your participation grade and earn 1 point for a minimal effort or 2 points for a serious effort. They will be announced during class.

EXCUSED ABSENCES FOR ILLNESS
An absence can be excused if you are ill (covid, flu, cold, etc.) or have an emergency, and you document your reason for your absence. For example, a covid test result is acceptable documentation. If you have an excused absence, you will receive the attendance point and can submit in-class exercises electronically (I will give instructions on piazza). You must inform me via email for an excused absence, preferably before class starts.

RECORD KEEPING
The TA and I will use Blackboard to maintain RAW scores and attendance data. I compute grades according to this syllabus in a private spreadsheet. There is a column in BB labeled “TOTAL”: Ignore it; it’s meaningless for this class. (BB will not allow me to disable or hide this column.) If you see an error in the BB records, please inform us.
overview | grading | policies | miscellaneous

Policies

READINGS
Readings are given on the schedule web page. I expect you to read the relevant material before class meets. The lectures may not cover everything in the readings and will often include material not found in the readings. Most chapters are fairly short and easy to read.

DISCUSSION BOARD USE
All students will be enrolled in the discussion forum for SWE 205 on Piazza. You will receive an invitation via your Mason email. We will use the discussion board throughout the semester. Ask all technical questions about the material or the assignments on piazza. You can also post about software failures, errors in the books or slides, or about topics that extend our classroom discussions.

IN-CLASS COMPUTER USE
Computers will be used extensively during in-class exercises, discussions, and examples, but lectures in this class will be computer free. Computers, whether in the form of laptops, tablets, mobile phone, or pocket-computers, may not be used while I am lecturing. I have a detailed explanation why, but here is the short summary: Computers interfere with your classmate’s ability to concentrate on the educational material, my concentration, and your learning. Taking notes by hand is much more effective than typing notes on a computer. If you have to check your email or text messages, or take a phone call, please sit near the door so you can politely step out. If your behavior is disruptive, I will ask you to close your computers, and if that doesn’t work, will ask you to leave the classroom.

EMAIL
I send course announcements to your Mason email account, so you must read it regularly. Professors are required to use your Mason email, not personal email accounts. When you send email to the professor or TA, please start the subject with “swe 205.” If not, we may not prioritize it. Questions about the technical material and class policies should be posted on the discussion board, not sent through email.

OFFICE HOURS
Office hours are times that I commit to being in my office, door open, first come, first served. You do not need an appointment, and no appointments are made. If you cannot make my office hours, then we can try to set up an appointment. Please note that I am seldom available after 5:00 pm. I will inform you in class or on the discussion board if I have to miss office hours.

TECHNOLOGIES USED
You will need access to a computer and stable wifi for this course. In-class exercises will often use computers, and you will find that a laptop will be better than a small-screen pocket computer (aka phone). This class will not require programming.
overview | grading | policies | miscellaneous

Miscellaneous

ELECTRONIC PRESENCE
I always accept linkedin requests from current and former students—we clearly have a professional relationship. (Be sure to remind me when you took my class.) I tweet random thoughts irregularly about software engineering @jeffoffutt. I do not initiate facebook requests from students, but usually accept them.

HONOR CODE STATEMENT
As with all GMU courses, SWE 205 is governed by the GMU Honor Code. In this course, all graded submissions carry with them an implicit statement that it is the sole work of the author, including joint work when explicitly authorized. If joint work is authorized (usually), all contributing students must be listed on the submission. Any deviation from this is considered an Honor Code violation, and as a minimum, will result in failure of the submission and as a maximum, failure of the class.

OFFICE OF DISABILITY SERVICES
If you need academic accommodations, please see me and contact the Disability Resource Center (DRC) at 703-993-2474. All academic accommodations must be arranged through the DRC.

OTHER USEFUL CAMPUS RESOURCES
Writing Center: A114 Robinson Hall; (703) 993-1200; https://writingcenter.gmu.edu
University Libraries “Ask a Librarian”: https://library.gmu.edu/ask
Counseling and Psychological Services (CAPS): (703) 993-2380; https://caps.gmu.edu

Top