|
|
|
|
| LEADER |
01686nam a2200301a 44500 |
| 001 |
UBP03427 |
| 003 |
AR-CdUBP |
| 005 |
20220310152257.0 |
| 008 |
151212s1982#######|||||||||||||||||eng|d |
| 020 |
|
|
|a 0-13-171711-1
|
| 040 |
|
|
|a AR-CdUBP
|b spa
|
| 041 |
|
|
|a eng
|
| 100 |
|
|
|a DeMarco, Tom
|
| 245 |
1 |
0 |
|a Controlling :
|b software projects. Management, measurement & estimation /
|c Tom DeMarco
|
| 260 |
|
|
|a New Jersey :
|b Prentice-Hall,
|c 1982
|
| 300 |
|
|
|a xii, 284 p. ;
|c 25 cm.
|
| 490 |
0 |
|
|a Yourdon press computing series
|
| 500 |
|
|
|a La Biblioteca posee: 1 ej.
|
| 504 |
|
|
|a Incluye referencias bibliográficas
|
| 505 |
0 |
|
|a CHAOS AND ORDER IN THE SOFTWARE DEVELOPMENT PROCESS. 1. The issue of control. 2. The estimating dilemma. 3. A new approach to control. 4. Projecting software costs. 5. The cost of measurement. SYSTEM MODELS AND SYSTEM METRICS. 6. The construction and use of system models. 7. A metric is...8. Specification: modeling the problem. 9. Specifiation metric. 10. Design: modeling the solution. 11. Design metric. 12. Implementation metrics. 13. Project planning: modeling the development process. 14. Result metrics. COST MODELS. 15. Cost projection: modeling resource use. 16. Corrected single-factor cost models. 17. Time-sensitive cost models. 18. A practical scheme for putting cost models to work. SOFTWARE QUALITY. 19. In search of software quality. 20. Software quality control. 21. Improving software quality. 22. Zero defect development. Appendix.
|
| 650 |
|
4 |
|a DESARROLLO DEL SOFTWARE
|
| 653 |
|
|
|a INFORMATICA
|
| 930 |
|
|
|a INFORMATICA
|
| 931 |
|
|
|a 03427
|b UBP
|
| 942 |
|
|
|c BK
|
| 945 |
|
|
|a SMM
|
| 984 |
|
|
|a 004.413
|b D391
|
| 999 |
|
|
|c 18995
|d 18995
|