|
|
|
|
| LEADER |
01957nam a2200313a 44500 |
| 001 |
UBP02808 |
| 003 |
AR-CdUBP |
| 005 |
20220310151944.0 |
| 008 |
151212s1998#######|||||||||||||||||eng|d |
| 020 |
|
|
|a 0-201-57169-2
|
| 040 |
|
|
|a AR-CdUBP
|b spa
|
| 041 |
|
|
|a eng
|
| 100 |
|
|
|a Jacobson, Ivar
|
| 245 |
1 |
4 |
|a The unified software development process /
|c Ivar Jacobson, Grady Booch, James Rumbaugh
|
| 260 |
|
|
|a Reading, Massachusetts :
|b Addison-Wesley,
|c 1998
|
| 300 |
|
|
|a xxix, 463 p. ;
|c 22 cm.
|
| 490 |
0 |
|
|a The Addison-Wesley object technology series
|
| 504 |
|
|
|a Incluye referencias bibliográficas
|
| 505 |
0 |
|
|a Part I. The unified software development process. Chapter 1. The unified process: use-case driven, architecture-centric, iterative, and incremental. Chapter 2. The four Ps: people, project, product, and process in software development. Chapter 3. A use-case-driven process. Chapter 4. An architecture-centric process. Chapter 5. An iterative and incremental process. Part II. The core workflows. Chapter 6. Requirements capture: from vision to requirements. Chapter 7. Capturing the requirements as use cases. Chapter 8. Analysis. Chapter 9. Design. Chapter 10. Implementation. Chapter 11. Test. Part III. Iterative and incremental development. Chapter 12. The generic iteration workflow. Chapter 13. Inception launches the project. Chapter 14. The elaboration phase makes the architectural baseline. Chapter 15. Construction leads to initial operational capability. Chapter 16. Transition completes product release. Chapter 17. Making the Unified Process work. Appendix A. Overview of the UML. Appendix B. The Unified process-specific extensions of the UML. Appendix C. General glosary.
|
| 650 |
|
4 |
|a UML
|
| 653 |
|
|
|a INFORMATICA
|
| 700 |
1 |
|
|a Booch, Grady
|
| 700 |
1 |
|
|a Rumbaugh, James
|
| 930 |
|
|
|a INFORMATICA
|
| 931 |
|
|
|a 02808
|b UBP
|
| 942 |
|
|
|2 cdu
|c BK
|
| 945 |
|
|
|a SMM
|
| 984 |
|
|
|a 004.652.5
|b J158u
|
| 999 |
|
|
|c 18387
|d 18387
|