Via Graham O’Keeffe @ askaboutvalidation
User requirements should be the starting point of any project you are working on. Time well-spent developing solid user requirements will help you enormously further down the line when you need to test your new equipment or software application. Too many times people rush their requirements and as a result, the project suffers. This article gives a clear outline of the best practices to follow when you create your user requirement specification.
So where are people going wrong with this initial phase. How hard can it be to create a document detailing what exactly you want a system or piece of equipment to do?
The answer is, it can be very difficult if you don’t really know in the first place what exactly you want the system/application/equipment to do.
We have put together our top 22 tips for developing a bullet-proof URS. We hope you find the following tips helpful!
Requirements may be developed internally by the supplier (in the case of product development). Requirements also may be provided by customers (for a configured product, custom application, or a service.
The requirements should define clearly and precisely what the system should do and state any constraints. Requirements should be reviewed and approved by the stakeholders and the subject matter experts.
2. Clear Concise Manner
Requirements should be documented in a clear concise manner for the vendors/suppliers. Do not leave any room for ambiguous requirements allowing scope for the vendors to suggest their product meets the requirement when it doesn’t.
3. One Requirement at a Time
Do not double up on requirements; make it clear in your URS one requirement at a time. It will be easier for you to see how the requirement is handled and it will also make it easier for you to test one requirement at a time.
Click here to read more.