The questions I was asking when writing the terms of reference for the development of the site, how to make it as simple and understandable to the customer, but at the same time to limit and maximally document the possibilities of the future product (site). I had to look at many different examples, ways of submitting TOR, reviewed – now I share my ideas and speculation.
It is no secret that TOR, as well as any important document, should have a clear structure, and when drawing up it should be strictly adhered to, otherwise you will get a wild mess in which not only the customer can not understand, but the doer (the developer) and then will long eyes will blink at it all. I chose the following structure for myself :
- Site Sections. Here you need to list all the sections and subsections of the site, which will be available on the site. do not necessarily detail that in each section (subsection), this we will deal later, now we just need to list them.
- Type Pages. Here you need to list all types of pages that you will have available on the site. For example: front page, search result output, print view, etc.
- Design layouts of typical pages. You should not be lazy and omit this item. Here you just need to visually (or verbally) indicate where and what elements of the site will be displayed on the page. This item can be prepared together with the designer, to solve all the conceptual issues. No need to attach ready-made layouts, it is enough to schematically mark everything. This is necessary to ensure that later the customer has no desire to move or move a particular element.
- The software part of the project. Do not be lazy and describe all the technologies that will be used on this site, for example, the server technology – PHP, or list all the client technologies. This point is necessary to protect yourself from the choice of customers hosting, which does not support, for example, PHP, and so, just in case. I think not too much…
- Site content and functionality. Here you can insert a table with the name of the section (subsection), its description and its properties (closed section, dynamic, displayed in an additional window, item in the main menu…).
- Additional Information. Here you should specify the things that, for one reason or another, did not fit into the previous items. They should not be a lot. For example: draw teasers for the following sections and listing these sections, develop a credit calculator (here its description). Some points of this section can be divided into sub sections, for example, the loan calculator : functionality, appearance, technical component, etc.
I think that this structure reflects the technological and design components of the future site in full. If there are any inaccuracies or this TOR is unsuccessful at all I’m waiting for your feedback and comments.
P.S. In the future I plan to write more material on the development of TK: the way of presentation, the formation and conduct of the brief with the customer.