Fall 2009 Final Exam Review Page

CSE1320 Section 002                                                                                       Dr. Tiernan's section

Topics to be covered on Final - all material since Test #2 as covered in class.  Final is comprehensive so review Test #1 and Test #2 review sheets as well.

 

Main Topics                                                                                               Final Exam is IN CLASS

C++                                                                                            Section 002; Wed. Dec. 9, 11:00 am

      In general terms, the difference between sequential programming (like C) and object-oriented programming (like C++)

C++ improvements on C

Be able to use:

C++ stream I/O

      cout, cin

      <<,>>

      <iostream>

bool

inline

Default parameters

Reference parameters

C++ dynamic memory management

      new, delete

C++ topics

Be able to:

write a C++ class with constructors, accessors, mutators and destructors

write an overloaded class member function

write an overloaded operator for a class

instantiate C++ objects

invoke member functions on C++ objects

Object-oriented concepts

Be able to describe and recognize:

Data abstraction

Data encapsulation

Information hiding

Classes and object

Polymorphism

Function name overloading

            how C++ decides which function to use

Operator overloading

            operators that cannot be overloaded

Templates;what they are

C library

      Math functions
      Char functions
      Error checking and reporting functions

C and C++ extra topics

Be able to recognize and understand:

Inheritance; base class and derived classes

member initialization list

I/O functions and flags

 

Pointers

Recursion

Arrays and structures

Function declaration and definition

Storage class and scope

 

Secondary and Related Topics

Error handling

            with input and output and library error functions

 

Test will have some or all of the following characteristics:

            multiple choice questions (not more than 10) – typically 1 to 2 points each

            short answer questions

            coding questions which require either

                        writing code or

                        interpreting code or

                        debugging code

                  ( ÒcodeÓ includes declarations, preprocessor directives, function definitions and

                  general coding of statements and control structures and I/O commands)

            matching questions

            fill-in-the-blank questions

      Questions generally have their point value listed in braces at the end/side of the question

      Every test will have at least 10 points worth of extra credit available

Test grades are assigned on a curve based on the range of actual scores on the test, i.e. the highest score on the test (for example, an 89) will be the top of the curve so all scores will be assigned based on where they fall (100 – 90 A, 89 – 80 B, etc.) AFTER the actual score has been divided by the curve.  For example, a high score of 89 would give that student an A because 89/89 100 = 100.  On the same test then, a score of 68 would be curved as 68/89*100 = 76 so that student would get a C (rather than a D for the original 68).

 

The test will make you think not just remember.  I write very challenging questions that require you to think all the way through them.  A small number of the questions will be memory type questions because some rules must be memorized to make a student an efficient programmer in a language.  Most however will require lots of mental effort.  Do not get too upset about it – remember EVERYONE is suffering through the same test you are and that everyoneÕs grade will be curved.  Check out my website for a few example test questions from previous semesterÕs tests.  They will give you a sense of how my tests are written.