MotoReview Report Kripal

1
A
Major Project Report
ON
BIKES AND CARS DATA MANAGER
for the Partial fulfilment of the award of

Degree of
Bachelor of Computer Application ( BCA)
Under the Guidance of : Submitted by:
Mr. Siddharth Mukherji Kripal Singh Rajawat

(AP-II, IT & CA) 16BCAN062
Dipesh Sharma
16BCAN076
Divesh Sharma
16BCAN077
Department of Information Technology & Computer Application

2
JECRC UNIVERSITY, JAIPUR

APRIL 2019
Candidate’s Declaration
I hereby declare that the project work, which is being presented in the Project Report, entitled
“MotoReview” in partial fulfillment for the award of Degree of “Bachelor of Computer Application”
in Deptt. of Information Technology , JECRC University is a record of my own investigations
carried under the Guidance of Mr. Siddharth Mukherji.
I have not submitted the matter presented in this Project Report anywhere for the award of any other
Degree.
Name of Candidate: Kripal Singh Rajawat
Signature
Enrolment No.: 16BCAN062
Name of Supervisor/Guide
Mr. Siddharth Mukherji
Countersigned By:
HoD-IT & CA
3
INDEX
ABSTRACT
1. INTRODUCTION
2. FEASIBILITY STUDY OF THE PROJECT
3. SYSTEM SPECIFICATION
3.1 HARDWARE SPECIFICATION
3.2 SOFTWARE SPECIFICATION
4. SOFTWARE FEATURES
4.1 NetBeans IDE 8.2 (Smarter way to code)
4.2 FEATURES OF FXML :
4.2.1 Features of FXML :
4.3 Scene Builder :
5. SYSTEM DESIGN AND DEVELOPMENT
5.1 FILE DESIGN :
5.2 Relational File Database :
5.3 INPUT DESIGN
5.4 OUTPUT DESIGN
5.5 DATABASE DESIGN
5.5.1 Objectives of Database design
5.6 DATAFLOW DIAGRAM
5.6.1 Diagrammatic view for Login Interface
5.6.2 Flow view for further process
5.6.3 Modification view :
6. Analysis
7. SYSTEM TESTING AND IMPLEMENTATION
7.1 SYSTEM TESTING
4
7.2 Test Plan

7.3 Black Box Testing
7.4 Unit Testing
7.5 Integration Testing
8. System Maintenance
8.1 Threats to System Security
8.2 System Security
8.3 System Security Measures
8.3.1 Identification
8.3.2 Access Control
8.3.3 Audit Control
8.3.4 System Integrity
9. SYSTEM IMPLEMENTATION
9.1 Planning
9.2 Training
9.2.1 Training Systems Operators
9.2.2 Training Guidelines
9.3 System Testing
9.4 Changeover planning
10. CONCLUSION
11. SCOPE FOR FURTHER ENHANCEMENT
12. BIBLIOGRAPHY
12.1 REFERENCE BOOKS
12.2 REFERENCE WEBSITES :
13. SNAPSHOTS OF REPORTS/OUTPUTS/FORMS/DESIGNS
13.1 Login view
13.2 User Registration view
13.3 Home View
13.4 Bike Company Selection section
13.5 Selected company’s bikes
13.6 Bike specific specifications
5
13.7 Car Company section

13.8 Support view
13.9 Car company selection view
13.10 Specific car selection view
14. CODING
14.1 FXML code for user interface development
14.1.1 Code for login panel design
14.1.2 UI code for Home view
14.1.3 UI Code for Bike Company selection module
14.1.4 UI code for registration
6
ABSTRACT
In today’s world Computer System is one of the integral part of out life. Computers have
made the life and lifestyle of corporate world to common man ease to a great extend.
The use of software in corporate world has made the functioning of the organization
smooth and efficient. Due to this the industry is able to keep the track of its progress
and maintain the records. These records can be easily accessed and thus help the
organization to know it’s functioning & track the success & failures of the processes.
This helps the organization to grow. Business software applications come with the
capability of automating several processes which are otherwise complex and time
consuming to be done manually. These applications save a lot of time and money by
accomplishing different tasks in minutes. Otherwise, businesses need to hire employees
to do those tasks. Choosing the right business software can help the company grow by
leaps and bounds. Small Business software application can perform word processing,
payroll, inventory control and accounting functions and a lot more. The software is
basically responsible for managing the tasks of the entire organization.
Use of the software is important for automation of the organization’s tasks as well as
reporting the progress or lags in the organization’s activities. This improves company’s
efficiency and effectiveness of the company’s activities. The software reduces the
workload and automation of activities. It also assists in elimination of human errors, as a
result, improves effectiveness and consistency. There are various types of business
software commonly used by companies. Software is responsible for accomplishing
different tasks. One of the most important business software for any organization is the
payroll system. This software is important for managing payments within the
organization for employees and contractors. This is able to calculate the payment and
tax deductions for each and every employee in the organization. Business Software
Solutions provides business productivity that is available in different types and modules.
The most important and motivating factors for using the Business Software are
increasing the productivity and profits.
7
1.INTRODUCTION
In today’s world Computer System is one of the integral part of out life. Computers have
made the life and lifestyle of corporate world to common man ease to a great extend.
The use of software in corporate world has made the functioning of the organization
smooth and efficient. Due to this the industry is able to keep the track of its progress
and maintain the records. These records can be easily accessed and thus help the
organization to know it’s functioning & track the success & failures of the processes.
This helps the organization to grow.
The proposed project is developed to manage the automobile in the automobile dealer
company. The main module in this project is login, automobile management, customer
management, sales, complaints and reports. The first module is the login. The
automobile showroom owner should login to the project for usage. The username and
password are verified and if it is correct, next form opens. If the username and
password are not correct, it shows the error message.
When a customer search for a automobile, if the automobile is available, they will be
taken to a page that shows the details of the automobile including automobile name,
automobile ID, quantity, price etc. “Automobile Management System” is useful for
maintaining automobiles, accurate vehicle information for customers effectively and
hence helps for establishing good relation between customer and automobile
organization. It contains various customized modules for effectively maintaining
automobiles information accurately and safely.
New user can register in order to use the full features of this system. Normal users can
also access the proposed system but with limited features. Only the registered users
can get more priorities than the unregistered guest user. Once the guest users register
to this system, they can also get full access to this system.
8
So in this way our Automobile vehicle manager will work with full efficiency and
accuracy also it contains various customized modules for effectively maintaining
automobiles information accurately and safely.
2. FEASIBILITY STUDY OF THE PROJECT
To make this software more handy and feasible to the user we have divided it into few
different different modules and they are as follows :
 Login module
 Registration module
 User module
 Automobile module
 Cars company module
 Bikes company module
 Support module
 Car specific module
 Bike specific module
Login module :
It is used for logging in the automobile details manager. It is used for verifying the user.
Once the user is authenticated, they can access the system.
Registration module :
New user can register in order to use the full features of this system. Normal users can
also access the proposed system but with limited features. Only the registered users
can get more priorities than the unregistered guest user. Once the guest users register
to this system, they can also get full access to this system.
User module :
It is used for adding new user and for updating existing customers. It is used for storing
new user as well as for updating the customer’s details. The module is very useful to
find the number of user who registered.
Automobile module :
9
It is used for adding new automobiles and for viewing, editing and deleting existing
automobiles. It is used for searching items in this system. Here the admin have the
privileges to search items in this system. Automobile details are stored with their brand
name. When a particular brand is being liked by people, that particular brand will be
purchased and kept in stock with large quantity.
Cars company module :
In this module of project we are keeping records of new car companies and if any new
company comes into the market than we have a option to add that new company into
the car company database.
Bikes company module :
In this module of project we are keeping records of new bikes companies and if any new
company comes into the market than we have a option to add that new company into
the bike company database.
Support module :
In this module of our project we placed a very important feature i.e. feedback and issue
complain. At runtime if any problem occurred to user than they may direct contact to us
and write us their problem in a very elaborative way.
3. SYSTEM SPECIFICATION
10
3.1 HARDWARE SPECIFICATION
CPU : Intel Core i3
RAM : 32MB
Hard Disk : 5 GB
Monitor : 16 LG
Mouse : Logitech mouse
Keyboard : 104 Keys
Mother Board : Intel
Speed : 3.3 GHZ
3.2 SOFTWARE SPECIFICATION
Operating System : Platform Independent
Front End : JAVAFX, FXML, CSS
Back End : JAVA, Oracle Database.
Reports : Data Report
Tools : NetBeans (Smarter way to code)
Support : FXML
4. SOFTWARE FEATURES :
11
4.1 NetBeans IDE 8.2 (Smarter way to code)
NetBeans IDE gives you skeleton applications in the form of project templates for all
the technologies it supports. In addition, it provides a set of sample applications, some
of which can be recreated step by step by following a related tutorial available on
NetBeans.org.
The IDE provides project templates and sample projects that help you create Java SE
applications, Java EE applications, Java ME applications, HTML5 applications,
NetBeans Platform applications, PHP application, and C/C++ applications.
 Best Support for Latest Java Technologies
 Fast & Smart Code Editing
 Easy & Efficient Project Management
 Rapid User Interface Development
 Bug Free Code
 Support for Multiple Languages
 Language cross platform support
4.2 FEATURES OF FXML :
FXML is popular because it focuses on data rather than data presentation. The
other markup language such as HTML is used for data presentation.
12
This separates the data and its presentation part and gives us the freedom to
present the data, the way we want, once we receive it using FXML.
Two or more systems can receive the same data from a same FXML and present
it in a different way using other markup language such as HTML.
4.3.1 Features of FXML :
 FXML focuses on data rather than how it looks
 Easy and efficient data sharing
 Compatibility with other markup language HTML
 Supports platform transition
 Allows FXML validation
 Adapts technology advancements
 FXML supports Unicode
4.3.2 Scene Builder :
 A drag-and-drop WYSIWIG interface.
 Tight integration with the NetBeans IDE.
 Integration with any Java IDE is easy.
 Live editing and preview features.
 CSS support
13
5. SYSTEM DESIGN AND DEVELOPMENT
5.1 FILE DESIGN :
A flat file database is a database designed around a single table. The flat file design
puts all database information in one table, or list, with fields to represent all parameters.
A flat file may contain many fields, often, with duplicate data that are prone to data
corruption. If data between two flat files have to be merged, it is needed to copy and
PSMte relevant information from one file to the other. There is no automation between
flat files.
If two or more flat files that contain client addresses, it is required to manually modify
the address parameters in each file that contains that client’s information. Changing
information in one file has no bearing on other files. Flat files offer the functionality to
store information, manipulate fields, print or display formatted information and exchange
information with others, through email and over the Internet. Some flat files may be
attached to external files, such as text editors, to extend functionality and manage
related information.
5.2 Relational File Database :
A relational database, on the other hand, incorporates multiple tables with methods for
the tables to work together. The relationships between table data can be collated,
merged and displayed in database forms. Most relational databases offer functionality to
share data:
 Across networks
 Over the Internet
 With laptops and other electronic devices, such as palm pilots
 With other software systems
Designing flat file databases is simple and requires little design knowledge. Flat files
can be developed using just about any database engine. Flat files can be created in
relational database engines by not taking advantage of relational design concepts.
14
Designing a relational database takes more planning than flat file databases. With flat
files, it is possible to add information, as you deem necessary.
With relational databases, it is required to be careful to store data in tables such that the
relationships make sense. Building a relational database is dependent upon the ability
to establish a relational model. The model must fully describe how the data is
organized, in terms of data structure, integrity, querying, manipulation and storage.
Relational databases allow defining certain record fields, as keys or indexes, to perform
search queries, join table records and establish integrity constraints.
Search queries are faster and more accurate when based on indexed values. Table
records can be easily joined by the indexed values. Integrity constraints can be
established to ensure that table relationships are valid. If the project is able to establish
a one-to-many relationship in the data tables, relational database should be used
because a flat file is not sufficient to handle the data processing needs. Relational
databases offer more robust reporting with report generators that filter and display
selected fields.
Relational databases offer the capability to building own reporting modules. Most
relational databases also offer the capability to import and export data from other
software. There are three primary relational database systems, proprietary, open source
and embedded. Proprietary relational databases require the use of proprietary
development languages, often times, to complement SQL. Microsoft Access, for
example, combines Visual Basic with SQL. Open source databases, such as MySQL,
are distributed freely to encourage user development.
Embedded, relational databases are packaged as part of other software packages, such
as with tax-preparation software packages. The vendor supplies the database, and all
manipulation tools, to control the database structure. These databases are, often times,
accompanied with tools to provide audit trails of transactions. The vendor supplies the
database, and all manipulation tools, to control the database structure.
15
Each row in a table has its own unique key. Rows in a table can be linked to rows in
other tables by adding a column for the unique key of the linked row (such columns are
known as foreign keys). Codd showed that data relationships of arbitrary complexity can
be represented by a simple set of concepts.
Part of this processing involves consistently being able to select or modify one and only
one row in a table. Therefore, most physical implementations have a unique primary
key (PK) for each row in a table. When a new row is written to the table, a new unique
value for the primary key is generated; this is the key that the system uses primarily for
accessing the table. System performance is optimized for PKs. Other, more natural
keys may also be identified and defined as alternate keys (AK). Often several columns
are needed to form an AK (this is one reason why a single integer column is usually
made the PK). Both PKs and AKs have the ability to uniquely identify a row within a
table. Additional technology may be applied to ensure a unique ID across the world,
a globally unique identifier, when there are broader system requirements.
The primary keys within a database are used to define the relationships among the
tables. When a PK migrates to another table, it becomes a foreign key in the other
table. When each cell can contain only one value and the PK migrates into a regular
entity table, this design pattern can represent either a one-to-one or one-to-
many relationship. Most relational database designs resolve many-to-
many relationships by creating an additional table that contains the PKs from both of the
other entity tables—the relationship becomes an entity; the resolution table is then
named appropriately and the two FKs are combined to form a PK. The migration of PKs
to other tables is the second major reason why system-assigned integers are used
normally as PKs; there is usually neither efficiency nor clarity in migrating a bunch of
other types of columns.
When a PK migrates to another table, it becomes a foreign key in the other table. When
each cell can contain only one value and the PK migrates into a regular entity table, this
design pattern can represent either a one-to-one or one-to-many relationship.
16
5.3 INPUT DESIGN
Input is any data or instructions entered into the memory of a computer. Two types of
input are data and instructions. Data is a collection of unorganized items that can
include words, numbers, pictures, sounds, and video. A computer processes data into
information, which is organized, meaningful, and useful. Instructions can be in the form
of programs, commands, or user responses.
A program is a series of instructions that tells a computer how to perform the tasks
necessary to process data into information. A command is an instruction given to a
computer program. A user response is an instruction you issue to the computer by
responding to a question posed by a computer program. Any hardware component that
allows entering data, programs, commands, and user responses into a computer is an
input device. Inputs of Automobile Management System are eid, ename, qualification,
automobileid, brand, cusid, cusname and salary.
5.4 OUTPUT DESIGN
Output design involves specifying how production of on-screen reports and paper based
reports will occur. Output may occur to database or file for storing information entered or
also for use by other systems. Output is data that has been processed into a useful form
called information. Four types of output are text, graphics, audio, and video. Text
consists of characters (letters, numbers, punctuation marks, or any other symbol
requiring one byte of computer storage space) that are used to create words,
sentences, and paragraphs.
Graphics are digital representations of non-text information such as drawings, charts,

photographs, and animation (a series of still images in rapid sequence that gives the
illusion of motion). Audio is music, speech, or any other sound. Video consists of
images played back at speeds to provide the appearance of full motion. An output
device is any computer component capable of conveying information to a user. Audio is
music, speech, or any other sound. Video consists of images played back at speeds to
provide the appearance of full motion.
17
5.5 DATABASE DESIGN
Database is designed to manage large bodies of information. The management of data

involves both the definitions of structures for the storage of information. In addition the
data base system must provide for the safety of the information solved, despite system
crashes or due to attempts at unauthorized access. For developing an efficient
database proposed project have to fulfill certain conditions such as controlled
redundancy.
 Defining the data

 Inputting the data
 Locating the data
 Accessing the data
 Communicating the data
 Revising the data
Objectives of Database design
In database design several objectives are designed such as:
 Ease of use
 Control of data integrity
 Control of redundancy
 Control of security
 Data independence (logical & physical)
 Data storage protection
 System performance
 System functions
 System compatibility
In a majority of cases, a person who is doing the design of a database is a person with
expertise in the area of database design, rather than expertise in the domain from which
the data to be stored is drawn e.g. financial information, biological information etc.
Therefore, the data to be stored in the database must be determined in cooperation with
a person who does have expertise in that domain, and who is aware of what data must
be stored within the system.
18
This process is one which is generally considered part of requirements analysis, and
requires skill on the part of the database designer to elicit the needed information from
those with the domain knowledge. This is because those with the necessary domain
knowledge frequently cannot express clearly what their system requirements for the
database are as they are unaccustomed to thinking in terms of the discrete data
elements which must be stored. Data to be stored can be determined by Requirement
Specification.
Once a database designer is aware of the data which is to be stored within the
database, they must then determine where dependency is within the data. Sometimes
when data is changed you can be changing other data that is not visible. For example,
in a list of names and addresses, assuming a situation where multiple people can have
the same address, but one person cannot have more than one address, the address is
dependent upon the name. When provided a name and the list the address can be
uniquely determined; however, the inverse does not hold - when given an address and
the list, a name cannot be uniquely determined because multiple people can reside at
an address. Because an address is determined by a name, an address is considered
dependent on a name.
Once the relationships and dependencies amongst the various pieces of information
have been determined, it is possible to arrange the data into a logical structure which
can then be mapped into the storage objects supported by the database management
system. In the case of relational databases the storage objects are tables which store
data in rows and columns. In an Object database the storage objects correspond
directly to the objects used by the Object-oriented programming language used to write
the applications that will manage and access the data. The relationships may be defined
as attributes of the object classes involved or as methods that operate on the object
classes.
The way this mapping is generally performed is such that each set of related data which
depends upon a single object, whether real or abstract, is placed in a table.
Relationships between these dependent objects is then stored as links between the
various objects.
19
Each table may represent an implementation of either a logical object or a relationship

joining one or more instances of one or more logical objects. Relationships between
tables may then be stored as links connecting child tables with parents. Since complex
logical relationships are themselves tables they will probably have links to more than
one parent. This process is one which is generally considered part of requirements
analysis, and requires skill on the part of the database designer to elicit the needed
information from those with the domain knowledge. This is because those with the
necessary domain knowledge frequently cannot express clearly what their system
requirements for the database are as they are unaccustomed to thinking in terms of the
discrete data elements which must be stored. Data to be stored can be determined by
Requirement Specification.
In a majority of cases, a person who is doing the design of a database is a person with
expertise in the area of database design, rather than expertise in the domain from which
the data to be stored is drawn e.g. financial information, biological information etc.
Therefore, the data to be stored in the database must be determined in cooperation with
a person who does have expertise in that domain, and who is aware of what data must
be stored within the system.
the relationships and dependencies amongst the various pieces of information have
been determined, it is possible to arrange the data into a logical structure which can
then be mapped into the storage objects supported by the database management
system. In the case of relational databases the storage objects are tables which store
data in rows and columns. In an Object database the storage objects correspond
directly to the objects used by the Object-oriented programming language used to write
the applications that will manage and access the data.
5.6 DATAFLOW DIAGRAM
A Data Flow Diagram (DFD) is a diagram that describes the flow of data and the
processes that change data throughout a system. It’s a structured analysis and design
tool that can be used for flowcharting in place of or in association with information.
Oriented and process oriented system flowcharts. Four basic symbols are used to
20
construct data flow diagrams. They are symbols that represent data source, data flows,
and data transformations and data storage. The points at which data are transformed
are represented by enclosed figures, usually circles, which are called nodes.
For achieving the abovementioned criteria’s we have to make use of various features
that are available with the RDBMS by enforcing integrity constrains, it is possible to
ensure data integrity and reduce data inconsistency to a great extent.
Data Flow Diagram Symbols
- Source or Destination of data
- Data Flow
- Process
- Storage
When analysts prepare the Data Flow Diagram, they specify the user needs at a level of
detail that virtually determines the information flow into and out of the system and the
required data resources.
21
The network is constructed by using a set of symbols that do not imply physical
implementations. The Data Flow Diagram reviews the current physical system, prepares
input and output specification, and specifies the implementation plan.
Steps to Construct Data Flow Diagrams
Four steps are commonly used to construct a DFD
 Process should be named and numbered for easy reference. Each name
should be representative of the process.
 The destination of flow is from top to bottom and from left to right.
 When a process is exploded in to lower level details they are numbered.
 The names of data stores, sources and destinations are written in capital
letters.
Rules for constructing a Data Flow Diagram
 Arrows should not cross each other.

 Squares, circles and files must bear names.
 Decomposed data flow squares and circles can have same names.
 Draw all data flow around the outside of the diagram.
Diagrammatic view for Login Interface
Moto Review
Login panel with
Many check
Point.
22
Oracle
database
Validate
username and
Password.
If values are
If values are
invalid than
valid than you
you will get an
will redirect to
error message.
home interface
Procee
d
Flow view for further process :
Successfu
l -
ly
Login
23
Bike company
Car company Specific
Specific Details
Details representing
representing in a table
in a table
After After
proceeding you proceeding you
will get car will get bike
specific specific
interface. interface.
Ex : Ex : Passion Pro
Lamborgirni
Specifications
Modification view :
Specifications
24
Modification
Modifications s
Made according Made
to requirements according to
For cars. requirements
For bikes.
Oracle database
constraints
check
Point.
If invalid
If valid than
than shows error
Data interface.
modified.
6. DATABASE TABLES
6.1 For Bike Company:

25
Bike No. Bike Company Name
Egg. 16515313 egg. Harley Davidson
6.2 For Car company :
Car No. Car Company Name
eg. 16515313 eg. Maruti
6.3 For Bike Specific data :
Bike No. Bike Name
eg. 16515313 eg. Splenor plus
6.4 For Car Specific data :
Car No. Car Company Name
eg. 16515313 eg. Maruti 800
6.5 For Login User Details :
Username. Password
26
eg. Kripal eg. ****************
6.6 For Registration of New User :
Name Email Address Password Mobile no. Address
Kripal kripal@gm.com ********* 999992989 Kalwar road, jaipur
7. SYSTEM TESTING AND IMPLEMENTATION
7.1 SYSTEM TESTING :

27
The common view of testing held by users is that it is performed to prove that there are
no errors in a program. It is extremely difficult since designer cannot prove to be one
hundred percent accurate. Therefore, the most useful and practical approach is with the
understanding that testing is the process of executing a program with explicit intention
of finding errors that make the program fail.
Testing has its own cycle. The testing process begins with the product requirements
phase and from there parallels the entire development process. In other words, for each
phase of the development process there is an important testing activity. It is extremely
difficult since designer cannot prove to be one hundred percent accurate. Therefore, the
most useful and practical approach is with the understanding that testing.
Successful testing requires a methodical approach. It requires focusing on basic critical

factors:
 Planning
 Project and process control
 Risk management
 Inspections
 Measurement tools
 Organization and professionalism
7.2 Test Plan
Before going for testing, first we have to decide upon the type of testing to be carried
out. The following factors are taken into consideration:
 To ensure that information properly flows into and out of program

 To find out whether the local data structures maintains its integrity during all
steps in an algorithm execution
 To ensure that the module operate properly at boundaries established to limit
or restrict processing
 To find out whether error - handling paths are working correctly or not
 To find out whether the values are correctly updated or not
 Check for validations
28
7.3 Black Box Testing
It is a software testing approach in which the tester doesn’t know the internal working of
the item being tested. For example in a Black box test, on software design the tester
only knows the input and the expected outputs. Tester doesn’t know how the program
derives the output. Tester doesn’t even imagine as to how, the coding is done. Tester
need to know only the specifications.
The advantages of black box testing approach are :
 The test is unbiased because the designer and the tester is independent of
each other
 The tester needs no specific knowledge on any programming language
 The test is done from the point of view of the user, not the designer.
 The test can be designed as soon as the specifications are complete
The disadvantages of black box testing approach are
 The test can be redundant if the software designer has already run a test
case.
 The test can be difficult to design
 Testing every possible input stream is unrealistic.
7.4 Unit Testing
Unit or module testing is the process of testing the individual components (subprograms
or procedures) of a program. The purpose is to discover discrepancies between the
modules interface specification and its actual behavior. In our system each module must
be tested independently for validation.
7.5 Integration Testing
Integration testing is the process of combining and testing multiple components

together. The primary objective of integration testing is to discover errors in the
29
interfaces between the components. In our system each of the modules mentioned
above, are tested for checking the integration between them, after each of them are
tested individually.
Software testing is an investigation conducted to provide stakeholders with information

about the quality of the software product or service under test. Software testing can also
provide an objective, independent view of the software to allow the business to
appreciate and understand the risks of software implementation. Test techniques
include the process of executing a program or application with the intent of
finding software bugs (errors or other defects), and verifying that the software product is
fit for use.
Software testing involves the execution of a software component or system component

to evaluate one or more properties of interest. In general, these properties indicate the
extent to which the component or system under test:
 meets the requirements that guided its design and development,

 responds correctly to all kinds of inputs,
 performs its functions within an acceptable time,
 it is sufficiently usable,
 can be installed and run in its intended environments, and
 achieves the general result its stakeholders desire.
As the number of possible tests for even simple software components is practically
infinite, all software testing uses some strategy to select tests that are feasible for the
available time and resources. As a result, software testing typically (but not exclusively)
attempts to execute a program or application with the intent of finding software
bugs (errors or other defects). The job of testing is an iterative process as when one
bug is fixed, it can illuminate other, deeper bugs, or can even create new ones.
Software testing can provide objective, independent information about the quality of
software and risk of its failure to users or sponsors.
30
Software testing can be conducted as soon as executable software (even if partially

complete) exists. The overall approach to software development often determines when
and how testing is conducted. For example, in a phased process, most testing occurs
after system requirements have been defined and then implemented in testable
programs. In contrast, under an agile approach, requirements, programming, and
testing are often done concurrently.
As a result, software testing typically (but not exclusively) attempts to execute a

program or application with the intent of finding software bugs (errors or other defects).
The job of testing is an iterative process as when one bug is fixed, it can illuminate
other, deeper bugs, or can even create new ones.
8. System Maintenance
All system is dynamic and subjects to constantly changing requirements. Effort must be
devoted to adapting them and design must be flexible specified so that such changes
can be easily implemented. It activity is called system maintains. It includes
improvement of system functions and correction of errors. Back up of the entire
database files are taken and stored in secondary storage devices like magnetic tapes
and disks so that it is possible to restore the system at the earliest. If there is a break
31
down or collapse, then the system giver provision to restore database files, storing data
in a separate secondary device leads to an effective and efficient maintains of the
system.
The master file has flags for maintains after for maintains. After the mentioned period,
the rejection suppliers, unused data in the files will be deleted in the master file. It
method is the increasing the memory to store the data. Software maintenance is a set of
software engineering activities that occur after software has been delivered for the
customer and put into operation. The success of the software and the project relies on
the maintenance procedure adopted. As with the venture of human, not a single one is
perfect. The further modifications are left to the followers. It is because the opinion or
vision or a thing differs from individual to individual. The maintenance is performed at
regular intervals to keep the project safe and reliable.
Development is single activity maintenance is a continuous activity. Maintenance

involves activities like inspections, corrections and enhancements. Once the system is
delivered and deployed, it enters the maintenance phase. The system need to be
maintained not because of some of its components wear out and need to be replaced,
but because there are some residual errors remaining in the system that must be
removed as they are discovered. It includes activities related to debugging the software
after it goes live, changes are required to address evolving software and enhancement
to meet changing customer requirements. So maintenance phase involves
 Understanding the effects of change.

 Testing the new parts
 Retesting the old parts that were not changed
 Making changes to both the code and the documents.
These changes have to be designed by the user before the change can be carried out.
Since requirement change request involves cost, user will be cautious while requesting
the software changes. The software will require continued support. The system
maintenance means the maintenance activities after and during the system
32
development processes. It include activities related to debugging the software after it

goes live, changes acquired to meet changes in user requirement.
Maintenance phase identifies if there are any changes required in the current system. If
the changes are identified, then an analysis is made to identify if the changes are really
required. Cost benefit analysis is away to find out if the change is really essential.
System Analysis
The term system is derived from the Greek word ‘systema’, which means of organized
relationship among functioning units of components. And the study of system concepts
has three basic implications:
 A system must be designed to achieve a predetermined objective

 Interrelationships and interdependence must exist among the components
 The objectives of the organizations as a whole have a high priority than the
objective of its subsystems.
 Software testing can also provide an objective, independent view of the
software to allow the business to appreciate and understand the risks of
software implementation.
Preliminary Analysis
Analysis is the detailed study of the various operations performed by a system and their
relationships within and outside the system. For the efficient and effective utilization of
the available resources, timing availability of accurate information is very important.
Information is the back bone of any organization. There for, it has to be made available
all time to ensure proper decision-making.
Information also has to be accurate, current, timely, relevant and usable. In other words,
an effective information system should be able to provide information to those in need of
it, at the time they need of it, at the time they need it and in the way they need it. The
need for managing data and retrieving information efficiently, lead to an extensive use of
computers in the business world.
33
The computers have convinced the management that computerized system is

preferable to the existing system; most organization has computerized their application
areas using traditional file processing concepts. The computerized system, by itself
does not guarantee of efficient information retrieval. The effectiveness of the system, to
great deal, depends on the way in which data is organized and managed. Way in which
data is organized in the existing system is not integrated, since there is no connection or
integration between one module and another on accomplishing the task.
Analysis is detailed study of various operations performed by a system and their

relationships within and outside the system. A key question is “what must be done to
solve the problem?” One aspect of analysis is determining the boundaries of the system
and determining whether or not a new proposed system should consider other related
items. It is the process of gathering and interpreting facts; diagnosing the problems and
using the information recommend improvements to the system.
8.1 Threats to System Security
The lists of potential threats are as follows
 Errors and Omissions

 Disgruntled and Dishonest Employees
 Fire
 Natural Disaster
 External Attack
The object-oriented paradigm emphasizes modularity and re-usability. The goal of an

object-oriented approach is to satisfy the "open closed principle". A module is open if it
supports extension, or if the module provides standardized ways to add new behaviors
or describe new states. In the object-oriented paradigm this is often accomplished by
creating a new subclass of an existing class. A module is closed if it has a well defined
stable interface that all other modules must use and that limits the interaction and
potential errors that can be introduced into one module by changes in another. In the
object-oriented paradigm this is accomplished by defining methods that invoke services
on objects. Methods can be either public or private, i.e., certain behaviors that are
34
unique to the object are not exposed to other objects. This reduces a source of many
common errors in computer programming.
The software life cycle is typically divided up into stages going from abstract
descriptions of the problem to designs then to code and testing and finally to
deployment. The earliest stages of this process are analysis and design. The distinction
between analysis and design is often described as "what vs. how". In analysis
developers work with users and domain experts to define what the system is supposed
to do. Implementation details are supposed to be mostly or totally (depending on the
particular method) ignored at this phase. The goal of the analysis phase is to create a
functional model of the system regardless of constraints such as appropriate
technology. In object-oriented analysis this is typically done via use cases and abstract
definitions of the most important objects. The subsequent design phase refines the
analysis model and makes the needed technology and other implementation choices. In
object-oriented design the emphasis is on describing the various objects, their data,
behavior, and interactions. The design model should have all the details required so that
programmers can implement the design in code.
8.2 System Security
Security is a critical stage in system development. Even candidate system must provide
built-in features for security and integrity of data. Without safe guards against
unauthorized access, fraud, embezzlement, fire and natural disaster, a system could be
so vulnerable as to threaten the survival of the organizations.
To do an adequate job on security, the risk, exposure, cost and specific measures such
as password should be analyzed to provide protection. In addition, back up of copies of
software and recovery restart procedures must be available when needed.
The amount of protection depends on the sensitivity of data, the reliability of the user
and the complexity of the system. The motive behind security is to keep the
35
organization running, protect data as an asset and seek management support for more
installations.
8.3 System Security Measures
After system security risk has been evaluated, the next step is to select security
measures. The measures are
 Identification
 Access Control
 Audit Control
 System Integrity
8.3.1 Identification
It is the scheme of identifying person to the system based on “Something you know”
such as a password or a picture badge, “Something you are” such as finger print or
voice print or “Something you have” such as credit card, key or special terminal. The
line of different safeguards the functioning of hardware, software and physical security
and operating procedure. Proper back of hardware and software are extremely
important.
8.3.2 Access Control
Controlling the access to the computer facility is secured through encoded cards or
similar devices. Encryption prevents intruders from accessing data by scrambling
messages across telephones to the destination.
36
8.3.3 Audit Control
Auditing must be supported at all levels of management. Audit control protects a system
from external security breaches and internal fraud or embezzlement. Various software
programs are available to help in audit function.
8.3.4 System Integrity
The line of different safeguards the functioning of hardware, software and physical
security and operating procedure. Proper back of hardware and software are extremely
important.
9. SYSTEM IMPLEMENTATION
System implementation is the important stage of project when the theoretical design is
tunes into practical system. The main stages in the implementation are as follows:
 Planning
 Training
 System testing and
 Changeover planning
37
9.1 Planning :
Planning is the first task in the system implementation. Planning is deciding on the
method and the time scale to be adapted. At the time of implementation of any system
people from different departments and system analysis involve. They are confirmed to
practical problem of controlling various activities of people outside their own data
processing departments. The line manager controlled through an implementation co-
ordinate committee. The committee consists of ideas, Problems and complaints of user
department. It must also consider the implementation of system environment.The line
manager controlled through an implementation co-ordinate committee. They are
confirmed to practical problem of controlling various activities of people outside.
 Self selection and allocation for implementation tasks.

 Consultation with unions and resources available.
 Standby facilities and channels of communication.
9.2 Training
The personnel in the system must know in detail what their roles will be, how they can
use the system, and what the system will or will not do. The success or failure of
welldesigned and technically elegant systems can depend on the way they are
operated and used.
9.2.1 Training Systems Operators
Systems operators must be trained properly such that they can handle all possible
operations, both routine and extraordinary. The operators should be trained in what
common malfunctions may occur, how to recognize them, and what steps to take when
they come.
Training involves creating troubleshooting lists to identify possible problems and

remedies for them, as well as the names and telephone numbers of individuals to
contact when unexpected or unusual problems arise.
38
Training also involves familiarization with run procedures, which involves working
through the sequence of activities needed to use a new system.
9.2.2 Training Guidelines
 Establishing measurable objectives

 Using appropriate training methods
 Selecting suitable training sites
 Employing understandable training materials
9.3 System Testing
System testing is an essential step for the development of a reliable and error-
freesystem. Once source code has been generated, software must be tested to uncover
andcorrect as many errors as possible before delivery to your customer. Your
goal is todesign a series of test cases that have a high likelihood finding
errors but how, thereare different methods that provides a systematic guidance for
designing tests that,Exercise the internal logic of software components,
andE x e r c i s e t h e i n p u t a n d
o u t p u t d o m a i n s o f t h e p r o g r a m t o u n c o v e r e r r o r s i n t h e program
function, behaviour, and performance
9.4 Changeover planning
In manufacturing, changeover is the process of converting a line or machine from

running one product to another. Changeover times can last from a few minutes to as
much as several weeks in the case of automobile manufacturers retooling for new
models. The terms set-upand changeover are sometimes used interchangeably
however this usage is incorrect. Set-up is only one component of changeover.
Example: A soft drink bottler may run 16oz glass bottles one day, perform a
changeover on the line and then run 20oz plastic bottles the next day.
39
The three ups :
Clean-up
Clean-up product, materials and components from the line. It may range from minor, if
only the label of a package is being changed (for example from an English to
a Spanish label) to major, requiring complete disassembly of the equipment, cleaning
and sterilizing of the line components in the case of an injectable pharmaceutical
product.
Set-up
Set-up is the process of actually converting the equipment. This may be achieved by
adjusting the equipment to correspond to the next product or by changing non-
adjustable "change parts" to accommodate the product. Typically it will be a combination
of both.
Start-up
Start-up is the time spent fine tuning the equipment after it has been restarted. It is
characterized by frequent stoppages, jams, quality rejects and other problems. It is
generally caused by variability in the clean-up and set-up or by variability in the product
or its components.
10. CONCLUSION
The system is completely menu driven and extremely user friendly since it is developed
in an efficient front end tools and FXML. Appropriate error messages are also provided
too guide the user in a proper and user friendly manner.
The software “MOTO REVIEW” has been developed in windows 2010 environment
using FXML+CSS as front end and ORACLE as back end. Time consumptions reduced
to a great extent and user as less complexity in handling it database.
The project is fully fledged and user friendly, End users will be lightened in using it
software because it is easy to have bills and reports and mostly all contents to be
40
entered are to selected from combo box. It reduces the calculating efforts to be carried
out by the user.
11. SCOPE FOR FURTHER ENHANCEMENT
Further expansion of the system also can be done in future if needed. The application
can be enhanced in the future with the needs of the organization. The database and the
information can be updated to the latest forthcoming versions.
There are also possibilities for enhancing and further developing the project with
customized reports according to the latest information and needs of the company. Thus
the system can be altered in accordance with the future requirements and
advancements. System performance evaluation must be monitored not only to
41
determine whether or not they perform as plan but also to determine if they should have
to meet changes in the information needed for the company.
The performance of the system will be evaluated to determine whether system achieves
the results that are expected and whether the predicted benefits of the system are
realized.
12. BIBLIOGRAPHY :
12.1 REFERENCE BOOKS :
 No book was used as reference during development of this desktop application.
12.2 REFERENCE WEBSITES :
 www.stackoverflow.com
 www.flaticon.com
 www.materialui.co
42
 www.youtube.com/durgasoft
 www.github.com
13. SNAPSHOTS OF REPORTS/OUTPUTS/FORMS/DESIGNS
13.1 Login view :

43
PIC : 1
13.2 User Registration view :

44
PIC : 2
13.3 Home View :

45
PIC : 3
13.4 Bike Company Selection section :

46
PIC : 4
13.5 Selected company’s bikes :

47
PIC : 5
13.6 Bike specific specifications :

48
PIC : 6
13.7 Car Company section :

49
PIC : 7
13.8 Support view :

50
PIC : 8
13.9 Car company selection view :

51
PIC : 9
13.10 Specific car selection view :

52
Pic : 10
14. CODING
Our coding section is devided into 3 parts:
 FXML code for user interface development.

 Java code.
 Cascading style sheets.
14.1 FXML code for user interface development
14.1.1 Code for login panel design:

53
<?xml version="1.0" encoding="UTF-8"?>
<?import com.jfoenix.controls.JFXButton?>
<?import com.jfoenix.controls.JFXPasswordField?>
<?import com.jfoenix.controls.JFXTextField?>
<?import javafx.scene.control.Label?>
<?import javafx.scene.image.Image?>
<?import javafx.scene.image.ImageView?>
<?import javafx.scene.layout.AnchorPane?>
<?import javafx.scene.shape.Line?>
<?import javafx.scene.text.Font?>
<AnchorPane id="AnchorPane" fx:id="anchorPane" prefHeight="534.0"

prefWidth="412.0" style="-fx-background-color: #2f2b43;"
xmlns="http://javafx.com/javafx/8.0.171" xmlns:fx="http://javafx.com/fxml/1"
fx:controller="FXMLDocumentController">
<children>
<JFXTextField id="textFileld" fx:id="userIdTxtField" layoutX="59.0" layoutY="190.0"
prefHeight="39.0" prefWidth="305.0" promptText="UserID" stylesheets="@login.css"
unFocusColor="#9b9e89" />
<JFXPasswordField id="textFileld" fx:id="pwdTxtField" layoutX="59.0" layoutY="267.0"
prefHeight="25.0" prefWidth="305.0" promptText="Password" stylesheets="@login.css"
unFocusColor="#ab9393" />
<JFXButton fx:id="registrationBtn" layoutX="45.0" layoutY="421.0"
onAction="#onRegisterClick" prefHeight="50.0" prefWidth="305.0" text="Registere
Here" textFill="#a19292">



</JFXButton>
54
<JFXButton fx:id="loginBtn" layoutX="59.0" layoutY="334.0" onAction="#onLoginClick"

prefHeight="39.0" prefWidth="101.0" style="-fx-background-color: #2196f3;"
text="Login" textFill="#f2e6e6">


</JFXButton>
<JFXButton fx:id="forgotPwdBtn" layoutX="225.0" layoutY="336.0" prefHeight="39.0"
prefWidth="155.0" text="Forgot your password ?" textFill="#b5a9a9" />
<Label layoutX="170.0" layoutY="61.0" prefHeight="50.0" prefWidth="120.0"
text="Moto" textFill="#2196f3">



</Label>
text="Review" textFill="#a7b5bf">


</Label>
<Line fx:id="line" endX="32.0" layoutX="337.0" layoutY="364.0" startX="-100.0"
stroke="#fffafa" strokeWidth="0.5" />
<ImageView fitHeight="25.0" fitWidth="23.0" layoutX="20.0" layoutY="203.0"
opacity="0.55" pickOnBounds="true" preserveRatio="true">
<image>
<Image url="/LogoMakr_9Tx3RH.png" />
</image>
</ImageView>
<image>
55
<Image url="/LogoMakr_9bo1Ux.png" />

</image>
</ImageView>
pickOnBounds="true" preserveRatio="true">
<image>
<Image url="@blueCar.png" />
</image>
</ImageView>
</children>
</AnchorPane>
14.1.2 UI code for Home view :
<?import java.net.URL?>
<?import javafx.scene.effect.BoxBlur?>
<?import javafx.scene.layout.Pane?>
<AnchorPane id="AnchorPane" prefHeight="601.0" prefWidth="660.0"

styleClass="mainFxmlClass" xmlns="http://javafx.com/javafx/8.0.171"
xmlns:fx="http://javafx.com/fxml/1" fx:controller="BikesNcarController">
<stylesheets>
56
<URL value="@bikesncar.css" />

</stylesheets>
<children>
<Pane prefHeight="601.0" prefWidth="151.0" style="-fx-background-color: #2f2b43;">
<children>
<Label fx:id="motoLabel" layoutX="3.0" layoutY="95.0" prefHeight="34.0"
prefWidth="55.0" text="Moto" textFill="#2196f3">


</Label>
<Label fx:id="review1Label" layoutX="7.0" layoutY="176.0" prefHeight="20.0"
prefWidth="111.0" text="Review !!" textFill="#d7cdcd">


</Label>
<Label fx:id="reviewLabel" layoutX="61.0" layoutY="87.0" prefHeight="50.0"
prefWidth="72.0" text="Review" textFill="#a7b5bf">


</Label>
<Label fx:id="welcomelabel" layoutX="7.0" layoutY="158.0" prefHeight="20.0"
prefWidth="111.0" text="Welcome to Moto" textFill="#d7cdcd">


</Label>
<Label fx:id="herelabel" layoutX="7.0" layoutY="208.0" prefHeight="20.0"
prefWidth="111.0" text="Here you will find" textFill="#b5a2a2">
57


</Label>
<Label fx:id="imptlbl" layoutX="8.0" layoutY="225.0" prefHeight="20.0"
prefWidth="136.0" text="important information" textFill="#b5a2a2">


</Label>
<Label fx:id="oflabel" layoutX="6.0" layoutY="243.0" prefHeight="20.0"
prefWidth="136.0" text="of latest cars and Bikes." textFill="#b5a2a2">


</Label>
<Label fx:id="dashLabel" layoutX="12.0" layoutY="270.0" prefHeight="47.0"
prefWidth="136.0" text=" Dashboard" textFill="#d7cdcd">


</Label>
stroke="#fcfcfc" />
<JFXButton fx:id="homeBtn" layoutX="9.0" layoutY="337.0" onAction="#onHomeClick"
prefHeight="34.0" prefWidth="123.0" text="Home" textFill="#a48989">


</JFXButton>
58
<JFXButton fx:id="BikesBtn" layoutX="10.0" layoutY="373.0" onAction="#onBikesClick"

prefHeight="34.0" prefWidth="123.0" text="Bikes" textFill="#a48989">


</JFXButton>
<JFXButton fx:id="carsBtn" layoutX="10.0" layoutY="415.0" onAction="#onCarsclick"
prefHeight="34.0" prefWidth="123.0" text="Cars" textFill="#a48989">


</JFXButton>
<JFXButton fx:id="logoutBtn" layoutX="9.0" layoutY="458.0" onAction="#onLogoutClick"
prefHeight="34.0" prefWidth="123.0" text=" Logout" textFill="#a48989">


</JFXButton>
<Line fx:id="lineaa" endX="100.0" layoutX="31.0" layoutY="517.0" startX="-13.5"
stroke="WHITE" />
<JFXButton fx:id="contactusBtn" layoutX="20.0" layoutY="542.0"
onAction="#onContactusClick" prefHeight="27.0" prefWidth="104.0" style="-fx-border-
color: white;" text="CONTACT US" textFill="WHITE" />
<image>
</image>
</ImageView>
59
<Label fx:id="bikesCountLbl" alignment="CENTER" layoutX="104.0" layoutY="381.0"

prefHeight="20.0" prefWidth="29.0" style="-fx-background-color: #2196f3;" text="0"
textFill="WHITE" />
<Label fx:id="carsCountlbl" alignment="CENTER" layoutX="103.0" layoutY="422.0"
textFill="WHITE" />
</children>
</Pane>
<Pane layoutX="131.0" prefHeight="76.0" prefWidth="541.0" style="-fx-background-
color: #2f2b43;">
<children>
<Label fx:id="topWelcomelabel" layoutX="45.0" layoutY="15.0" prefHeight="47.0"
prefWidth="486.0" textFill="#ddd0d0">


</Label>
</children>
</Pane>
<AnchorPane layoutX="147.0" layoutY="75.0" prefHeight="526.0" prefWidth="517.0">
<children>
<ImageView fitHeight="334.0" fitWidth="523.0" layoutX="4.0" opacity="0.37"
<image>
<Image url="@bike1.jpg" />
</image>
<effect>
<BoxBlur />
</effect>
</ImageView>
60

<image>
<Image url="@car5.jpg" />
</image>
<effect>
<BoxBlur />
</effect>
</ImageView>
<Pane layoutX="152.0" layoutY="172.0" opacity="0.32" prefHeight="208.0"
prefWidth="221.0" style="-fx-background-color: #2f2b43; -fx-border-color: white;">
<children>
<JFXButton fx:id="carBtn" layoutX="31.0" layoutY="113.0" onAction="#onCarBtnClick"
prefHeight="69.0" prefWidth="163.0" style="-fx-background-color: #2f2b43; -fx-border-
color: white;" text="Cars" textFill="WHITE">


</JFXButton>
<JFXButton fx:id="bikesBtn" layoutX="31.0" layoutY="27.0" onAction="#onBikeeClick"
prefHeight="69.0" prefWidth="163.0" style="-fx-background-color: #2f2b43; -fx-border-
color: white;" text="Bikes" textFill="WHITE">


</JFXButton>
</children>
</Pane>
</children>
</AnchorPane>
</children>
61
</AnchorPane>
14.1.3 UI Code for Bike Company selection module :
<?import javafx.geometry.Insets?>
<?import javafx.scene.control.Separator?>
<?import javafx.scene.control.TableColumn?>
<?import javafx.scene.control.TableView?>
<?import javafx.scene.layout.HBox?>
<?import javafx.scene.layout.Pane?>
<AnchorPane id="AnchorPane" prefHeight="600.0" prefWidth="800.0" style="-fx-

background-color: #2f2b43;" styleClass="mainFxmlClass"
fx:controller="BikesController">
<stylesheets>
<URL value="@bikes.css" />
</stylesheets>
<children>
62
<Pane layoutX="24.0" layoutY="24.0" prefHeight="570.0" prefWidth="174.0"

AnchorPane.bottomAnchor="15.0" AnchorPane.leftAnchor="15.0"
AnchorPane.topAnchor="15.0">
<children>
<Label fx:id="motolbl" layoutX="5.0" layoutY="103.0" prefHeight="40.0"
prefWidth="72.0" text="Moto" textFill="#2196f3">


</Label>
<Label fx:id="reviewlbl" layoutX="75.0" layoutY="99.0" prefHeight="50.0"
prefWidth="93.0" text="Review" textFill="#a7b5bf">


</Label>
<Label fx:id="factlbl" layoutX="-11.0" layoutY="193.0" prefHeight="25.0"
prefWidth="44.0" text="Fact :" textFill="#c3b1b1">


</Label>
<Label fx:id="boyslbl" layoutX="-11.0" layoutY="217.0" prefHeight="25.0"
prefWidth="174.0" text=""Boys loves their self earned" textFill="#c3b1b1">



</Label>
<Label fx:id="bikelbl" layoutX="-5.0" layoutY="232.0" prefHeight="33.0"
prefWidth="174.0" text="bike more than a girl"" textFill="#c3b1b1">

63



</Label>
<JFXButton fx:id="homebtn" layoutX="16.0" layoutY="337.0" onAction="#onHomeClick"
prefHeight="34.0" prefWidth="123.0" text="Home" textFill="#a48989">


</JFXButton>
<JFXButton fx:id="carbtn" layoutX="13.0" layoutY="373.0" onAction="#onCarClick"
prefHeight="34.0" prefWidth="123.0" text="Cars" textFill="#a48989">


</JFXButton>
<JFXButton fx:id="logoutBtn" layoutX="13.0" layoutY="409.0"
onAction="#onLogoutClick" prefHeight="34.0" prefWidth="123.0" text=" Logout"
textFill="#a48989">


</JFXButton>
<Line fx:id="line2" endX="100.0" layoutX="34.0" layoutY="490.0" startX="-13.5"
stroke="WHITE" />
<JFXButton fx:id="contactusBtn" layoutX="24.0" layoutY="518.0"
onAction="#onContactUsClick" prefHeight="27.0" prefWidth="104.0" style="-fx-border-
color: white;" text="CONTACT US" textFill="WHITE" />
<Label fx:id="totalCarCountLbl" alignment="CENTER" layoutX="107.0" layoutY="382.0"
textFill="WHITE">

64


</Label>
<ImageView fitHeight="145.0" fitWidth="135.0" layoutX="17.0" layoutY="-16.0"
<image>
<Image url="@motorcycle_icon.png" />
</image>
</ImageView>
</children>
</Pane>
<TableView fx:id="bikeCompanyTableView" layoutX="219.0" layoutY="83.0"
prefHeight="440.0" prefWidth="389.0">
<columns>
<TableColumn id="tbleView" fx:id="bikeNo" prefWidth="121.0" text="No." />
<TableColumn id="tbleView" fx:id="BikeComapnyName" prefWidth="266.0"
text="MotorBike Company" />
</columns>
</TableView>
<HBox layoutX="220.0" layoutY="541.0" prefHeight="51.0" prefWidth="396.0">
<opaqueInsets>
<Insets />
</opaqueInsets>
<children>
<JFXTextField id="txtField" fx:id="searchCompanyNameTxtField"
onAction="#onSearchClick" prefHeight="25.0" prefWidth="328.0" promptText="Search
Company Name">
<HBox.margin>
<Insets bottom="10.0" left="5.0" top="10.0" />
</HBox.margin>
</JFXTextField>
65
<JFXButton fx:id="searchbtn" accessibleRole="IMAGE_VIEW" buttonType="RAISED"

contentDisplay="GRAPHIC_ONLY" onAction="#onSearchClick" prefHeight="33.0"
prefWidth="30.0" style="-fx-background-color: #2196f3;" text="." textFill="#2196f3">
<HBox.margin>
<Insets bottom="8.0" left="8.0" right="8.0" top="8.0" />
</HBox.margin>


<graphic>
<ImageView fx:id="searchImage" fitHeight="20.0" fitWidth="32.0" pickOnBounds="true"
preserveRatio="true">
<image>
<Image url="@../LogoMakr_10mHaU.png" />
</image>
</ImageView>
</graphic>
</JFXButton>
</children>
</HBox>
<Label fx:id="mbLabl" layoutX="221.0" layoutY="25.0" prefHeight="51.0"
prefWidth="285.0" text="MotorBike Company List :" textFill="#b8a7a7">


</Label>
<Label fx:id="addcompanyLabl" layoutX="626.0" layoutY="83.0" prefHeight="40.0"
prefWidth="161.0" text="Add a New Bike Company :" textFill="#bfb3b3" />
<JFXTextField id="txtField" fx:id="addCarNoTxtField" layoutX="632.0" layoutY="136.0"
promptText="No." unFocusColor="#bca2a2" />
66
<JFXTextField id="txtField" fx:id="addCompanyNameTxtField" layoutX="632.0"

layoutY="167.0" promptText="Comapny Name" unFocusColor="#b9b0b0" />
<JFXButton fx:id="addCarCompanyBtn" layoutX="655.0" layoutY="226.0"
onAction="#onAddClick" prefHeight="27.0" prefWidth="79.0" style="-fx-background-
color: #2196f3;" text="Add" textFill="WHITE">


</JFXButton>
<Label fx:id="toLbl" layoutX="625.0" layoutY="277.0" prefHeight="34.0"
prefWidth="174.0" text="To remove any company " textFill="#bfb3b3" />
<Label fx:id="selectlbl" layoutX="626.0" layoutY="297.0" prefHeight="34.0"
prefWidth="174.0" text="select company name from" textFill="#bfb3b3" />
<Label fx:id="tableLbl" layoutX="626.0" layoutY="316.0" prefHeight="34.0"
prefWidth="174.0" text="table and press remove button." textFill="#bfb3b3" />
<JFXButton fx:id="removeBtn" layoutX="659.0" layoutY="368.0"
onAction="#onRemoveClick" prefHeight="27.0" prefWidth="79.0" style="-fx-background-
color: #2196f3;" text="Remove" textFill="WHITE">


</JFXButton>
<Separator fx:id="seprator" layoutX="204.0" layoutY="8.0" opacity="0.43"
orientation="VERTICAL" prefHeight="588.0" prefWidth="0.0" />
stroke="#fcfcfc" />
<JFXButton fx:id="refreshBtn" layoutX="660.0" layoutY="417.0"
onAction="#onRefreshClick" prefHeight="27.0" prefWidth="79.0" style="-fx-background-
color: #2196f3;" text="Refresh" textFill="WHITE">

67

</JFXButton>
<JFXButton fx:id="detailsBtn1" layoutX="660.0" layoutY="465.0"
onAction="#onDetailsClick" prefHeight="27.0" prefWidth="79.0" style="-fx-background-
color: #2196f3;" text="Details" textFill="WHITE">


</JFXButton>
</children>
</AnchorPane>
14.1.4 UI code for registration :
<?import com.jfoenix.controls.JFXPasswordField?>
<?import com.jfoenix.controls.JFXRadioButton?>
<?import javafx.scene.control.ToggleGroup?>
<AnchorPane id="AnchorPane" prefHeight="515.0" prefWidth="426.0" style="-fx-

background-color: #2f2b43;" styleClass="mainFxmlClass"
68
fx:controller="RegisterController">
<stylesheets>
<URL value="@register.css" />
</stylesheets>
<children>
<JFXTextField id="txtField" fx:id="emailIdTxtField" focusColor="WHITE"
labelFloat="true" layoutX="73.0" layoutY="181.0" prefHeight="39.0" prefWidth="288.0"
promptText="EmailId" stylesheets="@register.css" unFocusColor="#9a8a8a"
AnchorPane.rightAnchor="65.0" AnchorPane.topAnchor="181.0" />
<JFXRadioButton fx:id="maleRadio" layoutX="56.0" layoutY="275.0" selected="true"
text="Male" textFill="#b9a9a9" AnchorPane.bottomAnchor="223.0"
AnchorPane.leftAnchor="56.0" AnchorPane.rightAnchor="291.0"
<toggleGroup>
<ToggleGroup fx:id="gender" />
</toggleGroup>
</JFXRadioButton>
<JFXRadioButton fx:id="femaleRadio" layoutX="141.0" layoutY="275.0" text="Female"
textFill="#a19191" toggleGroup="$gender" AnchorPane.bottomAnchor="223.0"


</JFXRadioButton>
<JFXTextField id="txtField" fx:id="cityTxtField" focusColor="WHITE" labelFloat="true"
layoutX="74.0" layoutY="335.0" prefHeight="27.0" prefWidth="275.0"
promptText="Enter your city" stylesheets="@register.css" unFocusColor="#978585"
69
<JFXButton fx:id="signUpBtn" layoutX="135.0" layoutY="451.0"
onAction="#onSignUpClick" prefHeight="39.0" prefWidth="134.0" style="-fx-
background-color: #2196f3;" text="Sign Up" textFill="WHITE"
<JFXPasswordField id="txtField" fx:id="pwdTextField" focusColor="WHITE"
labelFloat="true" layoutX="72.0" layoutY="225.0" prefHeight="39.0" prefWidth="288.0"
promptText="Enter Password" stylesheets="@register.css" unFocusColor="#908686"
<JFXTextField id="txtField" fx:id="mobTextField" focusColor="WHITE" labelFloat="true"
promptText="Enter mobile number" stylesheets="@register.css"
unFocusColor="#978585" AnchorPane.bottomAnchor="129.0"
AnchorPane.topAnchor="393.0" />
text="Moto" textFill="#2196f3">


</Label>
text="Review" textFill="#a7b5bf">


</Label>
70

<image>
<Image url="@../LogoMakr_9Tx3RH.png" />
</image>
</ImageView>
<image>
<Image url="@../LogoMakr_9bo1Ux.png" />
</image>
</ImageView>
<ImageView fx:id="genderImage" fitHeight="33.0" fitWidth="36.0" layoutX="26.0"
layoutY="283.0" opacity="0.59" pickOnBounds="true" preserveRatio="true">
<image>
<Image url="/LogoMakr_7K8dsa.png" />
</image>
</ImageView>
<JFXRadioButton fx:id="otherRadio" layoutX="240.0" layoutY="293.0" text="Other"
textFill="#a49595" toggleGroup="$gender">


</JFXRadioButton>
<JFXButton fx:id="backButton" layoutX="327.0" layoutY="503.0"
onAction="#onBackClick" prefHeight="25.0" prefWidth="79.0" text="Back"
textFill="#a79595" />
<ImageView fx:id="phoneImg" fitHeight="27.0" fitWidth="27.0" layoutX="30.0"
layoutY="396.0" opacity="0.59" pickOnBounds="true" preserveRatio="true">
<image>
<Image url="@LogoMakr_4Uo0sV.png" />
71
</image>
</ImageView>
<image>
<Image url="@location.png" />
</image>
</ImageView>
<image>
</image>
</ImageView>
<JFXTextField id="txtField" fx:id="nameTxtField" focusColor="WHITE" labelFloat="true"
promptText="Name" stylesheets="@register.css" unFocusColor="#9a8a8a" />
<image>
<Image url="@../LogoMakr_9Tx3RH.png" />
</image>
</ImageView>
</children>
</AnchorPane>

MotoReview Report Kripal

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

MotoReview Report Kripal

Hochgeladen von

Copyright:

Verfügbare Formate

1

BIKES AND CARS DATA MANAGER

for the Partial fulfilment of the award of

Under the Guidance of : Submitted by:

Mr. Siddharth Mukherji Kripal Singh Rajawat

Department of Information Technology & Computer Application

JECRC UNIVERSITY, JAIPUR

in Deptt. of Information Technology , JECRC University is a record of my own investigations

carried under the Guidance of Mr. Siddharth Mukherji.

Name of Candidate: Kripal Singh Rajawat

Enrolment No.: 16BCAN062

7.2 Test Plan

13.7 Car Company section

Cars company module :

Bikes company module :

3.1 HARDWARE SPECIFICATION

CPU : Intel Core i3

Mouse : Logitech mouse

Keyboard : 104 Keys

Mother Board : Intel

Speed : 3.3 GHZ

3.2 SOFTWARE SPECIFICATION

Operating System : Platform Independent

Front End : JAVAFX, FXML, CSS

Back End : JAVA, Oracle Database.

Reports : Data Report

Tools : NetBeans (Smarter way to code)

4.1 NetBeans IDE 8.2 (Smarter way to code)

 Best Support for Latest Java Technologies

 Fast & Smart Code Editing

 Easy & Efficient Project Management

 Rapid User Interface Development

 Bug Free Code

 Support for Multiple Languages

 Language cross platform support

4.2 FEATURES OF FXML :

4.3.1 Features of FXML :

 FXML focuses on data rather than how it looks

 Easy and efficient data sharing

 Compatibility with other markup language HTML

 Supports platform transition

 Allows FXML validation

 Adapts technology advancements

 FXML supports Unicode

4.3.2 Scene Builder :

 A drag-and-drop WYSIWIG interface.

 Tight integration with the NetBeans IDE.

 Integration with any Java IDE is easy.

 Live editing and preview features.

5. SYSTEM DESIGN AND DEVELOPMENT

5.1 FILE DESIGN :

5.2 Relational File Database :

5.3 INPUT DESIGN

5.4 OUTPUT DESIGN

Graphics are digital representations of non-text information such as drawings, charts,

5.5 DATABASE DESIGN

Database is designed to manage large bodies of information. The management of data

 Defining the data

Objectives of Database design

In database design several objectives are designed such as:

Each table may represent an implementation of either a logical object or a relationship

5.6 DATAFLOW DIAGRAM

Data Flow Diagram Symbols

- Source or Destination of data