oh this is great! thank you for your input.

Could you expand on the UML diagram part? what actors, entities, functionalities and relationships would you consider/include in such a diagram? What assumptions would you make in the design?

as for time/pace complexity, could you give examples of what considerations should be in mind for the website? Im thinking scalability could be one, especially with the other question...

Suppose you join a development team and they are working on a web visualization product developed in ASP.NET, HTML, CSS, Angular, SQL Server, and C# that provides data insights to doctors (i.e. ROI, revenue, best brands vs worst brands, etc.), as well as internal users.

The team prides itself with the following technical qualities: Quality, Reliability, CI/CD (Continuous Integration and Delivery), as well as Technical Acumen
...