Thank you Konstantin for the details, that is exactly what I was looking for which is coming in 6.3 version. Let me briefly explain what I am looking for in case it helps in setting an example when you are documenting.
I start with your example as starting point. Customer Management is a component where it will have everything to work as application e.g. entities, controller, screens, services etc. There will be several other components e.g. Inventory Management, Accounting, Payroll management , Accounts Receivable etc.
Those components are almost independent except some touch points, Sales in Customer management will use the entities in Inventory Management, Invoice will have link with Accounts Receivable and Accounting etc. Therefore, in this case, there will be an use of Entities of Accounts Receivable in Customer Management and vice versa.
In this case the standard components are extended to meet specific industry specificity. Let’s take an example to simplify. Sales Order entity is extended to two different industry category say, Make to Stock type of business and Engineer to Order types. The standard component will have standard cross industry attribute of a sales order that is common to all industries and when there is a need of specific industry, the entity, controller, screen etc. will be extended. I understand from the answer to my other question that extending screen is not possible in the studio. I’m not sure if you have any plan to include it in 6.3, if yes that will be great! If not now, documentation with a practical sample app will be helpful.
I am eagerly waiting to read and use the documentation to proceed with this approach in my development. In case you need any help in sample application featuring this, let me know (you can e-mail me).