Agenda of the Presentation

• Introduction of project
• Scope
• Functionalities
• User Goal
• Use Cases
• Use case Diagram
• Class Diagram
• Sequence Diagram
• ERD Diagram
• Activity Diagram
• Package Diagram
• Deployment Diagram
• Schedule
• Conclusion
1
Project Introduction
• Ride Share is a android application where
different features are combined so that it can
give users a platform that manages all the
activities related to Pre-booking rides to reach
out their destination.
• This application is basically for frequent
travelers but not for professionals.

2
 Scope
• You can Pre-book your ride for the inter-city traveling You
don’t need to travel to the terminals and get waited for
buses.
• In this application we are mainly targeting passenger and
vehicle owner.

3
What not to do

The purpose of this project is to develop an

android application , not a Web based
application.

4
Functionalities

5
 Functional Requirements for each
module on web
Registration
• user will be able to create his account on RideShare by using an
email, username and a password.
• user will be able to sign in using username and password.
• user will be able to update his account information.
• user will be able to delete his account from RideShare.
Find Ride
• Passenger will provide his/her Leaving and destination location.
• Passenger will enter his/her leaving date, time and required Seats.
• Available Rides will be displayed according to passenger’s
schedule.
• Passenger will select and confirm his/her ride.

6
 Functional Requirements CONT..
Offer Ride
• Car owner will add his/her car details e.g number plate , cnic,
license and car’s document
• Car owner will upload his/her CNIC, License front and back.
• Car owner will provide his/her Leaving and destination location .
• Car Owner can re-schedule the ride within time constraint.
• Car’s owner will confirm his/her ride.
• Car’s owner will cancel his/her ride if have some problem.
• Car’s owner will be charged extra if he/she cancel his/her ride in
last 24 hours before his ride start.

7
 Functional Requirements CONT..
Data Management
• Client and ride information will store in database.
• All information regarding passenger, car’s owner and ride transactions
will store in database.
• Updated information about car’s owner and passenger will be store in
database.
• Deleted information about car’s owner and passenger will be deleted
from database.

Payment
• Cash
Feedback
• The user will be able to give feedback about ride share .
8
 Non-Functional Requirements
• Performance requirements
The system will be easily maintained by the
developer or other authorized trained person and it
shall respond as fast as possible in generating report
and for performing the other functionalities

9
Contd.
• Start-up Time
Application will start in (5, 7) seconds but it
depends upon the internet connection because
it is an android application.
• Response Time:
Application response time should be fast so that
the information will be quickly seen within a
limited time

10
Contd.
• Workload:
System should be able to deal with at least 100 users
at the same time
• Safety and Security requirements
Security requirements are important factors in this
system as classified data will be stored in the database
User validation will be done during login to insure
that the user is valid and that the user only has access to his
or her permission data
General users will only have access through the user
interface.
Application will ensure that the data of customers
should not be compromised
11
Activity Diagram

12
Class Diagram

13
Use Case Diagram

14
ER Diagram

15
 Test Cases
Create Account:

Test Case ID TC001

Test Case Version Version 1.0
Functionality Create Account
Actor Unregister User
Pre-Condition Must have desktop application on their systems.
Input data Username , password ,cnic,mobile number.
Normal Flow Expected Result Actual Result (Pass/Fail)
User requests system for
The system creates the user
registration and system accepts Pass
account
request.
Alternative flow Expected result Actual Result (Pass/Fail)
Invalid user name, password,
Invalid entry Fail System requests to login
email
Date 5-11-2018

Test conducted by Abdul Wahab Nizam , Abubaker Mujahid , Mohammad Nouman Aslam

Test verified by Mr. Malik Adnan Jaleel

16
 Test Cases
Login:

Test Case ID TC002

Test Case Version Version 1.0
Functionality Login User
Actor App User
Pre-Condition User must have their account.
Input data Username , password
Normal Flow Expected Result Actual Result (Pass/Fail)

If the username and password

Request to login to the application. matches, then system login to Pass
the user account

Alternative flow Expected result Actual Result (Pass/Fail)

Invalid user name, password, Invalid user name, password,
Fail System requests to login
email email
Date 5-11-2018
Test conducted by Abdul Wahab Nizam , Abubaker Mujahid , Mohammad Nouman Aslam
Test verified by Mr. Malik Adnan Jaleel

17
 Test Cases
Add Route
Passenger:

Test Case ID TC003

Test Case Version Version 1.0
Functionality Add Route
Actor Passenger
Pre-Condition User must login to the application.
Input data Username , password
Normal Flow Expected Result Actual Result (Pass/Fail)
Passenger request to add route. The system will confirm that route
Pass
is added.
Alternative flow Expected result Actual Result (Pass/Fail)
Routes are not available Route not add. Fail
Date 5-11-2018

Test conducted by Abdul Wahab Nizam , Abubaker Mujahid , Mohammad Nouman Aslam

Test verified by Mr. Malik Adnan Jaleel

18
 Table 10 Add Route Owner

Test Cases
Add Route Owner:
Test Case ID TC005
Test Case Version Version 1.0
Functionality Add Route
Actor Owner

User must login to the application

Pre-Condition
Must have an car

Input data Username , password

Normal Flow Expected Result Actual Result (Pass/Fail)

Owner request to add route. System will add the route.

Pass

Alternative flow Expected result Actual Result (Pass/Fail)

User don’t have car. Route will not added. Fail
Date 5-11-2018

Abdul Wahab Nizam , Abubaker Mujahid , Mohammad Nouman

Test conducted by
Aslam
Test verified by Mr. Malik Adnan Jaleel

19
 Test Cases
Confirm Ride:

Test Case ID TC006

Test Case Version Version 1.0
Functionality Confirm Ride
Actor Owner , Passenger

Pre-Condition User must login to the application, identified and authenticated.

Input data Username , password

Normal Flow Expected Result Actual Result (Pass/Fail)

If routes are added then ride

User request to confirm ride.
will confirm. Pass

Alternative flow Expected result Actual Result (Pass/Fail)

Doesn’t have routes No ride will confirm Fail
Date 5-11-2018

Test conducted by Abdul Wahab Nizam , Abubaker Mujahid , Mohammad Nouman Aslam

Test verified by Mr. Malik Adnan Jaleel

20
 Test Cases
Cancel Ride:

Test Case ID TC007

Test Case Version Version 1.0
Functionality Cancel Ride
Actor Onwer , Passenger
Pre-Condition User must login to the application, identified and authenticated.
Input data Username , password
Normal Flow Expected Result Actual Result (Pass/Fail)

The user requests to cancel ride. System cancels ride if ride is

Pass
confirmed.

Alternative flow Expected result Actual Result (Pass/Fail)

User doesn’t confirmed ride. Not able to cancel Fail
Date 5-11-2018

Test conducted by Abdul Wahab Nizam , Abubaker Mujahid , Mohammad Nouman Aslam

Test verified by Mr. Malik Adnan Jaleel

21
 Test Cases
Add Car:

Test Case ID TC0011

Test Case Version Version 1.0
Functionality Add Car
Actor Owner
Pre-Condition Owner must login to the application
Input data Username , password
Normal Flow Expected Result Actual Result (Pass/Fail)
System shows car detail
Owner request to add car Pass
options to owner.

Alternative flow Expected result Actual Result (Pass/Fail)

Owner doesn’t have car or details Owner doesn’t add details Fail

Date 5-11-2018

Test conducted by Abdul Wahab Nizam , Abubaker Mujahid , Mohammad Nouman Aslam

Test verified by Mr. Malik Adnan Jaleel

22
 Test Cases
Add Information :
Test Case ID TC0012
Test Case Version Version 1.0
Functionality Add information
Actor Owner
Pre-Condition User must login to the application, identified and authenticated.
Input data Username , password
Normal Flow Expected Result Actual Result (Pass/Fail)

Owner request to add information. System display information. Pass

Alternative flow Expected result Actual Result (Pass/Fail)

User doesn’t car Not shown

Fail
Date 5-11-2018

Test conducted by Abdul Wahab Nizam , Abubaker Mujahid , Mohammad Nouman Aslam

Test verified by Mr. Malik Adnan Jaleel

23
 Test Cases
View management:

Test Case ID TC0014

Test Case Version Version 1.0
Functionality View management
Actor Admin
Pre-Condition Admin must have server.
Input data
Normal Flow Expected Result Actual Result (Pass/Fail)
System show management
Admin request to view management. Pass
server to admin
Alternative flow Expected result Actual Result (Pass/Fail)
No data available No data displayed Fail
Date 5-11-2018
Test conducted by Abdul Wahab Nizam , Abubaker Mujahid , Mohammad Nouman Aslam
Test verified by Mr. Malik Adnan Jaleel

24
 Test Cases
Feedback:
Test Case ID TC0015
Test Case Version Version 1.0
Functionality Feedback
Actor User
Pre-Condition User must login to the application, identified and authenticated.
Input data Username , password
Normal Flow Expected Result Actual Result (Pass/Fail)

System shows feedback page and

Requests to give feedback Pass
user able to give feedback.

Alternative flow Expected result Actual Result (Pass/Fail)

User is not login Not able to giv feedback Fail
Date 5-11-2018

Test conducted by Abdul Wahab Nizam , Abubaker Mujahid , Mohammad Nouman Aslam

Test verified by Mr. Malik Adnan Jaleel

25
 Test Cases
Logout:

Test Case ID TC0020

Test Case Version Version 1.0
Functionality Logout
Actor App User
Pre-Condition User must login to the application, identified and authenticated.
Input data Username , password
Normal Flow Expected Result Actual Result (Pass/Fail)
Requests for logout from system User logout successfully Pass
Alternative flow Expected result Actual Result (Pass/Fail)
User exit Not logout Fail System requests to logout
Date 5-11-2018
Test conducted by Abdul Wahab Nizam , Abubaker Mujahid , Mohammad Nouman Aslam
Test verified by Mr. Malik Adnan Jaleel

26
Gantt Chart

27
 Status of Thesis Report

We have completed all the 5 chapters of our thesis

1. Introduction
2. Requirement Analysis
3. System Design
4. Development and Configuration Management
5. Quality Assurance

28
 Status of Thesis Report Cont.
• Chapter 1 Introduction
1.1 Introduction
1.2 Objective
1.3 Motivation
1.4 Document convention
1.5 Feasibility Report
1.5.3 Resource Feasibility
1.6 Schedule feasibility
1.7 Operational Feasibility

29
 Status of Thesis Report Cont.
• Chapter 2 Requirement Analysis
2.1 Introduction
2.1.1 Product Scope
2.1.2 Definitions, Acronyms and Abbreviations
2.1.3 Formatting conventions
2.2 Overall Description
2.2.1 Product Perspective
2.2.2 Product Functionality
2.2.3 Users and characteristic
2.2.4 Operating Environment
2.2.5 Designs and Implementations Limitation
2.2.6 User Documentations
2.2.7 Assumptions and Dependencies
2.2.8 Specific Requirements
2.3 Other Non-functional Requirements
2.3.1 Performance Requirements
2.3.2 Safeties and Securities Requirement
2.3.3 Software Quality Attribute
30
 Status of Thesis Report Cont.
• Chapter 3 System Design
• 3.1 Introductions
• 3.2 Use Case
• 3.3 Fully Dressed Use Cases
• 3.3.1 Use Case UC1: Create Account
• 3.3.2 Use Case UC2: Login
• 3.3.3 Use Case UC3: Logout
• 3.3.4 Use Case UC4: Delete Account
• 3.3.5 Use Case UC5: Update Account
• 3.3.6 Use Case UC6: Update Username
• 3.3.7 Use Case UC7: Update Password
• 3.3.8 Use Case UC8: Add Route
• 3.3.9 Use Case UC9: View Schedule
• 3.3.10 Use Case UC10: Confirm Ride
• 3.3.11 Use Case UC11: Cancel Ride
• 3.3.12 Use Case UC12: Add Car
• 3.3.13 Use Case UC13: Add Informaion
• 3.3.14 Use Case UC14: Update Information

31
 Status of Thesis Report Cont.
• 3.3.15 Use Case UC15: Offer Ride
• 3.3.16 Use Case UC16: Add Route
• 3.3.17 Use Case UC17: Update Ride
• 3.3.18 Use Case UC18:Confirm Ride
• 3.3.19 Use Case UC19:Cancel Ride
• 3.3.20 Use Case UC20:Payment
• 3.3.21 Use Case UC21:Cash
• 3.3.22 Use Case UC22:View Management
• 3.3.23 Use Case UC23:Confirm Ride
• 3.4 User Class Diagram
• 3.5 System Sequence Diagram
• 3.5.1 Create Account
• 3.5.2 Login
• 3.5.3 Update Username
• 3.5.4 Update Password
• 3.5.5 Add Route
• 3.5.6 Add Route Owner
• 3.5.7 Confirm Ride
• 3.5.8 Cancel Ride
32
 Status of Thesis Report Cont.
• 3.5.9 Offer Ride
• 3.5.10 Add car
• 3.5.11 Add Information
• 3.5.12 Update Information
• 3.5.13 Add Route
• 3.5.14 Update Ride
• 3.5.15 View Management
• 3.5.16 Payment
• 3.5.17 Logout
• 3.6 Interaction Diagram/Sequence Diagram
• 3.7 Deployment Diagram
• 3.8 Package Diagram
• 3.9 Activity Diagram

33
 Summary of 60% Project Implementation

• Registration, Find Ride and Offer Ride module are fully

integrated with each other.

• The remaining modules will be done in next iteration.

34
Conclusion
The objective of this presentation was:
• To cut down all the conflicts about
requirements and design of the system
• Displaying 100% implementation in front of
committee

35