CS321 Dr' Mark L' Hornick

1
CS-321 Computer Graphics

• Dr. Mark L. Hornick
• email hornick_at_msoe.edu
• web http//people.msoe.edu/hornick/
• webCT webct.msoe.edu
• Office CC-30
• Phone [phone]

2
Course Topics

• Overview of computer graphics
• Graphics input and output hardware
• Graphical user interfaces (GUIs)
• Lines and line generation
• Polygons and filling
• Two-dimensional (2-D) transformations
• Windowing and clipping
• 3-D objects
• 3-D transformations
• Projections and depth

3
Course Objectives

• understand computer graphics hardware,
  algorithms, and applications
• understand the design of event-driven graphical
  user interfaces
• understand and be able to apply concepts of
  object-oriented programming, inheritance,
  polymorphism, and event-driven systems
• be able to apply data structures to the
  management of computer graphics entities
• be able to use reference materials to gain
  knowledge of an unfamiliar software library
• be able to implement multi-module software
  systems incorporating components developed by
  others
• be able to clarify and document software
  requirements when specifications are initially
  incomplete or ambiguous
• understand the need for extensive internal
  software documentation, and be able to provide it

4
Your programming language background

• CE
• CS-1010 Programming 1
• CS-1020 Software Design 1
• CS-1030 Software Design 2
• CS-2851 Data Structures
• CS-280 Embedded Systems
• CS-381 Numerical Methods

5
Lab Projects

• Introduction to Linux
• Review of C
• Polymorphism and inheritance
• 2-D graphics
• Points, lines
• Polygons
• Curves
• 3-D graphics
• Scaling, translation, rotation
• Perspective

6
Lab Effort
7
Grading

• The grading formula applies only to those
  students who have successfully met the objectives
  of this course.
• There is a 10 per business day late penalty for
  all written work and no work will be accepted
  more than one week late for credit.
• The lowest quiz grade will be dropped.
• You are encouraged to discuss assignments (lab
  and homework) but everyone is responsible for
  doing and turning in their own work. (Sharing
  source code is not allowed.)
• All lab reports must be accompanied by a time log
  summary entered through the FAST system