ACCESS POLICY CONSOLIDATION FOR EVENT PROCESSING SYSTEMS

VI- Semester MCA Dissertation Report on

Student Name:- VIVEK KUMAR (1AZ11MCA66)

Project Guide Prof. Rajesh Rao K.

Department of MCA Acharya Institute of Technology

CONTENTS Introduction

Existing System

Proposed System

System Requirements Specification

Modules

System Design

Screen Shots

Test Cases

Conclusion

INTRODUCTION The project ACCESS POLICY CONSOLIDATION FOR

EVENT PROCESSING SYSTEMS deals with the manufacturer, shipping company and customers about the product’s buy or sale of establishments online.

Event processing systems respond to events in the system’s environment or user interface.

The key characteristic of event processing systems is that the timing of events is unpredictable and the system must be able to cope with these events when they occur.

INTRODUCTION CONT…

In business processes, it is necessary to detect inconsistencies or failures early. For example, in manufacturing and logistics processes, items are tracked continuously to detect loss or to reroute them during transport. To answer this need complex event processing (CEP) systems have evolved as a key paradigm for business and industrial applications.

CEP systems allow to detect situations by performing operations on event streams which emerge from sensors all over the world, e.g. from packet tracking devices.

EXISTING SYSTEMS

Current event processing systems lack methods to preserve privacy constraints of incoming event streams in a chain of subsequently applied stream operations.

This is a problem in large-scale distributed applications like a logistic chain where event processing operators may be spread over multiple security domains.

An adversary can guess from legally received outgoing event streams confidential input streams of the event processing system.

PROPOSED SYSTEM

This project presents a fine-grained access management for complex event processing.

Each incoming event stream can be protected by the specification of an access policy.

The utility of the event processing system is increased by providing and computing in a scalable manner.

HARDWARE-SOFTWARE REQUIREMENT SPECIFICATION

Software Requirements

Operating System - Windows XP /7/8 Application Server - Apache Tomcat 6.0 Front End - HTML, Java Server side Script - Java Server Pages. Database - MySQL Software Tools - Eclipse IDE Database Connectivity - JDBC.

HARDWARE-SOFTWARE REQUIREMENT SPECIFICATION

Hardware Requirements

• Processor - Pentium IV or above

• Speed - 1.1 GHz

• RAM - 512 MB or above

• Hard Disk - 20 GB or above

• Key Board - Standard Windows Keyboard

• Mouse - Two or Three Button Mouse

MODULES

Modules in this project are:

Event Processing Manufacturer Shipping Company Customer

MODULES DESCRIPTION Event Processing:- Event processing systems respond to events in

the system’s environment or user interface. The key characteristic of event processing systems is that the timing of events is unpredictable and the system must be able to cope with these events when they occur.

Manufacturer:- In this module manufacturer, insert the product details. The shipping company will forward the request to manufacturer sent by customer. So manufacturer can view product request from shipping company. The manufacturer will send the product details to shipping company to delivery date and pickup time means the manufacturer will send the export details.

MODULE DESCRIPTION CONT…

Shipping Company:- The customer can request a product from shipping company. So, in this module shipping company, view product request from customer. Then the shipping company forwards the request to manufacturer or rejects the request. So as per the product details sent by manufacturer the shipping company delivers the product.

Customer:- In this module customer, views the product details. If the customer likes to purchase any product then the customer order the product from Ship Company. The customer can also view the order from Ship Company. Customer views the import details.

E-R DIAGRAM

USE-CASE DIAGRAM

CLASS DIAGRAM

SEQUENCE DIAGRAM

SCREEN SHOTLogin Page

SCREEN SHOTSRegistration Page

SCREEN SHOTSCustomer’s Homepage

SCREEN SHOTSProduct Details Page

SCREEN SHOTSBooking Order Page

SCREEN SHOTSShipping Company’s Homepage

SCREEN SHOTSProduct Request Page

SCREEN SHOTSSend Order to Manufacturer

SCREEN SHOTSManufacturer’s Homepage

SCREEN SHOTSInsert Product Details

SCREEN SHOTSProduct Request Details

SCREEN SHOTSStatus of Requested Product

TEST CASES

Input Input Description

Excepted Value

Actual Result

Pass /Fail Remarks

Positive

Input

user name:

manufacturer

It should be accepted Accepted P Login

(Next Page)

Negative

Input

user name: user It shouldn’t be accepted Not

Accepted

P Invalid

username or

password

Negative

Input

user name:

“Empty”

It shouldn’t be accepted Not

Accepted

P Invalid

username or

password

Positive

Input

password:

********

It should be accepted Accepted P Hidden

password

Negative

Input

password:

“Empty”

It shouldn’t be accepted Not

Accepted

P Invalid

username or

password

CONCLUSION

This project addressed the inheritance and consolidation of access policies in heterogeneous CEP systems.

We identified a lack of security in multi-hop event processing networks and proposed a solution to close this gap.

More specific, we presented an approach that allows the inheritance of access requirements, when events are correlated to complex events.

THANK YOU