- Vision - You bring to us your idea at a very high level. Is it an
application of a website? What's it supposed to do? This shouldn't be
more than a paragraph or two.
- Requirements - This is where you have to be as specific as possible
regarding the details of what's being built. What must the software do? Does it have to look like
something?
Those are the pieces your going to have to provide. You can combine these
into one idea if you choose, but it's usually better to start general, then get
specific. After we've got these two pieces established, we go to work
creating a design specification document and a project estimation.
- Design - We provide this to you, and it explains what we're going to do.
Some prototype screenshots will be in this, and details about the technology
that will be used.
- Estimate - Based on what we know at this point, we can give you a somewhat
accurate idea of how long it will take and how much that will cost. Note
that this will be based on the project design at this point - if more things are
added later (because they weren't thought of in the requirements section) a
per-instance estimation will be given and added to this.
At this point if the project is accepted by you, development can commence.
However, prior to code being written, a 25% downpayment must be provided.
You can also ask for the 'current build' at any point, however if the project is
85% done, the amount of the downpayment must be brought to that percentage.
This is all part of the construction phase
- Construction - The software is written at this point. It will be based on
the previous artifacts and built to reflect what the final product visions by
the client.
Once construction is finished, tested, accepted by the client and the software is paid for, it will be turned
over. It is now in support - all defects found will be fixed without
charge, however new functionallity will be billed per-instance.
|