SE File

Download as pdf or txt
Download as pdf or txt
You are on page 1of 24

EXPERIMENT NO – 2

AIM: - Problem Statement of a Case Study Project

Problem Statement :

Hiring a cab or getting a car ride for far-across travel places has
always been a massive issue in Indian society. If abandoned in the
middle of the road, you have the option to walk to your destination.
But, it will be physically draining. How would you feel if your taxi driver
suddenly renegotiates the fare and when you say no the driver leaves
you grounded in the middle of nowhere? Traumatic experience right?

There are people who generally don’t prefer to travel in public transport
like busses, trains due to the crowd , safety issues and many more
genuine reasons , also if you are not a resident in a particular city then
Ola cab is the best option for travelling .

Solution:

Ola cabs need no introduction. It is India’s first car aggregator


company providing the best taxi services at the lowest fares and
makes it easy for you to book/rent a cab.

Ola Cabs is on a mission to build a smooth mobility system for billions


of people. Its preeminent aim is to provide the best car-riding
experience with no fuss.

The car aggregator company connects and partners with drivers and
taxi drivers to bring a modern change with the help of technology.

EN20CS301220 KISHKIN JOSHI


EXPERIMENT NO – 3

AIM: - Entity-Relationship Diagram of a Case Study

Entities: -
1. Customer
2. Driver
3. Cab
4. Bill
Attributes: -
1. Customer (Cust_id, Cust_name, Cust_phone, pickup_location , drop_location)
2. Driver(D_id , D_name , D_phone )
3. Cab(cab_no , cab_image , cab_model)
4. Bill (Bill_no, Bill_date, Bill_amt,Bill_tax)

EN20CS301220 KISHKIN JOSHI


Relationship – Cardinality: -
1. One Customer books one cab
2. One Customer pays one Bill
3. One Cab generates many Bookings.
4. One driver drives one cab.
5. One Driver takes one booking.

Primary Keys: -
1. Cab: - Cab_No
2. Customer: - Cust_id
3. Bill: - Bill_no
4. Driver : D_id
Foreign Keys: -
1. Cab : Cab_id
2. Driver : D_id

EN20CS301220 KISHKIN JOSHI


EXPERIMENT NO – 4

AIM: - Use Case Diagram of a Case Study Project

EN20CS301220 KISHKIN JOSHI


Use Cases: -
1. Login
2. Search Cab
3. Select Cab
4. Availability of Cabs
5. Cancel Booking
6. View Cab status
7. Generate Bill
8. Bill Payment

Primary Actors: -
1. Admin
2. Customer
3. Driver
Relationships: -
1. Extend: -
Dependency of one use case on another use case.
Here, VIP booking and normal booking extends booking
2. Generalization: -
Generalization is shown in Bill Payment where there are 3 options: -
 Pay With Cash
 Pay With UPI

EN20CS301220 KISHKIN JOSHI


EXPERIMENT NO – 5

AIM: - Data Flow Diagram of a Case Study Project


1. Level – 0 Data Flow Diagram: -

External Entities–
1. Customer
2. Admin
3. Driver

Process -
1. Car Booking Management System

Data Flow-:
2. Customer Orders Car
3. The Car Order is sent to Admin
4. Admin checks for available drivers nearby
5. Driver accepts booking
6. Invoice is sent to customer

EN20CS301220 KISHKIN JOSHI


2. Level – 1 Data Flow Diagram: -

External Entities–:
1. Customer
2. Admin
3. Driver

Process–:
1. Manage Customer Information
2. Manage Car Information
3. Monitor Car Details
4. Manage Transactions
5. Manage Driver Information

Data Store – :
1. Customer Database
2. Car Database
3. Transaction Database
4. Driver Database

EN20CS301220 KISHKIN JOSHI


Data Flow –
1. Customer Information
2. Categories List
3. Car Categories
4. Car Details
5. Car Chosen
6. Transaction Details
7. Driver Information
8. Driver List

3. Level – 2 Data Flow Diagram: -


 Customer Information Management: -

Process-:
1. Display Customer Information
2. Validates/ Process Customer Information

Data Store-:
1. Customer Info

EN20CS301220 KISHKIN JOSHI


Data Flow-:
2. Access Customer Information
3. Retrieve Customer Info
4. Enter/Update/Delete Customer Info

 Cab Information Management: -

Process-:
1. Display Cab Information
2. Validates/ Process Cab Information

Data Store-:
1. Cab Info

Data Flow-:
2. Access Cab Information
3. Retrieve Cab Info
4. Enter/ Update / Delete Cab Info

EN20CS301220 KISHKIN JOSHI


 Driver Information Management: -

Process-:
3. Display Driver Information
4. Validates/ Process Driver Information

Data Store-:
5. Driver Info

Data Flow-:
6. Access Driver Information
7. Retrieve Driver Info
8. Enter / Update / Delete Driver Info

EN20CS301220 KISHKIN JOSHI


EXPERIMENT NO – 6

AIM: - Activity Diagram of a Case Study Project

EN20CS301220 KISHKIN JOSHI


Action State / Activity: -
1. Login
2. System Dashboard
3. Display Details
4. Cab Booking
5. Send Invoice
6. View Cab Info
7. View Customer Info
8. View Feedback
9. Vip Booking
10. Normal Booking
11. Make Payment
12. Receive Payment
13. Logout
Fork Operation: -
The System Dashboard is divided into: -
1. Display Details
2. Cab Booking
3. Send Invoice

Join Operation: -
Display Details, Cab Booking and Send Invoice are joined together into Logout action state.

EN20CS301220 KISHKIN JOSHI


EXPERIMENT NO – 7

AIM: - Swimlane Diagram of a Case Study Project

Department: -
The departments are: -
1. Admin
2. Customer
3. Finance

EN20CS301220 KISHKIN JOSHI


Action State: -
1. Login
2. Admin Login
3. Customer Login
4. Driver Login
5. System Dashboard
6. Receive Booking
7. View Feedback
8. Booking confirmed
9. Send Invoice
10. View / Search Cab
11. Order Cab
12. Receive Invoice
13. Payment
14. Net Banking
15. Pay with Cash
16. Pay with card
17. Logout

Fork Operation: -
The login action state is further divided into: -
1. Admin Login
2. Customer Login
3. Driver Login
The System Dashboard is divided into: -
1. View / Search Cab
2. Order Cab

EN20CS301220 KISHKIN JOSHI


EXPERIMENT NO – 8

AIM: - Sequence Diagram of a Case Study Project

Actor: -
The Actor here is Admin.
Lifeline: -
1. Sign Up
2. Login Process
3. Order Taxi
4. Ola Service
5. Database
Messages: -
EN20CS301220 KISHKIN JOSHI
a) Call Messages: -
1. Registration
2. Customer Registration
3. Click login ()
4. Verify Username and Password
5. Search Cab
6. Cab Details
7. Process for Forgot Password
8. Operation
9. Reserve Car
10. Operation
11. Cab Information
12. Operation
13. Request Logout

b) Return Messages: -
1. Acknowledgement of Registration
2. Confirm
3. Acknowledgement of Login
4. Login Failed
5. Acknowledgement
6. View Cab Details
7. Acknowledgement for Forgot Password
8. Acknowledgement
9. Successfully Booked Cab
10. Acknowledgement
11. View of Details
12. Successfully Logout

EN20CS301220 KISHKIN JOSHI


EXPERIMENT NO – 9

AIM: - Class Diagram of a Case Study Project


Class Diagram of Cab Booking System: -

EN20CS301220 KISHKIN JOSHI


Classes of Cab Booking Management System Class Diagram: -

1. Login: - Manages all the operations of Login


2. Customer: - Manages all the operations of Customer
3. Driver: - Manages all the operations of Driver
4. Cab: - Manages all the operations of Cab
5. Cab_booking: - Manages all the operations of Cab_booking
6. Inventory: - Manages all the operations of Inventory (Stores)
7. Bill: - Manages all the operations of Bill

Classes & their Attributes of Car Showroom Management System Class Diagram: -

1. Login: - username, password


2. Customer: - cust_id, cust_name, cust_address, cust_phone
3. Driver: - d_id, d_name
4. Cab: - c_id, c_name, c_dom, c_cost
5. Cab_booking: - id, cust_id, car_id, cust_name
6. Inventory: - c_count, c_brand
7. Bill: - bill_no, bill_amt, bill_date

Classes & their Operations(Methods) of Car Showroom Management System Class Diagram:-

1. Login: - validate()
2. Customer: - login(), send_order(), receive_order(), search_car(), cancel()
3. Driver - login(), maintain(), view_report(), generate_bill()
4. Cab: - view_cab(), update_cab(), register_cab(), cancel_cab()
5. Cab_booking: - select_cab(), book_cab()
6. Inventory: - search(), check()
7. Bill: - view_bill(), pay_bill(), cancel_pay()

EN20CS301220 KISHKIN JOSHI


EXPERIMENT NO – 10

AIM: - Component Diagram of a Case Study Project

Components: -
1. Car
2. Customer
3. Employee
4. Car_Booking
5. Inventory
6. Sales
7. Security
8. Persistence
9. Database
Interface: - System Admin
EN20CS301220 KISHKIN JOSHI
Features Of Car Showroom Management System Component Diagram: -
1. Model the components of Car Showroom Management System.
2. Model the database schema.
3. Model the executables of an application.
4. Model the system’s source code.

EN20CS301220 KISHKIN JOSHI


EXPERIMENT NO – 11

AIM: - Study of various testing tools


Software Testing Tools: -
Software Testing tools are the tools which are used for the testing of software. Software
testing tools are often used to assure firmness, thoroughness and performance in testing
software products. Unit testing and subsequent integration testing can be performed by
software testing tools. These tools are used to fulfill all the requirements of planned
testing activities. These tools also work as commercial software testing tools. The quality
of the software is evaluated by software testers with the help of various testing tools.
Types of Testing Tools: -
As software testing is of two types, static testing, and dynamic testing. Also, the tools
used during these testing are named accordingly on these testing. Testing tools can be
categorized into two types which are as follows:
1. Static Test Tools: -
Static test tools are used to work on the static testing processes. In the testing through
these tools, typical approach is taken. These tools do not test the real execution of the
software. Certain input and output are not required in these tools.
1. Dynamic Test Tools: -
Dynamic testing process is performed by the dynamic test tools. These tools test the
software with existing or current data
The software testing tools are as follows: -

 Test management tool


 Bug tracking tool
 Automated testing tool
 Performance testing tool
 Cross-browser testing tool
 Integration testing tool
 Unit testing tool
 Mobile/android testing tool
 GUI testing tool
 Security testing tool

1. Bug Tracking Tool: -


The defect tracking tool is used to keep track of the bug fixes and ensure the delivery
of a quality product. This tool can help us to find the bugs in the testing stage so that
we can get the defect-free data in the production server. With the help of these tools,
the end-users can allow reporting the bugs and issues directly on their applications.

EN20CS301220 KISHKIN JOSHI


2. Automation Testing Tool: -
This type of tool is used to enhance the productivity of the product and improve the
accuracy. We can reduce the time and cost of the application by writing some test
scripts in any programming language.
3. Performance Testing Tool: -
Performance or Load testing tools are used to check the load, stability, and scalability
of the application. When n-number of the users using the application at the same time,
and if the application gets crashed because of the immense load, to get through this
type of issue, we need load testing tools.
4. Cross-Browser Testing Tool: -
This type of tool is used when we need to compare a web application in the various
web browser platforms. It is an important part when we are developing a project. With
the help of these tools, we will ensure the consistent behaviour of the application in
multiple devices, browsers, and platforms.
5. Integration Testing Tool: -
This type of tool is used to test the interface between modules and find the critical
bugs that are happened because of the different modules and ensuring that all the
modules are working as per the client requirements.
6. Unit Testing Tool: -
This testing tool is used to help the programmers to improve their code quality, and
with the help of these tools, they can reduce the time of code and the overall cost of
the software.
7. Mobile/Android Testing Tool: -
We can use this type of tool when we are testing any mobile application. Some of the
tools are open-source, and some of the tools are licensed. Each tool has its
functionality and features.
8. GUI Testing Tool: -
GUI testing tool is used to test the User interface of the application because a proper
GUI (graphical user interface) is always useful to grab the user's attention. These
types of tools will help to find the loopholes in the application's design and makes its
better.

9. Security Testing Tool: -


The security testing tool is used to ensure the security of the software and check for
the security leakage. If any security loophole is there, it could be fixed at the early
stage of the product. We need this type of the tool when the software has encoded the
security code which is not accessible by the unauthorized users.

EN20CS301220 KISHKIN JOSHI


Types of Tools:

S.No. Tool Type Used for Used by

1. Test Management Tool Test Managing, scheduling, defect testers


logging, tracking and analysis.

2. Configuration For Implementation, execution, All Team


management tool tracking changes members

3. Static Analysis Tools Static Testing Developers

4. Test data Preparation Analysis and Design, Test data Testers


Tools generation

5. Test Execution Tools Implementation, Execution Testers

6. Test Comparators Comparing expected and actual results All Team


members

7. Coverage measurement Provides structural coverage Developers


tools

8. Performance Testing Monitoring the performance, response Testers


tools time

9. Project planning and For Planning Project


Tracking Tools Managers

10. Incident Management For managing the tests Testers


Tools

EN20CS301220 KISHKIN JOSHI


EN20CS301220 KISHKIN JOSHI

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy