|
|
|
|
LEADER |
00000cam a2200000 a 4500 |
001 |
OR_ocm54115586 |
003 |
OCoLC |
005 |
20231017213018.0 |
006 |
m o d |
007 |
cr unu|||||||| |
008 |
040130s2003 maua ob 001 0 eng d |
040 |
|
|
|a OCL
|b eng
|e pn
|c OCL
|d OCLCQ
|d CEF
|d VLB
|d OCLCQ
|d AZU
|d NHM
|d OCLCQ
|d OCLCF
|d IDEBK
|d OCLCQ
|d OCLCO
|d UV0
|d S4S
|d C6I
|d OCLCQ
|d COO
|d OCLCQ
|d INARC
|d HS0
|d LDP
|d OCLCO
|d OCLCQ
|
019 |
|
|
|a 229448446
|a 729548784
|a 748104893
|a 1036822731
|a 1044619245
|a 1056403838
|a 1060867834
|a 1074321174
|a 1108947713
|a 1156878192
|a 1180978272
|
020 |
|
|
|a 9780201721843
|
020 |
|
|
|a 0201721848
|
020 |
|
|
|z 0201721848
|
024 |
1 |
|
|a 785342721843
|
024 |
3 |
|
|a 9780201721843
|
029 |
1 |
|
|a HEBIS
|b 291418228
|
029 |
1 |
|
|a NZ1
|b 12116220
|
035 |
|
|
|a (OCoLC)54115586
|z (OCoLC)229448446
|z (OCoLC)729548784
|z (OCoLC)748104893
|z (OCoLC)1036822731
|z (OCoLC)1044619245
|z (OCoLC)1056403838
|z (OCoLC)1060867834
|z (OCoLC)1074321174
|z (OCoLC)1108947713
|z (OCoLC)1156878192
|z (OCoLC)1180978272
|
050 |
|
4 |
|a QA76.76.P37
|b P38 2003
|
082 |
0 |
4 |
|a 005.1
|2 21
|
049 |
|
|
|a UAMI
|
100 |
1 |
|
|a Adolph, Steve.
|
245 |
1 |
0 |
|a Patterns for effective use cases /
|c Steve Adolph and Paul Bramble ; with contributions by Alistair Cockburn and Andy Pols.
|
260 |
|
|
|a Boston :
|b Addison-Wesley,
|c ©2003.
|
300 |
|
|
|a 1 online resource (xxii, 236 pages) :
|b illustrations
|
336 |
|
|
|a text
|b txt
|2 rdacontent
|
337 |
|
|
|a computer
|b c
|2 rdamedia
|
338 |
|
|
|a online resource
|b cr
|2 rdacarrier
|
490 |
1 |
|
|a The agile software development series
|
504 |
|
|
|a Includes bibliographical references (pages 217-218) and index.
|
520 |
8 |
|
|a Use cases have become a very popular requirements-gathering technique, yet many developers struggle when faced with writing them. They grasp the basic concepts, but find that writing effective use cases turns out to be more difficult than they expected. One factor contributing to this difficulty is that the community lacks objective criteria for judging the quality of use cases. This new book articulates the qualities of effective use cases by applying the proven patterns concept of development to this requirements-gathering technique. The authors present a catalog of thirty-six patterns that help the reader become proficient at judging the quality of their (and other's) patterns. These patterns represent solutions to recurring problems that application developers have faced in writing use cases. Each pattern is presented with examples that help the reader understand the benefit of the pattern, and just as importantly, the consequences of ignoring its proper use.
|
546 |
|
|
|a English.
|
590 |
|
|
|a O'Reilly
|b O'Reilly Online Learning: Academic/Public Library Edition
|
650 |
|
0 |
|a Software patterns.
|
650 |
|
0 |
|a Application software
|x Development.
|
650 |
|
0 |
|a Use cases (Systems engineering)
|
650 |
|
4 |
|a Engineering & Applied Sciences.
|
650 |
|
4 |
|a Computer Science.
|
650 |
|
6 |
|a Logiciels
|x Modèles de conception.
|
650 |
|
6 |
|a Logiciels d'application
|x Développement.
|
650 |
|
6 |
|a Cas d'utilisation (Ingénierie des systèmes)
|
650 |
|
7 |
|a Application software
|x Development.
|2 fast
|0 (OCoLC)fst00811707
|
650 |
|
7 |
|a Software patterns.
|2 fast
|0 (OCoLC)fst01124209
|
650 |
|
7 |
|a Use cases (Systems engineering)
|2 fast
|0 (OCoLC)fst01163102
|
700 |
1 |
|
|a Bramble, Paul.
|
776 |
0 |
8 |
|i Print version:
|z 0201721848
|w (DLC) 2002074419
|w (OCoLC)49901910
|
830 |
|
0 |
|a Agile software development series.
|
856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/0201721848/?ar
|z Texto completo (Requiere registro previo con correo institucional)
|
938 |
|
|
|a Internet Archive
|b INAR
|n patternsforeffec00adol
|
994 |
|
|
|a 92
|b IZTAP
|