Topic: Characteristics of an Software Requirement Specificati
Introduction: - The original goal, one SRS should have some qualities and different needs should be there. Desirable features of components of SRS and SRS.
A good SRS-
1. Correct
2. Complete
3. Undoubtedly
4. Verifiable
5. Compatible
6. Rank for importance and / or stability
7. Convertible
8. Following
An SRS is correct
An SRS is completed if the software has to do everything and SRS software responses are specified for all sections of input data. Purity and perfection go hand in hand; While purity ensures that what is specified is done correctly, perfection ensures that everything is actually specified. Correction is an easy asset to set up completely because it involves checking essentially every requirement in order to ensure that it represents the user's requirement. On the other hand, perfection is the most difficult asset to install; To ensure completeness, one has to find out the absence of specialties, and it is very difficult to ascertain the absence than to determine that there are currently some assets.
An SRS is unnatural if only one and only one interpretation of each requirement is explained. Requirements are often written in natural language, which are naturally ambiguous. If requirements are specified in a natural language, then the SRS writer must be especially careful to ensure that there is no ambiguity. One way to avoid ambiguities is to use some formal requirements specification language. The major disadvantage of using formal languages is the major effort needed to write SRS, the high cost of doing so, and increased difficulty in reading and understanding the requirements as well as the stated requirements.
If an SRS is verified and only if each requirement is verifiable. If a cost-effective process is present, then it is worth checking whether the final software meets the requirement. This implies that the requirements should be at least as subjective as it is difficult to verify subjective requirements. Neutrality is essential for verification. As the requirements are verified through frequent reviews, it also means that SRS is understood, at least by developers, clients and users. The ability to understand is clearly very important, because one goal of the phase of requirements is to produce a document on which the client, user and the developers can agree.
An SRS is consistent if there is no need to struggle with the other. Glossary can cause inconsistencies; For example, different requirements can use different words to refer to the same object. There can be a logical or temporary struggle between the requirements of the discrepancy. This occurs when SRS has two or more requirements, whose logical or temporal features can not be satisfied with any software system simultaneously.
Generally, all the requirements for software are not of equal importance. Some are important, others are important but not important, and there are some who are desirable, but not very important. Similarly, some requirements are the "core" requirements, which are unlikely to change with the passage of time, while others are more dependent on time. An SRS is ranked for importance and / or stability if the stability of importance and requirement is indicated for each requirement. Stability of requirement reflects the possibility of changing it in the future. It can be reflected in the context of the amount of expected change.
SRS is traceable if its original requirement is clear and if it facilitates reference of every requirement in future development. Forward traceability means that each requirement should be detectable for some design and code elements.
A good SRS-
1. Correct
2. Complete
3. Undoubtedly
4. Verifiable
5. Compatible
6. Rank for importance and / or stability
7. Convertible
8. Following
An SRS is correct
An SRS is completed if the software has to do everything and SRS software responses are specified for all sections of input data. Purity and perfection go hand in hand; While purity ensures that what is specified is done correctly, perfection ensures that everything is actually specified. Correction is an easy asset to set up completely because it involves checking essentially every requirement in order to ensure that it represents the user's requirement. On the other hand, perfection is the most difficult asset to install; To ensure completeness, one has to find out the absence of specialties, and it is very difficult to ascertain the absence than to determine that there are currently some assets.
An SRS is unnatural if only one and only one interpretation of each requirement is explained. Requirements are often written in natural language, which are naturally ambiguous. If requirements are specified in a natural language, then the SRS writer must be especially careful to ensure that there is no ambiguity. One way to avoid ambiguities is to use some formal requirements specification language. The major disadvantage of using formal languages is the major effort needed to write SRS, the high cost of doing so, and increased difficulty in reading and understanding the requirements as well as the stated requirements.
If an SRS is verified and only if each requirement is verifiable. If a cost-effective process is present, then it is worth checking whether the final software meets the requirement. This implies that the requirements should be at least as subjective as it is difficult to verify subjective requirements. Neutrality is essential for verification. As the requirements are verified through frequent reviews, it also means that SRS is understood, at least by developers, clients and users. The ability to understand is clearly very important, because one goal of the phase of requirements is to produce a document on which the client, user and the developers can agree.
An SRS is consistent if there is no need to struggle with the other. Glossary can cause inconsistencies; For example, different requirements can use different words to refer to the same object. There can be a logical or temporary struggle between the requirements of the discrepancy. This occurs when SRS has two or more requirements, whose logical or temporal features can not be satisfied with any software system simultaneously.
Generally, all the requirements for software are not of equal importance. Some are important, others are important but not important, and there are some who are desirable, but not very important. Similarly, some requirements are the "core" requirements, which are unlikely to change with the passage of time, while others are more dependent on time. An SRS is ranked for importance and / or stability if the stability of importance and requirement is indicated for each requirement. Stability of requirement reflects the possibility of changing it in the future. It can be reflected in the context of the amount of expected change.
Requirements specification
Writing the SRS is an iterative process. Even when the requirements of a system are specified, they are later modified as the requirements of client changes. So revising SRS should be easy. If its structure and style are such that SRS is variable, any necessary change can be easily done by preserving perfection and consistency. The presence of redundancy is a major impediment to mitigation, because it can easily lead to errors.SRS is traceable if its original requirement is clear and if it facilitates reference of every requirement in future development. Forward traceability means that each requirement should be detectable for some design and code elements.
from Science Technology http://bit.ly/30DQO94
Comments
Post a Comment