Essay details:

  • Subject area(s): Engineering
  • Price: Free download
  • Published on: 7th September 2019
  • File format: Text
  • Number of pages: 2

Text preview of this essay:

This page is a preview - download the full version of this essay above.

An IDP Project Report On

Car Race Booking System

Prepared by

Kalavadiya Priyank Y.

(Enrollment No:  120320107045 )


Patel Chintan B.

(Enrollment No:120320107029 )


Sheth Mahammad Aakib M.

(Enrollment No:120320107036 )

Guided By:

Internal Guide External Guide

Prof. Shruti Raval  Mr. Narendra Patel

(Assistant Professor, CE Dept) (Igex Solutions)


L. J. Institute of Engineering & Technology


November -2015

L. J. Institute of Engineering & Technology

S.G. Highway, Ahmedabad-382210



The report entitled 'Car Race Booking System' prepared by Kalavadiya Priyank Y.,Patel Chintan B.,Sheth Mahammad Aakib M. for Project Phase-I (Semester - 7) for the partial fulfilment of degree of Bachelor of Engineering (Computer Engineering), has been carried out under my supervision in Department of Computer Engineering, L. J. Institute of Engineering & Technology. His/ Her present work has been found satisfactory.

Date of Submission: 26/10/2015

  Prof. Prof. Shruti Raval               Prof. Seema Mahajan

  Project Guide          Head of Department

  Assistant Prof, CE Dept.        Computer Engineering



We hereby certify that we are the sole authors of this IDP project report and that neither any part of this IDPproject report nor the whole of the IDPProject report has been submitted for a degree by other student(s) to any other University or Institution.

We certify that, to the best of our knowledge, the current IDP Project report does not infringe upon anyone's copyright nor violate any proprietary rights and that any ideas, techniques, quotations or any other material from the work of other people included in our IDP Project report, published or otherwise, are fully acknowledged in accordance with the standard referencing practices. Furthermore, to the extent that we have included copyrighted material that surpasses the boundary of fair dealing within the meaning of the Indian Copyright (Amendment) Act 2012, we certify that we have obtained a written permission from the copyright owner(s) to include such material(s) in the current IDP Project report and have included copies of such copyright clearances to our appendix.

We have checked the write up of the present IDP Project report using anti-plagiarism database and it is in the allowable limit. In case of any complaints pertaining to plagiarism, we certify that we shall be solely responsible for the same and we understand that as per norms, University can even revoke BE degree conferred upon the student(s) submitting this IDP/UDP Project report, in case it is found to be plagiarized.


Enrollment Number Name Signature

120320107045 Kalavadiya Priyank Y.

120320107029 Patel Chintan B.

120320107036 Sheth Mahammad Aakib M.



Name of Guide:Prof. Shruti Raval

Signature of Guide : _______________


No task can be accomplished without proper support, guidance and appraisal. We are highly thankful to many people who contributed either directly or indirectly for this project and provided their invaluable cooperation to us to complete it.

We would like to thank our Head of Department, Dr. Seema Mahajan and our faculty members of Computer Engineering for constantly guiding and showing us the correct way to reach towards the desired goal.

Then we would like to thank our Internal guide Prof. Shruti Raval who has helped us out in each every phase of the project and without their support and guidance the project would not have been completed successfully.

The wholehearted help and co-operation by our friends is gratefully acknowledged.

Kalavadiya Priyank Y.

Patel Chintan B.

Sheth Mahammad Aakib M.



Company Profile


1. List Of Figures

2. List Of Tables


Notations I






Chapter : 1 Introduction

1.1 Project Summary

1.2 Project Purpose

1.3 Project Scope

1.4 Project Objectives

1.5 Technology Review

1.6 Literature Review 1







Chapter : 2 Project Management

2.1 Project Planning

2.2 Project Scheduling

2.3 Risk Management

2.4 Canvas Designing

2.4.1 AEIOU Summary Activities Environment  Interactions Objects Users

2.4.2  Empathy Summary

2.4.3  Ideation

2.4.4 Product Development 11





Chapter : 3 System Requirements Study

3.1    User Characteristics

3.2    Hardware and Software Requirements

3.3    Specific Requirements

3.3.1 Functionality

3.3.2 Usability

3.3.3 Reliability

3.3.4 Performance

3.3.5 Supportability

3.3.6 Design Constraints

3.4     Assumptions and Dependencies 19











Chapter : 4 System Analysis

4.1 Requirements of New System

4.2 Feasibility Study

4.3 Requirements Validation

4.4 Features Of New System

4.5 For OO Approach (If you are following OO Design)

4.5.1 Class Diagram

4.5.2 System Activity Diagram

4.5.3 Use case Diagram

4.5.4 Sequence Diagram

4.5.5 Collaboration Diagram

Chapter : 5 System Design

5.1 Database Design

Chapter : 6 Limitation and Future Enhancement

6.1 Limitation

6.2 Future Enhancement 63



Chapter : 7 Conclusion and Discussion

7.1 Self Analysis of Project Viabilities

7.2 Problem Encountered and Possible Solutions

7.3 Summary of Project work

Chapter:8 References 67

Appendix 1: Periodic Progress Report

Appendix 2: Design Engineering Canvas

Appendix 3: PSAR Report IX




' This is a Web Application for online car race booking system. This is an online booking service for those people who are really passionate about Car Race. The day when Car Race is organized by organizer, that day is Drive Day. In this system, we provide the every details of the Drive Day which is hold by an organization. By this system, interested people can find all the information about the Drive Day.

' People, who are interested in the Car Race, can purchase coupons online which are provided on the other websites that is distributed by the organizer. Users can register in the system by email or phone number and can book the tickets by using coupon code. When user books the slot, the coupon codes deactivate from the database, and remove from the other websites.

' It is a web based application which is run on the any web browser like Google Chrome, Firefox, Internet Explorer, etc. It is built by using PHP CodeIgniter and MySql. The basic aim of this application is for user facility. This application is use anywhere at any time by connected users only, just user need their internet connection and rights of each other to access this application.

' Users, who are purchased the coupons, user can book slots from our website. After the registration, user is notified by email or text message. We provide the One Time Password (OTP), for the conformation after booking the ticket for the security purpose. User can get the OTP by email.

' User, for which Drive Day, he/she book the slot, will get the information on the email or get notification by text message before the Drive Day. User can get the information about the schedule, location, information about drivers and other information about the Drive Day.

' For any reasons, user wants to cancel his/her slots; he/she can cancel the slot from the website before the Drive Day. It will automatically update the database, and active the coupon code on the website.      


Company Profile

iGex Solutions is an established high-potential player with a rich experience in developing customized commercial grade products and applications spanning multiple industry.


' iGex is a team of highly qualified professionals.

' iGex houses latest IT Infrastructure.

' iGex uses Licensed software tools, to keep abreast of the latest technology and updates.

' iGex owns development capacity for open source and license software.

' iGex provides reliable 24x7 support to their clients with online customer care service, as it has clientele all over the world.

Technical Presentation:

' AGR Presentation.

' .NET

' iGex Presentation.

' Corporate Presentation Address:

428, Kalasagar Mall,

Near Sattadhar Cross Road,

Ghatlodia - 380061,

Ahmedabad, Gujarat, India.


List of Figures:


List of Tables:



' My Project definition is 'Car Race Booking System.' An Abbreviations of this application are as follows:

' Booking System: People book their slots online for the Drive Day

' Organizer: The Team responsible for developing the website

' OTP (One Time Password)

' Notification

' Cancel Registration

' Developers: The team responsible for developing software system.



' For Class Diagram:

Symbol Name





' For Activity Diagram:

Symbol Name

Action State

Initial State

Final State.


Object Flow

Control Flow

' For Use Case Diagram:

Symbol Name

Use Case




System Boundry

' For Sequence Diagram:

Symbol Name



Message Return

Object Lifeline

Symbol Name

Classifier Role

Association Role


' For Collaboration Diagram:




1.1 Project Summary

We are developing an online Car Race Booking System PHP based website. This website is using for view, book & search different types of Rally. We book the different types of rallies held in forest, desert, etc. We book slots for interested people for rally using coupons which are distributed on the different web-sites.  We are also providing a secure registration and profile management facilities for Customers. Our website providing online payment system through PayPal. We are regular updates to registered users about new rallies.Our website is to help of Users to get connected in their own region.

1.2 Project Purpose

The administration module will enable a system administrator to manage time date and locations for rallies.Secure registration and profile management facilities for Customers. Regular updates to registered users about new rallies. Our purpose is customer book race slots without go to any booking agent and booking a race in own house.

1.3 Project Scope

' The main Scope is Consumers who are interested in booking online race slot by PayPal.

' They can use this website to search the rallies, view race tracks.

' Users must register for book slot. .

' User can also managing their profiles & know about new rallies.

1.4 Project Objectives

Registration for the customers requires them to provide their personal details. The objective behind this is that the registered customer can get the updates regularly about the race to his/her registered number or email id. The registration of customers is confirmed by the Admin. The customer can search for a Drive Day of the rally interested after registration.

After searching, the customer can view the track of the selected rally and then book the slots

Booked slots will have to be confirmed by the Admin, the aim here is to avoid overlapping of multiple slot booking. Admin will send a confirmation e-mail to the customer through our own personalized mailing system, notifying the customer that their slots have been confirmed.

1.5 Technology Review

' Front End:


This is a web based application developed using technology PHP in the front end.

Fig. 1.5.1 php logo

' JavaScript

JavaScript is a high level, dynamic, untyped, and interpreted programming language. It has been standardized in

' Platform:

' CodeIgniter

Fig. 1.5.2 CodeIgnitor Logo

CodeIgniter is an open source rapid development web application framework, for use in building dynamic web sites with PHP.

' Back End:

' MySql

Fig 1.5.3 MySql Logo

1.6 Literature Review

1.6.1 Study of current Existing System:


o In this website, the organizer Brisbane Sporting Car Club Ltd organizes the rally in Queensland, Australia. In this system, organization gives the schedule of the rally, maintains the records of the rally and shows the result of the rally which is hold in Queensland. It provides the details of the sponsors and future rally schedule that is hold in Queensland.


o In this website, the organizer organizes the rally called FIA WRC-World Rally Championship in Australia. In this system, it gives the schedule information about the rally, keeps the track about rallies and provides the news and other media about the rally. It books the sits called the baskets. It also gives the information about the future events about the rally.


o In this website, the organizer organizes the car race at Coseley School and Leisure Centre. In this system, it provides the information about schedule of the race day, venue, and results. It keeps the records about the race that will hold in past. It books the tickets of rally by registration. It also provides the photo gallery of the race.

1.6.2 Limitation of Existing System:

' Very complicated sitemap.

' Inefficiency and estimation of cost.

' Very hard to use for new users.

' Does not provide secure transactions for payment.

' No cancellation facility.

1.6.3 Usability Of Project:

' To create simple, easy to use web application.

' To provide accuracy and precision with reduced human intervention.

' Anytime anywhere booking facility.

' 24 x 7 booking service.

1.6.4 Innovative Ideas Of Project:

' Secure payment system for every customer.

' Location for non familiar people with race venue.

' Cancellation facility

' Quick updates by notification of updates by email or sms.

' Conformation of the transaction by OTP

' Registration via coupons.




2.1 Project Planning:

2.1.1 Project Development Approach And Justification:

A systems development life cycle is composed of a number of clearly defined and distinct work phases which are used by systems engineers and systems developers to plan for, design, build, test, and deliver information systems. Like

Fig. Software Development Life Cycle

2.1.2 Project Plan:

We are planning our project completing in given time duration. We are also gathering customer's requirement and satisfying all that needs. We are using best functionality to developing this website. Required Database was designed and normalized as required. Code was written in such a way that maximum functionality was coded with minimum possible lines of code.

2.2 Project Scheduling:

Gantt chart:

Fig. 2.2.2 Gantt Chart

2.3 Risk Management:

2.3.1 Risk Identification:

All projects have risks. If a potential risk of the project is not identified early, then the project will be at high risk to complete as per schedule. Hence, it is the most important process in risk management planning.

2.3.2 Risk Analysis:

It is the second step of risk management. Impact is the effect of the risk in case it happens. There are some technical and business factors while assigning impact.

' Customer loss.

' Loss of business, financial loss.

' Hardware integration problems.

2.4 Canvas Designing:

2.4.2 AEIOU Framework:

Fig Activity Canvas

Fig Environment Canvas

Fig Interaction Canvas

Fig Object Canvas

Fig User Canvas

2.4.2 Empathy Summary:

2.4.3 Ideation:

2.4.4 Product Development:



3.1User Characteristics:

' Customer:

Customer as an actor demands for particular product along with specification of all the requirements. Customer can:

' Create a new product request.

' Specify all requirements

' Optionally attach design specifications

' View all past request and its details.

' Admin:

The main job of an administrator is to manage the tasks performed by the user. Admin performs the following tasks:

' Creating whole systems.

' Configure all the parameters for displaying information.

' Configure role of the user be it the employee or the customer.

3.2 Software Requirements:

' Technology: PHP

' Language: PHP, Java Script, jQuery

' For Development: CodeIgniter

' Back End: MySQL

3.3 Specific Requirements:

3.3.1 Functionality:

' All requirements are very well known, clear and fixed.

' Whole technology should be understood.

' Code simplicity is one the best feature to understand the coding phase.

' Login, Registration will be done efficiently.

' The important key is contact number, verified the number or register the number.

' Logout.

  3.3.2   Usability:

' The whole system takes an hour to understand all requirements, specifications and functionality for a normal user.

' Developers need to be up-skilling and expected to bring great code to an organization.

' Developers must follow the specific standards, which the technology is used.

   3.3.3   Reliability:

' Maintainability: If any requirement occurs, then it should be easily incorporated in the system.

' Portability: The application should be portable on any browser

    3.3.4 Performance:

' Response time for transaction: This term represents the time for a database transaction. This application will take one to two seconds (average) for database transaction.

' Capacity: The system can accommodate around the many customer's capacity in this application.

' Resource Utilization: This application contain resources like,

o Laptop, mobile, tablet, etc.

o Communication is done through internet

' Cost Sensitivity: Under all circumstances, the maximum cost payable as submitted by the user will be the maximum cost charged to the user.

3.3.5 Supportability:

This section includes following supportability requirements:

' Naming Conventions:  All code will be written as specified by the Pascal Naming Convention (for Class name and Methods name), Camel Casing Convention (Method arguments and local variables) and Hungarian Naming Convention (Data type identification).

' Coding Standards: All codes will be written as required by the php Coding Standards.

' Cost-Effective-To-Maintain: It may covers divers level of documentation, such as system documentation as well as test documentation.

3.3.6 Design Constrain

There are many aspects of any design project that must be considered to determine the feasibility of the system.

Software Language: All coding will be done in standard of php platform.

Scheduling Constraints: Exhaustive searches of the entire set of combinations of jobs will not be done. Heuristics will be developed for this scheduling problem.

3.4 Assumptions and Dependency

There are no assumptions in this web application.



4.1 Requirements Of New System:

4.1.1 User Requirements:

User must be aware the system works properly with full availability, reliability, security and safety. The user responsibilities are as follows:

' Should know the data needed to address the problem.

' Should know how to use it.

' Should adhere to guidelines and prescribed standard.

4.1.2 System Requirements:

This web application is designed to booking the slots of race . It must fulfill all the functional and non-functional requirements.

4.2 Feasibility Study:

4.2.1 Technical Feasibility:

Technical feasibility determines whether the work for the project is being done with the present equipment, current procedures, existing software's technology and available persons or not. Thus it is important to check the system to be technically feasible.

System would be implemented using php technology which is quite easy to use and user friendly IDE CodeIgnitor.

' Software Platform:

o Database server- MySql

o Technologies- PHP

' Development Tool:

o CodeIgnitor

4.2.2 Economical Feasibility:

Economic feasibility looks at the financial aspects of the project. Economic feasibility concern with returns from the investments in project.

The software resources requirements for the proposed system is PHP development environment, MySql that are already owned by the client and do not require additional investment.

4.2.3 Implementation Feasibility:

Implementation feasibility deals with the study whether the service, which is being developed will run in the environment available with us, will the management of the organization approve the system?

Implementation feasibility is about basic infrastructure and material required to develop the system. It is found that:

' Infrastructure provided was a high configuration computer system to implement the application.

' The required software's like CodeIgnitor, MySql is provided.

' Literature like books, technical manuals and reports.

' Proper and timely guidance was provided by the guide.

4.3 Requirements Validation:

It is a process in which it is checked that gathered requirements represents the same system that customer really wants or it is showing different. The basic objective of requirement validation is that the SRS reflects the actual requirements correctly and accurately.

The common methods for requirement validation are as follows:

' Requirement Review:

It is review by group of people to find errors and point out other matters of concern. It may be formal or informal.

' Prototype:

The requirements can be checked using executable model of the system. Prototype which is build during analysis, can be used for requirement validation.

' Test Case Generation:

In this technique, various tasks are developed for requirements and they are- Verifiability, Comprehensibility, Traceability and Adaptability.

4.4Features of New System:

' It is an system which is for specific organization.

' Provide easy navigation and user-friendly interface:

' Payment Gateway Integration :

4.4 Object Oriented Approach:

Fig 4.5.1 Activity Admin

Fig. 4.5.2 Activity User

Fig 4.5.3 Collaboration Admin

Fig 4.5.4 Collaboration User

Fig. 4.5.5 Sequence Admin

Fig. 4.5.6 Sequence User

Fig 4.5.7 Use case



5.1 Database Design:

5.1.1 Admin_Master

Description: To store the login id and password and name of admin.

Primary Key: UserId

Field Name Data Type (With Size) Constraint

UserId int Primary key

UserName varchar(50) Not Null

Password varchar(50) Not Null

IsActive bit Not Null

UserType int Not Null

CreatedDate datetime Not Null

ModifiedDate datetime Not Null

Table 5.1.1

5.1.2 BookingMaster:

Description: to store the Detail of Booking.

Primary Key: BookId

Field Name Data Type (With Size) Constraint

BookId int Primary Key

CustId int Foreign Key

SlotId int Not Null

VoucherNo varchar(50) Not Null

IsConfirmed bit Not Null

CreatedDate datetime Not Null

ModiifiedDate datetime Not Null

Status varchar(25) Not Null

TransId varchar(25) Not Null

Amount decimal(10, 2) Not Null

IsCustParticipant bit Not Null

PartName varchar(50) Not Null

PartEmail varchar(50) Not Null

PartPhoneNo varchar(12) Not Null

IsCancelled bit Not Null

IsSendNotiToRecipient bit Not Null

Table 5.1.2

5.1.3 CMS Master:

Description: To Store the detail of company contact detail

Primary Key:ComapnyId

Field Name Data Type (With Size) Constraint

CompanyId int Primary Key

CompanyName varchar(50) Not Null

ContactPerson varchar(50) Not Null

ContactNO varchar(12) Not Null

CreatedDate datetime Not Null

ModifiedDate datetime Not Null

Table  5.1.3

5.1.4 Company Master:

Description: To store Company Details

Primary Key: CompanyId

Field Name Data Type (With Size) Constraint

CompanyId int Primary key

CompanyName varchar(50) Not Null

ContactPerson varchar(50) Not Null

ContactNO varchar(50) Not Null

CreatedDate datetime Not Null

Table 5.1.4

5.1.5 Table Name:  Course_Master

Description: To store the Detail Of Course or Race..

Primary Key: CourseID

Field Name Data Type (With Size) Constraint

CourseID int Primary key

CourseName varchar(50) Not Null

LocationID int Foreign Key

Price decimal(10, 2) Not Null

CreatedDate datetime Not Null

ModifiedDate datetime Not Null

Table 5.1.5

5.1.6 Table Name:  Course_Master

Description: To store the Detail Of Course or Race..

Primary Key: CourseID

Field Name Data Type (With Size) Constraint

CourseID int Primary key

CourseName varchar(50) Not Null

LocationID int Foreign Key

Price decimal(10, 2) Not Null

CreatedDate datetime Not Null

ModifiedDate datetime Not Null

Table 5.1.6

5.1.7 Table Name:  CustDetai

Description: To store the details of customers

Primary Key: CustId

Field Name Data Type (With Size) Constraint

CustId int Primary key

RaceId varchar(50) Foreign Key

CustName varchar(50) Not Null

Email varchar(50) Not Null

Password varchar(50) Not Null

PhoneNo varchar(12) Not Null

VoucherNo varchar(15) Not Null

CreatedDate datetime Not Null

ModifiedDate datetime Not Null

IsBookingConfirmed bit Not Null

IsEmailConfirmed bit Not Null

IsActive bit Not Null

EmailVerificationCode varchar(20) Not Null

Street varchar(120) Not Null

City varchar(20) Not Null

Postcode varchar(20) Not Null

State varchar(20) Not Null

5.1.8 Table Name:DealMaster

Description: To store the details of Maps

Primary Key: DirectionID

Field Name Data Type (With Size) Constraint

DirectionID int Primary Key

Title varchar(200) Not Null

TextColumn varchar(5000) Not Null

LocationID int Not Null

DirectionMap varchar(200) Not Null

CreatedDate datetime Not Null

ModifiedDate datetime Not Null

TripNoteFile varchar(200) Not Null

Table 5.1.8

5.1.8 Table Name:DirectionMaster

Description: To store the details of Maps

Primary Key: DirectionID

Field Name Data Type (With Size) Constraint

DirectionID int Primary key

Title varchar(50) Not Null

TextColumn varchar(50) Not Null

LocationID int Foreign Key

CreatedDate datetime Not Null

ModifiedDate datetime Not Null

DirectionMap varchar(200) Not Null

Table 5.1.8

5.1.9 Table Name:ErrorList

Description: To store the details of errors

Primary Key:ErrorId

Field Name Data Type (With Size) Constraint

ErrorId bigint Primary Key

ErrorCode varchar(50) Not Null

ErrorDate datetime Not Null

ErrorName varchar(250) Not Null

EventName varchar(50) Not Null

IPAdd varchar(50) Not Null

PageUrl varchar(250) Not Null

Table 5.1.9

5.1.9 Table Name:LocationMaster

Description: To store the details of location

Primary Key:LocationId

Field Name Data Type (With Size) Constraint

LocationID int Primary Key

LocationName varchar(10) Not Null

CreatedDate datetime Not Null

ModifiedDate datetime Not Null

ModifiedBy int Not Null

Table 5.1.9

5.1.10 Table Name:  MessageMaster

Description: To store the Detail of the message

Primary Key: MessageID

Field Name Data Type (With Size) Constraint

MessageID int Primary key

Message varchar(500) Not Null

Table 5.1.10

5.1.11 Table Name:  RaceSlot

Description: To store the Detail Of Race Slot

Primary Key: SlotID

Field Name Data Type (With Size) Constraint

SlotID int Primary key

LocationID int Foreign Key

CourseID int Foreign Key

StartDate datetime Not Null

StartTime varchar(20) Not Null

EndTime varchar(20) Not Null

Status varchar(200) Not Null

NoOfSeat int Not Null

CreatedDate datetime Not Null

ModifiedDate datetime Not Null

BookedSeat int Not Null

MoveNotes varchar(MAX) Not Null

IsDeleted bit Not Null

IsCancelled bit Not Null

Table 5.1.12

5.1.13 Table Name:  SiteSetting

Description: To store the Detail Of Site..

Primary Key: SettingID

Field Name Data Type (With Size) Constraint

SettingID int Primary key

NoOfDays int Not Null

EmailForNotification varchar(50) Not Null

Password varchar(50) Not Null

HostName varchar(50) Not Null

CancelationCharegDays int Not Null

CancellationPercet Decimal(5,2) Not Null

PaypalID varchar(100) Not Null

SMSHttpApi varchar(100) Not Null

EmailSignature varchar(100) Not Null

LblForCoupon varchar(100) Not Null

DaysbeforeRegStop int Not Null

Table 5.1.13

5.1.14Table Name:  tblfaq

Description: To store the Detail of frequently asked questions

Primary Key: FaqId

Field Name Data Type (With Size) Constraint

FaqId int Primary key

Question varchar(500) Not Null

Ans varchar(500) Not Null

Table 5.1.14

5.1.15 Table Name:  VoucherMastr

Description: To store the Detail of the voucher..

Primary Key: VoucherID

Field Name Data Type (With Size) Constraint

VoucherID int Primary key

VoucherNo varchar(25) Not Null

Status smallint Not Null

CreateDate datetime Not Null

ModifiedDate datetime Not Null

RaceID int Not Null

Cancelpercent int Not Null

CouponPrice decimal(10, 2) Not Null

PurchaserName varchar(100) Not Null

StateId int Not Null

DealId varchar(100) Not Null

ActivationCount int Not Null

Table 5.1.15


Limitation and Future Enhancement


' Lot of mundane and repetitive work.

' Inefficiency and estimation of cost.

' Maintenance of records for future references.

' Internet connection loss.

' Payment error occurs if slow internet connection.

6.2 Future Enhancement:

' Can provide facility of chatting for quick answer asked by user.


Conclusion and Discussion

7.1 Self Analysis  Of  Project Viabilities:

When studied about current system, some draw backs are to be found;

' Inefficiency and estimation of cost.

' Maintenance of records for future references.

' Loss of connection may be occurred.

7.2 Problem Encountered And Possible Solutions:

Problems Possible Solutions

Slow Internet Connection Use High Internet Connection

Payment error Use High Internet Connection

Leak of data

Protection of data.

7.3 Summary of Project:

For this project, I have completed the whole analysis phase which includes Project Report, All GTU PMMS Activities (PPR, PSAR, PLAGIARISM, CANVAS).


...(download the rest of the essay above)

About this essay:

This essay was submitted to us by a student in order to help you with your studies.

If you use part of this page in your own work, you need to provide a citation, as follows:

Essay Sauce, . Available from:< > [Accessed 17.02.20].