|
|
Approach to Developing a Redbourne Application
|
Developing a Redbourne Application  Redbourne recommend a simple structured process for developing web
applications and deploying them using the Redbourne system. This process
has much in common with rapid application development techniques and
methodologies and can be considered a superset of static web application
development and deployment. The process is summarised in the diagram above. 'Click' on the individual elements
for details of the process steps. Although the process delineates a number of distinct steps - recognise that
the steps in fact overlap and are iterative. At each stage you will learn
more about the problem you are trying to solve and will be able to refine
the previous stages.
The important points of
the process as a whole are: - Agree the business requirements up front in a statement of
requirements, paying particular attention to the clients expectations
from the application.
- It's a good idea to stage the implementation if this is possible, breaking
the application into a number of deliverable stages. This will allow you
to build confidence with the client and to get their site live as
soon as possible.
- The process is iterative. You work on a static 'look and feel', Review
this with the client, make revisions. When you do the dynamic design
you may realise the look and feel needs to be modified.
- Make use of the Redbourne test site facility to test and review
the operational site before making it live.
- Get the client to accept the application before making it live.
- Once the site is live, you can continue with the next phase using the
test site, without fear of damaging the live site.
|
|
|
(loadtime : 13ms) |
