Siva Project
Siva Project
Project Summary :
● The aim and objective of the application are to develop a system in which
job applicants and recruiters can communicate with each other. An Online
Job Portal is a platform where job seekers can register themselves and
search for suitable jobs. In contrast, employers register with the website
and fill vacant positions at their company. It is a package to be used by
agencies to improve the efficiency of a business. The system provides a
jobs catalog and information to members and helps them decide on the
jobs to apply for. The Admin and employers can keep the jobs catalog
updated so that the job seekers get the updated information all the time.
Why I chose this project ?
Structure
○ generateProfile()
○ updateProfile()
○ addEducation()
○ applyJob()
○ searchLanguage
()
○ addLanguage()
○ searchJobs()
Database
design
Basic
Workflow
Tools and Framework :
● Java SE 17.0. 2
● JDBC 4.3
● MYSQL 8.0
Why Java
● Java has a cleaner, more restrictive model - as a language. It was
designed to do OOPS.
Why MySQL
● In this project, all data are fixed, structured, and have complex
relationships. Also, modifications in a schema are occasional.
● MySQL's fixed and structured data schema provides greater consistency
and reliability than most databases. Another great benefit of using MySQL
is its superior data security due to ACID-compliant transactions,
● So in this project, I need to update more than one document or collection
per user request if I use MongoDB. It may lead to corrupted data, as there
is no ACID guarantee. MySQL is a mature and reasoned solution to ensure
data privacy and integrity.
Challenges Faced :
● Making complex relationships between more data.
● standard methods implementation of different user types
● More time is required to build around 7200 lines in a short period .
● implementation of search and sort filter in command-line is more
challenging
● Tracking every possible function for each class and making standard
functions fields as abstract in the parent class to be overridden in child
classes.
● Tracking every possible case of retrieving an enormous amount of data for
a previous page to be in control where the retrieved data can go redundant
on the next page.
● More confused in making indexes for fields in the table, which may be
redundant most time when a complex query occurs.
● difficulty in testing the performance of the app with importing the more
significant data into MySQL
Future Scope of this Project: