Show Bid Request
Small Project-Prototype of a Help Desk Trouble Tracking System
Bid Request Id: 24221
|
|
|
|
Posted by: |
dyinlove (3 ratings)
(Software buyer rating 10 )
|
|
Non-action Ratio: |
Very Good - 0.00%
|
|
Posted: |
Aug 11, 2002
5:27:00 PM EDT
|
|
Bidding Closes: |
Aug 14, 2002
11:59:59 PM EDT
|
|
Viewed (by coders): |
291 times
|
|
Deadline: |
8/17/2002
TIME EXPIRED
|
|
|
|
|
Description:
This is a working prototype of a help desk trouble tracking system. It should contain 4 forms (see other files for figures).It's not going for the real world application. It's just a practice problem for my final exam. Thanks...
Deliverables:
Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
Complete copyrights to all work purchased.
In theory, help desk technicians will use the system to record and track computer related problems reported by employees. The application must be developed using Visual Basic and connect to an Access database back-end. When the application is started a Login Form must be displayed. Only technicians with valid passwords and corresponding login IDs will be permitted to access the system. When a technician types their password, asterisks(*****) must be displayed instead of the actual password text. Error messages should be displayed if the technician fails to provide a password and corresponding login IDs. Failed attempts must be limited to three;otherwise, kick the perosn out of the system. A way to end the program should also be provided on this form. Once the technician has successfully logged into the system, they will be able to use the following features:
1.Create a new trouble ticket
2.Find a trouble ticket (open or close) by input the only ticket number.
3.Scan open trouble tickets only.
4.Scan closed trouble tickets only.
5.View past sloutions according to problem category.
6.Logout(back to login form).
In addition to the login form, trouble ticket form and solution form are required.
Trouble Ticket Form:
This form will allow technicians to record relevant trouble ticket information. All required fields from the provided database tables must be used. Upon accessing the trouble ticket form the technician should see a blank form. To creat a trouble ticket the technician will need to enter a fictitious trouble ticket number following the format provided. If the technician doesn't want to creat a new troubl ticet, the form should provide a way for him to perform any of the features listed above.
1.Ticket staus (open or close) must be displayed using the option buttons.
2.Ploblem categories are :PC, Printer, Network, Application, or Miscellaneous and must be selected using a combo box.
3.Ability to add or update up to 3 brief comments on open troubl tickets.
4.If the technician types any text in the solution box, the ticket should be closed after validation from the technician, otherwise it should remain open with no solution entry.
5.The technician should only be able to edit open trouble tickets, closed trouble tickets should remain closed.
6.Provide a way to access solution form and to return to the login or main form.
Solution Form:
This form will allow technicians to search for solutions from closed trouble ticets by category. The partial test bed will have at least 3 solutions in each category. The search should display the first three solutions from the selected category. If the technician finds an intersting solution he may wish to view the detailed trouble ticket information. At this point, the technician should be able to click a command button which will display the trouble ticket of the chosen solution.
1.Whenever the solution form is accessed, the fields should be empty.
2.Problem category combo box is the same one used on the trouble ticket.
3.Provide a means of acessing the trouble ticket of a specified solution.
4.Provide a way to retrun to the login and trouble ticket forms and optionally the main control form.
**only one form should be displayed at a time.
***see other files for figures and database.
Platform:
This should be done by Visual Basic 6.0 and connect to an Access database back-end.
This is needed to be run by Visual Basic 6.0
Must be 100% finished and received by buyer on:
Aug 17, 2002 EDT
Deadline legal notes: All times are expressed in the time zone of the site EDT (UT - 5). If the buyer omitted a time, then the deadline is 11:59:59 PM EDT on the indicated date.
Special Conditions / Other:
Must be completed by 8/17/2002 11:59:59 PM EST.
Thanks a lot.
Additional Files:
This bid request includes IMPORTANT additional attached files. Please download and read fully before bidding.
Remember that contacting the other party outside of the site (by email, phone, etc.) on all business projects < $500 (before the buyer's money is escrowed) is a violation of both the software buyer and seller agreements.
We monitor all site activity for such violations and can instantly expel transgressers on the spot, so we thank you in advance for your cooperation.
If you notice a violation please help out the site and report it. Thanks for your help.
|
|
|
Bidding/Comments:
|
All monetary amounts on the site are in United States dollars.
Rent a Coder is a closed auction, so coders can only see their own bids and comments. Buyers can view every posting made on their bid requests. |
See all rejected bids (and all comments)
| Name |
Bid Amount
|
Date |
Coder Rating |
|
|
This bid was accepted by the buyer!
|
$35 (USD)
|
Aug 12, 2002
7:16:24 AM EDT
|
10
(Excellent)
|
|
|
| Pl. check the attached demo. Modifications can be done. |
|
|
Attached File
|
|
|
|
|
|
