Photo Lab

1. Introduction

1.1 About Project

This project is aimed at developing an Photo Lab Management System (PLS) for a photo studio. This system can be used to store the details of the customers,employees,work details and update the details based on the customer details, material details.

DEO enters the details about the customer,materials,deletion of the customer details and admin mainly checks the details of customer,materials and enters the details about the employees and updates the details of employees in frequent intervals. Admin also deals with deletion of the DEO and employee details and he also plays a role in releasing the lock of the DEO account when it is locked.

2. Project Analysis

2.1 Purpose of the project

The Photo Lab Management System (PLS) is a complete system for managing photo processing labs in a most efficient way. By implementing the computerised management for Billing, Inventory you could utilise your resources to the fullest extent of efficiency thereby stepping up the productivity levels. This has been designed and developed after a thorough study of Photo Finishing Industrys needs and manual system of operations. So this product has come out as whole and Smooth Solution for your needs. In every data entry, before storing the data in computer, the system will confirm with the user, asking questions like 'Is this Ok? to ensure correctness of entered data in all respects. If it is not, then the user is in his liberty to correct it.

2.2 Existing System Commonly every details about photo lab are entered in the form of paper work. All the details about billing,employee salary,materials used for photos development and customer details comes under the paper work of photo lab.Person should be able to enter entire details about every thing in the paper work every work.But this is a difficult work for any one which takes a lot of time and this is the main disadvantage of the existing system.Costumer should be satisfy with product and should give the output to the customer in intime. We should not test the patience of the customer which definetly effects the business side.2.2.1 Problem in Existing System:

Problem is mainly the paper work.This should be rectified.

2.3 Proposed System

The system has full validation process in each and every data input element, to ensure that the user has entered only valid data. So the mistakes are eliminated in a great way. In every data entry, before storing the data in computer, the system will confirm with the user, asking questions like 'Is this Ok? to ensure correctness of entered data in all respects. If it is not, then the user is in his liberty to correct it. This manual is split into sections like Operations, which covers entering of day to day and periodical transactions that take place in a lab. Various reports that are available in the system are explained in the Report section.Usually data entry operator mainly makes a detail analysis every day and updates the data every day in the system about billing,salaries,materials,etc. Administrator checks about status of the photo lab every day.

3. Requirement Analysis

3.1 Purpose and Scope This project is aimed at developing an Photo Lab Management System (PLS) for a photo studio.

Usually data entry operator mainly makes a detail analysis every day and updates the data every day in the system about billing,salaries,materials,etc. Administrator checks about status of the photo lab every day.

3.2 Users of the System

1) Data Entry Operator(DEO)

2) Administrator

4. SpecificRequirements

4.1 Functional Requirements and Non-Functional Requirements

a.Functional Requirements:i. The tool mainly helps in giving perfect photo wanted by the customer.

DEO Login into his account.

Enters the details of the customer.

When the work status is completed then he uploads the customer photo and stores in the database.

The image is retrieved automatically from the database while seeing the customer details entered.

ii. Maintainance of employee salaries,materials updation and customer bills.

Enters the customer details and material details every day.

Updates the material details and customer details.

Admin Login into his account.

Maintains the employee details.

iii. Utilities should be maintained such that every task is given separate icon in the tool.

iv. Every customer is given unique number.

Number for every customer is automatically generated.

v. Administrator checks whether every customer paid bills or not.

Admin Login into his account.

Checks the customer details.

vi. Data Entry operator should maintain all the details about the

customer and administrator maintains the details about the employee.

b. Non-Functional Requirements:

i. Secure access of confidential data (users details). SSL can be used.

ii. 24 X 7 availability

iii. Better component design to get better performance at peak time.

iv. Flexible service based architecture will be highly desirable for future extension.

4.2 User Interface Requirements Professional look and feel.

Help should be very user friendly.

User interface should include good images.

4.3 Proposed System Architecture

5. System Requirements

5.1. Technologies Used:

1. UML.

2. J2EE. JSP, Servlets.3. XML.

4. AJAX .UML:

The Unified Modeling Language (UML) is an open method used to specify, visualize, construct and document the artifacts of an object-oriented software-intensive system under development.[1] UML offers a standard way to write a system's blueprints, including conceptual components such as:

actors,

business processes and

system's components, and activities

J2EE: Java Platform, Enterprise Edition or Java EE is a widely used platform for server programming in the Java programming language. The Java EE Platform differs from the Java Standard Edition Platform (Java SE) in that it adds libraries which provide functionality to deploy fault-tolerant, distributed, multi-tier Java software, based largely on modular components running on an application server.

XML:

XML (Extensible Markup Language) is a general-purpose specification for creating custom markup languages.[1] It is classified as an extensible language, because it allows the user to define the mark-up elements. XML's purpose is to aid information systems in sharing structured data, especially via the Internet.

5.2. Tools Used:

1. Eclipse 3.3 2. Apache Tomcat 5.0 3. Oracle 9I

4. Rational Rose 2002

5. VSS

ECLIPSE 3.3:

Eclipse is a multi-language software development platform comprising an IDE and a plug-in system to extend it. It is written primarily in Java and is used to develop applications in this language and, by means of the various plug-ins, in other languages as wellC/C++, Cobol, Python, Perl, PHP and more.

APACHE TOMCAT:

Apache Tomcat (or Jakarta Tomcat or simply Tomcat) is an open source servlet container developed by the Apache Software Foundation (ASF). Tomcat implements the Java Servlet and the JavaServer Pages (JSP) specifications from Sun Microsystems, and provides a "pure Java" HTTP web server environment for Java code to run. Tomcat should not be confused with the Apache web server, which is a C implementation of an HTTP web server; these two web servers are not bundled together. Apache Tomcat includes tools for configuration and management, but can also be configured by editing XML configuration files.

ORACLE 9I:

The Oracle Database (commonly referred to as Oracle RDBMS or simply Oracle) consists of a relational database management system (RDBMS) produced and marketed by Oracle Corporation. Oracle had become a major presence in database computing.

RATIONAL ROSE:

Rational rose is used for drawing the UML diagrams easily

and in required format.VSS:

Microsoft Visual SourceSafe is a file-level version control system that permits many types of organizations to work on several project versions at the same time. This capability is particularly beneficial in a software development environment, where it is used in maintaining parallel code versions. However, the product can also be used to maintain files for any other type of team.

6. System Design6.1 Data Flow Diagrams

6.1.1E- R Diagram

An entity-relationship model (ERM) in software engineering is an abstract and conceptual representation of data . Entity-relationship modeling is a relational schema database modeling method, used to produce a type of conceptual model or semantic data model of a system, often a relational database, and its requirements in a fashion. There are a number of entities, attributes, relationships etc, as mentioned below.6.2 Behavioral Diagrams

6.2.1 Use Case Diagrams

Use case diagram :

Use case diagrams are central to modeling the behaviour of a system, a subsystem of a class. Generally they show a set of usecases, actors and their relationships. These diagrams gives the static view of a system.Description:

Name Of The Use Case: Login Description:

DEO and administrator of the PLS system must be login to the

access the required services.

Pre Condition: Each user must have a valid user id and password.Post condition: Home Page will be displayed.

Flow of events:

Invoke the Welcome page of PLS System.

Enter the valid User ID and Password.

Click on Sign In button to access Home page.

Alternative Flow of Events:

If the DEO is new admin should Click on Registration Link.

If the DEO account is locked then he must contact administrator.

Name Of The Use Case: Data EntryDescription:

DEO of the PLS system after login he must enter the job to be

done for the customer and customer details.

Pre Condition: The DEO must be logged into the system.Post condition: Customer details are entered into the database.

Flow of events:

Login to the DEO Home Page.

Click on New Customer.

Click on Submit button for entering details into the database.

Name Of The Use Case: BillingDescription:

DEO of the PLS system after login he can enter the details about

the customer billing.

Pre Condition: DEO must be logged into the system.Post condition: Customer details will be displayed.

Flow of events:

Click on customer details.

Click on Submit button.

Name Of The Use Case: MaterialsDescription:

DEO of the PLS system after login he can update and enter the material details.

Pre Condition: DEO must be logged into the system.Post condition: Material details page will be displayed.

Flow of events:

Click on material updaion details.

Name Of The Use Case: ReportsDescription:

DEO of the PLS system after login he can generate the reports.

Pre Condition: DEO must be logged into the system. Post condition: Reports page will be displayed.

Flow of events:

Click on Reports.

Name Of The Use Case: Checking customer detailsDescription:

Administrator of the PLS system after login he can check the customer details which are already entered.

Pre Condition: Administrator must be logged into the system.Post condition: Customer details page will be displayed.

Flow of events:

Login to the admin Home Page.

Click on customer details.

Name Of The Use Case: Checking Billing DetailsDescription:

Administrator of the PLS system after login he can check the customer billing details which are already entered.

Pre Condition: Administrator must be logged into the system.Post condition: Customer billing details page will be displayed.

Flow of events:

Login to the admin Home Page.

Click on customer billing button.

6.2.2 Class Diagrams

Description: The class diagram shows the static design view of a system. It shows the relation between classes, collaborations and interfaces.SIMS system has the following classes.

Login:

This class is used login purpose. It contains userid,password are the attributes. It has the operations like

verifyuserid()

verifypassword()

connectwithDB()

disconnectwithDB()

Customer: This class shows the customer details. It contains customerid,name,address,phoneno,takingtime,deliverytime,noofcopies,validity are the attributes. It has the operations like

getcustomerdetails()

storecustomerdetails()

modifycustomerdetails()

deletecustomerdetails()

DEO details:

This class shows the details of the data entry operator. It contains

name,password,userid,address,gender,dob,phoneno are the attributes.It has the operations

like

getDEOdetails()

storeDEOdetails()

deleteDEOdetails()

Admin:

This class shows the administrator privileges. It contains userid,password are the attributes.It has the operations like

unlockDEO ()

deleteDEO()

employee()

customerbill()

Status:

This class shows the details of the work status. It contains userid,status are the attributes. It has the operations like

updatestatus()

connectwithDB()

materials:

This class shows the details of the materials. It contains availability,number are the attributes. It has the operations like

photosheet()

chemical()

Employee:

This class shows the details of the employee. It contains name,salary are the attributes. It has the operations like

salary()

unlockDEO:

This class shows the details of unlocking the DEO. It contains userid is the attribute. It has the operations like

unlock()

deleteDEO:

This class shows the details of deleting the DEO details. It contains userid,status are the attributes. It has the operations like

updatestatus()

connectwithDB()

6.2.3 Sequence Diagrams A sequence diagram is a interaction diagram that emphasizes the time- ordering of messages. The sequence diagram shows a set of objects ,messages, sent and received by those objects.

Registration:

Fig 6.2.3.1 Sequence diagram for RegistrationDescription:

1. Administrator enters his user id, password.

2. After successfully login. The administrator home page will be displayed.

3. Administrator enters the details of the DEO.DeleteDEO:

Fig 6.2.3.2 Sequence diagram for DeleteDEODescription:

3. Enter DEO id.

4. Delete the DEO details.

Login:

Fig 6.2.3.3 Sequence diagram for LoginDescription:

1. Enter user id , password, select type of user in the login screen.

2. These values are check with the database values.

3. If the database values are matched. By using type of user.

4. Corresponding home page will be displayed.

Material Update:

Fig 6.2.3.4 Sequence diagram for Material updateDescription:

1. DEO enters his user id, password.

2. After successfully login. The DEO home page will be displayed.

3. Enter the material details and update the material details.

New Customer:

Fig 6.2.3.5 Sequence diagram for Newcustomer

Description:

3. Enter the customer details.

Status Update:

Fig 6.2.3.6 Sequence diagram for Status update

Description:

3. update the work status of the customer.

Unlock Account:

Fig 6.2.3.7 Sequence diagram for Unlock account

Description:

3. Unlocks the DEO account.

6.2.4 Collaboration Diagrams Collaboration names a society of classes, interfaces, and others that work together to provide some cooperative behavior thats bigger than the some of all its part. Login:

Fig 6.2.4.1 Collaboration diagram for login

Material Update:

Fig 6.2.4.2 Collaboration diagram for MaterialupdateDeleteDEO:

Fig 6.2.4.3 Collaboration diagram for deleteDEO

NewCustomer:

Fig 6.2.4.4 Collaboration diagram for Newcustomer

Registration:

Fig 6.2.4.5 Collaboration diagram for RegistrationStatusUpdate:

Fig 6.2.4.6 Collaboration diagram for Statusupdate

Unlock Account:

Fig 6.2.4.7 Collaboration diagram for Unlock account

Fig 6.2.5.1 Activity diagram for Login

Fig 6.2.5.2 Activity diagram for Registration

Fig 6.2.5.3 Activity diagram for Status Update

Fig 6.2.5.4 Activity diagram for Material Update

Fig 6.2.5.5 Activity diagram for Unlock account

Fig 6.2.5.6 Activity diagram for Employee Salaries

Fig 6.2.5.7 Activity diagram for Customer billing 6.2.6 Component Diagram:

6.2.7 Deployement Diagram:

6.3 System Specific Modules

Login & Registration Customer details Reports

Bills Materials

Employees Login & Registration:

Admin should be login & he should register the DEO details. DEO should be login. Enter the details on these Login and Registration pages. Customer Details:

DEO should enter the customer details carefully. Reports:

After login in to the system Reports should be generated by the

DEO. The administrator views every day. Bills:

The bills of the customer should be entered and updated by the DEO.

Materials:

DEO should enter the details about the materials and updated them every day.

Employees: Admin should enter the details about the employees working in the studio.Admin also enters the salary details of the employees every month.6.4 System Evolution : The PLS system is implemented for a photo studio. It is developed on a pure java2EE architecture. It is using Oracle database. By using type 4th driver all database transactions are done. The 4th driver is database dependent. This driver is a pure java driver.

This stores the large amounts of data of the customers coming to the photo studio and the details about the employees and also the details about materials. It stores the data as category wise. Suppose if the category is apple, the data will be stored into the fruits inventory.

If the data is about employees then the data will be stored in to the Employess Inventory.

Similarly, if the data is about materials then the data will be stored into the materials inventory. Like wise all the data is stored into the database.6.5 Sample Code

LoginPage.jsp:

PHOTO LAB MANAGEMENT SYSTEMS

User Id:

Password:

ADHomme.jsp:

Home

Customer

Unlock

New DEO

Delete DEO

Material

Billing

Employee

Logout

View customer.jsp:

function get(id) //ajax code for displaying values

{

var req1=getRequestObject();

req1.onreadystatechange=function(){handleResponse1(req1);}

req1.open("GET","getdetails.jsp?id="+id,true); //redirecting to other jsp page

req1.send(null);

}

function handleResponse1(req1)

{

if(req1.readystate==4)

{

var s=req1.responseText;

var x=s.split("$");

document.getElementById("d1").value=x[0]; //retriving the fields for displaying

document.getElementById("d2").value=x[1];

if(x[3].indexOf("m")==4)

{

document.getElementById("d4").checked="true";

}

else

document.getElementById("d8").disabled=true;

document.getElementById("t1").style.visibility="visible"; //hidding the field after displaying the starting date

p2.innerText=x[5];

document.getElementById("t2").style.visibility="visible";//hidding the field after displaying the delivery date

p3.innerText=x[6];

document.getElementById("t5").style.visibility="visible";

p5.innerText=x[10];

document.getElementById("t6").style.visibility="visible";

p6.innerText=x[11];

if(x[14].indexOf("y")==4)

{

}

else

if(x[10].indexOf("y")==4)

{

document.getElementById("d30").style.visibility="visible";

document.f1.d31.src=x[15];

}

else

{

document.getElementById("d30").style.visibility="hidden";

document.f1.d31.src="";

}

function getRequestObject()

{

if(window.XMLHttpRequest)

{

return(new XMLHttpRequest());

}

else if(window.ActiveXObject)

{

return(new ActiveXObject("Microsoft.XMLHTTP"));

}

else

return(null);

}

Home

View

Customer Details

&nbs

p;

Userid:

Name:

Address:

Gender:

Male

Female

Mobile:

Starting Time:

DD

01

02

03

04

05

06

07

08

09

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

MM

JAN

FEB

MAR

APR

MAY

JUN

JUL

AUG

SEP

OCT

NOV

DEC

YYYY

2000

2001

2002

2003

2004

2005

2006

2007

2008

2009

2010

2011

2012

2013

2014

2015

Delivery Time:

DD

01

02

03

04

05

06

07

08

09

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

MM

JAN

FEB

MAR

APR

MAY

JUN

JUL

AUG

SEP

OCT

NOV

DEC

YYYY

2000

2001

2002

2003

2004

2005

2006

2007

2008

2009

2010

2011

2012

2013

2014

2015

Total Amount:

Advance:

Balance:

Paid:

Yes

No

Status:

select

YES

NO

No. of Copies:

Type of Photo:

select

Passport

Stamp

MaxiSize 4*6

Size 6*8

Size 8*12

Size 10*12

Size 12*15

Size 15*18

Validity of the card Upto in days:

7. SCREENS

Welcome page for Photo Lab Management Systemhttp://localhost:8089/FINAL/LoginPage.jsp

Home page for Data Entry Operator

Data Entry Operator entering Customer details

Viewing Customer details

Entering Material details

Updating Work Status of Lab

Administrator Home Page

Customer Bill Details

Entering Employee salaries

Viewing Employee Salaries

Deleting Employee from Photo Lab Management System

8. TestingTEST CASE IDDESCRIPTIONTEST STEPSEXPECTED RESULTREMARKSOK/ERROR

PLS_Login_tc_01

Verify that the user should be able to login to the systemInvoke browser with URL1. PLS login page should be displayed. a) user id b) password c)ok, cancel d) type of user.

Enter username, password and Type of user

2.User name, password should be displayed in the sims login page.

Then click ok.3.PLS Home page should be displayed

PLS_Reg_tc_02

Verify that the user should be able to registered to the systemInvoke browser with URL1.PLS registration page should be displayed with the first name, last name, user id, pwd, confirm password, date of birth, phone no, submit button.

Enter username, first name, password, confirm password, type of user.

2.Fields that are to be stored into the database, a message will be displayed like user successfully registered to the system.

8.1 Functional Test Cases

TEST CASE IDDESCRIPTIONTEST STEPSEXPECTED RESULTREMARKSOK/ERROR

PLS_customer_tc_03Enter the customer details and Verify the customer details entered by the DEO.Invoke browser with URLAfter the successfully login by the DEO, home page of DEO should be displayed.

Click New CustomerEnter the details about the customer like name,address, text fields and submit, cancel buttons should be displayed.

Click on Customer detailsDetails about the customer is displayed when the id of the customer is clicked.

PLS_Staus_tc_04To enter the status of the work given by the customer and the image of the customer. Invoke browser with URLThe page contains status field and image file upload button and submit button.

Click on Status update buttonEnter the status and upload the image of the customer.

PLS_Materials_tc_05Enter the details of the materials view and update them.Invoke browser with URLThe page contains material types and submit button and update button.

Click on material insertInsert all the material types data and click on submit button

Click on material updateUpdate the details of the materials and click update button.

Click on material detailsView the material details.

TEST CASE IDDESCRIPTIONTEST STEPSEXPECTED RESULTREMARKSDEFECT ID

PLS_Unlock_tc_06Mainly for unlocking the DEO account by the administratorInvoke browser with URLAfter successfully login by the Administrator.Home page of administrator should be displayed.

Click on Unlock account.Enter the userid and click on submit button.

PLS_ delete_tc_07Deletion of the and DEO detailsInvoke browser with URLAfter successfully login by the Administrator. His home page should be displayed.

Click on deleteDEOThis page contains the userid field and after entering userid click on delete button.

PLS_ employee_tc_08Enter the details the employeeInvoke browser with URLThe page contains all the fields about the employee details like name,salary,address etc fields.

Click on employee insertEnter all the details about the employee in the corresponding fields and click on submit button.

PLS_ employeesal_tc_08.1Enter the details about the salaries of the employee every monthInvoke browser with URLThe page contains all the fields about the employee id and salaries

Click on employee salariesEnter the details of the salaries of the customer and click on submit button.

8.3 System Test Cases

TEST CASE IDDESCRIPTIONTEST STEPSEXPECTED RESULTREMARKSOK/ERROR

PLS_customer_tc_09

Invoke browser with URLAfter successfully login by the DEO. His home page should be displayed with add customer hyper link.

Click new customer hyper link.Enter all the details about the customer and click on submit button.

Click submit button.The new item details are stored in to the database.

The details should be displayed.

PLS_employee_tc_10Invoke browser with URLAfter successfully login by the DEO. His home page should be displayed with add employees hyper link.

Click new employee hyper link.Enter all the details about the employee and click on submit button.

Click submit buttonThe new item details are stored in to the database.

The details should be displayed.

9. Conclusion Hence the Photo Lab Management System (PLS) for a photo studio is developed. This system is made finally to store the details of the customers,employees,work details and update the details based on the customer details, material details.

The system is developed which is useful for DEO to enter the details about the customer,materials,deletion of the customer details and admin mainly checks the details of customer,materials and to enter the details about the employees and updates the details of employees in frequent intervals. It also helps Admin for the deletion of the DEO and employee details and helps in releasing the lock of the DEO account when it is locked.

10. Appendix A - Hardware and Software Configurations

Hardware Requirements:1. PC with 2 GB hard-disk

2. 256 MB RAM

Software Requirements:1. Windows 95/98/XP with MS-office

2. Apache Tomcat server3. Java---front end

4. Oracle 10g--back end 11. Appendix B Data Base Tables

PLS DEODetails block employee3 empsal image2 photosheet chemical 11.1 PLS

Schema:Name Null? Type

USERID PRIMARY KEYVARCHAR2(20)

NAME VARCHAR2(20)

ADDRESS VARCHAR2(20)

GENDER VARCHAR2(20)

MOBILE VARCHAR2(20)

STARTINGDATE VARCHAR2(20)

DELIVERYDATE VARCHAR2(20)

NOC NUMBER

VUP NUMBER

TAM NUMBER

STATUS VARCHAR2(20)

TOPHOTO VARCHAR2(20)

ADVANCE VARCHAR2(20)

BALANCE VARCHAR2(20)

PAID VARCHAR2(20)

11.2 DEODetails

Schema:

Name Null? Type

USERID PRIMARYKEYVARCHAR2(20)

DEONAME VARCHAR2(20)

GENDER VARCHAR2(20)

MOBILE NUMBER

DOB VARCHAR2(20)

LOCATION VARCHAR2(20)

PASSWORD VARCHAR2(20)

11.3 block

PASSWORD VARCHAR2(12)

COUNT NUMBER(2)

STATUS VARCHAR2(5)

ENDMIN NUMBER(2)

TYPE VARCHAR2(10)

11.4 Employee3 Schema:Name Null? Type

USERID VARCHAR2(20)

NAME VARCHAR2(20)

GENDER VARCHAR2(20)

MOBILE VARCHAR2(20)

DOB VARCHAR2(20)

JD VARCHAR2(20)

TW VARCHAR2(20)

EXP VARCHAR2(20)

SALARY VARCHAR2(20)

11.5 Empsal

Schema:

Name Null? Type

EMPID VARCHAR2(20)

SALARY VARCHAR2(20)

PAIDDATE VARCHAR2(20)

STATUS VARCHAR2(20)

11.6 Image2

IMG BLOB

11.7 Photosheet

Schema:

Name Null? Type

AVAILABLEDATE PRIMARYKEYVARCHAR2(20)

TOP VARCHAR2(50)

VENDER VARCHAR2(20)

COST VARCHAR2(20)

AVAILABILITY VARCHAR2(20)

NUM VARCHAR2(20)

11.8 Chemical

AVAILABLEDATE PRIMARYKEYVARCHAR2(20)

TOP VARCHAR2(50)

VENDER VARCHAR2(20)

COST VARCHAR2(20)

AVAILABILITY VARCHAR2(20)

NUM VARCHAR2(20)

12. Appendix C - Limitations and Enhancements

Limitations:

If the type of user is Administrator, he works only with administrator role not the DEO role.

Enhancements:

Implementations of J2EE to provide high security are enhancements

required.

13. Appendix D - Bibliography Book References: [1] O REILLY, Java Server Pages , third edition , 2004. [2] GRADY BOOCH, IVAR JACOBSON, JAMES RUMBAUGH, Unified Modeling

Language , 2nd edition , 2004.

[3] H.M. DEITEL & P.J . DEITEL , JAVA How to Program ,6th edition , 2005.

[4] ROGER S. PRESSMAN ,Software Engineering , A Practitioners Approach , 6th

edition , 2005. [5] HERBERT SCHILDT , The Complete Reference JAVA , 5th edition, 2005. [6] RAGHU RAMA KRISHNAN , Database Management Systems , 3rd edition, 2003.

Web References:

[1] www.w3schools.com [2] www.java2s.com Client

View customer details

Admin

Unlock account

Delete DEO

View material details

DEO Registration

Customer billing

Employee

DEO login

New customer