Use Cases - Requirements in Context

Kulak, Daryl,Guiney, Eamonn,

ISBN 10: 0201657678 / ISBN 13: 9780201657678

Published by Addison-Wesley, 2000

About this Item

New. US edition. Expediting shipping for all USA and Europe orders excluding PO Box. Excellent Customer Service. Seller Inventory # ABEJUNE24-65636

Bibliographic Details

Title: Use Cases - Requirements in Context

Publisher: Addison-Wesley

Publication Date: 2000

Binding: Soft cover

Condition: Brand New

About this title

Synopsis:

Use Cases - Requirements in Context

From the Back Cover:

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