Developing a Redbourne Application

Statement of Requirements

A Statement of Requirements (SOR) should form the basis for agreeing to undertake a project for the Redbourne system. The client and the integration partner should work together to agree this as part of negotiating the design contract. The following list highlights some of the things that should be considered upfront in any successful application development. Note that this is not an exhaustive list!

• The business requirements for the application. Why does the client want a web application - what is the perceived business benefit. If this is unclear there is a good chance that the application will be perceived as deficient by the client.
• Required performance, availability and anticipated traffic load/visitor load as appropriate.
• Data Maintenance. The application may be fed from external data - for example an existing client database. How is that data going to be transferred and who has responsibility for the transfer. Has the Client understood the internal business processes that may need to change.
• Security Requirements. What are the clients expectations? Is a secure site appropriate, or an insecure site with authenticated access, or an open site?
• Understanding of both the 'public' interface to the application and any (hidden from public view), management interface requirements.
• Expected/required timescales.
• Delivery phases. Ideally it is a good idea if a web application development can be delivered in phases. Both the client and the partner can benefit from a phased approach: The client by having an active web application faster; The partner by proving the application, and their reputation with their client.

Only once the requirements are clearly defined should serious work begin on the application design.