Could you share a good technical task for the development of a website/web application?

Question

Preparation of terms of reference

Hello!
I really want to look at an example of a good, suitable technical task for developing a site, but on the Internet there is either "water" or unsatisfactory real examples. If you have seen a good TK somewhere, or you have one from your own practice (and you can show it to the public), I will be very grateful for the link / file.

Answer 1

Good terms of reference is a very streamlined term. "Good" could be called a technical task that meets certain requirements. But already these requirements, depending on the scale of the product being developed, the development methodology, the customer / contractor and other factors, can vary greatly.
So, for example, if you are working with a state or near-government customer/executor, it is very likely that you will have to prepare TOR in accordance with the requirements of GOST-19 and 34 (in particular GOST 34.602-89 and GOST 19.201-78), which involve the creation of very formal and detailed documents.
If you do not work according to a waterfall or similar methodologies, but use Agile approaches, it is very likely that detailed and worked out from general things to the smallest details of the TOR will not suit you, since it will not provide the required flexibility of the approach.
For some kind of design development (style, logo, graphics), when there is great initial uncertainty about what needs to be done, a fairly general brief may be the best option.
Summarizing: decide on the requirements for technical specifications, and, starting from them, you can already look for some options.

Answer 2

I have never seen a voluminous and all-encompassing TK. Usually this is a layout and a bunch of edits to it.

Answer 3

look at mine. Good or bad, you decide.
https://vk.com/doc399047259_464509206

Answer 4

Good terms of reference for a particular project are the result of good work by a specialist project manager.
The key to a good TOR is:
1) Work at the lead stage
2) Meetings and collecting the most necessary information
3) Survey of the customer's business processes
4) Preliminary technical examination of all possible problematic points
5) Prototyping - Mockups, if there are a couple of squares, then most likely a fiasco will await you 7) Preparation of the necessary applications for the TOR (Estimate (list of works), Schedule of work, List of page layouts, Warranty obligations (detailed), etc.) 8) preliminary examination of external services for integrations , etc. 9) Writing TK
you
10) Proper Project Evaluation
That's when you at least do this, then you can safely call your TK good.

Answer 5

In fact, TK should be concise and simple. So that you can easily understand the purpose of screens / blocks / functions and their relationship. This is enough to start writing to the spec.
But the specification itself, where all screens and business processes are decomposed to the level of classes / objects, database architecture, third-party solutions and api methods, will not be written by anyone except a tech lead or developer. And only this can be called a good TK, which you took and saw the code.
Therefore, the question is unlikely to have an answer that satisfies you.

Answer 6

Хороший план по подготовке ТЗ описан в моём блоге.
1. План создания технического задания (ТЗ)
2. Этапы проектирования сайта

Answer 7

ТЗ вместо ТЗ подойдёт.
Если реализуете такой веб-сервис, можете считаться юниор-программистом.
https://docs.google.com/document/d/1yk5kt1oV4278Lo...

Answer 8

A few points
1) It is necessary to describe all the fundamental positions that are included and not included in the development: for example, multilingualism or support for old browsers can be an unpleasant surprise
2) The question of how much detail each block needs to be described is open, sometimes it’s enough, sometimes screenshots are attached, it is important to describe the useful action
3) It is much easier to allocate 10-20% more in the project budget for unforeseen wishes of the customer than to prescribe all the details to the last comma and then still quarrel with the customer, since it is impossible to take everything into account
An example of a brief TOR for a one-page site , the description of the blocks is not complete, it is written according to the already approved design.

• Ability to set a title
  
• Ability to change text
  
• Possibility to change background color
  
• Ability to change text position (left or right)
  
• Possibility to set photos