Online Job Portal Java Project Report & Source Code

Objectives of the project:

  • Registration
  • Login
  • Authenticating
  • Updating Profile
  • Posting a job and removing or modifying job
  • Searching for a job
  • Taking online exam
  • Feedback

LITERATURE SURVEY

There are many applications developed related to this Online Job Portal, but, however, these systems are very complex for their own purpose. Most of them do not have the centralized database and easy access to users. So in this project, we are implementing this application through a centralized database and easy-to-use access for job seekers and job providers. The administrator is the primary actor to maintain the database, and also accepts comments from job providers and job seekers to improve and develop the application’s graphical user interface. Registered job seekers can also take the company online exam. In addition, qualified applicants can be classified according to this system based on their qualifications and company requirements.

Limitations

• The current Online Job Portal system is not a fully computerized and manual system for entering job candidates and job provider data and managing it.
• There is no centralized database maintenance
• There is no easy access to records of people seeking work in particular
• Job seekers can not easily navigate through the database

Benefits

• It is a fully automated system for managing the Online Job Portal database
• This system provides centralized database maintenance
• This system provides easy access to certain job seekers or their complete details
This system gives job seekers easy to navigate through the application to get more information in the most secure way.

IMPLEMENTATION

5.1. MODULES

The system is divided into three major parts depending upon the requirement they are.

  • 1) Administrator
  • 2) Job Provider
  • 3) Job Seeker

Administrator

All the users are controlled by admin. Administrator services are

  1. view job providers
  2. view job seekers
  3. view feedback

Examination

The job providers prepared questions and update the providers and conduct examinations to the job seekers and also send the particular examination results.

And the job seeker searches the particular job then attends the exam and also views his results after completion of the exam.

Software Requirements: 

Operating System: Windows XP/2003 or Linux/Solaris

User Interface: HTML, CSS

Client-side Scripting: JavaScript

Programming Language: Java

Web Applications: JDBC, JSP

IDE/ Workbench: Eclipse with My Eclipse Plug-in

Database: Oracle

Server Deployment: Apache Tomcat 6.0

Screen Shots:

  • HOME PAGE
  • LOG-IN PAGE
  • ADMIN PAGE
  • JOB PROVIDERS IN DB
  • JOB SEEKERS IN DB
  • FEEDBACK PAGE
  • JOB PROVIDER PAGE
  • UPDATE PROFILE PAGE
  • ADD NEW VACANCY PAGE
  • SEARCH JOB SEEKER PAGE
  • RESULT PAGE FOR SEARCH JOB SEEKERS
  • EXAM MANAGEMENT PAGE
  • PREPARE EXAM PAPER PAGE
  • PREPARING QUESTIONS PAGE
  • ADDING QUESTIONS PAGE
  • RESULT PAGE FOR SEARCH JOBS
  • EXAM MANAGEMENT PAGE
  • TAKING EXAM PAGE

TEST CASE REPORTS 

Name of the page: Admin Login

Sno TEST CASE Expected Result Actual Output Remarks
 1 New Admin logged on without sign in. Should return a message sign in  before log in. Sign in First Success
2. Invalid password Enter correct password Wrong password Success
3. Invalid username Invalid User Enter valid name Success
4. Special character entered in password field. Verify your password You Entered Invalid password Success

Name of the page: Job provider Login 

Sno TEST CASE Expected Result Actual Output Remarks
 1 New provider tried to log on without sign up. Should return a message sign up  before log in. Failure
2. Invalid password Enter correct password Wrong password Success
3. Invalid username Invalid User Enter valid name Success
4. Special character entered in password field. Verify your password You Entered Invalid password Failure

 Job Seeker Login 

Sno TEST CASE Expected Result Actual Output Remarks
 1 New seeker tried to log on without sign up. Should return a message sign up  before log in. Failure
2. Invalid password Enter correct password Wrong password Success
3. Invalid username Invalid User Enter valid name Success
4. Special character entered in password field. Verify your password You Entered Invalid password Failure

Name of the page: Exam Management 

Sno TEST CASE Expected Result Actual Output Remarks
 1 Provider tried to add exam paper without scheduling Schedule first NULL Failure
2. Seeker tried to write same exam again exam already taken Can Write Failure
3. Displaying a message after time up in exam Time up Time up Success
4. Selecting exam before scheduling date Invalid test NULL Failure

 

Warehouse Management System Java Project

Warehouse Management System mainly consists of five modules

1. Master maintenance
2. Receiving
3. Shipment
4. Billing
5. Reports

Master Maintenance :

Warehouse Management maintains the following master details for various purposes.

i) Suppliers Details
ii) Sublocation Incharges Details
iii) Retailers Details
iv) Products Details

Receiving :

Warehouse Management receives the stock in a validated manner against Purchase Order & Receipt No. Warehouse management receiving process includes all the items necessary to receive, from unloading the trucks to recording the account. Warehouse Management can perform the following receiving tasks.

i) Purchase Order
ii) Goods Order

Shipment :

Warehouse Management provides you a number of functions to maintain the flow of goods in the warehouse.
The following tasks are caused under this module …

i) Transfer inventory
ii) Put inventory on hold
iii) View inventory balances
iv) View inventory transactions

Billing :

Warehouse billing process allows the retailer to generate new bills and also allows viewing of existing bills.

Reports :

The reports process allows the user to produce the reports necessary for day to day warehouse operations. The standard reports are …

i) Inventory Reports
ii) Purchase Order Reports
iii) Administrative Reports

Software Requirements:

Operating System: Windows
Technology: Java
Web Technologies: Html, JavaScript
Web Server: Tomcat
Database: Oracle

Oracle application Development for Mall managament

The following details regarding property management database requirements:

There are two types of property:
1) Weekend Outlets
2) Permanent Shops

1) Weekend Outlets: (Friday & Saturday)

  • These outlets are booked in a week(Monday to Thursday) before every weekend.(Friday & Saturday)
  • All outlets are registered to particular tenants. Tenant details will be entered in the system.
  • Receipts are issued on weekly basis or monthly basis.
  • For Monthly Basis, normally there are 4 weekends or sometimes 5 weekends. Based on that, the receipt will be issued accordingly.
  • 5 weekends for example in September( 2,3 Sep, 9,10 Sep, 16,17 Sep, 23,24 Sep & 30 Sep Oct 1.)
  • Monthly booking depends on 1st Friday of the month. for example, in September month booking would be from Sep 2 to oct1 (bcoz 30 sep is Friday, so it would be under September month)
  • Payment would be paid on weekend basis (Friday & Saturday combined), not on a daily basis.
  • Outlets can be booked for one week or one month only. booking cannot be done for 2 weeks or 3 weeks.
There would be 3 reports for weekend sheds:
1) Weekly Collection report( format is attached for your reference weekend sheds report data-6)
2) Outlet report for particular outlet(Tenant registration details, booking details, Violation details, etc)
3) New Application for Outlet.

2) Permanent Shops

Shops have a contract period of 2 years with one month grace period and balance 23 month PDC will be provided.
Procedures of contract:
  • New Shop request application would be prepared initially. It will be printed and signed by the tenant. The application will be uploaded along with other necessary documents of the customer to the system.
  • When the application is approved, the contract would be prepared and customer details will be forwarded from application to Particular shop details.
  • PDC will be entered into the system.
Current situation: There are existing contracts & few empty shops. Details should be entered manually for existing contracts and above procedures should be followed for new contracts.
There is an attachment with name Shop details-data 3. it contains all the headings required for each and every shop data. along with that, we need to have a link for image files for the data such as contract copy, identity copy, etc.
We should be able to add headings for shop details if there is any need in future.
Based on the shop details, we should be able to prepare the following reports.
  • Shop report for a particular shop
  • Shop active status report for combined shops together.( shop status will be updated by authorized user at the end of every month)
  • PDC Conversion report at the end of every month.
  • Return Cheque Details at the end of every month
  • Violation report for a particular shop
  • violation details issued in a particular month
Graphical data would be preferred for the monthly reports.
We should be able to generate all monthly reports with monthly data along with accumulated data over a period of time.
During a contract period, there could be various request application from tenants such as Change of Activity, Change of Contract Name, contract cancellation, etc.
These application additional data should be entered manually by the authorized user and printed. All the related documents will be saved along with the application.
All the above requests including new shop application & Outlet Application should be combined together to get the request details for that particular month.
 
Above details are Basic requirements. If you need more data or explanation about the above requirements, we are ready to provide.
 
Request if possible: If we could send the application number to tenant or customer contact no. through SMS on submitting the application would be more useful to us.

Activity Control System Java Project Abstract

The four main activates when working with Activity Control System are Registration of time expenses Task, Project and Customer Management Reporting System Administration.

The five main activities when working with Activity Control System are:

• Registration of time expenses
• Task, project, and customer management
• Reporting
• System administration

PROPOSED SYSTEM

We developed a final year project called Activity Control System. By this proposed system we could maintain the records by using Database. Where we had all the details of Customers, Projects and Tasks. Here we can generate reports, bills.

Activity Control System is time collection software that is streamlined for billing and invoicing purposes. Activity Control System allows time tracking for customer and project related tasks. After being collected the data can then be exported for invoice generation.

The proposed four main activities when working the Activity Control System are Registration of time expenses, Task, project and Customer Management, Reporting System Administration.

Software Requirements

Operating System : Windows XP
User Interface : HTML, CSS
Programming Language : Java
Web Applications : JDBC, Servlets, JSP
Database : Oracle/Access
Server Deployment : Tomcat

Hardware Requirements

Processor : Pentium IV
Hard Disk : 1600GB
RAM : 512MB or more

Insurance Company Management System

Objective:

The objective of the Insurance Company project is to automate the management of insurance activities of an insurance company. The purpose is to design a system using which users can perform all activities related to insurance company.

Proposed System:

This makes it convenient to access required data easily. Various reports can be generated by the managers. The system integrated all information related to various branches. Using the Insurance Company Management System customers can make online payments.

Modules:

The Insurance Management System is proposed to have the following modules.

CEO, Manager, Agent and Customer

CEO Module:

The CEO is the Super user of the System. The CEO is responsible for defining the policies, policy terms and conditions, policy amounts, establishing the different branches, registration of the branch managers. CEO will also get information about policy details, branch details, manager details, agents details, customers details, customers policy details

Manager Module:

Manager is responsible for all activities at a specific branch. A manager appoints agents and interacts with customers. A manager can get data about customer policies, dues and payment details. A manager can also get agent details and commission information. A manager can generate various reports.

Agent Module:

Agents are employees of the insurance company who interact with potential customers and offer the necessary details, agents typically act as a liaison between customers and company. Agents are entitled for commission for each policy they sell. Using the system an agent can find customers policy details, customer’s personal details, commission collected, reports, available policy details, concerned manager details and agent personal details.

Customer Module:

Each customer must register with the system before one can avail the services. Customers can seek information regarding policies, register new policies, make online payments, view their current policy details etc.

Software Requirements:-

  • Web Presentation : HTML, CSS
  • Client – side Scripting : JavaScript
  • Programming Language : Java
  • Web based Technologies : Servlets, JSP
  • Database Connectivity : JDBC
  • Java Version : JDK
  • Backend Database : Oracle
  • Operating System : Windows, LINUX
  • Web Server : Tomcat