Based on UML, this book contains information on use cases, activity diagrams, state charts, and deployment diagrams.
This is not a reference book on what is UML, but a practical book on how to capture a software design using UML. The chapters are not disjoint, as a single example is used through the book to illustrate the interrelationship between the diagrams. The use cases are tied to activity diagrams, and are then tied to the state charts.
The fundamental idea that this book brings is a bottom-up approach to software 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 organization. This 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 white board in hopes that by constant discussion all aspects of the design will be uncovered. This book stresses that the act of design is just as important as the design artifact.
This is not a reference book on what is UML, but a practical book on how to capture a software design using UML. The chapters are not disjoint, as a single example is used through the book to illustrate the interrelationship between the diagrams. The use cases are tied to activity diagrams, and are then tied to the state charts.
The fundamental idea that this book brings is a bottom-up approach to software 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 organization. This 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 white board in hopes that by constant discussion all aspects of the design will be uncovered. This book stresses that the act of design is just as important as the design artifact.
