| 000 | 02837 a2200373 4500 | ||
|---|---|---|---|
| 001 | 72680 | ||
| 003 | TR-AnTOB | ||
| 005 | 20240917104217.0 | ||
| 008 | 030205s2003 maua b 001 0 eng | ||
| 010 | _a2003043724 | ||
| 020 | _a032112247X (alk. paper) | ||
| 040 |
_aDLC _cDLC _dDLC |
||
| 041 | _aeng | ||
| 042 | _apcc | ||
| 050 |
_aQA76.76.D47 _bL45 2003 |
||
| 090 | _aQA76.76.D47 L45 2003 | ||
| 100 |
_aLeffingwell, Dean _949460 |
||
| 245 | 0 |
_aManaging software requirements : _ba use case approach / _cDean Leffingwell, Don Widrig. |
|
| 250 | _a2nd ed. | ||
| 264 | 1 |
_aBoston : _bAddison-Wesley, _cc2003. |
|
| 300 |
_axxxvii, 502 p. : _bill. ; _c25 cm. |
||
| 490 | 0 | _aThe Addison-Wesley object technology series | |
| 504 | _aIncludes bibliographical references (p. 483-486) and index. | ||
| 505 |
_aIntroduction: 1. The requirements problem -- _t2. Introduction to requirements management -- _t3. Requirements and the software cycle -- _t4. The software team -- _tTeam skill 1. Analyzing the problem: 5. The five steps in problem analysis -- _t6. Business modeling -- _t7. Systems engineering of software-intensive systems -- _tTeam skill 2. Understanding user and stakeholder needs: 8. The challenge of requirements elicitation -- _t9. The features of a product or system -- _t10. Interviewing -- _t11. Requirements workshops -- _t12. Brainstorming and idea reduction -- _t13. Storyboarding -- _tTeam skill 3. Defining the system: 14. A use case primer -- _t15. organizing requirements information -- _t16. The vision document -- _t17. Product management -- _tTeam skill 4. Managing scope: 18. Establishing project scope -- _t19. Managing your customer -- _tTeam skill 5. Refining the system definition: 20. Software requirements, a more rigorous look -- _t21. Refining the use cases -- _t22. Developing the supplementary specification -- _t23. On ambiguity and specificity -- _t24. Technical methods for specfiying requirements -- _tTeam skill 6. Building the right system: 25. From use cases to implementation -- _t26. From use cases to test cases -- _t27. Tracing requirements -- _t28. Managing change -- _t29. Assessing requirements qulity in iterative development -- _tGetting started: 30. Agile requirements methods -- _t31. Your prescription for requirements management -- _tAppendixes: A. HOLIS artifacts -- _tB. Vision document template -- _tC. Use-case specification template -- _tD. Supplementary specification template -- _tE. Requirements management in the rational unified process -- _tF. Requirements management in the SEI-CMM and withing ISO 90000:2000. |
||
| 650 | 0 |
_aUse cases (Systems engineering) _949462 |
|
| 650 | 0 |
_aComputer software _xDevelopment _xManagement _929504 |
|
| 700 |
_aWidrig, Don _949461 |
||
| 902 | _a0026739 | ||
| 903 | _aMerkez Kütüphane | ||
| 942 |
_cBK _2lcc |
||
| 945 | _aBS | ||
| 999 |
_c72680 _d20965 |
||