Lecture #1 - Introduction to OOD

Web Resources:

Office Hours: Instructor & TAs

Content:

1. Office Hours
2. Starting Friday, January 16, I will hold help sessions from 9:00am until 11:45am each Friday in CST 4-201.
   Starting Friday, January 23, the TA's will also hold "surviving OOD help sessions each Friday from 4:00pm for an hour or two, also in CST 4-201.
3. Survey student background
4. Strategy versus Tactics
5. Why C++? Why not C#?
6. C++, An Assessment
7. Syllabus
   Describes topics to be covered, reading material for you to digest before coming to class, and due dates for the assigned projects.
8. Lecture #1 folder
   Contains a page of links to presentations and code discussed in this class. The Lecture folders will occasionally hold physical files of interest as well. Usually, however, all the materials of interest to the class are in the presentations and code folders. The contents of these folders will grow as you progress through the course.
9. FTP using IE
   Here is an easy way to transfer code folders from our website to your desktop.
10. Project #1 Specification
11. Visual Studio Help Notes
    
12. Visual Studio Help Session Notes
    
13. ECS (College of Engineering and Computer Science) Computer clusters:
    • Visual Studio 2008 will be used in this class, and it is installed on all the ECS Clusters, but may not be on other university clusters. So:
    • You need an account - ECS Help Desk.
    • Operational Quirks:
      Your home account is hosted on a drive mapped to H:. However, Visual Studio thinks mapped drives are not secure, and does not happily let you work there.
      You can do all your work on the C: drive of whatever machine you are using, but that is always wiped clean when you log-off. Thus, you may wish to work on the C: drive, save frequently to your home H:, and especially, save just before logging off.
    • Help Session in MadLab.
14. Code Grade Sheet
15. Submission Requirements
16. Parsing Prototype code - help for Project #1
    This demonstration code illustrates how to use modules, gives several good examples of modules, and may be of significant help to you in developing Project #1.
17. Parsing Prototype Structure
    
18. Modules
    A module is a physical package of code in files. In this course, by module, we mean those source code files that constitute a compilable entity. The result of compilation may be an execution image (exe), a dynamic link library (dll), or an object file (obj).
    A simple module example is provided in the code directory:
    HiResTimer
    
19. Notation
    When discussing object oriented designs, we will often use a subset of the Universal Modeling Language (UML), described briefly in these notes. You also may wish to consult UML Tutorial