Docu of Esms

8/14/2019 Docu of Esms

1/102

EMPLOYEE SHEDULER MANAGEMENT SYSTEM

INDEX:

1. EMPLOYEE SCHEDULING MANAGEMENT SYSTEM 04

1.1 ABSTRACT 04

2. INTRODUCTOIN 06

2.1 PURPOSE OF DOCUMENT 06

2.2 SCOPE 06

2.3 DEFINITIONS AND ACRONYMS 07

2.4 REFERENCES 07

REQUIREMENTS 08

3.1. GENERAL REQUIREMENTS 09

3.2 DATABASE REQUIREMENTS 09

3.3 FUNCTIONAL REQUIREMENTS 09

3.4 ADVANTAGES OF THE PROPOSED SYSTEM 10

PLATFORMS & TECHNOLOGIES 11

DESIGN SPECIFICATIPONS 14

5.1 DATAFLOW DIAGRAMS 15

5.2 LEVEL 1 15

5.3 LEVEL 2 15

5.4 LEVEL 3 16

5.5 LEVEL 4 17

5.6 DATA BASE DESIGN 18

5.7 ER-DIAGRAMS 21

SRI VENKATESWARA ENGINEERING COLLEGE, SURYAPET

1


2/102


3. PHYSICAL INTERFACE DESIGN (TABLES) 23

6.1 EMPLOYEE 24

6.2 REGS 24

6.3 SCEHEDULE1 25

6.4 SCEHEDULE2 25

AN OVERVIEW OF J2EE 26

7.1 J2EE APPLICATION COMPONENTS 27

7.2 JAVA TRANSACTION API (JTA) 30

7.3. J2EE ARCHITECTURE 33

7.4. OVERVIEW OF AWT 35

7.5. OVERVIEW SWINGS

40

8. CODING & IMPLEMENTATION 45

8.1 SCREEN SHOTS AND OUTPUT FORMS 76

9. TEST CASES 92

9.1 UNIT TESTING 95

9.2 INTEGRATION TESTING 95

9.3 VALIDATION TESTING 969.4 SYSTEM TESTING 96

10. MAINTENANCE AND IMPLEMENTATION 97

10.1 CORRECTIVE MAINTENANCE 98

10.2 ADAPTIVE MAINTENANCE 98

10.3 PREVENTIVE MAINTENANCE 98

11. CONCLUSION.... 99


2


3/102



3


4/102


EMPLOYEE SCHEDULING MANAGEMENT SYSTEM

ABSTRACT

The system, which was developed now, makes this process of

scheduling much easier and computerized. By this system the manager or

top level designated employee can fix the schedule of any employee

working under him, he even can check whether the employee is free in

the particular time or in other times. Thus the top level management can

easily fix the process of scheduling, and even can change the

appointment which is reflected immediately to the related employee

avoiding direct contact of the employee resulting in saving lot of time

and work overhead.

The system even has the option for only viewing the employees

activities or appointments. This feature avoids direct contact to the

respective employees database and activities. There is an option where

only the supervisor (the top-level manager) can have direct access to the

employees activities, he can change the appointments of the employees

working under him. No other employee of the same designation or same

level of hierarchy can do this.

This package is divided into three sub-modules.

Supervisor Employee

Read Only


4


5/102



5


6/102


INTRODUCTION

PURPOSE OF DOCUMENT

This document covers the ESMS interface design and all the

requirements of the Employee Scheduler Management System.

The purpose of this document is to define specification of

development for interface between Top level Management and

Employees of the Organization.

This document lists assumptions/dependencies for ESMS interface

design, an overview of ESMS and detailed design of ESMS Interface

along with input/output specifications etc.

The intended audiences for this document are:

PARTHI development team

AES Team

Scope

The scope of the document covers the ESMS interface design for

the following scenarios.

The scope of the document covers the process of scheduling the

manager or top level designated employee can fix the schedule of any

employee working under him, he even can check whether the employee

is free in the particular timeThis package is divided into three sub-modules.

Supervisor

Employee

Read Only


6


7/102


DEFINITIONS AND ACRONYMS

This sub-section defines all terms, acronyms and abbreviations

used within this document.

REFERENCES

Following are the list of documents referred to in the

Document, or those on which the Document is based

S.N

o

Doc. Id Document description Revisi

on

Remark

s

1.SDLC SDLC.pdf 2.0

2.SDLC SDLC_system_admin_guide.pdf 6.0

3.SDLC SDLC_variables_expressions_funct_vol1.pdf

6.0

4.SDLC SDLC_variables_expressions_funct_vol2.pdf

6.0


Acronym Explanation

ESMS Employee Scheduler management System

Documents In ESMS, Documents are containers of informationexchanged between applications.

Broker AES and PRATHI uses Broker as an information exchangemedial. It is a platform to exchange documents betweendifferent queues components as well as a repository of

documents.

7


8/102



8


9/102


3. REURIMENTS

3.1 GENERAL REQUIREMENTS

Life cycle of the case or Employee Scheduling system shall

include phases likeSupervisor,Employee, Read only and

Progress reports and all affected.

All the applications implemented shall have provision for

optimizing the number of Static connection to the database

using connection pooling.

It shall be possible to view and Schedule the EmployeeAppointments with the Higher Authority.

System shall automatically track, log and escalate Employee

Scheduling and Appointments

3.2 DATABASE REQURIMENTS

Microsoft Access Database shall be used with allRequirements

Necessary components of Assess shall be provided which

shall include

For Multi Standby (backup) system

3.3FUNCTIONAL REQUIRMENTS

Create New Employee of the organization and Scheduling

Update Employee Scheduling Timings


9


10/102


Change of Employee Scheduling for Corporate and

Individual Employees.

Maintenance of Contact Information in Between Employees

and Top-level Management.

Password reset for Contact

Change of Promotion

Maintains Scheduling timing history

Changes the Scheduling Process and Timings

3.4 ADVANTAGES OF THE PROPOSED SYSTEM

The system, which was developed now, makes this

process of scheduling much easier and computerized.

By this system the manager or top level

designated employee can fix the schedule of any employee working

under him, he even can check whether the employee is free in the

particular time or in other times.

The system even has the option for only viewing

the employees activities or appointments. This feature avoids direct

contact to the respective employees database and activities.

There is an option where only the supervisor (the

top-level manager) can have direct access to the employees activities,

he can change the appointments of the employees working under him.

No other employee of the same designation or same level of hierarchy

can do this


10


11/102


4. PLATFORMS & TECHNOLOGIES


11


12/102


The following hardware and software requirement provide by the

customer based on his BOM (Bill of Materials).

System shall able to support the platform independent features

System shall be support the existing software setup/environment.

Presently the hardware setup as follows:

Server Details: Sun SPARC Enterprise T5220 Server

World's first 64-thread, general purpose server powered

by the ground-breaking Ultras ARC T2 System on Chip

processor.

Record-breaking performance, with the highest levels of

space and energy efficiency

Designed for secure web scale and virtualized computing

Available from $14,995

1 CPU at 1.40 GHz

Ultras ARC T2 architecture

Available with up to 8 cores

Supports up to 64 threads

Supports up to 64 GB of memory

2 RU server

Supports Solaris 10 and Linux operating systems

Supports up to 8x 146 GB SAS drives

Includes 2x 8 lane PCI-E, 2x 4 lane PCI-E, 2x 4 lane

PCI-E or XAUI


12
http://www.sun.com/servers/coolthreads/t5220/http://www.sun.com/servers/coolthreads/t5220/


13/102


Client Details: Tomcat Server

Existing Installed Softwares:

Java 1.5, Tomcat, MS-Access, Swings

Specilal tools for development & testing:

OPERATING SYSTEM : Windows 2000 or higher

HARDWARE PLATFORM : Pentium IV Processor or higher

RAM : 512 MB Minimum Recommended

HDD : 1 GB Min HDD Space required.

SOFTWARE SPECIFICATION : Tomcat, J2SDK1.5, Awt, Swings,

Ms-Access,


13


14/102


5. DESIGN SPECIFICATION

DATA FLOW DIAGRAMS


14


15/102


Context flow diagram

5.2 Level: 1

5.3 Level: 2


MAIN

supervisor

Employee

ReadonlyPerpose

SUPERVISOR Conformation

LoginRegistration

Regs Table

ShceduleView

Empd Table

Name,password

Schedule2Table

15


16/102


5.4 Level: 3

5.5 Level: 4


View Schedule

Todays Activites Monthly Activities

Schedule2 Table

Name,password,EtimeStime,Preference,Dept,Description.

Empd Table

Read Only

Purpose

Login

Schedule

Close

View

Schedule

Name,password

Name,Dept,Stime,Etime,preferece

16


17/102



Employee

New Employee

Registered

Employee

Regs Table

Login

Schedule

View Schedule

Schedule1 Table

Name,deptpassword

17

Stime,Etime,preference


18/102


5.6 DATABASE DESIGN

Data objects


18


19/102


A data object is a thing about which you want to store information.

It has independent existence and can be uniquely identified.

The following data objects are derived for the system.

1. Employee

2. Register

3. Schedule

4. View

5. Supervisor

6. Reschedule

7. Add

8. Update

9. Generate Monthly Activities

Relationships

A relationship is a named association between agent and customer entity

or more than entities we say that relationship exists between clerk and

customer entity type. Similarly a relation between a clerk entity type and

a manager entity type.

The following relationships are identified for the system


19


20/102


For instance let us take the objects EMPLOYEE, REGISTER,

SCHEDULE, ADD, VIEW, the following relationships are identified.

Employee Register in Organization

Organization contains Employee Details

Employee Schedule Appointments.

Schedule requires Registration.

Employee add Scheduling Information.

The relationships between the remaining entities are as follows :

Supervisor views Scheduling informaion.

Supervisor View/Add Scheduling Infoemation.

Employee has Scheduling.

Scheduling containsActivies..


20


21/102


5.7 ER-Diagram

E-R Diagram as a method to represent a Data model and was

developed by Chen (1976). The main focus of a Data Model is to identify


21


22/102


the required data and show it diagrammatically, which is called Entity

Relationship Diagram. Its popularly is attributed to its simplicity. It has a

top-down design approach to decide the minimum data that we would

like to store for a given information system


22


23/102


6. PHYSICAL INTERFACE DESIGN (TABLES)

EMPLOYEE


23


24/102


Field Name Type & Size Validation

Id no Numeric (5) Unique &Not null

Name Char (50) Not null

Desg Char (50) Not null

REGS

SCHEDULE 1


Id no Integer Unique & Not nullName Char (40) Not null

Pwd Varchar (5)

SCHEDULE 2



Id no Char (5) Unique &Not null

Name Char (30) Not null

Pwd Char (30) Not null

Repwd Char (10) Not null

F-Name Numeric (5) Not null

L-Name Numeric (5) Not null

Dname Varchar (50) Not null

Dno Numeric (5) Not null

Sex Varchar (5) Not null

DD Integer Not null

MM Integer Not null

YY Integer Not null

Add Varchar(20) Not null

24


25/102




Id no Char (5) Unique &Not null

DD Integer Not null

MM Integer Not null

YY Integer Not null

Stime Date Not null

Etime Date Not null

Dname Varchar (50) Not null

Preference Varchar Not null

Descno Integer Not null

Desc Varchar Not null

Fback Varchar Not null

Details Long Not null

25


26/102



26


27/102


7. AN OVERVIEW OF J2EE

The following topics describe the J2EE Platform requirements

for each kind of J2EE platform element.

7.1 J2EE APPLICATION COMPONENTS

The J2EE runtime environment defines four application

component types that a J2EE product must support:

Application clients are Java programming language programs

that are typically GUI programs that execute on a desktop computer.

Application clients offer a user experience similar to that of native

applications, and have access to all of the facilities of the J2EE middle

tier.

Applets are GUI components that typically execute in a web

browser, but can execute in a variety of other applications or devicesthat support the applet-programming model. Applets can be used to

provide a powerful user interface for J2EE applications. Servlets, JSP

pages, filters, and web event listeners typically execute in a web

container and may respond to HTTP requests from web clients.

Servlets, JSP pages, and filters may be used to generate HTML pages

that are an applications user interface. They may also be used to

generate XML or other format data that is consumed by other

application components. A special kind of servlet provides support for

web services using the SOAP/HTTP protocol. Servlets, pages created

with the JavaServer Pages technology, web filters, and web event


27


28/102


listeners are referred to collectively in this specification as web

components. Web applications are composed of web components

and other data such as HTML pages. Web components execute in a

web container. A web server includes a web container and other

protocol support, security support, and so on, as required by J2EE

specifications. Enterprise JavaBeans (EJB) components execute in a

managed environment that supports transactions. Enterprise beans

typically contain the business logic for a J2EE application. Enterprise

beans may directly provide web services using the SOAP/HTTP

protocol.

J2EE Server Support for Application Components

The J2EE servers provide deployment, management, and

execution support for conforming application components.

Application components can be divided into three categories

according to their dependence on a J2EE server:

Components that are deployed, managed, and executed on a

J2EE server. These components include web components and

Enterprise JavaBeans components. See the separate specifications for

these components.

Components that are deployed and managed on a J2EE server,

but are loaded to and executed on a client machine. These components

include web resources such as HTML pages and applets embedded in

HTML pages.


28


29/102


Components deployment and management is not completely

defined by this specification. Application Clients fall into this

category. Future versions of this specification may more fully define

deployment and management of Application Clients.

J2EE Containers

Containers provide the runtime support for J2EE application

components. Containers provide a federated view of the underlying

J2EE APIs to the application components. J2EE application

components never interact directly with other J2EE application

components.

J2EE Servers

Underlying a J2EE container is the server of which it is a part.

A J2EE Product Provider typically implements the J2EE server-side

functionality using an existing transaction processing infrastructure in

combination with Java 2 Platform, Standard Edition (J2SE)

technology. The J2EE client functionality is typically built on J2SE

technology.

Resource Adapters

A resource adapter is a system-level software component that

implements network connectivity to an external resource manager. A

resource adapter can extend the functionality of the J2EE platformeither by implementing one of the J2EE standard service APIs (such

as a JDBC driver), or by defining and implementing a resource

adapter for a connector to an external application system.


29


30/102


7.2 JAVA TRANSACTION API (JTA)


30


31/102


The Java Transaction API consists of two parts:

An application-level demarcation interface is used by the

container and application components to demarcate transaction

boundaries. An interface between the transaction manager and a

resource manager used at the J2EE SPI level (in a future release).

RMI-IIOP

The RMI-IIOP subsystem is composed of APIs that allow for

the use of RMI-style programming that is independent of the

underlying protocol, as well as an implementation of those APIs that

supports both the J2SE native RMI protocol (JRMP) and the CORBA

IIOP protocol. J2EE applications can use RMI-IIOP, with IIOP

protocol support, to access CORBA services that are compatible with

the RMI programming restrictions (see the RMI-IIOP spec for

details).

JDBC API

The JDBC API is the API for connectivity with relational

database systems. The JDBC API has two parts: an application-level

interface used by the application components to access a database, and

a service provider interface to attach a JDBC driver to the J2EE

platform. Support for the service provider interface is not required in

J2EE products.

JAVA CONNECTOR ARCHITECTURE


31


32/102


The Connector architecture is a J2EE SPI that allows resource

adapters that support access to Enterprise Information Systems to be

plugged in to any J2EE product. The Connector architecture defines a

standard set of system-level contracts between a J2EE server and a

resource adapter.

SECURITY SERVICE

The Java Authentication and Authorization Service (JAAS)

enables services to authenticate and enforce access controls upon

users. It implements a Java technology version of the standardPluggable Authentication Module (PAM) framework, and extends the

access control architecture of the Java 2 Platform in a compatible

fashion to support user-based authorization. The Java Authorization

Service Provider Contract for Containers (JACC) defines a contract

between a J2EE application server and an authorization service

provider, allowing custom authorization service providers to be

plugged into any J2EE product.

DEPLOYMENT

The Java 2 Platform, Enterprise Edition Deployment

Specification defines a contract between deployment tools and J2EE

products. The J2EE products provide plug-in components that run in

the deployment tool and allow the deployment tool to deploy

applications into the J2EE product. The deployment tool provides

services used by these plug-in components.


32


33/102


7.3 J2EE ARCHITECTURE


33


34/102


Web Applications and Exploded Directory Format (EDF)


34


35/102


7.4 OVERVIEW OF AWT


35


36/102


AWT means Abstract Window Toolkit, It contains numerous

classes & methods that allow you to create & manage windows.

Although the main purpose of AWT is to create stand alone windows,

It can also be used to support applet windows.

AWT examines the standard controls & Layout managers

defined by Java. It also discusses menus & menu bar.

AWT controls are components that allow a user to interact with

your application in various ways for example, a commonly used

control is a push button. A Layout manager automatically positions

components within a container. Thus, the appearance of the window is

determined by a combination of controls that it contains and the

layout manager used to position them.

In addition to the controls, a frame window can also include a

standard style menu bar. Each entry in a menu bar activates a drop

down menu of options from which the user can choose. A menu bar is

always positioned at the top of a window. Although different in

appearance, menu bars are handled in much the same way, as are the

other controls.

While it is possible to manually position components within a

window, doing so is quite tedious. The default layout manager

automates this task. Which displays the components in a container

using left-to-right, top-to-bottom organization.

CONTROL FUNDAMENTALS


36


37/102


Labels

Push Buttons

Check Boxes

Choice Lists

Scroll bars

Text Editing

These controls are subclasses of Component.

Adding & Removing Controls

To include a control in a window, you must add it to the window.

To do this, you must first create an instance of the desired control and

then add it to a window by calling add( ), which is defined by

Container. The add( ) method has several forms.

Component add (Component comp object)

Here, comp object is an instance of the control that you want to add. A

reference to comp object is returned. Once a control has been added, it

will automatically be visible whenever its parent window is displayed.

Sometimes you will want to remove a control from a window when

the control is no longer needed. To do this, call remove( ). this method

is also defined by Container. It has this general form.void remove(Component object)

Here, object is a reference to the control you want to remove. You can

remove all controls by calling removeAll ().

Responding to Controls


37


38/102


Except for Labels, which are passive controls, all controls

generate events when they are accessed by the user. For example,

when user clicks a push button, an event is sent that identifies the push

button. In general, your program simply implements the appropriate

interface and then registers an event listener for each control that you

need to monitor. Once a listener has been installed, events are

automatically sent to it.

AWT CLASSES

The awt classes are contained in the java.awt package. It is

one of Javas largest packages. Fortunately, because it is logically

organized in a top-down, hierarchical fashion, it is easier to

understand and than you might at first believe. Table lists some of the

AWT classes

Class Description

AWT Event Encapsulates AWT events.

Border Layout The border layout manager

Button Creates a push button control.

Check Box Creates a Check Box control.

Color Manages Color in a portal,

Platform-independent Fashion

Component An abstract super class of

Various AWT components.

Container A subclass of component

that can hold other components.

Dialog Create a dialog window.


38


39/102


Event Encapsulates events

Flow Layout The flow layout manager.

Flow Layout positions components left

to right, top to bottom.

Font Encapsulates type font.

Frame Creates a standard window

that has a title bar, resize

corners ,& a menu bar.

Grid Layout The grid layout manager.

Grid layout displays

components in a two-

dimensional grid.

Image Encapsulates graphical images.

Label Creates a label that displays a string

List Creates a list from which a

user can choose . Similar to

standard windows list box.

Panel The simplest concrete sub-

class of Container.

Popup Menu Encapsulates a pop-up menu.

Scroll Bar Creates a scrollbar control.

Scroll Pane A container that provides a

horizontal and or vertical

scroll bars for another

component.


39


40/102


7.5 OVERVIEW OF SWINGS


40


41/102


The Swing components, which are part of the Java Foundation

Classes (JFC), can be used with either JDK 1.1 or the Java 2 platform.

About the JFC and Swing

What Are the JFC and Swing?

JFC is short for Java TM Foundation Classes, which encompass

a group of features to help people build graphical user interfaces

(GUIs). The JFC was first announced at the 1997 Java One developer

conference and is defined as containing the following features:

The Swing Components

Include everything from buttons to split panes to tables.

Pluggable Look & Feel Support

Gives any program that uses Swing components a choice of

looks and feels. For example, the same program can use either the

Java TM Look & Feel or the Windows Look & Feel. We expect many

more look-and-feel packages including some that use sound instead

of a visual "look" -- to become available from various sources.

Accessibility API

Enables assertive technologies such as screen readers and

Braille and in applets. Displays to get information from the user

interface. Enables developers to easily incorporate high-quality 2D

graphics, text and images in applications and in applets.

Drag and Drops Support (JDK 1.2 only):


41


42/102


Provides the ability to drag and drop between a Java application

and native applications. The first three JFC features were

implemented without any native code, relying only on the API defined

in JDK 1.1. This extension was released as JFC 1.1, which is

sometimes called "the Swing release. The API in JFC 1.1 is

often called "the Swing API."Note: "Swing" was the codename of the

project that developed the new components. Although it's an

unofficial name, it's frequently used to refer to the new components

and related API. Its frequently used to refer to the new components

and related API, which begin with javax.swing.

How Are Swing Components Different from AWT Components?

The AWT components are those provided by the JDK 1.0 and

1.1 platforms. Although JDK 1.2 still supports the AWT components.

We strongly encourage you to use Swing components instead. You

can identify Swing Components because their names start with J. the

AWT button class, for example, is named Button, while the Swing

button class is named JButton. Additionally, the AWT components

Are in the java.awt package, while the Swing components are in the

javax.swing package.

The biggest difference between the AWT components and

Swing components is that the Swing components are implemented

with absolutely no native code. Since Swing components aren't

restricted to the least common denominator -- the features that are

present on every platform -- they can have more functionality that

AWT Components. Because the Swing components have no more

functionality that AWT components.Because the Swing components


42


43/102


have no native code. They can be shipped as an add on to JDK 1.1 in

addition to being part of JDK 1.2.

Even the simplest Swing components have capabilities far beyond what

the AWT components offer:

Swing buttons and labels can display images instead of, or in addition

to, text. You can easily add or change the borders drawn around most

Swing components. For example, it's easy to put a box around the

outside of a container or label.

You can easily change the behavior or appearance of a Swing

component by either invoking methods on it or creating a subclass of

it.

Swing components don't have to be rectangular. Buttons, for

example, can be round. Asssistive technologies such as screen readers

can easily get information from Swing components. For example, a

tool can easily get the text that's displayed on a button or label.

Swing lets you specify which look and feel your program's GUI uses.

By contrast, AWT components always have the look and feel of the

native platform.

Another interesting feature is that Swing components with state

use models to keep the state. A JSlider, for instance, uses a

BoundedRangeModel object to hold its current value and range of

legal values. Models are set up automatically, so you dont have to

deal with them unless you want to take advantage of the power they

can give you.


43


44/102


If you're used to using AWT components, you need to be aware

of a few gotchas. When using Swing components:

Programs should not, as a rule, use "heavyweight" components

alongside Swing Components. Heavyweight components include all

the ready-to-use AWT Components (such as Menu and ScrollPane)

and all components that inherit from The AWT Canvas and Panel

classes. This restriction exists because then Swing Components, the

heavy weight components is always painted on top.

Swing components aren't thread safe. If you modify a visible Swing

component Invoking its setText method, for example -- from

anywhere but an event handler, Then you need to take special steps to

make the modification execute on the Event-dispatching thread. This

isn't an issue for many Swing programs, since Component modifying

code is typically in event handlers.

The containment hierarchy for window or applet that contains

Swing Components must have a Swing top-level container at the root

of the hierarchy.

For example, a main window should be implemented as a

JFrame instance Rather than as Frame instance.

You don't add components directly to a top-level container such as a

JFrame instead. You components to a container (called the content

pane) that is itself contained by the JFrame.


44


45/102



45


46/102



46


47/102


import java.awt.*;

import javax.swing.*;

import java.awt.event.*;

import javax.swing.border.*;

import javax.swing.event.*;

public class Option extends JFrame implements ActionListener

{

JButton ok;

JLabel l,l1,l2,l3,sel;

JTextField tf;

JPanel panel;

String border_type="Titled";

AbstractBorder border=new TitledBorder(" ");

public static int i;

public Option()


47


48/102


{

setTitle("Main Entry");

setSize(500,400);

move(120,100);

sel=new JLabel("Select");

sel.setForeground(Color.black);

l1=new JLabel("1.Supervisor");

l2=new JLabel("2.Employee");

l3=new JLabel("3.Read-Only Purpose");

ok=new JButton("OK");

l=new JLabel("ENTER YOUR CHOICE");

tf=new JTextField(10);

// logos inserting

ImageIcon image = new ImageIcon("f://logo.gif");


48


49/102


JLabel background = new JLabel(image);

background.setBounds(750, 550, image.getIconWidth(),image.getIconHeight());

getLayeredPane().add(background, new Integer(Integer.MIN_VALUE));

//

JPanel panel = new JPanel();

panel.setOpaque(false);

//panel.add( new JButton( "Hello" ) );

setContentPane( panel );

ImageIcon image1 = new ImageIcon("f://prathi2.jpg");

JLabel background1 = new JLabel(image1);

background1.setBounds(100,550, image1.getIconWidth(),image1.getIconHeight());

getLayeredPane().add(background1, newInteger(Integer.MIN_VALUE));

//

JPanel panel1 = new JPanel();

panel1.setOpaque(false);

//panel.add( new JButton( "Hello" ) );

setContentPane( panel1 );

panel =new JPanel();

panel.setBounds(200,300,550,230);

panel.setBackground(Color.gray);

Container c=getContentPane();


49


50/102


c.setBackground(Color.gray);

c.setLayout(null);

sel.setBounds(210,290,50,30);

l.setBounds(330,440,200,20);

l.setFont(new Font("convecta",Font.BOLD,16));

l.setForeground(Color.black);

l1.setBounds(230,330,200,20);

l1.setFont(new Font("convecta",Font.BOLD,16));

l1.setForeground(Color.black);

l2.setBounds(230,360,200,20);



l3.setBounds(230,390,200,20);



tf.setBounds(540,440,30,20);

tf.setFont(new Font("convecta",Font.BOLD,16));

ok.setBounds(580,440,60,20);

ok.setFont(new Font("convecta",Font.BOLD,16));

c.add(sel);

c.add(l);c.add(ok);c.add(tf);

c.add(l1);c.add(l2);c.add(l3);

tf.requestFocus();


50


51/102


tf.addNotify();

ok.addActionListener(this);

c.setBackground(Color.lightGray);

if(border_type.equals("Titled"))

{

c.add(panel);

panel.setBorder(border);

repaint();

}

setVisible(true);

}//end of Option constructor.

public void actionPerformed(ActionEvent e)

{

String s=tf.getText();

i=Integer.parseInt(s);

if(i==1&&(e.getSource()==ok))

{

ouser a3=new ouser();

}

else


{

CPro a2=new CPro();


51


52/102


}

else


{

ouser a1=new ouser();

}

}//end of actionPerformed.

public static void main(String a[])

{

new Option();

}//end of main method.

}//end of Option class.


52


53/102



import javax.swing.event.*;

import java.awt.*;


53


54/102



import java.sql.*;

import javax.swing.border.*;

import java.util.*;

public class details extends JFrame implements ActionListener

{

JLabel nl,np,stl,stp,etl,etp,desl,desp,detl,prel,prep;

JTextArea ta;

JButton close,feed,submit,postp,dchange,atten;

String msg,oname,pref;

int idn,d,m,y,descnum;

String s3=null;

JLabel p1,p2,pp1,pp2,p3,p4,dl,ml,yl;

JComboBox pd,pm,py,psh1,psm1,psh2,psm2;

JPanel panell;

String border_type="Line";

AbstractBorder border=new LineBorder(Color.black,1);

String[] hours={ "01","02","03","04","05","06""07","08","09","10","11","12", "13","14","15","16","17","18","19","20","21","22","23"};

String[] minits={"0", "05","10","15""25","30","35, "45","50","55"};

Stringyear[]={"2000","2001","2002","2003","2004","2005","2006","2007","2008","2009","2010","2011","2012","2013","2014","2015"};


54


55/102


Stringmonth[]={"01","02","03","04","05","06","07","08","09","10","11","12"};

String

date[]={"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"};

int ch=0;

Time sti,eti;

public details()

{

setTitle("Details");

setSize(415,420);


c.setLayout(null);

move(200,85);

nl =new JLabel("NAME:");

nl.setForeground(Color.black);

np =new JLabel();

np.setForeground(Color.black);

stl =new JLabel("StartTime:");

stl.setForeground(Color.black);

stp =new JLabel();

stp.setForeground(Color.black);

etl =new JLabel("EndTime:");


55


56/102


etl.setForeground(Color.black);

etp =new JLabel();

etp.setForeground(Color.black);

desl =new JLabel("DESCRIPTION:");

desl.setForeground(Color.black);

desp =new JLabel();

desp.setForeground(Color.black);

detl =new JLabel("DETAILS:");

detl.setForeground(Color.black);

ta =new JTextArea(30,30);

ta.setEditable(false);

close =new JButton("Close");

feed =new JButton("FeedBack");

submit =new JButton("Submit");

postp =new JButton("PostPone");

dchange=new JButton("ChangeDetails");

atten=new JButton("Attended");

prel =new JLabel("PREFERENCE:");

prel.setForeground(Color.black);

prep =new JLabel();

prep.setForeground(Color.black);

p1=new JLabel("Hr");

p1.setForeground(Color.black);


56


57/102


p2=new JLabel("Mn");


pp1=new JLabel("Hr");

pp1.setForeground(Color.black);

pp2=new JLabel("Mn");

pp2.setForeground(Color.black);

dl=new JLabel("DD");

ml=new JLabel("MM");

yl=new JLabel("YY");

dl.setForeground(Color.black);

ml.setForeground(Color.black);

yl.setForeground(Color.black);

p3=new JLabel("Changed Date:");


pd=new JComboBox(date);

pm=new JComboBox(month);

py=new JComboBox(year);

psh1=new JComboBox(hours);

psm1=new JComboBox(minits);

psh2=new JComboBox(hours);

psm2=new JComboBox(minits);

p3.setBounds(30,50,100,20);

dl.setBounds(125,30,30,20);


57


58/102


pd.setBounds(120,50,50,20);

ml.setBounds(185,30,30,20);

pm.setBounds(172,50,50,20);

yl.setBounds(245,30,30,20);

py.setBounds(222,50,60,20);

p1.setBounds(125,70,30,20);

psh1.setBounds(120,90,50,20);

p2.setBounds(180,70,30,20);

psm1.setBounds(170,90,50,20);

pp1.setBounds(305,70,30,20);

psh2.setBounds(300,90,50,20);

pp2.setBounds(365,70,30,20);

psm2.setBounds(350,90,50,20);

nl.setBounds(30,10,80,20);

np.setBounds(120,10,100,20);

stl.setBounds(30,90,100,20);

stp.setBounds(90,90,100,20);

etl.setBounds(240,90,100,20);

etp.setBounds(295,90,100,20);

desl.setBounds(30,110,130,20);

desp.setBounds(180,110,130,20);

detl.setBounds(30,170,120,20);


58


59/102


prel.setBounds(30,140,120,20);

prep.setBounds(180,140,120,20);

ta.setBounds(110,170,260,60);

feed.setBounds(120,250,100,20);

submit.setBounds(245,322,80,20);

postp.setBounds(230,250,120,20);

dchange.setBounds(230,273,120,20);

atten.setBounds(230,297,120,20);

close.setBounds(200,345,70,20);

c.add(nl);c.add(np);c.add(stl);

c.add(stp);c.add(etl);c.add(etp);

c.add(desl);c.add(desp);c.add(prel);

c.add(prep);c.add(detl);

c.add(pp1);c.add(pp2);c.add(ta);c.add(dl);

c.add(ml);c.add(yl);c.add(close);

c.add(feed);c.add(submit);c.add(postp);

c.add(p1);c.add(p2);c.add(p3);

c.add(pd);c.add(pm);c.add(py);

c.add(psh1);c.add(psm1);c.add(psh2);

c.add(psm2);c.add(dchange);

c.add(atten);//c.add(ta);

postp.setVisible(false);

atten.setVisible(false);


59


60/102


dchange.setVisible(false);

p3.setVisible(false);

pd.setVisible(false);

pm.setVisible(false);

py.setVisible(false);

psh1.setVisible(false);

psm1.setVisible(false);

psh2.setVisible(false);

psm2.setVisible(false);

submit.setVisible(false);



pp1.setVisible(false);

pp2.setVisible(false);

dl.setVisible(false);

ml.setVisible(false);

yl.setVisible(false);

close.addActionListener(this);

feed.addActionListener(this);

submit.addActionListener(this);

dchange.addActionListener(this);

postp.addActionListener(this);

atten.addActionListener(this);


60


61/102


panell=new JPanel();

panell.setBounds(110,240,260,117);

panell.setBackground(Color.gray);

if(border_type.equals("Line"))

{

c.add(panell);

panell.setBorder(border);

repaint();

}

setVisible(true);

}


61


62/102


public void senddetails(String msg1,String oname1,int id,int date,intmonth,int year)

{

msg=msg1;

oname=oname1;

idn=id;

d=date;m=month;

y=year;

System.out.println("msg="+msg);

}

public void process()

{

String detail=null;

String s1=msg.substring(0,2);

int t1=Integer.parseInt(s1);



Time st1=new Time(t1,t11,00);






62


63/102


Time et1=new Time(t2,t21,00);

s3=msg.substring(19,msg.length());

ResultSet rs;

try

{

Classcfn=Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");

Connectioncon=DriverManager.getConnection("Jdbc:Odbc:pro");

Statement st=con.createStatement();

rs=st.executeQuery("select details,preference,descno fromschedule2 where idno="+idn+" and dd="+d+" and mm="+m+" andyy="+y+" and desc='"+s3+"'");

while(rs.next())

{

descnum=rs.getInt("descno");

pref=rs.getString("preference");

detail=rs.getString("details");

} con.close();

}

catch(Exception ec)

{ System.out.println(""+ec); }

np.setText(oname);

stp.setText(""+st1);

etp.setText(""+et1);


63


64/102


prep.setText(""+pref);

desp.setText(""+s3);

ta.setText(detail);

}

public void actionPerformed(ActionEvent ae)

{

if(ae.getSource()==close)

{

this.setVisible(false);

}

else

if(ae.getSource()==feed)

{

postp.setVisible(true);

dchange.setVisible(true);

submit.setVisible(true);

atten.setVisible(true);

}

else

if(ae.getSource()==postp)

{

p3.setVisible(true);


64


65/102


pd.setVisible(true);

pm.setVisible(true);

py.setVisible(true);

psh1.setVisible(true);

psm1.setVisible(true);

psh2.setVisible(true);

psm2.setVisible(true);



pp1.setVisible(true);

pp2.setVisible(true);

dl.setVisible(true);

ml.setVisible(true);

yl.setVisible(true);

stp.setVisible(false);

etp.setVisible(false);

ch=1;

}

else

if(ae.getSource()==atten)

{

ch=3;

}


65


66/102


else

if(ae.getSource()==dchange)

{

ta.setEditable(true);

ch=2;

}

else

if(ae.getSource()==submit)

{

int d1 =Integer.parseInt((String)pd.getSelectedItem());

int m1 =Integer.parseInt((String)pm.getSelectedItem());

int y1 =Integer.parseInt((String)py.getSelectedItem());

int sh=Integer.parseInt((String)psh1.getSelectedItem());

int sm=Integer.parseInt((String)psm1.getSelectedItem());

Time sti=new Time(sh,sm,00);

String st=""+sh+":"+sm+"";

int eh=Integer.parseInt((String)psh2.getSelectedItem());

int em=Integer.parseInt((String)psm2.getSelectedItem());

Time eti=new Time(eh,em,00);

String et=""+eh+":"+em+"";

String post="PostPone";

String po="Yet To Attend";

String fb="Attended";


66


67/102


Vector vm=new Vector(10,10);

int uid[];

int r;

try

{

Class cfn=Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");

Connectioncon=DriverManager.getConnection("Jdbc:Odbc:pro");

Statement sta=con.createStatement();

ResultSet rs=sta.executeQuery("select idno from schedule2where dd="+d+" and mm="+m+" and yy="+y+" and desc='"+s3+"' ");

while(rs.next())

{

int id=rs.getInt("idno");

vm.addElement(""+id);

}

Enumeration enum=vm.elements();

uid=new int[vm.size()];

int p=0;

while(enum.hasMoreElements())

{

int ll=Integer.parseInt((String)enum.nextElement());

uid[p]=ll;

p++;


67


68/102


}

for(int i=0;i


69/102


}

Mcheck mck=new Mcheck(this,"Ok Submitted");

con.close();

}

catch(Exception ec)

{

System.out.println(""+ec);

}

}

}

/* public void method()

{

boolean check1=false;

Time stim,etim;

try

{

Class cfn1=Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");

Connectioncon1=DriverManager.getConnection("Jdbc:Odbc:pro");

Statement st2=con1.createStatement( );

ResultSet rs=st2.executeQuery("select stime,etime fromschedule2 where idno="+idn+" and dd="+d+" ");

while(rs.next())


69


70/102


{

stim=rs.getTime("stime");

etim=rs.getTime("etime");

int i=stim.compareTo(sti);

int j=sti.compareTo(etim);

int a=stim.compareTo(eti);

int b=eti.compareTo(etim);

if( (i==0)&&(b==0) )

{

check1=true;

}

if( ((i==-1) && (j==-1))||((a==-1)&&(b==0)) )

{

check1=true;

}

}

con1.close();

}

catch(Exception ec)

{

System.out.println(""+ec);

}


70


71/102


if(check1)

{

Mcheck mt=new Mcheck(this,"This time allready

scheduled");

}

else

{

value=1;

}

}*/

/*public static void main(String s55[])

{

new details();

}*/


71


72/102



72


73/102



import java.awt.*;


import java.io.*;

import java.sql.*;

public class uinf extends JFrame implements ActionListener

{

Runtime r;

JLabel l;

JComboBox cb;

JButton go;

String selectedname;

public uinf()

{

setTitle("Selection Of Employee");

setSize(500,400);

move(120,100);

l=new JLabel("Select the Employee's name You wish toView/Add");

cb=new JComboBox();

go=new JButton("GO");


73


74/102



c.setLayout(null);

l.setBounds(75,40,420,20);

l.setFont(new Font("convecta",Font.BOLD,16));

l.setForeground(Color.black);

cb.setBounds(95,150,150,25);

cb.setFont(new Font("convecta",Font.BOLD,16));

go.setBounds(250,150,52,26);

go.setFont(new Font("convecta",Font.BOLD,12));

go.setForeground(Color.black);

c.add(cb);c.add(l);c.add(go);

setVisible(true);

appendusers();

go.addActionListener(this);

}//end of uinf constructor.

public void appendusers()

{


74


75/102


try

{

Class cc=Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");

Connection con=DriverManager.getConnection("jdbc:odbc:pro");

Statement st=con.createStatement();

ResultSet rs=st.executeQuery("select l_name from regs");

while(rs.next())

{

String name=rs.getString("l_name");

cb.addItem(name);

}

con.close();

}

catch(Exception ee)

{

System.out.println(" "+ee);

}

}//end of appendusers.

public void actionPerformed(ActionEvent ae)

{

Object o=ae.getSource();


75


76/102


if(o==go)

{

selectedname=(String)cb.getSelectedItem();

todays td=new todays();

td.senditems(selectedname);

td.method();

td.display();

this.setVisible(false);

}

}//end of actionPerformed.

/*public static void main(String args[])

{

new uinf();

} */

}//end of uinf class.


76


77/102


DESCRIPTION OF HOME PAGE:


77


78/102


The project of Employee Scheduling has been carried out in threemodules

1. Supervisor2. Employee3. Read-only purpose

This form displays all modules in the project and helps to choose our ownchoice

DESCRIPTION OF LOGIN FORM:


78


79/102


If we have chosen the first module supervisor.

This form helps to login in to the organization by the specified nameand correct password

DESCRIPTION OF EMPLOYEE SELECTION:


79


80/102


In the login is successful next the supervisor provided with list of the

employees in the organization supervisor selects one of the Employee and

fixes his appointments

.

DESCRIPTION OF VIEW - SCHEDULE:


80


81/102


The scheduler can view the schedule of an employee byselecting any

year & month.

DESCRIPTION OF VIEW SCHEDULE:


81


82/102


In this supervisor fixes the schedule of an employee by selects the

date and fixes the staring time, ending time, description, Details for an

employee

DESCRIPTION TO CHECK FREE FORM:


82


83/102


In this form supervisor will check whether the employee is free at aparticular time.

DESCRIPTION:


83


84/102


To choose the second module ie., employee module we need toenter our choice as 2.

DESCRIPTION


84


85/102


In the employee module we can register a new employee ie., a newemployee or if he is the existing employee he need to choseregistered employee.

DESCRIPTION TO THE FILL_UP FORM:


85


86/102


If the employee is new employee then he need to enter

his

particulars in the registration form. As the user registers himself

he can login through his id and password.


86


87/102



87


88/102


DESCRIPTION:

In this form the registered employee login in to organization and continue

his process.

.


88


89/102


DESCRIPTION:

To choose the third module ie., read-only module we need to

enter our choice as 3.

DESCRIPTION:


89


90/102


This form will the employee to view his activities.


90


91/102


DESCRIPTION:

If employee wants to view his activities he select month,date and enter

Starting,ending date of a month.


91


92/102



92


93/102


DESCRIPTION:

Finally employee view his activities of a month.


93


94/102


9.TEST CASES


94


95/102


S

r.

No

Input Expected Behavior

Observed

behavior

Status

P = PassedF = Failed

1

Enter Wrong username and

password forEmployee

Error should bedisplayed as amessage

-do- P

2

Enter Correct username and

password forauthorized user

Home page should bedisplayed. -do- P

3

Create Newemployee from theoptions

New employee formShould be Displayed

-do- P

4

Create Schedulefor Activities

Activities will becreated -do- P

5

Check the Client

side validationslike mandatoryfields username,

passwords, email-id etc

Error message should

be displayed ifanything enteredwrong

-do- P


95


96/102


6Create calendarfor monthActivities

Calendar Should beDisplayed -do- P

7

View the

Scheduling,meetings,Activities list

Display Scheduling,

Activities list . -do- P

8

Enter as a newEmployee forRegistration

New Registrationwill be Displayed -do- P

9Login asSupervisor byentering wronguser name and

password

Error should bedisplayed -do- P

10 Login asSupervisor r byentering correctuser name and

password

Home page should bedisplayed

-do- P

11 Check theScheduling details

Employee SchedulingDetails Will beDisplayed

-do- P

12 Create Calendar forActivities

Calendar will beDisplayed -do- P

13 Update theSchedulinginformation

Updates theSchedulinginformation indatabase

-do- P

14 View and AddScheduling Detailsof the Employee

Displays view andAdd of theScheduling details

-do- P


96


97/102


TESTING

Testing is the major quality measure employed during the software

engineering development. Its basic function is to detect error in the

software. Testing is necessary for the proper functioning of the system.

Testing has to be done at four levels.

9.1 UNIT TESTING

Unit testing focuses verification effort on the smallest unit of the

software, design the module. Here, using the detail design as a guide,

important control paths are tested to uncover errors within the boundary of

the module. Unit testing is always white-box oriented, and the step can be

conducted in parallel for multiple modules.

9.2 INTEGRATION TESTING

Integration testing is a systematic technique for constructing the

program structure while at the same time conducting tests to uncover

errors, associated with interfacing .The objective is to take the unit

tested modules and build program structure that has been directed by

the design.


97


98/102


9.3 VALIDATION TESTING

Validation testing demonstrates the traces the requirements of the

software .This can be achieved through a series of black box tests

9.4 SYSTEM TESTING

System testing is actually a series of different tests whose primary purpose is

to fully exercise the computer-based system . Although each test has a

different purpose, all works should verify that all system elements have been

properly integrated and perform allocated functions. The various tests

include recovery testing , stress testing , perform testing


98


99/102



99


100/102


10.MAINTENANCE AND IMPLEMENTATION

CORRECTIVE MAINTENANCE

This acts to correct errors that are uncovered after the software is in

use.

10.2 ADAPTIVE MAINTENANCE

This is applied when changes is the external environment precipitate

modifications to software.

10.3 PREVENTIVE MAINTENANCE

This improves future maintainability and reliability and provides basis

for future enhancements.


100


101/102



101


102/102


11.CONCLUSION

This point describes you how to overcome the problem that

arisen in general for any person or organization scheduling the

appointments, activities or daily work is somewhat legitimate and a bit

of burden apart from other works being on hand.

The task of scheduling and fixing appointments as well as

other activities whether they may be official or personal is time

consuming and also may lead to confusion if not properly scheduled.

Calendar and Scheduler (package) is such a tool with

which this process of scheduling will be easy and even online in the

organisation where it is installed.

Scheduling becomes such an easy task that it reduces much

time when compared to previous methods. This enables for the

employee to check any other tasks waiting, postponed and so on. The

102