Use Cases: Requirements in Context

by Daryl Kulak, Eamonn Guiney

Use Requirements in Context describes how to gather and define software requirements using a process based on use cases. It shows systems analysts and designers how use cases can provide solutions to the most challenging requirements issues, resulting in effective, quality systems that meet the needs of users. Specifically, with use cases, you Reduce the incidence of duplicate and inconsistent requirements; Communicate requirements that are understandable to both users and developers; Prototype the right system well before the design phase is underway; Document the entire requirements process clearly and efficiently. Use Requirements in Context first examines the difficulties of requirements gathering and briefly introduces both use cases and the Unified Modeling Language (UML). Using detailed examples that run through the book, it then elaborates a four-step method for establishing requirements--an iterative process that produces increasingly refined requirements. Drawing on their own extensive experience, the authors offer practical advice on how to manage this process, including guidance on planning, scheduling and estimating. They also reveal common mistakes and pitfalls to avoid. This detailed, hands-on book shows you how Describe object relationships and interactions with use case diagrams and scenarios Specify functional and non-functional requirements Create the candidate use case list Break out detailed use cases and add detail to use case diagrams Add triggers, preconditions, basic course of events, and exceptions to use cases Other topics include stakeholder interviews, use case name filters, the context matrix, user interface requirements, team organization, and quality assurance.

Genres: Reference

329 pages, Paperback

First published May 8, 2000

Reviews

[Christophe Addinquy · Rating 3 out of 5]

This book complement other writings on use cases. This approach here looks close to Gery Schneider's one. But the original point here is all about the way the authors connect classic requirements management to use cases. Even if the approach address the overlooked question of mapping the cross-functional requirements to use cases, I don't feel convinced by the idea. Especially today it looks overweight for me. The appendices are more than 100 pages long, it doesn't helps to feel the reading pleasant.

[Tuna Temiz · Rating 3 out of 5]

"Use Cases: Requirements in Context" by Daryl Kulak offers a practical guide on employing use case methodology to articulate software requirements clearly and efficiently. The book shines in its ability to demystify the process of documenting and implementing user-centered design processes, making it particularly beneficial for beginners and intermediate practitioners in the field. Kulak's clear and straightforward writing style, complemented by relevant examples and best practices, facilitates an accessible introduction to use case theory and its application in real-world scenarios. This focus on practicality underscores the book’s value as a foundational resource for those looking to enhance their understanding and skills in requirements analysis.

However, the book's relevance is somewhat tempered by its limited engagement with the nuances of modern software development practices, particularly agile methodologies. While it lays a solid groundwork in use case fundamentals, the content may not fully satisfy professionals operating within more dynamic and fast-paced development environments. Additionally, the examples, though instructive, might not capture the complexity or scale of challenges faced in larger projects. As a result, "Use Cases: Requirements in Context" serves as a useful entry point for those new to the concept of use cases, but its scope and depth might not meet the needs of advanced practitioners or those seeking to integrate traditional approaches with contemporary agile frameworks. Further exploration and supplementary materials may be necessary to bridge these gaps and apply the principles of use cases effectively in diverse and evolving software development landscapes.

[Tim · Rating 3 out of 5]

A nice well structured book