title: Functional Software Requirement Specification and Project Timeline
body: <p>I don't have any experience in writing Requirement specification.</p>
  <p>I am writing a new in house web application in .Net and i have been given a document with all the requirments for this new software.</p>
  <p>There is a (in house written) time tracking system in use at the moment but i have been asked to redesign it in .Net.</p>
  <p>I am the only one in the company with software development experience and as this is internal software so they are not expecting me to write very detail documentation for that.</p>
  <p>I have designed the ERD diagram for the database schema, I have also divided the requirements into different sections in the excel sheet and set there priority (L,M,H) and  Phases (1,2,3) for delivery.</p>
  <p>My line manager has asked me to define the timeline for this project which is bit difficult as I will be working only 3 days a week on this project and don’t know how long it will take to complete the phase 1 as there are few other projects I am working on.</p>
  <blockquote>
  <p><strong>Do I really need to a Requirement Specification document because I have been given one in the word documents (in simple words) or Should I just stick with the one I have designed (divided in different sections). If I do need one then is there any example I can follow?</strong></p>
  <p><strong>Do i also need a Function specification document? Is it different than Requirement Specification?</strong></p>
  <p><strong>How do you normally set the timeline for the project? I have just defined the different tasks from database development to software development including and set the roughly days next to them.</strong></p>
  </blockquote>