Fall 2007
81197
Course SyllabusCPSC 6118 Human-Computer Interface Development(Online)
Instructor / Chris Whitehead, MCSE, Assistant ProfessorE-mail:
Office: CCT 441
Office Hours: TR, 7-7:30 pm, 8:45-9 pm; otherwise, by appointment.
Contacting Me: If you need to discuss something outside of the classroom, please e-mail me within CougarView.
Cell Phone: (706) 315-5946
Department Phone: (706) 568-2410
Department Fax: (706) 565-3529
Web Site:
Required Textbooks / / Title:The Essential Guide to User Interface Design, 3rd Edition
Author:Wilbert O. Galitz
Publisher: John Wiley & Sons, Inc.
ISBN: 978-0-470-05342-3
Year: 2007
Course Description / This courses teaches you, the student, how to design and implement human-computer interfaces. Particular emphasis is placed on available software development tools for such interfaces.
The course assumes you have a basic understanding of programming concepts prior to the taking this course. The course focuses primarily on interface design, supplemented by practical applications in either Java, C#, or Visual Basic .NET. You may choose to develop the practical applications in any of the three languages.
Course Outcomes / The following are this course's outcomes:
- Students will demonstrate knowledge of the principles of human-computer interface development and human-computer interaction.
- Strategies and actions used to produce the outcome:
- Study of human-computer interface development.
- Study of human-computer interaction.
- ABET criteria covered: A, B, C, G, I, J and K.
- Program objectives covered: 1, 2, 3, 6 and 8.
- Assessment methods: programming assignments, project implementation and documentation.
- Students will demonstrate knowledge of the user interface design process.
- Strategies and actions used to produce the outcome:
- Study of the user interface design process.
- Implement the user interface design process.
- ABET criteria covered: A, B, C, G, I, J and K.
- Program objectives covered: 1, 2, 3, 6 and 8.
- Assessment methods: programming assignments, project implementation and documentation.
- Students will demonstrate knowledge of user interface usability testing.
- Strategies and actions used to produce the outcome:
- Study of user interface usability testing.
- Study of the user interface usability testing process.
- ABET criteria covered: A, B, C, G, I, J and K.
- Program objectives covered: 1, 2, 3, 6 and 8.
- Assessment methods: project implementation and documentation.
- Students will demonstrate the ability to communicate effectively.
- Strategies and actions used to produce the outcome:
- Completion of project proposal, analysis and design and implementation documentation.
- ABET criteria covered: A, B, C, F, G, I, J and K.
- Program objectives covered: 6 and 8.
- Assessment methods: project proposal, analysis and design and implementation documentation.
Course Objectives / In meeting the course outcomes described above, at the completion of the course, students will be able to:
- define what a human-computer interface is;
- describe the characteristics of human-computer interfaces, particularly graphical and Web user interfaces;
- apply the principles of user interface design to practical applications;
- implement the user interface design process;
- describe how people interact with computers;
- describe the importance of human characteristics and considerations in design and be able to apply these to practical applications;
- describe how the business function and design interact;
- implement the principles of good screen design;
- develop effective menus and navigation systems;
- design and choose windows and windows' components;
- choose the proper device- and screen-based controls;
- describe the role text and messages play in user interface design;
- provide effective feedback and help;
- implement internationalization and accessibility within an interface design;
- describe how to create meaningful graphics, icons, and images;
- choose proper colors; and
- organize and layout windows and pages.
Assessment Methods / Grades in this course will be based on the following assessments:
- Responses to discussion questions - 25%
- Comments to other students' responses - 10%
- Programming assignments - 25%
- Final Project Proposal - 5%
- Final Project Analysis and Design - 10%
- Final Project Implementation and Documentation - 25%
Percentage / Grade
90 – 100 / A
80 – 89 / B
70 – 79 / C
60 – 69 / D
<60 / F
How to Access the Course / This course is being offered through CougarView. You can access CougarView at:
At this page, click on the "Login" icon within the CougarView portion of the page to activate the CougarView logon page. Your CougarView username and password are:
Username: lastname_firstname
Password: ddmmyy
where "ddmmyy" is your birthdate: 2 digits for day, month, and year.
If you try the above and CougarView will not let you in, please use the "Need Help with CougarView?" link below the username and password textboxes to request help. If you are still having problems gaining access after a few days in the class, please e-mail me.
Once you've entered CougarView, you will see a list of courses you have access to which contains some combination of the phrases "CPSC 6118" and "Fall 2007." If you don't see this entry in the list, please e-mail me.
Once you have clicked on the course's name and accessed the particular course itself, you will find a home page with links to other sections and tools. The first thing you should do is read the "Welcome (read first)" information. This information will give you a feel for what's available in the particular CougarView classroom environment and explain in more detail how the course will work. Once you've read this information, please feel free to explore the other areas, particularly the Course Content and Discussions.
How This Course Will Work / This course will consist of readings, discussion questions, programming assignments, and a final project. On a weekly basis, you will need to:
- review the week's lesson (approx. one hour per week);
- complete the weekly readings (approx. two hours per week);
- submit responses to weekly discussion questions based on the readings (approx. two hours per week);
- comment on other students' responses to the discussion questions (approx. one hour per week); and
- complete the programming assignments (approx. three hours per week).
- decide on and complete a final project (approx. one hour per week).
Student Responsibilities / As a student in this course, you are responsible to:
- manage your time and maintain the discipline required to meet the course requirements,
- complete all readings,
- actively participate in weekly discussions,
- complete and submit programming assignments,
- decide on and develop a final project, and
- read any e-mail sent by the instructor and respond accordingly.
Instructor Responsibilities / As your instructor in this course, I am responsible to:
- post weekly lessons outlining the assignments for the week;
- post weekly discussion questions;
- read all responses to discussion questions and comments to responses;
- actively participate in weekly discussions;
- grade discussion questions, comments, programming assignments, and the final project deliverables and post scores within one week of the end of the week in which they are submitted; and
- read any e-mail sent by students and respond accordingly within 48 hours.
Attendance Policy / Regularly participating in the class discussions and posting your responses as early as possible is important. If you do not respond to discussion questions or comment on other students' responses for two or moreweeks in a row, you may receive a WF. If an emergency prevents you from responding to discussion questions or commenting on other students' responses, please contact me to make alternative arrangements.
Tentative Schedule / The following is the tentative schedule for the course. It is subject to change. A current schedule will be maintained in the CougarView calendar.
WEEK / DATES / READINGS/TOPICS
Startup / 8/16 - 8/19
1 / 8/20 - 8/26 / Part 1 - The User Interface - An Introduction and Overview
Chapter 1 - The Importance of the User Interface
Chapter 2 - Characteristics of Graphical and Web User Interfaces
2 / 8/27 - 9/2 / Part 2 - The User Interface Design Process
Step 1 - Know Your User or Client
Step 2 - Understand the Business Function
9/3 / Labor Day Holiday
3 / 9/4 -
9/9 / Step 3 - Understand the Principles of Good Interface and Screen Design
4 / 9/10 - 9/16 / Step 3 - Understand the Principles of Good Interface and Screen Design (cont)
9/16 / Final Project Proposal Due
5 / 9/17 - 9/23 / Step 4 - Develop System Menus and Navigation Schemes
6 / 9/24 - 9/30 / Step 5 - Select the Proper Kinds of Windows
Step 6 - Select the Proper Interaction Devices
7 / 10/1 - 10/7 / Step 7 - Choose the Proper Screen-Based Controls
10/7 / Programming Assignments #1 and #2 Due
8 / 10/8 - 10/14 / Fall Break - No discussions or assignments
9 / 10/15 - 10/21 / Step 7 - Choose the Proper Screen-Based Controls (cont)
10/21 / Final Project Analysis and Design Due
10 / 10/22 - 10/28 / Step 8 - Write Clear Text and Messages
Step 9 - Provide Effective Feedback and Guidance and Assistance
11 / 10/29 - 11/4 / Step 10 - Provide Effective Internationalization and Accessibility
Step 11 - Create Meaningful Graphics, Icons, and Images
12 / 11/5 - 11/11 / Step 12 - Choose the Proper Colors
Step 13 - Organize and Layout Windows and Pages
13 / 11/12 - 11/18 / Step 14 - Test, Test, and Retest
11/18 / Programming Assignments #3 and #4 Due
14 / 11/19 - 11/25 / Thanksgiving Holiday
15/16 / 11/26 - 12/9 / Work on final project
12/10 / Final Project Implementation and Documentation Due
Online Discussions / To maximize your learning, you are expected to participate actively in the weekly discussions. This means posting responses to discussion questions, commenting on other students' responses, commenting on other students' comments, and responding to comments made to your responses and comments.
During Weeks 1-5, to earn credit for discussion question responses, you must post a response to at least one discussion question. The points you earn for this post will be based on the quality of the content; that is, the thoroughness, clarity, conciseness, and relevance to the discussion question.
To earn credit for discussion question comments, you must comment on at least one other student's response. Keep in mind that replies to comments made to your responses to discussion questions do not count as comments.Similar to responses, the score you earn for comments will be based on the quality of the content; that is, the thoroughness, clarity, conciseness, and relevance to the discussion question and the response you are commenting on, as well as the value they add to the discussion.
Remember, the purpose of the course discussions is to stimulate academic debate. Critical thinking is highly desirable! If you do not agree with someone's post, say so. Just do so with respect (see the Discussion Etiquette section below).
As previously stated, I will read every posted message, but I will not necessarily respond to everyresponse or to every comment. I will, however,interject comments where necessary for clarification.
Discussion Etiquette / CSU is committed to open, frank, and insightful dialogue in all of its courses. Diversity has many manifestations, including diversity of thought, opinion, and values. Students are encouraged to be respectful of that diversity and to refrain from inappropriate commentary. Should such inappropriate comments occur, I will intervene as I monitor the dialogue in the discussions. I will request that inappropriate content be removed from the discussion and will recommend University disciplinary action if deemed appropriate. Students as well as faculty should be guided by common sense and basic etiquette. The following are good guidelines to follow:
- Never post, transmit, promote, or distribute content that is known to be illegal.
- Never post harassing, threatening, or embarrassing comments.
- If you disagree with someone, respond to the subject, not the person.
- Never post content that is harmful, abusive; racially, ethnically, or religiously offensive; vulgar; sexually explicit; or otherwise potentially offensive.
Programming Assignments Turn-in Requirements / The details concerning programming assignments will be available within CougarView.
Final Project / You are required to complete an individual final project for this course together with a project proposal, an analysis and design deliverable, and an implementation and documentation deliverable. You are responsible for deciding on the scope of the project. Details of the project requirements will be posted within CougarView.
Assignment Due Dates / All responses to class discussion questions, comments to other students' responses, and programming assignments are due during the week in which they are assigned and no later than 11:59 PM (23:59) (Eastern Time).The due dates for specific responses, comments, and programming assignments will be given in the weekly lessons, as part of the posted thread, and in the course's calendar. Assignments submitted or modified after the assignment due date will assessed a late penalty as described below.
Late Assignments / If circumstances prevent the timely posting of assignments, please notify me by e-mail within CougarView. Unless you make prior arrangements with me, any assignment submitted after its assigned due date will be considered late. Late assignments may be submitted up to three days beyond their assigned due date and are subject to a 10% reduction in points for each day they are submitted beyond the assigned due date. Assignments not submitted by the assigned due date or within the three days following the assigned due due will be assessed a grade of zero (0).
Because of course grade reporting requirements, the final project must be submitted by the assigned due date -- no exceptions! Any final project not submitted by the assigned due date will be assessed a grade of zero (0).
Extra Credit / There are no provisions for extra credit in this course.
Incompletes / If unusual circumstances preclude you from completing the course and you have satisfactorily completed all the other course requirements up until that point, I will award you a grade of "Incomplete" provided you contact me regarding the unusual circumstances and you agree to certain conditions for removal of the "Incomplete." You must, however, contact me and arrange for the Incomplete as soon as you are aware that you will be unable to complete the course and before the last day of class.
Software / In this course, you may use either Java, C# or VB.NET for the programming assignments and the final project. If you intend to use Java as your application language, you will need the Java Software Development Kit (J2SDK) to complete programming assignments and your final project. The J2SDK is part of the Java 2 Platform Standard Edition (J2SE), which is available from:
The J2SE will run on just about any platform including Windows and Linux. If you work on your programs in the CSU labs, the J2SE is installed.
You will also need an editor to compose your Java source code. Although you can use Notepad or any Java editor, TextPad, JBuilder, Eclipse, or JavaBeans are the recommended editors. The CSU labs are equipped with these particular editors.
If you are going to use C# for your programming assignments and final project, you will need the following software for this course:
- Operating system: Windows 2000 or XP Professional or Windows Vista
- Development environment: Visual Studio .NET 2005
To complete the design requirements of this course, you will need:
- Modeling tool: Microsoft Visio 2000 or above or equivalent software
Obtaining MSDNAA Software / As a student in this course, you are eligible for free Microsoft software development software. This software is available from the MSDNAA site at:
If you live or work in the local Columbus area, you can drop by the Department of Computer Science on the fourth floor in the new Center for Commerce and Technology building and check out a copy of the CDs for Microsoft Visio. If you do not live or work in the local Columbus area, you may either download the software or request that the CDs be mailed to you.
Downloading the software. Shortly after the semester begins, you will receive a message that describes a process for downloading or checking out software from the Department of Computer Science as part of the MSDNAA agreement. Visio 2000 or above will be among those available.Once the software has been downloaded, it must be installed in accordance with the MSDNAA Agreement (
Requesting the CDs be mailed to you. As an alternative to downloading the software, you may request the software CDs be mailed to you. Simply send an e-mail message to our department secretary Dianne Phillips (). Include in the message your name, address, and the name and number of this course. Once you have received the CDs, you must install the software in accordance with the MSDNAA Agreement ( Once you have installed the software, you must place the CDs back in the box they came in (or a suitable container) and return them to the Department of Computer Science. There should be a return label in the box the CDs weren't sent to you in, but you will have to pay for the return postage.
Technical Support / You must have the ability to administer your own computer system(s), and to install and configure your own software. Ordinarily, I can only provide limited support.
Academic Honesty/
Plagiarism Policy / Academic dishonesty includes, but is not limited to, activities such as cheating and plagiarism ( Dishonesty/Academic Misconduct). It is a basis for disciplinary action. Any work turned in for individual credit must be entirely the work of the student submitting the work. All work must be your own. For group projects, the work must be done only by members of the group. You may share ideas but submitting identical assignments (for example) will be considered cheating. You may discuss the material in the course and help one another with debugging; however, any work you hand in for a grade must be your own. A simple way to avoid inadvertent plagiarism is to talk about the assignments, but don't read each other's work or write solutions together unless otherwise directed by me. For your own protection, keep scratch paper and old versions of assignments to establish ownership until after the assignment has been graded and returned to you. If you have any questions about this, please contact me immediately. For assignments, access to notes, the course textbooks, books and other publications is allowed. All work that is not your own, MUST be properly cited. This includes any material found on the Internet. Stealing or giving or receiving any code, diagrams, drawings, text or designs from another person (CSU or non-CSU, including the Internet) is not allowed. Having access to another person’s work on the computer system or giving access to your work to another person is not allowed. It is your responsibility to prevent others from having unauthorized access to your work.