This presentation describes numerous techniques for writing software functional requirements, focused on the core objective of clear and effective communication. You’ll see multiple styles of writing functional requirements and you’ll learn many vague “weak words” to avoid.
The presentation describes several common types of requirements ambiguity and shows how to rewrite ambiguous requirements to make them clearer. We’ll also explore the common issue of having solution ideas or design constraints embedded in requirements. Applying the techniques described in this presentation will help your requirements specifications speak more clearly to their various audiences.
** Eligible for PDUs, CDUs. **
Karl E. Wiegers, Principal Consultant
Karl E. Wiegers has provided training and consulting services worldwide on many aspects of software development, management and process improvement. Prior to starting Process Impact in 1997, Karl spent 18 years at Eastman Kodak Company in a variety of roles. Karl is the author of many books including: Software Requirements & More About Software Requirements.
FEATURED SPONSOR: QRA
Understanding the Key Productivity Indicators (KPIs)
API quota exceeded. You can make 500 requests per day.Using Productiveness Scorecards to Achieve Business Objectives
An Overview of BPM – Balanced Productivity Metrics
8 Top Tips to Being More Productive