ENEL 315 Winter 1999 Notes on the Final Exam

Contents

• Some of this text is borrowed previous Web pages
• Exam Topics
• Exam Format
• Reference Material
• Suggestions for preparation
• No solutions for last year's exam

[back to top of document]

The exam will focus mainly on topics that were heavily emphasized in lectures and labs. We are not going to make a lot of marks depend on topics that were given very little coverage in lectures and labs.

The exam will focus mainly on concepts covered after the mid-session test, but there will also be some questions on concepts covered before the mid-session test.

Questions could potentially be on any material covered in the course, with the following exceptions:

• You will not have to answer questions about using Linux or Emacs.
• You will not have to answer questions about using the gdb debugger.
• You won't have to know details of Java I/O classes such as FileReader, BufferedReader, etc.
• You will not be asked to draw any class relationship diagrams or object message diagrams. I think these diagrams are useful, but the rules for drawing them were so loosely specified that I can't ask for diagrams for anything but tiny, uninteresting programs. So I'd prefer not to ask for any class relationship diagrams or object message diagrams at all.

You do not need to memorize information about the Java API (the set of library classes available for use by developers). If a problem requires use of classes such as Math, Double, Vector, and so on, you will be provided with appropriate documentation or examples to work from.

[back to top of document]

• the exam is closed-book--you are not allowed to take any books or notes to your seat;
• you are not allowed to use a calculator or computer during the exam.

The exam will consist of many short questions. Questions will be of the following types:

• You will have to write function definitions or other short segments of C++ or Java to do specific tasks.
• You will have to draw diagrams and/or predict program output to show that you know how a given program works.
• You may have to write very short paragraphs (roughly two or three paragraphs) to show that you understand key terms and concepts from the course.

You will write all of your answers on the question paper, in spaces provided for answers.

[back to top of document]

• the header file TWList.h as used in Labs 3 and 4
• an example Java program that demonstrates (a) access to command-line arguments and (b) exception handling;
• an example illustrating C++ operator overloading;
• an example of a C++ class template.

[back to top of document]

• Review lecture notes and course handouts carefully. Many of the `Read This First' sections in lab handouts contain useful information.
• Re-do lab exercises using pencil and paper, especially those exercises that you found difficult when you first did them. Practice writing complete function definitions with pencil and paper--writing code by hand is a bit different from typing code in a text editor, and it's obviously an important skill to develop for tests and exams.
• Use the textbook to get background information when you find a particular topic difficult. Do not attempt to memorize all the textbook sections listed in your lecture notes as related reading--that is a very ineffective way to use your time.
• Review last year's exam. The format will be very similar this year; topics will change to reflect changes in the order of topic coverage this year. (Note: Java was not covered before the midterm last year.)

[back to top of document]