Home > Software Quality Tips > Software Quality Book Excerpts > Software Requirements, Second Edition -- Chapter 7, Hearing the Voice of the Customer
Software Quality Tips:
EMAIL THIS
 TIPS & NEWSLETTERS TOPICS 

SOFTWARE QUALITY BOOK EXCERPTS

Software Requirements, Second Edition -- Chapter 7, Hearing the Voice of the Customer


Karl E. Wiegers, Ph.D.
02.14.2007
Rating: -3.00- (out of 5)


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   



As a registered member of SearchSoftwareQuality.com, you're entitled to a complimentary copy of Chapter 7 of Software Requirements, Second Edition written by Karl E. Wiegers, Ph.D. and published by Microsoft Press.

The heart of requirements engineering is elicitation, the process of identifying the needs and constraints of the various stakeholders for a software system. In "Chapter 7, Hearing the Voice of the Customer," Wiegers addresses the general principles of effective requirements elicitation.



[IMAGE]

Book description:
Software Requirements, Second Edition describes several dozen practices that can help you gather, analyze, document, verify and manage your software project requirements. The emphasis is on realistic practical methods and process improvement, not theoretical models. Business, user, functional and nonfunctional req...


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   



RELATED CONTENT
Software Quality Book Excerpts
Perfect Software, Ch. 8: What Makes a Good Test
Seven Steps to Mastering Business Analysis, Ch. 1
Clean Code: A Handbook of Agile Software Craftsmanship, Chapter 1 -- What Is Clean Code?
The Software Project Manager's Bridge to Agility: Chapter 5, Scope Management
Software Security Engineering: A Guide for Project Managers -- Chapter 3, Requirements Engineering for Secure Software
Requirements Management Using IBM Rational RequisitePro: Chapter 1, Requirements Management
Implementing ITIL Configuration Management: Chapter 3, Determining Scope, Span and Granularity
Agile Software Development: The Cooperative Game, 2nd Edition -- Chapter 3, Communicating, Cooperating Teams
Inherent Quality Simplicity, Section V: The Evolution
Managing the Test People, Chapter 6: Keeping Your Beast Effective

Software requirements techniques (Prototyping, Storyboards, Modeling, State transitions)
Requirements practices evolving, but organizations still struggle
Why business analysts are application development key players today
Defining report requirements with use cases
When it comes to requirements, what is 'just enough'?
How requirements use cases facilitate the SDLC
GatherSpace beefs up cloud-based requirements management
Software development life cycle phases, iterations, explained step by step
How to deliver, implement testable software requirements
Excelling in the art and science of requirements elicitation
Software requirements: Moving beyond use cases

Software Requirements
Seven Steps to Mastering Business Analysis, Ch. 1
Software Security Engineering: A Guide for Project Managers -- Chapter 3, Requirements Engineering for Secure Software
Requirements Management Using IBM Rational RequisitePro: Chapter 1, Requirements Management
Mastering the Requirements Process, 2nd Edition: Chapter 2, The Requirements Process
Patterns for Effective Use Cases -- Chapter 1, What Is a Quality Use Case?
Effective Prototyping for Software Makers -- Chapter 3, Verify Prototype Assumptions and Requirements

RELATED GLOSSARY TERMS
Terms from Whatis.com − the technology online dictionary
requirements analysis  (SearchSoftwareQuality.com)

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary


uirements are all addressed.

Topics covered include customer involvement in the requirements process, use cases, prototyping, requirements prioritization, the software requirements specification, change management, requirements traceability, requirements management tools and managing requirements risks.

The second edition features more depth on every topic, a comprehensive requirements troubleshooting guide, an integrated set of sample requirements documents, and new chapters on the role of the requirements analyst, defining and using business rules, and applying requirements engineering to maintenance projects, package solution projects, outsourced projects, and emergent projects.

>> Read Chapter 7: Hearing the Voice of the Customer.

>> Buy the book





Rate this Tip
To rate tips, you must be a member of SearchSoftwareQuality.com.
Register now to start rating these tips. Log in if you are already a member.




DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.



Software Design & Testing - Project Management
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Site Map




All Rights Reserved, Copyright 2006 - 2009, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts