An SRS is an important part of the requirements process of the software life cycle and is used in design,implementation, project monitoring, verification and validation, and in training as described in IEEE St1074-1997. The SRS should be unambiguous both to those who create it and to those who use it. However,these groups often do not have the same background and therefore do not tend to describe software requirementsthe same way. Representations that improve the requirements specification for the developer may be counterproductive in that they diminish understanding to the user and vice versa.