Specification language
Introduction: - Requirements specification requires the use of some specification language. Language should support the desirable qualities of SRS - variability, understanding, unambiguous, and so forth. Apart from this, learning and using languages should be easy. As no one can expect, many of these characteristics in the specification language selection conflict. For example, to avoid ambiguity, it is best to use some formal language. But a natural language can be better for ease of understanding.
Although formal notifications are available to specify the specific properties of the system, natural languages are now often used for specific requirements. If formal languages are to be used, they are often used to specify special qualities or specific parts of the system, and these formal specifications are usually contained in the overall SRS, which is in a natural language. . In other words, the overall SRS is usually in a natural language, and when possible and desirable, some specifics in the SRS can use formal languages.
The main advantage of using a natural language is that both customers and suppliers understand the language. However, by the nature of a natural language, it is impermeable and obscure. In order to reduce the shortcomings of natural languages, the natural language is most often used in structured fashion. In structured English, the requirements are broken into sections and paragraphs. Each paragraph is then broken into sub-paragraphs. Many organizations try hard use of certain words like "will," "maybe," and "too" and try to restrict the use of common phrases to improve accuracy and reduce function and ambiguity. When using a natural language, a general rule is to be precise, factual and concise, and to organize the requirements in a hierarchically, where possible, give unique numbers to each different requirement.
Although formal notifications are available to specify the specific properties of the system, natural languages are now often used for specific requirements. If formal languages are to be used, they are often used to specify special qualities or specific parts of the system, and these formal specifications are usually contained in the overall SRS, which is in a natural language. . In other words, the overall SRS is usually in a natural language, and when possible and desirable, some specifics in the SRS can use formal languages.
The main advantage of using a natural language is that both customers and suppliers understand the language. However, by the nature of a natural language, it is impermeable and obscure. In order to reduce the shortcomings of natural languages, the natural language is most often used in structured fashion. In structured English, the requirements are broken into sections and paragraphs. Each paragraph is then broken into sub-paragraphs. Many organizations try hard use of certain words like "will," "maybe," and "too" and try to restrict the use of common phrases to improve accuracy and reduce function and ambiguity. When using a natural language, a general rule is to be precise, factual and concise, and to organize the requirements in a hierarchically, where possible, give unique numbers to each different requirement.
Components off and software requirements specification click here
For example, to specify the input or output formats, regular expressions can be very useful. Similarly, when systems like communication protocol are discussed, finite state automata can be used. Decision tables are formally useful for specifying the behavior of a system on different combinations of input or settings. Similarly, some aspects of the system can be specified or explained using the model created during the analysis of the problem. Sometimes the model can be included in the form of supporting documents which help to clarify requirements and motivation better.from Science Technology http://bit.ly/2K57eBl
Comments
Post a Comment