Following are certain important principle guidelines recommended to be followed while preparing the user requirements,
1) It is quite a good practice to highlight the useful information highlighting can be done by either making the data italic, underlined boldly or changing its color.
2) Use language consistently. mandatory requirements must be distinguished from desirable requirements.
3). While writing requirements, it is often a good practice to follow a standard notion throughout the document.
Example: The requirement can be in the bold format, the reason for its inclusion in normal text, etc.
Further, in order to ake the document more realistic, the source from which the given reason is acquired can also be associated with a particular reason. This provides us ease in considering
the source when suitable changes are being made to these requirements.
4) Mostly, avoid the usage of technical terms.
Structured language specifications for system requirements:
1. The structured natural language was initially proposed by Mr. Heninger with an intention to provide certain standards while writing the system requirements.
2. According to him, structured natural language is a decent style of writing system requirements that privileges the writers with well-defined standards and at the same time curbs their independency of using his own visualizations.
3. Hence, there will be a high degree of expressibility but this expressibility can adhere to equal measures of uniformity.
4. Structured natural language preaches to lower down the number of words used in describing the context of the system and allows us to look forward to the usage of templates whenever necessary.
5. Also to stress on certain of these requirements, structured natural languages facilitate to high light them.
6. Hence, in other words, the structured natural language expresses the system requirements in certain standard forms.
7. There should be a significant description corresponding to a function or a given entity.
8.Significant description corresponding to the inputs of the system as well as the source producing it.
9. Also, the description of output and the way are preceding towards.
10.Illustration related to the actions to be performed.
11.Illustration corresponding to the generation of side effects while performing a given operation.
12. Preconditions-before the function and post-conditions-after the function is called must be specified if the functional approach is used.
13.Any system that works because all its software system is in the working condition.
14. That means the existing system which is installed and implemented works when all software systems operate.
15. Specifications are defined in the early process for the existing system as well for any new system if it were to be added.
16. But for the new system and the existing system to work together they must interact with each other which is called interface and specification must be included in the requirements documents, interfaces of the existing system must have to be precisely specified.
17. It is easy to implement a new system with the help of the interface.
18. There are three kinds of interfaces that contribute to the operations of the existing system as well as the new system.
19. Existing programs or sub-system offer a range of services are accessed by calling interface procedures.
20. These interface procedures access these services for the specific functions they need. As they apply the services to their application and call these services through programming, therefore these interfaces are called application programming interfaces.