CSC323 2010S Software Design

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:



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

OO Analysis, The Head-First Approach

The One-Button Problem, Revisited

Back to Gathering Requirements. On to Cancelled.

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

You may wish to validate this document's HTML ; Valid CSS! ; Creative Commons License

Samuel A. Rebelsky,

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 or send a letter to Creative Commons, 543 Howard Street, 5th Floor, San Francisco, California, 94105, USA.