USED CAR SALE
DATABASE
GROUP MEMBERS
ANKIT RAJ
ASHWANI KUMAR
ANAND ABHISHEK
SUBMITTEDTO-
Dr RENUMOLV G
 FUNCTIONAL REQUIREMENTS
 NON FUNCTIONAL REQUIREMENTS
 GOALS OF IMPLEMENTATION
The objective of the “ USED CAR SALE ” is to provide better information
for the users of this system for better results for their maintenance in
the product details that is sales, purchases and stock.
 Simple System to learn with modules for Purchasing, Invoicing,
Preparation, Salesmen, Reporting,Customer Maintenance & Set-up
 Easy data entry through vehicle data look-up via vehicle registration
 Stock lists and advertising copy
 Preparation costs (internal and external)
 Invoicing function saves both customer & driver information
 A high quality purchase & sales invoices printed
 Customized car sale invoices, wordings, logos
 Invoicing & purchases process is easily amended in the
event of changes or errors
 Complete profit and loss analysis on every car sold
 Unlimited vehicle photographs
 Website Integration - have your stock displayed on your
website
S.NO FUNCTION
REQ
DESCRIPTI
ON
INPUT OUTPUT USED
1. LOGIN HOWTO
ENTER
NAME
/USER
ID/PHONE
NUMBER
ACCESS END USER
2. Permission
for
Administrat
ion to add
the data
System shall
allow the
administrat
or to add
the data
Add data
includes:
Car name,
Car
information
and Car
image
gallery.
CAR
DETAILS
END USER
3. CAR
SEARCH
Students
will be able
to search
for Cars.
Search will
be based on
exactly
matched
keywords.
CAR
DETAILS
END USER
4. CAR
GALLERY
Few images
of each Car
will be given
in a gallery
tab in each
Cars
section.
CLICK ON
THE IMAGE
CAR
DETAILS
END USER
5. PRICE
PRODUCT
Price of the
car shown
Product id,
Max retail
Price, Bill
no
Amount
Paid
End User
6. PURCHASE
_BILL
Purchasing
details
Purchasing
agency id,
agency
bill,Purchas
e
date,contac
t person
Bill End User
S.NO Non- FUNCTION REQ DESCRIPTION
1 Performance average load time of the
starting page of the
system will be less than 5
second (Since it would be
an online system, its speed
will also depend on
administrator‟s internet
speed)
2 User Interface It will be attractive.
3 Secure Login and
Database
Database and Login will be
made secure by using
private variables.Single
user will not be allowed to
make multiple accounts of
same id
4 Maintenance Maintenance is an ongoing
process, it will continue
even after the deployment
of the system.
5 Documentation Administrator will be
provided with all the
documentation in PDF
format.
6 Under-maintenance Page Under maintenance page
will be shown when the
system will be under
7 SECURITY Maintain user information
confidentiality.
To select an ideal methodology was based on
project requirements and goals.
 Functional Decomposition: The methodology should have stages
according to the interrelated activities which can be grouped into
different functional areas.
 Requirement Changes: If required, methodology provides scope to
change the requirement.
 Manage Risks: Determined the risk is an important activity to develop a
project.
 Iterative approach: Iteration allows refinement of requirement as well
as design.
 Documentation: Methodology provides support for large
documentation.
 Analysis and Design Support: A well-defined structure of the
methodology helps for analysis and designing to development
process..
 Implementation: The system should be implemented as per plan.
 Testing Support: More testing, more reliable the product is.
 Object Oriented Approach: Object oriented concepts will be used
in developing the project as it supports component reusability.
 Presentation on Used Car

Presentation on Used Car

  • 1.
    USED CAR SALE DATABASE GROUPMEMBERS ANKIT RAJ ASHWANI KUMAR ANAND ABHISHEK SUBMITTEDTO- Dr RENUMOLV G
  • 2.
     FUNCTIONAL REQUIREMENTS NON FUNCTIONAL REQUIREMENTS  GOALS OF IMPLEMENTATION
  • 3.
    The objective ofthe “ USED CAR SALE ” is to provide better information for the users of this system for better results for their maintenance in the product details that is sales, purchases and stock.  Simple System to learn with modules for Purchasing, Invoicing, Preparation, Salesmen, Reporting,Customer Maintenance & Set-up  Easy data entry through vehicle data look-up via vehicle registration  Stock lists and advertising copy  Preparation costs (internal and external)  Invoicing function saves both customer & driver information
  • 4.
     A highquality purchase & sales invoices printed  Customized car sale invoices, wordings, logos  Invoicing & purchases process is easily amended in the event of changes or errors  Complete profit and loss analysis on every car sold  Unlimited vehicle photographs  Website Integration - have your stock displayed on your website
  • 6.
    S.NO FUNCTION REQ DESCRIPTI ON INPUT OUTPUTUSED 1. LOGIN HOWTO ENTER NAME /USER ID/PHONE NUMBER ACCESS END USER 2. Permission for Administrat ion to add the data System shall allow the administrat or to add the data Add data includes: Car name, Car information and Car image gallery. CAR DETAILS END USER
  • 7.
    3. CAR SEARCH Students will beable to search for Cars. Search will be based on exactly matched keywords. CAR DETAILS END USER 4. CAR GALLERY Few images of each Car will be given in a gallery tab in each Cars section. CLICK ON THE IMAGE CAR DETAILS END USER
  • 8.
    5. PRICE PRODUCT Price ofthe car shown Product id, Max retail Price, Bill no Amount Paid End User 6. PURCHASE _BILL Purchasing details Purchasing agency id, agency bill,Purchas e date,contac t person Bill End User
  • 9.
    S.NO Non- FUNCTIONREQ DESCRIPTION 1 Performance average load time of the starting page of the system will be less than 5 second (Since it would be an online system, its speed will also depend on administrator‟s internet speed)
  • 10.
    2 User InterfaceIt will be attractive. 3 Secure Login and Database Database and Login will be made secure by using private variables.Single user will not be allowed to make multiple accounts of same id 4 Maintenance Maintenance is an ongoing process, it will continue even after the deployment of the system.
  • 11.
    5 Documentation Administratorwill be provided with all the documentation in PDF format. 6 Under-maintenance Page Under maintenance page will be shown when the system will be under 7 SECURITY Maintain user information confidentiality.
  • 12.
    To select anideal methodology was based on project requirements and goals.  Functional Decomposition: The methodology should have stages according to the interrelated activities which can be grouped into different functional areas.  Requirement Changes: If required, methodology provides scope to change the requirement.  Manage Risks: Determined the risk is an important activity to develop a project.  Iterative approach: Iteration allows refinement of requirement as well as design.
  • 13.
     Documentation: Methodologyprovides support for large documentation.  Analysis and Design Support: A well-defined structure of the methodology helps for analysis and designing to development process..  Implementation: The system should be implemented as per plan.  Testing Support: More testing, more reliable the product is.  Object Oriented Approach: Object oriented concepts will be used in developing the project as it supports component reusability.