Use Cases: Requirements in Context - Couverture souple

Kulak, Daryl; Guiney, Eamonn

Couverture souple

ISBN 10 : 0201657678 ISBN 13 : 9780201657678

Editeur : Addison Wesley, 2000

Synopsis

Book by Kulak Daryl Guiney Eamonn

A propos du livre

Présentation de l'éditeur

This book 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.

Use Cases, Second Edition: Requirements in Context describes a three-step method for establishing requirements―an iterative process that produces increasingly refined requirements. Drawing on their extensive, real-world experience, the authors offer a wealth of advice on use-case driven lifecycles, planning for change, and keeping on track. In addition, they include numerous detailed examples to illustrate practical applications.

This second edition incorporates the many advancements in use case methodology that have occurred over the past few years. Specifically, this new edition features major changes to the methodology's iterations, and the section on management reflects the faster-paced, more "chaordic" software lifecycles prominent today. In addition, the authors have included a new chapter on use case traceability issues and have revised the appendixes to show more clearly how use cases evolve.

The book opens with a brief introduction to use cases and the Unified Modeling Language (UML). It explains how use cases reduce the incidence of duplicate and inconsistent requirements, and how they facilitate the documentation process and communication among stakeholders.

The book shows you how to:

• Describe the context of relationships and interactions between actors and applications using use case diagrams and scenarios
• Specify functional and nonfunctional 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
• Manage the iterative/incremental use case driven project lifecycle
• Trace back to use cases, nonfunctionals, and business rules
• Avoid classic mistakes and pitfalls

The book also highlights numerous currently available tools, including use case name filters, the context matrix, user interface requirements, and the authors' own "hierarchy killer."

Quatrième de couverture

Use Cases: 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 can:

• Reduce the incidence of duplicate and inconsistent requirements;
• Communicate requirements that are understandable to both users and developers;
• Communicate a vision of what the application needs to do without the distractions inherent in a coded prototype;
• Document the entire requirements process clearly and efficiently.

Use Cases: 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 dedicate an entire chapter to the common mistakes made during requirements capture and specification, particularly those related to use case creation.

This detailed, hands-on book shows you how to:

• Describe the context of relationships and interactions between actors and applications using 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 tools examined in this book include the stakeholder interview, use case name filters, the context matrix, user interface requirements, team organization, and quality assurance.

0201657678B04062001

Détails de l'édition

• Éditeur: Addison Wesley
• Date d'édition: 2000
• ISBN 10: 0201657678
• ISBN 13: 9780201657678
• Reliure: Broché
• Langue: anglais
• Nombre de pages: 352