Medical Shop Management System Java Project using Oracle Database

Introduction

This is software that aims at easy management of medical stores. In the market, a lot of work is done manually. In this era of the computer revolution, where everything is digital, data management and operation also need to be computerized. The existing manual database management system is more problematic and tedious. The calculation of data is not always accurate. The computerized system would reduce the complexity of managing the records and making them secure and easy to access, and get any type of information like the product detail, patient, etc in an easy manner by a quick search.
This system keeps the records of medicines such as medicine name, MRP, MFG, expiry date, quantity in stock, etc. The software also generates patient or customer reports as print out for later reference. After booking the patient order, our stores provide the medicines by hand or home delivery together with the proper bill generated by this software.
This software focuses on high security so that no unauthorized user can make a random transaction. Only the person provided with the proper user ID and password can do the billing or see the reports. And then for signing up as a new user it requires an Authentication number is required which is only owned by the owner of the store. So that no random person can signup for the account.
The software provides two levels of security. As “only billing rights” and “managing rights” so that a person or staff or helper who is appointed for only billing purposes can not manipulate the data stored in the database. But the administrator who has the managing right can have complete access to the data.

Objectives:

The main objective of this software is to provide an easy way to submit information about medicines and some other information as well.
It also facilitates deletion or modification or searching of all information very easily. The system is also helpful for generating reports and statuses. The medical shop management system is software that processes computerized information and manages all the record of medicines which is under medical shop management.
The aim of this project is to make possible easy all the manual errors and problems by automating them, which the users are facing at different levels of management in medical stores as well as provide a high level of security for the data.

ER Diagram:

So in this project, we try to do the best of our effort and hard work to cover some parts of the system process.

Fast Query Process:-

Computerization of the query process is more economical than that of manual processing because the query is updated and stored instantly without any calculation mistakes here we have to just update the product master table or customer master table but in a manual process, we have to change all the records.

Entry new Records:-

Maintaining the records of new entry becomes very easy because every day there are new medicines coming into the market which has a huge demand in the market. So, it’s important to stay updated for patients’ health sake.

Maintenance of all of the records:-

Medical shop management helps in updating all the records from time to time.

Issuing reports:-

Issuing reports issues from the completion of the updating of all tables or records. Here reports issue status is maintained by which we know how much patient comes for medicines, we generate reports of stock status after updating the stock records, etc.

Highly secure:-

This software is highly secure because in the absence of authorized persons, nobody can provide medicines because they have a unique id or password to edit their records which are protected also.

Input or Output Screen Design

  • If the user clicks on generate report then the report page is visible otherwise log it is done according to the user´s rights provided.
  • Generate Report: Provides Report of the customer or patient for future reference and allows us to keep it as a Hard Copy.
  • A new user can get signed up by an authorized person for using this software.
  • The Main menu contains all quick links. In the menu bar, the user can jump to the desired location, saving his/ her time.
  • Search for the desired medicine quickly for modification or deletion.
  • View the stock as Table
  • Keep track of all the transactions by easily checking out the Sales Report
  • Hassle-Free Billing.
  • Easily Customize the purchases.

Download the complete project on Medical Shop Management System in Java & Oracle database using AWT and Swing with ODBC

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

Credit Card Application Portal Java MySQL DBMS Mini Project

Problem Statement:

The credit Card Application Portal provides a platform for Users to avail of a credit card by filling in the relevant details. Further, it enables them to manage card services in the application portal.

Description:

The Credit Card Application Portal not only enables users to avail of a credit card but also allows them to manage services related to it too.

The DBMS Project works in the following way:

• It initially checks whether a user is pre-registered at the application portal. If so, then he or she is directed to the services menu. If not, then it allows users to sign up as first-time users at the application portal.

• Upon completion of the above sign-up process, a confirmation email is sent to the user’s registered email id which he or she had provided during the sign-up process. The confirmation email also contains the user’s login credentials as well as his or her form number.

• Once the user receives the email, he or she is redirected to the initial login page of the application portal. Here, he or she can use the credentials that had been sent earlier to his or her email id to login into the services menu. Once the credentials are verified, the user is directed to the services menu.

• In the services menu, the user can avail of four major services i.e., he or she can update the pin or view his/her application details or view the type of card he/she would be issued with, or view the set of FAQs which he or she can refer to.

E-R Diagram:

ER Diagram Credit Card Application Portal

Tool to be used:

1. IntelliJ / Eclipse / NetBeans
2. WampServer / Xampp
3. Internet Browser (Microsoft Edge, Google Chrome, etc.)
4. PDF Viewer (Adobe Acrobat, Nitro Pro, etc.)

Modules in Credit Card Application Portal

This Java & MySQL Project is aimed at taking a step forward towards digitalizing the entire process of applying for a credit card as well as managing the same.

• Login
• Signup1
• Signup2
• Signup3
• CardType

LOGIN:

Credit Card Application Portal initially checks whether a user is pre-registered at the application portal.

• If so, then he or she is directed to the services menu. In the services menu, the user can avail of four major services i.e., he or she can update the pin or view his/her application details or view the type of card he/she would be issued with, or view the set of FAQs which he or she can refer to.

• If not, then it allows users to sign up as first-time users at the application portal.

SIGNUP1:

This module basically deals with inserting values into the database. Relevant details such as the User’s name, father’s name, date of birth, e-mail id, gender type, marital status, and his/their complete residential address are requested to be filled by the user in order to process the user’s application for availing a credit card. Upon filling in the above-mentioned details, a unique form number is generated which is associated with the user who has filled up the relevant details

SIGNUP2:

This module also deals with inserting values into the database. The user’s application is processed based on the form number generated in the previous module. Details such as Aadhar number, PAN number, educational details, salary, category, etc. are to be filled in by the user. Credit Card Application Portal Department of CSE, Sai Vidya Institute of Technology

SIGNUP3:

Being directed to this module from SIGNUP2, the user is further supposed to fill in details that would be stored in the database. Here, s/he is required to fill in the desired cash withdrawal limit, credit limit, monthly cycle, and the services which they wish to avail. Upon completion of the above-mentioned signup process, a confirmation email is sent to the user’s registered email id which he or she had provided in the SIGNUP1 module.

The confirmation email also contains the user’s login credentials as well as his or her form number. Once the user receives the email upon successful signup as a first-time user, he or she can use the credentials that had been sent earlier to his or her email id in order to login into the services menu.

Card Type

This module tells the user the type of card s/he would be granted. The type of card to be granted to the user is decided upon his/her income.

View Here and Download the Complete Credit Card Application Portal Java MySQL DBMS Mini Project Standalone Desktop application Source Code, Project Synopsis, Report, How to setup files, etc

Software Requirements

Programming language: Java, MYSQL
Operating system: Any OS (Recommended: Windows 10,
Windows Vista, Windows XP)
Application required: Standalone desktop application & Wamp Coding
language: Core Java

Related Projects on Credit Card Management System:

Java and MySQL Project on Credit Card Approval System
Credit Card Approval System Project in Java
Credit Card Approval System Project
Analysis on Credit Card Fraud Detection Methods CSE Project Abstract
Credit Card Fraud Detection Using Hidden Markov Model .Net Project Report
Credit Card Fraud Detection Using Hidden Markov Model Project Report
Analysis on Credit Card Fraud Detection Methods
Cyber Credit Card System Project Source Code In Java And Report
Petro Credit Card Management System Project with Source code
Cyber Credit Card System Java Project with Source Code
Credit Card Fraud Detection Using Hidden Markov Model Project Source Code
Credit Card Management System
Credit Card Approval System Java Project
Analysis on Credit Card Fraud Detection Methods Project
Credit Card Management System

Car Rental System Database Design Project

Data Requirements

The Car Rental System Database involves around three main entities Car, User, and Reservation

The car can be reserved from a rental location with a specific address. It has a unique Rental_Location_ID, a phone number, and a contact email. A rental location keeps track of the address where the car belongs using the street name, state, and zip code.

A rental location has several cars for rental. Each car is described by VIN, Registration Number, Color, Model, Manufactured year, Seating capacity of the car, whether it has Disabled friendly feature and its Status marked ‘Available’ or ‘Unavailable’

The car has a parameter Car Type. It can be ‘Economy’, ‘Standard’, ’SUV’, ‘Premium’ and ‘Minivan’. Car Type defines the rental price per day. A user can take Insurance per day for the rental car. There are different types of Insurance each having different medical coverage, collision coverage, and bodily coverage. Insurance Types are ‘Liability’ and ‘Comprehensive’. Car type and Insurance Type drives the Insurance price per day.

A user can reserve a car for several days. He can use any valid promotional code which is maintained by status. When a user books a car he mentions the start date and end date for which he needs the car. The end date will be hypothetical at the time of reservation and updated with the actual end date when the car is returned. The total amount and net amount are calculated based on start date, end date, rental price per day, insurance price per day, and promotional code if any

A user is categorized as a guest or customer. The user can continue reserving the car as a guest as long as he has not registered as a a customer. A user is uniquely identified by his/her license number. User information consists of his name as first name, middle name and last name, email, address, date of birth, and contact number

A registered customer will be provided with a login id and password. A customer can save his credit/debit card details for future payment

Partial payment can also be made at the time of reservation and the balance must be paid by the user during car return when the actual end date is known. If the user is a customer, he/she can pay through saved debit/credit card details

A user can add any accessories as part of his/her reservation. Accessories can be ‘Car Seat’ and ‘GPS’. A user can add as many accessories he/she needs as part of the reservation

The additional driver can be added as part of his/her reservation. For each additional driver, there will be an additional charge

A user can cancel a reserved car before the car has been rented. A reservation can have status as ‘Reserved’, ‘Completed’, and ‘Cancelled’. When the car is reserved, the status will be in ‘Reserved’ Status. Once the car is returned and the total amount is paid, the status will be ‘Completed’

Functional Dependencies

In Rental car location, Rental_Location_ID is the primary key
Rental_Location_ID —> {Phone, Email, Street_Name, State, Zip_Code}

Type of the car defines the rental price of the car per day
Car_Type —> Price_Per_Day

Type of the insurance defines the insurance coverage
Insurance_Type —> {Bodily_Coverage, Medical_Coverage, Collision_Coverage}

Insurance Type and Car Type defines the Insurance price per day
{Car_Type, Insurance_Type} —> {Insurance_Price}

A user is defined by his/her License_No
{License_No} —> {FName, Mname, Lname, Email,Address, Phone,DOB, User_Type}

In a user credential, Login_ID defines the rest of the attributes in the entity
{Login_ID} —> {Password, Year_Of_Membership, License_No}

Login_ID and Card_No in Card_Details defines complete card information
{Login_ID, Card_No} —> {Name_On_Card, Expiry_Date, CVV, Billing_Address}

Reservation_ID drives all the other attributes in Reservation relation
Reservation_ID —> {Start_Date, End_Date, Meter_Start, Meter_End, Rental_Amount, Insurance_Amount, Status, License_No, VIN, Promo_Code, Additional_Amount, Tot_Amount, Insurance_Type}

Payment_ID is the primary key of Payment relation
Payment_ID —> {Amount_Paid, Card_No, Expiry_Date, Name_On_Card, CVV, Billing_Address, Reservation_ID, Login_ID, Saved_Card_No, Paid_By_Cash}

Promo_Code defines other attributes in Offer_Details relation
Promo_Code —> {Description, Promo_Type, Is_One_Time, Percentage, Discounted_Amount}

Additional_Drivers relation
{Reservation_ID,Name} —> DOB

In Accessories relation, Accessory_ID drives the type and amount of the accessory
Accessory_ID —> {Type, Amount}

Download the Car Rental System Database Design Project Code, Report, and Presentation.

Online Job Portal Java Project Report & Source Code

Objectives of the project:

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

LITERATURE SURVEY

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

Limitations

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

Benefits

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

IMPLEMENTATION

5.1. MODULES

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

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

Administrator

All the users are controlled by admin. Administrator services are

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

Examination

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

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

Software Requirements: 

Operating System: Windows XP/2003 or Linux/Solaris

User Interface: HTML, CSS

Client-side Scripting: JavaScript

Programming Language: Java

Web Applications: JDBC, JSP

IDE/ Workbench: Eclipse with My Eclipse Plug-in

Database: Oracle

Server Deployment: Apache Tomcat 6.0

Screen Shots:

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

TEST CASE REPORTS 

Name of the page: Admin Login

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

Name of the page: Job provider Login 

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

 Job Seeker Login 

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

Name of the page: Exam Management 

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

 

Warehouse Management System Java Project

Warehouse Management System mainly consists of five modules

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

Master Maintenance :

Warehouse Management maintains the following master details for various purposes.

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

Receiving :

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

i) Purchase Order
ii) Goods Order

Shipment :

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

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

Billing :

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

Reports :

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

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

Software Requirements:

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

Oracle application Development for Mall managament

The following details regarding property management database requirements:

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

1) Weekend Outlets: (Friday & Saturday)

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

2) Permanent Shops

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

Activity Control System Java Project Abstract

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

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

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

PROPOSED SYSTEM

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

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

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

Software Requirements

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

Hardware Requirements

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

Insurance Company Management System

Objective:

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

Proposed System:

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

Modules:

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

CEO, Manager, Agent and Customer

CEO Module:

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

Manager Module:

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

Agent Module:

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

Customer Module:

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

Software Requirements:-

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

Web Based Library Java Project

ABSTRACT

The most important department in and across the departments of an Educational institution is Library department. It holds immense potential in terms of effectively and efficiently learning information through various resources available. The main purpose of the Library management system is to reduce the work of the Librarian. Library management system is being maintained manually till now, through this application it can be maintained in the database.

This is an Internet based & Web Based Library application that can be accessed throughout the web. This system can be used to search for all books, search books based on author, search books based on title and reserve books, find out book is in available state or not. This is one integrated system that contains both the user component and the librarian component.

EXISTING SYSTEM

This Web Based Library application maintains the details of books like what type of books are there, what books are in available state, and how many books are there for same title of different authors. This information is available only for librarian not for students.

The library management system is maintained manually till now, so the following disadvantages are occurred.

1. Wastage of time.
2. Work delay.
3. Decrease in the performance of the system.
4. More man power is required.

PROPOSED SYSTEM

In this Web Based Library system students are no need to go to library for reserving Book, just go to internet and search what types of books are there in library, search Books based on author, search books based on title and see what books are in Available state. In this way select which book we want and identify the book id and Reserve that book through reservation form. If more than one person requesting for single book, then the librarian see the list of reservation forms and issue the books based on First in First out order of reservation Forms and rejecting the other student’s requests. In this proposed the work delay and wastage of time will be reduced.

MODULE DESCRIPTION

The system “Web Based Library “consists of 2 modules.

1. Student module
2. Librarian module

Student module: students are first enter into the site by using user id and Password if these are correct then entered into site other wise rejects the request. In This site students are first search all books, search books based on title and search Books based on author in this students are seen the status of the book if is available Or not if it is available then see the book id for reservation purpose and finally Reserving the book through web.

Librarian module: librarian add new book details into database if books are Referenced once then keep the status as not available ate the time of adding new Book details. If librarian wants to modify the book details then update book details Option is available. If book are old then librarian can delete the book into database. Librarian can also see the search the all books, search books based on title and search books based on author. And issue the books to students. Student’s requests Forms are stored into reservation table. Librarian can see those forms by clicking the Option of list of reservation forms then issue the books to those students who are Requesting for what books. Librarian can see the inventory of all books, list of issued Books, list of renewal books, list of all students. If librarian wants to send messages To students then see the student’s details and send messages to their mail ids or call to their mobile numbers. Librarian can issue books to students’ maximum of four.

Software requirements:

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