Software Design Specifications with UML

Michael W. Bigrigg
Copyright 2004-2007



Table of Contents
Introduction
Use Cases : Actors
Use Cases : Goals
Use Cases : Scenarios
Activity Diagrams Overview
Activity Diagarams Part 1
Activity Diagarams Part 2
State Charts Overview
State Charts Part 1
State Charts Part 2
Deployment Diagarams : Components
Deployment Diagarams : Nodes
Deployment Diagrams : Communication



The fundamental idea that this book brings is a bottom-up approach to design. Rather than trying to come up with a big picture and then decomposing it into its individual pieces, this book advocates a recursive style of decomposition then organizationThis book will also stress a method of design. Too often we lock ourselves in a meeting room for a period of time with a blank whiteboard in hopes that by constant discussion all intracasies of the design will be uncovered. This book stresses that the act of design is just as important as the design artifact.

 

Acknowledgements

 

First I would like to thank Eswarian Subhrahmanian for our conversations about design. He was the one who introduced me to the idea of a bottom-up approach to design. It made teaching design, especially object-oriented software design, much more straightforwardI would also like to thank all the students that provided to me many of the insights in how they understood design. They were the ones that asked for a soup-to-nuts explaination of one single problem.