Car Dealership Information System

Car Dealership Information System
A PROJECT REPORT
Submitted by
Nitin Satija. 11514201709 Swati Singhal.. 10114201709 Rishab Kumar..10321401709 Deepak Sewal07121401709
In partial fulfillment for the award of the degree Of
BACHELOR OF BUSINESS ADMINISTRATION
JAGANNATH INTERNATIONAL MANAGEMENT SCHOOL VASANT KUNJ, NEW DELHI

2011

CERTIFICATE FOR PROJECT
This is to certify that this is a bonafide record of the project work done satisfactorily at Jagannath International Management School by the following students in the partial fulfillment of BBA V Semester -
Nitin Satija Swati Singhal Rishab Kumar Deepak Sewal
This report or similar report on the topic has not been submitted for any other examination and doesnt form a part of any other course undergone by the candidates.
Date: Place:
Project Guide Ms.Poonam Malik
Jagannath International Management School (Affiliated to GGS Indraprastha University, Delhi) Vasant Kunj, New Delhi

ACKNOWLEDGMENT
I would like to thank Mrs. Poonam Malik for introducing us to the field of Information Management and for her professional guidance and direction during the entire length of our project at the JIMS VK (GGSIPU). I would also like to thank my Project advisor Mrs. Poonam Malik for his guidance, support and patience. Their experience and expert knowledge inspired us to reach beyond our previous limits and capabilities.
Last but not the least; we would like to thank all those people who directly or indirectly contributed for helping us in the successful completion of the project.
Thank you
Nitin Satija Swati Singhal Rishab Kumar Deepak Sewal

TABLE OF CONTENTS
Chapter 1 Introduction 1.1Objective 1.2 Need for the system 1.3 Characteristics of proposed system 1.4 Scope of the project 1.5 Advantages of proposed system 6 7 8 9 10
Chapter 2 System Requirements 2.1 Hardware Requirements 2.2 Software Requirements 11 12
Chapter 3 System Specification 3.1 Security 3.2 Maintainability 3.3 Portability 3.4 Feasibility 16 16 16 16
Chapter 4 System Design 4.1 System Design 4.2 Design Principle 4.3 Design Concepts 4.4 Project Execution Model 4.5 Data flow diagram 18 19 20 21 22
Chapter 5 Implementation and Coding
32
Chapter 6 Software Testing 6.1 Objectives of testing 6.2 Testing Principles 6.3 Verification and Validation 6.4 Types of Testing 6.5 Testing procedure 57 58 58 58 59
Chapter 7 Utilities in the system
61
Chapter 8 Conclusion
64
Bibliography
66
INTRODUCTION
This project, Car Dealership Information System, is a Management Information System or MIS. A dealership management system (DMS) is a bundled management information system created specifically for automotive industry car dealerships or large equipment manufacturers, These systems often contain software that cater to the needs of the finance, sales, parts, inventory and administration components of running the dealership. It has been designed to carry out basic functionality of adding, modifying and deleting records pertaining to a car dealership and its various functions. It has been created using Visual Basic 6.0 as a frontend and Microsoft Access 2000 as a backend for the databases. It works on MS- Access. The references for the MS-Access and Visual Basic are provided with the introduction with the System Development Life Cycle. The coding part has been attached with the output generated.
I have tried to make the system more users friendly and more convenient to handle especially for the non computer professionals.

1.1 Objectives
The main objective of any computerized system is to minimize the manual work performed. As our project reduces the register work or manual work of as all the entry system has been computerized. Objective of our system is to minimize and overcome the limitations of manual work.
This computerized system possesses a good GUI which provides an ease of support to the administrators and to perform their task in a very efficient manner and this work is also effective in nature. This system is also capable of generating error free reports that describes all records and custom reports can also be generated. The handling of this project is also very simple so that anyone can understand it easily. And this system is also very beneficial from the security point of view. It helps in 1. Successfully introduce automation to the enterprise 2. Provide functionality to add, edit and delete records 3. Increase efficiency of the business
1.2 Need of the system

In todays fast changing world of technology every organization is in want of fully utilization of time and space in order to be counted in the lists of worlds highest-ranking organizations.
In order to this each organization is making itself fully computerized. Computerization also helps organization to minimize paper work as well as manpower.

There are several attributes in which the computer based information works. Broadly the working of Computer system is divided into two main groups. Transaction System Decision support system
Transaction System: A transaction is a record of some well-defined single and usually small
occurrence in a system. Transactions are input into the computer to update the database files. It checks the entering data for its accuracy. This means that numeric data appears in numeric field and character data in character field. Once all the checks are made, transaction is used to update the database. Transaction can be inputted in on-line mode or batch mode. In on-line mode, transactions are entered and updated into the database almost instantaneously. In batch mode, transactions are collected into batches which may be held for a while and inputted later.
Decision Support System: It assists the user to make analytical decision. It shows the various
data in organized way called analysis. This analysis can be made to help in making decisions. User can store information as per requirement, which can be used for comparison with other reports.
A Car Dealership or vehicle local distribution is a business that sells new cars and/or used cars at the retail level, based on a dealership contract with an automaker or its sales subsidiary. It employs Automobile Salespeople to do the selling. It may also provide Maintenance Services for cars, thus employing automobile mechanics, stock and sell spare automobile parts, and process warranty claims. Such a business has to figure in various factors to function and thus encounters a large amount of data pertaining to everything from models and prices to features and specifications. To keep an account of such large chunks of information manually is a difficult task and there is a risk of information loss, redundancy, and misuse. This is why there is a requirement for a Car Dealership Information System, which seeks to reduce or remove all the aforementioned problems and increase the efficiency of the business by introducing automation.

1.3 Characteristics of proposed system
The manual dealing of preparing reports is a very tedious job, as administrator first needs to search for applications from the files and then presenting those in the form of reports. Thus we need to automate this process to systemize and fasten up the overall system, as through computerization enormous data will become easily accessible. The system should be distributive in nature; it should be designed to provide functionalities as explained below: Database can be accessed by the Administrator.
Maintains the member information and leave applications. Administrator can take the backups and generate reports of any or all the databases.
1.4 Scope of the work

As in todays world there is nothing perfect, so there is always a chance of scope in every aspect of project. At this point of time our project is a standalone application whereas it can be converted into a fully automated system, reducing the paperwork to close to zero. Also in this the administrator has to enter the unique ID of a member into the forms of Visual Basic which consumes time.
We can improve this project further by using web services and fully automating it where-in applications can be submitted online and receive the corresponding response by e-mail. The data can be stored centrally at the server terminal.
The system covers 7 basic focus areas of a car dealership, viz. 1. General Information

2. Engine Specifications 3. Dimensions 4. Technical Information 5. Financials 6. Features 7. Accessories
1.5 Advantages of proposed system

With the feature of Login ID and password , data becomes more secure , as only the person who has the password and login id can view or modify records , rest no one can enter the system without password. It provides a better and faster way of managing and maintaining various transactions of the members Time wastage is minimal, as all records and reports are just a click away.
This system is an efficient, secure, tidy and fast way to manage so many
records.

Methodology
The data used in this project Report are collected from both Primary and secondary sources. The strategy behind the data collection process in this research project has been collecting, studying, analyzing and putting data in both logical/chronological orders. The books, Internet, analysis of existing Car Parking Systems, and other resources were of great help in completing and giving this project a final touch. The Faculties in the IT department of our institute contributed a lot towards the project. They gave me an in-depth knowledge of various aspects of an IT application database project.

Chapter 2
SYSTEM REQUIREMENTS
2.1 Hardware requirements
2 GB Hard Disk(minimum requirement) 512 MB RAM Supports for printer (Dot Matrix / Inkjet / Laser printer)that is, appropriate drivers are installed and printer connected. Printer will be required for printing of issues. Standalone system or network based system- not a concern, as it will be possible to run the application on any of these. Processor- Pentium 166MHz or above Monitor with appropriate resolution and color quality for proper and complete viewing of screens.
2.2 Software requirements

Any windows-based operating system (Windows-98/2000/XP/NT) Visual Basic 6.0 for coding/developing the software MS Access- for database
PLATFORMS VISUAL BASIC AS VISUAL PROGRAMMING LANGUAGE VISUAL BASIC follows an event driven programming approach. The user interface is designed first with all the required controls placed on the user interface form. Customizing their properties modifies these controls. After the user interface is designed the events that occur in the application are decided and are relating to their respective controls. Every control is associated with its respective events to be trapped.
VISUAL BASIC APPLICATION DEVELOPMENT The figure shows the steps that all visual basic developers follow as they prepare projects: Design and build user interface
Write event driven code Create and call other procedures
Test and debug
Prepared distribution file

The prototypical visual basic development cycle The steps mentioned above arent symmetrical. Some steps take longer than other do and there is repetition of several steps as the initial application is design is refined and enhanced. Most of the development time is spent in the first four steps. Even the most complex visual basic projects follow the steps described above. Most of time is spent in building the user interface and writing the code required by the application.
UNDERSTANDING THE ADVANTAGES OF VISUAL BASIC Lets take a minute to review some of the features that make visual basic such a robust and exciting development platform. The following key points make visual basic an excellent development tool: -
1 Visual Basic Application Are Event Driven - Event driven means the user is in control of the application. The user generates a stream of events each time he clicks with mouse or presses a key on the keyboard. Your visual basic application respond to those event a through the codes written and attached to those events.
2 Visual Basic Supports The Principals Of Object Oriented Design - This
means that
you can comport mentalist different aspects of your application as object and develop and test those objects independently of the rest of the application.

3 Microsoft Has Designed Visual Basic To Be A Complete Window Development System - This means that your visual basic application will look and behave like other windows program user might work with.
4 Visual Basic Is Infinitely Extensible through The Use Of Active X, Controls, Dynamic Link libraries (DLLS) And Add MS-ACCESS 07
Microsoft (MS) Access is relational database management system (RDBMS) used to stored and manipulate large collection of information of any kind. Here RDBMS refers to the organization of data in a series of rows and columns in such a manner that any specific piece of information is available with the click of a mouse and a few keystrokes. MSAccess has tools, which are easy to used and provide powerful development environment, making it an appropriate choice for novices as well as professional.
There are different ways in which an application with multiple components that includes, Access can be integrated. A component (in Microsoft terminology) is an application or development tool that makes it objects available to other applications. Using automation in Visual Basic it is possible to work with objects from other components to construct a seamless integrated application. Using the Object Linking and Embedding (OLE) technology, a user can include documents created in another component on a report or form within Access. Automation and OLE are distinct technologies, which are a part of the Component Object Model (COM), a standard proposed by Microsoft.

Microsoft Access is used as backend because: -
1.
It is easy to use.
2.
It can be integrated / connected easily with a Visual Basic.
3.
No programming skills required to work with.
4.
The database access time is better than other database Software. Access uses structured query language (SQL), which is English like language, and makes interaction between user and the database very simple. It helps in easy creation, manipulation and modification of the database.
5.

Chapter 3
SYSTEM SPECIFICATIONS
3.1 Security The application will be password protected. The user (administrator) will have to enter the correct username and password in order to access the application.
3.2 Maintainability The application will be designed in maintainable manner. It will be easy to incorporate new requirements in the individual modules.
3.3 Portability
The application is easily portable on any Windows-based system.
3.4 Feasibility
The economical and technical factors are considered to be feasibility study of the system. ECONOMICAL FEASIBILITY 1. No manpower cost is incurred in this proposed system as the system has been developed as project work. 2. The system has been developed in an environment where no hardware & software facilities have to be installed for the purpose of development. 3. The cost entailed in this respect was nil.

TECHNICAL FEASIBILITY 1. The existing hardware & software facilities are sufficient for development of this proposed system. However at the beginning of the project, the P-II 400MHz machine was enough for the work. Soon we realized that machine is little bit slower for some complicated data retrieval & it will keep the user unnecessary waiting for the result to pop-up on the screen. 2. So the project was relocated to P-IV machine. Thus no additional costs are incurred during the development of the project.
OPERATIONAL FEASIBILITY Here we consider the extent to which the proposed system will fulfill any administrators requirement. That is whether the proposed system covers all aspects of the working system or it has considerable improvements.
BEHAVIORAL FEASIBILITY A disputation of any kind of change in existing system may be appeared by users. But in the Car dealership information System there may be less chance of having any opposing views because this software is easy to operate and increases the efficiency in user operation. Because of its simplicity, any user can easily be trained to use the software.

Chapter 4
SYSTEM DESIGN
4.1 System design
Design is a meaningful engineering representation of something to be built. Software design is the first of three technical activities- designs, code generation and tests- that are required to build and verify the software. Design focuses on the four major areas of concern- data, architecture, interfaces and components. The Data design transforms the information domain model created during analysis into the data structures that will be required to implement the software. The data objects and relationships defined in the ERD provide the basis for the data design activity. The Architectural design defines the relationship between major structural elements of the software, the "design patterns" that can be used to achieve the requirements that have been defined for the system. The architectural design representation i.e. the framework of a computer based system can be derived from the system specification, the analysis model and the interaction of subsystems defined within the analysis model. The Interface design describes how the software communicates with itself, with systems that interoperate with it. An interface implies a flow of information and a specific type of behavior. Therefore, data and DFDs provide much of the information required for interface design. The Component-level design transforms structural elements of the software architecture into a procedural description of software components. The importance of software design can be stated with a single word- Quality. Design is the only way that we can accurately translate a customer's requirements into a finished software product or system.

4.2 Design principles
Software design is both a process and a model. The design process is a sequence of steps that enable the designer to describe all aspects of software to be built. The design model is the equivalent of an architect's plans for a house. The design process should not suffer from "tunnel vision"- a good designer should consider alternative approaches, judging each based in the requirements of the problem. The design should be traceable to the analysis model- it is necessary to have a means for tracking how requirements have been satisfied by the design model. The design should exhibit uniformity and integration- rules of styles and format should be defined for a design team before design work begins. A design is integrated if care is taken in interfaces between design components. The design should be structured to accommodate change The design should be structured to degrade gently, even when aberrant data, events or operating conditions are encountered- it should be designed to accommodate unusual circumstances. Design is not coding, coding is not design- when detailed procedural designs are created for program components, the level of abstraction of the design model is higher than source code. The only design code level address the small implementation details that enable the procedural design to be coded.
The design should be reviewed to minimize conceptual (semantic) errors- a design

team should ensure that major conceptual elements of the design have been addressed before worrying about the syntax of the design model.

4.3 Design concepts
The beginning of wisdom is to recognize the difference between getting a program to work, and getting it right. Fundamental software design concepts provide the necessary framework for getting it right. ABSTRACTION When we consider a modular solution to any problem, many level of abstraction can be posed. At the highest level of abstraction, a solution is stated in broad terms using the language of the problem environment. At lower level of abstraction, a more procedural orientation is taken. Finally, at lowest level of abstraction, the solution is stated in a manner that can be directly implemented. REFINEMENT Refinement is a process of elaboration. Refinement causes the designer to elaborate on the original statement, providing more and more detail as each successive refinement occurs. It helps the designer to reveal low-level details as design
progresses. It aids the designer in creating a complete design model as the design evolves. MODULARITY Software is divided into separately named and addressable components, often called modules that are integrated to satisfy problem requirements.

4.4 Project execution model
In this, we are developing an application phase developing process to manage the complexity, better project tracking, and quality to achieve consistency, software process is divided into set of phase, quality and progress checks are made without waiting till the development is completed. We have selected the waterfall model in the present application because this model is suitable to automate the existing manual system for which all requirements are known before the design starts. Requirement analysis & specification Design Implementation & unit testing Integration & system testing
Operation & maintenance
DATA FLOW DIAGRAM

INPUT USERNAME AND PASSWORD
SEARCH, ADDITION, DELETION AND MODIFICATION OF EMPLOYEE DATA/RECORDS
OUTPUT
Symbols used for E-R diagram.

Symbol Meaning
ENTITY
WEAK ENTITY
RELATIONSHIP
IDENTIFYING RELATIONSHIP
ATTRIBUTE
KEY ATTRIBUTE
MULTIVALUED
COMPOSITE ATTRIBUTE

ENTITY RELATIONSHIP DIAGRAMS
General Information
COMPANY
ID NUMBER
GENERAL INFORMATION
MODEL
COLOR MAKE YEAR BODYTYPE

Engine Specifications
ID NUMBER CAPACITY NO. OF CYLINDERS
ENGINE SPECIFICATIONS
TYPE NO. OF VALVES
EMISSION STD. MAX. TORQUE MAX. POWER

Dimensions
ID NUMBER BOOTSPACE TURNING RADIUS WHEELBASE
REAR TRACK
DIMENSIONS
LENGTH
WIDTH HEIGHT FRONT TRACK GROUND CLEARANCE

Technical Information
SEATING CAPACITY
ID NUMBER
TECHNICAL INFORMATION
MODEL
FUEL TANK CAPACITY NO. OF DOORS
TRANSMISSION NO. OF GEARS

Financials
ID NUMBER
INSURANCE
FINANCIALS
LOAN WARRANTY
PRICE

Features
BODY COLORED BUMPERS
ID NUMBER A.B.S.
AIRBAGS
FEATURES
E.P.S.
ALLOY WHEELS
CENTRAL LOCKING

Accessories
ID NUMBER
G.P.S.
SPECIAL PAINT
ACCESSORIES
STEREO
E.S.P.
GEAR LOCKS

PRICE ID NUMBER G.P.S. WARRANTY
FINANCIALS
SPECIAL PAINT
INSURANCE
ACCESSORIES
STEREO LOAN ID_NUMBER
E.S.P.
GEAR LOCKS
ID_NUMBER MAKE YEAR COMPANY
GENERAL INFORMATION
MODEL BODYTYPE COLOR LENGTH ID_NUMBER
FRONT TRACK
BOOT SPACE
HAS
ID_ NUMBER
HEIGHT
DIMENSIONS
TURNING RADIUS
WIDTH WHEEL BASE GROUND CLEARANCE

AIR BAGS
REAR TRACK
TYPE POWER
ENGINE_SPECIFICATION S
CAPACITY
TORQUE DOORS
A.B.S. VALVES EMISSION CENTRAL LOCKING
FEATURES
E.P.S.
ID_ NUMBER
BUMPERS ID_NUMBER
ALLOY_WHEELSS S
TECHNICAL INFORMATION
MODEL
DOORS GEARS
TRANSMISSION
SEATING CAPACITY
FUEL TANK CAPACITY

Chapter 5
Form Design and Coding

The proposed system is an application developed in Visual Basic 6.0, making it an event driven or menu driven system. Visual basic is an object based programming language. The programming does not execute itself in any predetermined sequence but different lines of code in response to events. Visual Basic specifically follows procedural approach of coding wherein the problem is decomposed into independent procedures or modules (coded and tested), which are later combined and finally a system is ready to be executed. It allows us to adopt a parallel approach, with independent sections of code for each option that the user might select.
Coding for the proposed system was not a very tedious task since forms were distributed amongst the team of developers, who individually coded their parts, tested them and then combined them to form car dealership information system.

FORMS AND CODING Home
Coding
Private Sub Command1_Click () Form2gi.Show End Sub Private Sub Command2_Click() Form3ENG.Show End Sub Private Sub Command3_Click()

Form4DIM.Show End Sub Private Sub Command4_Click() Form5TEC.Show End Sub Private Sub Command5_Click() Form6FIN.Show End Sub Private Sub Command6_Click() Form7FEAT.Show End Sub Private Sub Command7_Click() Form8ACC.Show End Sub

General Information
Coding
Private Sub cmdfirst_Click() Adodc1.Recordset.MoveFirst End Sub Private Sub cmdlast_Click() Adodc1.Recordset.MoveLast End Sub Private Sub cmdnext_Click() If Adodc1.Recordset.EOF = True Then Adodc1.Recordset.MoveFirst End If Adodc1.Recordset.MoveNext End Sub Private Sub cmdprevious_Click()

If Adodc1.Recordset.BOF = True Then Adodc1.Recordset.MoveLast End If Adodc1.Recordset.MovePrevious End Sub Private Sub Command1_Click() Adodc1.Recordset.AddNew End Sub Private Sub Command2_Click() If MsgBox("Save this record?", vbYesNo, "Save") = vbYes Then Adodc1.Recordset.Update Else Adodc1.Recordset.CancelUpdate End If End Sub Private Sub Command3_Click() If MsgBox("Are you sure?", vbYesNo, "Delete") = vbYes Then Adodc1.Recordset.Delete Adodc1.Recordset.MoveNext If Adodc1.Recordset.EOF Then Adodc1.Recordset.MoveLast End If End If End Sub Private Sub Command4_Click() Dim a As Variant a = InputBox("Please Enter Password") If a = "suparn" Then Frame1.Visible = True Command5.Visible = True Text1.Locked = False Text2.Locked = False Text3.Locked = False Text4.Locked = False Text5.Locked = False Text6.Locked = False Else MsgBox "You do not have authorization to edit.", vbCritical End If End Sub

Private Sub Command5_Click () Frame1.Visible = False Command5.Visible = False Text1.Locked = True Text2.Locked = True Text3.Locked = True Text4.Locked = True Text5.Locked = True Text6.Locked = True End Sub

Engine Specifications
Coding
Private Sub cmdfirst_Click() Adodc1.Recordset.MoveFirst End Sub Private Sub cmdlast_Click() Adodc1.Recordset.MoveLast End Sub Private Sub cmdnext_Click() If Adodc1.Recordset.EOF = True Then Adodc1.Recordset.MoveFirst End If

Adodc1.Recordset.MoveNext End Sub Private Sub cmdprevious_Click() If Adodc1.Recordset.BOF = True Then Adodc1.Recordset.MoveLast End If Adodc1.Recordset.MovePrevious End Sub Private Sub Command1_Click() Adodc1.Recordset.AddNew End Sub Private Sub Command2_Click() If MsgBox("Save this record?", vbYesNo, "Save") = vbYes Then Adodc1.Recordset.Update Else Adodc1.Recordset.CancelUpdate End If End Sub Private Sub Command3_Click() If MsgBox("Are you sure?", vbYesNo, "Delete") = vbYes Then Adodc1.Recordset.Delete If Adodc1.Recordset.EOF Then Adodc1.Recordset.MoveLast End If End If End Sub
Private Sub Command4_Click() Dim a As Variant a = InputBox("Please Enter Password") If a = "suparn" Then Frame1.Visible = True Command5.Visible = True Text1.Locked = False Text2.Locked = False Text3.Locked = False Text4.Locked = False Text5.Locked = False Text6.Locked = False Text7.Locked = False Text8.Locked = False

Else MsgBox "You do not have authorization to edit.", vbCritical End If End Sub
Private Sub Command5_Click() Frame1.Visible = False Command5.Visible = False Text1.Locked = True Text2.Locked = True Text3.Locked = True Text4.Locked = True Text5.Locked = True Text6.Locked = True Text7.Locked = True Text8.Locked = True End Sub

Dimensions
Coding
Private Sub cmdfirst_Click() Adodc1.Recordset.MoveFirst End Sub Private Sub cmdlast_Click() Adodc1.Recordset.MoveLast End Sub Private Sub cmdnext_Click() If Adodc1.Recordset.EOF = True Then Adodc1.Recordset.MoveFirst

End If Adodc1.Recordset.MoveNext End Sub Private Sub cmdprevious_Click() If Adodc1.Recordset.BOF = True Then Adodc1.Recordset.MoveLast End If Adodc1.Recordset.MovePrevious End Sub Private Sub Command1_Click() Adodc1.Recordset.AddNew End Sub Private Sub Command2_Click() If MsgBox("Save this record?", vbYesNo, "Save") = vbYes Then Adodc1.Recordset.Update Else Adodc1.Recordset.CancelUpdate End If End Sub Private Sub Command3_Click() If MsgBox("Are you sure?", vbYesNo, "Delete") = vbYes Then Adodc1.Recordset.Delete If Adodc1.Recordset.EOF Then Adodc1.Recordset.MoveLast End If End If End Sub
Private Sub Command4_Click() Dim a As Variant a = InputBox("Please Enter Password") If a = "suparn" Then Frame1.Visible = True Command5.Visible = True Text1.Locked = False Text2.Locked = False Text3.Locked = False Text4.Locked = False Text5.Locked = False Text6.Locked = False Text7.Locked = False

Text8.Locked = False Else MsgBox "You do not have authorization to edit.", vbCritical End If End Sub
Private Sub Command5_Click() Frame1.Visible = False Command5.Visible = False Text1.Locked = True Text2.Locked = True Text3.Locked = True Text4.Locked = True Text5.Locked = True Text6.Locked = True Text7.Locked = True Text8.Locked = True End Sub

Technical Information
Coding
Private Sub cmdfirst_Click() Adodc1.Recordset.MoveFirst End Sub Private Sub cmdlast_Click() Adodc1.Recordset.MoveLast End Sub Private Sub cmdnext_Click() If Adodc1.Recordset.EOF = True Then

Adodc1.Recordset.MoveFirst End If Adodc1.Recordset.MoveNext End Sub Private Sub cmdprevious_Click() If Adodc1.Recordset.BOF = True Then Adodc1.Recordset.MoveLast End If Adodc1.Recordset.MovePrevious End Sub Private Sub Command1_Click() Adodc1.Recordset.AddNew End Sub Private Sub Command2_Click() If MsgBox("Save this record?", vbYesNo, "Save") = vbYes Then Adodc1.Recordset.Update Else Adodc1.Recordset.CancelUpdate End If End Sub Private Sub Command3_Click() If MsgBox("Are you sure?", vbYesNo, "Delete") = vbYes Then Adodc1.Recordset.Delete If Adodc1.Recordset.EOF Then Adodc1.Recordset.MoveLast End If End If End Sub
Private Sub Command4_Click() Dim a As Variant a = InputBox("Please Enter Password") If a = "suparn" Then Frame1.Visible = True Command5.Visible = True Text1.Locked = False Text2.Locked = False Text3.Locked = False Text4.Locked = False Text5.Locked = False Text6.Locked = False

Else MsgBox "You do not have authorization to edit.", vbCritical End If End Sub
Private Sub Command5_Click() Frame1.Visible = False Command5.Visible = False Text1.Locked = True Text2.Locked = True Text3.Locked = True Text4.Locked = True Text5.Locked = True Text6.Locked = True End Sub

Financials
Coding

Adodc1.Recordset.MoveNext End Sub Private Sub cmdprevious_Click() If Adodc1.Recordset.BOF = True Then Adodc1.Recordset.MoveLast End If Adodc1.Recordset.MovePrevious End Sub
Private Sub Command1_Click() Adodc1.Recordset.AddNew End Sub Private Sub Command2_Click() If MsgBox("Save this record?", vbYesNo, "Save") = vbYes Then Adodc1.Recordset.Update Else Adodc1.Recordset.CancelUpdate End If End Sub Private Sub Command3_Click() If MsgBox("Are you sure?", vbYesNo, "Delete") = vbYes Then Adodc1.Recordset.Delete If Adodc1.Recordset.EOF Then Adodc1.Recordset.MoveLast End If End If End Sub Private Sub Command4_Click() Dim a As Variant a = InputBox("Please Enter Password") If a = "suparn" Then Frame1.Visible = True Command5.Visible = True Text1.Locked = False Text2.Locked = False Text3.Locked = False Text4.Locked = False Text5.Locked = False Else MsgBox "You do not have authorization to edit.", vbCritical

End If End Sub
Private Sub Command5_Click() Frame1.Visible = False Command5.Visible = False Text1.Locked = True Text2.Locked = True Text3.Locked = True Text4.Locked = True Text5.Locked = True End Sub

Features
Coding

Adodc1.Recordset.MoveNext End Sub Private Sub cmdprevious_Click() If Adodc1.Recordset.BOF = True Then Adodc1.Recordset.MoveLast End If Adodc1.Recordset.MovePrevious End Sub Private Sub Command1_Click() Adodc1.Recordset.AddNew End Sub Private Sub Command2_Click() If MsgBox("Save this record?", vbYesNo, "Save") = vbYes Then Adodc1.Recordset.Update Else Adodc1.Recordset.CancelUpdate End If End Sub Private Sub Command3_Click() If MsgBox("Are you sure?", vbYesNo, "Delete") = vbYes Then Adodc1.Recordset.Delete If Adodc1.Recordset.EOF Then Adodc1.Recordset.MoveLast End If End If End Sub
Private Sub Command4_Click() Dim a As Variant a = InputBox("Please Enter Password") If a = "suparn" Then Frame1.Visible = True Command5.Visible = True Text1.Locked = False Text2.Locked = False Text3.Locked = False Text4.Locked = False Text5.Locked = False Text6.Locked = False Text7.Locked = False Else

MsgBox "You do not have authorization to edit.", vbCritical End If End Sub
Private Sub Command5_Click() Frame1.Visible = False Command5.Visible = False Text1.Locked = True Text2.Locked = True Text3.Locked = True Text4.Locked = True Text5.Locked = True Text6.Locked = True Text7.Locked = True End Sub

Accessories
Coding

Adodc1.Recordset.MoveNext End Sub Private Sub cmdprevious_Click() If Adodc1.Recordset.BOF = True Then Adodc1.Recordset.MoveLast End If Adodc1.Recordset.MovePrevious End Sub Private Sub Command1_Click() Adodc1.Recordset.AddNew End Sub Private Sub Command2_Click() If MsgBox("Save this record?", vbYesNo, "Save") = vbYes Then Adodc1.Recordset.Update Else Adodc1.Recordset.CancelUpdate End If End Sub Private Sub Command3_Click() If MsgBox("Are you sure?", vbYesNo, "Delete") = vbYes Then Adodc1.Recordset.Delete If Adodc1.Recordset.EOF Then Adodc1.Recordset.MoveLast End If End If End Sub Private Sub Command4_Click() Dim a As Variant a = InputBox("Please Enter Password") If a = "suparn" Then Frame1.Visible = True Command5.Visible = True Text1.Locked = False Text2.Locked = False Text3.Locked = False Text4.Locked = False Text5.Locked = False Text6.Locked = False Else MsgBox "You do not have authorization to edit.", vbCritical End If End Sub

Private Sub Command5_Click() Frame1.Visible = False Command5.Visible = False Text1.Locked = True Text2.Locked = True Text3.Locked = True Text4.Locked = True Text5.Locked = True Text6.Locked = True End Sub

Chapter 6
TESTING
Software testing is the process used to measure the quality of developed software product. Effective software testing will contribute to the delivery of higher quality software products, more satisfied users, lower maintenance costs, more accurate, and reliable results. Usually, quality is constrained to such topics as correctness, completeness, security, but can also include more technical requirements as described under the ISO standard ISO 9126, such as capability, reliability, efficiency, portability, maintainability, compatibility, and usability. Testing is a process of technical investigation, performed on behalf of stakeholders, that is intended to reveal quality-related information about the product with respect to the context in which it is intended to operate. This includes, but is not limited to, the process of executing a program or application with the intent of finding errors. Hence software testing is necessary and important activity of software development process. It is a very expensive process and consumes one-third to one-half of the cost of a typical development project. It is partly intuitive but largely systematic. Good testing involves much more than just running the program a few times to see whether it works. Thorough analysis of a program helps us to test more systematically and more effectively.
6.1 Objectives of testing

Testing is a process of executing a program with the intent of finding an error. A good test case is one that has a high probability of finding as yet undiscovered error. A successful test is one that uncovers an as-yet-undiscovered error

6.2 Testing Principles
All tests should be traceable to customer requirements. Tests should be planned long before testing begins. Testing should begin in the small and progress toward testing testing in large. Exhaustive testing is not possible. To be most effective, testing should be conducted by an independent third party.
6.3 Verification and validation

Software testing is used in association with verification and validation (V&V). Verification is the checking of or testing of items, including software, for conformance and consistency with an associated specification. Software testing is just one kind of verification, which also uses techniques such as reviews, inspections, and walkthroughs. Validation is the process of checking what has been specified is what the user actually wanted.
6.4 Types of testing

Unit Testing- In unit testing, different modules are tested against the specification produced during design for the modules. The main goal of unit testing is to test the internal logic of the modules. A module is considered for integration and used by others only after it has been unit tested satisfactorily. Integration Testing- The main emphasis is on testing interfaces between modules. System Testing- In system testing, the entire software is tested. The reference document for this process is the requirements document and the goal is to see if software meets its requirements. This is essentially a validation exercise.

Acceptance Testing- Acceptance testing involves planning and execution of the functional tests, performance tests and stress tests in order to demonstrate that whether the implemented system satisfies its requirements or not. Stress Testing- Applying stress to a plan means that a large amount of data is fed in for processing in a short period of time. In other words, consumption of computer resources is drastically raised in that time frame with the intention to ensure that the system will still perform effectively if the same condition occurs in the future.
6.5 Testing Procedure

Different types of checks like duplicate checks; completeness check, validity check, etc. are incorporated in this system. The user is not familiar with the new system, the data entry screens are designed in such a way that they are Consistent Compatible Easy to use Has quick response Conventions for the System to be User Friendly All items that are logically related must be placed together. Whenever possible, list of values must be provided to display all valid options to the user. Errors and validation messages must be provided whenever required.

Test Review Test Review is the process, which ensures that testing is carried out as planned.

Chapter 7 Utilities in the system
General utilities in the system are as follows: Calculator Calendar Notepad Web search page
MAINTENANCE
Maintenance is the enigma of system development. It holds the software industry captive, trying up programming resources. Analysts and programmers spent far more time in maintaining then they go writing them. Maintenance accounts for 50-80 percent of the total system development. This problem occurs across all the industries largely because software is hand made; product design is an adhoc fashion with few standards. It comes out of late, is poorly documented and therefore it is difficult to maintain. There are other problems as well.
Few Tools And Techniques Are Available For The Maintenance. They Are: -
1. It is a good test plan 2. Standards, procedures and guidelines defined and enforced. 3. Programs are often maintained care for structure and documentation. 4. There is minimal standard for maintenance. 5. Programmers expect that they will not be in current commitment by the time their programs go into maintenance.

MAINTENANCE AND ENHANCMENT
Maintenance means restoring something to its original condition. Unlike hardware, software does not wear out, as it can be corrected. Maintenance can be classified into three different parts. They are:1. 2. 3. Corrective maintenance Adaptive maintenance Perfective maintenance
Corrective Maintenance: - Corrective maintenance means repairing, processing or performance

failures or making changes because of the previously uncorrected problems or false assumptions.
Adaptive Maintenance:- Adaptive maintenance means changing the problem function in the
system.
Perfective Maintenance:- means enhancing the performance or modifying the programs to

respond the users additional or changing needs. Of these types, more time and money are spent on the perfective and adaptive maintenance together. Maintenance covers a wide range of activities, including correcting coding errors, updating documentation and test data, and upgrading user support. Many activities classified as maintenance are actually enhancement.

REDUCING MANAGEMENT COST
Maintenance Management Audit
By the help of interviews and questionnaires the quality of the maintenance is evaluated. Some of the frequently asked questions are as follows: 1. Is the maintenance requests are logged in a maintenance request log? 2. What percent of total hours worked are spent in the error corrections, additions, changes, deletion and improvement? 3. Does your organization currently have a well defined maintenance reduction program? The data gathered are used to develop a diagrammatic study to provide the management with the assessment of the software maintenance function.
Software System Audit Which Entails

An overall view of the system documentation and an assessment of the quality of the data files and databases and the system maintainability, reliability and efficiency 1. Functional information gathered on all the programs in the system to determine how well they do the job. Each program is assigned a preliminary ranking value. 2. A detailed program audit, which considers the ranking value, Mean Time between Failure (MTBF), and the size of the maintenance backlog. MTBF determines the system availability to the users
Software Modification
A software modification consists of the following steps: 1. Program rewrites, which includes logic simplification, documentation updates and error correction. 2. System level update, which completes system level documentation, brings up to data flow diagrams or system flow charts, and cross reference programs. 3. Rebuilt of low ranking programs to make sure that the errors have been corrected.

Chapter 8
CONCLUSION
The project Car Dealership Information System has been a rewarding experience in more ways than one.
Firstly, we have gained an insight into the institution. This represents a typical real world situation.
Secondly, in order to generate information from the institution, a number of validations have been performed which has strengthened our understanding of database design.
Initially there were some problems but with the guidance of our project coordinator and project head we were able to solve the problems easily and implement validations.
Finally we can appreciate the power of VB and its file handling ability to make the module interactive and how the code can be reduced by applying procedures. We are now confident of handling such real life situations concerning front end and back end designs.

LIMITATIONS We have made humble effort in preparing the software, so that it can be in the functioning condition. But due to lack of time some conditions cannot be applied.
SCOPE The future enhancement of the software can provide many more other facilities in the different areas as scheme human resources and development section of institute.
FURTHER IMPROVEMENTS The further improvements can be done in project, are list can be generated in different format as according to the requirements, printing of list on printer directly given the commands or by pressing the command button, backup of all the records in the database, searching for a particular record in the database giving the search command.

BIBLIOGRAPHY
Special Edition Using Visual Basic 6 by Brian Siler and Jeff Spotts Mastering Visual Basic 6.0 , E. Petroutsos, BPB Publications, 1998 Microsoft ActiveX Data Object 2.6 Microsoft Data Environment Instance 1.0 Microsoft Data Report Designer 6.0 Visual Basic Run Time Objects And Procedures Visual Basic Objects And Procedures Software Engineering, K. K. Aggarwal & Yogesh Singh, 2nd Ed., New Age International,2005 Software Engineering-A Practitioners Approach R.S. Pressman, 5th Ed., McGraw Hill Int. Ed. 2001 Software Engineering, I. Sommerville, Addison Wesley,2002

Car Dealership Information System

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Car Dealership Information System

Uploaded by

Copyright:

Available Formats

Car Dealership Information System

In partial fulfillment for the award of the degree Of

BACHELOR OF BUSINESS ADMINISTRATION

JAGANNATH INTERNATIONAL MANAGEMENT SCHOOL VASANT KUNJ, NEW DELHI