Header image  

Computer Science and Systems Analysis

  Home ::   Teaching ::   Research  ::   Publications  ::   SEURAT  ::  
CSE 212 - Software Engineering for Human Computer Interaction

Instructor: Janet E. Burge, 205W Benton Hall, 9-0347, burgeje-at-muohio.edu
Office Hours: M:11,T:4, W:9, Th:4

Course Attendance Policy: This course involves class participation and includes a significant group-work component. Students who miss more than four class sessions for any reason (illness, interviews, travel) will be dropped from the course. If this occurs after the drop date, this will result in a failing grade for the course.

Prerequisite: CSE271
Required Text: Stone, Jarrett, Woodroffe, Minocha, User Interface Design and Evaluation
Additional References: See Course Documents on Cascade

Jump to the syllabus

Catalog Description: Principles of human-computer interaction (HCI) for software engineering. Psychological principles of HCI. Design methods such as task analysis and user-centered design. Projects demonstrating window, menu, and command design; voice and natural language I/O; response time and feedback; color, icons, sound.

Course Learning Objectives:

At the end of the course , students will be able to:

1: To provide students with an understanding of the core concepts of Human Computer Interaction

1.1: Define Human-Computer Interaction and explain its importance
1.2: List and explain the key user interface design principles
1.3: Define HCI vocabulary terms such as affordance, feedback, conceptual model, metaphor, etc.
1.4: Describe how a user interface could succeed or fail from a human diversity perspective
1.5: Explain the different user interface interaction styles and the tradeoffs involved in selecting one for a given software system

2: To evaluate a user interface for usability and utility

2.1: Discuss evaluation criteria for a user interface
2.2: Explain the difference between functional and usability requirements and give examples of each for a given software application
2.3: Evaluate a user interface based on the user interface design principles using both heuristic evaluation and user observation techniques
--- 2.3.1: Describe how the user interface does or does not achieve the quality attributes
2.4: Design and conduct a usability test and analyze the results

3: To apply the core concepts of Human Computer Interaction to building a User Interface

3.1: Define user-centered design and explain how it applies to user interface development
3.2: Perform a task analysis to develop requirements for a user interface prototype
3.3: Build a user interface prototype that is in accordance with HCI interface design principles
-- 3.3.1: Build a user interface prototype that is in accordance with HCI interface design principles
-- 3.3.2: Design a UI prototype so that it supports internationalization
-- 3.3.3: Demonstrate the consideration of the importance of response time and feedback in the prototype design and implementation user interface design principles
3.4: Explain and justify the design decisions made in the user interface prototype
-- 3.4.1: Explain and justify the choice of design modalities implemented in the prototype
-- 3.4.2: Describe which quality attributes were involved in decision-making and how they were implemented in the resulting system
-- 3.4.3: Explain how visual design elements were chosen (color, icons, fonts, etc.)
3.5: Use Scenario-Claims-Analysis to capture task analysis results and the rationale for the designed system

4: To understand the key HCI aspects of multi-media systems

4.1: Identify the key HCI issues involved in multi-media
4.2: Explain the advantages and disadvantages of using sound in a user interface
4.3: Identify areas where speech recognition would enhance the user experience
4.4: Compare different website implementations and describe how a website should be evaluated for usability

5: To understand the HCI issues involved in collaboration and communication using a variety of collaborative tools and environments

5.1: Describe the advantages and disadvantages of synchronous and asynchronous group communication
5.2: Participate in a team project where some interaction occurs using a collaborative software environment
5.3: Participate in a class activity where the interaction occurs in a virtual environment

Syllabus: Note: topics, dates, and assignments are subject to change at instructors discretion. Readings (with the exception of the first class) must be completed prior to the class time during which they will be discussed. For individual projects, no late work will be accepted. For group projects, presentations must be received on time. For other group deliverables late assignments will be penalized 10% the first 24 hrs, 25% the next (reductions will be taken at the time of computing the final grades for the course). Assignments more than 48 hours late will not be graded. Laboratory exercises must be completed during the scheduled lab period and turned in at the end of that time.

CSE 212 Syllabus
Date Topics Readings Assignments Due
1/9 Introduction Ch. 1 Survey - in class

Gathering Requirements

Lab: Paper Peer Review

Ch. 2

Homework #1: Facebook Usability

Team Project: Memo to Project Advisor, due Friday, 1/13


MLK Day - no class


Learning about Users and their Tasks

Ch. 3, 4

Homework #2
Team Project: Identifying Target Users; Task Analysis Plan, due Friday 1/20

1/23 Requirements Ch. 5, 6, 7 Homework #3
1/25 Lab: Building Surveys
1/30 Conceptual Design Ch, 8

Free Write #1: in class

Team Project: Instruments for User Studies


Exam 1


Design Rationale, Interaction Design

Ch. 9, 10

Homework #4

2/8 Lab: Value Sensitive Design    
2/13 Interaction Styles, Interaction Devices
Ch. 11, 12

Homework #5

2/14 Lab: TBD -
2/20 Interaction Elements, Design Ch. 13, 14, 15

Homework #6

2/22 Lab: Team Presentations   Team Project: System Requirements and Use Cases; Presentation

Designing a GUI

Ch. 16 Homework #7

Lab: Design Planning
Dr. Burge @SIGCSE


Spring Break - no classes


Spring Break - no classes


Designing for the Web

Ch. 17

Free Write #2: in class

3/14 Lab: Plan Review    
3/19 Design of Embedded Systems

Ch. 18, 19 Free Write #3: in class
  3/21 Exam 2



3/26 Evaluation

Ch. 20, 21

Homework #8



Lab: Team Meetings


Team Project: Design

  3/30 Alumni Conference   Must attend at least two sessions

Planning Evaluation

Ch. 22, 23 Homework #9
4/4 Lab: Evaluation Plan



4/9 Analysis
Ch. 24, 25 Quiz: open notes, closed book
4/11 Lab: Team Meetings    

More Evaluation

Ch. 26, 27

Free Write: In class
Team Project: Evaluation Plan, due 4/17


Lab: Evaluation


4/23 Communicating Findings, Pursuasion
Ch. 28, 29 Free Write: In class
4/25 Project Presentations  

Group Project: Presentations
Final Report due 4/27

5/2 Final Exam - 12:30  


Grading: The final grade for CSE212 is based on the following:


Assignment Percentage

Participation/In-class assignments/quizzes/labs

Homework Assignments 20%


  • Memo to Project Advisor (5)
  • Target Users/Task Analysis Plan (5)
  • Instruments for User Studies (10)
  • System Requirements and Use Cases (20)
  • Requirements Presentation (5)
  • Design/Prototype (10-20)*
  • Project Evaluation Plan (10)
  • Project Evaluation Report (10-20)*
  • Final Presentation (10)

* Weighting of project elements is application-specific



  • Exam 1 (10)
  • Exam 2 (15)
  • Final Exam (20)

Grading Policy: Numeric grades will be given for all assignments. Point values per-assignment will vary but will be scaled at the end of the semester into percentages and be computed using the percentages above to result in final grades using the percentages below:

98-100 = A+ 92-97.9 = A 90-91.9 = A-
88-89.9 = B+ 82-87.9 = B 80-81.9 = B-
78-79.9 = C+ 72-77.9 = C 70 - 71.9 = C-
68-69.9 = D+ 62-67.9 = D 60-61.9 = D-
< 59.9 = F


Academic Honesty: All work assigned as individual work must be done as individual work and in accordance with the departmental Academic Integrity statement. Violations will be handled in accordance with the Miami University Academic Honesty Policy.