Fall2012.CSIS672CourseSyllabus History

Hide minor edits - Show changes to output

Changed lines 72-73 from:
* To gain additional experience with team work and collaborative development efforts
to:
* To gain additional experience with team work and collaborative development efforts\\
Changed lines 77-79 from:
To receive a passing grade for the course, you must average a passing grade on each of the
following: assignments, tests, and final exam.
to:
To receive a passing grade for the course, you must average a passing grade on each of the following: assignments, tests, and final exam.\\
Changed lines 83-84 from:
Exam '''or''' Final Project 20%, and Class Participation 10%.
to:
Exam '''or''' Final Project 20%, and Class Participation 10%.\\
Changed lines 123-124 from:
* '''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.
(:cellnr valign=top align=right style='padding:5px;':)
to:
* '''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.\\
Changed lines 27-28 from:
Other hours available by appointment.
to:
Other hours available by appointment.\\
Changed lines 54-55 from:
* Saul Greenberg, et al. (2011), Sketching User Experiences: The Workbook, Morgan Kaufmann.
to:
* Saul Greenberg, et al. (2011), Sketching User Experiences: The Workbook, Morgan Kaufmann.\\
Changed line 111 from:
** See College of Charleston '''[[http://studentaffairs.cofc.edu/honor-system/studenthandbook/index.php | Student Handbook]]''', section on ''Classroom Code of Conduct'' (p. 58).\\
to:
** See College of Charleston '''[[http://studentaffairs.cofc.edu/honor-system/studenthandbook/index.php | Student Handbook]]''', section on ''Classroom Code of Conduct''.\\
Changed line 118 from:
* Do not submit programs with syntax errors. They are not eligible for credit.
to:
* Do not submit programs with syntax errors. They are not eligible for credit.\\
Deleted lines 126-128:
(:cell style='padding:5px;':)

->[--(Some material adopted from Prof. Leclerc's CSCI 340 syllabus)--]
Changed lines 116-117 from:
* Programming assignment grades will be based on design and style as well as
correctness of result.
to:
* Programming assignment grades will be based on design and style as well as correctness of result.
Deleted lines 103-108:
'''Tests:'''
* Attendance at tests is mandatory. Students 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.

'''Classroom:'''
Deleted line 63:
Changed lines 65-66 from:
* To understand basic human and machine factors that influence the development of
interactive computing systems
to:
* To understand basic human and machine factors that influence the development of interactive computing systems
Changed lines 67-68 from:
* To acquire skills in integrating HCI into the system development life-cycle (analysis,
design, implementation, evaluation)
to:
* To acquire skills in integrating HCI into the system development life-cycle (analysis, design, implementation, evaluation)
Changed lines 69-70 from:
* To learn at least one development methodology and one toolkit for
prototyping/implementing user interfaces
to:
* To learn at least one development methodology and one toolkit for prototyping/implementing user interfaces
Added lines 1-141:
|| border=0 width=100%
||![-College of Charleston-] ||! [-August 27, 2012-]||

!!%center%CSIS 672 Human Computer Interaction
!!!%center%Course Syllabus

(:table border=0 width=100%:)

(:cell width=20% align=right style='padding:5px;':)
'''Professor:'''
(:cell width=80% style='padding:5px;':)
Dr. Bill Manaris\\

(:cellnr valign=top align=right style='padding:5px;':)
'''Office:'''
(:cell style='padding:5px;':)
Room: 223 J.C. Long Building \\
Phone: (95)3-8159 \\
E-mail: manarisb@cofc.edu \\
Web: http://www.cs.cofc.edu/~manaris/\\

(:cellnr valign=top align=right style='padding:5px;':)
'''Office Hours:'''
(:cell style='padding:5px;':)
Monday, Wednesday 2 - 3:30PM.\\
Friday 2 - 3PM\\
Other hours available by appointment.

(:cellnr valign=top align=right style='padding:5px;':)
'''Course Description:'''
(:cell style='padding:5px;':)
Introduction to human computer interaction and user interface development. Topics include
definitions of Human-Computer Interaction, importance of good interfaces, psychological
foundations, user-interface design examples, interaction models and dialog types for interfaces,
user interface life-cycle, user-centered design and task-analysis, prototyping and the iterative
design cycle, prototyping tools and environments, user interface implementation, and interface
quality and methods of evaluation.

This course stresses the importance of good interfaces and the relationship of user interface
design to human-computer interaction. It is intended to provide an adequate basis in software
design and implementation for user interfaces. There will be content on both the issues and
engineering process for user interface development.

''Prerequisites:'' Each student must have completed CSCI 230 (Data Structures and Algorithms)
or an equivalent or higher course, or have permission of the instructor. Minimally, each
student should have strong background in software development, data structures, and
algorithms; also strong background in a high-level programming language such as Python, Java, or C/C++.\\

(:cellnr valign=top align=right style='padding:5px;':)
'''Textbook:'''
(:cell style='padding:5px;':)
* Debbie Stone, et al. (2005), User Interface Design and Evaluation, Morgan Kaufmann.
* Donald A. Norman (2002), The Design of Everyday Things, Basic Books.
* Saul Greenberg, et al. (2011), Sketching User Experiences: The Workbook, Morgan Kaufmann.

(:cellnr valign=top align=right style='padding:5px;':)
'''References:'''
(:cell style='padding:5px;':)
Additional reading materials will provided via handouts and the [[http://www.cs.cofc.edu/~manaris/?n=Fall2012.CSIS672 | class website]].\\

(:cellnr valign=top align=right style='padding:5px;':)
'''Learning Outcomes:'''
(:cell style='padding:5px;':)

* 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

(:cellnr valign=top align=right style='padding:5px;':)
'''Grading:'''
(:cell style='padding:5px;':)
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: 80-89; C: 70-79; D: 60-69; F: <60. The grades of B+/, C+/, and D+/
may be given at the professor's discretion.

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

(:cellnr valign=top align=right style='padding:5px;':)
'''Honor Code:'''
(:cell style='padding:5px;':)
* '''You must do your assignments alone''' (or with your teammates, for group assignments).
** It is relatively easy to find solutions (or related code), modify them, incorporate them into (or even worse, present them as) your own work. Such activity is considered '''cheating'''. This is a serious offense and will affect your academic career. If in doubt, check with the instructor '''before''' you look at any code or solution related to your assignment.
* You are '''not allowed to discuss assignments''' and possible solutions with any person other than the instructor, lab instructor, tutor, grader (or with your teammates, for group assignments).
* On assignments you will be asked to identify the person(s) you received help from, if any.
* '''Any violation of these rules is an honor offense'''. See the College of Charleston '''[[http://studentaffairs.cofc.edu/honor-system/studenthandbook/index.php | Student Handbook]]''', especially sections on ''The Honor Code'' (p. 11), and ''Student Code of Conduct'' (p. 12). There is other useful information there.\\

(:cellnr valign=top align=right style='padding:5px;':)
'''Test Policies:'''
(:cell style='padding:5px;':)
* 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.\\

(:cellnr valign=top align=right style='padding:5px;':)
'''Classroom Policies:'''
(:cell style='padding:5px;':)
'''Tests:'''
* Attendance at tests is mandatory. Students 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.

'''Classroom:'''
* You are expected to participate in class with questions and invited discussion.
* You are expected to attend all classes. You are responsible for announcements made in class, assignment due dates, etc. The grade 'WA' may be given for excessive absences.

* You should '''turn off all electronic devices''' (e.g., cell phones, pagers, etc.).
* You must use computers only as directed (e.g., no checking email, etc.) during class.

* In summary, you should contribute positively to the classroom learning experience, and respect your classmates right to learn.
** See College of Charleston '''[[http://studentaffairs.cofc.edu/honor-system/studenthandbook/index.php | Student Handbook]]''', section on ''Classroom Code of Conduct'' (p. 58).\\

(:cellnr valign=top align=right style='padding:5px;':)
'''Assignment Policies:'''
(:cell style='padding:5px;':)
* Programming assignment grades will be based on design and style as well as
correctness of result.
* Assignments must be submitted using instructions provided and by the due date and time.
* Do not submit programs with syntax errors. They are not eligible for credit.

(:cellnr valign=top align=right style='padding:5px;':)
'''Late Policy:'''
(:cell style='padding:5px;':)
* 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.
(:cellnr valign=top align=right style='padding:5px;':)

(:cell style='padding:5px;':)

->[--(Some material adopted from Prof. Leclerc's CSCI 340 syllabus)--]
(:tableend:)