0% found this document useful (0 votes)
20 views38 pages

Sem 3 Project Report

Project

Uploaded by

aviratraut98
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
20 views38 pages

Sem 3 Project Report

Project

Uploaded by

aviratraut98
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 38

Chapter 1

Intoduction

1
1.1 Project Abstract
In the dynamic and ever-growing automotive industry, the need for a seamless and user-friendly platform
for car enthusiasts to buy and sell vehicles is paramount. "Car Deals" aims to fulfill this need by providing
an innovative online marketplace where users can easily list their cars for sale, browse a diverse range of
available vehicles, and facilitate secure transactions.

Key Features:

1.User-friendly Interface:
An intuitive and responsive web and mobile interface designed for easy navigation, ensuring a positive
user experience.

2.Car Listing and Selling:


Sellers can create detailed listings for their cars, including specifications, images, and pricing information.
Integration of advanced search filters for buyers to efficiently find cars that match their preferences.

3.Secure Transactions:
Implementation of a secure and transparent payment system for seamless transactions between buyers and
sellers. Integration of payment gateways to facilitate online transactions securely.

4.Verification and Trust:


User profile verification to establish trust and credibility within the platform.
A rating and review system for buyers and sellers, enhancing transparency and accountability.

5.Real-time Notifications:
Push notifications and alerts to keep users informed about listing updates, inquiries, and transaction status.

6.Integration of Analytics:
Utilization of analytics tools to gather insights into user behavior, popular car models, and market trends.

2
1.2 Existing System:
In the existing system are done manually but in the proposed system we have to
computerize the car selling and buying in this application. And People want go to the
supplier for pickup the water can.
 Lack of security of data.
 More manpower.
 Time-consuming.
 Consumes a large volume of paperwork.
 Needs manual calculations.

1.2 Need of System:


 Understanding the data: Car Selling and Buying can help in gaining an understanding of
the data and the relationships between different features.
 This can help in identifying patterns and trends, as well as outliers and anomalies in the
dataset.
 Feature selection: Car Selling and Buying can help in selecting the most important features
for predicting the selling price of used cars.
 This can help in reducing the dimensionality of the dataset and improving the performance
of the model.
 Data preprocessing: Car Selling and Buying can help in identifying and handling missing
values, outliers, and other data quality issues. This can help in improving the accuracy and
reliability of the model.

3
1.3 Scope of work:

 Data exploration: The scope of Car Selling and buying includes exploring the dataset using
various statistical and visualization techniques.

 This includes calculating summary statistics, correlation analysis, and creating


visualizations like histograms, scatter plots, box plots, and heatmaps.

 Feature engineering: The scope of Car Selling and buying includes creating new features
from existing ones.

 This includes extracting information like age of the car, mileage, and condition of the car
from existing features.

 Model building: The scope of Car Selling and buying includes building a model using the
preprocessed dataset. This includes selecting an appropriate algorithm, training the model,
and evaluating its performance using metrics like accuracy, precision, and recall

4
1.4 Operating Environment – Hardware and Software:
Hardware Specification:
 Processor : snapdragon
 Clock speed : 500 MHZ
 RAM : 6 GB of RAM
 Memory : 128 GB or high

Software Specification:
 OS : Android
 IDE : Android Studio
 Database : Firebase

1.5 Technology Used:


 Front End : Android
 Back End : Java And Firebase

5
1.6 Module Specification:
1. Administration Management:
Admin Login:
Secure login functionality for administrators to access the system.
Authentication mechanisms to ensure only authorized personnel can log in.
Data Insertion:
Admins can add, modify, or delete car-related data into/from the system.
Implementation of data validation to ensure the accuracy and integrity of
information.
Logging and audit trails for tracking data modifications.

2. User Management:
User Access:
Registered users can log in and access the system.
Different roles (e.g., regular users, premium users) with varying levels of
access.
Data Display:
Displaying sorted and filtered car-related data based on user preferences.
Search and filtering options to help users find specific cars or categories.
Pagination and user-friendly interfaces for easy navigation.

6
3. Category Management:
Car Types:
Classification of cars into different categories or types (e.g., Sedan, SUV,
Electric).
Admins can manage and update the list of categories.
Sorting Information:
Implementation of sorting mechanisms for users to view cars based on
categories.
Dynamic updating of categories based on the addition or removal of car
types.

4. Selling and Buying Management:


Listing Cars for Sale:
Users can list their cars for sale, providing detailed information and images.
Validation to ensure accurate and complete information during the listing
process.
Buying Cars:
Users can browse the available cars for purchase.
A secure transaction system for users to buy cars.
Notifications and alerts for users during the buying process.
Transaction Security:
Integration of secure payment gateways to facilitate safe transactions.
Verification processes to ensure the legitimacy of sellers and buyers.
Order History:
Record-keeping of past transactions for both sellers and buyers.
Accessible order history for users to track their transactions.

7
Chapter 3
Proposed System

8
2.1 Proposed System :-
User Authentication:
Users (buyers and sellers) should be able to create accounts and log in securely.
Use Firebase Authentication or a similar service for secure user authentication.
User Profiles:
Allow users to create and manage profiles.
Sellers can add details about the cars they are selling.
Buyers can view and edit their profiles.
Car Listings:
Sellers can create detailed listings for each car they want to sell.
Include information such as make, model, year, mileage, price, images, and
additional features.
Provide a search and filter functionality for buyers to find specific cars.
Payment Integration:
Implement a secure payment gateway for users to make payments.
Support multiple payment methods (credit cards, digital wallets, etc.).
Order Processing:
Once a buyer decides to purchase a car, facilitate an order process.
Allow buyers to confirm their order and initiate payment.
Order History:
Keep track of users' order history.
Buyers and sellers should be able to view details of past transactions.

9
2.2 Project Objectives:-
To identify and understand the distribution of each variable in the dataset,
including their ranges, central tendencies, and spread, and to identify any missing or
erroneous data.
To explore the relationships between the different variables in the dataset,
including the correlations between them and any patterns or trends that emerge from
the data.
To determine the key factors that impact the
selling price of a used car, including the car's age, mileage, condition, and other
features,

2.3 User Requirement :-


 User Permissions:
 Enable users to create and manage profiles with relevant information.
 Show Cars
 Make Payment
 Ensure data integrity, security, and compliance with privacy regulations.
 Implement communication channels for volunteers and victims to interact effectively.

10
Chapter 3
Analysis & Design

11
3.1 Entity Relationship Diagram

12
3.2Data Flow Diagram

13
3.3 Use Case Diagram

14
3.4 Class Diagram:

15
3.5 Sequence Diagram:

16
3.6 Activity Diagram
Admin Activity Diagram:

17
User Activity Diagram:

18
3.7 Table Structure

19
20
3.8 User Interface Screens
Home Page:

Admin Login Page:

21
Admin Home Page:

Add Product Page:

22
Customer Registration Page :

Customer Home Page :

23
Customer Summary Page :

AdminView Order Page :

24
3.9 Test Case

Test Case Id Test Objective Step Input Expected Actual Result Status
Descripti Result Pass or
on Fail

TC_01 To check 1.Enter 9130500 registration Registration Pass


functionality of valid 564 should done sucessfully

registration page by phone completed


123 User Enter
2.Enter
entring valid phone in System User is Sucessfully
valid
and password Entered in System
password
3.click on
register
button

TC_02 To check 1.Enter 91305055 After Error Message Pass


functionality of Invalid 56 entering generated

registration page by phone invalid


302
2.Enter email id
entring Invalid
Invalid error
phone and password
password message
3.click on should be
register generated
button "Invalid
credential"

TC_03 To check 1.Enter 9130500 After Error Message Pass


functionality of Invalid 564 entering generated

registration page by email id invalid


2.Don’t email id
entring Invalid
Enter error
phone and Invalid
password message
password(BLANK)
3.click on should be
register generated
button

25
"Invalid
credential"

TC_04 To check 1.Enter 9130500 Display Home Page Pass


functionality of valid 564 Home Displayed
login page userId Page
123
2.enter
valid
password
3click on
login
button

TC_05 To check 1.Enter 9130500 Messege Messege Pass


functionality of invalid 564 should be Displayed
login page userId display
“Enter
With invalid input 2.enter
Location”
valid
password

26
TC_06 To check add 1.Enter Audi Product Product add Pass
product the add successful
SUV
produvt successful
detail 5000000

TC_07 To check add 1.Enter blank Details not Details not enter Pass
product without the enter
input produvt
detail

TC_08 To check the user 1.Select By click Order Order summary Pass
can proceed to buy the on the summary open
product product open

27
TC_09 To check the order 1.Go to By Order Order approved Pass
By admin Order Clicking approved
Page the
approve
button

TC_010 To check logout By Chick LogOut LogOut Pass


selecting logout Successful Successfully
logout button ly

28
4.Drawbacks and Limitations:

1.Record keeping is complex in the existing system.


2.To find out the records quickly is not possible in existing system.
3.As the growing trend in a world of computer, the need for accuracy, perfection, speed and large
data storage is must.
4.Each and every problem must be solved with a least amount of time and energy in the existing
system.

5. Proposed Enhancement:

Every software has some weakness, and to overcome some enhancements are needed that make
software powerful.

In future, few good changes will definitely make this software more powerful to work.

Following enhancements can remove its weaknesses:

 Printing facility can be included, so as to submission of reports to the customer is easier.


 Some function can be added to improve the easy usages of software.
 Security can be improved by introducing the different level user access to avoid the access to
confidential information by unauthorized user.

29
6. Conclusion:
After verification following conclusion can be drawn.

 The new system is successful in maintaining various data of customers.


 The computerized system arranges all orders and records systematically & sequentially.
 Today, in this fast world, we as man want to work fast and want sophisticated system to work
with. This project will fulfill user’s entire requirement.
 We have tried to make the software as user friendly as possible so as to bring efficiency in the
work.
 This project work really gives us opportunity to learn more and more about development of any
project.

7. Bibliography:
 The Complete Reference Java2 Fourth Edition
- Herbert Schildt

 The unified modeling language user Guide


-Grandy Booch

-James Rumbaugh

 w3schools
-https://www.w3schools.com/

30
8. ANNEXURE

ANNEXURE 1 : USER INTERFACE SCREENS (with validation)

31
ANNEXURE 3 : SAMPLE PROGRAM CODE

MainActivity.java

package com.example.carsapp;

import android.app.ProgressDialog;

import android.content.Intent;

import android.os.Bundle;

import android.text.TextUtils;

import android.view.View;

import android.widget.Button;

import android.widget.Toast;

import androidx.annotation.NonNull;

import androidx.appcompat.app.AppCompatActivity;

import com.example.carsapp.Model.Users;

import com.example.carsapp.Prevalent.Prevalent;

import com.google.firebase.database.DataSnapshot;

import com.google.firebase.database.DatabaseError;

import com.google.firebase.database.DatabaseReference;

import com.google.firebase.database.FirebaseDatabase;

import com.google.firebase.database.ValueEventListener;

import io.paperdb.Paper;

public class MainActivity extends AppCompatActivity {

private Button joinNowButton, loginButton;

32
private ProgressDialog loadingBar;

@Override

protected void onCreate(Bundle savedInstanceState) {

super.onCreate(savedInstanceState);

setContentView(R.layout.activity_main);

joinNowButton = (Button) findViewById(R.id.main_join_now_btn);

loginButton = (Button) findViewById(R.id.main_login_btn);

loadingBar = new ProgressDialog(this);

Paper.init(this);

loginButton.setOnClickListener(new View.OnClickListener() {

@Override

public void onClick(View view) {

Intent intent = new Intent(MainActivity.this, LoginActivity.class);

startActivity(intent);

});

joinNowButton.setOnClickListener(new View.OnClickListener() {

@Override

public void onClick(View view)

Intent intent = new Intent(MainActivity.this, RegisterActivity.class);

startActivity(intent);

});

String UserPhoneKey = Paper.book().read(Prevalent.UserPhoneKey);

String UserPasswordKey = Paper.book().read(Prevalent.UserPasswordKey);

if (UserPhoneKey != "" && UserPasswordKey != "")

33
{

if (!TextUtils.isEmpty(UserPhoneKey) && !TextUtils.isEmpty(UserPasswordKey))

AllowAccess(UserPhoneKey, UserPasswordKey);

loadingBar.setTitle("Already Logged in");

loadingBar.setMessage("Please wait.....");

loadingBar.setCanceledOnTouchOutside(false);

loadingBar.show();

private void AllowAccess(final String phone, final String password)

final DatabaseReference RootRef;

RootRef = FirebaseDatabase.getInstance().getReference();

RootRef.addListenerForSingleValueEvent(new ValueEventListener() {

@Override

public void onDataChange(@NonNull DataSnapshot dataSnapshot) {

if (dataSnapshot.child("Users").child(phone).exists()){

Users usersData = dataSnapshot.child("Users").child(phone).getValue(Users.class);

if (usersData.getPhone().equals(phone))

if (usersData.getPassword().equals(password))

Toast.makeText(MainActivity.this, "Please wait, you are already logged in...",


Toast.LENGTH_SHORT).show();

34
loadingBar.dismiss();

Intent intent = new Intent(MainActivity.this, HomeActivity.class);

Prevalent.currentOnlineUser = usersData;

startActivity(intent);

else {

loadingBar.dismiss();

Toast.makeText(MainActivity.this,"Password is
incorrect",Toast.LENGTH_SHORT).show();

else {

Toast.makeText(MainActivity.this, "Account with this " + phone + " number do not exists.",
Toast.LENGTH_SHORT).show();

loadingBar.dismiss();

@Override

public void onCancelled(DatabaseError databaseError) {

});

35
activity_main.xml

<?xml version="1.0" encoding="utf-8"?>

<RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"

xmlns:app="http://schemas.android.com/apk/res-auto"

xmlns:tools="http://schemas.android.com/tools"

android:layout_width="match_parent"

android:layout_height="match_parent"

android:background="@drawable/welcome"

tools:context=".MainActivity">

<ImageView

android:id="@+id/app_logo"

android:layout_width="300dp"

android:layout_height="100dp"

android:layout_marginTop="60dp"

android:src="@drawable/applogo" />

<TextView

android:id="@+id/app_slogan"

android:layout_width="248dp"

android:layout_height="wrap_content"

android:layout_alignParentTop="true"

android:layout_alignParentEnd="true"

android:layout_marginTop="153dp"

android:layout_marginEnd="29dp"

android:text="Where Car Dreams Become Reality"

android:textAlignment="center"

android:textColor="@color/colorPrimary"

36
android:textSize="30sp"

android:textStyle="bold|italic" />

<Button

android:id="@+id/main_login_btn"

android:layout_width="match_parent"

android:layout_height="wrap_content"

android:layout_alignParentBottom="true"

android:layout_alignParentStart="true"

android:layout_marginBottom="10dp"

android:layout_marginLeft="15dp"

android:layout_marginRight="15dp"

android:background="@drawable/buttons"

android:padding="20dp"

android:textAllCaps="false"

android:textSize="18sp"

android:text="Already have an Account? Login"

android:textColor="@android:color/white"

/>

<Button

android:id="@+id/main_join_now_btn"

android:layout_width="match_parent"

android:layout_height="wrap_content"

android:layout_above="@+id/main_login_btn"

android:layout_marginBottom="5dp"

android:layout_marginLeft="15dp"

android:layout_marginRight="15dp"

37
android:background="@drawable/input_design"

android:padding="20dp"

android:textAllCaps="false"

android:textSize="18sp"

android:text="Join Now"

android:textColor="@android:color/white"

/>

</RelativeLayout>

38

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy