What's the flow?

Hi --

Hello, I'm new to web programming. I want to learn about the process while developing web applications. What must come first? design, database or model?

I think the order must be design->database->model.

What's the best approach?

It depends so much on the project. When I'm working on something alone, at least, I always seem to work on the domain modeling and database design first, and then layer the program logic (the controllers) and design (to the extent that what I do can be called design :slight_smile: on top. But that's just how I work; it's not necessarily a recommendation that you proceed the same way.

David

Agile doesn't change the order of the traditional process of software development it shortens the cycles of releases.

More like this:    analysis->design->develop->deploy->anlysis->design->develop->deploy-

analysis->design->develop->deploy->anlysis->design->develop->deploy- analysis->design->develop->deploy->anlysis->design->develop->deploy- analysis->design->develop->deploy->anlysis->design->develop->deploy- analysis->design->develop->deploy->anlysis->design->develop->deploy- analysis->design->develop->deploy->anlysis->design->develop->deploy

    This increases transparency of status of the project, mitigates risks, and reveals scope and resource usage (velocity)...

~)o gustin

http://www.entryway.net

It depends so much on the project. When I'm working on something alone, at least, I always seem to work on the domain modeling and database design first, and then layer the program logic (the controllers) and design (to the extent that what I do can be called design :slight_smile: on top. But that's just how I work; it's not necessarily a recommendation that you proceed the same way.

I'm the same way, but neither of us are designers :slight_smile:

I think it's a good idea to go straight to the source though. Rails was created out of a 37signals application, so it's tailored to the way they work. Getting Real is their PDF book talking about it: Getting Real.