Users do not express their requirements at the level of specificity found in completed SRS documents. An ideal SRS for a software-intensive system can be characterized as having requirements that completely capture a problem, is devoid of design evidence, and has succinctly stated requirements. This type of document would generally overwhelm the user in the sheer density of detail, repetitiveness of the language, and the total number of requirements stated. Most users would not be readily able to determine if the system described in this manner would truly address their original needs. The user s confidence in the development process can be fortified if he can see steady transitions of requirements from his expressed concepts, to requirements to specification, to code, to product.
People are most comfortable with describing things in the language of their problem domain.
A high priority should be placed on allowing the user to directly express desires and ideas for needed capabilities of the expected system. The user may also provide some insight into specific testing criteria to be considered. The area of Systems and Software Systems Security underwent growth during the 1990s. The Internet s emergence spurred numerous e-companies to rapid growth and success, while the field of electronic commerce remains in its infancy. Like all software, security-relevant software often is designed and released with latent defects.