Unit testing and test driven design don’t help you if your requirements aren’t right. It may be that trying to create the tests will expose that you have a problem but wouldn’t it be nice to know that there are gaps in requirements before you sit down to write code? Although it’s impossible to get perfect requirements, most developers would love to get requirements that are better than what they’re getting.
Whether you’re getting requirements from a business analyst or you’re creating them yourself, here are a few simple tips for ensuring that your software requirements are right. These tips are pulled from my Pluralsight course Gathering Good Requirements for Developers.
Here are some things that you should check to ensure they have been covered:
- Are all the stakeholders represented? Have you received feedback from all of the parties impacted by the solution?
- Do you have functional requirements for all user requirements? Were you able to translate all of the high-level user requirements into specific requirements?
- Do all of the events that the system must respond to have responses? If you look at all of the events such as approvals, rejections, creations, and the like, do they all have a system response?