Here is a brief description of how I can help with the System Design...
What better way to demonstrate my capabilities than to point out I have been self-employed since 1988?
An important element of success.
Among those I am currently working with are—Microsoft Access, all versions. This type of database allows for the use of an SQL based query, and those that are graphically produced with features that are unique to Access.
- I am currently using MSSQL 2000 for a project that imports information from a number of different vendors (these are all for different products and services). Some bills are for 1 or 2 items, while others have several hundreds of thousands transactions, and still other use an old Microsoft Access solution. Data is then processed, and used to form a monthly bill.
Let me emphasis what this means in programming, there is a perfect world and there is reality. There are bugs, which is another way of saying mistakes—these will be corrected (and the time required to do so is calculated into the proposed project fee). There are forgotten pieces, these will be added. And, there are enhancements. The wouldn't it be nice if...
The last item is another way of saying, my completed projects allow people to see the potential a program has, not only is there light at the end of a tunnel, there's something better up ahead.
To review specific programming skill, you can click here: Programming. I'll describe a few of the systems I have designed. As an overview, these are between large and small in scope, but what I hope it displays is the variety of experience I have, and my ability to recognize the best solution. Because of years of experience, I'm not an advocate of one type of programming language or database, over the end product.
My current work with a Health Insurance organization involved receiving data from a number of different vendors, in an equal number of formats. These are text files, spreadsheets, and databases. Data is imported to a MSSQL 2000 database. Various forms of accounting are performed, validating the data and its numbers.
The organization then bills its various affiliates for these charges. Data is taken from the database, and formed into 2 Excel spreadsheets. As a general invoice, a template is used. In the supporting detail spreadsheet, the Powerbuilder program builds these Excel spreadsheets dynamically. Everything from column size, font style, formulas, and the data itself is handled 'on the fly'.
The files are then automatically emailed to the affiliates via Microsoft Outlook.
Order information arrives from a different company, one that takes the orders over the phone. Information is imported to an Access database, where orders are maintained, pick lists and on—hand reports printed, various text files to be sent back to the client are created, and data to be imported to a FedEx program are created. This simple, straight–forward process is an example of how much databases such as Access can be used for in developing applications. There is both the program, and the built-in features of Access so users can create queries or reports when necessary.
Another Health insurance application I have developed is to monitor the cost and success involved in a number of clinical trials. Because of recent laws, data has various security rules that most databases would not require. In other words, this application not only uses Word documents (with bookmarks), but employs another important feature that is inherit in databases. There are many types of users, with different levels of authority to see data, make changes, delete, etc. It also encrypts the data, which in performance terms is unnoticeable, but prevents any form of data-intrusion to PHI (Patient Health Information).