Tag: MySQL

Posted on

Product Stores & Inventory Management Project

Existing System

Following are the S/W for Procurement Process and Managing the database for all the projects of Programme ANSP from Demand – SO – Payments – Stores Inventory.

Challenges: Following are the Challenges in using the above-mentioned Inventory Management S/W

  • Multiple Client–Server Applications for data capturing.
  • Systems are very old and hence they are not able to cope with the latest S/W and H/W.
  • No communication between the applications.
  • No linkage between the projects, every project has a separate schema and instance.
  • Few processes cannot be automated.
  • The database may not be in normalized form.
  • Database structures may not be uniform across systems.
  • Effort duplication might be happening for data entry and reporting.
  • Software Maintenance may be a major concern.
  • No online approvals.

Proposed System

To Overcome the above-mentioned problems, an attempt is made to develop a Web-based product Stores & Inventory Management Project which is centralized, fully integrated having/ all the required functionalities of the existing system. Product Stores & Inventory Management Project will have FIVE major modules, Master, User Management, Procurement and Store Inventory, Payments

General Features 

  • A centralized, fully integrated System that can integrate all required functionalities of existing systems.
  • Should be able to handle any number of Projects without having any additional instances.
  • Organizational Changes should not impact the system.
  • Optimization in business process Automation.
  • Leverage the advantage of new technologies like Java, Spring, Hibernate, and Oracle RDBMS 11g.
  • Multiple users would access this application software with proper Authentication.
  • The proposed system should work both on LAN and WAN (TBD Internet), is a web-based application, and is easy to configure. This system would be developed in a user-friendly way.
  • Business Rule and Workflow for optimizing resources and reduction in Data entry redundancy.
  • Online approval can be done based on their roles and their responsibility.

Functionality Features 

  • Reports(Item/BOM/System/sub System/Article wise summary, Lifted Items, Shortage Lists, Expired items list, and Final Built-in Report), Various reports to be generated throughout the Procurement, Inventory  and other stages such as Proposal, Sanctions, Demands, Enquiry, Inventory, IR and Voucher Gate Passes 

Transaction logs 

  • Transaction log shall keep track of data items added, changed, or deleted.

For records that are added, the data items logged shall be:

  • User ID of the user who activated the functions.
  • Function name
  • Date/Time of the action
  • Data items added

For records that are modified, the data items logged shall be:

  • User ID of the user who activated the change
  • Function name
  • Data items after and before the change of action

For records that are deleted, the data items logged shall be:

  • User ID of the user who activated the function
  • Function name
  • Date/time of the action
  • The add/change/delete functions which shall be logged in the transaction log shall be a different functional requirement given in this document.

Access Control 

  • A valid user ID and password should be entered in order to access the Product Stores & Inventory Management application. Only the project administrator can create or disable user accounts.
  • A timeout to log out feature would be set for non-active sessions or sessions idle beyond a certain time period. Proper session management for the application would be set so those non-active sessions would be automatically logged out.

System Overview

The purpose of this document is to present a detailed description of the Web Publishing System of the “Product Stores & Inventory Management Project” for ANSP (Advanced Naval Systems Program). 

System Architecture

  1. Layered Approach

Product Stores & Inventory Management Project application would be developed in a layered approach. This would enable the team to work on different components independently and also for faster development. It increases flexibility, maintainability, and scalability. It helps in configuring different levels of security.  It also helps in testing components independently.

  • The user interface layer is which all end users would view. All UI components are created and integrated with the business layer.
  • In the business/ service layer, business objects help us in defining entities. Using these business objects, business logic is developed and attached to services. These services are exposed through an application programming interface (API).
  • The data access layer would connect to the database by using hibernate. Hibernate is a high-performance object/ relational persistence and query service. It not only takes care of the mapping from java classes to database tables and from java data types to SQL data types but also provides data query and retrieval facilities.
  • The repository includes a database and file system. The file system would include all the attachments uploaded through the application.
  • Audit log, security & external application integration would include auditing, and tracking of all actions and activities done by users. All integrations like SMS, email, and any hardware integrations are done in this layer.
  1. Detailed Application Layer Architecture

This Inventory Management application would be developed in three-tier architecture i.e.  Client, application and data tier. In the client tier, all end users can access by using a web browser and interact with the Product Stores & Inventory Management Project. UI components would include JSP, CSS, java scripts, and JSON. In the application tier, the application design would be included with presentation, business logic, and data access layers. As discussed earlier, these layers would help applications for faster accessibility and faster development. Architectural styles would include REST i.e. representational state transfer and architectural pattern would be MVC (Model View Controller). In the data tier, services would get the data from the Oracle database and present it in the presentation layer so that the end user can view and take necessary actions.

Functional Modules

The Inventory Management Project contains the following Main Modules

  • Stores & Inventory Management

Store inventory management is a module that enables the maintenance of accurate inventory of its products. The following are the modules.

  • Issue of items
  • FIM Issue using Gatepass

Store Inventory Module:

The Store Inventory would deal with functions like receiving items into inventory and issuing items from the inventory to the requested user based on approval. The system should generate vouchers as per the store’s format for both issues and receiving. Procurement and Store Inventory uses well-designed Web Forms for specific actions required by the users.

Operating Environment

This product will be developed mainly using open source technologies like apache, Java, Spring, Hibernate, Ext-JS, and Windows Operating System for developing this product.

Server Operating System

Ubuntu Linux or any other flavor of Linux

Language / Tools

Java, J2EE, Hibernate, ExtJS

Client O/s

Windows 7 and Above

Database

Oracle 11g

Application Server

Jboss/Apache Tomcat

Web Server

Apache2

Browser Support

Chrome, Mozilla Firefox 10+, Internet Explorer 9.0 and above

Server Hardware requirements:

Processor

Intel Xeon Processor 2.1 GHz

Memory (RAM)

16 GB or higher

Storage Capacity (HDD)

Minimum 500 GB

Port Speed:

10 Mbps Public & Private Networks

System Features & Requirements

Capability Requirements

This subsection provides a high-level overview of the major capabilities of the Project.

Users Capabilities

The System will provide the following capabilities to users:

  • The Product Stores & Inventory Management Project will enable all authorized users to:
  • Provision to Raise Material Gate Pass

External Interface Requirements

User Interfaces

The user would then enter the required data for processing and press the Save or Submit button, after which the processing would be done and the user would be returned to the main page.

The user would then be able to use the different functionalities of the Product Stores & Inventory Management Project by clicking on various links that are provided on each page.

There would also be a Logoff button which would help the user to end his session with the application and he will be transferred back to the login screen.

Functional Requirement

Login

Description & Priority

This feature will be used to LOG IN to the application (only permitted users can use the PMS). It is done in order to prevent any misuse of PMS

Login users:

User, HOD, PGD, PD, Admin, PJB, PMB (Approval Members), and Office users/Clerks can log in with their assigned User names and password.

Stimulus / Response Sequence

When the user gives the correct username and password combination, he/she is transferred to the main screen or the PMS main page.

Functional Requirements

Purpose

To check the credibility of a user and to prevent any misuse of the product.

Inputs

The input will be a username, password combination, and project associated with the program. 

A user can have multiple roles and a role can have multiple features. The change password feature should be with admin only; if the user wants to have a change password feature user has to enter a security question that is provided by the user at the time of user registration.

Output

The user will be transferred to the PMS main page on successful validation and will be alerted if the validation is unsuccessful.

Validations:

Login Credentials.

  • After login user access only assigned project-specific and assigned role-specific data. Here users can be assigned multiple roles and multiple projects.
  • There will be one default project and default role configured.

PMS Login Use Case

PMS Login Use Case

MATERIAL GATE PASS

Free issue material is the item that is issued to the respective supplier in order to develop/manufacture the required item.

FIM has been categorized into two types.

  • Returnable
  • Non-Returnable

Generation of returnable and non-returnable gate passes.

  • Before gate pass generation user has to raise the gate pass requisition in a specified format with an auto-generated gate pass requisition number.
  • If the type of gate pass is returnable then PDC (Proposed Date of Completion) has to be mentioned (Mandatory).
  • If the gate pass purpose is FIM then QA/QC approval is required.
  • After the gate pass requisition is approved the generation of the gate pass is done by the admin.
  • The below Screen is for requisition for gate passes. To generate a gate pass, the admin has to select the gate pass requisition number on the gate pass generation page and get the gate pass requisition details with some entry fields like packed by & date, supervised by, SOB Number, and date.
  • After taking the concerned officer’s approval gate pass with items went to the security office for the check, if approved out of control number.

Gate Pass System

  • For the issue of an item/ BOM for an outside organization or supplier then the issue has been done by raising gate pass requisition.
  • Gate Pass requisition of two types 1) returnable and 2) non-returnable.
  • After gate pass requisition approval takes place and approval has been done the store admin raises the gate pass with item information.
  • Sends the item with gate pass to the security to out that item.
  • For gate passes also concerned officer’s approvals are mandatory

Gate pass requisition

Returnable:

In the case of items issued on returnable gate passes, the cost of FIM will not be added to items received in the supply order.

  • Requisition gate pass raised by user &approved by project director
  • Gate pass raised by store member/ issued by store member which required authorized officer’s approval.
    • Issue of returnable gate pass max period allowable is 11 months (In PDC, it has to be mentioned).
    • The system has to prompt/alert two weeks before the expiry of the above period in returnable gate pass.
  • FIM BG (bank guarantee) by vendor needs to do for a specific time and date.

Provision for a check box indicating the required FIM BG amount is available in the preform

Non-Returnable

Non-returnable gate pass would be generated for the following:

  • Transfer to other work centers (other labs/inventory) on a permanent basis

– FIM BG (bank guarantee) by vendor needs to do for a specific time and date.

– External issue voucher prepared by the stores with a gate pass

– Inclusion of FIM cost lot-wise/Total cost of supply item when delivery takes place.

– External issue voucher with a gate pass both need to approve

  • Requisition gate pass raised by user & project director
  • Gate pass raised by store admin which required authorized officer’s approval.
  • External issue vouchers are prepared for all items irrespective of their destiny.

– Deduction from stores will be done after approval of external vouchers from respective users and authorities and receipt of Voucher (Acknowledgement) details from another unit.

– FIM gate pass going to labs conversion issue voucher prepared for items flight hardware.

– Nonflight items FIM to other labs external voucher, transfer voucher, and gate pass issued

– Certified received voucher (CRV) from the other inventory once received, the external voucher is prepared.

Note: All items go through returnable/non-returnable gate passes only.

In case a vendor brings an item for entry into the project, a pass is prepared by MMG and sent to Security online to allow the firm inside.

In order to deny permission for entry to those items that were sent on returnable gate passes, it is suggested that a format/ screen be provided for the user to request for the issue of pass by MMG. In that format, the User has to state whether the items being brought inside by the vendor have gone out on returnable gate pass or are being supplied on S.O He has to give reference to S.O or returnable gate pass.

Where a gate pass is prepared whether returnable or Non-returnable, periodically the control no and date issued by Security is to be entered against the gate pass. In case of returnable gate pass corresponding control no and dates are also to be recorded.

Gate pass generation

  • After gate pass requisition approvals, store admin generates gate pass to out the items which are issued to outside organizations/ suppliers as requested item/ BOM (FIM) wise.
  • By taking concerned authority approvals stores admin sends the same to security to out the item/ BOM.

Generation of returnable and non-returnable gate passes.

  • Before gate pass generation user has to raise gate pass requisition in a specified format.
  • If the type of gate pass is returnable then PDC (Proposed Date of Completion) has to be mentioned (Mandatory).
  • If the gate pass purpose is FIM then QA/QC approval is required.
  • After the gate pass requisition is approved the generation of the gate pass is done by store members.
  • The below Screen is for requisition for gate passes. To generate a gate pass, the admin has to select the gate pass requisition number on the gate pass generation page and get the gate pass requisition details with some entry fields like packed by & date, supervised by, SOB Number, and date.
  • After taking the concerned officer’s approval gate pass with items went to the security office for the check, if approved out of control number.

Gate Pass Requisition Screen for Returnable/ Non-Returnable: 

Gate Pass Requisition User Interface

TBL_GATEPAS_REQUISTITION

TBL_GATEPASS_ITEMS

Posted on

IT Banking Portal Student Java Project Using Eclipse

EXECUTIVE SUMMARY OF THE PROJECT

Synopsis 

The mini-project made by us is basically a demonstration of the banking systems around the world on a very basic scale, in which we have created a GUI (Graphic User Interface) using the eclipse platform of JAVA and using the file management systems in JAVA. Basically, we have provided an interface to add, delete and view the different many accountants of a particular branch of a bank and also to add, delete and view the different bank holders and also store their account numbers, contact numbers, and salaries in the file, just to use whenever required. We have used the file management system in JAVA to store the details of all the accountants and the account holders.

Introduction 

The application that is the essence of the project works by defining various classes that even have further subclasses so as to modularize the final code. The code is written in a neat fashion with appropriate documentation. It provides a smooth, unfaltering user experience so as to facilitate its use among all age groups.

The use of exception handling in Java is implemented so as to prevent the user from getting stuck in a process and understanding the use of the application in a more suitable manner. It eases the reading and understanding of naive runtime errors generated. The use of the multithreading concept in Java lets us use multiple threads at a single time and also lets us do multiple tasks simultaneously which is required in the banking system.

Problem Statement 

The motivation behind the project was the lack of a simple well-written application to access and modify the details of the bank accountants of a particular branch and the bank account holders at the same time. It gave us enough motivation to make a GUI-based application to solve the same. In a world like this, can a whole lot of the population afford to waste the time looking for the details in the hard-copied registers and looking for all the accountants and the account holders when they can be easily maintained as a simple application?

Objective 

The main objective of the project makes the user to access the details of all the bank accountant’s bank account holders. It also gives the accountant the authority to delete, and modify the details of the account holders but the reverse is not possible

because that’s the hierarchy in a banking system works in that way. The aim is to give the accountant entire power virtually on the application. With our application, we have achieved just that. The application could have been designed in many different ways, but we have produced a solution of application that minimizes time complexity as well as space complexity by using Encapsulation, Polymorphism, Inheritance, and data abstraction. Along with these, Interfaces and various access modifiers have been implemented so as to maintain privacy and definition of access in different blocks Of code. The use of exception handling lets the user know exactly what went wrong.

METHOD

The application works by reading all the accountants and the account holders from a different file, which can be updated by the proprietor of the application, and also the same power is given to the admin of the bank. The file has the information stored in a particular format, which is decoded by the string reader functions in the code. Each time we enter or want output from the file we have to read this string reader function which is an in-built function of java and can be directly used just by importing the required files.

If there exists an object for the particular accountant or the account holder already, then that object is accessed, instead of creating a new one. If an object that is not available in the file is to be accessed then that object needs to be created and then accessed hence access to that object is not allowed and hence access is denied. We have to make sure that the object we want to access is present in the file system otherwise we have to create an object. The usage of various JFrames also enables us to increase our scope and work beyond the limitations of java by using the GUI effectively to give users an attractive interface to work with and get the work done.

SYSTEM REQUIREMENTS:-

  • Eclipse platform for JAVA GUI (Graphic User Interface)
  • JDK(Java Development Kit)
  • Windows Operating System

WORKS DONE:- (SCREENSHOT PF OUTPUT AND EXPLANATION)

  1. Main Page:–

This is the main frame that will be displayed as soon as our project gets executed. This is also the first page and the directive page as it directs us either to the admin section or to the accountant section. It consists of two buttons ADMIN LOGIN AND ACCOUNTANT LOGIN.

  1. Admin login page:–

This is the page that gets displayed as soon as the user clicks on the admin login button.

It consists of 2 labels namely enter a name, enter a password, one button, one text field, and one password field to get the password. To hide the password we have here used the echo Code property of the password field to encrypt it.

  1. Login Failed:–

This page gets displayed as soon as the user gets the name and the password on the frame admin login form but the dialog box with the message “Sorry, Username or Password Error” only when either the password or the name entered is incorrect.

4. Admin login Section:–

This frame gets displayed when the user enters the correct name and password. It has 4 different buttons which will direct to the things written on them. Only the ADMIN can enter the details of the Accountant and no one else. It consists of the addition, viewing, and removal of the accountant.

5. Add Accountant Page:–

This frame appears when the Accountant login button has been selected and the name and password entered are correct. This frame consists of the heading Add Accountant and it consists of 6 labels and 6 text fields and 2 buttons. This

6. Accountant Added Successfully:–

This frame appears when an accountant is added successfully.

This frame comes under the admin section. It consists of a dialog box that is used to make a JOptionPane.showMessageDialog() function.

  1. Database of all accountants:–

This is the database frame of all accountants under the institution. This contains various information about the accountants.

  1. Deleting an accountant:–

This frame comes under the admin section.

This frame does the job of deleting an accountant.

This is in the control of the admin whether to delete or not.

  1. Record Deleted Successfully:–

This frame comes when the record is deleted.

This frame confirms that the record is deleted successfully.

  1. Accountant Login Form:–

This frame can be chosen from the main frame of the project.

In this framed name and password of an accountant has to be given and if it is correct then the accountant section frame pops up.

  1. Accountant Section:–

This frame comes under the accountant’s control.

In this Frame, the accountant can add and view users.

  1. Add Account section:–

This frame appears when the button to add an account is hit in the Accountant section.

This frame saves the user’s various details in the database.

  1. Account Added Successfully:–

This frame confirms that the user is added successfully. This frame comes under the accountant section.

  1. Database of users:–

This is the database of users.

This comes under the accountant view section.

FUTURE WORKS:-

  • Since the project was made on a very basic level the obvious future work for the project would be to inculcate into it more complexities of the real-life kind of banking system. Since the project we made was only for the students of the branch IT in its future work we can inculcate more branches
  • Another future work that might sound interesting is to provide a server to it and make it using a database like MySQL(My Structured Query Language) which is a database used often with Java to store the details and the contents into it. It will be relatively easier for both the user as well as the programmer to use MySQL instead of the file management system, this is because in the file management system, we have to distinctly code to read in a string or anything else but when using MySQL we can directly use the add, delete and modify inbuilt functions of the MySQL database system and connect it to the Java program through server and then take in the command from the user in java and then pass on the same command to MySQL. Java and MySQL can be connected to each other through database connectivity which basically connects them through

RESULT AND DISCUSSION:-

The main result of the project is that we are now able to create a banking interface within a branch and between the accountants and the bank account holders. It can also be used to display the details of the users/bank account holders if we want to know something about them as and when we require it.

The usage of JFrame also enables a good graphical user interface making the banking system look more attractive and hence more appealing to the user. Since we have used many components on the JFrame like the text fields, password fields, radio buttons, and other buttons. All the components within them contain a lot of properties that can further be used to make it more attractive and more user friendly and also more encrypted in a way hence ensuring the data encryption in the Java program.

CONCLUSION:-

This was our project ever involving the connectivity of a language with the file management systems. This surely taught us a lot of things like how to store the details and how to look for the details in the backup database and how to create a database and how to back up our data regularly. Through this project, we ended up making an IT portal that has important significance and is very essential to us all. Through this project, we have gathered more knowledge about java, eclipse, and file systems in java. We also got to know a bit more about databases and how we use them.

This project also taught us how to work in a team and taught us various leadership skills and how to coordinate in a team and get the work done.

Posted on

Employee Task Management System Web Project using PHP and MYSQL

Problem Description

We need to make a system in which mentors can assign tasks to the employee and other mentors can monitor the availability of employees and on that basis, they can assign him/her new task. As well as employees can see all the assigned tasks with priorities. The app should be able to: Store data on new Employees/Trainees and new Task Assignments Employees can see the availability of other employees, trainees, and interns but trainees will not be able to see other availability. Employees can assign tasks with details like task name, task description, assigner, priority, and expected hours for completion to other employees’ or trainees’ ToDo lists considering the maximum limit of a total of eight hours for an employee before assigning any task.

Target Audience

This is a very common problem in companies where an employee already working on an assigned task and another mentor or boss going to assign him a new task, S/He might not know the employee’s availability and the priority of the task on which the employee already working. In that scenario, there will be lots of communication going around to assign the task, due to which task going to be delayed. To resolve these issues and make employee availability transparent, we need to make a system in which mentors can assign tasks to the employee and other mentors can monitor the availability of employees and on that basis, they can assign him/her new task.

As part of the curriculum of B.tech and to gain practical knowledge in the field and Python programming and web development we have made this project. We have boosted our skills through it.

In this Project, we have worked on VS Code and GitHub. Git Bash, Mysql, Software xamp, CSS, and HTML.

Employee Task Management System is created in PHP and MYSQL. It deals with the rundown of workers in an organization or an association. It likewise contains the training went by every Employee. Representative is the foundation of an organization so the Employee Management System is an extremely useful framework for an association or organization.

It also contains training attended by each employee. The employee is the backbone of a company so the Employee Management System is a very helpful system for an organization or company. This system also manages the company employee details like their attendance, their performance, salary details, and leave details.

This section compresses the assessment of the writing important to the Employee Management System. It looks at hypotheses, ideas, methodologies, strategies, and systems important to the venture.
Comparative existing advances identifying with the improvement of the Employee Management Systems are talked about.

In this Project, we have worked on VS Code and GitHub. Git Bash, Mysql, Software xampp, CSS, and HTML. Employee Management System is created in PHP and MYSQL. It deals with the rundown of workers in an organization or an association. It likewise contains the training went by every Employee.

Representative is the foundation of an organization so the Employee Management System is an extremely useful framework for an association or organization. It also contains training attended by each employee. The employee is the backbone of a company so the Employee Management System is a very helpful system for an organization or company. This system also manages the company employee details like their attendance, their performance, salary details, and leave details.

Design Diagrams:

Use Case Diagram:

Data Flow Diagram:

ER Diagram: Sequence Diagram:

Activity Diagram:

Functional Requirements

REQ-1: Authentication 

  1. Login- The user can log in to the system with his/her username and
  2. Logout- The user can log out from the
  3. Login failure- If the user does not exist in the database or the user has not yet been authorized by the

REQ-2:Authorization 

  1. User role check- After logging in, the user role will be checked from the database and the user interface will be displayed according to their role.

REQ-3: Employee Management 

  1. Display- Users with defined roles can display the content of the database. To be more specific, an employee can only view his/her personal Boss and can not only see his/her personal information but also employee’s information who are under his/her department or school.
  2. Edit- A user with an employee role can edit his/her specific personal

information. Boss can only edit employees’ personal information that is under his/her coverage except for user role type. The Boss can check employee availability.

REQ-4:Trainee Management 

  1. Training – The Boss and employee shall create training tasks and assign them to other Bosses and employees and employees and trainees respectively that are required to attend the training as well. Boss and Employee can also check the availability of the trainee.

REQ-5: Task Management 

  1. Tasks – Boss and Employee can check assigned tasks, they can check task priority. they can also create the task and assign the task.

1. Sign Up
2. Login Up
3. View Employee Details
4. Create Task
5. Priority
6. Availability
7. Assign Task
8. Task Status
9. Task Done
10. Task Details
11. Personal Details
12. Submit Task

System Features

Module Description

Sign Up: Bosses, employees, and trainees will sign up using their credentials.

stimulus: boss/employee/trainee will sign up through the signup button.

response: dialogue box for “thank you for signing up” appears.

Log in: Boss, employee or trainee will log in to the system using their unique ID.

stimulus: boss/employee/trainee will log in through the login button.

response: for boss/employee/trainee different pages will appear respectively.

View employee details: contains employees’ details.

stimulus: click on the button to View employee details.

response: Details appear (only boss and employee can view details)

Create Task: boss can create tasks for employees or another boss. Employees can create tasks for trainees or other employees. trainee can not create tasks.

stimulus: click create task button.

response: the task will be created

Priority: Check the assigned task priority.(boss/employee/trainee)

stimulus: click on check assigned task priority.

response : shows priority(High,Medium,Low).

Availability: check availability of boss/employee/trainee for assigning the task.

stimulus: click on the check availability button.

response: shows availability.

Assign Task: After creating the task the creator will assign the task to the boss/employee/trainee.

stimulus: click on the button to assign a task.

response: Task will be assigned

Task Status: change the task status whether it is completed/submitted/in progress.

stimulus: click on the button to change task status.

response: changes will be done according to your status when you choose options from it.

The task is done: The feature indicates the task is done. Only bosses and employees can access this feature.

stimulus: click on the task done button.

response: status will be updated once the task is done.

Task Details: will get trainees through the details of the task assigned.

stimulus: click on the View Task Details button

response: details appeared

Personal Details: will display personal details of the trainee to her /him.

stimulus: click on the View personal details button.

response: personal view appears to him/her.

Submit Task: The feature is for trainees only, to submit the task.

stimulus: click on submit task button

response: the task will be submitted.

Future Scope

1) AI is applied in almost every industry and may become a standard in the near future. 

2) Data visualization represents the data in a visual and understandable manner: graphs, diagrams, maps, etc.

Conclusion

This is a customized task management tool that enables your enterprise to manage all tasks efficiently in this troubled time & even in the post-COVID age. Our robust task management app help organizations face challenges related to project management & gain a higher Return Of Investment over the period while meeting deadlines and utilizing resources effectively.

Download the Complete Employee Task Management System Project code, Report, PPt, and Design Documents

Posted on

IoT based Attendance System Project Using Blockchain and JAVA MySQL

The success of this IoT-based Attendance System app will ensure that many more parents and organizations will be motivated to use this common platform. It becomes complicated when strength is more. With the increase in technology, attendance monitoring is designed with android or web-based applications. However, the intention of this design is to provide a Blockchain-based app that can be downloaded and used by the organization with no third-party control to meddle with the data.

There is an update option to modify attendance when it’s needed. However, the modifications are recorded and tracked, just in case, it’s a fraudulent activity. Attendance is captured using IOT automatically and is entered into the blockchain which makes the data tamper-proof, secure and robust. The privacy of its users is preserved because the user ids are generated by a trusted third party. This data is available for the government for Scholarships and other related decision-making.

IOT-based Attendance System using Blockchain is an application that is made for students and faculty of a particular college to maintain students’ attendance which is captured through an IOT device(biometric) and then the attendance is stored in the Blockchain. Blockchain is used in this application to ensure safety and a tamper-free environment as the data cannot be manipulated and is used for government purposes.

Objectives

Generally, in many institutions attendance is monitored and marked using conventional systems like android or other similar web applications. Few conventional databases do not have features like checking whether any information has experienced unauthorized changes or not. In this system when the data is entered into the blockchain, no one is allowed to edit or delete the data.

This makes the application transparent and different from other web-based attendance systems as IoT is used to capture attendance through biometrics of the students in the class. Students’ poor attendance rate is one of the most challenging problems tackled by college management today. With the help of this application, student attendance rates can be improved which is also helpful for the government to take precise decisions regarding scholarship-like schemes for students with transparent data. Using blockchain and some encryption techniques, this application is made secure from any manipulations.

Student Login Page

Methodology

The fingerprint module will collect fingerprint data from multiple users and sends it over the internet to the website. The IoT-based Attendance System website is coded in HTML, and CSS, JSP has a MySQL database, and records of attendance are stored in Blockchain. By logging into the website, the student can view all their attendance records. The timestamp of students’ attendance is encrypted and stored in the blockchain.

CONCLUSION AND FUTURE SCOPE

This IoT-based Attendance System application helps to automize the attendance system and makes it easy to manage all the data. Encryption, decryption, and blockchain make the application very secure. The application has a very user-friendly UI and is made to keep UI and UX in consideration.

The future enhancement of this IoT based Attendance System application is

  • To use Ethereum to make the application up to date with the technologies
  • To generate automatic weekly and monthly reports

DATABASE TABLES SCREENSHOTS

Tables in the project.
Test case showing the home page after pasting the URL in the browser
Test case showing navbar functionalities working.
Test case showing login is done and navigated to the home page
Test case showing student registration is working.
Test case showing faculty registration
Test case showing faculty registration is working.
Test case showing attendance stored in blockchain

IoT based Attendance System Using Blockchain
Test case showing student’s attendance records.
Test case to get student report
Test case showing Student’s attendance report.
Test case showing download report is working
Test case showing all student details.
Test case showing all student’s attendance records.

Flow Chart Diagram:

Flow Chart

Architecture Diagram

Architecture Diagram

Usecase Diagram:

usecase diagram

Software Requirements

Programming Language: Java
Graphical User Interface: HTML, CSS with Bootstrap, JSP
Libraries: MYSQL connector jar file, Apache Tomcat jar file
Encryption Algorithm: SHA-256
API: JDBC
Framework: Java EE
Tool: Eclipse, MYSQL

Hardware Requirements:

IOT Fingerprint Scanner

Posted on

Hospital Patient Medical Records Information Project App

Introduction

Information and communication technologies (ICTs) have great potential to improve health in all countries by enhancing access to health information and making health services more efficient. Mobile applications (apps) and other related software can also improve the quality of services and reduce their cost. The aim of the Patient Medical Records Information project was to enable health care practitioners such as doctors and nurses working in hospitals to be able to retrieve patient medical information remotely on any mobile device.

In this Patient Medical Records Information report, I will outline the research I conducted in choosing various technologies. I will discuss the problems I encountered and the solutions I came up with to overcome these issues in creating the specific application. I will also discuss the many technologies I used in the creation of the app including a data model representing the design.

The architecture of the solution

The overall structure of the solution is that the mobile app is being created for the hospital to maintain patients’ records and keep nurses and doctors up to date without carrying heavy paperwork around with them. The technologies I used to create this app suggested by my supervisor were Ionic, PHP, Angular JS, JavaScript, and MYSQL.

PHP provides integration of general-purpose programming and web-development scripting language. It is suited for server-side web development, and scripting and is used for professional websites. AngularJS is used for dynamic web apps and allows you to use HTML as a template language extending HTML’s syntax to express the application’s components clearly and concisely (Docs.angularjs.org, 2016). I chose both PHP and AngularJS because I had very limited knowledge of how they work and I wanted to improve my knowledge and skills in using them and they were also free. 

JavaScript is a programming language used to make web pages interactive (Chapman, 2016) and MYSQL Database is an open-source relational database management system (RDBMS) based on Structured Query Language (Search EnterpriseLinux, 2016).  Both of these programs were chosen because my supervisor requested me to use them and they were also free to use. Finally, Microsoft AZURE Cloud storage is open cloud storage, flexible, enterprise-grade cloud computing platform (Azure.microsoft.com, 2016). I decided to use this platform as my supervisor provided it to me free of cost I researched it and I found a lot of information online to help me complete this project.

The clients who are the doctors and nurses wanted to be able to log in to a mobile app to retrieve information in relation to patients. Firstly the doctors’ requirements were to be able to see all of the patients registered to him/her and the associated patient information. Nurses wanted to be able to log in and see all patient files and associated information as they worked with all patients. The second requirement was that once the doctor/nurse logged in to the mobile app they would have the ability to update the patient records for example blood pressure, heart rate, types of medicine, etc and they could also add notes or remarks. When the remarks and related updated information is added to the mobile app it then updates all the medical history and notes related to the patient. Furthermore, once the doctor/nurse checks the patient’s information in the future the patient’s information will be updated which makes it an effective and efficient method in contrast to multiple physical files.

The Hospital Patient Medical Records mobile app itself is written in AngularJS and JavaScript and through the HTTP requests the mobile app sends the requests to the PHP and the PHP then retrieves the data from the cloud MYSQL and transmits the data back to the mobile app.

Class diagram and Data Model

Through the HTTP requests the mobile app sends the requests to the PHP and the PHP then retrieves the data from the cloud MYSQL and transmits the data back to the mobile app. I designed the mobile app using these technologies as it was a requirement of the project given by my supervisor.

Technologies used

The technologies used included:

  1. JavaScript
  2. PHP
  3. AngularJS
  4. MYSQL Database
  5. Microsoft AZURE Cloud storage 
  6. Ionic

I chose both PHP and AngularJS because I had very limited knowledge of how they work and I wanted to improve my knowledge and skills in using them and they were also free. 

JavaScript and MYSQL Database were chosen because my supervisor requested me to use them and they were also free to use. I utilized Microsoft AZURE Cloud storage as my supervisor provided this platform to me free of cost and I researched it and found a lot of information online to help me complete this project.

Problems Encountered/Solved

At the beginning of the Patient Medical Record project, I was overwhelmed with the task at hand as I didn’t know where to start or what to do, so my project supervisor guided me and gave me advice about how to commence the project and what to do to begin.

The first time I tried to retrieve the data from the database it took me 4 days to retrieve it. Subsequently, I spoke to one of my colleagues and my project supervisor and did some research online and I figured out how to retrieve the information more efficiently and effectively.

Time management was an issue because I had many assessments to do and I left work late and I was running out of time in the end. For example during the Easter break, I had numerous projects due so I found it difficult to allocate time to all of the different assessments. I also wasted my time using a Google database called Firebase at the beginning of my project but later on, I decided not to use it because of the project requirements, and as a consequence, I wasted 2 weeks.

Also in relation to time management, I didn’t anticipate how time-consuming the research from the project would be. E.g. it took me a number of days to understand PHP and learn how to write a PHP script that could talk to the database. AngularJS was never taught in college so I had to take the time to teach myself. Although I completed the project in the allocated time I learned the importance of organization and prioritizing work.

Conclusions

Mobile technologies are emerging as a powerful tool for health information transfer including making patient information portable and accessible. I gained a lot of experience from using the 4 technologies and I believe I have the capability of using them if needed for future projects or for employment purposes.

I am also aware of how to solve specific problems and how to research these problems e.g. in relation to database retrieval or how to successfully manage my time. I recognize that I can overcome difficulties and achieve my goals successfully by being persistent, organized, and patient. Although working in isolation on individual projects it is important and is a necessary part of employment it is important to seek advice or guidance from superiors or colleagues that may shed light on an issue or provide a new perspective.

Recommendations

In terms of further developing the Hospital Patient Medical Records Information Project App, it could be linked to local GPs, pharmacies, and other health care providers so there is a complete holistic picture of the patient and his/her medical history. I would also have managed my time better as I was under severe pressure and time constraints and this may have affected the quality of the end product.

Posted on

Design & Development of Disaster Safety Android app

A Disaster Safety Android app that helps people inform you about everything that is nearby by using help centers before and during an accident. Also, a PHP-based website to enter data on the server-side and work with the android application successfully. The Disaster Safety mobile app also gives you the location of all your friends and family that have been accessed by the user. The app can store offline maps and information about help centers also comes through messages and is displayed on the map.

Innovation:

India being a disaster-prone country suffers a lot of casualties every year not because of the lack of resources but because of the lack of information on these resources. This app brings the resources to you, even when you are in the middle of nowhere and knows nothing about what to do in such a situation, Disaster Safety app can save your life.

Features:

  • It works in offline mode and saves the data.
  • It not only works at the time of disaster but also in various situations like you are any kind of trouble or your phone is lost.
  • Gives the news and the guidelines about the various disasters.
  • Can track the location of your friends and family in danger.
  • Notifies you when your friend or a family member is in danger.
  • Saves a lot of power consumption as works offline.
  • Locates the nearby relief centers, hospitals, and police stations not only by internet but also through SMS.

Database Model

admin user

Column

Type

Null

id

int(11)

No

username

varchar(30)

No

password

varchar(50)

No

family 

Column

Type

Null

member_id

varchar(13)

No

family_id

varchar(13)

No

permission_given

tinyint(1)

No

guidelines 

Column

Type

Null

id

int(11)

No

calamity

varchar(30)

No

before_cal

text

No

during_cal

text

No

after_cal

text

No

help 

Column

Type

Null

id

int(11)

No

latitude

double

No

longitude

double

No

type_of_help

varchar(30)

No

login 

Column

Type

Null

Default

id

varchar(13)

No

 

name

varchar(30)

No

 

status

tinyint(1)

No

1

latitude

double

No

0

longitude

double

No

0

gcm_regId

text

Yes

NULL

news 

Column

Type

Null

Default

id

int(11)

No

 

notification

text

No

 

info

text

No

 

date

varchar(10)

No

 

Posted on

Design & Implementation of Library Management System Java Project

Abstract

In every institute or city, there are libraries. A lot of software’s are being made in the past to manage the library system so that easy and proper functioning of the library can be there. This project aims at building such a project by implementing some of the functionalities that have been present in the older software’s using the content and the knowledge.

Giving a brief overview of the project is that this will be a core java project. The information regarding the books and members of the library is stored in the database. Very basic and user-friendly screens will be there for a good user experience and for the most part it will be implementing some easy and necessary features of the library management system.

functionalities :

  • Very friendly user interface.
  • Easy to issue and return books.
  • Easy to search books.
  • Adding and deleting members will be easy.
  • Adding and deleting books will be easy.
  • Can view all the members of the library
  • View all the books in the library

For accomplishing these functionalities very easy screens will be provided. Complex features of the general library management system will not be implemented but this system will be very useful for the staff in the library rather than the students. This will be small software implementing some easy features of the library management system in practice.

Introduction

The software Library Management System has the following main modules.

Insertion to Database Module  – Easy insert of books and members
Search Facility system  – search for the book
Deletion to Database Module – Easy to delete books and members
Issue Books  – Easy to issue books
Return Books  – Easy to return books and  charge fine on members and other basic operations

ER Diagram

ER Diagram

System Requirement and Specifications

Purpose:

This specification document describes the capabilities that will be provided by the software application ‘‘Library Management System’.

The system aims at providing the Library of an institute with better functioning and easy to issue the books and return books and many other facilities that can reduce the human work to an extent.

Scope:

 The software product ‘Library Management System’ will be an application that will provide information regarding the current situation and presence of books in the library and also very specific details of the library. Various functions can be performed like updating the number of books, issuing the books and adding and deleting members, etc.

References:

The details about the books and the members are provided by the Library head.

Overall Description:

The ‘Library Management System’ will have the capability to maintain information about the library regarding issues of books members of the library and fine and the students and many other things.

Product Perspective:

The application will be window-based. Very easy to use and good searching methods are provided to make it easy to search books and members.

System Interfaces:

The system has a very friendly interface and the java language provides the ease with which anyone can use it.

User Interface:

As the system will start there will be a menu where there will be some choices for the user about the management.
Each screen will have a title describing the things that can be done there. Most of the screens have an admin password box where an admin password is needed to fill. For general users, there is the option of searching the books only.

Product Description:

Normal users and students, cannot do the changes in the database. Only the admin using its password can change the contents of the database. Most things required a password. So it is designed for the admin to keep track of the records of books issued and other things.

User characteristics:

Educational level: He should be comfortable with the English language.
Technical Expertise: Should be comfortable using the general-purpose application on the computer.
Constraints: The whole system is user-driven. There are no warnings in the system if there is a decrease in copies of a book. The searching of the books and members is also very limited and no partial searching is there. The admin password can be changed only after doing changes in the code. As it is just a prototype so it lacks many features of the exact library management system.

Future Scope

As the project lacks many features like good searching of members and books, partial searching, and searching regarding many other fields. The details of the members are also very less. So this project can be extended very easily in the near future to make it more efficient and with more user-friendly frames and screens. Icons can be added to this project to look more attractive and very friendly. More modules can be added to make it do more work. More admin IDs and passwords can be added so that more Admins can use them and each admin can be provided with a different set of authority to change the contents of the database. More functions can be provided to the admin like changing passwords and fine to the library members. 

Posted on

Online Medical Shop DBMS Python Mini Project

This project is based and innovated on an Online medical shop, wherein we store all the details about the customers, the stock of the medicines, orders, and payments and also the project will include a page wherein the user will indicate the symptoms and will get a probable disease and the prescribed medicine.

The project is aimed to modernize and support existing small business owners. In the age of technology where online medicine is dominated by e-commerce giants such as 1mg, net meds, etc. We wanted to develop a solution for small business owners as well.

The existing Medicinal systems have the provision for any user to book a request for a particular medicine through e-commerce. And further, the traditional methods to visit the medicinal centers for mere inquiry are time-consuming and monotonous and the non-availability is disappointing.

The data relevant to the processing of the request may or may not be manually stored or be captivated in a file system that is prone to manual errors, inconsistency, redundancy, and difficulty in retrieval. With our system, the availability can be shown so, even if a customer wants a pickup of his/her medicine. they can do so without any problems. Our model also has an integrated web scraper, which is an innovation we have come up with. This scraper can scrape medicines off the net for data warehousing.

This system maintains the storage details of all the customers and medicines that are stored in the shop. The system will keep track of the orders made and the payment details. NoSQL will be used to store future suggestions and customer reviews.

The main part of the project will be a part where the customer will be able to select his/her symptoms and medicine will be referred to them. Along with the expected disease. We also would integrate Web Scraping of all the medicines related to a particular disease entered by the user to store it in our database.

Software Requirements

• Language support required: Python 3.5 or later, HTML5, JS, CSS3
• NoSQL database required: MongoDB
• Relational Database required: MySQL
• Windows 7 or 10 /Mac OS X 10.11 or higher, 64-bit /Linux: RHEL 6/7, 64-bit (almost all libraries also work in Ubuntu)
• Heroku and pip are preferred for deployment and installation of packages (such as Django,asgerif, mongoose, etc) specified in requirements.txt
• A web browser support is needed.

If using the software through deployment, no language support in your machine is required.

Conclusion & Future Enhancement

This project was successfully built and completed. The project is an online medical shop with two categories of users (admin and customer) who can update inventory and place orders respectively. We have also added a web scraper as an innovation to this project. However, there are a lot of changes and addition of functionalities that can be done, which we intend to do after peer and faculty review.

Some of the enhancements are :

  • Listing of products linked with images to generate a more shop-relevant UI
  • Remove some programming language constraints
  • Online Deployment
  • And changes that our faculty and peers suggest.

In the end, we would once again thank our college, examiners, faculty guides, and teachers to help us finish the project within the speculated timeline.

Posted on

Supermarket Management and Billing System Java Project

The project is on Supermarket Management and Billing systems. The supermarket is a huge shop where we all can find a lot and lots of products may whether grocery or fashion or utensils etc. in the various categories in different departments. Also, there is a huge number of staff in different positions. It has to keep all the records of its staff so that the employee management would be effective. So, to make such problems easier to handle we have developed this system that not only keeps authentic data may that be of transactions into and out of the supermarket or that be the information of its employee.

The manager module in the software helps to keep information of employees and the cashier and the data entry operator module helps to keep records of transactions inside and out of the supermarket.  The barcode scanning system in the software help to run the transaction process fast and effectively.

INTRODUCTION

The Supermarket Management and Billing System, a desktop application, is developed to provide all the facilities and services required in various shops like shopping centers, mini-mart, fancy shops, etc. The main objective of the system is to provide efficient transactions with minimal error.  Bar code scanning technology helps cashiers with faster and more efficient billing. Cashier, manager, and data entry operator are provided with their own authorization account so that only the authorized person can perform their respective jobs. Users in the system: –

  • Cashier: a – person who handles the transaction
  • Data entry operator- enter the products imported into the store as well as update the details.
  • Manager- supervise all the activities going on in the shop

Statement of Problems

  • Manual data entry takes much more time than the barcode method.
  • The manual calculation can generate errors while buying or selling goods.
  • More time consumption for any transaction and findings of the products.

Objective and Scopes

  • To provide an efficient and effective billing methodology.
  • To keep a record of every business transaction
  • Maintain the stock management and the billing system
  • Reduce the time consumption for every process in the buying and selling of goods.

Database ER Diagram:

Database ER Diagram

METHODOLOGY

The project is to do with the concept of OOP (Object Oriented Programming) with Java and relational database with MYSQL and for the excess printer for the billing process we use Visual Basic Script (VBScript).  Taking into account the statements of the problem, we developed a system that not only helps in maintaining precise transactions but also keeps track of every business that has been done. There is the provision of a login module for individual employees as per their job title after which they will be provided with their respective job functions. With the help of the software, they can achieve a better working experience along with consistent precision.

There are various organized tables which makes the software very effective. The shop assistant module is the symbol of modern business techniques. It is a customer-friendly module. The manager has an organized manner of employee management such as addition or removal of cashier or data entry operator or shop walker. S/he has access to the profile of every employee in his hand at any time of necessity. Logs module helps him/her to analyze the customer’s choice. Furthermore, the automation in the billing system helps the cashier in their transaction in a very precise manner. The use of barcodes makes it easier for making bills and the automatic calculation prevents them from simple mistakes.

CONCLUSION

Supermarket Management and Billing System are developed for the professional handling of the supermarket’s sales and buying as well as the management of the whole supermarket. It is very easy and useful application software that increases the productivity of the business.

Our project on Supermarket Management and Billing systems has been implemented successfully. We take this opportunity to express our sense of indebtedness and gratitude to all those people who helped us in completing this project.

Posted on

System Analysis and Design for Student Hostel Management System Project

Introduction

PURPOSE

The purpose of this SRS & System Analysis and Design document is to build a Hostel Management System Site to help students book hostel rooms at their own convenience, file complaints, and write reviews about the room.

INTENDED AUDIENCE AND READING SUGGESTIONS

The Hostel Management System project is useful for both students and hostel committee members.

PROJECT SCOPE

The purpose of this Hostel Management System is to ease hostel management and to create a convenient and easy-to-use application for students. The system is based on a relational database with room allotment, review, and complaint features.

The Application will be able to perform the following operations:

  1. Allot Rooms: Students will be able to choose hostel rooms according to their convenience and pay for the same.
  2. File a complaint: Students will be able to file a complaint regarding any of the facilities and if the complaint could not be resolved within the specified time, it would be sent to the higher authorities.
  3. Review the rooms– Seniors who have already stayed in the room will get an option to review a room in which they can upload the room pictures and write about the problems(if they had faced any).

Mess: Students will be able to pay the hostel fees, see their past payments and write reviews about the food and management.

ANALYSIS

Specific requirements

External Interface Requirements

User Interfaces

The goal of this Hostel Management System is to design the web application that will be used for the proper management of hostels. The user types are listed below-

  • Students
  • Hostel Committee
  • Mess Committee

ER Model

Hostel Management System ER Diagram

DESIGN

RELATIONAL SCHEMA

  1. Users
  2. Reviews
  3. Writes rev
  4. Rooms
  5. Complaints
  6. Writes com
  7. Student

USER INTERFACE DESIGN

GOAL

MAKE INTERFACE

  1. Pleasing to the eye.
  2. Simple to Use.
  3. Minimize the effort it takes for users to accomplish the work.

PRINCIPLES OF USER INTERFACE

  1. Layout
  2. Content Awareness
  3. User experience
  4. Consistency
  5. Minimize user effort

VARIOUS USER INTERFACES

  • HOME– It includes navigation among different pages. Starting with registration and login and address of other pages.
  • REGISTRATION/log in If you are a new user you have to register and if already a user only login is sufficient. After registration and login user will be redirected to the home page.
  • ROOM ALLOTMENT– After logging in it is necessary for the user to fill room allotment form if the room is already booked user will be redirected to the allotment form.
  • DASHBOARD– After booking the room user can see the status in the dashboard including username, scholar no and room booked.
  • REVIEW A ROOM – The user can review the room he is allowed only after login. This page is accessible only when the room is allocated. The review includes the description and the photo of the room. After the submission page is directed to another page from where the user can view his review and even delete it.
  • VIEW YOUR REVIEW– It keeps the track of the user’s reviews.
  • REVIEWS OF ROOMS– Before booking the room the user can view the review of various rooms.
  • COMPLAINTS– After room allotment, if the user requires to file any complaint he can register his complaint.
  • YOUR COMPLAINTS– It keeps a record of all the complaints filed by the user.

FLOWCHART

Hostel Management System Flow Chart Diagram

CONCLUSION

Till now, room allotment is done manually and physical presence is also required for the same. Students have to come a few days prior to the beginning of classes in order to select rooms. Hence this particular project deals with the problems of managing a hostel and avoids the hecticness of carrying out tasks manually.