|
|
|
Application Development. Our Process.
The process we use to write our web applications from start to finish depends on how clearly the client envisions the final product.
For our clients with ideas for new web sites venturing into previously unexplored territory or taking an existing concept and adding a new twist (which are usually start-ups), we take the iterative approach. For corporate clients who know exactly what they want already, we map out a solid, formal specification and produce flowcharts.
When we're writing an application with the iterative approach, we'll choose to go with Ruby on Rails. The iterative approach is well-documented in many places on the web, but in short, it offers several major advantages for the client. The two biggest advantages are the ability to see something working in a very short time and the option to give input throughout the entire development process as changes are made. With complex systems such as software, this ensures that the project is on track by giving concrete proof that progress is being made.
We recommend this method for projects with complex logic and changing scope.
Now, when writing an application under more rigid guidelines, we produce a document called a Software Requirements Specification (SRS). In as much detail as we can muster, we describe the features of the site as we understand it. We shoot this document back to the client, they read over it, and send us any changes we have to make to make it fit the vision. This method of development and communication is better suited for projects where the specifications are well-known. The advantage of doing things this way is that less effort is put towards re-writing and re-designing, as with the iterative approach.
We recommend this method for projects with simpler logic and rigid scope.
