(Latest Revision: 09/11/2003)
Week 02 Notes for CS 2500, Section 001 -- Fall 2004
CS 2500, Section 001, Tuesday, Septemember 07, 2004
Notes for Lab Day
- Meet first day in lab to do hello world assignment
- Take Roll.
- Announcement(s)
- Anyone who still needs to add CS 2500 should contact me
- A level-two version of program #1 is due Tuesday, September 14
Get started on this soon, while the Hello
World! assignment is still fresh in your mind.
- Locate where to get Hello World! handouts and Jove
handouts online:
- check out the links from the Hello World! handout.
CS 2500 Notes for Rest of Week
- Take Roll.
- Pass out any left-over accounts.
- Discuss with class what they should have turned in
for the "Hello World" assignment.
- Look at file that tells results of lab 01 (Hello World!)
- In Carrano we are reading chapter one (program design) and
chapter two (recursion).
- In Anderson we are reading chapters 1-3,5 (intro to Unix).
- Final due date for Programming assignment #1 is Thursday, September 23
- Perhaps finish up from last week or do some lecture topics from below.
- Discuss programming assignment #1.
- What is the assignment?
- Design considerations -- how does the top-down design work?
- Information to put in function headers
- What do you have to turn in on Tuesday, Sept 14?
- What does a level-two program look like?
- What should this level-two program look like?
- The level-two program needs documentation for the main program,
for the functions called by the main program (they are called
level-two functions), and for the functions called by
the level-two functions (they are called level-three
functions.)
- The documentation for every function must tell what the
function will do when it is completed. (Normally you
don't write documentation to tell what a stub function does.)
- In the level-two program you need to finish the code for the
main function and all the level-two functions.
- In the level-two program you need to have stubs for all the
level-three functions.
- Look at "What you have to turn in" for Tuesday on the assignment
sheet.
- Discuss program testing strategies and requirements.
- Data Coverage -- Black Box Testing
- Average inputs
- inputs near and on boundaries
- Code Coverage -- White/Clear Box Testing
- Statement Coverage
- Path Coverage
- Show example of reading e-mail on the Sun Ultra's.
- The compiler command option for naming the executable
file:
(g++ -o letters letters.cpp)
- Discuss compiling/debugging with jove
- How to execute the compiler "inside" jove: (C-u, C-x,
C-e)
- C-x 1 "unsplits" the screen.
- How to break out of jove to a sub-shell whilst "saving
your place": (M-s)
- Testing the program while in the sub-shell.
- How to break out of the sub-shell and return to "your
place" in jove: (exit)