WEEK 1

Introductions

·        Intro me

·        Intro you

      o       Name, program, favorite desert

o       Why are they here?

o       What do they hope to do?

o       Work experience?

Course

·        Importance of data structures

·        Material builds on previous material DO NOT FALL BEHIND

·        What we will cover

o       Through chapter 12

o       About a chapter a week

·        My expectations

o       On time to class

o       Written and programming HW

o       HW on time, may not be late

o       Average of all quizzes equals one test grade

o       Mid-term and final exams

o       Lecture and lab each time

·        Programming experience

o       Java, other?

o       Arrays, objects?

o       File I/O?

Break – get books

·        SDLC

o       Analysis, Specification, Design, Analysis of Solution, Implementation (code)

o       Test & debug, Maintenance & evolution, Obsolescence

o       Every author, teacher has a little different definition of SDLC, know the concepts

o       Analysis – covered in Systems Analysis & Design course

o       Specification

§         Formal structure

§         Name & description

§         Parameters

§         Preconditions

§         Returns (post conditions)

§         Throws – Appendix C

·        Throws usage

try

{

      <statements>;

}

catch (<type> e)

{

<actions>

<can use e.toString() >

}

o       Design (architecture)

§         Identify major modules (objects) and interfaces

§         Top-down

§         Pseudo code

§         Example: clean the house

o       Implementation

§         Use final variables and enums

·        Example: final double PI = 3.14159;

·        Never put in a literal number unless it is clearer and not going to change

In Class

            Do p. 16 Self-test

o       Run time analysis

§         Stair counting problem from the text

§         Describe O( ) analysis

§         The algorithm can be more important than the processor speed!

In Class

            Do p. 26, Self-test

o       Test & debug

§         Test for:

·        Proper action

·        Likely problem cases

·        Improper cases

·        Boundary conditions (explain what these are, importance)

§         Debugging

·        Don’t guess, understand

·        Use tools (breakpoints, trap, trace) (also print statements)

In Class

            Do p. 35 Self-test exercises

Introduce

            Netbeans

            Do simple application (temperature conversion?)

Homework

            Show how to print a screen.