Car portal- Ewa final assignment

Online business portal - used vehicles
P a g e 1 | 38
ASIA PACIFIC INSTITUTE OF INFORMATION TECHNOLOGY
PANIPAT (HARYANA – INDIA) – 132103
Enterprise Web Applications (CE00365-3)
Topic: Online business portal for sell and purchase of used vehicles
Lecturer: Mr. Ravi Sachdeva
Date Assigned: 29th January 2014
Date Due: 15th APRIL, 2014
Submitted By: Prince Kumar (PT082219)
Level -3: Com

P a g e 2 | 38
A.Acknowledgement
To acknowledge and thank every individual, who directly or indirectly contributed to this
venture, personally it would require an inordinate amount of time. I am deeply indebted to
many individuals whose cooperation and encouragement has made job considerable easier.
I am very much willing to express my sincere gratitude to APIIT SD INDIA, Panipat for
providing such an opportunity for fulfilling my most cherished desire of reaching the goal. I
too take this opportunity as a great privilege to express gratitude to my parents and friends for
their support and encouragement throughout the project.
A single word would not suffice the contribution made by some of the faculty of APIIT SD
INDIA who were always there in time of need. I greatly acknowledge the working and
contributing of: Mr. R.K. Choudhary (Director- APIIT SD INDIA) who encouraged us with
all kinds of facilities and idea.
Mr. Ravi Sachdeva (Module Lecturer) who was standing with me in all difficulties and guided
me throughout the project. I would also like to acknowledge him contribution in making this
subject lot easier for the students and providing every possible help to the students.

P a g e 3 | 38
B.Certificate
This is to certify that Prince Kumar, a student of A.P.I.I.T SD INDIA, Panipat
(Final Year, Computing) have successfully completed the individual project on “Online
business portal for sell and purchase of used vehicles”, of module Enterprise
Web Applications. Under an absolute guidance of Module lecture Mr. Ravi Sachdeva.
He was found honest, diligent towards his assigned project work. I wish him all
the best for his future accomplishments.
Submitted By: Signature:
Prince Kumar Mr. Ravi Sachdeva
Intake no: PT1082219

P a g e 4 | 38
Contents
A. Acknowledgement.........................................................................................................................2
B. Certificate ......................................................................................................................................3
1.0 Section A..........................................................................................................................................5
1.1 Introduction.................................................................................................................................5
1.2 Purpose of the System.................................................................................................................6
1.3 Topic Background.......................................................................................................................6
1.4 Project Objective.........................................................................................................................7
1.5 Project Scope...............................................................................................................................7
1.6 Target Audience..........................................................................................................................8
1.7 Project Schedule..........................................................................................................................8
1.8 Summary Of the major Functions of website...........................................................................8
2.0 Section B ........................................................................................................................................12
2.1 Requirement Specification .......................................................................................................12
2.1.1 Page Description.................................................................................................................13
3.0 Section C........................................................................................................................................17
3.1 Design and Modelling ...............................................................................................................17
3.1.1 Database Structure ............................................................................................................17
3.1.2 Interface Design..................................................................................................................22
3.1.3 Web Site Architecture .......................................................................................................27
3.1.4 Web page descriptions.......................................................................................................28
4.0 Section D........................................................................................................................................32
4.1 Implementation .........................................................................................................................32
4.2 Problem Encountered and Solution ........................................................................................34
5.0 Section E ........................................................................................................................................35
5.1 Conclusion .................................................................................................................................35
6.0 Section F.........................................................................................................................................36
6.1 References..................................................................................................................................36
7.0 Section G........................................................................................................................................38
7.1 Appendix..............................................................................................................................38
7.1.1 Gantt Chart ........................................................................................................................38

P a g e 5 | 38
1.0 Section A
1.1 Introduction
Auto Bazar offers online ad solutions for automakers and sellers to connect with the most
qualified buyers shopping for used vehicles providing the features as:
 Connect with dealers to buy used cars.
 Being Paid Member: Free user can send request to admin to become paid member.
 Customization: Users can customize their profile according to their choice.
 Feedback: Visitors can send feedback to admin.
 Login: There are three login (Free, Paid and Admin). Only registered users should be
able to login.
 Message: Admin can send private message to single and multiple users. Paid and free
member can only view admin message.
 Search Used Vehicles: Now registered users can search used vehicle with
specifications according to their Profile boundaries
 Upload Vehicle: Users can upload their used Vehicle photo but only registered
subscribers would be able to upload vehicle details.
 User Registration: Registration page is there for Visitor/anonymous user. The system
maintains two types of users: Free Subscriber and Paid Subscriber.
Millions of vehicle purchasers visit these web applications each month which connects a buyer
and a seller every fraction of seconds. This proposed web based application framework
“Online business portal for sell and purchase of used vehicles” as outlined above is an
attempt to provide a faster growing automotive marketplace for buyers and sellers. It will be
the destination for those who are looking to buy or sell a used car. With the vehicle listings
from nearly thousands of dealers nationwide with classified and private-party listings it will
offer the best selection of used cars online, as well as the content and advice to support the
shopping experience. This system will help to grow and strengthen the relationship between
registered auto classified dealers (suppliers, sellers) and consumers (visitors- Free users,

P a g e 6 | 38
buyers, Paid users, etc.) while providing its users with the best online Auto Shopping
experience.
1.2 Purpose of the System
The purpose of this document is to give the overview of the system. The main aim of the project
is to develop an application outline that is centered on enhancing and facilitating the
communication among the different participating entities involved in the business of Auto
Marketing systems including owners, buyers, sellers, car dealers, auto classified businesses and
market researchers.
With this application, site visitors can search by make and model to access new and
used car inventories from local dealers & independent sellers. This application framework
combines powerful inventory search features for used car configuration with pricing
information, photograph, and description. This application also provide two main features that
is searching and customization.
1.3 Topic Background
An Auto Portal system offers ad solutions for automakers, sellers and dealers to connect with
the buyers shopping for used vehicles. Used Vehicles portal are paid ones through access to
them is free but services like while searching of vehicles the details of the seller are not shown
to free user for this free user is unable to see the actual content of the sites and in most of the
sites free user have limited functionalities which cannot fulfill the needs of the user. In that the
users finds difficulties in selling their used vehicles and while searching with actual information
about the vehicles and many more. Nowadays, presently there is lack of proper system in
market which can fulfill the needs of the users.
There is a huge demand of such website which can handle the overall flow in an easy way.To
overcome from the existing system problem, Developer is implementing an online web based
application i.e., “Online business portal for sell and purchase of used vehicles” which attempts
to provide a better service to automotive marketplace for sellers and buyers.
Auto bazar is a kind of business portal for used cars which help the user to sell and buy vehicle
in effective manner.

P a g e 7 | 38
1.4 Project Objective
Objective of the system is to provide better solutions for the portal users who are willing to sell
and purchase vehicles. Portal should be user friendly as much as possible. Developer provide
whole system in such a way that it would be more flexible than previous system in order to add
more new functionality to its real time users. The developer has develop this system for seller
and buyer. The objective is to provide common platform for seller and buyer.
1.5 Project Scope
This application framework can be expanded and utilized by site developers to create a
customized portal for large auto classified organization. Online business portal for used
vehicles website is only for cars. The scope of the system allow developer to know about the
limitations of the proposed system. The system is designed for the people who is having much
more interest in sell and purchase vehicles. The proposed system is a website developed for
people who wants to sell their vehicles and purchase vehicles. This system provides all library
portal functionalities in one where user can upload their vehicles, can search used cars, can
customize web pages according to their choice.
 The system is not for mobile devices. Therefore the users cannot access the system
everywhere. They have to have their laptops/desktop to enjoy the services provided by
the system.
 The system is limited for Indian Territory. Therefore no foreign people can register in
the System and avail facilities which is otherwise not present in the past system.
 The system is developed in English. Therefore the user can not convert the system in
his Native language
 The website content is limited in terms of user. Some of the information about the user
is provided when then user is registered.

P a g e 8 | 38
1.6 Target Audience
Vehicle Seller: Those users who wants to sell their used vehicles.
Vehicle buyer: Those users who wants to buy used vehicles.
Vehicle Dealer: The user who gives the common platform to buyer and seller to interact.
1.7 Project Schedule
Refer to Appendix 7.1.1
1.8 Summary Of the major Functions of website
The major functions of the system are given below:-
1. Functions of Administrator
1.1 Adding new Vehicles/Subscribers.
This functionality will allow admin to add new vehicles and new subscribers. In add
subscriber admin will perform registration task of user as in part of adding vehicle admin
will upload the vehicle with details.
Vehicle Seller
Vehicle Buyer
Vehicle Dealer

P a g e 9 | 38
1.2 Approving/Rejecting Uploaded Vehicle Details
In this functionality admin has the right to accept or reject the details of the vehicles. When
user will upload the vehicle then the request will be sent to admin and after that admin will
approve or reject the vehicle. This functionality will help to check whether the details of
the vehicle is correct or not.
For example :- if the details and picture of the vehicle is not for the website then admin will
reject the vehicle request from the user and admin will maintain the dignity of the website.
1.3 Deleting existing Vehicles/Subscribers.
This functionality will allow admin to delete subscribers and vehicles. For example: User
is provided wrong information about their profile then admin can delete subscriber.
Likewise in vehicle if any user is provided wrong information then admin can delete
1.4 Setting Status of members as free subscriber/paid Subscriber.
This functionality includes approval of payment request which will be sent by free
subscriber to admin and then admin will approve the user request to paid subscriber. For
example: Like Free user has to become paid member, then free user will sent payment
request to admin in the form of DD/Cheque then admin will check the details of the
payment after that admin will set status to Paid. Admin can directly set user status to paid.
1.5 Searching Vehicles.
This includes searching of vehicles with brand, model and with max and min. price. This
will be easy to check whether the user is getting appropriate information about the vehicle
and user.
1.6 View Feedback of Free and Paid User.
This includes feedback given by the free and paid user. It will help admin to main decorum
of the website.
1.7 Send Message.
This includes sending message to paid and free subscriber. Admin has the permission to
send message to single and multiple subscribers. For example: Admin has to convey
message then admin has to send message to single or multiple subscriber

P a g e 10 | 38
1.8 Viewing list of all free subscribers /paid subscribers.
In this admin can view user details of the free and paid subscribers. This will help admin
to maintain records of the users with user details and payment methods.
2. Functions of Paid User
2.1 Change Password
Paid user can change their password. This help to avoid hacking, For example: in case user
password is hacked by other user, to prevent this hacking there is need of change password
in user profiling.
2.2 Edit Profile
The paid user have the right to edit their profile so that if they have entered any wrong
information during registration then it can be changed.
2.3 Search Used Cars
and user.
For example: If user is searching any vehicle, then user will get the information about the
uploaded person with vehicle details.
2.4 View Admin Message
In this paid user can view the message sent by the admin so that paid user can update their
profile as per the command or suggestions given by the admin.
2.5 Upload Vehicle
In this paid user can upload their vehicles and the request will be send to the admin for
approval.

P a g e 11 | 38
3. Functions of Free User
3.1 Edit Profile
The free user have the right to edit their profile so that if they have entered any wrong
information during registration then it can be changed.
3.2 View Admin Message
In this free user can view the message sent by the admin so that paid user can update their
profile as per the command or suggestions given by the admin.
3.3 Upload Vehicle
In this paid user can upload their vehicles and the request will be send to the admin for
approval of vehicle.
3.4 Search used cars
and user.
For example: If user is searching any vehicle, then user will not get the information about
the uploaded person only vehicle details will be shown to user.
3.5 Change Password
Free user can change their password. This help to avoid hacking, For example: in case user
password is hacked by other user, to prevent this hacking there is need of change password
in user profiling.

P a g e 12 | 38
2.0 Section B
2.1 Requirement Specification
There are three types of user in the system:
Free User
Free user can register as visitors of the system. Who will be having limited functionality like
user can search used vehicle but contact information will not be shown to free user and then
second functionality free user can only view admin message and third user can update their
profile and then if free user wants to use more functionality in search menu then user has to
become paid member i.e., payment request this is another functionality of the free user and
then fourth free user can change their password i.e. change password and then free user can
upload vehicle.
Paid User
Paid user will not have to register themselves, user become paid when admin approves their
payment process. Paid user can search used vehicle with contact information of the seller.
Paid User can upload vehicle. User can view admin message User can change their password
i.e. change password.
Admin
He is the user who can maintain the system and regulate the services. Admin has all rights to
access the whole system and database. Admin has the responsibilities to maintain the user
status and having the maintenance of the whole system time to time as up gradation.
Challenges in Project
The main challenge for developing such system is:
 To understand the concepts that are followed in recruitment on all the three levels,
“Free user ‟, „Paid User‟ and the ‟admin‟.
 24X7 Availability: Steps have to be taken to make the system available throughout so
that the user can access it anytime. Moreover such a kind of facility makes it efficient
and effective than the traditional system.
 Fake ID‟s creation need to be checked as in online system this is one of the most

P a g e 13 | 38
Common found issues. A check need to be done so as to prevent this.
 Payment request will be done in proper way.
2.1.1 Page Description
Functionality: user_registration
Information Mandatory Types of
information
Validation
First Name Yes Text Box Required Field
Validator
Last Name Yes Text Box Required Field
Validator
User Name Yes Text Box Required Field
Validator
Email Id Yes Text Box Required Field
Validator
Password Yes Text Box Required Field
Validator
Confirm Password Yes Text Box Compare validator
and Required Field
Validator
Gender Yes Dropdown List Required Field
Validator
Mobile Number Yes Text Box Custom Validator
and Required Field
Validator
State Yes Dropdown List Required Field
Validator
City Yes Dropdown List Required Field
Validator
Address Yes Text Box Required Field
Validator
Pincode Yes Text Box Required Field
Validator
This page related to the user registration process where user can register all the information
Required for making user account in the Portal.

P a g e 14 | 38
Functionality: Upload_vehicle
information
Validation
Brand Name Yes Dropdown List Required Field
Validator
Model Yes Dropdown List Required Field
Validator
Version Yes Dropdown List Required Field
Validator
Kms Driven Yes Text Box Required Field
Validator and
custom validator
Fuel Type Yes Dropdown List Required Field
Validator
Color Yes Text Box Required Field
Validator
Condition Yes Text Box Required Field
Validator
Description Yes Text Box Required Field
Validator
Upload Photo Yes Browse Image None
Price Yes Text Box Required Field
Validator and
custom validator
User ID Yes Label None
Contact Name Yes Label None
E-Mail Id Yes Label None
Phone Number/Cell
Number
Yes Label None
This page related to the Vehicle uploading process where user can upload vehicle with contact
details, account details of the user will be taken from the session of the user.
Functionality: Send Message
information
Validation
User ID Yes Check Box List None

P a g e 15 | 38
Subject Yes Text Box Required Field
Validator
Message Yes Text Box Required Field
Validator
This page related to the Messaging process where admin will send message to single or multiple
Users. User Id will be in Check Box List.
Functionality: Admin_Login
information
Validation
User Name Yes Text Box Required Field
Validator
Password Yes Text Box Required Field
Validator
This page related to the Login process where user name and password will be taken from
database of admin login.
Functionality: Free_User_Feedback
information
Validation
User_id Yes Text Box None
Validator
Validator
This page related to the Feedback process where user enter subject and message and then data
will be store in freeuser_feedback table.
Functionality: Paid_User_Feedback
information
Validation
User_id Yes Text Box None
Validator
Validator

P a g e 16 | 38
This page related to the Feedback process where user enter subject and message and then data
will be store in paiduser_feedback table.

P a g e 17 | 38
3.0 Section C
3.1 Design and Modelling
3.1.1 Database Structure
Table Name: admin_Login
SI. No Table Name Data Type Description
1. user_name Varchar(20) This is the user
name of the admin
used for login.
2. password Varchar(20) This is the password
of admin used for
login.
Table Name: Brand
1. Brand_Id Varchar(30) Unique Number of
Brand which would
be used as reference
in Model
2. Brand_Name Varchar(30) Name of the Brand
of the car.
Table Name: city
1. StateID Varchar(30) Unique Id of the
state which would be
used as reference in
City.
2. CityID Varchar(30) Unique Id of city.
3. CityName Varchar(30) Name of the city.

P a g e 18 | 38
Table Name: freeuser_feedback
1. user_id Varchar(30) User Id of the User.
2. Subject Varchar(30) Subject of the
feedback.
3. Message Varchar(30) This field is for
message where user
can suggest or
comment.
Table Name: message
1. user_id Varchar(30) User name of the
user.
message.
3. Message Varchar(500) This field is for
message where
admin can give
notifications to user.
Table Name: Model
1. Brand_Id Varchar(30) Unique Id for Brand.
This is the reference
in Brand Table.
2. Model_Id Varchar(30) Unique ID of the
Model
3. Model_Name Varchar(30) Name of the model
of Brand.
Table Name: paiduser_feedback
1. user_id Varchar(10) User Id of the User.

P a g e 19 | 38
feedback.
3. comment Varchar(300) This field is for
message where user
can suggest or
comment.
Table Name: State
1. StateID Varchar(30) Unique ID of State.
2. StateName Varchar(30) Name of the State.
Table Name: upload_vehicle
1. Brand_name Varchar(20) Name of the Brand.
2. Model Varchar(20) Name of the Model
as per Brand.
3. Version Varchar(20) Name of the version
as per Model.
4. Kms Varchar(20) Km covered by
vehicle.
5. Condition Varchar(20) Condition of the
vehicle.
6. Description Varchar(20) Details of the
Vehicle.
7. Upload_photo image Content of the
image.
8. Price Varchar(20) Price of the vehicle.
9. User_id Varchar(20) Unique Id of user.
10. Contact_name Varchar(30) First and last name
of the user.
11. Email_id Varchar(30) Email Id of the user.
12. Phone_number Varchar(15) Contact Details of
the user.

P a g e 20 | 38
13. Status Varchar(30) Status of the user in
terms of paid or free.
14. Fueltype Varchar(30) Fuel type of the
vehicle in terms of
CNG, Petrol or
diesel.
15. Color Varchar(30) Color of the vehicle.
16. Vehicle_id int Unique ID of the
vehicle.
Table Name: user_registration
1. first_name Varchar(30) First Name of the
user.
2. last_name Varchar(30) Last Name of the
user.
3. user_name Varchar(30) User name used for
login.
4. Email_id Varchar(40) Email of the user.
5. Password Varchar(50) This is the password
used for login.
6. Gender Varchar(10) Gender of the user.
7. Mobile_no Varchar(20) Contact number of
the user.
8. user_status Varchar(20) Status of the user In
terms of paid and
free.
9. Cheque_no Varchar(20) Cheque Details of
the user
10. dd_no Varchar(20) DD Details of the
user.
11. User_id Int Unique ID of the
user.
12. State Varchar(30) State of the user.
13. City Varchar(30) City of the user.

P a g e 21 | 38
14. Address Varchar(50) Address of the user.
15. Pincode Varchar(30) Pincode of the user.
16. Bank_name Varchar(50) Bank name of the
user for payment.
16. Theme Varchar(30) It contains current
theme of the user.
Table Name: Version
1. Model_Id Varchar(30) Unique Id of the
Model
2. Version_Id Varchar(30) Version Id of the
Model.
3. Version_Name Varchar(30) Name of the Version
as per Model.

P a g e 22 | 38
3.1.2 Interface Design
Fig: 3.1.2.1
This is the login page of free user, where free user enter user name and password. This will
be done by only user registration. Login of Paid user will be same as login page of free user.
Fig: 3.1.2.2
This is admin login page where admin will enter user name and password.
Enter User
Name
Enter
Password
Click To
login
Paid User
login
Admin login
Enter User Name
of admin
Enter Password
of admin
Paid User
login
Free User
login
Click To login admin
homepage
Website
Logo
Website
Banner
Website
Banner
Website
Logo

P a g e 23 | 38
Fig: 3.1.2.3
This is admin home page which consists of menus like add vehicle, add subscriber, delete
subscriber, delete vehicle, and many more. Where admin can handle website content.
Session
Menu Bar
Menus
Website Logo
User Name
List
Subject
Message
Click to send message
Logout From the session

P a g e 24 | 38
This windows shows the user list of the member where admin will send message to single or
multiple user of the system with subject and message this act as a notifications.
Fig: 3.1.2.5
Admin will able to set status of the member. When free user sends payment request to admin.
Then admin approve their request to become paid member
Fig: 3.1.2.6
User RequestDD Details
Cheque Details
User Status
Search by brand or price
Details of search cars

P a g e 25 | 38
User will able to search with brand name, with price and details will be shown below the
search button
Fig: 3.1.2.7
This is the view message window where user will get the notifications from the admin.
View Message By Admin
Details of upload vehicle
Details of user
Click to upload

P a g e 26 | 38
User can upload their vehicle with details and user details will be taken from the session
itself.
Fig: 3.1.2.9
User will send payment request by selecting mode of payment and then name of the bank and
then cheque/dd details.
Click to submit payment details
Select mode of
payment
Enter Details of Bank
Enter Payment Details

P a g e 27 | 38
3.1.3 Web Site Architecture

P a g e 28 | 38
3.1.4 Web page descriptions
Design Decision
The Design decision consist of stages like prototyping, storyboarding etc. Decision will be
done during designing process to increase the quality of the website and to make more practical.
Design Decision will be done on position, layout, font size, font, table, div, hyperlink, image
and so on. Some are listed below:
 Grid View: Grid view is used to retrieve data from database and to display the records.
Grid view is also applicable for editing, updating, for displaying records and Deleting.
 Access Data Source: This tag is used to configure data base with the grid view.
 Table: Table tag is used for mainly the alignment purpose.
 Div.: Div. tag is used to gather contents of the main portion of the website according
the need. Simple changes will be done to in CSS.
 Form: Form tag is used to access the asp controls available on the webpage. Simply
writing runat: ‘server’ will made it favourable to use asp controls inside the form.
 Heading: Heading tag is just used to display the heading of the page. It increases the
Web accessibility of the website. Such as, if a blind person tries to access the website,
heading should be read as heading not only a simple text.
 Style sheets: Style sheets are used to perform mouse hover event on the hyperlinks. It
is applied by both internal and external. Inline style is also used in the website. The
website that has been planned to design has been gone through three stages for
completion.
 Label: It is used to simply display the text.
 Textbox: It is used to enter the input by the user.
 Drop down List: This is used to display the possible inputs in drop down.
 Radio Button List: This is used to show inputs in checkbox form, but only one input
can be selected.
 Button: This tag is used to perform some action on click event.
 Image Button: This tag is also similar to button tag but instead of text it consists of
images and is used while displaying images on buttons.
 Required Field Validation: It is used to validate any field with the compulsion
Of fill.

P a g e 29 | 38
 Regular Expression Validation: It. is used to validate the format of the field to
which it is connected.
 Compare Validation: This is used to compare the input of two fields.
 Other: Other decisions regarding colour, size, font and other style
The website that has been planned to design has been gone through under three stages
for completion.
Fig 3.1.4.1
1.0 Coding
 Design the form taking asp controls by simply drag and drop onto the page.
 Align the page, contents must be fully aligned. Table tag is used to align the page
properly.
 Complete the design by pouring colours, selecting appropriate size and position of the
controls.
 As the design has ready, data base connectivity has to be done if needed and Database
connectivity of the form controls with the database has been done.
 The below listed classes are imported and their objects are used for connectivity.
System.Data.sql.client
System.Data
System.Data.IO
 Results and instructions for the database queries are viewed with the help of Grid
View and Message boxes.
 When the coding completes the next stage is validation.
Design Decision
1.0 Coding
2.0 Validation
3.0 Web Accessibilty and Test

P a g e 30 | 38
2.0 Validation
 The input fields present if the page must be validated. So that the controls like text box,
radio buttons are validated with the help of validators provide by asp.net framework.
These are:
a. Required Field
b. Regular Expression
c. Compare
 Required field is used when a field must be get field by the user. If required field
validator is applied on any field it can’t be left empty by the user.
 Regular expression is used to enter the data in a particular format. To describe the
format various symbolic codes are there. This validator acts as a barrier for wrong
format inputs.
 Compare validator is simply used to compare two fields. It controls two fields and the
data of those fields must be the same.
 After validating the controls, form authentication has been applied.
 Form authentication means to write few asp codes that will restrict the usage of web
pages only by the preferred users.
 Complete website should be authenticated to prevent the undesirable access of the
website.
3.0 Web Accessibility and Test
 After the completion of above stages. The last stage is to check the web accessibility
of the website.
 Web accessibility is provided to the website with three main measures as given
below:
a. Heading: Heading tag has been provided so that the physically disable person
can also differentiate between simple text and heading.
b. List: List has the same function that the blind person can also perceive that
the data is represented in a list.

P a g e 31 | 38
c.Alt: Alt tag of image is used so that if the image will not display due to any
reasons, the text written in alt tag would be there, that would represent the
image.
 The website has been fully tested for errors and authentication rights. Each web page
has been tested for authentication. Website is fully completed and is ready to
implement.

P a g e 32 | 38
4.0 Section D
4.1 Implementation
Steps1: Open Microsoft visual studio 2010. Go to New Then Choose Website and then give
the name of the website and location where have to store the website.
Step2: Make Folder for Admin, Free, CSS, Image, App_Data to work in manner.
Step3: Make database (Portal.mdf) in that make separate table for user_registration,
admin_login, Brand, city, freeuser_feedback, message, paiduser_feedback, state.
Step4: Make Master page for each user.
Step5: First of all make user_registration write connection query which connect system to
database and then write insert query in user_registration.aspx.cs.
Step6: Then make user login for free and paid user and then make some related pages like
About us, contact information and Help.
Step7: Then in free user make homepage, Edit Profile, Search Used cars, Upload Vehicle,
View admin message, Paid request, change password and feedback forms.
Step8: In Edit profile insertion and Updation is there. The data is retrieving according to
their user id.
Step9: For search used car Brand Name, model name is retrieving from database. Then on
the button click of the search there is query for search, Image will be retrieve with
the help of handler.
Step 10: In upload vehicle page Brand name, model and version is retrieving from the
database. Then simple insertion is there, for image upload image has to convert in
Binary format.
Step 11: Then come to payment request user has given option to enter bank name with cheque
and DD details and then change password is there to prevent hacking and there is
Another page which is for feedback where user can give feedback to admin and view
Message will be shown according to the user name with the help of grid view.
Step 12: Now come to paid user, in this user can search used car with contact information of
the vehicle. Another page paid user can only view message according to their user
name this will be done with the help of grid view.

P a g e 33 | 38
Step 13: Feedback form is given to the paid user which will be sent to admin.
Step 14: Now come to admin part. There is insertion which will be done on to add subscriber
and as same on add vehicle and then delete vehicle and subscriber will be done with
the help of grid view. On back view code will be there to delete user and vehicle
From the Specified table.
Step 15: Then another task whether admin will approve request for paid and to approve
Vehicle.
Step 16: Then Feedback part will be done, simply data will be shown to admin with user_id,
Subject and message.
Step 17: Then there is page where customer details will be shown to admin.
Step 18: Run the code
How customization will be done on Web Pages:
The customization of the web pages is done mainly for the user so that it can change the theme
using runtime environment. Customization was possible by:
 Change Theme: It will change the Color of the website and user will experience new Color
of the website.
 At the time of registration the default theme and skin is set.
 Then after the user is login and can change its theme.
 The theme is stores in user database as per specific user and when the user again log in then
the user will have the saved themes.

P a g e 34 | 38
4.2 Problem Encountered and Solution
Fig 4.2.1
The Error regarding while changing the theme. Developer assign to write in the PerInit code
in every page.
Fig 4.2.2
The error related to date & time. Developer try to solve this but developer fail to solve this
error. Sometime code will run and sometime this problem occur.

P a g e 35 | 38
5.0 Section E
5.1 Conclusion
Online business portal for sell and purchase of used vehicles system provides a better way for
faster searching and uploading; it is a portal system which is meant for seller and buyer. There
are several things which are important in a car portal like making free user to paid user,
searching vehicles according to their profiles. After a complete indent of hard work I conclude
that the project was absolutely challenging for implementing features such as searching
according to their free and paid user. The project is comes out to be successful in some way.
Quickly summarizing all the efforts put into this assignment, I would like to conclude that this
assignment has definitely helped me enhancing my Web Designing skills and improve my
existing knowledge in ASP.NET in a unique way. I learnt various essentials of web designing
as well as learnt more of Grid View, Image Handling, Web Personalisation, Web Accessibility
and CSS. I have also learnt of how to work with Image handling in ASP.net, using various SQL
commands and its structure. This assignment has helped in incorporating all the important and
necessary features required in any dynamic website.
Last but not the least, I have also learnt the importance of Grid View, Image Handling, Web
Personalisation, Web Accessibility, CSS and learnt the proper methodology of developing web
related projects. Like any other web-application, my website had errors; I had also performed
proper testing so as to ensure that my website remains robust, usable and manageable. Working
as a .net Web application designer and Programmer proved quite of a unique experience. I am
sure this project would be beneficial for me in the near future.
Future Enhancements
 The Car portal can be designed with the help of technologies like Silverlight, CSS3 and
HTML 5 in order to provide more interactive and rich internet web based applications.
Local and multiple language support will enhance the portals rating and thus improves
the search engine optimization.
 Personalization will be done like changing font style, change theme this help user to
attract more towards website.
 Providing Messaging functionality in user profile.

P a g e 36 | 38
6.0 Section F
6.1 References
Websites
Unknown [2010]. Using the Validation Controls. - Aspalliance
Available: http://aspalliance.com/chapters/chapters/0672328232/Walther_ch03.pdf.
Last accessed 03th April 2014.
Unknown [2008] Validation Controls. - Mokkie
Available:http://www.mokkie.com/book/aspnet_wkbk_2nd_ed_sample_validator_chapter.pd
f. Last accessed 04th April 2014.
Scott Mitchell. [2014]. Working with Data in ASP.NET2 .0: Querying Data with the Sql
Data Source Control. Available:
http://i2.asp.net/asp.net/files/DataTutorials/datatutorial47cs.pdf?cdn_id=2014-04-02-001.
Scott Mitchell. [2014]. Working with Data ASP.NET2 .0: Inserting, Updating, and Deleting
Data with the Sql Data Source. Available:
http://i2.asp.net/asp.net/files/DataTutorials/datatutorial49vb.pdf%3Fcdn_id%3D
Mudassar Khan. [05 Oct 2012]. Bind Grid View using SqlDataSource Programmatically
from code in ASP.Net. Available: http://www.aspsnippets.com/Articles/Bind-GridView-
using-SqlDataSource-Programmatically-from-code-in-ASPNet.aspx.
Last accessed 10th April 2014
Books
 Dino Esposito. (2011). Chapter 7.Working with the Page. In: Dino Esposito
“Programming Microsoft® ASP.NET 4.” USA: Microsoft Press.

P a g e 37 | 38
 Dino Esposito. (2011). Chapter 10.Data Binding. In: Dino Esposito “Programming
Microsoft® ASP.NET 4.” USA: Microsoft Press.
 Matthew MacDonald. (2011). Chapter 12. Styles, Themes, and Master Pages. In:
Matthew MacDonald “Beginning ASP.NET 4 in C# 2010” USA: Apress.
 Matthew MacDonald. (2011). Chapter 13. Website Navigation. In: Matthew
MacDonald “Beginning ASP.NET 4 in C# 2010” USA: Apress.
 Stephen Walther; Kevin Hoffman; Nate Dudek. (2010). Chapter 3. Using the Validation
Controls In: Stephen Walther; Kevin Hoffman “ASP.NET 4 Unleashed” USA: Sams.
 Stephen Walther; Kevin Hoffman; Nate Dudek. (2010). Chapter 9. Using the
SqlDataSource Control In: Stephen Walther; Kevin Hoffman “ASP.NET 4
Unleashed” USA: Sams.
 Stephen Walther; Kevin Hoffman; Nate Dudek. (2010). Chapter 11. Using the Grid
View Control In: Stephen Walther; Kevin Hoffman “ASP.NET 4 Unleashed” USA:
Sams.

P a g e 38 | 38
7.0 Section G
7.1 Appendix
7.1.1 Gantt Chart

Car portal- Ewa final assignment

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (16)

Ähnlich wie Car portal- Ewa final assignment

Ähnlich wie Car portal- Ewa final assignment (20)

Mehr von Prince Kumar

Mehr von Prince Kumar (12)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Car portal- Ewa final assignment