Requirement specification builds the relationship between business and developers, allowing customers and developers come to an agreement about the project flowing. However, user requirement specification is a vital part of any software development. If you are not clear about what customers want and what you are providing them, then how you will perceive what you have achieved. A good user requirement specification provides better estimation, reduces cost, improves customer satisfaction and gives you a clear idea about the time duration of the project. URS are written by the system owner and end-users with input from Quality assurance. User Requirements Specifications are not normally intended to be a technical document. Users with only a general knowledge should be able to perceive the requirements written in the URS. To be successful at requirements gathering some crucial rules should be maintained. You should not assume that you know what the customer wants. Instead ask the customer as much as you can. However, user should be involved from the start. You should be clear about what you doubt. Moreover, you should create a clear, concise and thorough requirements document and provide those to the customer.