CS-243|Database Systems

Project Proposal

Instructor: Dr. Qaiser S Durrani

Date: May 12, 2024

1
Project Title:

Care Connect

Group Members:

Sr No. Name Roll No.

1 Muhammad Asad Ullah (GL) 221400089
2 Jawad Akhtar 221400071
3 Rana Zunair 221400101
4 Muhammad Moaz 221370187

2
Table of Contents:
1. Problem Statement 04
2. Scope
2.1 Do 04
2.2 Don’ts 04
3. Functional Requirements 05
4. Non Functional Requirements 08
5. Technologies 09

3
1. Problem Statement:
The project aims to design and implement a database system for a platform that connects
individuals seeking assistance with skilled professionals in the domestic and healthcare
services sector. The challenge is to create a reliable and secure system that addresses
concerns related to trust, security, quality assurance, and legal compliance.

2. Scope:
2.1 Do:
1. We’ll allow customers to sign up and create their profiles.
2. The system will also allow both customers to login if they have already an account.
3. We’ll integrate with a third party banking service to generate payment challans.
4. We’ll implement functionality for customers to browse different service categories
and search for specific services and workers by their name.
5. We’ll implement a review system that’ll allow the customer to open customers
profile and then view give reviews.
6. We’ll also have an admin panel to update the data of the website.

2.2 Don’ts:
1. No Automated Hiring Confirmation: We’ve decided not to include an automated
system that dispatches hiring confirmation emails to customers. We believe in
keeping the hiring process personal and less mechanized.
2. No Real-time Availability Tracking: We won’t be tracking the real-time availability of
workers. This decision is based on the complexity of real-time updates and respect
for the privacy of our workers.
3. No In-app Training or Certification: We won’t be offering in-app training or
certification for workers. While we value service quality, we believe this is best
handled outside of the app due to the resources required.
4. Basic Search and Filtering: We’re keeping our search and filtering options simple.
Customers can browse and search for services and workers, but we won’t be offering
advanced search options to avoid overwhelming users with choices.
5. No Social Media Integration: We’ve decided not to integrate with social media
platforms. We believe in keeping our platform separate and maintaining the privacy
of our users.

4
3. Functional Requirements:

3.1 Client Searches For Worker

3.1.1 System should allow a client to search for a worker through their name.

3.2 Client Hires Worker

3.2.1 System should allow client to narrow down his search for a worker by giving his
preferences such as service category.

3.2.2 System should allow client to narrow down his search for a worker by giving his skills.

3.2.3 System should allow client to narrow down his search for a worker by giving his name.

3.2.4 System should allow client to narrow down his search for a worker by giving his
professional education.

3.2.5 System should allow client to narrow down his search for a worker by giving his salary.

3.2.6 System should allow client to narrow down his search for a worker by giving his age.

3.2.7 System should allow client to narrow down his search for a worker by giving his gender.

3.2.8 System should allow client to narrow down his search for a worker by giving his
personality.

3.3 Display Service Provider Information

3.3.1 The system shall display client detailed information about the service provider, including
their ratings.

3.3.2 The system shall display client detailed information about the service provider, including
their skills.

3.3.3 The system shall display client detailed information about the service provider, including
their experience.

3.3.4 The system shall display client detailed information about the service provider, including
their personality.

3.3.5 The system shall display client detailed information about the service provider, including
their reviews.

3.4 Generate Challan for making payment

3.4.1 Upon choosing a worker, system should generate a challan form which will then be used
customer to make payment for that contract.

3.5 Client select duration of contract

3.5.1 Before payment section, system shall ask the user to enter the duration of contract to calculate
the charges for this contract.

5
 3.6 Client cancels contract

3.6.1 System should allow client to cancel a contract by entering contract id.

3.7 Client rates Customer

3.7.1 System should allow a client to rate a worker on a scale of five stars.

3.8 Client comment customer

3.8.1 System should allow client to give comment to a worker.

3.9 Customer create Profile

3.9.1 System should allow client to create his profile by providing name.

3.9.2 System should allow client to create his profile by providing gender.

3.9.3 System should allow client to create his profile by providing dob.

3.9.1 System should allow client to create his profile by providing contact.

3.9.1 System should allow client to create his profile by providing CNIC.

3.9.1 System should allow client to create his profile by providing profile picture.

3.9.1 System should allow client to create his profile by providing country.

3.9.1 System should allow client to create his profile by providing province.

3.9.1 System should allow client to create his profile by providing city.

3.9.1 System should allow client to create his profile by providing address.

3.10 Customer edit profile

3.10.1 System shall allow client to edit his profile by visiting account section.

3.11 Customer deletes profile

3.11.1 System should allow customer to delete his account.

3.12 Admin Manages Worker profile

3.12.1 System should allow admin to create worker’s profile by providing name.

3.12.2 System should allow admin to create worker’s profile by providing skills.

3.12.3 System should allow admin to create worker’s profile by providing experience.

3.12.4 System should allow admin to create worker’s profile by providing experience.

3.12.5 System should allow admin to create worker’s profile by providing education.

3.12.6 System should allow admin to create worker’s profile by providing age.

3.12.7 System should allow admin to create worker’s profile by providing education.

3.12.8 System should allow admin to create worker’s profile by providing gender.

3.12.9 System should allow admin to create worker’s profile by providing expected salary.

6
3.12.10 System should allow admin to create worker’s profile by providing personality.

3.12.11 System should allow admin to create worker’s profile by providing cities.

3.13 Customer views worker profile

3.13.1 System should allow admin to view Worker’s profile.

3.14 Admin search worker profile

3.14.1 System should allow admin to search for a worker’s profile.

3.15 Admin edit worker profile

3.15.1 System should allow admin to edit worker’s profile.

3.16 Admin deletes worker profile

3.16.1 System should allow admin to delete worker’s profile.

3.17 Admin prints workers list

3.17.1 System should allow admin to print the list of workers.

3.18 Admin print worker profile

3.18.1 System should allow admin to print the profile of a worker.

3.19 Admin views Contracts

3.19.1 System should allow admin to view contracts.

3.20 Admin deletes Contracts
3.20 System should allow admin to delete contracts.

3.21 Admin edits Contracts

3.21.1 System should allow admin to edit contracts.

3.22 Admin prints Contracts

3.23.1 System allow admin to print list of contracts.

3.23 Admin print specific Contract

3.23.1 System should allow admin to print the details of a specific contract.

3.24 Admin manages clients

3.24.1: System should allow the admin to search a client by using CNIC.

3.24.2: System should allow admin to search for a client by using Client ID.

3.24.3 System should allow admin to edit the details of a client by clicking on edit button.

3.24.4 System should allow admin to delete a client’s profile.

7
 3.25 Admin manages service category
3.25.1 System should allow admin to add a service category.
3.25.2 System should allow admin to delete a service category.

3.26 Admin accepts contract

3.26.1 System should allow admin to accept a contract.

3.26.2 System should allow admin to reject a contract.

4. Non-Functional Requirements:

 Performance Requirements:
1. The system should be able to handle up to 10,000 concurrent users.
2. The response time for any client request should not exceed 2 seconds under normal load
conditions.
3. The system should be able to process 500 transactions per second during peak hours.
 Availability Requirements:
1. The system should be available 24/7, with a downtime of less than 0.1% annually.
2. The system should have a recovery time objective (RTO) of less than 1 hour in case of system
failure.
 Scalability Requirements:
1. The system should be able to scale to support an increase of up to 50% in the number of
users annually.
2. The system should be able to scale to support an increase of up to 100% in the volume of
data annually.
 Security Requirements:
1. The system should encrypt all sensitive data using industry-standard encryption algorithms.
2. The system should detect and respond to security incidents within 1 hour.
 Usability Requirements:
1. The system should have a user-friendly interface, with a learning curve of less than 1 hour
for new users.
2. The system should provide clear and concise error messages within 2 seconds of a user
making an error.
 Maintainability Requirements:
1. The system should allow for updates and patches to be applied with less than 1 hour of
downtime.
2. The system should have a mean time to repair (MTTR) of less than 4 hours.
 Reliability Requirements:
1. The system should have a mean time between failures (MTBF) of at least 500 hours.
2. The system should have a failure rate of less than 0.1%.

4. Actors/Service Provider:

8
 Customer
 Service Provider
 Admin

5. Technologies:

 HTML
 CSS
 JAVASCRIPT
 REACT
 MySQL