Subsystems, purpose of lists?

Question

1C

Here is a picture in which, according to the textbook, I arrange the subsystems in which this or that list will be displayed.
But I don't understand the logic at all.
1) Clients: service subsystems and accounting.
2) Employees: services, salary, but for some reason accounting is not marked, but if you type in Google, then:
But basically, his tasks include maintaining the company's financial records, compiling the organization's budget and income and expense reports. Also, the specialist is engaged in payroll, preparation and submission of reports to the tax office and funds.
3) Nomenclature, something incomprehensible in general, what is it in general and what should be in it? The book says:
Directory Nomenclature will contain information about services,
provided by Jack of All Trades LLC, and about the materials
that can be used in this case.
On the basis of what did the book decide this way?
4) Warehouses: Materials, services, why is there no check mark for accounting? After all, if you google it, then:
This model of the accounting structure is used in medium and large organizations. At the same time, departments can be created in the accounting structure:
material, which keeps records of the receipt and expenditure of inventories;



And what am I supposed to understand from this? How should I decide what belongs to what? Or write a standard that you personally work to and adhere to.

Answer 1

In my opinion, you are asking the wrong question in Google that interests you. The answers found are irrelevant to the problem. Well, here's roughly on the points:
2) Employees "for some reason, accounting is not marked." And the accounting department is not interested in each employee individually. It will take into account in the expenses of the enterprise one total amount - the salary of all employees. And each individual employee will apparently be engaged in the subsystem Salary.
3) The nomenclature "what is it in general". A list of services that the company provides to customers, and a list of materials that are required to provide these same services. "Painting of walls" - service. "Can of paint" - material. These will be the elements of the Nomenclature directory. It is related to all subsystems except Salary.
4) Warehouses "why there is no accounting checkmark". A warehouse is a specific physical place where, for example, the same can of paint lies. There may be several warehouses. And the accounting department only needs to know that the organization has so much paint, for such and such an amount.
All this division is conditional, this is the vision of the developer. You can put all the checkboxes - nothing will break. But why does a person who deals with personnel and salary in an organization need information about customers? At least superfluous, and perhaps he is not supposed to see her!

Answer 2

And what am I supposed to understand from this?

Ask the author of this course.
refer to the original source:
https://its.1c.ru/db/pubdevguide83/content/27/hdoc...
https://its.1c.ru/db/v8std/content/543/hdoc/_top/p. ..

Answer 3

write a standard that you personally work to and adhere to.

The main standard for everything: common sense !
First, make the functionality that is asked of you in the TOR, and then, using subsystems and functional options, create convenient desktops for users. What difference does it make from how many subsystems you can open the Employees directory, if your salary is calculated incorrectly in principle?