Custom Software

Requirements Collection:
You must determine the customer's requirements before starting the design (AKA define the task). Sure I'm stating the obvious, but many companies start down the design road before getting all the requirements. Then specific requirements get 'wedged' in. Without a clear set of requirements, the project is doomed from the start. We usually contract requirements on a time & materials basis because it's very difficult to determine how long and how many requirements there will be. We can use our requirements form or your own internal form. Requirements are pieces of data, business rules, etc.

System Design: This is a high level view of the programs/modules and data of the system. It shows where the requirements are being satisfied within the system. At this point, the data can be organized into tables, and the table rules created. The system design is usually contracted on a time & materials basis due to the nature of the task. If desired, an estimate for the application design portion can also be provided. Visio is our preferred tool.

Application Design: Based on the system design, each program/module can be designed. If desired, an estimate for the application coding portion can also be provided. Visio is our preferred tool.

Application Coding: Using the application design, code each program/module in the specified language. Visual Studio is our preferred tool.

Documentation: Defining how to use the system, how to maintain the data and software. Microsoft Word is the preferred tool (with help from Visio).