CAR Showroom Management System ABSTRACT This is a live project which was developed for a local CAR Agent. It is useful to the Agent to maintain the Customers details, Sales Details, Company items and services and also CAR Details. If any customer uy a CAR in loan that persons CAR will recogni!es with the help of CAR no. CAR Recognition System, which will cover the following modules The agent will enter the CAR "o It will help the user to search the CAR details and the re#uired details of the customer .The agent enters the customer details and maintain company details.
Regarding Regarding the registrati registration on module, it contains contains the information information aout newly joined joined $ser details li%e name of the user, password etc. CAR Details module contains the details li%e "ame of the CAR, send from, send to etc. &illing and 'ayment Detail will contain the details li%e Actual Amount to e paid, emi. Searching is having the details of the customer. Any agent will login and search the details of the customer it will show all details li%e customer Details, CAR name, payment type etc. This “CAR projec ectt main mainly ly cont contai ains ns the the CAR CAR “CAR Sh Showr owroo oom m Manage Manageme ment nt Syste System” m” proj information and loan recovering details. The CAR is purchased that CAR amount will e cleared or not. It will clear then its o%. (ther wise the agent will search the details of the customer and recover the loan.
)ardware Re#uirements*+ •
'entium+I -'rocessor.
•
/01 2& Ram
•
03/ 4& Cache 2emory
•
)ard dis% 35 6&
•
2icrosoft Compatile 353 or more 4ey &oard
Software Re#uirements* + 7indows
•
Operating System :
•
Programming language: v."8T
•
Front-End *
isual isual Studio /559
•
a!"-End:
S:; S8R8R
8
In compet competiti itive ve usine usiness ss organi organi!at !ation ion the ailit aility y to effici efficient ently ly align align resour resources ces and usine usiness ss activi activiti ties es with with strate strategic gic ojecti ojectives ves can mean mean the differ differenc encee etwee etween n succee succeedin ding g and just just surviving. To achieve strategic alignment, organi!ation are increasingly managing their activities and processes as projects+in essence, projecting their usiness to monitor performance more closely and ma%e etter usiness decision aove their overall wor% portfolio. &y planning and trac%ing projects with clarity and precession, organi!ations can respond with greater aility to the demands of fast changing usiness environment. 2a%ing strategic goals or
reality re#uires technology that is roust enough to support your core usiness and yet fle
T7AR8? is one of the e
'roposed System
The e
I"'$T D8SI6" Input design is the process of converting user+oriented input to a c omputer ased format. Input design is a part of overall system design, which re#uires very careful attention .(ften the collection of input data is the most e
($T'$T D8SI6" (utputs from computer systems are re#uired primarily to communicate the results of processing to users. They are also used to provide a permanent copy of these result for latter consultation .Computer output is the most important and direct source of information to the
users. Designing computer output should proceed in an organi!ed well through out the manner. The right output must e availale for the people who find the system easy o use. The outputs have een defined during the logical design stage. If not, they should defined at the eginning of the output designing terms of types of output connect, format, response etc,
. LANGAUGE SPECIFICATION
4.1 FEATURES OF VISUAL BASIC. NET
Visual Basic. NET, the latest version of visual basic, includes many new features. The Visual Basic supports interfaces but not implementation inheritance.
Visual basic.net supports implementation inheritance, interfaces and overloading. In addition, Visual Basic .NET supports multithreading concept.
COMMON LANGUAGE SPECIFICATION (CLS)
Visual Basic.NET is also compliant with C! "Common anguage !peci#cation$ and supports structured e%ception handling. C! is set of rules and constructs that are supported by the C& "Common anguage &untime$. C& is the runtime environment provided by the .NET 'ramewor() it manages the e%ecution of the code and also ma(es the development process easier by providing services.
Visual Basic.NET is a C!*compliant language. +ny obects, classes, or components that created in Visual Basic.NET can be used in
any other C!*compliant language. In addition, we can use obects, classes, and components created in other C!*compliant languages in Visual Basic.NET .The use of C! ensures complete interoperability among applications, regardless of the languages used to create the application.
IMPLEMENTATION IN!ERITANCE
Visual Basic.NET supports implementation inheritance. This means that, while creating applications in Visual Basic.NET, we can drive from another class, which is (now as the base class that derived class inherits all the methods and properties of the base class. In the derived class, we can either use the e%isting code of the base class or override the e%isting code. Therefore, with help of the implementation inheritance, code can be reused.
CONSTRUCTORS AN" "ESTRUCTORS
Constructors are used to initiali-e obects, whereas destructors are used to destroy them. In other words, destructors are used to release the resources allocated to the obect. In Visual Basic.NET the sub #nali-e procedure is available. The sub #nali-e procedure is used to complete the tas(s that must be performed when an obect is destroyed. The sub #nali-e procedure is called automatically when an obect is destroyed. In addition, the sub #nali-e procedure can be called only from the class it belongs to or from derived classes.
GARBAGE COLLECTION
arbage Collection is another new feature in Visual Basic.NET. The .NET 'ramewor( monitors allocated resources, such as obects and variables. In addition, the .NET 'ramewor( automatically releases memory for reuse by destroying obects that are no longer in use. In Visual Basic.NET, the garbage collector chec(s for the obects that are not currently in use by applications. /hen the garbage collector comes across an obect that is mar(ed for garbage collection, it releases the memory occupied by the obect.
O#ERLOA"ING
0verloading is another feature in Visual Basic.NET. 0verloading enables us to de#ne multiple procedures with the same name, where each procedure has a di1erent set of arguments. Besides using overloading for procedures, we can use it for constructors and properties in a class.
MULTIT!REA"ING
Visual Basic.NET also supports multithreading. +n application that supports multithreading can handle multiple tas(s simultaneously, we can use multithreading to decrease the time ta(en by an application to respond to user interaction. To decrease the time ta(en by an application to respond to user interaction, we must ensure that a separate thread in the application handles user interaction.
STRUCTURE" E$CEPTION !AN"LING
Visual Basic.NET supports structured handling, which enables us to detect and remove errors at runtime. In Visual Basic.NET, we need to use Try2Catch2'inally statements to create e%ception handlers. 3sing Try2Catch2'inally statements, we can create robust and e1ective e%ception handlers to improve the performance of our application.
THE .NET FRAMEWORK
The .NET 'ramewor( is a new computing platform that simpli#es application development in the highly distributed environment of the Internet.
OB%ECTI#ES OF& NET FRAME'OR
4.To provide a consistent obect*oriented programming environment whether obect codes is stored and e%ecuted locally on Internet* distributed, or e%ecuted remotely.
5.To provide a code*e%ecution environment to minimi-es software deployment and guarantees safe e%ecution of code.
6. Eliminates the performance problems.
There are di1erent types of application, such as /indows*based applications and /eb*based applications.
To ma(e communication on distributed environment to ensure that code be accessed by the .NET 'ramewor( can integrate with any other code.
VISUAL STUDIO .NET
Visual !tudio .NET is a complete set of development tools for building +!7 /eb applications, 89 /eb services, des(top applications, and mobile applications In addition to building high* performing des(top applications, you can use Visual !tudio:s powerful component*based development tools and other technologies to simplify team*based design, development, and deployment of Enterprise solutions.
Visual Basic .NET, Visual C;; .NET, and Visual C< .NET all use the same integrated development environment "I=E$, which allows them to share tools and facilitates in the creation of mi%ed*language solutions. In addition, these languages leverage the functionality of the .NET 'ramewor( and simplify the development of +!7 /eb applications and 89 /eb services.
Visual !tudio supports the .NET 'ramewor(, which provides a common language runtime and uni#ed programming classes) +!7.NET uses these components to create +!7 /eb applications and 89 /eb services. +lso it includes 9!=N ibrary, which contains all the documentation for these development tools.
&* FEATURES OF S+L "ATA BASE
INTRO"UCTION TO S+L
Ser,er
!>l !erver is comprehensive operating environment that pac(s h power of mainframe relation database management system into user?s microcomputer. It provides a set of functional program that user can use as tools to build structures and perform tas(s. Because applications are developed on !>l !erver are completely portable to the other versions of the programmer can create a comple% application in a single user, environment and then move it to a multi*user platform. 3sers do not have to be an e%pert to appreciate !>l !erver but the better user understands the program, the more productively and creatively he can use the tools it provides.
Re-at.ona- "ata/ase Management System
!>l !erver the right tool
!>l !erver gives you @igh Capacity
=atabase management tools
!tructure of !>l !erver =atabase
S0- Ser,er 1ata/ase 2an /e 1es2r./e at two 1.3erent -e,e-s
7hysical !tructure
ogical !tructure
Phys.2a- Str42t4re
a$ 0ne or more data #les b$ Two or more log #les c$ 0ne control #le
Log.2a- Str42t4re
a$ Table spaces b$ !egments c$ E%tents d$ =ata Bloc(s The data #les contain all user data in terms of tables, inde% and views. The log #les contain the information to open and be recovered, of undone after a transaction "&ollbac($.
The control #le physical data, media information to open and manage data #les. If the control #le is damaged the server will not be able to open or use the database even if the database is undamaged.
"ATABASE The conventional data processing approach is to develop a program "or many programs$ for each application. This result in one or more data #les for each application. !ome of the data may be common between #les. @owever one application may re>uire the #le to be organi-ed on a particular #eld, while other application may re>uire the #le to be organi-ed on another #eld. + maor drawbac( of the conventional method is that the storage access methods are built in to the program. Therefore, though the same data may be re>uired by two applications, the data will have to be sorted in two di1erent places because each application depends on the way that the data stored.
There are various drawbac(s of conventional data #le processing environment. !ome of them are listed belowA
"ata Re14n1an2y !ome data elements li(e name, address, identi#cation code, are used in various applications. !ince data is re>uired by multiple applications, it is stored in multiple data #les. In most cases, there is a repetition of data. This is referred to as data redundancy, and leads to various other problems.
"ata Integr.ty Pro/-ems =ata redundancy is one reason for the problem of data integrity. !ince the same data is stored in di1erent places, it is inevitable that some inconsistency will creep in.
"ata A,a.-a/.-.ty Constra.nts /hen data is scattered in di1erent #les, the availability of information from a combination of #les is constrained to some e%tent.
"ata/ase Management System + database management system "=B9!$ consists of a collection of interrelated data and a set of programs to access the data. The collection of data is usually referred to as the database. + =atabase system is designed to maintain large volumes of data. 9anagement of data involvesA
=e#ning the structures for the storage of data
7roviding the mechanisms for the manipulation of the data
7roviding for the security of the data against unauthori-ed access
Users o5 the "BMS Broadly, there are three types of =B9! usersA
The application programmer
The end user
The database administrator "=B+$ The application programmer writes application programs that use the database. These programs operate on the data in the database. These operations include retrieving information, inserting data, deleting or changing data.
The end user interacts with the system either by invo(ing an application program or by writing their >ueries in a database >uery language. The database >uery language allows the end user to perform all the basic operations "retrieval, deletion, insertion and updating$ on the data.
The =B+ has to coordinate the functions of collecting information about the data to be stored, designing and maintaining the database and its security. The database must be designed and maintained to provide the right information at the right time to authori-ed people. These responsibilities belong to the =B+ and his sta1.
A"#ANTAGES OF A "BMS The maor advantage that the database approach has over the conventional approach is that a database system provides centrali-ed control of data. 9ost bene#ts accrue from this notion of centrali-ed control.
RE#$%#A%C& CA% E CO%'RO((E#
3nli(e the conventional approach, each application does not have to maintain its own data #les. Centrali-ed control of data by the =B+ avoids unnecessary duplication of data and e1ectively reduces the total amount of data storage re>uired. It also eliminates the e%tra processing necessary to trace the re>uired data in a large mass of data present. +ny redundancies that e%ist in the =B9! are controlled and the system ensures that these multiple copies are consistent.
INCONSISTENC6 CAN BE A#OI"E"
!ince redundancy is reduced, inconsistency can also be avoided to some e%tent. The =B9! guarantee and that the database is never inconsistent, by ensuring that a change made to any entry automatically applies to the other entries as well. The process is known as propagating update.
T!E "ATA CAN BE S!ARE" + database allows the sharing of data under its control by any number of application program or users. !haring of data does not merely imply that e%isting applications can share the data in the database, it also means that new applications can be developed to operate using the same database.
STAN"AR"S CAN BE ENFORCE"
!ince there is centrali-ed control of data, the database administrator can ensure that standards are maintained in the representation of the
stored data formats. This is particularly useful for data interchange, or migration of data between two systems. SECURIT6 RESTRICTIONS CAN BE APPLIE" The =B9! guarantees that only authori-ed persons can access the database. The =B+ de#nes the security chec(s to be carried out. =i1erent chec(s can be applied to di1erent operations on the same data. 'or instance, a person may have the access rights to >uery on a #le, but may not have the right to delete or update that #le. The =B9! allows such security chec(s to be established for each piece of data in the database.
INTEGRIT6 CAN BE MAINTAINE"
Centrali-ed control can also ensure that ade>uate chec(s are incorporated in the =B9! to provide data integrity. =ata integrity means that the data contain in the database is both accurate and consistent. Inconsistency between two entries can lead to integrity problems. @owever, even if there is no redundancy, the data can still be inconsistent. 'or e%ample a student may have enrolled in 4 courses in a semester when the ma%imum number of courses one can enroll in is . +nother e%ample could be that of a student enrolling in a course that is not being o1ered that semester. !uch problems can be avoided in a =B9! by establishing certain integrity chec(s to be carried out whenever any update operation is done. These chec(s can be speci#ed at the database level, besides the application programs.
"ATA IN"EPEN"ENCE
In non*database systems, the re>uirement of the application dictates the way in which the data is stored and the access techni>ues. Besides, the (nowledge of the organi-ation of the data, the access techni>ues are built into the logic and code of the application. These
systems are data dependent. Consider this e%ample, suppose the university has an application that processes the student #le. 'or performance reason, the #le is inde%ed on the roll number. The application would be aware of the e%isting inde%, and the internal structure of the application would be built around this (nowledge. Now consider that the some reason, the #le is to inde% on the registration data. In this case it is impossible to change the structure of the stored data without a1ecting the application too. !uch an application is a data dependent one. It is desirable to have data independent applications. !uppose two applications 8 and D need to access the same #le. @owever both the applications re>uire a particular #eld to be stored in di1erent formats. +pplication 8 re>uires the #eld customer balanceF to be stored in decimal format, while the application D re>uires it to be stored in binary format. This would pose a problem in an old system. In a =B9! di1erences may e%ist in the way that data is actually stored, and the way that it is seen and used by a given application.
FEATURES OF R"BMS
The ability to create multiple relations and enter data into them
+n interactive >uery language
&etrieval of information stored in more than one table
NORMALI7ATION Normali-ation is a process of simplifying the relationship between data elements in a record. It is the transformation of comple% data stores to a set of smaller, stable data structures.
Normali-ed data structures are simpler, more stable and are easier to maintain. Normali-ation can therefore be de#ned as a process of simplifying the relationship between data elements in a record.
P4r8ose For Norma-.9at.on Normali-ation is carried out for the following four reasonsA
To structure the data so that there is no repetition of data, this helps in saving space.
To permit simple retrieval of data in response to >uery and report re>uests.
To simplify the maintenance of the data through updates, insertions and deletions.
To reduce the need to restructure or reorgani-e data when new application re>uirements arise.
Testing * Testing is a process of e
Testing (jectives* 3.
Testing is a process of e
/.
A good test case is one that has a proaility of finding an as yet undiscovered error
.
A successful test is one that uncovers an undiscovered error
Testing 'rinciples* •
All tests should e traceale to end user re#uirements
•
Tests should e planned long efore testing egins
•
Testing should egin on a small scale and progress towards testing in large
•
8
To e most effective testing should e conducted y a independent third party
•
The primary ojective for test case design is to derive a set of tests that has the highest livelihood for uncovering defects in software. To accomplish this ojective two different categories of test case design techni#ues are used. They are
7hite o< testing.
&lac% o< testing.
)hite-*o+ testing: 7hite o< testing focus on the program control structure. Test cases are derived to ensure that all statements in the program have een e
lo!"-*o+ testing: &lac% o< testing is designed to validate functional re#uirements without regard to the internal wor%ings of a program. &lac% o< testing mainly focuses on the information domain of the software, deriving test cases y partitioning input and output in a manner that provides through test coverage. Incorrect and missing functions, interface errors, errors in data structures, error in functional logic are the errors falling in this category.
Testing strategies* A strategy for software testing must accommodate low+level tests that are necessary to verify that all small source code segment has een correctly implemented as well as high+level tests that validate major system functions against customer re#uirements.
Testing fundamentals* Testing is a process of e
Testing Information flow* Information flow for testing flows the pattern. Two class of input provided to test the process. The software configuration includes a software re#uirements specification, a design specification and source code. Test configuration includes test plan and test cases and test tools. Tests are conducted and all the results are evaluated. That is test results are compared with e
$nit testing* $nit testing is essential for the verification of the code produced during the coding phase and hence the goal is to test the internal logic of the modules. $sing the detailed design description as a guide, important paths are tested to uncover errors with in the oundary of the modules. These tests were carried out during the programming stage itself. All units of iennaS:; were successfully tested.
Integration testing * Integration testing focuses on unit tested modules and uild the program structure that is dictated y the design phase.
System testing* System testing tests the integration of each module in the system. It also tests to find discrepancies etween the system and itBs original ojective, current specification and system documentation. The primary concern is the compatiility of individual modules. 8ntire system is wor%ing properly or not will e tested here, and specified path (D&C connection will correct or not, and giving output or not are tested here these verifications and validations are done y giving input values to the system and y comparing with e
Acceptance Testing: This testing is done to verify the readiness of the system for the implementation. Acceptance testing egins when the system is complete. Its purpose is to provide the end user with the confidence that the
system is ready for use. It involves planning and e
Test Cases* Test cases are derived to ensure that all statements in the program have een e
6uarantee that logical decisions on their true and false sides.
•
8
•
8
•
8
The test case specification for system testing has to e sumitted for review efore system testing commences. CONCLUSION
The pac%age was designed in such a way that future modifications can e done easily. The following conclusions can e deduced from the development of the project.
Automation of the entire system improves the efficiency
It provides a friendly graphical user interface which proves to e etter when compared to the e
It gives appropriate access to the authori!ed users depending on their permissions.
It effectively overcomes the delay in communications.
$pdating of information ecomes so easier.
System security, data security and reliaility are the stri%ing features.
The System has ade#uate scope for modification in future if it is necessary.
F$'$RE E%,A%CEME%'S:
This application avoids the manual wor% and the prolems concern with it. It is an easy way to otain the information regarding the various products information that are present in the Super mar%ets. 7ell I and my team memers have wor%ed hard in order to present an improved wesite etter than the e
BIBLIOGRAPHY
The following oo%s were referred during the analysis and e
MCROSOF' .%E' )', C/
2icrosoft .net series
ASP .%E' 0.1 PROFESSO%A(
7ro< 'ulishers
ASP .%E' )', C/ 0112
Apress 'ulications
C/ COO3 OO3
( reilly 'ulications
PRO4RAMM%4 MCROSOF' ASP .%E' 0.1 APP(CA'O%
7ro< 'rofessional 6uide
E4%%%4 ASP .%E' 0.1 E-COMMERCE % C/ 0112
"ovice to 'rofessional.
)ES'ES:
www.google.com www.microsoft.com
