The document describes a car showroom management system project submitted by Muhammad Shoaib, Hamza Chaudhry, and Sheryar Abbasi. The project aims to develop a software application to help manage customers, sales, company inventory, and vehicle details for a luxury car dealership. Key features include online and manual booking of vehicles, searching vehicle information, updating or canceling orders, and admin functions like user registration, vehicle registration, and booking operations. Testing will use black-box testing methods like equivalence partitioning.

1. SE-1 PROJECT
Submit to: Sir Ghulam Mustafa

2. CAR SHOWROOM MANAGEMENT SYSTEM
 Group members:
 MUHAMMAD SHOAIB 16-ARID-1222
 HAMZA CHAUDHRY 16-ARID-1208
 SHERYAR ABBASI 16-ARID-1243

3. CAR SHOWROOM MANAGEMENT SYSTEM
 PROJECT SCOPE
 This project is developing for luxurious cars agent. It is easy to Maintain
Customers detail ,sales details ,company items and services cars detail .
 Car showroom Management System Project provides solution for
showrooms for organizing data using software application. This software
application helps administrator to update data in step by step process
while selling car to customer. Using this system management team can
update customers information, car information, payment details,
Insurance details, take orders..etc.

4. MODULES SYSTEM:
 User Module
• Car categories
• Booking
A. Online booking
B. Manual booking
• Search Vehicles
 Admin Module
• Registration
A. Admin Registration
B. User Registration
C. Car Registration
• Booking Operation
A. Booking Confirmation
B. Booking Cancellation

5. Model
 We use XP model in our project.
 When should Extreme Programming be Used?
o Extreme Programming (XP) was created in response to problem domains whose
requirements change. Your customers may not have a firm idea of what the system
should do. You may have a system whose functionality is expected to change every
few months. This is when XP will succeed while other methodologies do not.

6. Functional approach Requirements:
Cust0mer Functionalities
 Function name: recieve the car.
 Input : Selection of the car.
 Output: car can be delivered.
 Precondition:.selection of the car
 Postcondition: receive the car.
 Function name: view cars with details.
 Input : Selection of the car.
 Output: Details of the
car:Name,Model,cost,availability.
 Precondition:.open car module.
 Postcondition: detail should be provided to the
user.

7. Functional approach Requirements:
Cust0mer Functionalities
 Function name: Update/Cancel order.
 Input : cancel/update the order.
 Output: order cancellation/ updated notification.
Precondition:.open cancel/update module.
 Postcondition: order cancelled.

8. Functional approach Requirements:
System admin functionalities
 Function name: Log in with admin
.account.
 Input : Admin username and password.
 Output: Admin view of the system.
Precondition:.admin log in.
 Postcondition: view of system.
 Function name: Add new car/
car category.
 Input : enter car category details.
 Output: car category successfully added
notification.
Precondition:.new car exist in stock.
 Postcondition: view of car.

9. Functional approach Requirements:
System admin functionalities
 Function name: Remove car/ car category.
 Input : car remove request.
 Output: car removed notification.
Precondition:.login admin module.
 Postcondition: car removed notification.

10. Testing
 Strategy :Black-Box Testing is use
 Black Box Testing:
• Equivalence class partitioning:
Characteristic Valid equivalence class invalid equivalence class
First char must be
alphabetic
Letter Non-letter
Next three numerics All numeric One non numeric
Range 100-500 In range Above range
Below range
Equivalence class table for customer-account-number

11. Testing
 Test execution
 Example: Search and select the car
R-001:
The users should be able to search the car and select among them.
Use case:AC01 search and select the car
Actors: User
Purpose: user search and buy the car
Overview: The user search and select the car and
and then receive the car.
Cross References: R-001

12. Testing
 Typical Course of Events
Actor action System response
• The actor start the system and login. The
display screen appears.
• The actor search the car by clicking on the
keypad or keyboard
Car is displayed on the screen.
• Then actor selected the car by click on mouse. Car is selected.
• Actor click on buy button by mouse. Request for cash using credit card or cheque.

13. Test Case
Test Case ID: T-011 Test Item: Search And Buy Car
Wrote By: M.Shoaib Documented Date: 7th june 2018
Test Type: Manual
project Name: Car Showroom System Release And Version Num: V1.0
Test Case Description:
Search And Buy Car
Operation procedure:
Login
search car
select and buy
Pre-conditions: Post-conditions:
First login Check the receive car
Inputs data and/or events: Expected output data and/or events:
Search And select Car Receive The Car
Required test scripts (for auto): NA
Cross References: (Requirements or Use Cases) R-001, AC-01