Software Requirements: Developer Best Practices
Autor Karl Wiegers, Joy Beattyen Limba Engleză Paperback – 29 aug 2013
- Describes practical, effective, field-tested techniques for managing the requirements engineering process from end to end.
- Provides examples demonstrating how requirements "good practices" can lead to fewer change requests, higher customer satisfaction, and lower development costs.
- Fully updated with contemporary examples and many new practices and techniques.
- Describes how to apply effective requirements practices to agile projects and numerous other special project situations.
- Targeted to business analysts, developers, project managers, and other software project stakeholders who have a general understanding of the software development process.
- Shares the insights gleaned from the authors' extensive experience delivering hundreds of software-requirements training courses, presentations, and webinars.
Preț: 207.89 lei
Preț vechi: 259.86 lei
-20% Nou
Puncte Express: 312
Preț estimativ în valută:
39.79€ • 41.97$ • 33.16£
39.79€ • 41.97$ • 33.16£
Carte disponibilă
Livrare economică 12-26 decembrie
Livrare express 27 noiembrie-03 decembrie pentru 54.04 lei
Preluare comenzi: 021 569.72.76
Specificații
ISBN-13: 9780735679665
ISBN-10: 0735679665
Pagini: 672
Ilustrații: black & white illustrations
Dimensiuni: 188 x 231 x 36 mm
Greutate: 1.13 kg
Ediția:Revised
Editura: Microsoft Press
Seria Developer Best Practices
ISBN-10: 0735679665
Pagini: 672
Ilustrații: black & white illustrations
Dimensiuni: 188 x 231 x 36 mm
Greutate: 1.13 kg
Ediția:Revised
Editura: Microsoft Press
Seria Developer Best Practices
Notă biografică
Cuprins
- Introduction
- Acknowledgments
- Software requirements: What, why, and who
- Chapter 1: The essential software requirement
- Chapter 2: Requirements from the customer's perspective
- Chapter 3: Good practices for requirements engineering
- Chapter 4: The business analyst
- Requirements development
- Chapter 5: Establishing the business requirements
- Chapter 6: Finding the voice of the user
- Chapter 7: Requirements elicitation
- Chapter 8: Understanding user requirements
- Chapter 9: Playing by the rules
- Chapter 10: Documenting the requirements
- Chapter 11: Writing excellent requirements
- Chapter 12: A picture is worth 1024 words
- Chapter 13: Specifying data requirements
- Chapter 14: Beyond functionality
- Chapter 15: Risk reduction through prototyping
- Chapter 16: First things first: Setting requirement priorities
- Chapter 17: Validating the requirements
- Chapter 18: Requirements reuse
- Chapter 19: Beyond requirements development
- Requirements for specific project classes
- Chapter 20: Agile projects
- Chapter 21: Enhancement and replacement projects
- Chapter 22: Packaged solution projects
- Chapter 23: Outsourced projects
- Chapter 24: Business process automation projects
- Chapter 25: Business analytics projects
- Chapter 26: Embedded and other real-time systems projects
- Requirements management
- Chapter 27: Requirements management practices
- Chapter 28: Change happens
- Chapter 29: Links in the requirements chain
- Chapter 30: Tools for requirements engineering
- Implementing requirements engineering
- Chapter 31: Improving your requirements processes
- Chapter 32: Software requirements and risk management
- Epilogue
- Current requirements practice self-assessment
- Requirements troubleshooting guide
- Sample requirements documents
- Glossary
- About the authors