[otto_ortega]

I totally agree with this. On my experience that is the approach that works best.

1 - Define the requirements 2 - Design the UI AND its behavior

From seeing the UI and understanding how it is expected to behave you can get a clear idea of what entities and attributes you will need, from there you can derive the database design.

3 - Design the database in a way it fits all the data you need to display on the UI, and all the data you don't need to display but need to make the UI behave in the way you need it.

4 - Code the business logic required to link the database to the UI, in whatever language you choose.