VB GUI for Proprietary Database

Closed Posted Feb 12, 2008 Paid on delivery
Closed Paid on delivery

We are designing a graphic interface using Visual Basic 2005 for a large, widely-used proprietary DB2-like database. The company that markets the database has released their own GUI architected on a web-based platform, but it has been recognized in the marketplace as a failure, wrought with poor design and slow performance. Considering that the database in question has been in existence for over a decade, there seems to be little doubt that the “right?? GUI will not come from the application vendor. There are a few other companies that compete in this space, but none have been able to create a simple, high-quality interface that users of the database require. Note that this UI is ONLY a front-end interface with “hooks?? into the back-end database. The database itself is fully functional and requires no modifications or additional programming. The decision to stray from a three-tier architecture and web-based interface was made because only a few users will ever be connected to the database to perform database tasks. We believe that the extra overhead of software and hardware required to implement the existing UI is excessive for the functions that the UI provides. Further, the decision to use VB specifically was made because of its relatively fast development cycle and familiar UI.

## Deliverables

[ Ideal Candidate ] All individuals considered for this project should possess the following qualifications: 1. Must be able to communicate effectively, both verbally and written, in the English language; 2. Must be able to dedicate several days per week to this project; 3. Must be well-versed in Visual Basic 2005 4. Is flexible and passionate about this project. [Non-Disclosure Agreement (NDA) ] Complete details of the database and its usage will be made available to you after you have signed a Non-Disclosure Agreement (NDA). This agreement will help to protect our intellectual property during the entire project by legally preventing you from discussing the technical details of the project with others, as well as preventing you from using the information that we provide to you to compete against us. Your code will become our intellectual property and you will not be permitted to market or distribute the code, or any portion thereof. [ Application Design ] This GUI has a look and feel similar to the Microsoft Management Console with some minor cosmetic differences. It will be broken down logically into several modules. A module will be defined as a single functional piece of the application that provides the user with data from the back-end database, formatted within the bounds of the GUI. Any given module will both present the user with back-end data and allow the user to update the back-end database using property panels, right-click menus, or Wizards. For example, one module will query an ADMINISTRATORS table in the database (which consists of all users that can access the database) and will present that list along with other details about the user (including description, password, access rights, etc) in a clean, user-friendly format within the GUI. A user can elect to make additions, changes or can delete items in the ADMINISTRATORS table by way of Wizards, property panels, right-click menus, etc in the GUI. Note that in some cases, a module will need to perform calculations or manipulate the back-end data in some way before the data is presented in the GUI. Likewise, some user-entered data may need to be modified or changed by the module before being written to the database. [ Available Information ] A functioning “Alpha?? version of the application is currently available and will be used as the foundation for the remaining modules. This Alpha version consists of the base UI, classes to connect to the back-end database, and the first of several dozen modules. Also available is documentation to detail the current design and technical details of the Alpha version. Layout mock-ups (designed in VB) for each module will be provided to you and you will be required to make the design functional. Because of the depth of the back-end database, you will need to work closely with me to understand the technical details of database. The candidate must be able to understand our requirements and complete the VB code to support those requirements. For testing and implementation, you will be given access to several instances of the back-end database (via the Internet) which reside on a server in our home office. Note that even though you will be accessing a database, you will not be using an existing API or ODBC connection agent. The database uses a proprietary, freely-distributed command-line interface and coding has already been created to utilize this connection. [ General Design Workflow ] The following procedures will be followed whenever a new module is implemented: 1. We will provide you with a Functional Design Specification (FDS) as a Word document. This document will contain detailed information about the module and its functionality, specific database commands to collect and update data in the database, expected module behaviors, UI details, Wizard functionality details and other important information. In addition, the FDS will also contain a detailed checklist of completion criteria for the module. This checklist will be used to determine when a module is considered complete. 2. A mock-up (created in VB 2005) of the screen layout, design, formatting, Wizards and menus will also be provided to you. Because this is only a mock-up, no real data or functionality will be provided. The mock-up will simply show how the UI should appear in the final design. 3. Once you have reviewed the specifications and layout, we will collaborate via conference calls, e-mail or IM to answer any questions you may have about the proposed design and accessing the data to support it. 4. You will be required to make the mock-up functional by accessing the actual data from the database and integrating your code with the screen design per the module specification document. 5. The module will be reviewed and tested for bugs and error handling. Any discrepancies will be formally noted by way of a Bug Fix Request (Microsoft Word document) and passed back to you for resolution. Additional meetings, calls or e-mails may be required during this phase. This process will continue until the module design is finished per the completion criteria checklist in the FDS. [ Work Environment and Expectations ] Because of the informal nature of this project, you will be able to work at a time and location best suited for your needs. However, you will be expected to devote several days per week to the project and will be held accountable for delivery dates of each module of the application. Compensation (either hourly or fixed price) will be dependent on your ability to complete required functions on agreed-upon delivery dates. [ Other Disclosures ] The selected programmer will be paid at the agreed hourly or fixed rate in order to complete a working release of the UI. Long term support of the application will likely be required for bug fixes and enhancements as the product matures. Programmers considering this assignment should determine if they are also interested in assisting us on a long-term basis. However, please note that there are no guarantees, neither expressed nor implied, that this will turn into a long-term assignment. [ Project Timeline ] We anticipate that the Beta release of this product should be able to be completed by an experienced Visual Basic programmer within 6-8 months. This is obviously widely dependent on the number of hours/days per week that the selected candidate can devote to the project as well as the ability of the programmer. As mentioned previously, after the Beta release, bug fixes and application enhancements will likely serve to extend the project beyond a 6-8 month timeframe.

.NET Database Administration Engineering Microsoft MySQL PHP Software Architecture Software Testing SQL Visual Basic Windows Desktop

Project ID: #3714895

About the project

Remote project Active Mar 5, 2008