Specification Writing

Following a set of meetings to gain an understanding of the challenges facing your business, a proposal is presented to explain how you will be working with us if you decide to proceed. In this document, we will outline the key features that we expect your system to benefit from including a overview description of the functionality you can expect and on which we have based our price.

It is important that you are happy we have covered all of the key components before agreeing to proceed with us to the next stage. We use our technical experience and business knowledge to accurately estimate the length of time required to develop the software. Based on this, the cost of your software is determined.

Before a single line of code is written or database table constructed, your system is mapped out with a Technical Specification. Following a short lead time, we will arrange to visit you to begin the requirements gathering process. For a system of this size, we would expect this process to span several weeks including multiple visits to liaise with staff and will consist of two members of our development team; a business analyst and technical programmer.

During these visits, key staff within your organisation are asked to spend time assisting us to understand precisely what your software needs to accomplish. Through this interaction, we develop a more detailed understanding of the issues you face, ask questions and help devise the best solution to meet your challenges.

On completion of our visits, we will collate the information we have gained from you, resulting in a specification document that describes how the system will function; options available to each type of user, validation, the results of each action etc.

< Back to Development