Proficient Key for Huge and Active Multitroupe

Title of the Project: Proficient Key for Huge and Active Multitroupe Project Architecture: N-Tire SDLC Methodologies: Waterfall/Spiral Model Course: Roll No: Name of the Student: Technology And Language: Internal Guide: E-Mail ID: Mobile No (Student): Abstract of the Project: Introduction:
The Proficient Key for Huge and Active Multitroupe is a network based application used in pay-TV, teleconferencing, real-time distribution of stock market price and etc. In this project, we propose a scalable, efficient, authenticated group key agreement scheme for large and dynamic multicast systems. The proposed key agreement scheme is identity-based which uses the bilinear map over the elliptic curves.

JAVA

Functional Requirements:
Key Generation is used to generate private keys. Message Transmission is used for multicasting and unicasting. Cryptography is used for encryption and decryption of data Authentication for new users.

Non-Functional Requirements:
The system should be Network-based system. Users should use the system via Network. Each user should have a user account. The system should have the IP address It doesnt permit to unregistered user to access for Insurance on Network. The system should have Role based System functions access. Approval Process has to be defined. The system should have Modular customization components so that they can be reused across the implementation.

These are the mainly following: 24 X 7 availability Better component design to get better performance at peak time Flexible service based architecture will be highly desirable for future extension.

Existing System
Let us consider the existing system is manual and the manual system works in the following way: The existing system involves either centralized key server (in which all the systems depend on centralized server for key generation), and individual rekeying is done for join or leave operations in case of distributive key generation algorithms. In this case of individual re-keying, after every join or leave operation each member individually rekeys.

The more resources are used for re-keying because it is done for each join or leave operations. In this case of using a centralized server, the risk of single point failure is Key information depends on centralized key server.

Computational and Communication cost is more. Individual re-keying is done. Whenever a member joins or leaves in the case of distributed key generation algorithm.

More resources used for re-keying because it is done for each join or leave operations.

Proposed System
To overcome all the difficulties of the existing system the management has proposed automated the whole system and the development of the new automated system contains the following activities, which try to automate the entire process keeping in view of the database integration approach. The proposed system involves collaborative key agreement in which all nodes become a part of the secure group key.

Moreover, rekeying is done after a batch of join or leave operations. The protocol remains efficient even when the occurrences of join/leave events are very frequent. The Key information does not depend on centralized key server. It is free from the problem of single point failure. Computational and Communication cost is less. The resources used for rekeying is minimized because it is being done for batch of join/leave operations

Modules
Key Generation This module is used to generate Private Keys. User used that keys .It is generated by DES algorithm. Message Transmission Multicasting means that one sender can send one message to multiple destination Unicasting means one message can send to only one receiver. Cryptography Algorithms are used to perform Encryption Same decryption is done by receiver to Decrypt the message Authentication User login and password is there to provide proper authentication.

Users of the System:

This system should be designed to support the following users: Admin Normal users

Environment:
Operating System : - Microsoft Windows XP/2000 or Higher Data Base Server: ORACLE 10G Clients: CONSOLE Development Tools: Net beans 6.8 Documentation Tools: MS Office 2003/2007 Drawing Tools: IBM Rational Rose Enterprise User Interface: AWT & SWINGS Code Behind: AWT & SWINGS

Hardware Requirements:
Number 1 Description PC With Minimum 20 GB Hard-Disk And 1GB RAM

Software Requirements:

Number 1 2. 3. 4.

Description Windows XP/2000 Or Higher With MS-Office 2003/2007 Oracle 10G AWT & SWINGS CONSOLE

Milestones:
No. Milestone Name Requirements Specification Milestone Description Remarks

Technology Familiarization

Complete specification of the system including defining hierarchies constitutes this milestone. A document detailing the same should be written and a presentation on that be made. Understanding of the technology needed to implement the project.

Attempt should be made to add some more relevant functionality other than those that are listed in this document.

Database Creation

A database of at least 10 entries of users with at least 1 should application admin.

High-level and Detailed Design Development of Front End Functionalities.

Listing down all possible scenarios and then coming up with flow-charts or pseudo code to handle the scenario. Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options The front-end developed in the earlier milestone will now be able to update the database. Other features should be functional at this stage. In short, the system should be ready for integration testing. The system should be thoroughly tested by running all the test cases written for the system (from milestone 5).

The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective. It is important to finalize on the database at this stage itself so that development and testing can proceed with the actual database itself. The scenarios should map to the requirement specification

During this milestone period, it would be a good idea for the team to start working on a test-plan for the entire system. This test-plan can be updated as and when new scenarios come to mind.

Integrating the Front-end with the Database

Integration Testing

Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged.

Final Review

Issues found during the previous milestone are fixed and the system is ready for the final review.

During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled

The following steps will be helpful to start of the project:

Study and be comfortable with : JAVA & SQL . Gather some knowledge of product hierarchies and maintenance before starting the design. Create a user database with different access levels. Start with creating the login screen. Create menus for navigation and group the functionalities as sub menus. Create the help-pages of the application in the form of FAQ. This will helps user.