CSC323 2010S Software Design

Class 06: Gathering Requirements

Back to Object-Oriented Design and Analysis. On to Analysis.

This outline is also available in PDF.

Held: Thursday, February 11, 2010

Summary: We begin to consider ways in which programmers and clients discuss the components of a system, particularly through requirements and use cases.

Related Pages:



Requirements: The Basics

The big question: What is the software supposed to do?

Most frequently, we call the agreed-upon characteristics of the software the requirements.

Side notes:

Use Cases: A Technique for Exploring Requirements

Detour: Dog Doors and Other Issues from HFOOAD

Use Cases: An Exercise

Back to Object-Oriented Design and Analysis. On to Analysis.

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.