Where can I find samples and best examples of TOR for software development?

Question

Programming

Sobsvtenno a subject, it is possible English.
PS
Google and Yandex give some kind of rubbish like:
1. GENERAL REQUIREMENTS
1.1 The terms of reference are drawn up in accordance with GOST 19.106-78 on A4 sheets in accordance with GOST 2.301-68, as a rule, without filling in the fields of the sheet. Numbers of sheets (pages) are affixed at the top of the sheet above the text.
1.2 The approval sheet and the title page are drawn up in accordance with GOST 19.104-78. The informational part (abstract and content), the change registration sheet may not be included in the document.
no, it's not necessary.
You need:
1. TOR for the development of a successful product, for example, (simply) Excel
2. a checklist of what should and should not be in a good TOR.

Answer 1

It all depends on what development methodologies you use.
Most often it all looks like this:
1) First, user stories (user stories) are added, the functionality that you want to have in the program. They consist of one or two sentences, briefly describe one single function. For example: I want users to be authorized with confirmation by email; I want the user with the "admin" role to have his own page for administration; i.d. There should not be any technical nuances in the stories, only "I want" the customer (well, or yours).
2) Then a roadmap is drawn up, in which you describe each step of the work of this function (user story) from the user's point of view:
1. Main page.
1.1 In the upper right corner there are fields for authentication (for login and password). Nearby is the "login" button and the "register" link.
1.2 If the authentication is successful, you go to the page ... and the message "Welcome ..." is displayed.
Then, based on this map, prototyping is done, tasks are allocated, if necessary, divided into smaller subtasks.
To see other people's TK, climb on someone else's code on github. There, very often people describe their roadmap.

Answer 2

About a couple of years ago, I needed to structure the database of contacts with clients. Invented a little bicycle solution for my needs. TK can be downloaded from the link .
As I remember now, at that time it took me 25-30 hours of pure time to compile it. At the beginning, I did not know what tools to use so that the performer would understand all the nuances correctly, so I rewrote a lot. Also, in the process of writing, new ideas constantly appeared, which, as it seemed to me, could no longer be included in the TOR.
As a result, after the release of the first version of the program, it took another month to finalize it. I used it for about six months, all this time I collected information that could be improved. Then, having gained experience and knowledge, I wrote a new TOR, which consisted of 20 sheets and about a dozen additional files with pictures and tables. It took about a month to draw up the second TOR.

Answer 3

It seems to me that a successful product can only be made using agile, iterations.
I never managed to plan everything and foresee all the little things.

Answer 4

This video helped me a lot
.

Answer 5

My opinion, if no one limits you in the standards for the implementation of TK, then we must proceed from the following:
1. Time.
2. The usefulness of TK for developers and others, but primarily for developers.
2.1. Utility is primarily a description of the business logic.
2.2. Prototype (I do in Balsam).
2.3. Connections with subsystems and integration.
2.4. Data structures and loading.
I write TK both in accordance with GOSTs and in corp. standards, but it is most effective when no one sets limits.
There will be questions write in the LAN.

Answer 6

I can recommend books
www.ozon.ru/context/detail/id/30958003 Domain
-Oriented Design (DDD). Structuring of complex software systems
www.ozon.ru/context/detail/id/27995134 Development of software requirements

Answer 7

The Edison company was on the hub and in their articles they shared links to examples of their TK. In general, if you read https://habrahabr.ru/company/edison/blog/267569/ and https://habrahabr.ru/company/edison/blog/267671/ , I think it will not be difficult for you to find examples of their TK

Answer 8

Google literature and courses on managing software requirements, agile software requirements
Here is a good book www.amazon.com/Managing-Software-Requirements-Appr...
Everything is mostly in English, in Russian only rubbish or normal translated books, such as
www. piter.com/product/iskusstvo-upravleniya-it-pro... (by the way, from microsoft dude).
With the possible exception of Beskov's courses and individual articles, posts by different authors.
PS: there are no universal checklists and schemes here and cannot be. Different types of products, customers, conditions require different requirements.

Answer 9

They wrote more on Habré. There was a vulnerability on some freelancer site, all files from personal correspondence could be found through Google in this way: site:freelancer.com filetype:pdf and there the output is from real TK. Not really sure about the site.

Answer 10

For the second point, I recommend focusing on GOST34
www.rugost.com/index.php?option=com_content&view=a...
www.rugost.com/index.php?option=com_content&view=a...
Any serious customer always works with caution on GOST, and you don’t have to invent anything yourself, you just need to remember that GOST is a recommendatory standard and, for example, all items that should be in the TK according to GOST, don’t have to be in your version :) It
’s a little more difficult with foreign ones - they they are not always guided by ISO / IEEE (I did not have to work with those who would require compliance - everyone had their own TOR format)
Therefore, it is better to immediately discuss the structure of the document. :)