Our Services

Project Description

An online dynamic estimate and quotations system which allows our client to interact with their customers in a more efficient and cost-effective manner. Our client can submit quotes to which their clients can accept, query or reject. All communication is online, with alerts being sent by email. The system has full security, audit trails, alerts and reminders as well as comprehensive user support and administrative sections

Technologies Used

Written in ASP.NET & C#, using nHibernate to generate SQL.

Initial Phase

We were approached by our client with an idea for a website for an online quoting system. We held initial meetings to understand the purpose of the website and how our client wanted it to function for their customers. We began by producing a functional specification and a 'static' website so that the client would have a visual representation of our software. This ensured that both parties knew exactly what kind of software was being built and demonstrations enabled the client to give feedback. It also allowed staff and management, not involved in the initial meetings, to give their input. Therefore the software could be 'sold' throughout the business.

Development Phase

Once the client had agreed the specification the development phase began. The software was designed and written in a modular way to allow new functionality to be added which would have minimal impact on the entire system.Testing any new functionality is ringfenced to the module updated. Developing in a modular fashion allows the code to be re-usable for other projects. The software was written using .Net and Ajax running on a MSSQL2000 Database. At all times we kept the client fully informed of progress and any issues that arose. Due to our work in the initial phase there was very little wasted development time.

Testing

As development was completed we began 3 phases of testing. Initially we carried out unit testing, our development teams testing. We then gave our client access to our task management system so they could view all issues being raised and there resolution. We wanted to make our testing process as transparent as possible. As this was progressing, test scripts were prepared to ensure all functionality was tested and business processes were followed. These tests were not performed by our development team but by staff who, upto this point, had not been involved in the project. This allowed fresh sets of eyes to view and test the software. Once Fairmort's testing phase was completed, a demonstration site was put live on the internet to allow our Client to begin their QA phase and 'play' with the software. We also gave the client our test script results to show the testing we had completed. As the client began their testing we began to complete all the required documentation and help files.

Go Live

Once testing was complete, we arranged with our clients technical staff the installation of the software. We also arranged post go-live support. All documentation was handed to our client, documentation that we keep up to date.