CSE 115
Week 1
January 14 – 18, 2008
Monday



Syllabus
Course Policies
Communications Assignment
Wednesday
Announcements



If you do not have a syllabus, please
come get one.
If you have not signed and turned in
the last page of the syllabus, please
do so.
If you are having registration issues,
please come and see me.
Wednesday Game Plan





Questions about course/policies
Communications Assignment Sign Up
Sheet
Recitation Change Form
Lab 1 Prep Work
Introduction to Computer Science
Wednesday




What is computer science / computer
engineering?
What do computer scienists /
engineers do?
Some history of the field
Programming Paradigms and
languages
Friday Announcements

Handouts so far:
– Syllabus
– Communications Assignment Sign Up
Sheet
– Lab 1 Prep Work


Turn in last page of syllabus
No class on Monday
Friday Game Plan


Modeling
Object-oriented programming
Friday

Object Oriented Program
– System of objects that work together to
solve some problem.

Create model through iterative
refinement to reach an executable
program.
Friday


First identify the objects in the domain
that will be useful to us in solving the
problem.
Objects have two main parts:
– Properties: features that describe an
object
– Capabilities: actions an object can
perform
Friday




Establish our design first (use UML
class diagrams to help us)
Create source code (Java code)
Compile source code into byte code
Run byte code to execute program
Friday

We will be using a lot of objects, so
let’s start out with how to create one:
– new BouncingBall()


The expression above creates a
bouncing ball object.
Objects do not exist until an
expression like this is evaluated.
Friday


Since that is true, that means objects
do not exist until run time, because
the only time we can evaluate
expressions is when we are running a
program.
So what do we spend our time doing
when we write programs?
Friday

We define classes. Classes give the
formal definitions of what the object
will eventually be able to do.