Where to start software design: from the database structure or business logic?

Question

Project management

Gathered a team to design a new product. The team includes a product owner, a database administrator, and backend and frontend guys. There is no team leader, no architect, no system and business analyst. The task of this composition is to design and launch a product. With the translation of business wishes into the language of technologists, there is no. But it's not clear where to start. DBE says that without a description of the business logic, it will not be able to design a database schema. Backenders cannot design APIs without seeing the schema. What do respected experts say?

Answer 1

1. Describing the requirements of business tasks
2. Creating a dictionary of the subject area (domain model schemas, use cases, etc.)
3. Designing a class diagram, a database based on domain_model
4. Implementing classes, databases, interfaces
5. Testing
p.s 4 can be performed in parallel