What Is Requirements Definition Document For a Project?
The requirements definition document includes a general description that specifies competitive advantages of the project under development and its functionality. It briefly outlines the main properties of the product and indicates what qualifications a user should have to work with it. At the same time, the document does not contain a detailed description of the functionality. The special requirements section contains definitions of functional requirements, performance requirements, interface requirements and a number of other requirements. This document should contain interpretations of abbreviations (acronyms) and technical terminology used to describe the product.
If you make up your mind to outsource qa to Ukrainian testers it would be great as then your development costs will be reduced but project quality, on the contrary, – increased!
Once the requirements definition document is written, it must be subjected to static testing to check the requirements for completeness, consistency, feasibility, maintainability, uniqueness and relevance.
Types of requirements. Above we defined the requirements as a description of what the system can do, or what operating conditions must be ensured for the system to be able to perform the tasks assigned to it. This implies using a wide range of different information sources therefore it makes sense to break requirements into categories. For example, a set of such categories is represented by the following list:
Functionality. This set of requirements determines which functions a given software product should perform at the system or user level. For clarity, it can describe what the product should not do.
Interfaces. This category of requirements describes inputs received from external systems, and outputs directed to external systems. Are there any restrictions on these interfaces related to data formats and data bearers?
Data. These requirements describe the input and output of the proposed system. What format is used for this? What data should be saved? How much data are transferred to the system and from the system and at what transmission rate? To what accuracy must the calculations be performed?
Productivity. The requirements of this category describe the scalability and synchronization issues, for example, how many simultaneous users must be supported by the system, how many transactions the system should perform per unit of time, how long the user should wait for a response to his request.