project report on event management.pdf | Java Servlet | Java ...

1. INTRODUCTION 1.1.Scope of The Project The objective of this application is to develop a system that effectively manages all the data related to the various events that take place in an organization. The purpose is to maintain a centralized database of all event related information. The goal is to support various functions and processes necessary to manage the data efficiently.

1.2. Existing System This existing system is not providing secure registration and profile management of all the users properly.This system is not providing on-line Help.This system doesn’t provide tracking of users activities and their progress.This manual system gives us very less security for saving data and some data may be lost due to mismanagement.This system is not providing event management through internet.This system is not providing proper events information.The system is giving manual information through the event management executer.

1.3. Proposed System The development of this new system contains the following activities, which try to automate the entire process keeping in the view of database integration approach.This system maintains employee’s personal, address, and contact details.This system will provide on line help and search capabilities. User friendliness is provided in the application with various controls provided by system rich user interface.Authentication is provided for this application only registered users can access. event information files can be stored in centralized database which can be maintained by the system. provides the employees to manage the events systematically.

1

This system

2. SYSTEM ANALYSIS 2.1 FEASIBILITY STUDY A feasibility study is a high-level capsule version of the entire System analysis and Design Process. The study begins by classifying the problem definition. Feasibility is to determine if it’s worth doing. Once an acceptance problem definition has been generated, the analyst develops a logical model of the system. A search for alternatives is analyzed carefully. There are 3 parts in feasibility study.

2.1.1 Operational Feasibility Question that going to be asked are 

Will the system be used if it developed and implemented.



If there was sufficient support for the project from the management and from the users.



Have the users been involved in planning and development of the Project.

2.1.2 Technical feasibility 

Does the necessary technology exist to do what is been suggested



Does the proposed equipment have the technical capacity for using the new system?



Are there technical guarantees of accuracy, reliability and data security?



The project is developed on Pentium III with 128 MB RAM.



The environment required in the development of system is any windows platform.



The observer pattern along with factory pattern will update the results eventually.



The language used in the development is JAVA J2SDK1.4.0, Servlets, JDBC, Tomcat Server and database as Oracle 8i.

2.1.2 Economical Feasibility To decide whether a project is economically feasible, to consider various factors as cost benefit analysis, long-term returns and maintenance costs. 2

2.2 FUNCTIONAL REQUIREMENTS Functional requirement defines a function of a software system or its component. A function is described as a set of inputs, the behavior, and outputs. Functional requirements may be calculations, technical details, data manipulation and processing and other specific functionality that define what a system is supposed to accomplish. Behavioral requirements describing all the cases where the system uses the functional requirements are captured in use cases.

NUMBER OF MODULES

The system after careful analysis has been identified to be presented with the following modules: The Modules involved are

Event Management Module : The employees who can use the application their personal information, contact information and other information etc… This module consist of events information. All the information like type of the event, incharge of the event. These all information is maintained here. Here in this module application is maintaining the total information of the event and the resources. Like type of the resource, resource details and resource management.

Event Task Manager Module : The module is having the information of the events and their task manager details. Events task are maintained here, the total details of the events and incharge details maintained. In this module the information of the event and their details like, what are the events are there and from which event and to which event the movement is going on , which date , status of the event etc.

Scheduling : This module consists of events information. All the information like type of the event, in charge of the event. These all information is maintained here.

3

Security & Authentication Module : Security & Authentication module is main module which can provide security for entire processing of the system by using username, password, login, password modifications etc.

Reports Module : In this module system can generate different type of the reports.

Payment Module: In this module user can pay the amount.

2.3 NON-FUNCTIONAL REQUIREMENTS Performance Requirements: Performance is measured in terms of the output provided by the application. Requirement specification plays an important part in the analysis of a system. Only when the requirement specifications are properly given, it is possible to design a system, which will fit into required environment. It rests largely with the users of the existing system to give the requirement specifications because they are the people who finally use the system. This is because the requirements have to be known during the initial stages so that the system can be designed according to those requirements. It is very difficult to change the system once it has been designed and on the other hand designing a system, which does not cater to the requirements of the user, is of no use.

The requirement specification for any system can be broadly stated as given below: 

The system should be able to interface with the existing system



The system should be accurate



The system should be better than the existing system

4

Reliability : In this system reliability means the mail which is send by the source must reach the target user with any modification and accurate.

Security : The web server and database server should be protected from hacking, virus etc

Portability : The application will be developed using standard open source software (Except Oracle) like Java, tomcat web server, Internet Explorer Browser etc these software will work both on Windows and Linux o/s. Hence portability problems will not arise.

Availability : This software will be available always.

Maintainability : In this system the presentation layer is clearly separated from the service layer. So any modification in future will be done with less efforts. The database will be running at the server. Users access these forms by using the user-ids and the passwords.

5

2.4 HARDWARE REQUIREMENTS: Processor

:

Intel P-IV based system

Processor Speed

:

2.0. GHz

RAM

:

1GB

Hard Disk

:

40GB to 80GB

2.5 SOFTWARE REQUIREMENTS:

Database

:

Oracle 10g

Server

:

Apache Tomcat 4 or higher

Frontend

:

HTML

Scripting language

:

Java Script

Web Technologies

:

Servlets, Jsp

IDE

:

My Eclipse

Technology

:

Java

6

2.6 DFD’s (Data Flow Diagrams) Data Flow Diagram for Context Level

CONTEXT LEVEL DATA FLOW

Data Input Stages Employee

Administrator

Data Output Stages Data Base Department

EventManager

Data Input Stages

Event

Data Output Stages UI Screens

EventTypes

Data Input Stages Employee

Task

Data Output Stages Reports

Profile

Security

AdventExecuter

System Process Fig: 2.6.1 Data flow diagram for Context Level 7

Data Flow Diagram for Level-1

Fig: 2.6.2 Data Flow Diagram for Level-1 Data Flow Diagram for Administrator Context Level-1

Fig: 2.6.3 Data Flow Diagram for Administrator Context Level-1 8

Data Flow Diagram for Level 1.0

Fig: 2.6.4 Data Flow Diagram for Level 1.0

Data Flow Diagram for Level 1.0.1

Fig: 2.6.5 Data Flow Diagram for Level 1.0.1

Data Flow Diagram for Level 1.1

Fig: 2.6.6 Data Flow Diagram for Level 1.1

9

Data Flow Diagram for Level 1.1.0

Fig: 2.6.7 Data Flow Diagram for Level 1.1.0

Data Flow Diagram for Level 1.2

Fig: 2.6.8 Data Flow Diagram for Level 1.2

Data Flow Diagram for Level 1.3

Fig: 2.6.9 Data Flow Diagram for Level 1.3

Data Flow Diagram for Level 1.4

Fig: 2.6.10 Data Flow Diagram for Level 1.4 10

Data Flow Diagram for Level 1.5

Fig: 2.6.11 Data Flow Diagram for Level 1.5 Data Flow Diagram for Event Manger Context Level-1

Fig: 2.6.12 Data Flow Diagram for Event Manger Context Level-1 11

Data Flow Diagram for Level 1.0

Fig: 2.6.13 Data Flow Diagram for Level 1.0

Data Flow Diagram for Level 1.1

Fig: 2.6.14 Data Flow Diagram for Level 1.1

Data Flow Diagram for Level 1.2

Fig: 2.6.15 Data Flow Diagram for Level 1.2

12

Data Flow Diagram for Level 1.3

Fig: 2.6.16 Data Flow Diagram for Level 1.3 Data Flow Diagram for Level 1.4

Fig: 2.6.17 Data Flow Diagram for Level 1.4

Data Flow Diagram for Employee Context Level-1

Fig: 2.6.18 Data Flow Diagram for Employee Context Level-1 13

Data Flow Diagram for Level 1.0

Fig: 2.6.19 Data Flow Diagram for Level 1.0

Data Flow Diagram for Level 1.1

Fig: 2.6.20 Data Flow Diagram for Level 1.1

Data Flow Diagram for Level 1.2

Fig: 2.6.21 Data Flow Diagram for Level 1.2 Data Flow Diagram for Level 1.3

Fig: 2.6.22 Data Flow Diagram for Level 1.3 14

3. SYSTEM DESIGN 3.1 UML DIAGRAMS The unified modeling language allows the software engineer to express an analysis model using the modeling notation that is governed by a set of syntactic semantic and pragmatic rules.

3.1.1 Class Diagram : The class diagram shows a set of classes, interfaces, collaborations and their relationships.

Fig: 3.1.1.1 Class diagram for event management 15

3.1.2 Use case diagrams: Use case diagram consists of actors, use cases and their relationships. These diagrams are especially important in organizing and modeling the behaviors of a system.

login

Login

Status

Event Type

Employee

Events

Tasks

Fig: 3.1.2.1 Use case diagram for Employee

16

EventTypes Event login Types

Department Departments Status

Adminiostrator

Event Type Designations Designation

Incharges Incharges

Events Manager

Employees

Fig: 3.1.2.2 Use case diagram for Administrator

17

EventTypes Login login

ResourceType Departments

AllocateResource

Allocate Resource

EventManager

resource Resource Resources

Events

Events task Manager tasks Schedule Schedule

tasks Tasks Tasks

profile

Fig: 3.1.2.3 Use case diagram for Task Manager

18

3.1.3 Sequence Diagram: The Sequence diagram is an interaction diagram that emphasizes the time-ordering of messages.

Fig: 3.1.3.1 Sequence diagram for Admin

19

Fig: 3.1.3.2 Sequence diagram for Event Manager

20

Fig: 3.1.3.3 Sequence diagram for Employee

Administr ator

login

Employee

login login

validate

validLogin validLogin

Fig: 3.1.3.4 Sequence diagram for Login

21

3.1.4 Activity Diagram An Activity diagram is a special kind of a state chart diagram that shows the flow from activity to activity within a system.

Fig: 3.1.4.1 Activity diagram for Admin 22

Fig: 3.1.4.2 Activity diagram for Task Manager

23

Fig: 3.1.4.3 Activity diagram for Employee

24

3.1.5 Collaboration Diagram The second interaction diagram is collaboration diagram. It shows the object organization as shown below. Here in collaboration diagram the method call sequence is indicated by some numbering technique as shown below. 3: validate

login

2: login 4: validLogin 5: validLogin

1: login

Emplo yee

Adminis trator

Fig: 3.1.5.1 Collaboration Diagram for Login 5: validateEmpInfo

Emplo yee 2: validate 6: empAdded Login

4: addEmp 1: login

Admi n

3: validLogin

Fig: 3.1.5.2 Collaboration Diagram for Employee Registration 25

3.2 ER-DIAGRAM

Fig: 3.1.3 ER diagram for event management

26

3.3 Tables

3.3.1 User Table Name username password

Data Type Text Text

Size 20 20

Name eid customer_Name Event_Type

Data Type Number Text Text

Size 14 14 14

Address cno

Text Number

14 14

Event_time event_date

Text Text

14 14

Total_amount

Number

14

Adv_amount status

Number Text

14 14

Rdate

Number

14

Data Type Number Text Number

Size 20 20 20

3.3.2

3.3.3

Event Table

Pay Table

Name cardno bankname cvvno

27

3.4

SYSTEM ARCHITECTURE

Fig 3.4.1 Architecture of Proposed System

28

4.

IMPLEMENTATION

INTRODUCTION: Implementation is the stage of the project when the theoretical design is turned out into a working system. Thus it can be considered to be the most critical stage in achieving a successful new system and in giving the user, confidence that the new system will work and be effective. The implementation stage involves careful planning, investigation of the existing system and it’s constraints on implementation, designing of methods to achieve changeover and evaluation of changeover methods.

4.1 TECHNOLOGIES USED 4.1.1 About JAVA: Initially the language was called as “oak” but it was renamed as “java” in 1995.The primary motivation of this language was the need for a platformindependent(i.e. architecture neutral)language that could be used to create software to be embedded in various consumer electronic devices. 

Java is a programmer’s language



Java is cohesive and consistent



Except for those constraint imposed by the Internet environment. Java gives the programmer, full control

Finally Java is to Internet Programming where c was to System Programming.

Importance of Java to the Internet :

Java has had a profound effect on the Internet. This is because; java expands the Universe of objects that can move about freely in Cyberspace. In a network, two categories of objects are transmitted between the server and the personal computer. They are passive information and Dynamic active programs. in the areas of Security and probability. But Java addresses these concerns and by doing so, has opened the door to an exciting new form of program called the Applet.

29

Applications and applets :

An application is a program that runs on our Computer under the operating system of that computer. It is more or less like one creating using C or C++ .Java’s ability to create Applets makes it important. An Applet I san application, designed to be transmitted over the Internet and executed by a Java-compatible web browser. An applet I actually a tiny Java program, dynamically downloaded across the network, just like an image. But the difference is, it is an intelligent program, not just a media file. It can be react to the user input and dynamically change.

Java Architecture : Java architecture provides a portable, robust, high performing environment for development. Java provides portability by compiling the byte codes for the Java Virtual Machine, which is then interpreted on each platform by the run-time environment. Java is a dynamic system, able to load code when needed from a machine in the same room or across the planet.

Compilation of code When you compile the code, the Java compiler creates machine code (called byte code)for a hypothetical machine called Java Virtual Machine(JVM). The JVM is supposed t executed the byte code. The JVM is created for the overcoming the issue of probability. The code is written and compiled for one machine and interpreted on all machines .This machine is called Java Virtual Machine. Compiling and interpreting java source code.

30

Pc compiler Macintosh compiler

Source code

Java Byte code Platform indepen dent

Java interpreter

Java interpreter macintosh

SPARC Compiler

Java interpreter (SPARC)

Fig 4.1.1.1 SourceCode Applications

During run-time the Java interpreter tricks the byte code file into thinking that it is running on a Java Virtual Machine. In reality this could be an Intel Pentium windows 95 or sun SPARCstation running Solaris or Apple Macintosh running system and all could receive code from any computer through internet and run the Applets.

4.1.2 servlets/JSP A Servlet Is a generic server extension. a Java class that can be loaded Dynamically to expand the functionality of a server.Servlets are commonly used with web servers. Where they can take the place CGI scripts. A servlet is similar to proprietary server extension, except that it runs inside a Java Virtual Machine (JVM) on the server, so it is safe and portable Servlets operate solely within the domain of the server. Unlike CGI and Fast CGI, which use multiple processes to handle separate program or separate requests, separate threads within web server process handle all servlets. This means that servlets are all efficient and scalable. Servlets are portable; both across operating systems and also across web servers. Java Servlets offer the best possible platform for web application development.

31

Servlets are used as replacement for CGI scripts on a web server, they can extend any sort of server such as a mail server that allows servelts t extend its functionality perhaps by performing a virus scan on all attached documents or handling mail filtering tasks. Servlets provide a Java-based solution used to address the problems currently associated with doing server-side programming including inextensible scripting solutions platform-specific API’s and incomplete interface. Servlets are objects that conform to a specific interface that can be plugged into a Java-based server.Servlets are to the server-side what applets are to the server-side what applets are to the client-side-object byte codes that can be dynamically loaded off the net. They differ form applets in than they are faceless objects(with out graphics or a GUI component).They serve as platform independent, dynamically loadable,plugable helper byte code objects on the server side that can be used to dynamically extend server-side functionality. For example an HTTP servlet can be used to generate dynamic HTML content when you use servlets to do dynamic content you get the following advantages:  They’re faster and cleaner then CGI scripts  They use a standard API( the servlet API)  They provide all the advantages of Java (run on a variety of servers without needing to be rewritten)

Attractiveness Of Servlets: They are many features of servlets that make them easy and attractive to tuse these include:  Easily configure using the GUI-based Admin tool]  Can be Loaded and Invoked from a local disk or remotely across the network.  Can be linked together or chained, so that on servlet can call another servlet, or several servlets in sequence.  Can be called dynamically from with in HTML, pages using server-side include-tags.

32

 Are secure-even when downloading across the network, the servlet security model and servlet and box protect your system from unfriendly behavior.,

Advantages of the servlet API One of the great advantages of the servlet API is protocol independent. It assumes nothing about:  The protocol being used to transmit on the net  How it is loaded  The server environment it will be running in  These quantities are important, because it allows the Servlet API to be embedded in many different kinds of servers.There are other advantages to the servelt API as well These include:  It’s extensible-you can inherit all your functionality from the base classes made available to you  It’s simple small, and easy to use.

Features of Servlets: 

Servlets are persistent.Servlet are loaded only by the web server and can maintain services between requests.



Servlets are fast. Since servlets only need to be l\loaded once, they offer much better performance over their CGI counterparts.



Servlets are platform independent.



Servlets are extensible Java is a robust, object-oriented programming language, which easily can be extended to suit your needs.



Servlets are secure



Servlets are used with a variety of client.

Servlets are classes and interfaces from tow packages,javax .servlet and javax.servlet.http.The java.servlet package contains classes t support generic, protocolindependent servlets.The classes in the javax.servelt.http package To and HTTP specific functionality extend these classes 33

Every servlet must implement the javax.servelt interface.Most servlets implement it

by

extending

one

of

two

classes.javax.servlet.GenericServlet

or

javax.servlet.http.HttpServlet.A protocol-independent servlet should subclass GenericServlet.while an Http servlet should subclass HttpServlet, which is itself a subclass of Generic-servlet with added HTTP-specific functionality. Unlike a java program, a servlet does not have a main() method,Instead the server in the process of handling requests invoke certain methods of a servlet.Each time the server dispatches a request to a servlet, it invokes the servelts Service() method, A generic servlet should override its service() method to handle requests as appropriate for the servlet.The service() accepts two parameters a request object and a response object .The request object tells the servlet about the request, while the response object is used to return a response InContrast.anHttp servlet usually does not override the service() method.Instead it overrides doGet() to handle GET requests and doPost() to handle Post requests. An Http servlet can override either or both of these modules the service() method of HttpServlet handles the setup and dispatching to all the doXXX() methods.which iswhy it usually should not be overridden The remainders in the javax.servlet and javax.servlet.http.package are largely support classes .The ServletRequest and ServletResponse classes in javax.servlet provide access to generic server requests and responses while HttpServletRequest and HttpServletResponse classes in javax.servlet provide access to generic server requests and responses while HttpServletRequest and HttpServletResponse in javax.servlet.http provide access a HTTP requests and responses . The javax.servlet.http provide contains an HttpSession class that provides built-in session tracking functionality and Cookie class that allows quickly setup and processing HttpCookies. Loading Servlets: Servlets can be loaded from their places. From a directory that is on the CLASSPATH. The CLASSPATH of the JavaWebServer includes service root/classes/, which

is

where

the

system

classes

reside.From

the