Documentos de Académico
Documentos de Profesional
Documentos de Cultura
CHAPTER 1
INTRODUCTION
1. Luiant Software Solutions was established in the year 2012. Ever since committed to IT
services providing, Luiant has been enjoying its exponential growth with Web
2. Our IT services provide seamless integration between the customer and Luiant.
5. We serve to deliver cost effective interactive technology and design solutions without
6. Using the latest programming and design technologies, Luiant Software Solutions creates
the optimal, effective online as well as desktop experience for every client.
2
1.2 OBJECTIVE
One of the major tasks is sending the vehicles for servicing. In the manual process,
there are no provisions to know whether the vehicle need to sent for servicing, unless
Adding vehicles and/or equipment is a simple process and doesn’t require a wealth of
information.
The application will keep track of many details such as Employee number, Name,
personal information, License Information. It also allows the user to edit their
Employee Information. Under this module there will be facility to add, delete, Modify
CHAPTER 2
SYSTEM ANALYSIS
The existing system of vehicle booking is solely done at the showroom. Due to space
constraints, vehicle showrooms are generally placed at the outskirts of the city and new
customers will have to make repeated journeys to complete all the formalities.
Drawbacks
Managing huge Fleet information manually is a tedious and error prone task.
In order to schedule vehicles as well as staff, scheduler of this system should not know
how many vehicles are there on board and available for allocation.
Keeping track of repair information is a must as some times vehicles might be referred
for insurance.
The proposed system has it own advantage such as quick in processing. The proposed
system would avoid all the errors in the manual system. It also reduces human Labors and time.
The existing system is found necessary to reduce the lot of manual work in the system.
Proposed system is the computerization of the system with GUI based client server system,
which takes care of the process involved. The application gives the user easy to work with and
also carry out all the labor and product details.
Advantages
CHAPTER 3
SYSTEM SPECIFICATION
RAM : 1 GB
CHAPTER 4
SOFTWARE DESCRIPTION
C# being a .NET language, supports language interoperability, i.e. C# can access code
written in any .NET compliant language and can also inherit the classes written in these
languages. This is not possible in Java.
The code written in C#, on compilation generates an ‘.exe' or ‘.dll' file which is also
called Portable Executable file. These files contain MSIL (Microsoft Intermediate
Language) code. As against this, the Java code on compilation generates a ‘.class' file,
which contains byte code.
The portable executable file of C# can contain any number of classes, whereas, the
‘.class' file in Java contains only one class.
The methods in C# are not virtual by default. On the contrary, methods in Java are
virtual by default, which degrades the performance.
The classes in C# are grouped in Namespaces, whereas, classes in Java are grouped in
Packages.
The C# namespaces are not related to the directories. The packages in Java are directly
related with the directory names.
The variables of primitive data types in C# are more powerful. This is because even
though they are not objects functions can be called using them. The variables of
primitive data types in Java cannot call functions.
C# has features like Properties and Indexers. These features are not available in the Java
language.
SQL SERVER
ADO.NET provides a set of classes which a script can use to interact with databases.
Scripts can create instances of ADO.NET data classes and access their properties and methods.
A set of classes which work with a specific type of database is known as a .NET Data
Provider. ADO.NET comes with two Data Providers, the SQL Server.NET Data Provider
(which provides optimised access for Microsoft SQL Server databases) and the OLEDB.NET
Data Provider, which works with a range of databases.
The OLAP Services feature available in SQL Server version 7.0 is now called SQL
Server 2000 Analysis Services. The term OLAP Services has been replaced with the term
Analysis Services.
Analysis Services also includes a new data mining component. The Repository
component available in SQL Server version 7.0 is now called Microsoft SQL Server 2008 Meta
Data Services.
CHAPTER 5
PROJECT DESCRIPTION
It is difficult to communicate with the regarding sectors and specifically for educational
based area, even then the students suffer a lot to identify where to get an area of exact
information and so.
The project keeps track the information about the Vehicles, sales, service, Parts, and
services.
The details of the maintenance that are being performed such as repairs/services and to
be performed are also maintained.
The maintenance to be performed can also be scheduled for each type of vehicles. The
details of the parts/inventory used for the vehicles are maintained.
The reorder level and the reorder quantity are predefined for each particular type of
part.
The particulars of the various vendors are maintained in this system.
8
Employee Details
Customer
Vehicle
Registration
Sales
Service
Order
Employee
The details of the employees like name, designation and many other details of the
employees working in the showroom can be maintained through this application. This module
helps to give the detailed information about the newly entered joined employee and they have
to create credentials with basic information, so that they can access their updates in all aspect
of departments for communicating and customers at a specialized level in each department.
Customer
The details of the customers like name, address, vehicle booked and many other details
can be maintained through this application. Customer details must need for the sales process
and vehicle service information’s also.
Vehicle
This module is used to store all the vehicle details of the company. It contains the
information such as the reg no, engine no, owner name, address, model name, vehicle color,
brand name, reg date, fc date.
9
Registration
This module is used to stores the details of goods purchased by the company. It contains
the details such as customer name, customer id, address, phone no, vehicle model, brand name,
date booking, vehicle prize, amount paid. When the application is installed user must register
with their basic details such as name, email ID, mobile number, vehicle no, car model, and etc
before start with the application. This process is used to the user to login with the application
then only user can able to work on the application.
Sales
This module is used to stores the details of goods sale by the company. It contains the
details such as Customer name, address, phno, model name, color, prize, date of sales. This
module is used to generate the billing for each booking to the customer. Customer can pay
payment through online.
Service
This module is used to stores the details of vehicle service by the company. Vehicle
no, Customer name, phone number, model name, brand name, service date, service status and
send a mail to the customer when the service completed.
Order
This module is used to the customer booking and details and status of the vehicle
delivery by the admin. After the delivery all the information’s are stored in the database such
as delivery date, customer details and product details with payment details. This module is
used to store the booking details such as customer name, date, source destination. This details
are stored by the customer and view by the adman for maintain payment and billing.
Reports
In this module is used to show the reports of the entire transactions of the company.
All the information’s are stored in the database and reports are generated for all the purpose.
Reports can generate daily or monthly by the administrator.
10
vehicle request
Showroom
Admin / database
User response
LEVEL: 1 ADMIN
Request
Admin 1.1
1.1 login
Login Response
Add
1.2
1.2 customer
customer
view
Add
1.3 1.3 employee
employee
view
Add
1.4
Add
1.5 1.5 service
service
view
Add
1.6 1.6 vehiclereg
Vehicle
reg
12
1.7 add
1.7 Vehicle
Vehicle
view
1.8 add
1.8 Order
order
view
Reports
13
LEVEL: 2 USERS
1.1
User 1.2 registration
Registrat
ion
1.2
Login
1.3
1.2 vehicle
Vehicle
14
Primary key: Id
Table: Employee.
Primary key: Id
Table: Sales.
Primary key: Id
Table: Service
Table: tbl_UserReg
Table: Vehicle
Primary key: id
Table: vehiclereg
Registration Page
Registration page used to register the details of the users such as username, password,
full name, mobile number and Email id. Which is used to login into the user page in the
application. Registration detail is stored in the database. (Refer figure)
Login Page
Login page allows user to give the values such as username and password. Once the user
registers their details in a registration page, login can be done. (Refer Figure )
Booking Details
Booking details panel allow the user to enter the name, address, date, phone number
of the customer. (Refer figure).
Employee Details
Employee details panel will allow the admin to give input values such as Name,
Designation, Date, category, Type, overview, highlight, cost, and modify contents. (Refer
figure)
Service Details
Service details panel will allow the admin to give input values such as vehicle name,
no.of days, service Date, service name, Type, overview, description of complaints, cost, and
modify contents. (Refer figure)
Sales Details
Sales details panel allow the user to enter the sales vehicle, customer address address,
date, cost of the vehicle of the customer. (Refer figure).
Customer Details
Customer details panel will allow the admin to give input values such as Name,
address, DOB, email, mobile, gander and etc. (Refer figure)
20
Registration Page
Use can get the success message or error message from the system based on their
input values. (Refer figure)
Login page
The username and password are successfully referred from the login table and
successfully navigate to the User page. (Refer Figure)
Customer page
Admin can view the customer details which is stored by the admin. (Refer Figure).
Vehicle page
Upload page is used to allow the user to upload the vehicle image from our local disk
by admin. (Refer Figure)
Booking page
Admin can view the vehicle and deliver to the customer for booking. (Refer Figure).
Sales page
Admin can view the sales details and retrieve the information’s date wise (Refer
Figure).
Employee page
Admin can view the employee details which is stored by the admin. (Refer Figure).
Service page
Admin can view the service details of the vehicle and get the notification based on the
service delivery which is stored by the admin. (Refer Figure).
21
CHAPTER 6
SYSTEM TESTING
Output: if the username and password is correct the page will redirect into homepage
otherwise it will send alert message “invalid username and password”.
In the registration page, if the user did not give proper information like invalid email,
mobile number and etc., a dialog box with an error message will be displayed.
CAPTER 7
SYSTEM IMPLEMENTATION
Prepare for System Implementation, where all steps needed in advance of actually
deploying the vehicle showroom system is performed, including preparation of both the
production environment and the Consumer communities and also showroom details.
Deploy System, where the full deployment plan, initially developed during System
Design and evolved throughout subsequent lifecycle phases, is executed and validated.
That the details are collecting for the anamalais Toyota.
CAPTER 8
CONCLUSION
CAPTER 9
APPENDICES
Source Code
Registration Page
using System;
using System.Collections.Generic;
using System.Data;
using System.Data.SqlClient;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
try
return;
if(txtMobile.Text.Length != 10)
return;
if (!rEmail.IsMatch(txtEmail.Text.Trim()))
return;
}
29
da.Fill(ds);
if (ds.Tables[0].Rows.Count > 0)
return;
con.Open();
cmd.ExecuteNonQuery();
con.Close();
Response.Write("<script type='text/javascript'>alert('Registeration
successfully')</script>");
Response.Redirect("Default.aspx");
catch(Exception ex)
}
30
finally{
con.Close();
Response.Redirect("Default.aspx");
Login Page
using System;
using System.Collections.Generic;
using System.Data;
using System.Data.SqlClient;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
{
31
if (!IsPostBack)
Session.Remove("Table");
Session.Remove("UserId");
Session.Remove("BackPage");
try
cn.Close();
cn.Open();
da.Fill(ds);
cn.Close();
32
Response.Redirect("home.aspx");
Response.Redirect("EmpHome.aspx");
Response.Redirect("customerhome.aspx");
Session["UserId"] = ds.Tables[0].Rows[0]["id"].ToString();
Response.Redirect("UserHome.aspx");
else
{
33
Label1.Text = "Invalid!!!";
catch
finally
cn.Close();
Response.Redirect("UserRegistration.aspx");
//Response.Redirect("UserRegistration.aspx");
}
34
Employee Details
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data;
using System.Data.SqlClient;
Session["Table"] = "";
Session["BackPage"] = "";
try
35
return;
if (TextBox6.Text.Length != 10)
return;
if (!rEmail.IsMatch(TextBox7.Text.Trim()))
return;
cn.Close();
cn.Open();
36
cmd.ExecuteNonQuery();
cn.Close();
catch
try
cn.Close();
cn.Open();
da.Fill(ds);
TextBox1.Text = ds.Tables[0].Rows[0][0].ToString();
TextBox2.Text = ds.Tables[0].Rows[0][1].ToString();
37
TextBox3.Text = ds.Tables[0].Rows[0][2].ToString();
TextBox4.Text = ds.Tables[0].Rows[0][3].ToString();
TextBox5.Text = ds.Tables[0].Rows[0][4].ToString();
TextBox6.Text = ds.Tables[0].Rows[0][5].ToString();
TextBox7.Text = ds.Tables[0].Rows[0][6].ToString();
TextBox8.Text = ds.Tables[0].Rows[0][7].ToString();
TextBox9.Text = ds.Tables[0].Rows[0][8].ToString();
cn.Close();
catch
try
cn.Close();
cn.Open();
cmd.ExecuteNonQuery();
38
cn.Close();
catch
try
cn.Close();
cn.Open();
cmd.ExecuteNonQuery();
cn.Close();
catch
}
39
Session["Table"] = "employee";
Session["BackPage"] = "EmployeeDetails.aspx";
Response.Redirect("Report.aspx");
}
40
Registration
41
Login
42
Admin Home
43
Employee
44
Customer
45
Vehicle
46
Vehicle registration
47
Service
48
Sales
49
User Home
50
Order
51
CHAPTER 10
Reference Books
MacDonald, Matthew, User Interfaces in C#: Windows Forms and Custom Controls,
Apress Publisher, 1st Edition, 2002.
Patrick Smacchia, Practical .Net2 and C# 2: Harness the Platform, the Language, and
the Framework, Paradoxal Press Publisher, 2nd Edition, 2006.
Web References
www.w3schools.com
www.programmersheaven.com
www.codeproject.com
www.sourcefordgde.com
www.ieee.org
www.csharp-station.com