|
Sidebar - Skyscraper and Firefox
|
SCJD Study Notes - Application Design
| A semi-formal description of what a user wants from a system and how they expect to interact with the system to bring about a specific result. Generally people; however, a user can also be another system or another piece of the same system. Sometimes referred to as scenarios.
|
| Class-Responsibility-Collaboration cards. Martin Fowler calls it "One of the most valuable techniques for learning OO" (UML Distilled p9)
|
| Two flavours: sequence and collaboration. Useful when trying to capture the behaviour of several objects within a single use case. Martin Fowler recommends using State diagrams to model the behaviour of one object across multiple use cases. (UML Distilled p78)
|
| Classes describe objects in the domain and the static relationships that exist between them. Detail the class data (attributes) and operations (behaviour).
|
| Patterns are example models of processes that crop up repeatedly in software development. For example, developers are often faced with problems that require moving through a list or collection. The Iterator pattern describes a standard technique for handling iterations.
|
On-line Analysis and Design Tutorials/Lectures
Free Modeling Software
- ArgoUML free case tool; part of the Tigris.org open-source platform.
- If you're using Linux or Sun Solaris, you can download a free copy of JVision for non-commercial use. (Sorry, if you're using Windows it will cost you.)
Miscellaneous
|