To reverse engineer software artifacts from user interfaces

1. Reverse Software
Engineering
Case Study
UBER/CREAM/Rent a Ride APP

6. Other
User
interface

7. Requirements
• This application will provide services to passengers and drivers. Ride Service Management System
(RSMS) connects passengers and drivers using GPS system. Everyone who has any type of vehicle
can register on this application. This app will support all type of vehicles. This application enables
passengers to order any kind of vehicle with their Smartphone. The main objective of this
application is that drivers online register their vehicles by providing their essential information and
then check their nearest pick and drop.
• The project has two parts, the first one is an application run on android device and the second one
is server on Nosql database. Android section will have two applications. One is master refers to
driver and other one is client refers to passengers.
• If the driver accepts booking then the server will send order confirmation to the passenger
application
• This application is managing passengers’ booking in quick and easy way with shortest time
possible. With one click on the button you can order a vehicle if you are a passenger. With another
click you accept or decline requests if you are a driver. No third party to be added to control this
work.
• Some types of vehicles still don‟t have any online ride service. But with this application, any type
of vehicle can register. This app will support all type of vehicles. This app will run in all cities. All
vehicle drivers can register and earn money using this app without any limitation. This service will
not have any central office.

8. Functional Requirements
• The Application must have a logo at the start of application.
• Every online booking needs to be associated with an account
• One account cannot be associated with multiple user.
• Search results should enable users to find the most recent and relevant
booking rides options.
• System should enable users to book / pay for their rides only in cash or
credit card.
• The application shall keep track of all processes and changes happening to
the data between login and logout times of the users.
• The application should enable the users to logout after using the
application when the user clicks on the logout button.

9. NON-Functional Requirements
Usability
• The Application should be easy to use by every user. In order to accomplish this objective, the system should have a simple and well-designed
interface.
Accessibility
• The Application should be made accessible to the people who live everywhere in the world. anyone can use the system regardless of the
location and can get the information they acquire.
Performance
• The performance of the application should be fast and efficient in adding information of drivers. The system should be available for user in real
time and always up to date.
Speed
• The application response time is a significant requirement because the action cannot be postponed or delayed. The application should be fast
enough to satisfy the user‟s needs and should not waste their time.
EFFICIENCY
• Efficiency of any system is concerned with the minimum processing time as well as the optimal use of system resources in designing the
proposed systems. Our android application will be efficient in using processing resources. It can be efficiently run on all android devices.
Availability
• The Application should operate 24 hours a day.
Friendly GUI’s
• The users of this application have different types of people and different levels of technical skills, therefore the application should be
understandable by all the users. Consequently, the Application should provide an easy to use, friendly Graphical User Interface (GUI).

10. User Functions Model
General User should
• Interact with the application
• Be able to login to their accounts
using their email and password
provided
• Be able to logout from their profiles.
Admin should
• Be able to add, delete and modify
database
• Be able to add and remove users and
set authority
• Be able to monitor the system
Admin-Managers should
Be able to view all drivers
Be able to view the list of customers
Be able to view all the customer
request
Be able to view all workers available
Be able to create, edit and delete
information
Be able to search for information
Be able to notice the editing‟s and
changes made by the users.

11. DFD Level-1
Book a
Ride
Cancel a
Ride
Pickup
Feedback
Payment
Passenger
Driver
Uber Admin
Driver
Registration
destination
Destination
request
Offer Available rides
Coordinates
Amount
Comments Type &
Payment
details Accept Ride
Driver &
Vehicle Details
Driver
Approval &
Passenger
Star Ratings
Overall
Ratings

13. Assignment
Search interfaces for a “Bargainable Ride Rent” App and construct
• Functional Requirements
• User based grouped functional requirements
• 2nd Level DFD of Book-a-Ride function
• EasyPaisa based payment Use Case Description
• User interface for EasyPaisa based payment and Star Rating
Deadline NEXT Class
• CHARTS of Individual User Interface Assignment