Class 07: Analysis

Back to Gathering Requirements. On to Cancelled.

This outline is also available in PDF.

Held: Tuesday, February 16, 2010

Summary: We consider the basic tools of object-oriented analysis.

Related Pages:

EBoard.

Notes:

Surprise! It's bad writing day in CSC 323. The primary question: How do you learn from things that don't have a clear point?
EC for CS Table Friday.
EC for Rosenfield Symposium this week.
Readings for next class: HFOOAD 5 and BC 31.

Overview:

BC 30: When A Button Is All That Connects You To The World.
Object-Oriented Analysis, The Head-First Approach.
Putting The Two Together.

Dealing with Readings

Part of the growing process of being a computer scientist is learning how to deal with materials of varying quality and depth.

What do you do when assigned a reading that you find problematic? (For example, it may be obvious, it may be too dense, or it may just be poorly written.)

Snark doesn't cut it.

In every case, it is still your responsibility to do your best to extract something useful from the reading.

For most readings in CS, you should be able to find a bit of code or a bit of design to understand and critique.

For every reading, you should be able to find a main point. (It may be hidden, but we have to assume that if it's published, it has a point.)

Beautiful Code 30: When a Button Is All That Connects You to the World

Incidentally the Beautiful Code reading for today cites wikipedia as one of its sources. Apparently what is not so acceptable for high school history classes is acceptable for CS academia. Why might the cases be different?

What makes the code beautiful?
What lessons can you derive from this chapter?

Your questions ....

OO Analysis, The Head-First Approach

What did you see as the main points of the chapter?
What advantages/disadvantages would you see to building a DogInfo object to store the list of barks?

The One-Button Problem, Revisited

So, let's consider how we might use what we know of OO analysis so far to study the one button problem.

Back to Gathering Requirements. On to Cancelled.

[Skip to Body]
Primary: [Front Door] [Schedule] - [Academic Honesty] [Instructions]
Current: [Outline] [EBoard] [Reading] - [Assignment]
Groupings: [EBoards] [Examples] [Handouts] [Outlines] [Readings]
Related Courses: [CSC223 2007F (Davis)] [CSC223 2004F (Rebelsky)] Misc: [SamR]

Disclaimer: I usually create these pages on the fly, which means that I rarely proofread them and they may contain bad grammar and incorrect details. It also means that I tend to update them regularly (see the history for more details). Feel free to contact me with any suggestions for changes.

This document was generated by Siteweaver on Tue May 11 12:40:51 2010.
The source to the document was last modified on Mon Jan 25 20:52:44 2010.
This document may be found at http://www.cs.grinnell.edu/~rebelsky/Courses/CSC323/2010S/Outlines/outline.07.html.

You may wish to validate this document's HTML ; ;

Samuel A. Rebelsky, rebelsky@grinnell.edu

Copyright © 2010 Samuel A. Rebelsky. This work is licensed under a Creative Commons Attribution-NonCommercial 2.5 License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc/2.5/ or send a letter to Creative Commons, 543 Howard Street, 5th Floor, San Francisco, California, 94105, USA.