Synopsis Applied Use Case Driven Object Modeling with UML: An Annotated e-Commerce Example provides a practical, hands-on guide to putting use case methods to work in real-world situations. This companion workbook to Use Case Driven Object Modeling with UML bridges the gap between the theory presented in the authors' first book, and the practical issues involved in the development of an internet/e-commerce application. Uniquely conceived as a workbook, featuring an e-commerce system for an on-line bookstore as a running example, the book dissects its design in detail, demonstrates the most common design mistakes, and reveals the correct solutions. The hands-on exercises give you the opportunity to detect, identify, and correct critical errors on your own, before reviewing the solutions provided in the book. The workbook is structured around the proven ICONIX Process, a streamlined approach to UML modeling designed to avoid analysis paralysis without skipping analysis and design. It presents the four key phases of this minimalist approach to use case driven design: domain modeling; use case modeling; robustness analysis; and sequence diagramming.For each of these topics, the book provides an overview, detailed discussion, top 10 mistakes, and a set of exercises for honing object modeling and design skills.Another unique aspect of this book is the three chapters on reviews. The authors devote a chapter each to requirements review; preliminary design review; and critical design review. This focus on "designing quality in" by teaching how to review UML models fills a major gap in the published literature. The book shows you, by example, how to avoid more than 70 specific design errors as shown in the "Top 10" error lists on the inside covers and within each chapter. With the information, examples, and exercises in this book, you will develop the knowledge and skills you need to apply use case modeling more effectively to your next application. 0201432897B04302001 From the Back Cover Applied Use Case Driven Object Modeling with UML: An Annotated e-Commerce Example provides a practical, hands-on guide to putting use case methods to work in real-world situations. This companion workbook to Use Case Driven Object Modeling with UML bridges the gap between the theory presented in the authors' first book, and the practical issues involved in the development of an internet/e-commerce application. Uniquely conceived as a workbook, featuring an e-commerce system for an on-line bookstore as a running example, the book dissects its design in detail, demonstrates the most common design mistakes, and reveals the correct solutions. The hands-on exercises give you the opportunity to detect, identify, and correct critical errors on your own, before reviewing the solutions provided in the book. The workbook is structured around the proven ICONIX Process, a streamlined approach to UML modeling designed to avoid analysis paralysis without skipping analysis and design. It presents the four key phases of this minimalist approach to use case driven design: domain modeling; use case modeling; robustness analysis; and sequence diagramming. For each of these topics, the book provides an overview, detailed discussion, top 10 mistakes, and a set of exercises for honing object modeling and design skills. Another unique aspect of this book is the three chapters on reviews. The authors devote a chapter each to requirements review; preliminary design review; and critical design review. This focus on "designing quality in" by teaching how to review UML models fills a major gap in the published literature. The book shows you, by example, how to avoid more than 70 specific design errors as shown in the "Top 10" error lists on the inside covers and within each chapter. With the information, examples, and exercises in this book, you will develop the knowledge and skills you need to apply use case modeling more effectively to your next application. 0201432897B04302001 See all Product description
B**J
Warning: This is not standard UML or Use Cases as usually practiced
I have had this book since it was written (1999). Readers/buyers should be aware that this book is based around the version of a proprietary method called Iconix at the time; nothing wrong with that except UML has moved on since then.What is wrong is its demonstration and use of Use Cases. It does things with use cases that are generally seen (by regular users of UML) as bad practice such as; showing dependency/sequencing between use cases on use case diagrams. Readers should beware of adopting styles like this in standard UML projects as it is off standard as far as conventional UML is concerned. If anything it is closer to what I've seen defined as OML - Open Modelling Language, a mutant offspring from UML at best that does things that its parent decided was not good practice.You've been warned, a fair read but not how most people do it and may be non-standard in most organisations.
M**N
Good focal point for OO-analysis and -design.
If you, like me, understand OOP and UML well, but need good guidance on the ICONIX-approach to analysis and design, then I think this book is for you. If you, like me, have a lot of "free dangling" knowledge around process, analysis and design and need to get some focus, then this book is definitely for you. The book is without a doubt authoritative.The book is short, practical, concise and well-structured. Apart from first few chapters where the author waffles on a bit and beats his own drum, the book is all meat and no fat.After having read it, I was able to apply the approach straight to one of the projects I am currently leading, and I felt far better equipped to read other books on OO-analysis and -design.
C**M
A practical guide through the maze of OO theory.
If you want to try Use Cases & UML but you're not sure where or how to begin then this book could help kickstart your efforts. The book's approach is a good fit for Corporate IT shops - particularly if you regularly have aggressive deadlines to meet and methodologies are expected to earn their keep within weeks ! A cautionary note: identifying generalisation relationships starts very early in the process i.e. before object behaviour is clearly understood. Looking for inheritance too early can cause "analysis paralysis". All in all, an excellent way to get started with OO analysis and design - the purists and theorists won't like it but it's not aimed at them anyway.
C**N
Interesting but long winded
The book does expand my knowledge on the subject but has the tendency to drivel on and on for my liking and does get very boring. Not a very technical textbook.
Trustpilot
1 day ago
1 week ago
