Tag: Oracle

Posted on

E-Learning System Web Portal Java Project

Objective:

“e-Learning” is an educational-based java web application; this web portal helps college students to get all the resources & study materials of every course available on the online portal. All the students can access this website portal anytime and from anywhere on the internet. E-Learning System is a very good online e-learning portal compared to all web links given by Google, Bing, Yahoo, ChatGPT, or any website while searching for student course materials.

Contents

Existing System:

In Present Educational based E-learning system, students can get information from books or study materials provided by professors manually. But in this system, students may not get the related and sufficient information according to their syllabus. The above resources do not provide discussion forums between students and professors to clarify their doubts. There is no proper guidance for the students.

Proposed System

The main aim of this E-Learning system is to provide sufficient study materials to the academic students according to their syllabus from which students can easily download study materials of their relevant course. The first step is to register in order to access this website. In this system, we are providing discussion forums between students and professors where students can easily clarify their doubts. Modules of this website are Admin, professor, student, and mentor.

Modules:

Admin:

  • Admin can view all member’s details like professors/asst. professors, mentors, and students. Here each user (student/mentor/professor) can upload material.
  • The uploaded material can be verified by the admin. The admin can validate the material if the material is related to the subject. The validated materials are only visible to the students.
  • The admin can view the queries which are sent by the students to the mentors. The admin can also check how many solved queries and unsolved queries.

Student:

  • Each student must and should be registered before login. Here we have user authentication every time. Students can upload material, view material, and send queries. The upload materials first verify by the admin and then visible in the view material tab.
  • The student view uploaded material by all the users which is validated by the admin and he can download materials.
  • The student can send a query to the mentor if he/she has any doubts regarding academic subjects.

Mentor:

  • Mentor registration and login.
  • Mentors can upload material, view material, forward queries, and reply to queries. The upload materials first verify by the admin and then visible in the view material tab.
  • The Mentor view uploaded the material by all the users which is validated by the admin and he can download materials.
  • The Mentor can solve a query if he/she is unable to solve queries forward it to Asst.Professor/Professor.

Professor:

  • Professor registration and login.
  • Professor can upload material, view material, and reply to queries. The upload materials first verify by the admin and then visible in the view material tab.
  • The Professor view uploaded the material by all the users which are validated by an admin.
  • The Professor can solve a query and send it back to the mentors.

Software Requirements:

           Operating System: Windows 10/11

           Web Technologies: HTML, CSS, JavaScript

           Programming Language: Java, JSP, Servlets

           Backend Database: MySQL /Oracle 10G

           IDE / Work Bench: Eclipse/ Netbeans

Posted on

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

Posted on

Pharmacy Management System DBMS Project

Introduction

Pharmacies are an essential component of healthcare and handle the function of selling medicines. Even though the pharmacies do not seem different than any other shop, their functioning is very different due to various laws regarding medicines. For example, most of the medicines available in a pharmacy cannot be purchased without a prescription.

Even with a signed prescription, there is a limit on the quantity that can be purchased. Additionally, pharmacists can do a background check on customers’ medical history to ensure that they are not involved in medical abuse. In addition, there are other laws on the operations of pharmacies like a requirement for the safe disposal of expired medicine and the requirement of license for employees that mix/prepare the medicines.

Thus, preparing a Database Management System for a pharmacy not only requires a study of how things are handled from a customer or employee point of view but also the relevant rules and regulations.

With this Pharmacy Management System DBMS Project, we aimed to develop a comprehensive system that could deal with challenges faced in day to day operation of a modern pharmacy.

ER Modelling

The final ER diagram and UML diagram are shown below with explanations.

ER Diagram

UML Diagram:

1. A single customer can have multiple prescriptions. Thus, the relationship between them is one too many.
2. A prescription consists of multiple medicines, so the relation is one too many. In the case of refills, a prescription can generate multiple orders. So, this relation is one too many as well.
3. A single order can contain multiple medicines, thus the relationship is one too many. One order, however, can generate only one bill. Thus, the relation between bill and order is one-to-one.
4. A customer can make multiple purchases and hence, the relationship between the customer and the bill is one too many. This is because every bill has only one customer.
5. In the medicine table (stock), the medicine’s name and batch numbers can uniquely identify every medicine we have in inventory. The batch number is assumed to be unique among manufacturers.
6. Disposed medicines are weak entities and use foreign key medicine’s Name and Batch Number as their primary key.
7. One employee can receive multiple notifications and one notification can be sent to multiple employees, thus the relationship is many to many.
8. Multiple employees can dispose of the same medicines. Similarly, one employee can dispose of multiple medicines. Hence, the relationship is many to many.
9. One employee can prepare multiple orders. However, a specific order can only be prepared by one employee. Thus, the relationship is one too many. Relations and Normalization

Conclusion

The Pharmacy Management System DBMS Project was a good learning experience for implementing a real-world DBMS and helped us understand the nuances of full implementation. The most interesting part was the experience of starting from the real world and then translating the concepts into the terms of a DBMS. Paired with a capable application front end, it can handle day-to-day operations for a pharmacy.

Download the Complete Pharmacy Management System DBMS Project Code, Report, and deployment help for free.

Posted on

Restaurant Management System Oracle SQLPLUS DBMS Project

We have created a Database for a Restaurant as a part of our Database Management System project for the Database Management System. It has been developed using Oracle SQLPLUS software. In our database, we have considered all the major functionalities that are required in a restaurant. An organized system in any restaurant makes the job a lot easier to manage everything properly.

There are lots of different kinds of data to consider here. The various food details have to be stored. We should also have a record of all the customers who come to the restaurant. We need to maintain proper ordering data too to keep track of the various food items ordered by the customer. The feedback given to the customer and the table number where they sat may also be needed for future reference. Finance is one of the most important components here which has to be maintained well too. Then come the people who work in the restaurant and provide service to their customers. All of their details should also be kept properly.

The entire Restaurant Management System project is not only about just storing the data. The process of retrieving the data also should not be troublesome. The users should be able to access it easily and the process should be fast too. So, all the related data should be interlinked which will help in these cases. Many times, the users might also want to insert new data and update or delete them too. Those cases also we have considered. Even after these modifications, the database should work perfectly. Finally, in a nutshell, our work is useful for storing all the data in an organized and efficient manner, saving valuable time, and reducing the huge paperwork.

DATA REQUIREMENTS & CONSTRAINTS

The Restaurant Management System must have the following data requirements and constraints:

Customers who come to the restaurant are identified by their customer IDs and their names, ages, phone numbers, and addresses are recorded. The customer’s name should always be present. Customers give orders. Each Order is identified by order ID and has food ordered, bill no., and date. Bill no. and table no. should be unique. The maximum number of food items that can be ordered is 20. Payment has to be done for the order. Payment is identified by payment ID, it also contains the mode of payment (Cash, Debit card, Credit card, and UPI), total amount, amounts received, amounts returned, and date.

The total amount should be equal to the amount received – the amount returned and should always be greater than zero. There are three kinds of staff members in the Restaurant – Manager, Chef, and Waiter. Every staff member is identified by staff ID and has a name, date of birth, contact number, address, and salary. Staff name and contact should be present for every staff. Waiters’ salaries should be greater than ₹100. The chef’s salary should be greater than ₹500. The manager’s salary should be greater than ₹1000.

The chef cooks the food and the waiter takes and serves the orders. The order consists of varieties of food. Every food is identified by its food ID, it also has a name, description, and price. The price should be greater than ₹100 and lesser than ₹1000. Food names should be present for every food item. Customers are at tables. Tables are identified by table number and have several seats. Several seats should be more than 4. The customer gives feedback. Each feedback is identified by a Feedback ID and contains ratings (1-5) and comments.

FUNCTIONAL REQUIREMENTS

Insertion of Data

1. Details of customers are stored.
2. Details of the orders placed are stored.
3. Details of the dishes are stored.
4. Details of the tables are stored.
5. Details of the payments done are stored.
6. Feedback given by customers is also stored.
7. Details of the staff (manager, chef, waiter) of the restaurant are stored.
8. Details of which cooked food is stored
9. Details of which waiter served which order are stored
10. Details of which dishes are ordered in a particular order are stored

Removal of old data

1. A customer decides to delete his order on a particular date. So by his id and date of order, the staff id, food id, and order id should be deleted.
2. A customer decides to delete a food item from his order. So its food id needs to be deleted.
3. An order has been placed to cook which gets rejected at the last moment. So its food id for cook needs to be deleted.

Modification of data

1. A customer has changed his address. So, his address needs to be updated for delivery of his order by order_id.
2. The amount of payment needs to be updated for an order
3. A customer decides to change his feedback on the services of the restaurant
4. A customer decides to change his mobile number at the time of delivery of an order

Data Retrieval

1. Display the name of the customer who gave the order on the entered date.
2. Display the list of all the bills no for a particular food
3. Display the rating given by a particular customer
4. Display the name of the customer who did give a particular comment and rating
5. Display the table_no where a particular order was served

Posted on

Citizen Card System Java Project

Abstract:

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

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

UML Diagrams:

Use Case Diagram:

Sequence Diagram:

Activity Diagram:

Class Diagram:

Existing System:

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

Proposed System:

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

Output Results:

1. Homepage


2. Admin Login Page

3. Admin Home Page

4. View Users


5. Citizen Registration

6. Citizen Login


7. Citizen Home


8. View Profile

9. Insurance Info

10. Electricity Bill Payment

11. Bank Bill Payment

12. Gas Bill Payment

13. RTO Bill Payment

Software Requirements:

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

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

 

Posted on

Online Crime Investigation System Project in Java

Project Abstract: This Online Crime Investigation System software presents the part of an organization’s work as per the requirements, specifications, and conditions mentioned in the user manual. This application s/w has been developed and completed successfully and also tests successfully by taking “Test Cases” It is user-friendly and has all the needed menu options, which can be utilized by the user to perform the desired operations. Moreover, help messages are provided which will help any authorized user from using the system without trouble.

The proposed system is not limited presently. Presently we have to login to the system online and post the complaints. We can further develop the system by using the “Voice Recognition System”. So this project has got scope to get developed in the near future. The scope of the project exists throughout the life of the product development, testing and implementation.

Deployment of  Application:

1) Copy the Online Crime Investigation System application folder to

F:\Tomcat5.5.9\webapps\

2) Click on start.bat in the bin folder of tomcat

3) Create a User in Oracle as follows:

CREATE USER OCR IDENTIFIED BY OCR;

GRANT DBA TO OCR;

CONN OCR/OCR

Now place the all tables in the table.txt file at the SQL Command Line

And type the following command

COMMIT;

4) Create user DataSourceName(DSN) as

click  –> Start —> Control Panel—> Administrative Tools

Software Requirements:

  • Operating System: Windows 98 or above
  • Front end : HTML & JAVA SCRIPT, J2EE(JSP,servlets,Ajax),
  • Back end : Oracle 8i
  • Web Server: Tomcat 5.5.9
  • Front end  : HTML & XML
  • Middleware : J2EE(JSP)
  • Application server : Web logic 7.0

Crime Investigation System Screen Shots:

1.    Crime Investigation System

HomePage

Homepage for the Crime Investigation System Application

Overview

Functional Overview

This module/screen is the Homepage for the Crime Investigation System Application.

Technical Overview

This module Admin or Police Department or Customer can login through screen and customer can register.

Navigations

Customer Login ->Customer LoginScreen

AdminLogin ->Admin Login Screen

Home ->Application Homepage

Department Login ->Department Login Screen

Registration ->Customer Registration Form

ADMIN MODULE

2.    Admin Login Screen

Admin Login Screen

2.1.1    Overview

Functional Overview

This module/screen is used to Admin Login Process.

Technical Overview

  1. This module takes the valid Admin Username and password.
  2. The particulars are valid you will get Admin Homepage otherwise it will displays the message “Invalid Login Information”.

Navigation

AdminLogin->AdminLoginScreen

Action Controls

Control
Name		 Type Description Action
       
Login button Gets the particulars of the Admin Login Details. Admin Homepage
Clear Button Clear the fields on the form Login Screen

3.    Admin Home Screen

3. Admin Home Screen

3.1.1    Overview

Functional Overview

This module/screen is used to operate Administration Module.

Technical Overview

  1. This module is used to create new Police Departments and updating the existed department details.
  2. This module is used to create new thief Information and updating the existed thief information
  3. Creating New Caution Information.

Navigation

AdminLoginProcess->AdminHomePage Screen

Action Controls

Control
Name		 Type Description Action
       
New Department HyperLink Displays the New Department  registration Form Department Registration Form
All Departments HyperLink Displays the existed department details screen List of departments
New Thief Information Hyperlink Displays the New thief  registration Form Thief  Registration Form
Thief Information HyperLink Displays the existed thief details screen List of Thief Information
Caution HyperLink Displays Caution registration Screen Caution Registration Form

4.    Department Registration Screen

Department Registration Screen

4.1.1    Overview

Functional Overview

This module/screen is used to register New Department Information.

Technical Overview

  1. This module takes the valid new Department Information and Login details.
  2. These New Department particulars will be stored into “POLICE_DEPARTMENT” database table and login details into “LOGIN_MASTER” table.

Navigation

New Department->Department Registration Screen

Action Controls

Control
Name		 Type Description Action
       
Register button Gets The new Department    information and login details from the form. Stores the department data into table POLICE_DEPARTMENTlogin details into table LOGIN_MASTER
Clear Button Clears the field in the form New Department Registration form will be displayed

5.    Updating Department Details Screen

SCREEN1

5. Updating Department Details Screen

SCREEN2

Updating Department Details Screen1

5.1.1    Overview

Functional Overview

This module/screen is used to Display the list of Department and Updating the department  Information according  to the Department Id.

Technical Overview

  1. Click on Update then it will takes the Department Id and displays Screen2 (Popup Window).

Navigation

All Departments->Department Details

Action Controls

Control
Name		 Type Description Action
       
Update button Displays the Department  information of selected Department Id. Displays the Department Information Screen(Screen2)
Close Button Closes the Department Modification form Displays All Department Screen (Screen1)

6.    Thief Registration Screen

Thief Registration Screen

6.1.1    Overview

Functional Overview

This module/screen is used to register New Thief Information.

Technical Overview

  1. This module takes the valid new Thief Information.
  2. These New Thief particulars will be stored into “THIEVES” database table .

Navigation

New Thieves Information->Thief Registration Screen

Action Controls

Control
Name		 Type Description Action
       
Register Button Gets The new Department    information and login details from the form. Stores the thieves data into table THIEVES
Clear Button Clears the field in the form New Thieve Registration form will be displayed

7.    Updating Thief Details Screen

Updating Thief Details Screen

SCREEN1 

7.1.1    Overview

Functional Overview

This module/screen is used to Display the list of Thieves and Updating the thief Information according  to thief Id.

Technical Overview

  1. Click on Update then it will takes the thief Id and displays Screen2 (Popup Window).
  2. If you select thief category then according to the selected Category it will Displays Screen3

Navigation

Thieves Information->Thieved Information

Action Controls

Control
Name		 Type Description Action
       
Update button Displays the Thief   information of selected Thief Id. Displays the Thief Information Screen(Screen2)
Close Button Closes the Thief Modification form Displays All Department Screen (Screen1)

8.     Caution Registration Form

Caution Registration Form

7.1.2    Overview

Functional Overview

This module/screen is used to Create New Cautions.

Technical Overview

  1. This module takes the valid caution Information and will be stored into CAUTIONS Data Base Table.

Navigation

Caution->Caution Registration Form

Action Controls

Control
Name		 Type Description Action
       
Save button Gets the required input details. caution Information and will be stored into CAUTIONSData Base
Clear Button Clears the fields data New Caution Form will be displayed

DEPARTMENT MODULE 

8.    Department Login Screen

Department Login Screen

8.1.1    Overview

Functional Overview

This module/screen is used Department Login Process.

Technical Overview

  1. This module takes the valid Username and password.
  2. The particulars are valid you will get Department Homepage otherwise it will displays the message “Invalid Login Information”.

Navigation

Department Login->Department Login Screen

Action Controls

Control
Name		 Type Description Action
       
Login button Gets the particulars of the Department Login Details. Department   Homepage
Clear Button Clears the Form Details New Login Screen Will be displayed

  

9.    Department HomePage

Department HomePage

9.1.1    Overview

Functional Overview

This module/screen is used to process the Department operations.

Technical Overview

  1. In This module department can see his complaint details and thief information.
  2. Updating complaint status and modifying the selected thief informtaion.

Navigation

Department Login Process -> Department Homepage. 

10.    Requested Complaints

Requested Complaints

10.1.1    Overview

Functional Overview

This module/screen is used Display the complaints Information.

Technical Overview

  1. Updating the complaint status by changing the options in the Modify column.
  2. In options when the complaint status is ‘Closed’ then only you will get new option ‘ReOpen’ in the options

Navigation

Requested Complaints->Complaints Status

Action Controls

Control
Name		 Type Description Action
       
Update button Gets the modified details. Changes the status of the complaint in COMPLAINT_REG Table

 

11.    Thief Details Screen

Thief Details Screen

11.1.1    Overview

Functional Overview

This module/screen is used to Display the list of Thieves and Updating the thief Information according  to thief Id.

Technical Overview

  1. Click on Update then it will takes the thief Id and displays Screen2 (Popup Window).
  2. If you select thief category then according to the selected Category it will Displays Screen3

Navigation

Thieves Information->Thieve Information

Action Controls

Control
Name		 Type Description Action
       
Update button Displays the Thief   information of selected Thief Id. Displays the Thief Information Screen(Screen2)
Close Button Closes the Thief Modification form Displays All Department Screen (Screen1)

 

12. Customer Information

Customer Information

11.1.2    Overview

Functional Overview

This module/screen is used to Display all registered Customer Details

Navigation

Customer Information->Customers Information Screen

CUSTOMER MODULE 

12.    Customer Registration Screen

Customer Registration Scree

12.1.1    Overview

Functional Overview

This module/screen is used to Customer Registration.

Technical Overview

  1. This module takes the valid new Customer Information and Login details.
  2. These New Customer particulars will be stored into “CUSTOMER_MASTER” database table and login details in “LOGIN_MASTER”.

Navigation

Registration->Customer Registration Screen

Action Controls

Control
Name		 Type Description Action
       
Register Button Gets The new Customer information and login details from the form. Stores the employee data into table “CUSTOMER_MASTER”
Clear Button Clears the field in the form New Registration form will be displayed

13.    Customer Login Screen

13. Customer Login Screen

13.1.1    Overview

Functional Overview

This module/screen is used Customer Login Process.

Technical Overview

  1. This module takes the valid Username and password.
  2. If The particulars are valid you will get Department Homepage otherwise it will displays the message “Invalid Login Information”.
  3. If you forgot your password then click on Forget Password option.

Navigation

Customer Login->Customer Login Screen

Action Controls

Control
Name		 Type Description Action
       
Login button Gets the particulars of the Customer  Login Details. Customer    Homepage
Clear Button Clears the Form Details New Login Screen Will be displayed

 

14.    Customer HomePage

Customer HomePage

14.1.1    Overview

Functional Overview

This module/screen is used to process the Customer operations.

Technical Overview

  1. In this module customer can register his complaints and update the complaints.
  2. Customer can modify the complaint information, if the status is “Pending”.
  3. Checking the status of the complaints.
  4. Displaying all department details.
  5. Displaying all thief information.
  6. Changing the personal details.
  7. changing the password.

Navigation

Customer  Login Process -> Customer  Homepage

15.    Complaint Registration Screen

Complaint Registration Screen

15.1.1    Overview

Functional Overview

This module/screen is used to register the new Complaint

Technical Overview

  1. This module takes the valid new Complaint Information.
  2. These New Complaint particulars will be stored into “COMPLAINT_REG” database table.

Navigation

Complaint Registration->Complaint Registration Screen

Action Controls

Control
Name		 Type Description Action
       
Register button Gets The new Compliant   from the form. Stores the Complaint data into table “COMPLAINT_REG”
Clear Button Clears the field in the form New Complaint  Registration form will be displayed

16.    Thief Details Screen

Thief Details Screen

16.1.1    Overview

Functional Overview

This module/screen is used to Display the list of Thieves Information.

Navigation

Thieve Information->Thieve Information

17.    Department Details Screen

 Department Details Screen

17.1.1    Overview

Functional Overview

This module/screen is used to Display the list of Departments Information.

Navigation

Departments->Department Information

18.    Changing Customer Profile

Changing Customer Profile

18.1.1    Overview

Functional Overview

This module/screen is used to Change the Customer Information.

Technical Overview

  1. This module takes the modified Customer Information from (Screen1).
  2. These New modified   particulars will be updated into “CUSTOMER_MASTER” database table.
  3. If u want update these modified details then click on “Update” in SCREEN1
  4. If you want to change the password then click on “Change Password” then “SCREEN2” will be displayed

Navigation

Change Profile->Customer Information

19.    Complaint Status Details Screen

 Complaint Status Details Screen

19.1.1    Overview

Functional Overview

This module/screen is used to Display the list of Complaints.

Technical Overview

  1. This module takes the valid search options like datewise and compliant type.
  2. According to the selected search option the complaints will be displayed.
  3. Click on “Show All” button, If no option selected then it will display all complaints information.
  4. Click on “Search”  button without selecting any search option then it will display message “Select Valid Search option”

Navigation

Complaint Status->Complaint Information.