Library Hours
Monday to Friday: 9 a.m. to 9 p.m.
Saturday: 9 a.m. to 5 p.m.
Sunday: 1 p.m. to 9 p.m.
Naper Blvd. 1 p.m. to 5 p.m.
LEADER 00000cam a2200517Ma 4500
003 OCoLC
005 20240129213017.0
006 m o d
007 cr cn|||||||||
008 150904s2003 xx o 000 0 eng d
010 |z 2003051832
019 1256736892|a1280829168
024 8 9780321154989
024 8 0321154983
029 1 AU@|b000067091673
035 (OCoLC)1100827826|z(OCoLC)1256736892|z(OCoLC)1280829168
040 CEF|beng|epn|cCEF|dOCLCO|dOCLCF|dCNCEN|dOCLCQ|dINARC
|dOCLCO|dOCLCQ|dOCLCO
049 INap
082 04 658/.05421
082 04 658/.05421|221
099 eBook O'Reilly for Public Libraries
100 1 Kulak, Daryl,|eauthor.
245 10 Use Cases :|bRequirements in Context, Second Edition /
|cKulak, Daryl.|h[O'Reilly electronic resource]
250 2nd edition.
264 1 |bAddison-Wesley Professional,|c2003.
300 1 online resource (272 pages)
336 text|btxt|2rdacontent
337 computer|bc|2rdamedia
338 online resource|bcr|2rdacarrier
347 text file
365 |b54.99
504 Includes bibliographical references (p. 235-236) and
index.
520 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."
542 |fCopyright © 2004 by Pearson Education, Incorporated
|g2004
550 Made available through: Safari, an O'Reilly Media Company.
590 O'Reilly|bO'Reilly Online Learning: Academic/Public
Library Edition
650 0 Use cases (Systems engineering)
650 0 System design.
650 6 Cas d'utilisation (Ingénierie des systèmes)
650 6 Conception de systèmes.
650 7 System design|2fast
650 7 Use cases (Systems engineering)|2fast
700 1 Guiney, Eamonn,|eauthor.
856 40 |uhttps://ezproxy.naperville-lib.org/login?url=https://
learning.oreilly.com/library/view/~/0321154983/?ar
|zAvailalbe on O'Reilly for Public Libraries
938 Internet Archive|bINAR|nusecasesrequirem0000kula_g0w9
994 92|bJFN