Reference no: EM132327177

TPM CAR PARK MANAGEMENT SYSTEM

This assignment requires basic level of programming to create windows app forms.

The management of TPM has completed the construction of a multi-storey car park where tenant offices staff working around the TPM new car park to park their cars. The car park can accommodate a total of 200 cars, where each level will have 50 parking spaces. In order to manage the cars parked there, a system is required to be developed. A registered car owner will be charged RM80 for roof top level parking and RM120 for covered parking on other levels. The system would be used by the parking management office to register the car owner's application for a car park. A deposit of 80% of the monthly parking charges will be required upon registration and can be refunded upon withdrawal of the car park space by the car owner. Car owners may reserve the parking space for durations of 3 months or 6 months from the registration date. If a car parking bay reserved by a car owner has expired, the owner must renew the parking bay reservation at the parking management office.

DATABASE STRUCTURE -

OWNER	Description
Identification Card Number or Passport Number	The unique IC number or passport number of the car owner
OwnerName	Full Name of the owner
Contact Number	Owner's email address
E-mail address	Owner's email address
CarNumber	Owner's car number

 

ParkingBay	Description
ParkingSpaceID	The parking bay number, using the car park level and the bay number. Example: Level 2 bay number 5 will be designated as L2-005
Date Registered	The date the car park bay was registered
DepositPaid	The deposit paid by the owner
DateExpired	The date the registered bay will expire
Status	Parking bay status as "Available" or "Assigned"

 

Payment	Description
Payment Code	Unique sequential code for each payment made
PaymentDate	Date of the payment made
PaymentAmount	Amount paid for the parking
ParkingSpaceID	Foreign key from ParkingBay table

 

User	Description
Username
Password	User's password for logging into the system
First Name	User's first name
Last Name	User's last name
Role	User's role as "Administrator" or "Staff"

SYSTEM REQUIREMENTS -

1. Login

The system must require user to enter their username and an assigned password before using the system. If the parking administration staff does not have access to the system, the manager can assign an access username and password for the staff.

2. The system must have the following functional requirements:

a. Register Owner / Renew Parking

Car owner who wants to park their car at the car park is registered by the system. Once registered, a parking bay is assigned to the car owner, depending on the availability of parking bays on each floor. If all the parking bays are already occupied, then the system should inform the user.

If a car owner's reserved parking bay has expired, the owner must renew the parking bay at the parking management office.

b. Withdraw/Cancel

If a car owner who do not wish to park at the car park anymore, the occupied parking bay occupied will be released. However, the record of the car owner will be retained.

c. Update Details To enable car owner's information such as Car Number, Contact Number and E-mail address to be updated in the system by the parking management staff.

d. Payment

Car owners make payment at the parking management office and as each payment made, a receipt will be generated. Hint: the receipt is generated using the report tool in Visual Studio.

e. Report

The manager of the parking management office can generate a report of all cars parked at the car park sorted by floors which should include the following information: Car Owner's Name, Car Number, ParkingSpaceID, Date Registered, Date Expired

The manager has full access to the system functionalities, and staffs can access to all functionalities except generating the report.

SUBMISSION REQUIREMENTS -

You or your group is required to submit the following for your documentation:

a. APU Assignment Cover Page

b. Table of Contents

The table of contents should have the section headers and the corresponding page number.

c. Introduction

This should include the task, the scope of the new system, and the objectives for the new system.

d. Storyboard

This section includes a sketch design of Windows Forms used in the system, indicating the layout and the components to be used for the interface (forms and report structures). This may be drawn using mockup tools or wireframe software which can be found online.

Brie f description for each control used on a Windows Form is required. Refer to the sample on Page 4.

e. Output Screen Designs

This section includes the actual screen when the program is executed. This may be done by capturing the screen that has been implemented in the program. The Output Screen Design must match with the Input Screen Design.

f. User Manual

Produce a detailed user manual of at least 10-15 pages on using the system that you or your group has developed. The manual must include step by step instructions to perform a specific task in the system which includes screen shots to assist users in using the system.

g. Critical Assessment

Identify the strengths and the weakness that you or your group has found in the new system. If there any weaknesses, provide recommendation(s) on how the system might be improved in the future.

h. References

PRESENTATION - Your group is to prepare a 15-20 minutes presentation to demonstrate your program to the lecturer. The presentation will be graded based on the ability to demonstrate the working of your program and the ability to answer questions.

Attachment:- Assignment File.rar