How are the functional and “entities” correctly described in the design?

Question

Design

How to correctly describe the "entities", functionality and properties, the meaning of each function of the project?
Where to start describing, for example, the possibility of an online broadcast (webinar)?

Answer 1

Functional requirements - a list or a tree like yours. What you have in the screenshot is more like a structure, not a functional requirement.
We read: Software requirements
For the description of entities, look towards UML or ERM .

Answer 2

From experience: simpler is better. If you have a website or mobile application, the following format will do:
1) Structure.
2) Visual component.
3) Architectural component:
- data types;
- lists;
- functionality.
An example for a web service:
Structure -Main
-Channels
--Channel
1
page --Channel 2 page -About the
service
... -then. B should include a list of the latest news (link to a detailed description of the news list). Architectural component
-Data types --News
---The data type is designed to account for news. The data type must include the following attributes:
----Header* (type: string);
.....
-Lists
--Latest news
---List of the last 5 news (reference to "News" data type). The list should include:
----title;
....
--- The list must be sorted by date, descending.
In functionality, you describe what could not be organically described in the sections above. For example, something with a referral system.
====
And further. If your project is being implemented on a ready-made platform, for example, some CMS, BI solution or accounting system, I recommend contacting the appropriate consultants or independently studying the capabilities and limitations of the chosen platform. Otherwise, you can spend time describing what cannot be implemented due to technical limitations.