[attachment=3854]
Project Title :Automobile Inventory System

---

Presented By;
NAME: JGME DORJI.
BCA VI B
ROLL NO: 560748197.
APEX.
(Singye Agencies)

---

Introduction
Now days the computer has become one of most important needs in every field like scientific research, business activities, entertainments, educative fields etc. From this importance the computer soft ware became one the most important technology which provides interface and solution for the modern people.
One of the most important applications of the computer is to assist researcher, manager or any individual in solving problems by analyzing the data provided by the individuals and store records or data and provide up to date information and data to the individuals for the efficient management of their organization.
It is thus very important for all learners of computer science to know how to design computer-based information systems to aid management. Besides that birth of object oriented and platform independent programming language has changed a great deal in programming styles and logic. So the Dot NET has become more important and popular language among the co-IT workers and also the professionals.
Due to the advancement of information Technology in present era it really important for computer students to choose a appropriate topic for the project as the partial fulfillment of the requirement for their degree. So therefore I have done Automobile inventory system as the partial fulfillment for the degree of BCA.

Objectives

Few objectives of the project are:
The general objective of this project is to minimize the manual work.
The overall objective of this database is to store information of vehicle purchased from supplier and keep records of all the transaction made in the organization.
Viewing and updating of stock details, purchase details and sales details.
To keep the record of customers.
To keep the details of the supplier.
To generate reports for purchase, invoice and sales and can print out the reports and can also save it.
To generate invoice to the customers.

Tool Used

VB.Net (front end):
Visual basic dot net (vb.net) is an object oriented programming language (OOP), from Microsoft. It supports all key OOP feature like polymorphism, inheritance, abstraction, encapsulation. It is the dot net version of visual basic (VB) language. Vb.net uses common language runtime(CLR) for program execution. It is one of the most popular way of developing a windows application.
NET Framework is used by Microsoft SQL Server to offer high-performance database access.

SQL server (backend):
SQL (pronounced as ess-que-el) stands for structured query language which is used to communicate with database. According to ANSI (American National Standard Institute), it is a standard language for RDBMS. It lets us access, retrieve, manipulate, update and manage data on a database.
SQL command such as select, update, delete, create and drop can be used to accomplish almost everything the one need to do with the database. SQL Server 2000 Enterprise Edition is the most comprehensive version of SQL Server 2000 and supports the full set of SQL Server 2000 features. This version is most appropriate for large organizations that need to manage immense amounts of data quickly and efficiently.

Requirement Analysis

Requirement analysis is one of the crucial and first steps towards the development of any project. The primary objective of Requirement Analysis is to describe the needs and the requirement of the customer. Requirement analysis provides the software designer with representation of information, function, behavior that can be translated to architectural, interface and component-level designs.
Followings are the few points related to this system (Automobile Inventory System)
Buying of vehicles by the organization from the individual supplier.
Selling of the vehicle to the customers(i.e sales records)
Generating invoice to customers.
Automatic updating of Stock.
Viewing and updating of stock details, purchase details and sales details.


Module Description
Generally this project is divided into five main Modules.
¢ Login Module
¢ Supplier registration module.
¢ Purchase Module
¢ Sales module
¢ Customer module

Login Module:
This module is just an entry point, through which any user/employee can log into the system and can operate on the system provided they know the Administrator name and password. In order to log into the system, user/employee has to type the Administrator name and password in the field provided

Supplier registration module:
Basically any Enterprise or organization has regular suppliers and they keep their details in the database. It is fact that the number of suppliers may increase or decrease. So in this module we can add the new supplier and Delete/Remove the existing suppliers.

Purchase Module:
The details of the transactions made with the suppliers are recorded in this module. When the vehicles are purchased and stored the stock gets automatically updated.

Sales Module:
The out flow of goods (vehicle) from the Stock are recorded in this module. When we sale the vehicles from store and enter their details, it will automatically deduct the Stock value and so the Stock gets updated. We can view sales details. We can print the bills for customer when sales are made.

Customer Module
In this module, customer details (i.e phno, address, etc..) and kind of vehicles that they have booked along with the booking amount paid..etc. are maintained. We can easily view/update the customer table.
Entity Relationship Diagram

Dataflow Diagrams
A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system. It differs from the flowchart as it shows the data flow instead of the control flow of the program.
With a dataflow diagram, users are able to visualize how the system will operate, what the system will accomplish, and how the system will be implemented. The context Diagram for the Automobile Inventory System considered in this project is shown below.
Level¬-0

Level - 1
Level-1.1
Level-1.2
Level-1.3

Level-1.4
Level-1.5

Data Dictionary

Singye Agencies: Name of the organization
User/Employee: A person who operates the system.
Supplier: One who supplies vehicles to the organization is called supplier. It includes an enterprise, a person or a company. Supplier doesnâ„¢t change very often. It is important in the business that we keep the details of suppliers.
Customer: Any one who comes to the organization and orders a vehicle or asks for service is called customer.
Purchase: purchase of vehicles by the organization from the individual suppliers.
Sale: sale of vehicles by the organization to the respective customers.
COF: Customer Order Form (COF) is a form that needs to be filled by the customer during the order or booking of the particular vehicle.
Invoice: A bill which is given to the customer when they buy the vehicle.
Tax: Amount of money imposed by the government to the organization on particular vehicle as Business Sale Tax (BST). It will be calculated on the actual rate/cost price of the vehicle and not the selling price.

Date: System date
Time: system time
Database Structure
Login Table
Field name Datatype Size Description Constraint
Uid Varchar 50 User name
Pwd Varchar 50 User password

Customer table
Field name Datatype Size Description Constraint
COF Int 30 Customer Order Form Primary key
Date Datetime 8 Date of order of the vehicle
Name Varchar 30 Name of customer
Vehicle(model) Varchar 10 Name of vehicle
Proposed
delivery date Datetime 30 Likely delivery date of the vehicle
Col 1st choice Varchar 30 1st colour choice
Col 2nd choice Varchar 30 2nd colour choice
Booking amt paid Int 30 Advance amount paid
Balance Int 30 Balance amount after advance payment
Add.office Varchar 30 Office address of customer
Ad.residence Varchar 30 Residence address of customer
Phone no Int 30 Phone number of customer

Supplier Table
Field name Datatype Size Description Constraint
name Varchar 30 Name of supplier
Supplier_id Varchar 30 Supplier code Primary key
Email id Varchar 15 Email id of supplier
Contact no Int 10 Contact number of supplier
address Varchar 15 Address of supplier

Purchase Table
Field name Datatype Size Description Constraint
Supplier_id Varchar 30 Supplier code Foreign key
Vehicle model Varchar 10 Name of vehicle
Eng no Varchar 15 Engine number of the vehicle Primary key
Key no Int 30 Vehicleâ„¢s key number
Colour Varchar 30 Colour of the vehicle
Mfg year Varchar 30 Manufactured year of vehicle
Cubic capacity Int 30 Cubic capacity of the vehicle
Seat capacity Int 3o No.of seats available in the vehicle
Tax Int 30 Tax imposed on particular vehicle
Quantity Int 30 Number of vehicle purchased
Rate Int 30 Price of each vehicle
Amt Int 3o Rate*quantity

Sale Table
Field name Datatype Size Description Constraint
COF Varchar 30 Customer order Form Foreign key
Eng.no Varchar 15 Engine number of the vehicle Foreign key
Delivery date Datetime 30 Date on which the vehicle is delivered

Invoice table
Field name Datatype Size Description Constraint
Date Datetime 30 Date of invoice
Invoice_id Varchar 10 Invoice no. of sale made to customer Primary key
COF Varchar 30 Customer Order Form Foreign key
Eng no varchar 15 Engine number of the vehicle Foreign key
Invoice_total Varchar 10 Total amount of bill



Testing
Unit Test Procedures
Testing is an important activity in the software quality initiative. There are different types of testing, strategies of testing and the process involved in carrying out the tests. Among several types and methods of testing I have chosen Unit Testing to implement in my project (software).Unit testing is normally considered as an adjunct to the coding step. The design of the unit tests can be performed before coding begins or after source code has been generated. Each test case should be coupled with a set of expected results. Unit testing focuses verification effort on the smallest unit of software design, the software component or module. Using the component-level design description as a guide, important control paths are tested to uncover errors within the boundary of the module.
¢ Check the structures part of the code within a module or a code segment.
¢ Test the functionality of the code within a module by debugging each module and giving various inputs.