0% menganggap dokumen ini bermanfaat (0 suara)
48 tayangan14 halaman

Contoh Laporan Rental Mobil

Laporan ini membahas rancangan database untuk sistem rental mobil yang meliputi skenario bisnis, model entitas relasional, tata letak situs untuk administrator dan frontend, serta contoh tampilan antarmuka pengguna. Tujuan sistem ini adalah memudahkan pelanggan dalam melihat ketersediaan mobil dan melakukan pemesanan secara online.

Diunggah oleh

Vian Hjjf
Hak Cipta
© All Rights Reserved
Kami menangani hak cipta konten dengan serius. Jika Anda merasa konten ini milik Anda, ajukan klaim di sini.
Format Tersedia
Unduh sebagai DOCX, PDF, TXT atau baca online di Scribd
0% menganggap dokumen ini bermanfaat (0 suara)
48 tayangan14 halaman

Contoh Laporan Rental Mobil

Laporan ini membahas rancangan database untuk sistem rental mobil yang meliputi skenario bisnis, model entitas relasional, tata letak situs untuk administrator dan frontend, serta contoh tampilan antarmuka pengguna. Tujuan sistem ini adalah memudahkan pelanggan dalam melihat ketersediaan mobil dan melakukan pemesanan secara online.

Diunggah oleh

Vian Hjjf
Hak Cipta
© All Rights Reserved
Kami menangani hak cipta konten dengan serius. Jika Anda merasa konten ini milik Anda, ajukan klaim di sini.
Format Tersedia
Unduh sebagai DOCX, PDF, TXT atau baca online di Scribd

LAPORAN RANCANGAN DATABASE RENTAL MOBIL

Nama Mata Kuliah : Prakt. CMS


Judul Projek : Databse Rental Mobil
Nama Pembuat : Febriyanto Maria Bang Ritan
NIM : 211210007
Kelas :12D2

JURUSAN TEKNOLOGI INFORMASI


PROGGRAM STUDI SISTEM INFORMASI
UNIVERSITAS MERCUBUANA YOGYAKARTA
DAFTAR ISI

Daftar isi................................................................................................................................................ii
Daftar gambar......................................................................................................................................iii
BAB I SKENARIO...............................................................................................................................4
1.1 Judul project................................................................................................................................4
1.2 Case scenario...............................................................................................................................4
1.3 Buisnis Rules...............................................................................................................................4
1.4 Contraint......................................................................................................................................5
1.5 Problem.......................................................................................................................................5
BAB II ERD PHYSICAL MODEL.......................................................................................................6
2.1 Erd physical model......................................................................................................................6
BAB III SITE MAP CMD DAN FRONT-END....................................................................................7
3.1 Sitemap cms................................................................................................................................7
3.2 Sitemap front-end........................................................................................................................7
BAB IV SCREENSHOOT TAMPILAN FRON-END TIAP MENU....................................................8
4. 1Menu Beranda.............................................................................................................................8
4. 2Menu Tentang.............................................................................................................................9
4. 3Menu Mobil...............................................................................................................................10
4. 4Menu Kontak.............................................................................................................................11
4. 5Menu Login...............................................................................................................................12

ii
DAFTAR GAMBAR
Gambar 2. 1 Erd Physical Model...........................................................................................................6

Gambar 3. 1 Sitemap Cms.....................................................................................................................7


Gambar 3. 2 Sitemap Front-End............................................................................................................7

Gambar 4. 1 Menu Beranda...................................................................................................................8


Gambar 4. 2 Menu Tentang...................................................................................................................9
Gambar 4. 3 Menu Mobi.....................................................................................................................10
Gambar 4. 4 Menu Kontak..................................................................................................................11
Gambar 4. 5 Menu Login.....................................................................................................................12

gambar 5. 1 login.................................................................................................................................13
gambar 5. 2 home................................................................................................................................13
gambar 5. 3 news_kategori..................................................................................................................13
gambar 5. 4 news.................................................................................................................................14
gambar 5. 5 logout...............................................................................................................................14

iii
BAB I SKENARIO
1.1 Judul project
Sehubungan dengan projek ini saya mengambil judul “Database Rental Mobil”

1.2 Case scenario


P24 ONE STOP RENTAL adalah salah satu usaha rental mobil yang bergerak di bidang
jasa. Saat ini, usaha tersebut sedang dalam masa perkembangan yang baik. Namun, ada
beberapa kendala yang sering terjadi, salah satu kendala yang sering terjadi yaitu ketersedian
kendaraan yang akan di sewakan kepada pelanggan tidak sesuai dengan permintaan pelangan
yang akan menyewakan kendaraan tersebut. Penyebab utamanya, yaitu sistem yang
dijalankan masih bersifat manual,
Oleh sebab itu, di buatkan sistem secara online, untuk memudahkan pelanggan dan juga
para pekerja rental. Karena, dengan sistem online, dapat menampilkan daftar, jenis, tipe,
harga mobil yang bisa disewakan serta juga akan melihat ketersediaan mobil apa saja yang
bisa di rental, dan dapat memasukan data diri dari pelangan kami.

Pengunaan website kami sangat mudah. Custumer dapat meliat keterangan mengenai
mobil pada halaman main page. Keteranga mobil berupa id mobil, jenis mobil,nomor polisi,
tahun buat,dan juga harga harian. Setlah pelanggan menemukan mobil yang ingin dirental.
costumer harus mengisi data data seperti nama, alamat, tanggal lahir, nomor id, jenis id, dan
tanggal lahir di website perusahaan.

Setelah mengisi data, data data harus dicek oleh karyawan. Karyawan dapat melakukan
pengecekan setelah masuk kedalam server admin, tentunya dengan memasukan data
karyawan seperti id karyawan, nama karyawan, alamat, nomor hp, dan jabatan. Setelah
melalui pengecekan. Setelah selesai. Halamakan bralih ke tahap transaksi. Halaman teransaksi
berisi id transaksi dan juga rincian harga seperti harga sewa, dan total harga. Namun perlu
diingat, jika pelangan harus membayar uang muka sebesar 20% sebelum melakukan
penyewaan dan jika mobil telah di siapkan maka, pelangan tidak bisa membatalkan pesanan
dan jika dibatalkan maka,uang muka di awal tidak dapat di kembalikan lagi. Setelah
melakukan transaksi, pelanggan dapat melaukan perentalan dengan membawa langsung mobil
ataupun diantar sesuai dengan alamat yang dicantumkan.

1.3 Buisnis Rules


 Custumer dapat meliat keterangan mengenai mobil pada halaman main page.
 Setelah pelanggan menemukan mobil yang ingin dirental. costumer harus mengisi
data data seperti nama, alamat, tanggal lahir, nomor id, jenis id, dan tanggal lahir di
website perusahaan.
 Karyawan dapat melakukan pengecekan setelah masuk kedalam server admin,
tentunya dengan memasukan data karyawan seperti id karyawan, nama karyawan,
alamat, nomor hp, dan jabatan.
 Setelah melakukan transaksi, pelanggan dapat melaukan perentalan dengan membawa
langsung mobil ataupun diantar sesuai dengan alamat yang dicantumkan.
 pelangan di wajibkan untuk membayar uang muka sebesar 20% sebelum melakukan
penyewaan kendaraan yang diinginkan, agar kendaraan tersebut segera di siapkan
untuk di sewa
 Transaksi berisi id costumer dan juga rincian harga seperti harga sewa, harga harian,
dan total harga

4
1.4 Contraint
 Jika pelangan sudah membayar uang muka dan mobil telah di siapkan maka,
pelangan tidak bisa membatalkan pesanan dan jika dibatalkan maka,uang muka di
awal tidak dapat di kembalikan lagi.

1.5 Problem
 sistem yang dijalankan masih bersifat manual, sehingga pelanggan yang ingin
menyewa kendaraaan dengan jenis tertentu tidak mengetahui kendaraan apa saja yang
tersedia.

5
BAB II ERD PHYSICAL MODEL

2.1 Erd physical model

gambar 2. 1 erd physical model.

6
BAB III SITE MAP CMD DAN FRONT-END
3.1 Sitemap cms

gambar 3. 1 sitemap cms

3.2 Sitemap front-end

gambar 3. 2 sitemap front-end

7
BAB IV SCREENSHOOT TAMPILAN FRON-END TIAP MENU

4. 1 Menu Beranda

gambar 4. 1menu beranda

8
4. 2 Menu Tentang

gambar 4. 2 menu tentang

9
4. 3 Menu Mobil

gambar 4. 3 menu mobi

10
4. 4 Menu Kontak

gambar 4. 4 menu kontak

11
4. 5 Menu Login

gambar 4. 5 menu login

12
BAB V SCREENSHOOT TAMPILAN CMS
5.1 Tampilan login

gambar 5. 1 login

5.2 Tampilan home

gambar 5. 2 home

5.3 Tampilan news_kategory

gambar 5. 3 news_kategori

13
5.4 Tampilan news

gambar 5. 4 news

5.5 Tampilan logout

gambar 5. 5 logout

14

Common questions

Didukung oleh AI

Including a detailed problem statement in the project report is crucial as it helps accurately define the challenges faced by the rental system, such as the manual handling of bookings leading to availability issues. This understanding is vital for developing targeted solutions that address specific inefficiencies and for aligning project goals with real-world needs. It ensures that all stakeholders have a clear understanding of the issues, which is essential for gaining support for the proposed system changes and for guiding the project's development and implementation phases .

The Entity-Relationship Diagram (ERD) plays a crucial role in designing the rental system's database by visually representing the data model. It outlines the key entities involved, such as customers, vehicles, and transactions, and shows how these entities are related to each other. This helps in organizing and structuring database tables and their relationships, ensuring that the database efficiently supports the functionalities of the online rental system. A well-designed ERD is foundational for ensuring data consistency and integrity .

The sitemap provides a structural blueprint for the front-end design, organizing the layout of pages such as the homepage, contact page, vehicle information, and user account sections. It influences the user interface by determining the navigation flow, ensuring users can intuitively access services without confusion. Effective sitemap design is crucial for creating a logical and seamless user journey, reducing abandonment rates, and enhancing user satisfaction through clarity and ease of use. The sitemap must reflect optimal pathways for achieving common user goals like viewing vehicle details and completing transactions .

The business rule requires customers to pay a 20% advance payment before renting a vehicle. This rule ensures that the rental company secures a commitment from the customer, preparing the vehicle for rental. However, it could negatively impact customer satisfaction, as cancellations are not refunded, which may deter customers who are uncertain about their plans. This policy safeguards the company’s operations against last-minute cancellations but could also result in dissatisfaction if customers perceive it as inflexible .

Transitioning to an online system offers several benefits, including improved efficiency, as it automates the booking and data entry processes, reducing human error and workload for employees. It enhances customer experience by providing real-time information about vehicle availability and streamlines the transaction process. This can lead to increased customer satisfaction and possibly higher rental rates, as customers can easily find and book vehicles that meet their needs without delays or misunderstandings .

The report identifies a key constraint that once the advance payment is made and the vehicle is prepared, the customer cannot cancel their order without forfeiting their deposit. This constraint has significant implications for system design, requiring the integration of strict transaction validation and tracking mechanisms. For the user experience, it necessitates clear communication of the terms before the transaction and potentially affects customer perceptions of flexibility and fairness. Effective user interface design will need to mitigate these issues by making terms clear upfront .

The integration of a front-end sitemap is directly related to effective customer interaction by providing a clear and organized structure for navigating the platform. It ensures that users can quickly find the information they need, such as available vehicles, pricing, and contact information. A well-designed sitemap aids in reducing cognitive load and helps guide users through the process of renting a vehicle efficiently and intuitively. This directly impacts user satisfaction and can significantly reduce drop-off rates by facilitating seamless and effective interactions with the platform .

Employee involvement is critical in the transition from a manual to an online system as it ensures the successful adaptation and continued operation of the rental system. Employees need to be trained to use the new system, handle data entry, and manage online transactions. Their feedback is essential for identifying potential system issues and for improving usability. Employees act as intermediaries, ensuring data accuracy during transactions, and their support can enhance customer trust and service reliability. Therefore, their active participation is pivotal for smooth implementation and sustained system efficiency .

Implementing an online platform for the rental system presents challenges such as data security, ensuring that user and transaction information is protected against breaches. Another challenge is system reliability, requiring robust architecture to handle real-time data processing without frequent outages. Further, user adoption could be an obstacle, needing user-friendly interfaces and comprehensive support to transition existing customers from manual to digital processes. Scalability is also a potential issue, as the system must efficiently handle increasing transaction volumes as the business grows .

The main problem identified in the current rental system is that it is manual, leading to issues such as customers not knowing which vehicles are available. The proposed online system addresses these issues by allowing customers to view detailed information about available vehicles, such as type, price, and availability, on a website. This ensures that the customers can make informed decisions. Additionally, the system requires customers and employees to input and verify necessary data online, ensuring the process is streamlined and errors are minimized .

Anda mungkin juga menyukai