Ebook Use Case Modeling, by Kurt Bittner, Ian Spence
By conserving Use Case Modeling, By Kurt Bittner, Ian Spence in the gadget, the way you review will certainly also be much easier. Open it and start reading Use Case Modeling, By Kurt Bittner, Ian Spence, simple. This is reason why we recommend this Use Case Modeling, By Kurt Bittner, Ian Spence in soft file. It will not disturb your time to obtain the book. Additionally, the on the internet air conditioner will certainly likewise ease you to browse Use Case Modeling, By Kurt Bittner, Ian Spence it, also without going somewhere. If you have connection net in your office, house, or gizmo, you can download and install Use Case Modeling, By Kurt Bittner, Ian Spence it directly. You could not likewise wait to obtain the book Use Case Modeling, By Kurt Bittner, Ian Spence to send out by the seller in other days.
Use Case Modeling, by Kurt Bittner, Ian Spence
Ebook Use Case Modeling, by Kurt Bittner, Ian Spence
Find out the strategy of doing something from several resources. Among them is this publication entitle Use Case Modeling, By Kurt Bittner, Ian Spence It is an extremely well known book Use Case Modeling, By Kurt Bittner, Ian Spence that can be suggestion to review now. This recommended publication is one of the all great Use Case Modeling, By Kurt Bittner, Ian Spence collections that remain in this website. You will additionally find various other title and also styles from various authors to look here.
Reviewing behavior will certainly constantly lead people not to completely satisfied reading Use Case Modeling, By Kurt Bittner, Ian Spence, a book, 10 publication, hundreds e-books, as well as much more. One that will make them feel satisfied is completing reviewing this e-book Use Case Modeling, By Kurt Bittner, Ian Spence and also getting the message of the publications, then finding the other next publication to read. It proceeds even more as well as more. The time to finish reviewing an e-book Use Case Modeling, By Kurt Bittner, Ian Spence will be consistently various relying on spar time to invest; one instance is this Use Case Modeling, By Kurt Bittner, Ian Spence
Now, exactly how do you recognize where to purchase this e-book Use Case Modeling, By Kurt Bittner, Ian Spence Don't bother, now you could not go to the book establishment under the bright sunlight or night to look the e-book Use Case Modeling, By Kurt Bittner, Ian Spence We below always help you to find hundreds sort of book. One of them is this book qualified Use Case Modeling, By Kurt Bittner, Ian Spence You may visit the link page given in this set and after that opt for downloading and install. It will not take more times. Merely attach to your net accessibility and also you can access guide Use Case Modeling, By Kurt Bittner, Ian Spence on-line. Of program, after downloading Use Case Modeling, By Kurt Bittner, Ian Spence, you could not publish it.
You can conserve the soft file of this publication Use Case Modeling, By Kurt Bittner, Ian Spence It will certainly rely on your extra time and tasks to open as well as review this e-book Use Case Modeling, By Kurt Bittner, Ian Spence soft documents. So, you may not hesitate to bring this publication Use Case Modeling, By Kurt Bittner, Ian Spence anywhere you go. Just add this sot data to your gizmo or computer system disk to permit you check out each time and also all over you have time.
-- A ready reference for the use case practitioner.
-- Reviews the fundamentals of use cases, and then explores the details of writing better use cases.
-- Based on real-world issues, and how project teams overcame them.
Use cases are a simple, straightforward -- yet very powerful -- way to express the functional requirements (or behaviors) of a system. Use cases have gained widespread acceptance because they make requirements less ambiguous by specifying exactly when and under what conditions certain behaviors occur. As a result, those who effective employ use cases to model their systems can better deliver projects on time, within budget, and with fewer defects. However, use case modeling is not that easy; it is a practice that comes with characteristics that can impact a project. In this new book, the authors allow you to benefit from their considerable experience making use cases work well in a number of different environments. With the advice, tips, and tricks presented herein, the reader will be further along the path to understanding and exploiting the power of use cases, and ultimately constructing better applications. In writing this book, the authors have worked closely with use case founder Ivar Jacobson, and the book is unique in that it presents a Rational Software Corporation-centric examination of this topic.
- Sales Rank: #796831 in Books
- Published on: 2002-08-30
- Released on: 2002-08-20
- Original language: English
- Number of items: 1
- Dimensions: 9.00" h x .90" w x 7.60" l, 1.23 pounds
- Binding: Paperback
- 368 pages
From the Back Cover
Developers who effectively employ use cases deliver better applications--on time and under budget. The concept behind use cases is perhaps as old as software itself; they express the behavior of systems in terms of how users will ultimately interact with them. Despite this inherent simplicity, the use case approach is frequently misapplied, resulting in functional requirements that are confusing, cumbersome, or redundant.
In Use Case Modeling, experienced use case practitioners Kurt Bittner and Ian Spence share their tips and tricks for applying use cases in various environments. They delve into all aspects of use case modeling and management, demonstrating how development teams can capitalize on the approach's simplicity when modeling complex systems.
In this ready reference, readers will discover how to
- Introduce a development team to use cases and implement a use case approach
- Identify the key elements of a use case model, including actors; and the components of a use case, including basic flow, preconditions, post-conditions, sub-flows, and alternate flows
- Master the objectives and challenges of creating detailed descriptions of use cases
- Improve their descriptions' readability and consistency
- Prevent and remedy common problems arising from the misuse of include, extend, and generalization use case relationships.
- Organize and conduct a review of a use case model to realize the best possible approach
The book draws extensively on best practices developed at Rational Software Corporation, and presents real-life examples to illustrate the considerable power of use case modeling. As such, Use Case Modeling is sure to give development teams the tools they need to translate vision and creativity into systems that satisfy the most rigorous user demands.
0201709139B08062002
About the Author
The director for Requirements Management Solutions at Rational Software, Kurt Bittner served on the original Rational Unified Process development team. He has twenty years of experience in software development, including work in requirements capture, analysis, design, development, and project and product management.
A senior consultant at Rational Software, Ian Spence specializes in the adoption of the Rational Unified Process and the use case driven approach that it recommends. He has over eighteen years of experience in the software industry, covering the complete development lifecycle, including requirements capture, architecture, analysis, design, implementation, and project management.
0201709139AB08062002
Excerpt. © Reprinted by permission. All rights reserved.
Why Bother with Use Cases? WHAT ARE "USE CASES" ALL ABOUT?
In a world where it seems we already have too much to do, and too manythings to think about, it seems the last thing we need is something new thatwe have to learn. As Eric Sevareid observed, the chief cause of problems issolutions.
But use cases do solve a problem with requirements: with strict declarativerequirements it's hard to describe steps and sequences of events. To seewhy, let's consider a simple example:
Example
Some requirements that must be satisfied by an automated teller system:
The system shall allow customers to withdraw cash from their accounts. The system shall ensure that the customer's account is never overdrawn. If the customer attempts to overdraw the account, the system will allow the account to be overdrawn, up to a specified amount, for a transaction fee. If the customer is using an automated teller machine (ATM) that is owned by a financial institution other than the one to which the account belongs, an additional fee will be charged to the account. Simple enough, you say. Or is it?
In what order should these things be done? Does it matter? If the ATM is not one that is owned by the customer's financial institution, should the ATM usage fee be charged before or after checking for overdraft? If the customer's account balance is less than the ATM usage fee, charging the ATM usage fee before checking for overdraft will automatically result in an overdraft charge being applied, even if the customer decides to cancel the transaction. Is this the right behavior? With only declarative requirements, which is all that many projects have, it's impossible to say.
Use cases, stated simply, allow description of sequences of events that,taken together, lead to a system doing something useful. As simple as thissounds, this is important. When confronted only with a pile of requirements, it's often impossible to make sense of what the authors of the requirements really wanted the system to do. In the preceding example, use cases reduce theambiguity of the requirements by specifying exactly when and under whatconditions certain behavior occurs; as such, the sequence of the behaviors canbe regarded as a requirement. Use cases are particularly well suited to capturing these kind of requirements. Although this may sound simple, the fact is that conventional requirement capture approaches, with their emphasis ondeclarative requirements and "shall" statements, completely fail to capturethe dynamics of the system's behavior. Use cases are a simple yet powerfulway to express the behavior of the system in way that all stakeholders caneasily understand.
But, like anything, use cases come with their own problems, and as useful as they are, they can be misapplied. The result is something that is as bad, if not worse, than the original problem. Therein lies the central theme of this book--how to utilize use cases effectively without creating a greater problem than the one you started with.
WHO SHOULD BE INTERESTED IN USE CASES?
The short answer to this question is "just about everyone," or at least everyoneinvolved in some aspect of delivering a system that satisfies the needs ofthe customer. To be more specific about who should be interested in use cases,the following roles can benefit from the use-case technique of describing systembehavior:
- Customers, who need to be sure that the system that is getting built is the one that they want
- Managers, who need to have an overall understanding of what the system will do in order to effectively plan and monitor the project
- Analysts, who need to describe and document what the system is going to do
- Developers, who need to understand what the system needs to do in order to develop it
- Testers, who need to know what the system is supposed to do so that they can verify that it does it
- Technical writers, who need to know what the system is supposed to so that they can describe it
- User-experience designers, who need to understand the users' goals and how they will use the system to achieve these goals.
- And anyone else who wants to better understand what needs to be built before it is actually constructed
HOW TO READ THIS BOOK
This book is fundamentally about creating use-case models and, more importantly,about writing detailed descriptions of use cases. To remain focused onthis task, we have intentionally left out the parts of the project life cycle that use the use cases but are not directly involved in writing them. These areas include user-interface design, analysis, design, technical writing, testing, and project management. Other authors have covered a number of these areas adequately, and we felt that you, the reader, were best served if we focused narrowly on the use cases themselves. We hope you will agree.This book is intended to be a ready reference for the practitioner, the personwho is actually doing the work and grappling with the unique problemsof working with use cases. It can certainly be read cover to cover, but the realintent behind the book is to provide you with something that can continue toadd value after the first reading, providing you with a "mentor" at your fingertips. The topics presented in the book have arisen from working withcountless project teams who grappled with the same issues facing you.
The book is divided into two parts. In Part I, Getting Started with Use-Case Modeling, we introduce the basics concepts of use-case modeling thatyou will need to understand in order to be effective using use cases. We conclude Part I with a description of an excellent way to get started with usecases: with a workshop.
- The first chapter, A Brief Introduction to Use-Case Modeling, provides practical background for people who are unfamiliar with use cases, or for people who have read other books and articles and still find themselves wrestling with the basic ideas. The purpose of the chapter is to provide a brief overview of the use-case approach without getting into a lot of formal details.
- The second chapter, Fundamentals of Use-Case Modeling, presents the foundations underlying the use-case modeling technique. The concepts presented here will provide the basis for the subsequent chapters in the book.
- The third chapter, Establishing the Vision, provides the essential tools for determining the business problem to be solved, for identifying the stakeholders in the solution, and for deciding what the system should do for those stakeholders to solve the business problem. This information is essential if we are to define the right solution when we develop our use-case model.
- The fourth chapter, Finding Actors and Use Cases, describes the process and subtleties of identifying the key elements of the use-case model. The purpose of this content is to help you through the sometimes-confusing task of getting started by providing a sound understanding of the basic concepts of actors and use cases.
- The fifth chapter, Getting Started with a Use-Case Modeling Workshop, describes the practicalities of getting started using use cases, including how to run a use-case workshop and how to deal with the practical details of starting to work with use cases.
In Part II, Writing and Reviewing Use-Case Descriptions, we explore thefiner details of working with use cases, including the anatomy of a use case,how to write use-case descriptions (instead of the simple but incompletedescriptions presented in Part I), and what it means to work with use cases inpractice. In these chapters, we explore in-depth how to write detailed use-casedescriptions.
- The sixth chapter, The Life Cycle of a Use Case, describes the transitions that a use case undergoes as it evolves from concept to complete description. This chapter establishes context for the remaining chapters and places the content of Part I into a larger context.
- The seventh chapter, The Structure and Contents of a Use Case, describes the various constituent parts of a use case--the basic flow, preconditions, postconditions, and the alternate flows, as well as related topics.
- The eighth chapter, Writing Use-Case Descriptions: An Overview, describes the objectives and challenges related to writing detailed descriptions of use cases and presents strategies for successfully mastering this challenging task.
- The ninth chapter, Writing Use-Case Descriptions: Revisited, discusses the mechanics of how to go about writing use-case descriptions, how to handle details, and how to structure the descriptions for readability. This is done using an evolving example in which a variety of techniques are progressively and systematically applied to improve the quality of the use-case description.
- The tenth chapter, Here There Be Dragons, describes the problems that most teams encounter when using relationships between use cases (specifically the include, extend, and generalization relationships) and relationships between actors.
- The eleventh chapter, Reviewing Use Cases, describes how to organize and conduct reviews of the use-case model, including a summary of areas where particular focus is needed.
- The final chapter, Chapter 12, Wrapping Up, touches on a number of topics related to how use cases are used in the larger context of the project, bringing our journey into the world of use cases to a close. In doing so, we provide the< reader with a number of references to sources to consult for further information about how use cases are used in other disciplines.
ACKNOWLEDGMENTS
We have had the pleasure over the years to work with many colleagues andcustomers who have helped shape the views that are presented here. A fullenumeration of all of these people would be impossible, but we find ourselvesespecially indebted to a number of our colleagues for contributing to ourviews on use cases. We are in great debt to Ivar Jacobson, who originated theconcepts of use-case modeling and initially defined their role in the modernsoftware development process, for his support and encouragement on thisproject. We are also indebted to our colleague Dean Leffingwell for his workdefining the role of use cases and traditional requirements-managementapproaches. We would also like to thank Bryon Baker, Chris Littlejohns,Anthony Kesterton, Gary Evans, Laurent Mondamert, Peter Eeles, Brian Kerr,and Susan August for their insightful suggestions at various points in thelong evolution of this book. Special thanks go to Douglas Bush and Ida Audehfor their assistance in helping us to write clearly and concisely. We would alsolike to thank the many technical consultants at Rational whose experiencesand questions have helped to shape this book. Finally, we would like to thankthe customers with whom we and these consultants have worked, since theirexperiences and questions have ultimately made us realize that this book hasbeen sorely needed. To all these people goes a great share of the credit for this book; any flaws or shortcomings are exclusively our own.
Kurt Bittner and Ian Spence
April, 2002
0201709139P08062002
Most helpful customer reviews
2 of 2 people found the following review helpful.
Best Use Case format for your clients
By Jim Fuhring
Here is the scenario... you're a business analyst that is attempt to show business clients the value of writing use cases. Many books exist with various ways to format the use case. You take all those books and write the same use case in all the different formats. Guess which one the business looked at and understood? You got it. The really fine work of Bittner and Spence. If you use a table driven methodology, your clients won't be happy. The use case structure that is recommended in this book has been used in many projects where I currently work, and they have been very successful in forming a dialog with the clients as to how they need to the use the system and what true value they get out of it. The key part of this book is the concept of maturity of the use case. This is something that you can schedule in a project plan and demonstrate to the customers. Great job guys.
3 of 3 people found the following review helpful.
Very good introduction and reference to Use Case modeling
By L. Romero
I recently had to do the use case modeling for a new system and found this book. I also looked at a book by Alistar (I believe that's the name of the author) but it looked to overwhelming compared to this book. This book is easy to read and you can start creating your model right away and add more complexity as you read.
It includes partial examples of use cases for a system in the appendix but have full ones in their website.
One thing I wished they had gone deeper into is the use case 'extensions'. They do mention them but in a very limited way.
The appendix has a partial example of a use case model and states that the full example is online at [...] but it does not seem to be there, however.
0 of 0 people found the following review helpful.
Excellent book
By Sebastian Carneiro
This is the book I've looking for. If you need, like myself, to grasp a solid foundation about use cases, its nature, advantages, and to exploit its power to communicate and agree about the solution that the stakeholders and developers of an application need, this is the book for you.
See all 16 customer reviews...
Use Case Modeling, by Kurt Bittner, Ian Spence PDF
Use Case Modeling, by Kurt Bittner, Ian Spence EPub
Use Case Modeling, by Kurt Bittner, Ian Spence Doc
Use Case Modeling, by Kurt Bittner, Ian Spence iBooks
Use Case Modeling, by Kurt Bittner, Ian Spence rtf
Use Case Modeling, by Kurt Bittner, Ian Spence Mobipocket
Use Case Modeling, by Kurt Bittner, Ian Spence Kindle
Use Case Modeling, by Kurt Bittner, Ian Spence PDF
Use Case Modeling, by Kurt Bittner, Ian Spence PDF
Use Case Modeling, by Kurt Bittner, Ian Spence PDF
Use Case Modeling, by Kurt Bittner, Ian Spence PDF
