Approach
We have found that an iterative user-centred approach to software design and development works best. In our RAD based methodology there are number of process steps outlined below. We use a number of visual modelling notations such as SSADM, UML and Entity relationship to build a visual representation of the system, before we commence development.
Step 1: The PBQ
We start this process by completing a Briefing Questionnaire during the proposal phase. This is an interactive meeting between you the client and us where we produce a first cut set of outline designs based on our business frameworks. This meeting provides us with a good understanding of your requirements and thus allows us to a produce a qualified proposal.
Step 2: Proposal delivery and presentation.
The next step is to work through the outline design and translate it into a written proposal. Which is then sent to you in both electronic and printed formats. We then build a prototype, i.e. the shell of the system with a number of screens or web pages; just enough to give you an idea of what it will be like to "drive" the finished product. Following this we then hold a short proposal meeting with you; where we:
Present our approach to the project
Demonstrate the solution prototype
Hold an open Q&A session
This meeting provides real opportunity for client stakeholders to gain a deeper understanding of the project under proposal and to scrutinise us as a potential supplier.
Step 3: Design (Paper build)
When a project is awarded we undertake the requirement definition phase. We build (with you) a paper model of your system. We find that building a paper model of the system is much more tangible than writing a quasi-legal system specification, and is therefore much more effective. We do this in a series of weekly JAD (joint application development) sessions giving you, the customer, time to reflect on decisions in between.
Step 4: Project review
When the paper build is complete we hold it up to the light and look for holes in our understanding via a project walk through this gives you a chance for a final review and signoff. So by now we will of asked you in four different ways and levels what you want from your solution. These are:
· Via the project brief questionnaire
· Via the proposal prototype
· Via the paper build
· Via the project walk through
We now feel confident about freezing the system requirements and starting the main development work.
Step 5: Development
Once development commences we will deliver work on a phased basis. We supply and install the phased release on your system. We then ask you to test and sign-off the phase within a week of receipt of each delivery. After signoff you can start using the release.
Step 6: Deployment
We use a number of methods of deployment. For a new deployment we will always attend your site and install the application. Depending on the technology used and our means of support access we may remotely install subsequent phases.
Step 7: Support
We offer support for all our systems.
Billing
Our billing will be staged too. Typically we ask for 30% of project cost on award of the project. From there as each section of work is delivered we will ask you to conditionally sign it off i.e. say it is acceptable except for x, y, z. We will then bill you for that section of work. When x, y and z have been fixed we will ask you for a full sign-off of the work. The invoice falls due when the full sign-off has been given.