Quick Desktop application: Locker key tracking software

Job Description

I need a desktop application that uses a local database and is written in .NET or Java to replace an aging application currently utilized by a University's Student Recreation Center to keep track of the keys used to gain access to the day lockers provided to visitors/patrons for temporary storage. This system is used to check keys in and out, and also reports on the keys currently checked out by patrons.

A detailed requirements document is provided but the main functionality is:

1. Provide the ability to look up a patron from a local database

2. Provide the ability to enter in new patron information

3. The ability to check out a key (tracking the key number)

4. The ability to check in a key either by patron or key number

5. The ability to list all currently checked out keys.

This is a very short turnaround assignment with the possibility of additional work to add reporting and additional checkin/checkout tracking.

Contractor requirements:

I am looking for a contractor that has the following skills:

1. Familiarity with C#, VB.NET or Java

2. Desktop application programming experience

3. Database design and programming

How to apply

Please submit a cover letter that highlights:

1. Your experience, especially that which matches the job description including desktop and database programming

2. Your speed in turning around work for review

Please respond with any technical challenges or questions you have about this project.

## Deliverables

Campus Recreation Key Tracking Software

# Purpose

The purpose of this project is to replace an aging application currently utilized by a University's Student Recreation Center to keep track of the keys used to gain access to the day lockers provided to visitors/patrons for temporary storage. This system is used to check keys in and out, and also reports on the keys currently checked out by patrons.

At a later date it may also be utilized to checkout other items in other functional areas of the recreation center.

# Delivery Requirements

1. All software source code

2. Compiled executable

3. Empty database

4. Your testing database

5. Configuration instructions

# Architecture Requirements

1. Desktop Applications (WinForms or Java Equivalent)

2. Acceptable languages include C#, VB.NET (.NET v3.5 or higher) or Java (1.6 or higher)

3. Database should be Microsoft SQL Server Express or similar

4. 32-bit executable

# Functional Requirements

## Application Data

? Patron's First Name (30 characters)

? Patron's Last Name (30 characters)

? Patron's Identification Number (a unique number)

? Patron's Status (one of the following)

o Faculty

o Staff

o Student

o Graduate

o Affiliate

? Patron's Checkout Permission (Boolean)

? Key Number - a number used to track a locker key (20 characters)

? A history of activity for each patron. This includes a time-stamp history that will include the patron's name, key number, checkout time, and check-in time.

## Initial Screen

1. The initial application screen should present the user two options:

a. The ability to enter in a Patron's student ID card information.

b. Show all the currently checked out keys

2. The Patron's Student ID card has a magnetic stripe that is read by a card reader. Swiping the card will cause the Patron's 16 digit card number to be entered in as if it was typed on a keyboard.

3. Digits 7-15 of the information from the card is Patron's Identification Number

a. For example, the information from the card could be: 3456123**47890456**7

b. The Patron Identification Number is: 47890456

c. All other numbers except digits 7-15 can be ignored

4. Pressing <Enter> after the card number is entered should proceed to the next screen (no button click should be required)

a. If the Patron does not exist in the database then Patron Entry screen will be displayed

b. If the Patron already exists in the system then the Patron Information screen will be displayed.

## Patron Entry Screen

1. The user will enter in the patron's First Name, Last Name and Status (Student or Faculty, etc.)

2. The Patron Identification Number will be automatically filled from the card swipe

3. The Patron's Checkout Permission should be set to True

4. This information will then be saved to the database

5. After completing this information the Patron Information Screen will be shown

6. User should be able to cancel and go back to the initial screen

## Patron Information Screen

1. This screen will show the Patron information (Name, Status) and their Patron's Checkout Permission.

2. If the Patron currently has a key checked out, the Key Number will be displayed.

3. If the Patron's Checkout Permission is False then they will be never be able to check out keys.

a. Note: there is no requirement for the ability to change this value via the software. Any update of this permission will be made directly via the database in this first release.

4. If a Patron already has a key checked out, they will not be able to check out an additional key. Each patron may only have one key at a time.

5. If the Patron does not have a key checked out then the user is able to input a Key Number which identifies the key that the Patron will check out. The user can then click a "Checkout" button.

a. The system should record a timestamp, the Key Number that is checked out, and the Patron that checked the key out in the database.

b. If that Key Number is already registered to another Patron an error should be displayed.

6. If a Patron has a key checked out then the software should allow the user to check that key back in. The system should record the timestamp of when the key was checked back in. That information should be associated with the initial checkout record.

7. User should be able to cancel back to the initial screen.

8. After checking out a key or checking in a key the user should be taken back to the initial screen.

## Current Checked Out Keys Screen

1. This screen should display a list of all keys currently checked out for all Patrons.

2. The Key Number, Patron information and checkout time should be displayed for all keys that are currently checked out in a data grid.

3. The list should be sorted with the earliest checked out key at the top.

4. From this screen the user should be able to select a checked out key in the data grid and have the option to check that key in.

a. The system should record the timestamp of when the key was checked back in. That information should be associated with the initial checkout record.

5. The user should be able to return to the initial screen

.NET C# Programování Java Microsoft MySQL SQL Visual Basic Pracovní plocha Windows

Identifikační číslo projektu: #2708198

O projektu