I usually start from the middle - sketching objects/entities and
operations that should be applied on them.
Then goes a first version of workflow diagram for client-server
communication and a design of server calls.
At that point there's enough material to start sketching UI and
normalizing data for a database.
Usually I never get one side completely solid while there's design work
to do on the other side, also the client-server workflow diagram get's
heavily updated while working on UI mockups.
It's also quite usual to discover missing points in functional
requirements during UI/services/database design.
Speaking of tools, I find it really helpful to use some spreadsheet for
designing (and even documenting) object structures.
In recent projects I used it heavily for linking my data structures to
3rd party objects, generating JSON test objects etc...
Hope you find some of these tips helpful :)
Cheers,
Tomislav
On 26.8.2015. 18:37, mark goldin wrote:
This is is out of topic but can someone please share personal
experience/other resources about how do you start designing a new pretty
large project? What I mean is that every web based application would have
UI and a backend and they both non existent for the new project. Would you
start designing your UI based on business requirements and then proceed to
database already knowing what the UI needs or would you start designing a
solid database foundation first?
Thanks
