How would you structure your workflow for a web application ?

Posted by cx42net on Stack Overflow See other posts from Stack Overflow or by cx42net
Published on 2010-05-02T15:24:00Z Indexed on 2010/05/02 15:27 UTC
Read the original article Hit count: 159

Filed under:
|
|
|
|

Hi !

When designing a web application (or something else), it's good to have a workflow, and it's better to have a well ordered one.

Starting with this idea in mind, I'd like to know what is your process from having an idea to maintain this great working project.

For me actually, the process is the following one :

  1. Having the idea
  2. Checking this project already exists, and how it works
  3. Describing on a paper its functionalities
  4. finding a good and adequate name for this (and checking the domain availability with WHOISMyProject)
  5. Making a quick layout of the project on a paper
  6. Designing the project (via TheGimp, Photoshop, etc)
  7. Making a complete mockup of each pages
  8. Developing a prototype of the client-side application (with false datas)
  9. Developing the server side
  10. Testing
  11. Making the documentation/help/faq
  12. Releasing the project
  13. Maintaining it.

Would you change the order of some points ? add/remove some ? I would please to know how you do that. I'm looking to set up a perfect workflow in order to make my project become real in the best way possible.

Thank you for your opinion !

© Stack Overflow or respective owner

Related posts about Workflow

Related posts about process