Online Chatting System with Displaying Chat History Project

Online chatting system with display chat history application works on wired networks like LAN. This chat system project has the option to chat with different languages.

Chat application works for multiple users but each user must register with the application. After login user can enter into a group for a chat.

After register and login part is done user can view available user online and offline. User can chat with a person who is logged to the system.

In order to chat with the respective language, the user must install the editor of that language.

This application works on LAN communication when user login with application request is sent to the server for authentication and gets a response. The server-side database will store information of each user data.

Online Chatting System Class Diagram:

Modules overview:

User Registration Form:

The first step for using this application is the registration form where the user will ask for a login or signup option. User can select register if he is a new user and enter all these details to get a unique id and password.

Using these details he can log in an application.  The registration form will have all validations checks for each field.

User Module:

After registration is done user will get user id and password using these details he can log in to the application and use all features.

There are options for users to change password. User can view the list of available users online and offline and perform chat operations.

Chatting Module:

Under chatting module user can view a list of available users with online and offline status. He can select the user and send request after acceptance he can chat with the user.

User will have setting options for changing font and color. User can enter a message and use the send button to send a message which is displayed under the upper window.

User can chat with multiple users at a time he can view list previous chats and delete messages.

Sequence Diagram for Login:

Sequence Diagram for Forgot Password:


Sequence Diagram for Chat:


Activity Diagram:

Online Fee Challan Generation Project Synopsis

INTRODUCTION:

The project is a web-based application where the user can generate Challan to pay the fee. The system automates the conventional process of generating Challan by visiting the college website. The system would be having two logins: Admin and User Login. Admin can view student details and can even add or update things in their account.

Modules:

  • Admin login
  • Student/user login
  • Student details
  • The Fee details
  • Dues

Software Requirements:

  • Windows XP,Windows 10
  • Sql 2012
  • Visual studio 2017

Advantages:

  • This software is user friendly you will automatically feel the difference in managing the fee challan things on the implementation of software
  • It perfectly manages the fees by creating the student profile with demographic information, contact details and parent information
  • Using this software is completely safe
  • It also offers quick payment 

Disadvantages:

  • User must have a reliable internet connection

College Feedback System Java Project

Abstract:

College feedback system is a web application which provides an easy way to know information about a college. In this application, all the information of the college will be added by admin. Students can find all the details of college and can give feedback which will be helpful to fresher’s who are searching for college information.

Existing System:

In the existing system, there is no proper information about colleges. Students who are searching for college details should go physically and make enquire about college which takes a lot of time and effort. The student is not able to give feedback about college.

Proposed System:

The proposed system provides an easy way to a student who is searching for college information. All the information is added by admin where students and fresher’s can easily access the information. This system saves a lot of time and effort of students. This system also provides a chance for students to give feedback about the college.

Modules:

Admin:

Admin needs to get logged in with valid username and password. Admin can add college, add placement and view college.

Student:

The student needs to get registered with the application by entering all the details in the registration page. A student can get logged in by entering college name, username, and password. A student can view profile, View College, view placements and can give feedback.

Fresher:

Fresher can get registered with the application by entering all the details in the registration page. Fresher can get logged in by entering college name, username, and password. Fresher can view profile, View College, view placements and can give feedback.

Output Results Pages:

  • Homepage:
  • Admin login page:
  • Admin home page:
  • Add college page:
  • Add placements page:
  • Student registration page:
  • Student login page:
  • Student homepage:
  • View profile page:
  • View college page:
  • View placements page:
  • Feedback page:
  • fresher registration page:
  • Fresher login page:
  • Fresher homepage:
  • View profile page:
  • View college page:
  • View feedback page:

Automation of Faculty Remuneration System Java Project

Introduction

This Automation of Faculty Remuneration System project is an online portal.

This web-based application allows the college faculty to get important data about their remunerations for their invigilation’s.

Since college faculty operates through pc, they can keep checking about the payment given to them frequently, the faculty login is to be performed through a computer.

Faculty can see the allotted students in their class

Existing system

There are many online portals available for faculties but they are not very efficient, the faculties are unable to access the details.

Disadvantages of Existing System

It is not helpful in assigning the invigilation details and managing the regularly

Proposed system

This is a web application for the automation of generating the invigilation to the faculty.
The count of students attending the examination, the faculty is invigilating are taken into account and the pay is automatically updated in their personal account.
An approach to the admin can be made if any errors are present in the remuneration details and can be modified immediately.

Advantages of the proposed system

It is helpful in assigning the invigilation details and managing the regularly with modifications.

Description of modules:

Faculty login: This allows the registered faculty to login in order to view their invigilation details.

Admin login: The admin assigns the invigilation to the faculty and add the required rooms and allocate the students according to them.

Student login: This allows the student to check in which room they are allotted.
Server management: The server smartly handles data and allows the details to be updated frequently and maintained securely.

UML Diagrams:

Use Case Diagram:

Activity Diagram:

Class Diagram:

Output Results:

  • Home Page
  • Admin Login page
  • Admin Home Page
  • Add Faculty Page
  • Add Student Page
  • Add Room Page
  • Faculty Allocation Page
  • Faculty Login Page
  • Faculty Home Page
  • View Students Page

Conclusion:

This system is very helpful in order to do all the above-mentioned tasks. Generally, there may be a chance that some faculties may not get the payment properly. Instead, by means of using this application, it reduces the burden to the faculty and also, the faculties can contact admin easily by means of having the application. It is a good platform for the faculty.

Bakery Store Final Project Synopsis

The below Requirements for a model for Final Bakery Store Project:

  1. Minimum 6 entities
  2. Minimum one inheritance – with 2 subclasses
  3. Minimum one interface with one implementation
  4. Role based model – Eg., Admin and Regular users should have different functionalities
  5. Should implement CRUD functionality for all entities – based on user roles – it should be logical with your model
  6. Should use Java collections for entities relationships. Design your model in such a way that collections are used for associations between entities.
  7. This task is mainly to think logically about the functionalities that a system can perform based on user roles in order to create the design.
  8. DDL statements with Entity relationship diagrams of all the entities.

Classes List:

  • Bakery Items
  • Users
  • Admin
  • Customers
  • Order
  • Account

Interface

  • Payment

Class Relationship:

  • Bakery_Items to Account (MANY TO ONE)
  • USER to ACCOUNT(ONE TO ONE)
  • Customer and Admin are subclasses of User(inheritance)
  • User to Orders(ONE to MANY)
  • Account to Orders(ONE to MANY)
  • Payment<interface> to Orders(One to Many)

UML Diagram for Bakery Store

Database Table List

  • Bakery_items
  • Users
  • Account
  • Orders

DDL Statements:

Table Bakeryitems

Create Table BakeryItems

  • Item_id number(10) NOT NULL,
  • item_name varchar(50) NOT NULL,
  • price number(10),
  • DateOfManufacturing DATE,
  • CONSTRAINT BakeryItems_pk PRIMARY KEY (item_id),

Create Table Account

  • Account_id number(10) NOT NULL,
  • Customer_username varchar(50) NOT NULL,
  • customer_id number(10),
  • CONSTRAINT Account_pk PRIMARY KEY (Account_id),
  • CONSTRAINT fk_User
  • FOREIGN KEY (User_id)

Create Table User

  • User_id number(10) NOT NULL,
  • username  varchar(50) NOT NULL,
  • password  varchar2(10),
  • email  varchar2(10),
  • phone  Number(10),
  • Account_id varchar2(10),
  • CONSTRAINT Customer_pk PRIMARY KEY (customer_id),
  • CONSTRAINT fk_Account
  • FOREIGN KEY (Account_id) 

Create Table Order

  • Order_id number(10) NOT NULL,
  • item_name  varchar(50) ,
  • item_id  Number(10),
  • order_date varchar2(10),
  • payment_id  Number(10)
  • CONSTRAINT Order_pk PRIMARY KEY (Order_id),
  • CONSTRAINT fk_Bakery_Item
  • FOREIGN KEY (Item_id)