Software requirements / Karl Wiegers and Joy Beatty.
Material type:![Text](/opac-tmpl/lib/famfamfam/BK.png)
- text
- unmediated
- volume
- 9780735679665 (pbk.)
- 0735679665 (pbk.)
- 005.1 23
- QA76.76.D47 W517 2013
Item type | Current library | Shelving location | Call number | Status | Date due | Barcode | Item holds |
---|---|---|---|---|---|---|---|
![]() |
Bahria University Karachi Campus Library | Software Engineering | 005.1 (Browse shelf(Opens below)) | Checked out to Bushra Fazal (03-2109-0009) | 2025-01-30 | BUK14818 |
Includes bibliographical references (pages 605-618) and index.
Software requirements: what, why, and who: The essential software requirement ; Requirements from the customer's perspective ; Good practices for requirements engineering ; The business analyst -- Requirements development: Establishing the business requirements ; Finding the voice of the user ; Requirements elicitation ; Understanding user requirements ; Playing by the rules ; Documenting the requirements ; Writing excellent requirements ; A picture is worth 1024 words ; Specifying data requirements ; Beyond functionality ; Risk reduction through prototyping ; First things first : setting requirement priorities ; Validating the requirements ; Requirements reuse ; Beyond requirements development -- Requirements for specific project classes : Agile projects ; Enhancement and replacement projects ; Packaged solution projects ; Outsourced projects ; Business process automation projects;- Business analytics projects ; Embedded and other real-time systems projects -- Requirements management: Requirements management practices ; Change happens ; Links in the requirements chain ; Tools for requirements engineering -- Implementing requirements engineering: Improving your requirements process ; Software requirements and risk management.