What is the best workflow for a web application?

Question

I am going to start a web application. Before starting, I would like to get some tips on what the best workflow / order is for creating a web application like this.

My project will consist of a server part with PHP and MySQL. The client will be XHtml, CSS and jQuery. AJAX will also be used.

I am sure that this may depend on certain situations, but, in general, what is the best procedure for developing a project with these credentials?

Should I start server side development first? Or should I start from the client side? Or should I do both at the same time? What about the database - should this be a priority? Then maybe DAO?

Answer 1

Start with the data first. Server-side data is the constant core core of the application. If this data model is incorrect, you have nothing.

You should be able to unit test the data model to prove that you have the right attributes and relationships. It does not require much. A few test cases for insert, update, and query.

You will support this data model with internal processing.

This should also be checked on the module to demonstrate that it works, and does everything necessary for your data model. It will be a little harder as this processing.

You can then think about the data model that web services provide Ajax.

, , JSON . , , front-end GUI. .

, Ajax, .

Answer 2

, , ().

. . - .

"", GUI, ... - . , , , , , -.

Answer 3

, , , . , , , .

, , , , , , ajax, , . , , , - .

Answer 4

, , , , - ...

• , , .

• . . , . . .

• , . , ...

---

pets
----
id
name
species
# etc...

---

• . Rails. DDL .

• DAO - , , .

• Then I usually process the application object with an entity. Get a view and controllers. Quickly switch between test code and implementation code.

This is a general sequence, but there are corrections all the time and so on. You will need to go back to your database design and develop it when you create the actual functionality.