eJobs-UrbanClap.pptx

IPS - On Demand Service
Booking (e-Jobs)
Under The Guidance Of
Proff. Vivek Dave
Submitted To:
Department of MCA
Faculty of IT & Computer Science,
PARUL University
Developed By
Amit Sinha (190511201750)

2
Index
1. Project Profile
2. Requirement Analysis
3. Design
4. Implementation
5. Testing
6. Future Enhancement
7. Bibliography
PIET-MCA (IPS - ON DEMAND SERVICE BOOKING (E-JOBS))
4/19/2023

4/19/2023
PIET-MCA (IPS - ON DEMAND SERVICE BOOKING (E-
JOBS))
3
IPS - On Demand Service Booking (e-Jobs) for Home or Office.
1. Project Profile
1.2. Project Description:
1.1. Project Definition
This eJobs application is an android based application and its
purpose is to provide the users with efficient services online. The
application will allow the user to log in and look for the related
service section to hire help. The application will also allow the
service providers to register and make a profile so that they are
easy to find and contacted accordingly.
4/19/2023

4/19/2023 PIET-MCA (IPS - ON DEMAND SERVICE BOOKING (E-JOBS)) 4
This application is beneficial for both customers and service
providers because it will efficiently get the job done and is a
better marketplace for the service providers.
The application will help in services that are as small as an
electrician job and as big as a housing project planner etc.
This application will have a user-friendly interface so that it is
easy to understand and people with very less mobile
knowledge can also use it easily. The main purpose of this
application is to erase the need to physically go somewhere
to get some help, why go somewhere to hire someone when
it’s all just one click away.

A. Front End
 Visual Studio Code
 React Native
 React JS
A. Front End
 .Net MVC Web API
1.3. Tools and Technology

4/19/2023
PIET-MCA (IPS - ON DEMAND SERVICE BOOKING (E-JOBS)) 6
2. Requirement Analysis
2.1. Feasibility Studies
• Technical Feasibility
• Economic Feasibility
• Operational Feasibility
• Admin
• Vendor(Service Provider)
• Consumer(Customer)
2.2. Users of the System
4/19/2023

• Login
• Task Management
• User Management
• Services Management
• Payment
• Feedback Management
• Notification
2.3. Modules

2.4. Hardware & Software Requirements
Hardware requirement
1. Server Side
A. Hardware Requirements
● Processor : i3 or higher
● RAM : 4 GB or more
● Memory : 250 GB or higher
● System Type : 64-bit Operating System, x64-based
Processor

B. Software Requirements
● Tools : Visual Studio Code
● Web API : .Net MVC Web API
● Reports : Dialog Flow by Google
● Web Browser : Google Chrome, Mozilla Firefox
C. Documentation Software
 MS Office 2019

2. Client Side
A. Hardware Requirements
● RAM : 4 GB or more
● Memory : 100 GB or higher
● System Type : 64-bit Operating System, x64-based
Processor
B. Software Requirements
● Web Browser : Google Chrome, Mozilla Firefox,
Android, iOS

2.5. Use Case Diagram
Admin

Consumer

Vendor

3. Design
3.1. Use Case Scenario
Use Case Description
Id 1
Name Login/Registration
Actor Admin/Service Provider/Customer
Pre-Condition Admin / Service Provider / Customer a Login and
Service Provider/Customer Signup in the system
Success End
Condition
Email for Successful Signup/ Homepage for Login
Failed End Condition Error Message for Failure with Reason
1. Registration/Login

Id 2
Name Profile Update
Pre-Condition Admin/Service Provider/Customer makes changes to
their profile
Success End
Condition
Profile Page with update message
Failed End Condition Profile Page with failure message
2. Profile Update

Id 3
Name Services
Pre-Condition Admin can Add Services into the system
Customer can Book Services
Service Provider Provide Services
Success End
Condition
Services Add & Book successfully
Failed End Condition Fail to Book & Add Services
3. Services

Id 4
Name Feedback
Pre-Condition Admin & Service Provider Can view the Feedback.
Customer give feedback
Success End
Condition
Feedback sends successfully
Failed End Condition Feedback not send
4. Feedback

Id 5
Name Payment
Pre-Condition Admin & Service Provider Track the Payment details.
Customer do the Payment
Success End
Condition
Payment Successfully
Failed End Condition Payment Failed
5. Payment

3.2 UML Diagram
3.2.1. Class Diagram

3.2.2. Sequence Diagram

3.2.3. Activity Diagram

3.2.4. Collaboration Diagram
Admin Collaboration Diagram

Customer Collaboration Diagram

Service Provider Collaboration Diagram

3.2.5. Package Diagram

3.2.6. Deployment Diagram

3.2. Entity Relationship Diagram

3.2. Entity Relationship Diagram
admin
Column Type Constraints Description
id int Primary Key,
Not NULL
Id
username Nvarchar
(20)
NULL Admin Name
Email Nvarchar
(30)
NULL Admin Email
password Nvarchar
(10)
NULL Password

Payment
PId int (11) Primary Key,
Not NULL
Id
BkId Int (11) Foreign key, Not
NULL
Booking ID
Status Nvarchar
(50)
NULL Status

Cid int Primary Key,
Not NULL
Consumer Id
UserName Nvarchar (20) NULL Consumer User Name
Email Nvarchar (30) NULL Consumer Email
Password Nvarchar (20) NULL Consumer Password
Contact Nvarchar (10) NULL Contact No. of Consumer
City Nvarchar (20) NULL City name of Consumer
Address Nvarchar (20) NULL Address of Consumer
Image Nvarchar (100) NULL Profile Photo of Customer
Consumer

Services
Svid int Primary Key, Not
NULL
Id
Category Nvarchar (10) NULL Service Name
Title Nvarchar (20) NULL Title of Service
Price Money NULL Service Price
Time Time (7) NULL Condition of Services
Serviceimg Nvarchar
(100)
NULL Services image

Vendor
vid Int Primary Key, Not NULL Vendor Id
UserName Nvarchar (10) NULL Vendor User Name
Email Nvarchar (20) NULL Vendor Email
Contact Nvarchar (10) NULL Vendor Contact
Number
Degree Nvarchar (10) NULL Vendor Degree
Experience Nvarchar (10) NULL Working Experience
Address Nvarchar (50) NULL Vendor Address
City Nvarchar (20) NULL Vendor City
UserImg Nvarchar (100) NULL Vendor Profile Image
DegreeImg Nvarchar (100) NULL Vendor Degree Image
Password Nvarchar (50) NULL Vendor Password

Banner
Id Int Primary Key, Not NULL Banner Id
Title Nvarchar (10) NULL Banner Title
Type Nvarchar (10) NULL Banner Type
Category Nvarchar (20) NULL Banner Category
Image Nvarchar (500) NULL Image Of banner

Category
cgid int Primary Key, Not
NULL
Category Id
Title Nvarchar (10) NULL Title of the Category
Description Nvarchar (50) NULL Description of Category
Image Nvarchar (100) NULL Photos of Image
Category

Booking
Bkid int Primary Key, Not NULL Booking Id
Cid Int Foreign key, Not NULL Customer Id
Vid int Foreign key, Not NULL Vendor Id
Status Nvarchar (10) NULL Booking Status

4. Implementation
4.1. Form Layouts
1.Splash Screen Page

2. Landing Page

3. Login Page

4. Registration Page

5. Customer Home Page

6. Services Page

7. Services Description Page

8. Booking Services Page

9. Admin Login Page

10. Admin Dashboard Page

11. Add Banner

12. Add Vendor

13. Add Services

14. Order History
4.1. Report Layouts

15. Order History Print

15. Order History in Pdf

15. Profile Page

15. Share Application Details

15. Share Application Details in WhatsApp

15. View Services

15. View Users Details

15. Company Location Page

4.3. Coding Convention (Business Logic)
using Dapper;
using HelpExpert.comman.Models.Auth;
using HelpExpert.comman.Models.Consumer.User;
using HelpExpert.comman.Models.Vendor;
using HelpExpert.comman.Repositories.Interface;
using System;
using System.Collections.Generic;
using System.Configuration;
using System.Data;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace HelpExpert.comman.Repositories
{
public class AuthRepo : IAuthRepo
{
private readonly IDbConnection _dbConnection;
public AuthRepo(IDbConnection dbConnection)
{
_dbConnection = dbConnection;
}
public async Task<ConsumerInfo> Login(Login login)
{var Query = LoginQuery(login.UserType);
var UserData = await _dbConnection.QueryFirstOrDefaultAsync<ConsumerInfo>(Query,
new { @email = login.Email, @password = login.Password });
return UserData;}

public async Task<Guid> CreateToken(int id, int Usertype, string tokenType)
{var token = Convert.ToInt32(ConfigurationManager.AppSettings["TokenExpires"]);
DateTime expiresOn = DateTime.UtcNow.AddMinutes(token);
var sqlQuery = CreateTokenQuery();
var guid = Guid.NewGuid();
await _dbConnection.ExecuteAsync(sqlQuery, new
{@accessToken = guid,
@userID = id,
@userType = Usertype,
@expired = false,
@tokenType = tokenType,
@expiresOn = expiresOn,
});
return guid;}

private static string LoginQuery(int type)
{
var sqlQuery = new StringBuilder();
if (type == 1)
{
sqlQuery.Append(@"Select * from dbo.Consumer where Email=@Email and
Password =@Password");
}
else if (type == 2)
{
sqlQuery.Append(@"Select * from dbo.Vendor where Email=@Email and Password
=@Password");
}
return sqlQuery.ToString();
}

private static string CreateTokenQuery()
{
sqlQuery.Append(@"INSERT INTO
AuthToken(AccessToken,UserID,UserType,Expired,TokenType,ExpiresOn)
VALUES(@accessToken,@userID,@userType,@expired,@tokenType,@expiresOn);");
return sqlQuery.ToString();}
public async Task<String> CheckUserExist(VerifyContect contact)
{
var Query = UserExistQuery(contact.Usertype);
var Exist = await _dbConnection.QueryFirstOrDefaultAsync<String>(Query, new {
@email = contact.Email });
return Exist;
}

private static string UserExistQuery(int usertype)
{
if (usertype == 1)
{
sqlQuery.Append(@"Select Id,Email from dbo.Consumer where Email=@Email");
}
else if (usertype == 2)
{
sqlQuery.Append(@"Select Id, Email from Vendor where Email=@Email");
}
}

public async Task<int> CreateConsumerUser(ConsumerInfo coninfo)
{ try
{ var Query = CreateConsumerUserQuery();
int user = await _dbConnection.ExecuteScalarAsync<int>(Query, new
{ @name = coninfo.UserName,
@email = coninfo.Email,
@phoneno = coninfo.Contact,
@address = coninfo.Address,
@city = coninfo.City,
@password = coninfo.Password,
@image = coninfo.Image, });
return user;}
catch (Exception e)
{throw e;}}

private static string CreateConsumerUserQuery()
{
sqlQuery.Append(@"INSERT INTO Consumer
values(@name,@email,@phoneno,@address,@city,@password,@image);SELECT Id from
Consumer where Email=@email;");
}
public async Task<String> CheckConsumerUserExist(string email)
{
var Query = UserConsumerExistQuery();
@email = email });
return Exist;
}

private static string UserConsumerExistQuery()
{var sqlQuery = new StringBuilder();
sqlQuery.Append(@"Select Email from dbo.Consumer where Email=@Email");
}
public async Task<ConsumerInfo> GetConsumerUserdata(int conId)
{ var Query = GetConsumerUserDataQuery();
ConsumerInfo Exist = await
_dbConnection.QueryFirstOrDefaultAsync<ConsumerInfo>(Query, new { @c_id = conId });
return Exist;
}private static string GetConsumerUserDataQuery()
{var sqlQuery = new StringBuilder();
sqlQuery.Append(@"Select * from dbo.Consumer where Id=@c_id");
return sqlQuery.ToString();}

public async Task<int> CreateVendorUser(VendorInfo info)
{try {var Query = CreateVendorUserQuery();
int user = await _dbConnection.ExecuteScalarAsync<int>((string)Query, new
{ @name = info.UserName,
@email = info.Email,
@phoneno = info.Contact,
@city = info.City,
@address = info.Address,
@password = info.Password,
@image = info.Image,
@status = info.Status,
@adharnum = info.AdharNumber,
@adharimage = info.AdharImage,
@adharstatus = info.AdharVerifyStatus, });

return user;
}
catch (Exception e)
{ throw e; }
}
{
sqlQuery.Append(@"INSERT INTO
Vendor(UserName,Email,Contact,City,Address,Password,Image,Status,AdharNumber,AdharIm
age,AdharVerifyStatus)
values(@name,@email,@phoneno,@city,@address,@password,@image,@status,@adharnu
m, @adharimage,@adharstatus);SELECT Id from Vendor where Email=@email;");
}

public async Task<string> CheckVendortUserExist(string email)
{
var Query = UserVendorExistQuery();
@email = email });
return Exist;
}
private static string UserVendorExistQuery()
{
sqlQuery.Append(@"Select Email from dbo.Vendor where Email=@Email");
}

public async Task<VendorInfo> GetVendorUserdata(int deliveryId)
{
var Query = GetVendorUserDataQuery();
VendorInfo Exist = await _dbConnection.QueryFirstOrDefaultAsync<VendorInfo>(Query,
new { @d_id = deliveryId });
return Exist;
}private static string GetVendorUserDataQuery()
{
sqlQuery.Append(@"Select * from dbo.Vendor where Id=@d_id");
}
}
}

5. Testing
Test Case ID TC001
Test Case Summary This test case was conducted for checking Admin login.
Related Requirement RS001
Prerequisite Admin must be registered in system.
Test Procedure 1. Enter the Email and password.
2. Check the Email & Password correct ornot.
3. Click on loginbutton.
Test Data Email: admin@gmail.com
Password: ********
Expected Result Admin enters into the system.
Actual Result Admin can view the home page.
Status Pass
Remarks This test case is for login into the system.
Created By Amit Sinha
Date of Creation 05/02/2021
Executed By Amit Sinha
Date of Execution 05/03/2021
Test Environment Android Emulator
1. Admin Login

Test Case ID TC002
Test Case Summary This test case was conducted for checking User login.
Prerequisite User must have to register into the system.
Test Procedure 1. Enter the Email and password.
2. Check the Email & Password correct ornot.
3. Click on loginbutton.
Test Data Email: amit@gmail.com
Password: ********
Expected Result Users enter into the system.
Actual Result Users can view the home page.
Status Pass
Remarks This test case is for login into the system.
Created By Amit Sinha
2. User Login

Test Case ID TC003
Test Case Summary This test case was conducted for Registration of User.
Test Procedure 1. Enter First Name, Last Name, Email, Phone No. and Password.
2. Click on add button.
Test Data Username: Amit, Email: amit@gmail.com , Phone: 9998316492
Address: Ognaj, Gota Vasant Nagar
City: Ahmedabad
Password: ********
Expected Result Add expert in system.
Actual Result Users registered into System successfully.
Status Pass
Remarks This test case for Registration of user.
Created By Amit Sinha,
3. User Registration

4. Booking Services
Test Case ID TC004
Test Case Summary This test case was conducted for Services Booking.
Test Procedure 1. Enter Username, Mobile, Email, Address Phone No.
2. Click on Booking button.
Test Data UserName: Amit
Email: amit@gmail.com
Phone: 9998316492
Address: Ognaj, Gota Vasant Nagar
City: Ahmedabad
Vid: 102
SvId: 2
Expected Result Booking Service Successfully
Actual Result Booking Services into System successfully.
Status Pass
Remarks This test case for Booking Service.
Created By Amit Sinha,

 In future I will improve the Message functionality.
 In Future I Will be adding Sharing Information functionality.
 In Future I will be going to Live Tracking in Future. On the Basis
Consumer can track the vendors
 As well a I will provider Proper Update to Customer for great UI
and new Functionality Experience
6. Future Enhancement

7. Bibliography
 Web Links:
o https://reactjs.org/
o https://www.w3schools.com/REACT/react_intro.asp
o https://reactnative.dev/docs/getting-started
o https://github.com/facebook/react-native
o https://www.tutorialspoint.com/react_native/index.htm
o https://www.javatpoint.com/react-native-tutorial

 Videos Links:
o https://www.youtube.com/channel/UC80PWRj_ZU8Zu
0HSMNVwKWw
o https://www.youtube.com/channel/UCWv7vMbMWH4
-V0ZXdmDpPBA
 Documentation Links:
o https://app.creately.com/diagram/
o https://app.genmymodel.com/
o https://app.diagrams.net/

4/19/2023 81
Thank You!
A Presentation By
Amit Sinha

eJobs-UrbanClap.pptx

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to eJobs-UrbanClap.pptx

Similar to eJobs-UrbanClap.pptx (20)

Recently uploaded

Recently uploaded (20)

eJobs-UrbanClap.pptx