Fall 2017»CSCI 380 Course Syllabus

CSCI 380 Course Syllabus

College of CharlestonAug. 22, 2017

CSCI 380 Ė User Interface Development

Course Syllabus


Dr. Bill Manaris


Room: 326 Harbor Walk East Building
Phone: (95)3-8159
E-mail: manarisb@cofc.edu
Web: http://www.cs.cofc.edu/~manaris/

Office Hours:

MWF, 2:00pm-3:00pm
Other hours available by appointment.


"For end-users, the interface is the system. So design in this domain must be interaction-focused and human-centered. Students need a different repertoire of techniques to address this than is provided elsewhere in the curriculum." See ACM/IEEE Computer Science Curricula 2013 (CC 2013).

This course spans CC 2013 HCI/Foundations [4 Core-Tier1 hours] and HCI/Designing Interaction [4 Core-Tier2 hours]. It also includes elements from the following CC 2013 electives: HCI/Programming Interactive Systems (Software Architecture Patterns), HCI/User-Centered Design and Testing (Prototyping techniques and tools, Evaluation with and without users), and others (as time allows).

Course Description:

Introduction to human-computer interaction and user interface development. Topics include human factors of interactive software, interactive styles, design principles and considerations, development methods and tools, interface quality, and evaluation methods. Stresses the importance of good interfaces and the relationship of user interface design to human-computer interaction.

Prerequisites/ Requirements:

  • CSCI 221 with a grade of C- or better.
  • MATH 207 (co-requisite or prerequisite)



  • JythonMusic GUI library for quick functional prototyping (and usability testing).

Additional reading materials will provided via handouts and the class website.

Learning Outcomes:

  • To understand how HCI relates to other aspects of software engineering
  • To understand basic human and machine factors that influence the development of interactive computing systems
  • To gain basic skills and knowledge for user interface design
  • To acquire skills in integrating HCI into the system development life-cycle (analysis, design, implementation, evaluation)
  • To develop an appreciation for user-centered design
  • To learn at least one development methodology and one toolkit for prototyping/implementing user interfaces
  • To gain awareness of other tools and methods available
  • To develop at least one user interface
  • To gain additional experience with team work and collaborative development efforts


To receive a passing grade for the course, you must average a passing grade on each of the following: assignments, tests, and final exam.
Scale: A: 90-100; B+: 85-89; B: 80-84; C+: 75-79; C: 70-74; D+: 65-69; D: 60-64; F: 0-59.

Final Grade Computation: Assignments (4-6) 30%, Tests (2) 35%, Comprehensive Final Exam or Final Project 15%, and Class Participation 20%.

Test Policies:

  • Attendance at tests is mandatory. You must complete tests with no discussion or sharing of information with other students.
  • Calculators, computers, cell phones, etc. may not be used during a test, unless otherwise directed.

Classroom Policies:

Assignment Policies:

  • Assignment grades will be based on creative inspiration, design, style, and correctness of result.
  • Assignments may NOT be submitted via email.
  • Submission instructions will be provided for each assignment.

Honor Code:

  • You must do your assignments alone (or with your teammates, for group assignments).
  • You are not allowed to discuss assignments and possible solutions with any person other than the instructor (or with your teammates, for group assignments). Any violation of these rules is an honor offense.
  • On assignments you will be asked to identify the person(s) you received help from, if any.

  • Lying, cheating, attempted cheating, and plagiarism are violations of our Honor Code that, when suspected, are investigated. Each incident will be examined to determine the degree of deception involved.

    Incidents where the instructor determines the studentís actions are related more to a misunderstanding will be handled by the instructor. A written intervention designed to help prevent the student from repeating the error will be given to the student. The intervention, submitted by form and signed both by the instructor and the student, will be forwarded to the Dean of Students and placed in the studentís file.

    Cases of suspected academic dishonesty will be reported directly by the instructor and/or others having knowledge of the incident to the Dean of Students. A student found responsible by the Honor Board for academic dishonesty will receive a XXF in the course, indicating failure of the course due to academic dishonesty. This status indicator will appear on the studentís transcript for two years after which the student may petition for the XX to be expunged. The F is permanent.

    Students should be aware that unauthorized collaboration--working together without permission-- is a form of cheating. Research conducted and/or papers written for other classes cannot be used in whole or in part for any assignment in this class without obtaining prior permission from the instructor.

    Students can find the complete Honor Code and all related processes in the Student Handbook.

Late Policy:

  • You have four "late" days for the whole semester. You may use these days as you wish for assignment submission. If you use them up, no late assignments will be accepted.
  • If you submit everything on time (i.e., use no late days), you will earn an additional 2.5 bonus points on your course grade.