What should be in a serious TK?

Question

PHP

Content:

Content
Site development
time Multilingual
General requirements
Services presented on the site
Requirements for content management system (CMS)
Product catalog Product
characteristics Product
images
Store management
Site design and management
Feedback
Orders
Accounting for goods in stock
Search engine optimization
Payment systems
Currencies
Speed ​​of work
Work with goods out of stock
Online consultant
Delivery of goods
Registration of sellers
Requirements for layout
Encoding and DOCTYPE
Crossbrowser compatibility
Micro-markup , micro-formats and micro-markup
Display of the site in various devices
Correct operation when real text is typed in, layout reliability
Correct operation on Windows, Mac and Linux
Accessibility when
HTML5 Forms images are turned off (loading)
Correct tag structure
Workability when JavaScript is turned off
Workability when Flash is turned off Layout
style features
SEO Requirements
Supplement to Terms of Reference

TK for an online store like dx.com. What did I forget?

Answer 1

Everything is somehow spread out... and not systematized...
Nothing is written about the workflow of the store, nothing about interfaces for employees, and this is the most important thing.
About integration with accounting.
Multilingual? Which? Only the interface or the Product Catalog should also be multilingual?
In general, you still need to torture the customer for a long time in terms of requirements ... and if you are a pro, it’s better not to mention
things related to technologies (in most cases JavaScript, Flash, HTML5, Encoding and DOCTYPE
Cross-browser compatibility Micro-markup, micro-formats and micro-markup for the customer is an empty phrase)
Also the customer will be interested in how efficient the workflow is in order to hire fewer workers.

Answer 2

You do not have a clear TK structure. I would offer you 2 options for redoing:
1) Quick. Add to the beginning of the TOR sections about the purpose of the online store (why is it needed) and the tasks that need to be solved to achieve the goal. Next, describe the IM structure, then describe each page of the structure - what functionality should be, how the interface should work, etc. After the description of the pages, place other requirements that are important for your project: SEO, multilingualism, data transfer (if any), admin panel, layout, etc.
2) Less fast. Everything is the same as in paragraph 1 +
add a section describing the entities used in the IM, lists, functionality, for example:
-Data type "News", attributes "Title (string)", "Content (html)";
-List "News", consists of news (data type "News"), sorted by date in descending order.
And in the description of the pages, refer to the corresponding entities, lists, and functionality, for example:
The "News" page should include a list of the same name. Each element of the list should be a link to the corresponding news page.
This will allow you to better work out the logic of the project, identify controversial and ambiguous points at the design stage.
On the other hand, it is important to note that if the TOR in its current form is guaranteed to provide the same understanding for all project participants, and takes into account all the necessary points, then leave it in this form, why do you need to do extra work.

Answer 3

If you want to do everything in a completely adult way, look towards the SRS 830 or its domestic counterpart - GOST 34. (But, I suspect, this is quite harsh for your purposes).

Answer 4

And "TK" what do you make? If, say, the front end, then not bad for a start.
If there is a whole online store (in fact, a new e-commerce engine), then in these points there is not even a millionth of what you will have to face.
For each of these items:
Catalog of goods
Characteristics of goods
Store management
Orders
Accounting for goods in stock
Delivery of goods
Registration of sellers
you can write a dissertation. And these are far from all the moments that you will have to face when working with an online store, even on a much smaller scale (although I see this dx.com for the first time, but it looks like a modest analogue of aliexpress and others like them)

Answer 5

Possible:
- Server requirements
- Legislative framework (152-FZ)

Answer 6

When compiling the TOR, I am guided by logic - Describe what is incomprehensible or non-standard. You can evaluate the project for risks, highlight which elements of the project have the highest risks and begin to describe them. I never plan content, it appears automatically through a convenient Word feature - "auto-content".
At the end of writing, I format, move the text around the dock for beauty. When I write TK, I just write in order without structure. Then I give it to the developer and tester for testing. They comment on the TK by asking questions about what is not clear where, or offer their own version of the description if I wrote it inaccessibly / incorrectly. Then I combine the edits and give them to the management. The management adds its 5 cents and can be shown to the client. (constant display to the client takes place as the TK is written, so that it doesn’t turn out that you wrote nonsense for 2 weeks that the client does not need).

Answer 7

The "serious" TK should contain the following things:
1) The goals of the project that will be solved with the help of the project - there is not a word about the project. Here are those participants, from the problem, and how they will be solved if the product exists and works successfully (not a word about the product here!)
2) Project objectives - how the goals will be achieved with the help of the project. You need to list the success states of what describes "success in achieving the goal."
3) Solution image - scripts, screens, data structures. In other words, the answer to the question "What does a successful product look like and how does it work?".
It is advisable to leave the third paragraph at your discretion and responsibility, and sign the first two. It is the image of the solution that you form as a specialist. The main thing is to fix the task.
Read more here -www.deppkind.com/product_requirements_document
Example here - files.deppkind.com/DemoofRequirementsDocument.pdf