Online Library Management System (Summer Project using J2EE) Source Code

This is a website project created by the University students especially for the students of college campus.
Here a student can Search, Apply, Reserve or Cancel the Reservation for the Library books.
The Student must sign in with their College Library username and password to access these services.

High-Level Design

1. Login:

It accepts the username and password and checks them. There are two types of users: Administrator and Student.
There are three attempts if the supplied input is wrong.

2. Main Module:

This is the main screen window which contains different menus for a particular user.
The main module contains several sub-modules like adding/deleting users or books to the database, issuing/returning books.

3. Student module:

3.1 Search: Search a book.
3.2 Apply: If the book is available to apply for the book.
3.3 Reserve: If the book is not available to reserve it.
3.4 Cancel: Cancel the request for the book.

4. Student Record :

Contains the details about book issue, return and fines etc
4.1 Issue: Issuing the book
4.2 Return: Returning the book.
4.3 Status: Status about the borrowers and pending requests etc.
4.3 Report: Generating the report.

5. Data Entry :

This includes sub-modules for adding/deleting the users and books to the database.
5.1 Books :Add/Update/delete the books
5.2 Users : Add/Update/Delete users

6. User Accounts :

It includes sub-modules for adding or changing the username and passwords for the users, enabling and disabling etc

Unit Test Plan For Online library management system

Sl No Test  Case Name Test Module Expected Result
   1 Login_fnValidate_Valid() Calls fnValidate() after entering valid User Name and Password. Displays the Welcome Screen
   2 Login_fnValidate_Invalid() Calls fnValidate() after entering invalid User Name and Password. Displays error message as “Invalid username or password!!”
   3 Student_fnAdd_Valid() Calls fnAdd() and saves entered details to the database if all the validations are met. Displays a message “Employee details are successfully added to the database”
   4 Student_fnAdd_Invalid() Calls fnAdd() and displays error message if any of the required field is left empty and other validations are not met. Displays an error message “Sorry Cannot Add… Please fill all the mandatory details!!” or “Sorry Cannot Add… Invalid details!!”
   5 Student_fnApply_Valid() Call fnApply() and saves all the valid entered details to the database. Displays a message “book details are available in the database”
   6 Student _fnApply_Invalid() Calls fnApply() and displays error message if any of the required field is left empty and other validations are not met. Displays an error message “Sorry Cannot Book details are not available!!”
7 Student_fnSearach_Valid() Call fnSearch() and saves all the valid entered details to the database. Displays a message “book details are available in the database”
8 Student_fnSearach_Invalid() Call fnSearch() and displays error message if any of the required field is left empty and other validations are not met. Displays an error message “book details are not available in the database”
9 Student_fnReserve_Valid() Call fnReserve() and saves all the valid entered details to the database. Displays a message “book has been reserved successfuly”.
10 Student_fnCancel_Valid() Call fnCancel() Displays a message “book that has been reserved is cancelld”.
11 BookInfo_fnAdd_Valid() Calls fnAdd() and saves entered details to the database if all the validations are met. Displays a  message “Bok Information details are successfully added to the database”
   12 BookInfo_fnAdd_Invalid() Calls fnAdd() and displays error message if any of the required field is left empty and other validations are not met. Displays an error message “Sorry Cannot add Book details!!”
13 BookInfo_fnIssue_Valid() Call fnIssue() and saves all the valid entered details to the database. Displays an message,book is issued successffully
 

14

BookInfo_fnIssue _Invalid() Calls fnIssue() and displays error message if any of the required field is left empty and other validations are not met. Displays an error message “Sorry Cannot be able to issue the book. Book is already issued…
15 BookInfo_fnReturn_Valid() Call fnReturn() and saves all the valid entered details to the database. Displays an message,book is returned

successffully

16 BookInfo_fnReturn _Invalid() Calls fnReturn() and displays error message if any of the required field is left empty and other validations are not met. Displays an error message “Sorry Book is not received.
17 BookInfo_fnStatus_Valid() Call fnStatus() and saves all the valid entered details to the database. Displays an message regarding the status of the books.
18 Admin_fnAddUser()

 

 

Calls fnAddUser() and saves entered details to the database if all the validations are met. Displays a message “Student details are successfully added to the database”
19 Admin_fnAddBook()

 

 

Calls fnAddBook() and saves entered details to the database if all the validations are met. Displays a message “Book details are successfully added to the database”
20 Admin_fnDeleteBook()

 

 

Calls fnDeleteBook() and saves entered details to the database if all the validations are met. Displays a message “Book details are successfully deleted from the database”
21 Admin_fnDeleteUser()

 

 

Calls fnDeleteUser() and saves entered details to the database if all the validations are met. Displays a message “Student details are successfully deleted from the database”

UML Diagrams:

Class Diagram:

ER Diagram:

Download the below attached Development of an online Library Management System Project Code & DB

College Information Management System (CIMS) Application

College Information Management system (CIMS) application that effectively manages the storage and retrieval of information on the internal network of a college. In other words, it is a web application for a college.

How a College Functions?

    There are many activities that take place in a college. They are below

  • Admissions: The traditional process of admission requires a student to collect the admission forms, fill them and submit them to the college.
  • Student Enrollment: The student applications are screened and those found suitable are called for an interview and finally selected. 
  • Planning and recording schedules: It is necessary that every college prepares its own academic timetables for:
    1. Classes for each course.
    2. Sports and games.
    3. Extra curricular activities such as competitions and cultural activities.
    4. Meetings and seminars held to review academic schedules teaching strategies and other requirements of the college. 
  • Staff recruitments: the college periodically recruits Teachers, Professors, and Non-teaching staff members. Records on their salaries leave the position, etc., need to be maintained by the college.

As listed above the CIMS application should allow performing all the activities and if possible additional activities in a more easy and efficient manner. This application should be highly scalable and customizable for different types of colleges depending on their requirements.

The application should have an interface for accessing and retrieving data about students and staff and the college itself.

  1. A database management system in which data can be stored safely, while also being easy to access.
  2. A website for the college where outsiders can obtain information about the college.
  3. A central server that controls all the information of the college and also hosts the website of the college.
  4. An internal communication system for exchanging information, scheduling meetings and conferences. 

The following list gives an overview of what CIMS may contain.

This is abstract information about a college process.

Admissions for staff and students

  • Academic details – attendance, exams, marks.
  • Complete fee details, course wise and student wise.
  • Exams – performance.
  • Library Management.
  • Staff: Teaching, Non-Teaching.
  • Leave: Students, Employee
  • Attendance Students, Employee
  • Courses – currently offering, new courses.

Miscellaneous

  • Timetable
  • Curriculum scheduling
  • Calendar 

Reports

  • Student academic report
  • Student TC details
  • Leave Reports
  • Pay Slip
  • Library Report
  • Department wise report
  • Full Academic report 

Planning intranet for a college Requirements   Data management between departments of a college.

Every college has staff and students and all the data related to students and staff that are maintained in college records in the form of files. Similarly, the college maintains the daily activities such as timetable, year wise curriculum, and examination schedules. Maintaining such huge data for years the college needs

  • Manpower
  • Space in the office to maintain shelves, cabinets, and racks
  • Good administration strategy
  • Perfect organization
  • Ease of use
  • Efficient data retrieval 

That is we need to have an environment that is organized with numbered file cabinets. In such a system every folder has its place.

But maintaining such an extensive file system is not possible manually and it is also not cost effective.

Now the question is what makes it easier to maintain such data?

The solution is computerizing the management system.

  • Online website.
  • Internal file management.
  • Keep track of student and staff files.
  • Library management system.
  • Scheduling conferences, news, and announcements.

In order to develop the intranet, we need to do analysis about the requirements of the college system. After the analysis, we need to design the structure flow and model of our Intranet Project. We then need to write programs in Java and integrate to test and deploy the Intranet for a college.

What are the analysis and design, what does it include? 

Analysis:                   

This deals with an investigation of a whole product part by part. It is the abstract separation of a whole into its constituent parts for study. The analysis of any particular project is the paramount requirement before any other operation

Design:

It is a preliminary or initial sketch indicating the basic plan required to execute the project.

Think of what we need to build.

Identify the data needed to be organized in the INTRANET.

  • Student data
  • Staff data
  • Books data

Student Data:

Students may be categorized into two types. An enrolled student and a new student to enrol. The fields that specify the students are as follows.

Admitted Students

  • Personal information
  • Name
  • Parent
  • Address
  • Contact information
  • Date of birth
  • Gender
  • Academic information
  • Admission number
  • Course joined
  • Date of joining
  • Remarks

 Application form for new students

Personal information

  • Name
  • Parent
  • Address
  • Contact information
  • Date of birth
  • Gender

Academic information

  • Applied date
  • Previous college information
  • Previous degree details
  • Course applied for
  • Percentage of marks
  • Application id
  • Application mode (online/offline)
  • Nationality

Official details

  • Accept/Reject
  • Remarks
  • Application mode 

Staff data:

The staff may be categorized into two types, teaching, and non-teaching staff.

Personal and general details

  • Name
  • Gender
  • Nationality
  • Contact information (permanent/present)
  • Application mode
  • Professional job experience
  • Income details

Book data:

Managing the data concerning books is called Library management.

Student Details

  • Student identification number
  • Student name
  • Student address
  • Date of issue of the book
  • Phone number

Book Details

  • Book code
  • Book name
  • Price
  • Number of copies
  • Author
  • Publication
  • Edition
  • Course
  • Transactions
  • Book code
  • Student identification number
  • Date of issue
  • Due date
  • Date of return

Conferences, meetings, news

  • Date
  • Time
  • Purpose
  • Audience
  • Place

 Others

  • Website data
    1. College history
    2. Curriculum
    3. Courses offered
    4. Achievements
    5. Contact information

  Designing the project

    This includes

  • Finalizing the flow
  • Establishing relations
  • Designing the GUI
  • Organizing the data management

Plan for flow

  • Login
  • Main window
  • Options to view students, staff, library, schedules
  • Student
    1. Admitted
      • Select a classroom from list
      • Next, Previous, Add, Save, Modify, Home, Search.
    2. New Admissions
  • Next, Previous, Home, Update Status, View all.
  • Staff
  1. Select a department
  • Next, Previous, Add, Save, Modify, Home, Search, View all.
  • Library
    1. List of the category of books.
    2. Available books.
    3. Check whether the book is available or with the student.
    4. Ability to issue books and note down the details.
  • Schedules
    1. Calendar
  1. List of schedules.
  • Web
  1. Homepage
  2. Links to admission form, course details, contact information, etc. 

WORKING MODEL OF CIMS

  • Login dialogue for CIMS
  • Main page
    1. Student details
    2. Employee details
    3. Library details
    4. Payroll
    5. Attendance
    6. College information
    7. Course information
    8. Latest happenings
  • If we click on Student link
    1. Admission details
    2. Course information
    3. Academic details
  • If we click on Employee Link
  1. Personal information
  2. Course responsibilities
  3. Academic details
  • If we click on Attendance link
    1. A screen with two options, student lists or employee lists with present or absent status appears.
  • If we click on the library link
  1. Books Available for Issue
  2. New books to add
  3. Status of books
  4. Return books with fine (if any)
  • If we click on college link
    1. Just shows the college details
  • If we click on course information
  1. Course details
  2. Subject details
  • Latest happenings
    1. Calendar
    2. Timetable
    3. Holidays
    4. Notice
    5. News and announcements
  • Other pages

Web page: A home page with the following links

  1. About us
  2. Courses
  3. Admissions
  4. List of students
  5. Staff
  6. Contact us
  7. Library
  8. Administrator

Food Ordering Management System PHP & MySQL Project

Summary of the System: 

There is a lot of scope online food ordering business and we can tap it to the max extent possible as everyone has access to an online ordering facility via the internet. Food business usually will have high demand and hence online business prospect for food ordering should be profitable.  We will provide an easily accessible interface wherein the customer can view and place the order easily.

The customer can register initially with minimum details and will be allowed to check the menu items before ordering them, adding them to cart and submit the order. The system records the details in MySQL database so that it will be easy to retrieve later. The users of the system also include employee/admin who will handle info related to product addition and assigning vehicle for placed orders.

Problem Statement:

The food business in restaurants is being carried out in the same fashion for so many decades. In the restaurants, when the customers visit, they will read the large menu cards which just has the name of the item and price. They have to decide in moments time and place the order just to wait in the queue for getting the ordered items on their table. Sometimes, the waiting time is so huge that the customers will actually lose interest in the item. Moreover, some customers will be in their office or busy to come physically to the restaurant and eat.

To ease the process of ordering the items, giving a description of each item and getting the item on the table the online food ordering system is designed. Some of the common problems are listed below.

The general problems faced while ordering food physically in a restaurant are listed below.

  1. Viewing the complete description of the menu item before ordering.
  2. Placing the order standing in a queue.
  3. Waiting for the customer’s turn to get the food.

These hurdles will be avoided by placing the order online

Users of the System:

The users of the system include the customers and the employees. The employees of the system are responsible for updating the menu items as well as the delivery of the item to a particular address. The customers will visit the website, check for the items available in the menu, order for one or more items in the menu. All the activities such as ordering items online, delivery of the items by employees, the vehicle used to deliver the items etc. will be recorded in the database for all the events.

Users of the database:

The top-level management who owns the food business will be using the database. They can try to infer details like

  1. what is the most demanded item?
  2. Which item is not ordered at all?
  3. What amount of business is made on daily basis?
  4. How the delivery of items is being carried out? etc.

Use Cases:

Use case diagram for Customers

Use case Diagram for Employees

The architecture of the Application 

Entities and its Attributes:

The main entities identified in the system are listed below.

  1. Customer [Attributes -> cid, name, email, pwd, phno, address]
  2. Employee [Attributes -> eid, name, phno, email, password]
  3. Orders [Attributes -> oid, pid, cid, odate, quantity, delivery status, vehicle]
  4. Products [Attributes -> pid, name, description, price, file]
  5. Vehicle [Attributes -> vid, status,vehicle_number]
  6. Cart [Attributes -> id, cid, pid, qty, status] 

Logical Design: 

The identified entities along with the attributes in the system are listed in Section 1. The tables that are designed are given below.

Customer Module:

The customer table consists of below details

  1. cid {primary key} [type : int auto_increment] assigned for each unique customer.
  2. name [type : varchar(30)] represents name of the customer
  3. Email [type : varchar(30)] represents email of the customer
  4. Pwd [type: varchar(30)] used for saving password of the customer
  5. Phnno [type : int(11)] is used for saving phone number of customer
  6. Address [type : text] used for saving the address of the customer

This table is used to get the details of customers

Employee Module:

Employee table is used to save

  1. eid {primary key} [type : int auto_increment] assigned for each unique employee.
  2. name [type : varchar(30)] represents the name of the employee.
  3. Phno [type : int(15)] is for saving phone number of employee
  4. Email [type : varchar(32)] saves the email info of an employee
  5. Password [type : varchar(32)] will save password of employee

Orders Module:

Order table used to save

  1. oid { primary key } [type : int auto_increment] assigned for each order.
  2. pid { foreign key references products: pid } .
  3. Cid [foreign key references customer: cid]
  4. Quantity [type : int (25) ] represents the quantity of the ordered product.
  5. Odate [type : datetime] represents a timeframe of the products ordered by the customer
  6. Quantity [type : int (11)] provides the quantity ordered by the customer
  7. Delivery status [type : tinyint(1)] saves the delivery status whether delivered or pending
  8. Vehicle [type : int(11)] helps in assigning vehicles. foreign key references: vehicles vid

Products Module:

Products tables used to save

  1. pid {primary key} [type : int auto_ioncrement ] assigned for each product.
  2. name [type : varchar(20)] represents the name of the product.
  3. description [type :text] represents the description of the product.
  4. Price [type : double(10,5)] saves the price of the product ordered
  5. File [type : text] saves the image of product ordered

Vehicle Module:

Vehicle table used to save

Vehicle [Attributes -> vid, vehicle number]

  1. vid {primary key} [type : int auto_increment] assigned for each vehicle.
  2. Status [type : int(11)]
  3. Vehicle number [type: varchar(30)] saves the registration number of the vehicle assigned for delivery

Cart Module:

Cart table used to save

Cart [Attributes -> id, cid, pid, qty, status]

  1. Id {primary key} [type : int auto_increment] assigned for each cart
  2. Cid foreign key references customer id from the customer table
  3. Pid foreign key references products table
  4. Qty saves all quantities related to products added in cart
  5. The status will save delivery status

Entity-Relational diagram:

Download Food Ordering Management System PHP & MySQL Project Source Code.

Job Suggestion Website Java Project

To help job seekers to find the job information online conveniently and quickly we are going to develop this project. The project title is job suggestion website. Here We are going to develop this website to ease the difficulty of searching for jobs according to the area of interest and according to locations where they want to work. To develop this website we have to collect information from different companies by crawling the data with their domains and location. These crawled data need to store by using some database (such as mongoDB or phpmyadmin or mysql). The stored data of companies should be searchable by location or domain. For searching, we will use elastic search or other search engines. To search companies user need to enter location or domain and our website will suggest companies according to the given information.

Output Results Explanation:

This User interface is for job portal home page where admin can log in with registered user id and password. The user can view a list of features available in this application.

After successful login admin can view different features and perform operations form this page.

Admin can view employee details with user id, employee name, company name, contact number, email id, date of registration and charges.

List user interface will display a list of applications which are applied for jobs.

Using View jobs user interface admin can view a list of jobs posted with job id, job description, company name, and date of posting with requirements.

The user can select posted jobs from this list and look after detail of job with address, time and company profile. The user can apply using directly from this interface.

This interface is confirmation message after user applying for the job.

This user interface is for the admin who can post new walk-in details. List of posted details is shown with walk-in id, job title, company name, location, walk-in date.

Using this User interface admin can add new walk-in details and post to the existing list.

This interface is for showing successful posting of a new walk in.

This interface is for user registration where the employee should register with an application for applying for a job. The user must enter login detail and contact information using this form.

Admin can view a list of job seekers details who had applied for a different job posting . Admin can view job seeker id, username, qualification, percentage.

Search interface can help admin or user to find respective job seeker or job postings without searching from the list. Admin can select criteria, location, experience, functional area and get results.

Using manager login form user must enter valid user id and password to log in with application only after login user can use any features.

Company manager can view employer details after login to the application.

The manager can view a list of job postings from different companies. He can post a new job for his company.

The manager can add new job post for the list based on his company requirement.

This interface is for post successfully posted confirmation.

This interface is for user login where user had already registered with the application. He can enter user id and password and apply for a job.

The user can view a list of placements papers and download for reference.

This interface will display downloaded placement paper with previous questions and answers.

Using this interface user can download sample resumes.

This interface shows details of downloads available for a user like networking question papers, database question papers..etc.

UML Diagrams:

Use Case Diagram:

Sequence Diagram:

Activity Diagram:

Class Diagram:

ER Diagram:

Metadata

Metadata has data about data. Metadata actually has the data that describes the data we store in our SQlite database files.

S.NO Table name attributes properties Data type  key
1 Admin Userid User1, user2, .. varchar Primary key
password varchar
2 Employer  Home

 

User name

password

Employer name Varchar

varchar

Primary key

 

Job Street

 

View Jobs

 

Post New Job

 

SaveJob Details

 

 

ViewJobDetails

 

SeniorSE,HR….

Software,Accountant

SeniorSE,HR….

 

SeniorSE,HR….

 

Varchar

Varchar

Varchar

Varchar

 

Varchar

 

Search Jobs

 

J2EE Software Engineer…. varchar Primary key
3 Job Seeker Home Search Jobs J2EE Software Engineer…. varchar Primary key
Apply Job JOB1, JOB1…. varchar
My Profile PerID1, PerID2.. varchar
My Applications A-1, A-2.. varchar
Update Profile

Downloads

PerID1, PerID2.. Varchar

varchar

Citizen Card System Java Project

Abstract:

The project ‘Citizen Card system’ provides us the data regarding the citizen of a country. Every citizen has a unique Id to trace the personal data in each and every division or service that he enters. The data can be traced using the unique Id of that particular citizen.

In case a citizen wishes to use the services or utilities by the Government or private institutions, he ought to go to the various divisions with varied Id for that specific division. But a citizen card allows the citizen to enjoy all the services and utilities under a single card. The citizen card system assists us in gaining the data regarding the services or utilities as well as providing the data regarding the conduct of the citizen in credit rating.

UML Diagrams:

Use Case Diagram:

Sequence Diagram:

Activity Diagram:

Class Diagram:

Existing System:

The existing system is a system operated by humans and the citizen requires to reserve his data through excel sheets or disk drives, but there is always a risk of losing the data due to mismanagement.

Proposed System:

The proposed system is more user-friendly and makes the entire project maintenance very uncomplicated and manageable. This system motivates people to get the Citizen Card, which is a multi-purpose card. This is a social responsible website and functions on the principles of the citizen data and strengthening the citizen safety in the country.

Output Results:

1.Homepage


2.Admin Login Page

3.Admin Home Page

4.View Users


5.Citizen Registration

6.Citizen Login


7.Citizen Home


8.View Profile

9.Insurance Info

10.Electricity Bill Payment

11.Bank Bill Payment

12.Gas Bill Payment

13.RTO Bill Payment

Software Requirements:

  • Operating System :  Windows
  • Database :  Oracle
  • Technology :  Java/j2ee,JDBC,Servlets,JSP
  • Web Technologies :  Html ,CSS, Java Script
  • Web Server :  Tomcat
  • IDE          : Eclipse/ Net beans