Simple tips in writing a software requirements and specification Document(SRS) document

Hey Sam,niether i nor you nor Tamer is saying not to use a template.My point to mention was that rather not sticking to a template seems not a nice idea.Since template is not more of abstract out line i think its the information that we put in any template to categorize it.I hope this will clear it.Thank you.

knights, I agree that "Not following a researched one, seems not a very nice idea.". I think that what Tamer is saying is that use of a template before researching requirements is not a good idea. If a template is adequately documented and after a new project's requirements are determined, if a template satisfies the requirements then there is nothing in this article saying to not use the template.

Its nice to have this discussion. But what we need to take care of there are several points that makes me choose a template, or even build my own template such as the type of project, the process methodology I'm using, the audience of the document, etc. I believe that there is no project similar to the other. What I mean with not to stick to a certain template, is to look first at the whole environment of the project, and the culture and mentalities of the client, then decide which template to use, or even build your own template if it will utilize your resources, and if it will be the best to be used for the project.

Thanks a lot Hussein, I'm sure that you've seen this problem in Egypt in several projects, and I'm sorry to say that some of these projects were for enterprise organizations.

Thanks A lot Sam, one of the major problems I found is that system analysts miss analyze the system carefully, and with misunderstanding of the job of the quality assurance.