HIP* - For office use Only DGL
FYS WI SL
CIE CA CBL
LC UR CAP

Course Syllabus
Spring 2015 CpSc 427:  Interface Design  
Instructor: Dr. David Dailey

Meeting Time:  MWF 1:00 - 1:50 p.m.

Meeting Place: 224 AT&SH.

Instructor's Office Hours: MWF,  8:00 a.m. - 9:00 a.m.; Tuesday. 10:30 a.m. - 12:30 p.m.., or by appointment.

Instructor's Office location: AT&SH 248

Instructor's e-mail address:  david.dailey@sru.edu

Assessment: The connection of course outcomes, with departmental outcomes and ultimately with university outcomes is discussed at some length at http://cs.sru.edu/~whit/assessment/.

Prerequisites:  CpSc 413 and CpSc 317. 

Supplemental Textbook: Ratner -- Human Factors and Web Development -- Lawrence Erlbaum publisher.

Required reading: Class web page found at http://srufaculty.sru.edu/david.dailey/cs427/index.htm

Computing labs: The class will primarily use equipment provided in the classroom; but other machines on campus are available and may be used as well.

Method of determining final grade
: Assignments: 30%; quizzes 15%; class participation 15%; team project (including writeup and presentation): 40%.

Final exam:  The course will not have a final exam, but rather will meet (as per http://www.sru.edu/academics/enrollment/AcademicRecords/Pages/FinalsSchedule.aspx ) for a final class Thursday, May 7th, at 1:00 p.m.

Attendance policy: Regular attendance is expected. Excessive absences will have an effect on your grade. If a prolonged illness should cause you to miss several class periods, you are expected to discuss this with the instructor.

Late work: Assignments will be accepted until three weeks after the due date, but with a penalty of 10% for any assignment turned in after the due date and a penalty of 20% for work turned in more than one week after the due date. Assignments more than three weeks late, or beyond the end of the semester, cannot be accepted.

Make-up exams: It is the student's responsibility a) to notify the instructor beforehand if he or she must miss an exam due to illness or family emergency and b) to take the initiative in finding a time suitable to the instructor for a make-up exam. Make-up exams must be scheduled within one week following the original exam date.

Academic Integrity

All academic work for this course must consist of your own work. Though it remains the student's responsibility to read and understand the University's expectations here, I wish to emphasize the following excerpts from that statement:

"It is expected that students engage in the following pre-emptive behaviors:
The fact that this course is in Computer Science does not lessen the student's responsibility to make sure that work submitted for a grade is his or her own work. Again, from the University's statement on Academic Integrity:
The University gives many examples of academic dishonesty, including:

Assignments and tasks: Each assignment will be explained in class. Any uncertainties students may have about an assignment should be raised at the time the assignment is made. Students may be required to use e-mail for certain assignments; assignments submitted via e-mail must include, in this order, the course number, the student's last name and the assignment number in the subject line of the message. Assignments submitted through e-mail that do not follow the exact format explained in class may receive a grade of zero.

Several homework assignments will be given during the semester. Unless otherwise stated, these assignments are to be completed individually by each student. Students may be called upon to present and explain their work to the class or to the instructor and should be consistently and adequately prepared to do so.

Team projects may be assigned. To the extent that it is possible, each student's contributions to such projects should be identified.

As the semester progresses, additional details about assignments may be found on the class web page.

Class discussion: Interface design is a topic with few certainties. Opinions abound. It is expected that the student will augment the discussion  through readings of the literature in the subject.

Tentative Schedule of Topics

The instructor reserves the right to change topics covered or the order in which they are covered at his/her discretion. Assignments shown may vary. Refer to lecture notes and/or course web-site for details.

Week 1 --   Class introduction; user interface and necessary skills

a.   The web application

b.   user expectations

c.   domain knowledge

d.   basic JavaScript

Week 2 --  Screen and mouse coordinates, positioning and moving objects

a.   graphical web -- SVG

Weeks 3 - 5 --   Advanced web programming

a.   Events, objects, array methods

b.   DOM techniques

Week 6 --   Human Factors

a.   Perception

b.   Psychophysics

c.   memory

d.   problem solving

e.   cognition

Week 7 - XML, HTML and SVG

a. cross DOM programming, XML

b. SVG DOM and userinterface -- getBBox(), getCTM()

Week 8 --  IV. Usability Evaluation

a.   Usability testing
b.   task efficiency vs. user satisfaction
c.   accessibility,
d.   navigability
e.   analyzing behavioral protocols

Week 9 --   Collaborative computing, data mining and usability

 Collaborative computing

a.   Tools for managing group work

b.   methods of dividing labor

c.   group protocol

Data Mining and Usability (3 hours)
a.   Bootstrapping from public data
b.   Lexicography
c.   Advanced statistical methods
    i.   Multiple regression
    ii.   Factor analysis
    iii.   Multidimensional scaling

Weeks 10 & 11 --  Lab work on team projects.

Developing Effective Interfaces (3 hours)

a.   Matching interface elements to user requirements

b.   Graphical user interfaces

c.   Mapping the screen

d.   Active and functional vs. explanatory or decorative

Accessibility (2 hours)

a.   Accessibility guidelines and regulations

b.   W3C Standards

c.   Biometrics

Quiz: Probable time for quiz.

Weeks 12 - 13 --   Team project is finished.

Alternative interfaces (2 hours)

a.   Multiple touch points

b.   Accelerometers

c.   Mobile computing

d.   Pervasive computing

Human-Centered Computing (2 hours)

a.   Task analysis

b.   The individual and the group

c.   Human-centered design

d.   Stakeholders or constituents

Weeks 14-15 --  Final projects: presentation, discussion and critique.

 

 

Computer Science Department
Course Competency Plan

COURSE: CpSc 427 - Interface Design

Catalog Description: This Information Technology major course uses graphical user interface design concepts to introduce interface design possibilities. This senior-level course requires students to produce an intricate interface that utilizes systems design, information management, systems administration & security, and programming concepts from lower-level courses. This course is intended as a capstone course that introduces human user interface theory and practice. Prerequisites: CpSc 413 and CpSc 317. (3 credits)

Course Outcomes: This course and its outcomes support the Information Technology Learning Outcomes of Problem Solving and Critical Thinking (PS&CT) and Communication and Interpersonal Skills (C&IS). These Information Technology Learning Outcomes are tied directly to the University Wide Outcomes of Critical Thinking and Problem Solving and Communication.

Program Objectives Assessed in CpSc 427

Degree

Program Objective

Assessed Course Objective

IT

I.a. Apply programming and system management techniques to address information technology problems

1. Build web based  projects with appropriate computer-human interface designs and techniques.

IT

II.c. Devise effective user interfaces for the web

2. Work with a team to develop large interface design project.

 

II.d. Work cooperatively in teams and with others

IT

II.b. Use written, oral, and electronic communication to convey technical information effectively

3. Develop a written report concerning a large interface design project.

4. Develop an oral reports concerning a large interface design project.  

IT

III.a. Determine the economic and organizational effects of information technology on global society

5. Demonstrate understanding of the cultural and social  interplay between technology and humans.

 

Additional Course Objectives include:

The student will be able to:

  1. Describe and analyze computer-human interface design theory and techniques.
  2. Create interactive Web pages within the constraints of system security and administration requirements.
  3. Utilize appropriate tools for interface design projects.