المستخلص: |
An SRS is basically a software developer's understanding of a customer or potential user's requirements and dependencies in a written form at a particular point in time which is usually prior to any actual design or development work. SRS documentation assures that both the client and the software developer/analyst understand the other's requirements from that perspective. Only the customer really knows the problem at hand، but only the system analyst can help the customer to express these problems correctly and completely. A number of systematic approaches for requirement gathering, elicitation, selection, and validation have been developed in recent years which often fail to recognize the need and importance of this fact that the customer usually cannot decode the formal or semiformal models produced by the system analyst, using formal methods. Obviously the most natural way that these two parties can use to communicate, express what they expect from the system and specify the requirements with least miscommunication is Natural Language (NL).
|