Below is an exmple of the process we will go through to create your custom application. This is a very brief example, but hopefully you will understand the types of information and the detail that we will need. Once we have this we can come up with a proposal and a quote on how much it will cost.
Contact us my e-mail or phone and we can discuss your needs and walk you through the process if necessary.
Example
Step 1: Define the Problem
We need to determine what the program is going to do. We
can come to your site and analyze your current business processes and come up
with suggestions on how they could be improved with custom programs or
integrating existing business solutions.
If you already have a clear idea of what needs to be done, then
this needs to be communicated to our programming team. These are the
things we need to know:
1) What type of application do you need
| Type |
Pro |
Con |
| Single user desktop application |
Fastest |
Only 1 user can run the program - data is stored on one computer. |
| Multiple user desktop application on a local network (LAN) |
Multiple users sharing data. |
Must be connected to local network to use the application.
Must be installed on all client machines.
|
| Web-Enabled desktop application |
Multiple users sharing data.
Laptop/Home computer access to the data over the internet.
|
Slower than a LAN desktop application.
Must be installed on all client machines.
|
| Web Browser based application |
Multiple users sharing data.
Laptop/Home computer access to the data over the internet.
Access data anywhere there's a web browser (internet cafe).
Can be accessed from a WAP device like a mobile phone.
Doesn't need to be installed on client computers. |
Slowest data entry method. |
| Combination of Web-Enabled and Web Browser |
Multiple users sharing data.
Access data anywhere there's a web browser (internet cafe).
Can be accessed from a WAP device like a mobile phone.
Speed when you're at your own computer (office, laptop, or home). |
(Best of everything) |
2) WHO will be using the program.
Often there are people accessing the same program but with different ROLES. For example: A billing application may be accessed by the following:
| Role |
Functions |
| Data Entry |
Adds invoies (telephone orders) |
| Manager |
Add or Edit invoices |
| Accounting |
Needs reports on how much was invoiced and integration with accounting systems |
| Executives |
Want reports on sales trends with graphs |
The point is that we need to know the differnent TYPES of people who will be using the application, and what each one will expect the program to do for them.
3) The exact data that each of the above user types will need.
This is where your current business processes come in. If you have any existing paper forms then we should have a look at these. For example - in our billing application we may need the following:
| Table |
Contents |
| User |
Name and password for each person using the application.
Roles for this user (what are they allowed and not allowed to do)
|
| Customer |
Account Number
Customer Name
Address
Phone Number
E-mail address
Terms
Credit limit
Notes
|
| Invoice |
Customer
Invoice Number
Date
Materails & Labor
Tax
Total |
| Invoice Items |
Name of product or service
Price
Qty
|
| Payment |
Date
Invoice Paid
Amount
|
4) Style.
If you want it branded for your company - we'll need a good graphic of your company logo (or we can design one for you) as well as your company color schemes, mascots, or any other ideas you may have about how the application should look. Scribbled diagrams on napkins are great for this.
5) Integration.
Does it have to work with any other existing business software. For example - we may want our billing application to integrate with Microsoft Outlook to e-mail invoices instead of printing them. Or we may want it to save invoices in Acrobat PDF files for archiving.
e-mail or phone us to begin the process of building your application!