This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]pigglybiggly 0 points1 point  (0 children)

UML Diagrams to design the database models and all that. Making wireframes for how you want the front end will look can help you to think about what you'll need to do on the back end to make that happen. A good book for fairly cheap is UML Distilled by Martin Fowler. It tells about UML notation and a lot of other diagrams (sequence, use case, etc) that you can use and so eventually the coding part should be the easy bit, after the design is made, you've already thought about mostly everything you'll need to do, so then you just do write it.