Writing use cases as a means of capturing the behavioral requirements of software systems and business processes is a practice that is quickly gaining popularity. Use cases provide a beneficial means of project planning because they clearly show how people will ultimately use the system being designed. On the surface, use cases appear to be a straightforward and simple concept. Faced with the task of writing a set of use cases, however, practitioners must ask: "How exactly am I supposed to write use cases?" Because use cases are essentially prose essays, this question is not easily answered, and as a result, the task can become formidable. In Writing Effective Use Cases, object technology expert Alistair Cockburn presents an up-to-date, practical guide to use case writing. The author borrows from his extensive experience in this realm, and expands on the classic treatments of use cases to provide software developers with a "nuts-and-bolts" tutorial for writing use cases. The book thoroughly covers introductory, intermediate, and advanced concepts, and is, therefore, appropriate for all knowledge levels. Illustrative writing examples of both good and bad use cases reinforce the author's instructions. In addition, the book contains helpful learning exercises--with answers--to illuminate the most important points. Highlights of the book include: A thorough discussion of the key elements of use cases--actors, stakeholders, design scope, scenarios, and more A use case style guide with action steps and suggested formats An extensive list of time-saving use case writing tips A helpful presentation of use case templates, with commentary on when and where they should be employed A proven methodology for taking advantage of use cases With this book as your guide, you will learn the essential elements of use case writing, improve your use case writing skills, and be well on your way to employing use cases effectively for your next development project.
Any system, including a business, that offers a set of services to outside actors while protecting the interests of the other stakeholders can be described with use cases. The readability of textual use cases is particularly helpful in ...
Author: Alistair Cockburn
Publisher: Addison-Wesley Professional
Provides 31 development and structural patterns for software developers to refer to as examples of well-written use cases that help model software requirements. The development patterns describe the characteristics of good writing practices and project organization, while the structural patterns identify the basic components of use cases and how they should be organized. Annotation copyrighted by Book News, Inc., Portland, OR
Writing Effective Use Cases is a technique guide , describing the nuts and bolts of use case writing . Although you can use the techniques on almost any project , the templates and writing standards must be selected according to the ...
Author: Steve Adolph
Publisher: Addison-Wesley Professional
Diagramming and process are important topics in today’s software development world, as the UML diagramming language has come to be almost universally accepted. Yet process is necessary; by themselves, diagrams are of little use. Use Case Driven Object Modeling with UML - Theory and Practice combines the notation of UML with a lightweight but effective process - the ICONIX process - for designing and developing software systems. ICONIX has developed a growing following over the years. Sitting between the free-for-all of Extreme Programming and overly rigid processes such as RUP, ICONIX offers just enough structure to be successful.
Synergy between use case modeling and aspect-oriented programming (AOP) is the topic of Ivar Jacobson's book, ... ghastly (in our opinion) use case template from renowned guru Alistair Cockburn's book Writing Effective Use Cases:4 4.
Author: Don Rosenberg
Extending the scenario method beyond interface design, this important book shows developers how to design more effective systems by soliciting, analyzing, and elaborating stories from end-users Contributions from leading industry consultants and opinion-makers present a range of scenario techniques, from the light, sketchy, and agile to the careful and systematic Includes real-world case studies from Philips, DaimlerChrysler, and Nokia, and covers systems ranging from custom software to embedded hardware-software systems
Use Cases should always be checked and corrected after they have been written, • Each guideline has a specific impact on Use ... Cockburn, A., Writing Effective Use Cases, Addison-Wesley, 2001. scenarios, IEEE Transactions on Software ...
Author: Ian F. Alexander
Publisher: John Wiley & Sons
Highlights of the book include: A thorough discussion of the key elements of use cases--actors, stakeholders, design scope, scenarios, and more A use case style guide with action steps and suggested formats An extensive list of time-saving ...
Author: Alistair Cockburn
This book constitutes the refereed proceedings of the 15th European Conference on Object-Oriented Programming, ECOOP 2001, held in Budapest, Hungary, in June 2001. The 18 revised full papers presented together with one invited paper were carefully reviewed and selected from 108 submissions. The book is organized in topical sections on sharing and encapsulation, type inference and static analysis, language design, implementation techniques, reflection and concurrency, and testing and design.
Cockburn, A. Writing Effective Use Cases. ... Schneider, G. & Winters, J. Applying Use Cases – A Practical Guide. ... Regnell, B., Andersson, M. & Bergstrand, J. A Hierarchical Use Case Model with Graphical Representation.
Author: Jorgen Lindskov Knudsen
Beginning Database Design, Second Edition provides short, easy-to-read explanations of how to get database design right the first time. This book offers numerous examples to help you avoid the many pitfalls that entrap new and not-so-new database designers. Through the help of use cases and class diagrams modeled in the UML, you’ll learn to discover and represent the details and scope of any design problem you choose to attack. Database design is not an exact science. Many are surprised to find that problems with their databases are caused by poor design rather than by difficulties in using the database management software. Beginning Database Design, Second Edition helps you ask and answer important questions about your data so you can understand the problem you are trying to solve and create a pragmatic design capturing the essentials while leaving the door open for refinements and extension at a later stage. Solid database design principles and examples help demonstrate the consequences of simplifications and pragmatic decisions. The rationale is to try to keep a design simple, but allow room for development as situations change or resources permit. Provides solid design principles by which to avoid pitfalls and support changing needs Includes numerous examples of good and bad design decisions and their consequences Shows a modern method for documenting design using the Unified Modeling Language
Most texts on systems analysis include discussions about use cases. (Alistair Cockburn's book Writing Effective Use Cases3 is a particularly readable and pragmatic account.) Use cases can be at many different levels, from high–level ...
Author: Clare Churcher
Practical SharePoint 2013 Governance is the first book to offer practical and action-focused SharePoint governance guidance based on consulting experiences with real organizations in the field. It provides the quintessential governance reference guide for SharePoint consultants, administrators, architects, and anyone else looking for actual hands-on governance guidance. This book goes beyond filling in a governance document template and focuses entirely on actions to take and behaviors to adopt for addressing real-world governance challenges. Walks you through how to define what SharePoint offers and who is involved Offers key governance strategies for you to adopt or advise to your customers Provides real-world examples that apply each governance concept to an actual scenario What you’ll learn Define a scope to offer SharePoint as a service to an organization Specify roles and responsibilities involved in a SharePoint service Envision and strategize a SharePoint roadmap Plan for growing and upgrading a SharePoint environment Measure and report on performance metrics Set boundaries for development standards and testing processes Who this book is for Practical SharePoint 2013 Governance is for SharePoint consultants,administrators, architects, and anyone else looking for actual hands-on governance guidance. It is an excellent choice for people who like action-focused concepts or who want to go beyond documentation and theory. This book is a fantastic choice for anyone looking for agile ideas to put into practice without necessarily embarking on a lengthy governance exercise upfront. Table of ContentsPart I: Orientating SharePoint Governance 1. Understanding SharePoint Governance Part II: Defining the SharePoint Service 2. Defining Your SharePoint Service and Service Tiers 3. Determining Your SharePoint Features and Functionality 4. Establishing Your Team's Roles and Responsibilities 5. Shaping Your User Readiness and Training 6. Measuring and Reporting on Your SharePoint Service Performance Part III: Expanding the SharePoint Service 7. Creating Your SharePoint Roadmap 8. Promoting a Feedback Process 9. Managing Your SharePoint Demand Funnel 10. Growing Your SharePoint Service 11. Preparing for SharePoint Upgrades and Patches Part IV: Customizing the SharePoint Service 12. Committing Sponsorship and Ownership of Customizations 13. Facilitating and Isolating End-User Customizations 14. Designing Your Development Standards and Testing Processes 15. Framing Your Information Architecture and UI Standards 16. Coordinating Your Code Promotion and Release Processes 17. Rapid Concepts
Note One of the best books I have read on how to write effective use cases is Alistair Cockburn's book, Writing Effective Use Cases, ... I have read this book a number of times, and each time I improve my process for writing use cases.
Author: Steve Goodyear
“Agile Software Development is a highly stimulating and rich book. The author has a deep background and gives us a tour de force of the emerging agile methods.” —Tom Gilb The agile model of software development has taken the world by storm. Now, in Agile Software Development, Second Edition, one of agile’s leading pioneers updates his Jolt Productivity award-winning book to reflect all that’s been learned about agile development since its original introduction. Alistair Cockburn begins by updating his powerful model of software development as a “cooperative game of invention and communication.” Among the new ideas he introduces: harnessing competition without damaging collaboration; learning lessons from lean manufacturing; and balancing strategies for communication. Cockburn also explains how the cooperative game is played in business and on engineering projects, not just software development Next, he systematically illuminates the agile model, shows how it has evolved, and answers the questions developers and project managers ask most often, including · Where does agile development fit in our organization? · How do we blend agile ideas with other ideas? · How do we extend agile ideas more broadly? Cockburn takes on crucial misconceptions that cause agile projects to fail. For example, you’ll learn why encoding project management strategies into fixed processes can lead to ineffective strategy decisions and costly mistakes. You’ll also find a thoughtful discussion of the controversial relationship between agile methods and user experience design. Cockburn turns to the practical challenges of constructing agile methodologies for your own teams. You’ll learn how to tune and continuously reinvent your methodologies, and how to manage incomplete communication. This edition contains important new contributions on these and other topics: · Agile and CMMI · Introducing agile from the top down · Revisiting “custom contracts” · Creating change with “stickers” In addition, Cockburn updates his discussion of the Crystal methodologies, which utilize his “cooperative game” as their central metaphor. If you’re new to agile development, this book will help you succeed the first time out. If you’ve used agile methods before, Cockburn’s techniques will make you even more effective.
However, we must first repair the bad reputation that use cases have picked up from the people who write them poorly. ... 30See Writing Effective Use Cases (Cockburn 2001c) for a description of briefs, casual and fully dressed use cases ...
Author: Alistair Cockburn
Publisher: Pearson Education
This book offers a unique insight into a revolution in software development that allows model specifications to be fully and efficiently translated into code. Using the most widely adopted, industry standard, software modelling language, UML, the reader will learn how to build robust specifications based on OMG's Model Driven Architecture (MDA). From there, the authors describe the steps needed to translate the Executable UML (xUML) models to any platform-specific implementation. The benefits of this approach go well beyond simply reducing or eliminating the coding stage - it also ensures platform independence, avoids obsolescence (programming languages may change, the model doesn't) and allows full verification of the models by executing them in a test and debug xUML environment. This is an excellent reference for anyone embarking on what is surely the future of software development for medium and large scale projects.
4.7 Effective use of use case modelling In the previous section we met a number of techniques for managing complexity in use cases ... The best source of guidance that we are aware of is Alistair Cockburn's ' Writing Effective Use Cases ...
Author: Chris Raistrick
Publisher: Cambridge University Press