In order to write the software requirement specification first analyze the running system where the software is required for. There are the different formats to write the software requirement specifications. But some commonly used formats are as follows: 1. Write the shortcomings of existing system after the analysis of domain. These are the drawbacks that make us to move to some more efficient system. 2. Describe the objectives of required system that should be fulfilled to overcome the shortcomings of existing system. 3. Describe the features of proposed software and develop a feasibility report. 4. Draw a logical diagram of the proposed system. There are mainly two ways 'structured' and 'object oriented' commonly used for system analysis so, logical design depends upon the way of analysis. This is the general description of writing the software requirement specifications. These may somewhat vary depending upon the type of software or type of domain of software. Some times there is no existing software i.e. The existing system is manual. Thus in different situations the format of writing the software specifications may differ.
