When an off the shelf or purchased Web application doesn’t meet your needs, you will probably start thinking about custom development. A few things you should think about first are:
- Cost. Custom programming/application development from scratch is expensive.
- Have you thought the functionality of the application through thoroughly?
- If #1 is not an issue and you have a clear idea of what you want, the next step is to develop a requirements document. This is one of the first things you need to provide to your developer for a quote on the development work.
What is a requirements document?
A requirement document defines the functionality of the application from the server platform to the last click of the mouse.
Depending on the complexity of your application, you may need to define the following in detail.
- Project Overview (purpose/indented audience)
- Server platform
- Programming language
- Specific project features
- User interface (define in detail)
- Admin Interface (define in detail)
- Flow Charts
- Decision tables
- Navigation structures
- Browser compatibility
Why do I need a requirements document?
The requirements document ensures that the customer and the developer are communicating effectively to meet the common goal of creating a custom application.
Going back and adding/changing the app in the final stages will extend the scope of the project and push the roll out date back. There is nothing worse than hearing “It’s going to be another 10k to add that”. Doing your homework up front prevents this from happening.
For sample requirement documents search Google for “web application requirements document template” or just click here.
– See more at: http://www.awsp.com/blog/web-design/requirements-document/#sthash.aLs6DHMP.dpuf