CSCI 200 S07 Introduction to Programming

REVERSE CHRONOLOGICAL ORDER WILL BE THE POSTING ORDER ON THIS PAGE

4-23-2006 Handed back quizzes and exercise reports -- the final exercise report will be due back on Friday and there will be a TEST which is Cumulative on the material we have covered this semester.  In class we looked at image filters and did an example, the grayscale filter, by modifying the threshold filter in ImageViewer 1.0 -- in actually adding a grayscale filter you will want to add a menu item to the Filter Menu.  We looked briefly at ImageViewer 2.0 which should be your baseline for your Filter Assignment.  Your Filters should be put in a clearly marked folder on your J: Drive and will be collected and graded next Monday.

4-20-2007 Today we are looking at the Image Viewer -- first version and just introduced the concept of Layout Managers.  Next week we'll go into that material further.  We also had a QUIZ and the Exercise Report for Chapters 9 and 10 was collected.  Next week the Exercise report will be on Chapter 11 and the Image Viewer Filters Assignment will be due on Friday and there will be a TEST on Friday that will be Comprehensive.

4-16-2007 Looks a little more at Foxes and Rabbits.  In particular talked about Abstract Classes (contrasted with Concrete Classes) and Interfaces which are just a set of abstract methods that a class is expected to IMPLEMENT.  Interfaces allow a class to have some of the attributes achieved with multiple inheritance in C++.  Handed back the first set of Exercise Reports using 5 point scoring which translates to a grade using the rubric: GRADE = 10*SCORE + 45.

4-13-2007 LOOKING AHEAD: we're going to be doing chapter 10 and chapter 11 and if possible a little more material.  There will be a quiz next Friday April 20 on Chapters 8, 9, and 10 and your next Exercise report is due then.  Then there will be a TEST on April 27th and April 30th will be FINAL GAME DAY.  Try to enhance the game or create a new one.  The Game should illustrate what you have learned.  Try to extend it so that something happens.  For example you could have lectures going on in the rooms of the university and have the player listen and ask or answer questions, or you could have the game be in a Casino and having CRAPS as one of the game and each room be a place where a different game is played, like Black Jack, Poker (might be pretty tricky to program that), etc.  Think of something clever and make it work!  Doughnuts will be provided by the management! (ME)

4-13-2007 FORMAT OF YOUR WEEKLY REPORT -- This report should CONVINCE ME YOU ARE WORKING HARD TO LEARN THE MATERIAL.  Your weekly report needs 4 SECTIONS: 1) Name Block (good idea to put a header with your name too so you won't have to staple the report together), 2) Exercise Report by exercise -- very brief summary, any difficulty, resolution, 3) Summary of Progress -- only need one of these at the end to give an overall assessment of your own progress.  It should answer the question: How are you doing?  What are you doing to do better?  What problems are you having.  Finally 4) the Appendices and Evidences which is any material that convinces me you are making serious progress towards your goal.

 WEEKLY REPORT FORMAT:  Report must be typed and printed.  I recommend you use Microsoft Word, but other professional looking printouts will be acceptable.  The report must be turned in as hardcopy.
1. Name/ Date/ and Subject Block -- in upper left hand corner, for example:
Name: Ray Schneider
Date: April 13, 2007
Subject: Exercises and Topics in Chapter 8

2. The Second section is the Exercise Report -- it should be listed by Exercise and for each exercise done: a) Provide a brief summary of what you did, b) if you had difficulty, what you did to overcome the difficulty, c) if you failed to overcome the difficulty what you think kept you from overcoming the difficulty.

3. Summary of Progress: Summarize your understanding of the chapter and what questions remain.  What did you think was particularly difficult?  What do you think needs further clarification?

4. APPENDICIES and EVIDENCES: The point is to convince me that you are making progress.  Incorporate in this section any hardcopy of code that you wrote or work you are fairly proud of and want to call my attention to.

4-2-2007 Wednesday is GAME DAY -- when the students will present their First Cut at a World-of-Zuul type of adventure game.

3-30-2007 Next Wednesday is GAME DAY!  You should have a working World of Zuul type of Game to show off to the class and talk about your enhancements.

3-27-2007 (msg sent 3/26 at 4:21 p.m.) Well in the light of the sad state in which I find some of the J: drive folders I have decided to be magnanimous -- merciful and generous and all those kinds of things and let you miscreants turn in your CRAPS program by Thursday at 3 P.M. -- so the new SnapShot and final chance will occur on Thursday.  So get you CRAPS game finished and annotated and in your J:Drive myGames or myPrograms or CRAPS folder by Thursday at 3 p.m.

3-26-2007 The final snapshot of the CRAPS Game will be taken today after 3 p.m. your game should be functional and it should be fully documented using JavaDoc.  Your next project will be to modify the World of Zuul to create you own game concept.

3-19-2007 Today we looked a little more closely at testing in Chapter 6.  In particular we used the JUnit features of BlueJ to generate additional tests in a test harness using the Diary examples.  The CRAPS Game is due for a Folder SNAPSHOT at 3 P.M. Today so be sure you have your program there and ready.

3-12-2007 Handed back the tests.  The results were pretty poor on the whole the average was 50.55% and since the test was not all that difficult I can only infer that you are not studying very hard or doing the exercise assignments.  We reviewed the test in class and went through a Pseudocode example of the Dice Game.  The Dice Game as a program was assigned and is due to be completed next Monday (3/19)

3-2-2007 Test today: 3 pages. Time to complete based on student completion times is plotted at the right.  The test was open book, open notes, and open computers.

 

2-28-2007 Test on Friday.  It will be on Chapters 1 through 4 and will be Open Book.  See today's lecture which summarizes the kinds of questions that will be on the test.  The Quizzes you've taken should be some indication however.  You mid-term grade will be composed of a Logs Grade, a Quizzes Grade, and a Test Grade with adjustments for Attendance and Participation.  The Test will be weighted the heaviest, the Quizzes and Logs will be weighted in that relative order.  I will probably drop the worst quiz grade, so if you missed a quiz that will be the one that will be dropped.  Normally quizzes cannot be made up.  Today in class we talked about Object-Oriented Programming being rather like circuit design in that because of the large sets of components available you could select your components, read the documentation on how to use them and then build your programs out of proven components.  We did a small exercise with the Random Class and generated a random-number generator and then modified the code to add the ability to mimic a dice roll.  Then we reviewed briefly what we had covered in the previous four chapters of the book.

2-26-2007 We make a little Starship program in class today with a couple of constructors and some getters and setters.  Don't forget there will be a test on Friday on Chapters 1 through 4.  This test, plus your quizzes and logs will form the basis for your Mid-Term Grade.

2-23-2007 We had a QUIZ and four students were absent.  The biggest problem on the class is that students did not seem to understand the difference between Constructors and Accessors.  The questions on the Debugger were easily answered by looking them up in the book, but only a couple of students figured out that to create a Starship and designate the number of DilithiumCrystals would take a header like: public Starship(int numDilithiumCrystals) and that took most people down into the second category.  Average was 15 or 68.2% but since it was open book I think that was pretty poor on balance.

NEXT WEEK WE WILL HAVE A TEST ON THE FIRST FOUR CHAPTERS.  On Monday We Will Write a little Program.

2-20-2007 Yesterday we started into Chapter 3 and also took a quick look at the BlueJ debugger.

2-16-2006  Today we did a little Java from scratch outside the BlueJ environment.  It took a little longer than I expected so we didn't get into Chapter 3 the way I had envisioned.  Get cracking on Chapter 3 exercises.  You now know how to create, at least in principle, a stand alone Java application.  The chief class has to have a static main() method which runs at start up.  Appendix E offers more information about stand alone applications.

2-13-2007 Well we finished Chapter 2 and don't seem the worse for wear.  The results from the second Quiz are much better than the results of the first.  Too many students don't have books and too many don't have Java and BlueJ running on their personal computers.  It is essential to program and do the exercises to do well in the class so I urge you to do what is necessary.

KEY TO QUIZ:  Method ISA

// METHOD HEADER
 <access modifier> <return type> <method name> "(" [<parameter list> optional]")"
// METHOD BODY
"{" //to open body
       // code in body
"}" //to close body

With an open book quiz there is no reason why everyone didn't get a perfect score.

2-7-2007 SNOW DAY due to late opening of the college so Chapter 2 will end on Monday -- and typical chapter coverage will be from Wednesday to Monday with a quiz on Monday until we slip another day due to snow of get back in sync some other way.  Keep working on your logs and Journals.

2-5-2007 Reviewed Chapter 1 Quiz results with students and pointed out how important studying and taking notes is to success by handing out the levels of study sheet.  Reviews FIELDS, CONSTRUCTORS, and METHODS and we did exercises 2.6 to 2.20 in class for the most part. QUIZZES will be weekly.  I also mentioned that I take a snapshot of the J:Drive logs every Friday.

2-2-2007 Reviewed Chapter 1, talked about Grading with three primary grading elements: Logs, Quizzes, and Tests.  Gave out a quick quiz intended to go only about ten minutes, however since some students arrived late I decided to let the quiz go longer and it went about twenty minutes.  The results are on the right -- 13 scoring 7 or less of 28 points.  This sends me the message that you are not doing any work outside of class since the quiz was just the exercises at the end of the chapter which were assigned work.  We will review the results on Monday.  You cannot learn programming if you don't work at it.  It's simply impossible.  Seven people in the class did better.  There was a reasonably general sentiment that we are going too fact.  However it is important to not that we have at least 13 chapters to cover and there is no time to smell the roses.  You should be working a minimum of six hours a week outside of class and preferably nine.  If you are not doing the work and not asking questions in class then the reason you are doing poorly is that you are not working to do better.  You get out of something what you put into it.  Nothing in, then nothing out!
1-29-2007 Chapter 1 -- we covered Classes/Objects Object STATE, methods and methods with parameters and progressed to exercise 1.9.  We also introduced the concept of logging your work.  I used Notepad to create a log of the work I was doing in the front of the class to illustrate the process to the students.  We concluded the class by manual creating shapes in the Workbench and moving them about to form the picture of a house.  The assignment is to continue through the chapter doing examples.

 

1-26-2007 Introductory Class -- the class went fairly well except that some of the students had difficulty running the Shapes class in BlueJ due apparently to permissions problems.  I'm not sure what the problem is so I put in a help ticket to IT to query what the problem might be.  We will confirm on Monday if the problem still persists.  I was able to run the Shapes class from my office computer in the student's directory, but that may be misleading.