Customized Software - Evaluation & Development Process

This is an outline of the various stages of the software development process from initial consultation to final implementation. Note that you are not obligated to proceed to any stage. If you decide at any point that you wish to stop the process, you may do so.

Summary Analysis

We start off with a summary analysis of your requirements. This is usually accomplished through a discussion of the expected functionality of the software. The purpose of this analysis is to determine an approximate time frame and cost for development.

In-Depth Analysis

Upon approval to proceed, an evaluation fee is paid in advance. We then do an in-depth analysis of your requirements. This can take from several hours to several days and is accomplished through interviews, fact finding and, if possible, a first hand understanding of the environment in which the program will be used. More ...

Concept of Project

After this analysis, we are able to put together a conceptual design on paper. This concept of project is an outline of the project that is created based on the in-depth analysis. It is detailed to the point of providing a road map for continued development. The estimated time needed to complete the project is based on this outline. This extremely important and critical stage makes sure that we are headed in the right direction by making certain that all the requirements have been met, understanding how they will be met, and if the intended method of operation is acceptable to you.

Cost and Payment Terms

Normally, a more accurate cost is provided following the concept of project stage. Note that some very large projects may be too complex to provide an actual cost and will be developed on an estimated schedule and budget. It should also be noted that, despite the efforts put fourth in the concept of project stage, changes made by our clients are inevitable - usually resulting in increased costs.

An up front payment in addition to a payment plan will be put in place prior to the next stage. More ...

Detailed Design on Paper

After everything is clearly outlined in the concept of project, a detailed plan is created on paper. This is the most efficient, and consequently cost effective, method of designing a software program. As this involves the actual mechanics of how the software will eventually be written, technical questions always arise during this stage which will often require input from our client. Identification of issues early on, and in this fashion, greatly helps to produce the most stable software possible.

Prototype

The prototyping stage provides a ruff visual representation of the planned user-interface and how that interface will meet your requirements. This stage is extremely important for determining usability, as it is our design philosophy that the programming work with the user-interface and not the other way around. Designed for our clients to actually experience the concept of the program, you will be able to physically work with some of the parts of the interface and may also see some simulated results from the prototype program. You can look at the prototype as being all flash and no substance. But it does fulfill it's objective of developing an appropriate user interface. Once feedback has been obtained about the suitability of the prototype, the actual programming will begin.

Programming

The process of actually developing the software will proceed during the weeks and months ahead. Status reports will be made available as prominent sections of the project are partially or fully completed.

Quality Assurance

During and after the software is developed, testing is performed by the development team to ensure that everything works. However, despite all reasonable efforts, actual users will make different assumptions of how to use the program and will invariably encounter problems. Consequently, the next stage of testing, real world testing, is performed on site. This generally requires the program be used on a test basis, while current methods for performing the same functions remain in place.

Help Systems

Also following the programming period is the development of the help systems. This is a typical HTML help system (the industry standard) with accompanying FAQ and a Help Desk (on line up-to-the-minute help topics) as may be needed. Optionally, a tutorial help system may also be developed to assist in training new users.

Training

Training is typically provided just prior to the real world testing stage. Optional additional training can also be made available after the Implementation stage.

Implementation

Once the program is functioning as expected, it will phase out current methods in a manner that is appropriate to the situation. Other than a data entry period, this is usually immediate. However, it's possible that the situation may dictate that the transition will require days or even weeks.

Tech Support

Initial tech support will be provided during the initial implementation and training period. This, in combination with the training, is intended to provide a solid understanding of how to use the program in addition to addressing any issues that may arise during this stage. Additional tech support for future needs will optionally be made available through a support plan. Typically this is not required as the same assistance can be obtained through a combination of the help systems and a skilled supervisor.