The structure of the technical task

The questions that I asked when writing a technical task for developing a website, how to make it as simple and understandable for the customer as possible, but at the same time limit and document as much as possible the possibilities of the future product (website). I had to look through a lot of different examples, methods of presenting TK, I looked through it - now I share my ideas and conjectures.


It’s no secret that the TK, like any important document, should have a clear structure, and when compiling the assignment, it should be strictly followed; a long time later, his eyes on all this will be swollen. I chose the following structure for myself:

1. Site sections. Here it is necessary to list all sections and subsections of the site that will be available on the site. it is not necessary to describe in detail that in each section (subsection), we will deal with this later, now we just need to list them.
2. Typical pages. Here it is necessary to list all types of pages that you will have on the site. For example: the title page, the search results, the appearance of the print, etc.
3. Design layouts typical pages. Do not be lazy and miss this item. Here you just need to visually (or in text form) 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 conceptual issues. No need to put ready-made layouts quite schematically mark everything. This is necessary so that later the customer does not have a desire to move or move one or another element.
4. The software part of the project. Do not be lazy and paint all the technologies that will be used on this site, for example, server technology - PHP or list all client technologies. This item is needed in order to protect yourself from the choice of hosting customers that do not support, for example, PHP, and so, just in case. I think not superfluous ...
5. Content and functionality of the site. Here you can insert a sign with the name of the section (subsection), its description and its properties (closed section, dynamic, displayed in the additional window, item in the main menu ...).
6. Additional Information. Here it is necessary to indicate those things that for one reason or another have not been settled in the previous paragraphs. They should not be much. For example: draw teasers for the following sections and list these sections, develop a loan calculator (right here is its description). Some points of this section can be divided into sub sections, for example, a 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 TK unsuccessfully waiting for your feedback and comments.

PS In the future I plan to write more materials on the development of TK: the method of presentation, the formation and conduct of brief with the customer.