CSE687 Lecture #1
CSE687 - Object Oriented Design
Lecture #1 - Introduction to OOD
13 January 2009
../../webpages/FawcettHome.xml
../../webpages/Courses.xml
../../webpages/Code.xml
www.ecs.syr.edu/faculty/fawcett/handouts
../../webpages/CoreTechnologies.xml
../../webpages/Books.xml
../../webpages/Articles.xml
../../webpages/Mathematics.xml
../../webpages/research.xml
../../webpages/MastersProjects.xml
../../webpages/swdev.xml
../../webpages/webdev.xml
../../webpages/news.xml
../../webpages/OtherLinks.xml
../../webpages/SiteDesign.xml
../../webpages/graduates.xml
../../webpages/AllPages.xml
../../webpages/OfficeHours.xml
../../webpages/notices.xml
Contents
../../webpages/CSE681.xml
../../webpages/CSE686.xml
../../webpages/CSE687.xml
../../webpages/CSE775.xml
../../webpages/CSE776.xml
../../webpages/CSE778.xml
../../webpages/CSE784.xml
../Lectures/CSE687CodeL1.xml
../lectures/CSE687CodeL2.xml
../Lectures/CSE687CodeL3.xml
../Lectures/CSE687CodeL4.xml
../Lectures/CSE687CodeL5.xml
../Lectures/CSE687CodeL6.xml
../Lectures/CSE687CodeL7.xml
../Lectures/CSE687CodeL8.xml
../Lectures/CSE687CodeL9.xml
../Lectures/CSE687CodeL10.xml
../Lectures/CSE687CodeL11.xml
../Lectures/CSE687CodeL12.xml
../Lectures/CSE687CodeL13.xml
../Lectures/CSE687CodeL14.xml
../Lectures/CSE687CodeL15.xml
../Lectures/CSE687CodeL16.xml
../Lectures/CSE687CodeL17.xml
../Lectures/CSE687CodeL18.xml
../Lectures/CSE687CodeL19.xml
../Lectures/CSE687CodeL20.xml
../Lectures/CSE687CodeL21.xml
../Lectures/CSE687CodeL22.xml
../Lectures/CSE687CodeL23.xml
../Lectures/CSE687CodeL24.xml
../Lectures/CSE687CodeL25.xml
../Lectures/CSE687CodeL26.xml
../Lectures/CSE687CodeL27.xml
../Lectures/CSE687CodeL28.xml
Content
Syllabus
StudyGuideDesign.xml
StudyGuideTemplates.xml
StudyGuideClassRelationships.xml
www.research.att.com/~bs/homepage.html,
www.accu.org,
www.gotw.ca/publications/standard_c++_meets_managed_c++.htm,
www.codeproject.com,
www.sellsbrothers.com,
www.gotw.ca,
www.cuj.com,
devCentral.iftech.com,
www.ddj.com,
www.boost.org,
technetcast.ddj.com
../../webpages/officeHours.xml
This lecture is an introduction to the CSE687 course. Today we discuss topics to be covered
in this course, its
projects, examinations, and grading. We then introduce the notion of modules and discuss
common notation to be used throughout the course.
../../webpages/officehours.xml
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.
Survey student background
Strategy versus Tactics
../presentations/CPPvsDotNet.ppt
../presentations/assessmentCPP.ppt
Syllabus
Describes topics to be covered,
reading material for you to digest before coming to class, and due dates
for the assigned projects.
There are two ways to retrieve example code from the college server.The easiest is to go to the class code folder:
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-project.org/
../projects/Pr1s09.doc
../projects/VCCHLP.doc
../Code/DemoVisualStudio/demoDocumentation.doc
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 - helpdesk.ecs.syr.edu.
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.
../projects/PrGS687.doc
../projects/Submiss.doc
../code/Project1HelpS06
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.
../code/Parser/ParserStaticStructure.vsd
../presentations/modules.ppt
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:
../code/HiResTimerNativeCpp
../presentations/notation.ppt
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 dn.codegear.com/article/31863