How to Consider the High-Level Design of BS Architecture

1. Association relationship between database tables
From the association relationship, you can see the relationship between entities. Once the relationships between entities are determined, there will be no directional bias during development.

2. url design
From the url design, we can see the general content of each web page. Similarly, after the general content of a page is determined, there will be no directional deviation in development.

3. Interface flow & design
Use Axure to first determine the block diagram of the website flow. The block diagram includes the flow between web pages, the specific content and layout of the web pages. Ensure that the final development results meet the requirements.

Points 2 and 3 seem to be somewhat repetitive, both of which are the determination of the content of the page, but the applicable people are different.
The target reader of url design is back-end development, which is actually interface design. Back-end developers can encode according to the url to obtain dynamic data. But front-end developers cannot see the design of the interface from it.
The target readers of interface process & design are mainly front-end developers, and secondary developers are back-end developers. Front-end development can be laid out and designed according to the block diagram of the web page and then developed, and the back-end developer can clearly see the flow between web pages.
You can also choose according to the ability of the team. The third point can fully confirm the style, content, and process of the interface, which is suitable for teams with front-end developers. Point 2 omits the confirmation of interface style, which can speed up development in projects where only backend developers develop.