Hour-Wise Lecturer Tracking Web Project Synopsis

The project titled “hour-wise-lecturer Tracking” is an HTML/Python web application developed on windows operating system.

On bigger colleges and campus like Bhavan’s Vivekananda college. It becomes a difficult task to locate any lecturer as to where and in which room he/she might be in. Also, if there is any change in the regular classrooms of that particular class, there is no way information is given or updated to the students (both from the current class or other students). And also in case if a lecturer wants to know if there are any empty classrooms available for that particular hour, he/she have to send a student to look out for which in turn results in a waste of time.

Rather, we are trying to propose a system through which it would be easy to know the location of a lecturer by other students or faculty and also to find out the availability of empty classrooms. This system also helps the lecturers share hyperlinks of their respective class notes with the students in the form of pdf’s or documents.

This application contains various modules such as

  • Trackers: this module deals with finding the location of the lecturer, as to where and in which room he/she might be in.
  • Notes: this module deals with the hyperlinks of respective class notes generated by the lecturer.
  • Available classrooms: this module deals with the availability of empty classrooms for that particular hour.

UML Diagrams:

Faculty Use Case Diagram:

Student Use Case Diagram:

HoD Use Case Diagram:

Activity Diagram:

Output Screen Results details:

  • Home Page:
  • Faculty Registration Page:
  • Faculty login Page:
  • Faculty Home Page:
  • Update Profile page:
  • Availability :
  • Class Room Availability:
  • Upload Time Table:
  • view Feedback:
  • Send a reply:
  • Send notifications:
  • Student Registration:
  • Student Login Page:
  • Student home:
  • View time table:
  • View faculty availability:
  • Feedback page:
  • View Notification Page:
  • Hod login Page:
  • Upload classroom Page:

Loss Control System for Insurance Producers .Net Project

Introduction

Insurance companies issue various types of policies to protect home and business owners from various types of unforeseen calamities such as fire, floods, theft etc.  However, prior to issuing or renewing a policy, the insurance company conducts a field survey of the property to ensure that the property is adequately secured and is not vulnerable to damage.  Thus the insurance company ensures that the chances of damage or loss are controlled.  For example, if a petrol pump has to be insured, the petrol pump owner should provide for adequate fire safety equipment, signboards prohibiting smoking near the fueling area etc.

In order to conduct these surveys, the insurance company enlists the services of independent surveyors residing near the property.  These surveyors are trained personnel and are pre-approved for certain types of activities.  The aim of the project is to develop a system used by insurance companies and surveyors to record the surveys to be done, assigning a surveyor to conduct the survey, capture, and approval of survey results, recording and approving of the surveyor’s Time and Expenses (T&E) Report. 

Workflow of the proposed system

Detailed Functionality

 1.    Record the Surveys to be done

Prior to issuing or renewing an insurance policy, the underwriting department raises an RFS (Request for Service) in LCS.  The details to be entered include –

Location to be surveyed

Type of insurance coverage (fire, theft, flood etc.)

Date by which the survey should be completed

Surveyor ID  (to be searched based on the location’s pin code)

Type of service requested (eg. Survey.  In future, the same system can be extended to verify insurance claims)

The estimated budget for the survey (This is the amount of money that the insurance company is willing to spend towards surveyor’s T & E)

The underwriter may also attach a copy of insurance policy application to RFS.

  1. Working with an RFS

Once an RFS is assigned to a surveyor, he/she starts working on the RFS.  The surveyor should be able to query the status of various RFS’s assigned to him/her.  Typical activities that are carried out by Surveyor on RFS include –

Scheduling a visit to the location – Enter the scheduled date and time in the system and update the status.

Survey the location and Write a Survey report – Attach the survey report to RFS on completing the site visit.

Writing recommendations and following-up on recommendations – Writes recommendations on the corrective actions to be taken at the location and updating the action taken on the recommendation.

Entering time and expense details – Record the time and expenses incurred to carry out the survey and the follow-up actions.  These details have to be entered by date and activity.

Close RFS – After all the details are entered, the surveyor closes the RFS.

  1. Approving Time and Expenses

The underwriter reviews the T&E reports and either approves or disapproves the expenses based on the budget.

In case it is disapproved, he/she cites the reasons for disapproval.  The surveyor is informed to update the expenses accordingly.

If it is approved, it is sent to the finance section for payment.

  1. Reporting

This module generates various reports for surveyors and underwriters.

For surveyors –  List of RFS by status,  List of RFS received or completed during a given period, Report on T & E for a given period

For underwriters – List of RFS by status (across surveyors or for a specific surveyor), List of RFS raised or completed during a given period,   T&E claimed and paid during a given period.

UML Diagrams:

Use Case Diagram:

Sequence Diagram:

Activity Diagram:

Class Diagram:

REQUIREMENTS

Software Requirements:

Visual Studio .NET

Front-End: C# in ASP.NET

Back-End: SQL Server

Hardware Requirements: 

RAM: 2 GB

Hard disc: 80 GB

Test Cases:

s.no Test case name Test procedure Pre-condition Expected result output Specification
1 Login Enter userid and password Displays pay bills form success Login
2 Login Enter admin and password  

Displays the status

success Login
3 Login Enter user and password Error message success Login
4 Pay bills Enter details Select billername, date, accountno Displays bill paid successfully success Pay bills
5 Add biller Select the biller Select billername Add biller successfully success Add biller
6 Add biller Select the biller Select name Displays as already exists success Add biller
7 View details As admin Displays list of pending transactions success View status
8 View details As admin Update status Displays status success View status
9 View details As user Edit date, amount Displays all transaction of that user success View report

Download the below-attached Loss Control System for Insurance Producers .Net Project Source Code

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)

College Student Attendance and Staff Profile System

The main aim of developing this java application is to provide a complete school or college based attendance management system for students and profile system for staff and management.

Faculty information is to be maintained securely and should be accessible only to the respective faculty and the administrator when required. Student’s daily attendance should be entered by the faculty and should be managed perfectly. In the existing system manually the corresponding faculty will enter attendance details in files. If the administrator or faculty want to know the student information, he must able to search the sheets, this consumes a lot of time. Here the project eliminates that problem and makes the process automation.

The Student Attendance and Staff Profile project mainly focus on maintaining of faculty profile, student daily attendance in which different levels of users are restricted to access the database. We can make the users access the data but they can’t modify or update the database. Only the authorized faculty and administrator can access and update the database. Each faculty and administrator should log in to get the details of the faculty and student attendance.

Objectives of the project

  • Complete automation is possible in this sector, which is against the main disadvantage namely time-consuming.
  • Can maintain company faculty details and student details.
  • Any kind of information based on faculty profile or student attendance can be retrieved within less time.
  • Only authorized faculty or administrator can access the database by providing necessary information.

Requirement Analysis

A requirement is a feature that must be included in the system. Before the actual design and implementation start, getting to know the system to be implemented is of prime importance.

We are overcoming the difficulty of maintaining faculty details and student attendance which were manual in the current system and here we generate detailed information about the faculty and students attendance which will save our time to maintain all information and retrieve when required. 

Functional Requirements:

This section describes the functional requirements of the system for those requirements which are expressed in the natural language style.

A faculty member should be able to login to the system through the first page of the application, and he can perform actions like viewing and entering student attendance and can update his profile. An administrator can login into his account and he will update the faculty information.

System Design:

UML Diagrams:

Class diagram
Fig: Class diagram

Description:

In this class diagram, we are considering the main classes administrator, faculty, and databases where we mainly perform the operations. Here we are also providing the classes for the interface as the operations can be facilitated easily and this comprises of the many options. And we maintain classes for the faculty to maintain its student details and the faculty details are also maintained.

Interaction Diagram for Registration of new faculty:

Description:

In this interaction diagram, the administrator registers a new faculty member by entering his details in the registration form and updates the database.

Interaction Diagram for daily attendance:

Sequence diagram for daily attendance
Fig: Sequence diagram for daily attendance

Collaboration diagram for daily attendance:

Description:

In this interaction diagram, the faculty selects a subject and a date and enters the attendance by clicking on the corresponding checkboxes of students roll numbers and updates the database by clicking submit.

Interaction Diagram for change password:

Sequence Diagram for change password
Fig: Interaction Diagram for change password
Collaboration Diagram for change password
Fig: Collaboration Diagram for change password

Description:

In this interaction diagram, the user can change the password by entering the new password and validate the password by re-entering it and update the database by submitting it.

Interaction Diagram for faculty details update:

Description:

In this interaction diagram the faculty details will be displayed and he can update the details that are already available in the database from the user interface and the new details entered can be updated in the database.

Use case diagram for administrator:

Description:

In this use case diagram, it includes the main functionalities of the administrator. Here main activity of administrator is to register the faculty, view daily, monthly and cumulative attendance.

Description:

In this use case diagram, it includes the main functionalities of the faculty. Here main activity of faculty is to maintain student attendance, update the student’s attendance and to modify his profile.

Description:

Here the activity diagram explains how the system administrator performs different operations.

Data Base Design 

DATA BASE TABLES Field Data type
Faculty_login_rowid number
Faculty_id varchar2(60)
Faculty_password varchar2(60)

Table 1:faculty_login 

Field Data type
Faculty_profile_rowid Varchar2(60)
Faculty_id varchar2(60)
Faculty_name varchar2(60)
Faculty_dept varchar2(60)
Faculty_course varchar2(60)
Faculty_desg varchar2(60)
Faculty_qual varchar2(60)
Faculty_dob varchar2(60)
Faculty_texp varchar2(60)
Faculty_rexp varchar2(60)
Faculty_iexp varchar2(60)
Faculty_spl varchar2(60)
Faculty_joinyear varchar2(60)
Faculty_emailid varchar2(60)
Faculty_phno varchar2(60)
Faculty_addr_dono varchar2(60)
Faculty_addr_street varchar2(60)
Faculty_addr_city varchar2(60)
Faculty_addr_pin varchar2(60)

Table 2:faculty_profile 

Field Data type
Faculty_status_rowid Varchar2(60)
Faculty_id varchar2(60)
Faculty_name varchar2(60)
Faculty_course varchar2(60)
Faculty_dept varchar2(60)
Faculty_courseyear varchar2(60)
Faculty_section varchar2(60)
Faculty_acyear varchar2(60)

Table 3:faculty_status 

Field Data type
rid Varchar2(60)
dt varchar2(60)
sub varchar2(60)
H71A0XX1 varchar2(60)
H71A0XX1 varchar2(60)
H71A0XX1 varchar2(60)
. varchar2(60)
.. varchar2(60)
…. varchar2(60)
H71A0XXN varchar2(60)

Table 4:f_att_bxxxxx 

Field Data type
Student_rollno Varchar2(60)
Student_joiningyear varchar2(60)
Student_course varchar2(60)
Student_dept varchar2(60)
Student_acyear varchar2(60)
Student_course_year varchar2(60)
Student_section varchar2(60)

Table 5:mic_student_status

System Test Cases & System Test Report

SNO Name Input Expected result Observed Result
1. Giving the wrong username and password Username

And password

Alert message should be displayed Alert

the message is displayed indicating

invalid

username

or

password

2. Registering faculty without proper information Faculty details Alert messages should be displayed Alert

messages are displayed.

3. Inserting attendance into the database attendance Message should be displayed if attendance inserted successfully Message is displayed
4. Click On Sign Out User should be signed out and Login page should be displayed Login page is displayed

Output Screens:

1) Login screen
2) Administrator Profile
3) Change Password
4) All faculty
5) Add faculty
6) Remoce faculty
7) Validation message
8) View faculty status
9) Edit faculty status
10) Add faculty status
11) Select Date
12) Daily attendance
13) Select month for attendance
14) Cumulative attendance
15) Aggregate attendance
16) Report generation
17) Logout Page
18) Faculty Home Page
19) Faculty Profile
20) Update faculty Profile
21) Select subject to view attendance
22) Date wise attendance
23) Cummulative attendance
24) Selection of subject
25) Enter attendance
26) Attendance entered Successfully

CONCLUSION

The project mainly focused on the total computerization of student’s attendance details and faculty profile in which different levels of users are restricted to access the database. By restrictions, we can make the users access the data but they can’t modify or update the database like students attendance, and other information etc.

This project mainly operated by two modules mainly faculty and administrator. The administrator can view the details of the students like marks view. The faculty members can view, update, add and delete the student’s attendance. This approach has features such as less manual intervention, data security is high and confidentiality can be maintained. The user can access the student’s details within less time.

Installation Steps:

  • Install Java (Java Run Time Environment)
  • Install Apache Tomcat with port number 9090.
  • Install Oracle 10g with port number 8080.
  • Create new system DSN with data source name: project & Username: project
  • Copy the project folder to c:\tomcat 6.0\webapps
  • Load the database from a backup file.
  • Open any browser and type the following address
  • http://localhost:9090/project/login.html
  • Now use the login credentials to log in and continue.

Login Credentials:

Oracle 10g:

Username: project
Password: project

Login.html:

For administrator-> Username: admin password: admin
For faculty-> Username: 101 Password: 101

DSN: project

For attendance the database is available for the following details:

Please select these from the list:
Class: IV c.s.e Section: A or B

Download College Student Attendance and Staff Profile System Java Project Source Code and Database

Online Entertainment Portal Java Project

Abstract:

Online Entertainment Portal is a web application which is used to provide services of Movies With options like online Streaming, buy option. It’s a good Platform Which Connects Sellers with customers who are Movie Lovers. Apart from this we have books section for book lovers And a customer Buy from Seller.

UML Diagrams:

Use Case Diagram:

Sequence Diagram:

Class Diagram:

Activity Diagram:

This System includes 2 Modules

ADMINISTRATOR

He has the full authority over the website. He can View all the registered sellers and users, has the access/power to delete them, he can also edit the website like update them regulary. He is responsible for safety of information which is provided by both the users/customers and sellers who by their product on this site.

CUSTOMERS

There are generally 2 types of customers over here

  1. Users :-

They use the site to stream movies/videos and read books and try to Register for an event. Users have two options either they can buy a Movie if they buy it a Dvd will be delivered to them for which prices are to be paid

  1. Sellers:

They use the site to sell their products like movies, books. They decide the price of their products and regularly need to update about the quantity of product present with them.

Output Results:

Home Page:

Admin Home Page:

View Users Page:

View Sellers Page:

Seller Registration Page:

All Output Screens:

  1. Home page:
  2. Admin login page:
  3. Admin home page:
  4. View users page:
  5. View sellers page:
  6. Seller registration page:
  7. Seller login page:
  8. Seller home page:
  9. Add movies page:
  10. Add books page:
  11. User registration page:
  12. User login page:
  13. User home page:
  14. View movies page:
  15. Movie Details page:
  16. Purchase page:
  17. View books page:
  18. Book Details page:
  19. Purchase page:
  20. Contact us page:

Software Requirements:

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