Final Project Report

Online Tutor Finding Application

Project Supervisor
Akmal Khan

Submitted By

F24PROJECT84C98

Maryam Zahrah BC230429699

Software Projects & Research Section,

Department of Computer Sciences,
Virtual University of Pakistan

P a g e 1 | 61
 CERTIFICATE
This is to certify that Maryam Zahrah (BC230429699) have worked on
and completed their Software Project at Software & Research Projects
Section, Department of Computer Sciences, Virtual University of
Pakistan in partial fulfillment of the requirement for the degree of BS
in Computer Sciences under my guidance and supervision.

In our opinion, it is satisfactory and up to the mark and therefore

fulfills the requirements of BS in Computer Sciences.

Supervisor / Internal Examiner

Mr. Akmal Khan

Supervisor,
Software Projects & Research Section,
Department of Computer Sciences
Virtual University of Pakistan

___________________
(Signature)

External Examiner/Subject Specialist

<<External Supervisor Name>>

___________________
(Signature)

Accepted By:

_____________
(For office use)

EXORDIUM

P a g e 2 | 61
In the name of Allah, the Compassionate,
the Merciful.

Praise be to Allah, Lord of Creation,

The Compassionate, the Merciful,
King of Judgment-day!

You alone we worship, and to You alone

we pray for help,
Guide us to the straight path

The path of those who You have favored,

Not of those who have incurred Your

wrath,
Nor of those who have gone astray.

P a g e 3 | 61
 DEDICATION

Thanks to Allah Almighty and his Prophet Muhammad (PBUH)

I want to dedicate this project to my respected and my honorable
parents. They guided and prayed for me throughout the project.
Thanks to teachers and friends who also cooperated with me to
complete this project in time. They motivated me for this project
and wished for my success in life.

P a g e 4 | 61
 ACKNOWLEDGEMENT

I take this opportunity to express my profound gratitude and deep

regard to my guide Sir Akmal Khan and Virtual University for
guidance, monitoring and constant encouragement throughout
this project. The blessings, help and guidance given by them time
to time carried me a long way. They showed the way of
completing the project.
I am extremely grateful to Sir Akmal Khan for providing me
with knowledge and his expertise. His valuable guidance and
encouragement in the project were helpful for me and lead to
completion easily.
I am also thankful to Virtual University for the valuable
information provided by them. I am grateful for their cooperation
during the period of my project. I am also grateful for all those
people who were directly or indirectly involved in this project
and prayed for me.

P a g e 5 | 61
 PREFACE

In today’s digital education landscape, connecting students

with qualified tutors has become crucial. The Online Tutor
Finding Application addresses this need by offering a smart,
secure, and user-friendly platform. It enables students and parents
to find tutors based on subject, availability, and location, while
allowing tutors to manage profiles and sessions efficiently.
This project spans the full software development lifecycle from
requirement analysis to design and implementation demonstrating
core principles of software engineering. The documentation
includes system requirements, use cases, diagrams, interfaces,
and testing scenarios to ensure clarity and structure. This
initiative aims to improve private tutoring accessibility and
contribute meaningfully to modern education.

P a g e 6 | 61
 TABLE OF CONTENTS

Contents:

CHAPTER NO. 1.…………………………………………………………………

09
GATHERING & ANALYZING INFO………………………………………….
10

1.1 INTRODUCTION……………………………………… 10

1.2 PURPOSE…………………………………………. 10

1.3 SCOPE……………………………………………. 10

1.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS…. 11

1.5 PROJECT REQUIREMENTS………………………. 11

1.5.1 Functional Requirements………………………….11

1.5.2 Non-Functional Requirements…………………. 12

1.6 USE CASES AND USAGE SCENARIOS……. 14

1.6.1 Use Case Diagrams……... 14

1.6.2 Usage Scenarios………... 14

1.7 DEVELOPMENT METHODOLOGY…… 25

1.7.1 Chosen Methodology………………………… 25

1.7.2 Reasons for Chosen Methodology…………… 25

1.7.2 Work Plan (Gantt Chart) ……………………... 29

1.7.2 Project Schedule (Submission Calendar) ……. 30

P a g e 7 | 61
CHAPTER NO. 2 ……………………………………………………………… 31
DESIGNING THE PROJECT ……………………………………………….32

2.1 INTRODUCTION ……………………………………… 32

2.2 PURPOSE …………………………………………….

33

2.3 SCOPE ………………………………………………. 33

2.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS…. 33

2.5 ARCHITECTURAL REPRESENTATION (ARCHITECTURE

DIAGRAM) …………………………………………… 34

2.6 DYNAMIC MODEL: SEQUENCE DIAGRAMS………… 36

2.7 OBJECT MODEL/LOGICAL MODEL: CLASS DIAGRAM........ 49

2.8 DATABASE MODEL (DATABASE DIAGRAM) ………… 50

2.9 GRAPHICAL USER INTERFACES ……………………… 51

CHAPTER NO.3 …………………………………………………………… 56

DEVELOPMENT …………………………………………………………… 56
3.1 DEVELOPMENT PLAN (ARCHITECTURE DIAGRAM) … 58

P a g e 8 | 61
 CHAPTER 1
Gathering & Analyzing Info

P a g e 9 | 61
Gathering and Analyzing Info
1.1 introduction:
This document for the Online Tutor Finding Application provides a
comprehensive overview of the system's scope, objectives, and detailed
requirements. This application is designed to serve as a reliable platform
that connects students or parents with qualified tutors across various
subjects and educational levels. The document elaborates on the functional
and non-functional requirements, use case diagrams, system architecture,
user interaction scenarios, and the methodology adopted for system
development.

By clearly outlining the intended features and performance expectations,

this document ensures alignment between stakeholders—including
developers, designers, and end-users—throughout the software
development lifecycle. It serves as a blueprint to guide the design,
implementation, and validation of a user-friendly, efficient, and scalable
platform that simplifies the process of finding and engaging with suitable
tutors.

1.2 Purpose:

The purpose of this chapter is to get the clear understanding of the project.
What is the project scope, requirements, methodology, and timelines for
the development of the project? Without having the clear understanding of
the purpose, we will not be able to achieve the exact target.

1.3 Scope:

The Online Tutor Finding Application is designed to streamline the

process of connecting students and parents with qualified tutors. By
creating personalized profiles, users can easily search for tutors based on
their specific needs, whether it's mastering complex math equations or
improving language skills. Tutors can manage their schedules,
communicate directly with students, and build their reputation through
ratings and reviews.

P a g e 10 | 61
Our platform is designed to be user-friendly and accessible on both
desktop and mobile devices, making it easy to find and book tutoring
sessions anytime, anywhere. The admin panel ensures the platform runs
smoothly and it moderates user interactions. It also maintains a high
standard of quality.

By bringing together students and tutors, we aim to create a more efficient

and effective learning experience. Our application empowers students to
take control of their education and provides tutors with a flexible platform
to share their knowledge and expertise. With a focus on personalized
learning and professional development, we strive to bridge the gap
between students' learning goals and tutors' expertise.

1.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS

SRS: Software Requirement Specification

DBMS: Data Base Managements System

GUI: Graphical User Interface

1.5 Project requirements

1.5.1 Functional Requirements:

Functional and non-functional requirements

Functional Requirements:
1-User Registration and Authentication

 All users (admin, tutors, and parents/users) can register and log in
securely.
 Admin and tutors receive account details from the admin.
2-Profile Management

 Users (parents) can update their profiles after registration.

 Tutors can upload and manage resumes and profile details (e.g.,
qualifications, experience, subjects).
3-Tutor Search and Selection

 Parents can search and filter tutors based on subjects like Computer
Science, Medical, etc.

P a g e 11 | 61
  Detailed tutor profiles, including experience, qualifications, and
fees, are visible to parents.
 Parents can select multiple tutors for various subjects and generate
fee vouchers for payment.
4-Payment and Fee Management

 Admin generates fee vouchers for parents based on selected tutors.

 Parents can download fee vouchers, make payments, and upload
proof of payment (voucher).
 Admin can view and verify uploaded fee vouchers and manage
expense and profit reports.
5-Class Management

 Tutors can share class schedules, links (e.g., Zoom, Google Meet),
and other session details with registered students.
 Parents can view class schedules and access class links from their
chosen tutors.
6-Online Quiz and Progress Tracking

 Tutors can create quizzes (MCQ-based) for students to assess their

progress.
 Parents/students can take quizzes online and view their performance
results.
 Tutors can monitor students’ quiz progress to provide feedback or
additional help.
7-Notifications and Communication

 Notifications (email or SMS) for important actions like tutor

selection confirmation, fee payment status, and quiz updates.
 Parents and tutors can communicate through chat or messaging
features as needed (if included).
8-Admin Management of Categories and Tutors

 Admin can add, update, or delete subject categories (e.g., Medical,

Engineering).
 Admin registers tutors in specific subjects, providing all relevant
details.
 Admin can update/delete tutor profiles and manage associations
between students and tutors.

1.5.2 Non-Functional Requirements

1-Performance:

P a g e 12 | 61
The system should support concurrent access by multiple users without
slowdowns.
2-Security:
Ensure data protection with secure logins, encrypted transactions, and
secure data handling.
3-Usability:
The application should have an intuitive and easy-to-navigate interface for
all user types.
4-Reliability:
The system must be consistently available with minimal downtime to
support user needs.
5-Scalability:
The application should be designed to handle future growth in user and
tutor numbers smoothly.
6-Compatibility:
Ensure compatibility across major web browsers (e.g., Chrome, Firefox)
and device types.
7-Data Integrity:
All data, including user information and payment details, should remain
accurate and consistent.
8-Maintainability:
The codebase should be organized to allow for easy updates and
debugging.
9-Backup and Recovery:
Regular data backups and a recovery mechanism to prevent data loss in
case of failure.
10-Accessibility:
Ensure the application is accessible to users with disabilities, following
web accessibility standards.
11-Response Time:
Pages and operations should load and complete within 2-3 seconds for a
smooth user experience.

P a g e 13 | 61
 1.6 USE CASES AND USAGE SCENARIOS

1.6.1 Use Case Diagram:

Fig 01: Usecase Diagram

1.6.2 Usage Scenarios:

Usage Scenario # 1
Use case Title Register
Use case id UC-01
Actions 1. User /Tutor fills in the registration form by giving
P a g e 14 | 61
 email or password and other details.
2. User submits the form through the submit button.
Descriptions Allows users (parents)/Tutor to create a new account
in the system by entering required details like name,
email, phone number, and password.
Alternative Paths User already exists in the system. If yes, prompt for
re-registration.
Pre- conditions User is not yet registered in the system.
Post conditions New user account is created.
Author BC230429699
Exceptions If the registration data is incomplete or invalid, show
an error message.

Usage Scenario # 2
Use case Title Login
Use case id UC-02
Actions 1. User/ Tutor/Admin enters login credentials (email
and password).
2. User clicks login.
Description Allows users, tutors, and admins to log in to their
respective panels. Verifies the credentials to give
access to the correct dashboard.
Alternative Paths If incorrect credentials are entered, show an error
message.
Pre- conditions User has registered an account.
Post conditions User is authenticated and directed to the correct
panel (Admin/Tutor/Parent).
Author BC230429699
Exceptions If credentials are invalid, system shows an error
message and prevents login.

P a g e 15 | 61
 Usage Scenario # 3
Use case Title Logout
Use case id UC-03
Actions 1. User/Tutor/Admin clicks logout.
2. User is logged out of the system.
Description Allows any actor (Admin, User, Tutor) to safely log
out of the system and end the session at any time.
Alternative Paths None.
Pre- conditions User is logged in and needs to terminate the session.
Post conditions User is logged out and redirected to the login page.
Author BC230429699
Exceptions If logout fails due to session issues, show an error
and remain logged in.

Usage Scenario # 4
Use case Title View Tutor Profile
Use case id UC-04
Actions 1. User searches for a tutor.
2. User clicks on a tutor's profile.
Description Users (parents) can view the detailed profile of a
tutor, including their qualifications, experience,
subjects taught, and availability.
Alternative Paths None.
Pre- conditions User is logged in and looking for a tutor.
Post conditions The tutor's profile is displayed with all the details.
Author BC230429699
Exceptions If no tutor matches the search criteria, show a "No
results found" message.

Usage Scenario # 5
Use case Title Update Profile

P a g e 16 | 61
Use case id UC-05
Actions 1. User navigates to profile settings.
2. User updates details.
3. User submits.
Description Allows users (parents, tutors) to update their profile
details (like name, contact, address, etc.).
Alternative Paths If the user does not want to update, cancel the
operation.
Pre- conditions User is logged in and has a profile in the system.
Post conditions Profile is updated with new details.
Author BC230429699
Exceptions If the data is invalid or incomplete, show an error
and prevent saving.

Usage Scenario # 6
Use case Title Select Tutor
Use case id UC-06
Actions 1. User browses through the list of tutors.
2. User selects one or more tutors for specific
subjects.
Description Users can select tutors for different subjects based on
their preferences (e.g., Math, English, Science, etc.).
Alternative Paths User selects no tutor or incorrect subjects.
Pre- conditions User is logged in and searching for a tutor.
Post conditions Tutors are selected and saved to the user's list.
Author BC230429699
Exceptions If no tutors are available or selected, an error
message appears.

Usage Scenario # 7
Use case Title View Scheduled Class Details
Use case id UC-07
Actions 1. User logs in.
P a g e 17 | 61
 2. User navigates to the dashboard.
3. User clicks on a scheduled class.
Description Users (students) can view details of upcoming
classes, including timing, subject, and class link.
Alternative Paths No scheduled classes found.
Pre- conditions User has at least one class scheduled.
Post conditions Class details are displayed.
Author BC230429699
Exceptions If the class link is broken or timing is missing, show
an error message.

Usage Scenario # 8
Use case Title Take Online Quiz
Use case id UC-08
Actions 1. User selects a quiz.
2. User answers the questions.
3. User submits the quiz.
Description Users (students) can take an online quiz created by
tutors to assess their knowledge on a subject.
Alternative Paths User does not answer all questions.
Quiz submission time expires.
Pre- conditions User is logged in and has access to an active quiz.
Post conditions Quiz results are recorded and available for review.
Author BC230429699
Exceptions If the quiz fails to load or submission times out,
show an error message.

Usage Scenario # 9
Use case Title View Quiz Results
Use case id UC-09
Actions 1. User clicks on a completed quiz.
2. User views results and performance.
Description Users (students) can view their performance in

P a g e 18 | 61
 quizzes they have taken, including scores and
feedback.
Alternative Paths If no results available, show a "No results" message.
Pre- conditions User has taken at least one quiz.
Post conditions Quiz results are displayed with scores.
Author BC230429699
Exceptions If the results are not accessible, display an error.

Usage Scenario # 10
Use case Title View Progress
Use case id UC-10
Actions 1. User logs into the portal.
2. User views quiz results and progress.
Description Users (students) can view their performance and
progress in quizzes provided by the tutor.
Alternative Paths User has not taken any quiz yet.
Pre- conditions User has an account and has taken at least one quiz.
Post conditions User can view a detailed report of progress in
quizzes.
Author BC230429699
Exceptions If no quiz has been taken, show a message
indicating no progress data available.

Usage Scenario # 11
Use case Title Pay Fee
Use case id UC-11
Actions 1. User selects a fee voucher.
2. System redirects to the payment gateway.
3. User completes payment.
4. System confirms payment and updates the
database.
Description Allows users to pay for tutor services.
Alternative Paths Payment fails (redirect to retry payment).

P a g e 19 | 61
 User cancels the payment (redirect to dashboard).
Pre- conditions User is logged in and has a pending fee voucher.
Post conditions Payment is processed, and confirmation is sent to
the user.
Author BC230429699
Exceptions If the payment gateway is unavailable, show an
error message.

Usage Scenario # 12
Use Case Title Manage Tutor Profile
Use Case ID UC-12
Actions 1. Tutor logs in.
2. Tutor updates resume and other profile
information.
3. Tutor submits the changes.
Description Tutors can manage their profile, including
uploading and updating their resume, adding
qualifications, and other personal details.
Alternative Paths Tutor fails to update profile, cancels action.
Pre-Conditions Tutor is logged in and has access to their profile.
Post-Conditions Profile is updated and visible to users.
Author BC230429699
Exceptions If an invalid file format or data is uploaded, show an
error message.

Usage Scenario # 13
Use Case Title Upload Resume
Use Case ID UC-13
Actions 1. Tutor selects "Upload Resume" option.
2. Tutor uploads a file (PDF or Word format).
3. System validates and stores the resume.
Description Tutors can upload their resumes to display
qualifications and expertise.
Alternative Paths Unsupported file format uploaded (display error).
Upload fails (retry option provided).
Pre-Conditions Tutor is logged in.
System has sufficient storage space.
Post-Conditions Resume is uploaded and visible to parents/users.
Author BC230429699
Exceptions If file storage fails, notify the tutor with an error
message.

P a g e 20 | 61
 Usage Scenario # 14
Use Case Title Schedule Class
Use Case ID UC-14
Actions 1. Tutor selects "Schedule Class" option.
2. Tutor inputs class details (date, time, subject,
mode of teaching).
3. System saves the schedule and notifies the
user/parent.
Description Tutors can schedule classes for students and share
details with users.
Alternative Paths Conflicting schedule entered (display conflict
warning).
Notification to user/parent fails (log an error).
Pre-Conditions Tutor is logged in.
The system is online.
Post-Conditions Class is successfully scheduled and stored in the
system.
Author BC230429699
Exceptions If the scheduling process fails, notify the tutor with
an error message.

Usage Scenario # 15
Use Case Title Create Quiz
Use Case ID UC-15
Actions 1. Tutor selects "Create Quiz" option.
2. Tutor enters quiz details (title, subject, questions, and
answers).
3. System saves the quiz and makes it accessible to students.
Description Tutors can create quizzes to assess students'
knowledge.
Alternative Paths Incomplete quiz details provided (prompt for
completion).
Quiz fails to save (retry option provided).

Pre-Conditions Tutor is logged in.

System has quiz creation functionality enabled.
Post-Conditions Quiz is created and available for students to take.
Author BC230429699
Exceptions If quiz creation fails, notify the tutor with an error
message.

P a g e 21 | 61
 Usage Scenario # 16
Use Case Title Monitor Progress
Use Case ID UC-16
Actions 1. Tutor selects "Monitor Progress" option.
2. System retrieves and displays students' quiz
results, attendance, and grades.
3. Tutor analyzes and records observations.
Description Tutors can monitor students' progress and
performance metrics.
Alternative Paths No progress data available (show "No records
found").
System fails to retrieve data (show error message).

Pre-Conditions Tutor is logged in.

Student progress data is available in the system.
Post-Conditions Tutor reviews students' progress for further actions.
Author BC230429699
Exceptions If data retrieval fails, notify the tutor with an error
message.

Usage Scenario # 17
Use Case Title Register Tutor
Use Case ID UC-17
Actions 1. Admin accesses the "Register Tutor" option.
2. Admin fills in the tutor's details (name,
qualifications, subject expertise, contact).
3. System validates and stores the information.
Description Admin can register tutors in the system for parents
and students to access.
Alternative Paths Tutor already exists (system notifies admin).
Mandatory fields are left empty (validation errors
displayed).

Pre-Conditions Admin is logged in.

The system is online.
Post-Conditions Tutor is successfully added to the system and listed

P a g e 22 | 61
 in the database.
Author BC230429699
Exceptions If the system fails to save data, display "Unable to
register tutor" error.

Usage Scenario # 18
Use case Title Generate Fee Voucher
Use case id UC-18
Actions 1. Admin selects the tutor and student.
2. Admin sets the fee amount.
Description Admin generates a fee voucher for a student based
on the selected tutor and course. Includes details
like amount and payment method.
Alternative Paths Admin fails to input the correct fee or tutor details.
Pre- conditions Admin is logged in and has necessary details about
the tutor and student.
Post conditions Fee voucher is generated and available for
download.
Author BC230429699
Exceptions If fee is not provided or details are missing, error
occurs and voucher is not generated.

Usage Scenario # 19
Use case Title Verify Payment
Use case id UC-19
Actions 1. Admin receives proof of payment.
2. Admin verifies the voucher/payment details.
Description Admin verifies the payment made by the user,
confirming that the student has paid the tutor's fee.
Alternative Paths Payment verification fails (incorrect amount,
invalid proof).
Pre- conditions Payment proof is uploaded by the user.
Post conditions Payment is verified and marked as "paid."
Author BC230429699
Exceptions If payment is not verified, show an error or alert the
user for re-upload.

P a g e 23 | 61
 Usage Scenario # 20
Use case Title Generate Report (Admin)
Use case id UC-20
Actions 1. Admin accesses the report section.
2. Admin generates the report.
Description Admin can generate reports related to expenses,
profits, and other analytics for the platform,
providing a summary of financial data.
Alternative Paths Admin doesn’t select necessary parameters (like
date range).
Pre- conditions Admin is logged in and has access to financial data
and parameters for report generation.
Post conditions Report is generated and available for download.
Author BC230429699
Exceptions If the report cannot be generated due to missing
data or incorrect parameters, show an error
message.

Usage Scenario # 21
Use case Title Store Information in Database (Admin)
Use case id UC-21
Actions 1. Admin logs in.
2. Admin navigates to the database management
section.
3. Admin inputs tutor, student, or class data into the
database.
4. Admin confirms and saves the data.
Description Admin stores all relevant data such as tutor,
student, and class information into the system’s
database.
Alternative Paths If data fails to be saved due to connectivity issues,
Admin retries the operation.
If the data is incorrect, Admin makes necessary
corrections before saving.
Pre- conditions Admin is logged in and authorized to input data.
Post conditions The data is saved correctly in the database and is
available for future reference.
Author BC230429699
Exceptions If the data entry fails or the database connection is
lost, an error message is shown.

P a g e 24 | 61
 1.7 DEVELOPMENT METHODOLOGY

1.7.1 Chosen Methodology

The adopted methodology of this project is the VU process model.
The VU process model is the combination of water fall model and the
spiral model which are discussed below:
Methodology:
A logical and systemic approach for to the design process, as a well as a
set of decision-making guidelines, is provided by the software design
methodology. A design methodology is the set of notations or diagrams
that outline a series of activities. Every project manager understands the
importance of selecting the best method for the job. Here are few
examples:
 Water fall model
 Spiral model

Water fall model:

The Waterfall Model is a structured, linear approach to software
development that divides the project into sequential phases. First,
Requirements Gathering is conducted to document and define all project
requirements comprehensively. This is followed by the System Design
phase, where the architecture and components are planned based on the
initial requirements. Implementation involves the actual coding, adhering
closely to the design document to build the system’s functionalities. Once
coding is completed, the Integration and Testing phase assembles and tests
the system to identify and resolve any issues. After testing, the
Deployment phase releases the product to the end-users. Finally,
Maintenance involves updating and addressing any post-deployment
issues, ensuring the software remains functional over time.
Advantages:
 Easy to understand and follow due to its linear structure.
 Well-organized phases with defined deliverables.
 Simple project tracking, as each phase has specific milestones.
 Effective for small projects with stable, well-defined requirements.
 Documentation is thorough, supporting long-term maintenance.
Disadvantages:
 Rigid structure makes changes difficult and costly.
 Testing occurs late, which can lead to delayed issue discovery.
 Limited user feedback during development, as users only see the
final product.

P a g e 25 | 61
  Unsuitable for complex projects with evolving requirements.
 Risk of rework if requirements change after initial phases.

Fig 02: Water Fall Model

Spiral model:
The Spiral Model is a risk-driven software development process that
combines iterative and sequential aspects. It was designed to handle large,
complex, and high-risk projects by breaking development into cycles or
"spirals." Each spiral consists of four main phases: Planning, Risk
Analysis, Engineering, and Evaluation. In the Planning phase, objectives
and requirements are defined. Risk Analysis then identifies and mitigates
potential risks to reduce uncertainties. During Engineering, the product is
designed, developed, and tested based on the current requirements. In the
Evaluation phase, the client reviews the product, providing feedback to
guide the next cycle. This model allows for adjustments and improvements
with each iteration, making it suitable for projects with evolving
requirements. By incorporating feedback and continuously addressing
risks, the Spiral Model promotes a flexible, adaptive approach, enhancing
project stability and meeting user needs effectively.

P a g e 26 | 61
 Fig 03: Spiral Model

Advantages:
 Identifies and mitigates risks early.
 Adapts to changes throughout development.
 Continuous client reviews.
 Early prototypes for testing.
 Better project monitoring and adjustments.
 Continuous testing improves product quality.
Disadvantages:
 Difficult to manage multiple cycles.
 Iterative process extends timelines.
 Increased costs due to repeated cycles.
 Requires skilled risk management.
 Overkill for smaller, fixed projects.
 Excessive documentation in each phase.

VU process model:

P a g e 27 | 61
As it is already mentioned that VU process model is the combination of
water fall model and spiral model which is also called the hybrid approach
of system development so in my project “Online Tutor Finding
Application” I chose this model. The idea behind this model is to get the
benefits of both these models. Essentially, Water Fall Model is a
framework for software development, proceeds sequentially through a
series of phases, starting with system requirement analysis and leading the
product release and maintenance, whereas the key characteristics of spiral
model is risk management at regular stages in the entire software
development cycle. In VU Process Model we will be working in phases to
complete out project. The reason to select this model is that this approach
of system development maximizes the quality of system and minimizes the
disadvantages and risk. It is linear model and easy to understand. This
provides the much facility to estimate the project cost and provides batter
understanding to project developer. VU process model is heavily
dependent on risk analysis and evaluation in each phase.
VU Process Model:

Fig 04: VU Process Model

P a g e 28 | 61
1.7.2 Work Plan (Gantt Chart):

Fig 05: Gantt Chart

Fig 06: Time Line

1.7.2 Project Schedule (Submission Calendar):
P a g e 29 | 61
Fig 07: Submission Calendar

P a g e 30 | 61
 CHAPTER 2
Designing the Project

Chapter 2: Design the Project

2.1 INTRODUCTION:

P a g e 31 | 61
This Design Document provides a detailed framework for the development

of the Online Tutor Finding Application, translating the requirements

outlined in the SRS into actionable technical designs. It ensures that all

stakeholders and team members have a shared understanding of the

system's architecture, design, and implementation.

Contents Overview

This document encompasses:

Entity Relationship Diagram (ERD): Visualizing system data and

relationships to build an efficient database.

Sequence Diagrams: Defining task execution flows for each use case to

clarify system interactions.

Architecture Design Diagram: Structuring the application into logical,

tiered layers for scalability and modularity.

Class Diagram: Defining objects, attributes, and relationships to support

object-oriented development.

Database Design: Establishing a schema for efficient data storage and

retrieval.

P a g e 32 | 61
Interface Design: Prototyping user interfaces to demonstrate application

features and usability.

Test Cases: Ensuring system reliability and accuracy by detailing

scenarios for functional and non-functional validation.

2.2 PURPOSE:

The purpose of this Design Document is to translate the functional and

non-functional requirements defined in the SRS into a clear, structured,
and technically sound design for the Online Tutor Finding Application. It
provides a comprehensive blueprint that guides the development team
through system architecture, database design, interface layouts, and
interaction flows. By addressing technical design decisions early, it helps
mitigate development risks and ensures that the final product aligns with
stakeholder expectations. This document also enables effective
collaboration among team members by offering a shared technical vision
and reference point throughout the development process.

2.3 SCOPE:
This document encompasses the complete technical design of the Online
Tutor Finding Application, covering all core system components, their
interactions, and data management strategies. It includes visual models
such as ER diagrams, sequence diagrams, and architecture designs that
collectively define how the system will function and scale. The scope also
extends to user interface mockups and test cases, ensuring usability and
reliability are incorporated from the design stage. It sets boundaries for
what the system will deliver during the development phase, offering a clear
direction for implementation and evaluation.

2.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS:

DD: Design Document

DBMS: Data Base Managements System

GUI: Graphical User Interface

P a g e 33 | 61
 2.5 ARCHITECTURAL REPRESENTATION (ARCHITECTURE
DIAGRAM):
This architectural Design Diagram offers a structured representation of the

Online Tutor Finding Application, emphasizing the interaction between its

core layers: the Presentation Layer, Application Layer, and Data Access

Layer. The Presentation Layer focuses on delivering a user-friendly

interface for seamless interaction, while the Application Layer handles the

business logic, ensuring smooth execution of features such as tutor

registration, scheduling, and quiz management. The Data Access Layer

manages secure and efficient communication with the database, ensuring

data integrity and reliability. This layered architecture promotes

modularity, scalability, and maintainability, forming the backbone of the

application’s design.

P a g e 34 | 61
Fig 08: Architectural Diagram

P a g e 35 | 61
 2.6 DYNAMIC MODEL: SEQUENCE DIAGRAMS:
These sequence Diagram capture the interactive flow of operations within

the Online Tutor Finding Application, showcasing how various actors such

as Admins, Tutors, and Parents engage with the system. These diagrams

visually represent the step-by-step exchange of messages and actions,

illustrating processes like tutor registration, class scheduling, and course

management. By mapping out these interactions in chronological order, the

diagrams offer an insightful perspective on the system's functionality,

ensuring clarity and precision in their workflows.

P a g e 36 | 61
Fig 09: Register

P a g e 37 | 61
Fig 10: Login

P a g e 38 | 61
Fig 11: Logout

P a g e 39 | 61
Fig 12: View Tutor Profile (by User and Admin)

P a g e 40 | 61
Fig 13: Update Profile (by User/Tutor)

Fig 14: Select Tutor

P a g e 41 | 61
Fig 15: View Scheduled classes

Fig 16: Take Online Quiz

P a g e 42 | 61
Fig 17: View Quiz Results

Fig 18: View Progress

P a g e 43 | 61
Fig 19: Pay Fee

P a g e 44 | 61
Fig 20: Manage Tutor Profile

P a g e 45 | 61
 Fig 21: Upload Resume

Fig 22: Schedule Class

P a g e 46 | 61
 Fig 23: Create Quiz

Fig 24: Monitor Progress

P a g e 47 | 61
 Fig 25: Register Tutor

Fig 26: Generate Fee Voucher

P a g e 48 | 61
Fig 27: Verify Payment

P a g e 49 | 61
 Fig 28: Store Information in database (by Admin)

2.7 OBJECT MODEL/LOGICAL MODEL: CLASS DIAGRAM:

This Class Diagram showcases the key components of the Online Tutor
Finding Application, highlighting the primary classes, their attributes, and
the relationships among them. It provides a visual representation of how
the Admin, User/Parent, Tutor, Students, Fee_Payment, Quiz, and Class
interact within the system. This diagram serves as a blueprint for
understanding the structure and ensuring seamless communication between
different modules of the application.

P a g e 50 | 61
 Fig 29: Class Diagram

2.8 DATABASE MODEL (DATABASE DIAGRAM):

The Database Design Diagram provides an overview of the database
structure, highlighting the organization of data and the relationships
between various entities in the Online Tutor Finding Application. It
ensures a systematic approach to data storage and retrieval, covering key
entities. This diagram serves as a blueprint for maintaining data

P a g e 51 | 61
consistency, optimizing queries, and supporting the application's
functionality by clearly defining primary keys, foreign keys, and
relationships among the tables. It plays a crucial role in ensuring data
integrity and smooth operation of the system.

Fig 30: Database Design Diagram

2.9 GRAPHICAL USER INTERFACES:

P a g e 52 | 61
P a g e 53 | 61
P a g e 54 | 61
P a g e 55 | 61
P a g e 56 | 61
CHAPTER 3
Development

P a g e 57 | 61
1.2 DEVELOPMENT PLAN (ARCHITECTURE DIAGRAM):
This architectural Design Diagram offers a structured representation of the

Online Tutor Finding Application, emphasizing the interaction between its

core layers: the Presentation Layer, Application Layer, and Data Access

Layer. The Presentation Layer focuses on delivering a user-friendly

interface for seamless interaction, while the Application Layer handles the

business logic, ensuring smooth execution of features such as tutor

registration, scheduling, and quiz management. The Data Access Layer

manages secure and efficient communication with the database, ensuring

data integrity and reliability. This layered architecture promotes

modularity, scalability, and maintainability, forming the backbone of the

application’s design.

P a g e 58 | 61
P a g e 59 | 61
 REFERENCES
W3Schools for HTML:
https://www.w3schools.com/html/

YouTube – Learn HTML (free course):

https://www.youtube.com/watch?v=UB1O30fR-EE
(Traversy Media – HTML Crash Course)
Learn to Code PHP – W3Schools PHP Tutorial:
https://www.w3schools.com/php/

Learn to Code MySQL – W3Schools MySQL Tutorial:

https://www.w3schools.com/sql/

Cs 403 book for database

Cs504 for sequence diagrams and Usecase diagram
Cs304 for classes and class diagram

P a g e 60 | 61
 APPENDIX

Chapter 1 Introduction and analysis

Chapter 2 Designing phase
Chapter 3 Architecture phase

P a g e 61 | 61