Lecture #1 - Introduction to OOD

Web Resources:

Office Hours: Instructor & TAs

Content:

1. Office Hours
2. Starting this Friday, I will hold help sessions from 9:00am until 11:45am each Friday in CST 4-201.
   Starting Friday next week, the TA's will also hold "surviving OOD help sessions each Friday at 4:00pm, 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. There are two ways to retrieve example code from the college server.
   The easiest is to go to the class code folder:
   http://www.ecs.syr.edu/faculty/fawcett/handouts/CSE687/code,
   browse to the folder of the code you want, and right-click on the zip file in that folder and save-target.
   Another way is to use a secure FTP client like FileZilla
9. Project #1 Specification
10. Visual Studio Help Notes
    
11. Visual Studio Help Session Notes
    
12. 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 CST 3-201 computer cluster.
13. Code Grade Sheet
14. Submission Requirements
15. 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.
16. Parsing Prototype Structure
    
17. 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
    
18. 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