| |||||||||||||||
|
Amazon.co.uk Trade-In Store
Did you know you can trade in your old books for an Amazon.co.uk Gift Card to spend on the things you want? Visit the Amazon.co.uk Trade-In Store for more details. |
Product details
|
Use cases are increasingly popular, but many large organizations find it difficult to develop the complex use case models they need -- and poorly developed models fail to achieve their goals. In Advanced Use Case Modeling, Volume I, two leading use case experts present proven techniques for applying use cases in even the most challenging environments. The book begins with a clear, rigorous, example-driven explanation of the fundamental concepts of use cases. Next, the authors introduce repeatable processes for developing use cases that successfully drive systems design. Readers will learn the traps and pitfalls of use case design and how to avoid them; then discover new techniques for addressing the most important use case modeling issues -- several of which have never before been discussed in a book. All descriptions and examples reflect the latest UML notation. For all object-oriented designers, analysts, and software engineers -- and for all managers and users involved in object-oriented development projects.
"This book isn't just another introduction to use cases. The authors have used their wealth of experience to produce an excellent and insightful collection of detailed examples, explanations, and advice on how to work with use cases."
—Maria EricssonThe toughest challenge in building a software system that meets the needs of your audience lies in clearly understanding the problems that the system must solve. Advanced Use Case Modeling presents a framework for discovering, identifying, and modeling the problem that the software system will ultimately solve.
Software developers often employ use cases to specify what should be performed by the system they're constructing. Although use case-driven analysis, design, and testing of software systems has become increasingly popular, little has been written on the role of use cases in the complete software cycle. This book fills that need by describing how to create use case models for complex software development projects, using practical examples to explain conceptual information.
The authors extend the work of software visionary Ivar Jacobson, using the Unified Modeling Language (UML) as the notation to describe the book's models. Aimed primarily at software professionals, Advanced Use Case Modeling also includes information that relates use case technique to business processes.
This book presents a process for creating and maintaining use case models in a framework that can be fully customized for your organization. The authors, pioneers in the application of use cases in software development, bring their extensive experience to cover topics such as:
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organise and find favourite items. |
The authors take us beyond how to draw diagrams and get to grips with myriad issues of description in documentation in the project lifecycle. The authors' approach of questioning all aspects of the use case model is vital to their success. The chapter on testing, though only an overview, provides enough information to turn use cases into more than a trendy requirements tool.
Throughout there are excellent sidebars on issues in use case modelling. The authors offer both sides of the argument and then plump for their preference.
It is hard to find fault with this book.
The chapters pertaining to relating the Use Cases to other artifacts - such as test cases, the User Interface, and the Object Model - offer very practical and sound advice. You can tell that the authors have actually done it before and are speaking from experience and lessons learned.
The chapter explaining Extend Relationships offered the clearest and most complete description of the Extend Relationship that I have encountered.
All of the writing is very approachable and the examples sprinkled throughout the book and in the Appendixes are very helpful.
Each step of the design process is explained thoroughly, and several alternative procedures are presented. Also, the appendices are valuable references of themselves. They contain a Use Case Development Review Checklist and a complete Development Case, which outlines each major step on the use case modeled development cycle.
The authors have also done an excellent job in bringing together information from outside sources to compile their work. Rather than preaching a specific format or model, the reader is presented with many different customizable options for applying the theories in the book. The carefully cited sources also give excellent direction for further reading.
I was disappointed to find a flaw with the printing of the book. In my copy the pages containing the table of contents were out of order. However, I found that I was more disappointed because a potential reader might skip this book on the shelf just because of a printing mishap. This information within is too valuable to miss.
A real danger with theory books is the potential to either underestimate the reader or talk over the reader's head. This book walks that fine line with ease. I felt that the ideas and terms were presented in a logical and clear manner. It is a valued reference for my work.
My first books on use cases focused more on UML rather than use cases. I did not give a hoot on use cases, because they look so simple on paper (and that's why I didn't buy a book specifically on use cases!) But as I grew as a developer, I began to believe that use case modelling if done well can significantly reduce development effort and bring about quality solutions. Use cases are the foundation to the understanding of the system that you are trying to develop. Use cases deserve serious attention.
The main problem with use cases is that you either don't know how to start or when to stop. This book tells you both. It tells you how to develop your use case model systematically from scratch and how to make provisions so that your use case model can grow. IMO, that's the main draw for this book.
The authors also give good insights on the possible approaches the reader can take to expand his/her use case model iteratively. It cautions the modeller to keep a balanced model so that stakeholders can understand, rather than one that specifies everything but gets bogged down by the details.
Semantics, you can get it elsewhere, but this book discusses it pretty well too. The examples are clear and relevant.
All in all, Frank and Granville did an excellent job covering the topic.
|