Category: CSE Projects

Download All Computer Science Engineering Final Year Projects, Project Abstracts, Project Reports, C, C++, JAVA, .NET, C#, VB, PHP Projects. CSE projects listed here covers different topics in java for final year students for free download.

Posted on

Preemptive Scheduling Systems Project Report

Introduction to Preemptive Scheduling Systems Project:

Preemptive scheduling systems are systems which can be employed to predict possibly threatening grave harms in several territories such as framework, factory machines, ancient statues, dams, bridges etc. The accumulation and interconnection of field data usually employing a dispensed structure of transducers is the essence of Preemptive scheduling. Every application leads to change in the state and the situation of the transducer.

The traditional maintenance systems in factories and other places point out the harm already done and report it after the harm has occurred. The reporting of the harm after its done is not a reasonable and optimum manner for the functioning of a factory.

This project suggests a new method that anticipates grave harms that may terminate production beforehand and schedule the maintenance correspondingly. The critical feature of preemption systems is that information from different sections of a machine undergoes frequent exertion. For instance, a part such as a ball bearing doesn’t show the harm caused immediately.

It’s a prolonged and slow procedure that initiates with a petty distortion in the ball bearings. Such distortions are noticed by the unusual conduct like sudden fluctuations. These sudden signs can be considered and based on a data over an extended period, the degree of the harm caused may be determined in the initial phases of the procedure.

 The project deals with Embedded System, which is a blending of hardware and software employed to attain a sole job. Embedded Systems mean computer systems which supervise, react to or curb exterior surroundings that are linked to systems via sensors, actuators and alternative I/O interfaces. These systems must maintain the timing and other restrictions enforced on it by the surroundings. An Embedded System is an element residing in bigger system. This system aims to accomplish a sole and well-determined job.

Download Preemptive Scheduling Systems Project Report.

Posted on

Seminar Report on A Distributed Mobile Database Implementation On Pocket Pc Mobile Devices Communicating Over Bluetooth

Introduction to  A Distributed Mobile Database Implementation On Pocket Pc Mobile Devices Communicating Over Bluetooth Seminar topic:

A distributed database system is formed on self-contained mobile databases organized on mobile gadgets. At the core of the architecture, there are chosen gadgets that act as data directories which gather the outline of the databases and be the connection points for the whole nodes which desire to send queries related to the distributed database. The system is executed on pocket PCs which operate the Microsoft WinCE operating system and converse employing a Bluetooth.

The most fascinating and encouraging type of such surroundings is the mobile adhoc network(MANET) , where a  mobile host can turn as a hub of knowledge, destination or a path finder that transmits data to its destination. The chief objective of this plan and execution is to offer a system by which mobile objects contribute data in disjointed settings.

 The system involves moving nodes that can acquire one of three available parts: requesting nodes(RNs), database nodes(DBNs) and a database directory(DD). A DBN comprises of  mobile database of its own. The outline of the DBNs in the network are reserved in DD. RN acts as a node that transmits its inquiry to the DD for further proceedings.

This paper suggests a distributed mobile database system for execution on Bluetooth-enabled mobile devices. The benefits of this the suggested mechanism include

  • Flexibility: Mobile devices can adapt their proceeding ability to alter to their requirements.
  • Scalability: The suggested system can uphold services that are based upon location with innumerable mobile devices and supervising inquiries protecting the server from additional responsibilities.
  • Reliability: The dependability of the suggested system is highly appreciable as it has always succeeded.

Download Seminar Report on A Distributed Mobile Database Implementation On Pocket Pc Mobile Devices Communicating Over Bluetooth.

Posted on

Hybrid Model For JIT-Oriented Web Service Discovery Project Abstract

Introduction to Hybrid Model For JIT-Oriented Web Service Discovery Project:

In the present situation, the location of a specific web service in a limited time for any user busy in a particular job has become a very challenging task. Web service discovery is a procedure of finding out a machine-process able explanation of a web service that might have been earlier anonymous and which satisfies specific operational measure. Most of the Web Service Discovery procedures have not succeeded to find out the definite services.

The supposed system assists in offering effective web service discovery and refines the unnecessary services, with the help of Just-In-Time (JIT) ideology. JIT offers effective services to consumers on the basis of their context. The final goal of JIT is to remove the insignificant services so that the user receives the significant services. Effectiveness can be strengthened by understanding the context.  The knowledge of the context intents to know the definite services relying on the consumer’s position for the consumer needs to be met to the highest level. By grading the services, refining can be carried out. The recommended structure matches the consumer context to the service context in order to remove the insignificant services.

There are two varied procedures of web service discovery systems-Non-Semantic web service discoverer and Semantic web server discoverer. The services are compared on the basis of keywords in Non-Semantic web service discovery. It is tough for a consumer to get the wished results as number of significant services regained with regard to the keywords might be few and number of significant services might be many. In Semantic web service discovery procedures, every service contains semantic knowledge regarding services and it would be brought on the basis of semantic explanation.

Just-In-Time (JIT) is a building ideology that removes wastage related to time, labor and place for storing. It offers solely the wished services to the users.

Download Hybrid Model For JIT-Oriented Web Service Discovery Project Abstract.

Posted on

Defending Against Sybil Attacks Using Sybil limit Protocol Project Report

Introduction to Defending Against Sybil Attacks Using Sybil limit Protocol Project:

There is always a threat to open-access distributed systems like peer-to-peer systems from Sybil attacks, where a ill-willed user creates many fake identities known as Sybil nodes. Unless a reliable central authority is organized to bond identities to real persons, safeguarding against Sybil attacks is a serious problem. 

Amidst the limited dispersed approaches, our recent SybilGuard protocol uses a key perception on social networks to restrict the number of Sybil nodes acknowledged. In spite of its encouraging efforts, SybilGuard can permit many number of Sybil nodes to be acknowledged. Moreover, SybilGuard believes that social networks are fast-mingling, which has not been accepted in the actual world. 

This project deals with the SybilLimit protocol that uses the similar perception as SybilGuard, but provides a refined and close to reality results. In our trial for a million-node system, the number of Sybil nodes acknowledged is decreased by a factor or about 200 times. When the approaches based on fast-mingling social networks are regarded, SybilLimit’s assurance is at most a log and factor away from maximum. Ultimately, on the basis of three large-scale real-world social networks, the foremost proof that real-world social networks are really fast-mingling has been offered by us. This proves the basic supposition behind SybilLimit’s and SybilGuard’s approach. 

Hardware Requirements: 

The system should have a Pentium IV 2.0GHz or above Processor, a RAM of 1 GB or above, a HDD of 40 GB and above and a Display of 64 x 480(SVGA). It should have Multimedia support, a keyboard and a mouse.

Software Requirements: 

The system needs a platform of Windows 9x/NT/2000/XP, a Frontend ASP.NET and a Backend Microsoft SQL Server.

Download Defending Against Sybil Attacks Using Sybil limit Protocol Project Report.

Posted on

Development of a Repository and Search Engine for Alumni of College Rase

Introduction to Development of a Repository and Search Engine for Alumni of College Rase:

An alumni association refers to an union of graduates (alumni) or former students. The students of  universities, colleges, schools, fraternities and sororities make a group with the alumni from the same institution. Social events are conducted, newsletters or magazines are published to generate funds for the institution.These alumni organizations are chiefly conducted at universities or departments of universities or may be conducted amidst students who studied in a particular country. Previously, alumni associations were regarded as the old boy network  but nowadays they include graduates from any age group and demographics. 

This project’s objective is to create a repository for a college’s alumni which is of great significance to the institution. The Repository and Search Engine(RASE), an Internet based application, can be approached round the globe. This enables the users to access the Search Engine to gain information about the college alumni but they cannot be added. The database can be updated only when the alumni belongs to that institution. 

The project is supposed to be finished in two stages. The first stage would include the development of a simple system which would be employed to gather data from the students of the present final year prior to the end of their term. The second stage would involve the working of the system that would enable the passed out alumni to get registered.

 Hardware Requirements: 

An Intel Pentium IV or later Processor, a RAM of minimum 512 MB, a Secondary storage of 80 GB is required. 

Software Requirements: 

An Operating System Server: Windows XP or later, a Database server : Oracle or MYSQL, a client :Microsoft Internet Explorer, tools and environment: Apache Tomcat 1.6, JDK 1.6, a user interface:Html, Jsp and a code behind: Java, Jdbc, SQL are required.

Download Development of a Repository and Search Engine for Alumni of College Rase.

Posted on

Dynamic Search Algorithm in Unstructured Peer-to-Peer Networks Project Abstract

Introduction to Dynamic Search Algorithm in Unstructured Peer-to-Peer Networks Project:

In unorganized peer-to-peer networks, creating effective search algorithms is a major challenge. Two usual types of search algorithms include flooding and random walk(RW). Flooding conducts an aggressive search that involves utmost nodes. As it produces several query messages, it can’t be scaled. On the other hand, RW conducts a conventional search and produces a limited query messages but consumes a lengthy search time.

Therefore Dynamic Search(DS) algorithm is suggested, which is a  generalized form of Flooding and Random Walk. When it comes to short-term search, DS follows flooding, whereas it follows RW during long-term search. In order to refine the performance of the search, DS unites with the knowledge-based search mechanisms. The performance of DS is calculated by few performance measures such as success rate, search time, query hits, query messages, query efficiency etc. As shown by the outcome, DS offers  a good tradeoff  within performance and price. According to the power-law graphs, DS functions 25 times better than flooding and 58 times better than RW  and as per the bimodal topologies, it functions 186 times better than flooding and 120 times better than RW. 

Dynamic Search algorithm has benefits such as reduced search time and combines both flooding and random walk technique. These algorithms take the benefit from the knowledge gained from the earlier search outcomes and on the basis of the knowledge, they route query messages with various weights. 

Hardware Requirements: 

The hardware requirements include any Processor above 500 MHz, a RAM of 128 Mb, a Hard Disk of 10 Gb, a Compact Disk of 650 Mb, a standard keyboard and  mouse and a VGA and High Resolution Monitor as an output device. 

Software Requirements: 

The software requirements involve Windows Family as an Operating System, JDK1.5 as a Language, Microsoft Sql Server as a Database and Java Swing as Front end.

Download Dynamic Search Algorithm in Unstructured Peer-to-Peer Networks Project Abstract.

Posted on

Text Editor Project in Java

Introduction to Text Editor Project:

For editing plain text files, a program called text editor is used. A plain text file is shown and edited by displaying all the characters the way they are involved in the file. The control characters of the used character set are the sole characters employed for mark-up. In real, it is newline, tab and form feed. ASCII is the most frequently used character set because of more frequent use of plain text files for programming and configuration and less frequent use of them for documentation (for instance, detailed instructions, user guides) as compared with the past. 

Text Editor is software that edits plain text and comprises of Java Swings and AWT. This project has all the frames prepared in Swing. These days, most of the programmers use Swing. Swing offers stronger and manageable GUI components as compared to AWT. Modern Java GUI is represented by Swing. 

Swing was a result of the shortcomings in Java’s original GUI subsystem: the Abstract Window Toolkit. AWT is a fundamental set of controls, windows and dialog boxes that aid a usable but restricted graphical interface. 

Text Editor Features: 

The text editor provides the fundamental features of an editor such as string searching, multiple font colors, various fonts and dock which includes the options most frequently used such as cut, copy paste etc. 

Text Edito System Analysis and Design: 

This phase involves the software development process and its entire structure. This phase also depicts the number of classes required for the package architecture, the database design and the data structure design. After the creation of the software development model, Analysis and Design play a vital role in the entire development cycle. Even a small flaw in the designing stage could prove to be very harmful in the later stages of the development of the software.

Download Text Editor Project in Java.

Posted on

Mobile Agent Based Fault Tolerance System Implementation Procedure in Java

The actual procedure followed to implement the proposed design as mentioned in the previous chapter is explained in this chapter. As mentioned the proposed design is implemented using Java and the all the required screens are designed using the Java swings and the data base is created in Oracle SQL. This chapter summarizes all the important classes and tables used along with the flow of the application are clearly described in this chapter.

Classes used in the application

Every aspect across java programming is an object and these objects can be inherited in the form of class and the objects of the class can be created to initiate the core functionality used across the class. Following are the classes created in this project with respect to initiate the flow of the application. All the classes used across this application are created using the Java swings framework and the flow of the business logic is as listed below

  • AddClient.java
  • Administration.java
  • CommonUtil.java
  • First.java
  • LinkStatusForm.java
  • MasterServer.java
  • MobileAgent.java
  • ReceiveData.java
  • SecondFrame.java
  • SendDataForm.java
  • ServerModule.java
  • UKprogg.java

All the java files are created with an extension of .java and the corresponding logic used across these java files are as given below 

AddClient.java 

Required logic to add the clients to the servers is given in this class. As per the design few clients can be added to the server and the corresponding procedure is coded in this class. Java swing frame work is used to create this logic and all the basic components of the swing class like text fields, layouts and gaps are used to create the basic layout out the of the screen and is as shown in the appendix section. A separate client id is issued to the newly added client and assigned to the desired server and the corresponding logic used here is that the server id is tracked against adding the required client and the newly added client is to the serve and the server is identified with the server id. Once the client is added, a new row is added to the client table and the corresponding query used here is Initially the number of clients are calculated and if this count is as per the defined handled clients for the server, then only the client is added to the desired server else the client is added to the next available server.  Once the required constraints are satisfied the client is added to the client table and the rows are incremented by 1 against the table.  Whenever the client is added to the server and the database is updated, the link status of the server and the client is also updated and set to on the corresponding logic is written.

When the client is added to the server, the corresponding client IP address and the client name are also updated against the database table client. 

Administration.java 

Administration.java class is used to create the user interface for all the administration activities and the coding procedure followed is explained in this section. The key administration tasks used in this project are to start or stop the master server, check the status of the links, start the distribution mode of the network and initiate the mobile agent for detecting the faults across the distributed networks. Administrator can check the status of the links between the clients and the server at any point of time and they are provided an option with respect to this.  A link status form is opened at the user interface and the administrators can view the status of the desired links at this window and even this window is created using the swings. Distributed network option is also available to the administrator and they can initiate the distributed mode of the network.  Admin is provided with an Mobile agent button and the users can click on the button to start the mobile agent, where this agent collects the information related to the distributed network faults and suggests the options for the fault recovery options. The key java code used to create this logic is as given below 
A new object is created in the private methods to initiate the administrator requests and thus the overall functionality of the admin module is coded in this java class.

CommonUtil.java

This class is used to created the frequently used java functions like the database functions and thus if at all a new instance of the database is required an object is created for this class and initiated to dump the complete coding logic in this case.  Following are the important methods used in this class and the corresponding description of the methods are also given below

getConnection

This method is used create the connection to the database and the basic JDBC drivers are used to create the connection to the database using the Connection class across java. Once the connection is established, the corresponding statements and other parameters are initiated. Oracle thin driver is used to create the bridge to the database in this class and the user name and password to access the database are also provided in this method

getServerNameByServerId 

This method can be used to get the server name by providing the server if as the required parameter.  A separate global server is used as the required table and the server information is recorded in this table and thus the information is fetched from the database and the corresponding query used for this process is as given below 
getServerIdByServerName 

This method can be used get the server  name by providing the server name as the required parameter and the value is fetched from the global server database table. Following is the query used to get the required information from the table 

getClientIdByClient_name 

This method can be used to fetch the required client id with the help of client name and the client name is provided as the required parameter to the method.  Below is the query is used to get the required client information with the help of client name 

getClientNameByClientId 

This method can be used to get the client name by providing the client id as the required parameter and this name is fetched from the database table known as client and the actual query is used in this context is as given below 

LinkStatusForm.java 

As mentioned the administrator can check the status of the links from the desired server and the client and the corresponding code is given in this java class. User interface is provided in such a way that the users can select the desired from the dropdown list and also can select the client id from the list and the swing components are used to create this interface.  All the ids of servers and clients are fetched from the corresponding database tables and the required logic is given in this class. Once the users selects these values, these values are given as the input to the query built and this query is fired on the status table to get the current status of the desired server and client and the corresponding coding logic used is as shown below 

Thus the current status of the client and the server can be fetched using this logic and the query as shown above. 

MasterServer.java 

Master server is initiated across this project and the corresponding logic used is given in this java class. From the master server user can start the desired server and in this project two servers are created and named as Server A and Server B and once the user clicks on the desired button, the actual server operations are started. Java swings are used as the required framework and all the key components are added to get the required interface to the application. The actual action performed by user is captured using the action events provided with the swings package and based on the action performed the corresponding server is started and the key coding logic used in this context is as shown below 

From the above code it is clear that if server A is selected the corresponding ID is tracked and the actual server module is started and this procedure is repeated for both the servers as shown in the above code. 

MobileAgent.java 

This is the important class used among all the classes created in this application. Mobile agent is the java class that captures all the link failure information and displays to the administrator and the administrator can set the status to On again using this class and the corresponding functionality used. User is also provided the required suggestion to check the alternative paths across this process and the corresponding functionality is provided in this class. The link status information is fetched from the database and the corresponding logic is used as given below 

 From the above code it is clear that the required information is gathered from the database table link_status and the status values are iterated in a loop using the result set object available with the JDBC package and the fetched values are displayed to the users in a tabular form and required rows are added to this table using this information fetched from the database table.  A vector object is used to store all the values retrieved from the database and the loop is iterated against this loop. 

ReceiveData.java 

As mentioned in the design of this project, clients and servers can receive the data from the any other servers and clients and the required programming logic is given in this java class. All the data received from any other client or server is displayed to the users in the form a table and the required logic is written using the java swings framework and the corresponding components in the swing framework. Database connections are established to gain the access to the information related to all the received data by a particular client or server. A table with name datapackets is created in the database and that particular information is gained from this table and displayed to the users in a tabular form. All the data received is fetched from the table and stored in a vector object and thus a loop is iterated using the JDBC result set object and the corresponding values are displayed to the user and the corresponding screenshot is as shown in the next chapter. The actual coding logic used for this java class is as shown below 

SendDataPage.java 

As mentioned in the design chapter, any client or server can send to the desired client and server and the required programming logic is created in this java file. A window is created across this section and the users can type the desired message to be sent and actual number of packets is also calculated using this logic. A separate text field is created in this class and the client or server can add the required message to the text area and the data entered is sent to the desired client or server and the number of packets sent is also calculated in this class and the corresponding coding done is as given below 

From the above code given it is clear that all the data sent is saved in the database table datapackets  and the inserted text is converted to the desired format and the corresponding client and server information are added as well. A prepared statement is created and the query is inserted to the prepared statement and executed to insert these values in to the database table. 

Following are the database tables used in this application

  • Globalserver
  • Client
  • Link status
  • Data packets 

All the important classes are explained in this chapter and the corresponding code is also provided. The actual results achieved against this implementation are given in the next chapter. 

Posted on

Project Design for Computer Engineering On Fault Tolerance System For Highly Dynamic Distributed Systems

As the main aim of this project is to design and implement a fault tolerance system for highly dynamic distributed systems using an agent based approach, the actual design implemented in developing this application is given in this chapter. A mobile agent based approach is followed to identify the failures across the dynamic distributed networks and a fault tolerant environment is provided across this approach. A detailed explanation to the front end and database design is given as below

Front end design

A virtual dynamic distributed network is created using Java in this project and to create a distributed network two servers and four clients modules are created in this project and these nodes are assumed to be in a distributed nature.  A single server module can handle two clients in this design and thus a total of four clients are managed by the two independent and distributed servers. These two servers are controlled by a master server module, where these two servers are the distributed sample of the single master server. The actual programmatic implementation and design aspects to create these modules are given as below

Master server

Master server is the key component in this process and can maintain the two independent and distributed servers. Master server is represented with a server icon and when this master server icon is clicked by the user; the actual functionality of the application is started. On and Off radio buttons are provided against the master server icon and when the user checks the On button two server modules are invoked and when the user clicks on the Off button, users are asked to choose one of the servers to terminate its operations. Once the On button is clicked, the actual process is started and it is explained in detail as below

Server modules

As it is already mentioned two servers are created and considered as the distributed servers and each server can handle two clients and in future more clients can be added as per the user requirements and this provision is also provided at the design level.  A server module is composed of few aspects and the detailed explanation to the server operations is as given below. A distributed server is represented by the server name like Server A and On and Off radio buttons are provided against the server icon. When the user clicks on the On button, the server operations are initiated and the actual operations are listed below.

Send data

Send data is the primary operation available for both the servers and this option is provided to the user across the server in the form a simple button. Whenever the user clicks on the send data button, a browse window is opened and the user can select the desired file to be sent from the servers. Once the file is selected, the very next operation is to choose the client as each server can handle two or more servers. In general the clients are identified with the client name or IP address. To simplify the concept a unique number is assigned to the clients and this number is assumed to be IP address of the client, as this application is a standalone and no network operations are included to simply the demonstration.

Once the client is selected, send button is clicked against the server icon and then the sending process is initiated and this process is represented graphically till the data is send to the client.  The number of packets transmitted to the client is also displayed to user. Users are provided with an option to check the total number of packets being transmitted before sending the data to the client and also can check the actual number of packets transmitted to the client. User can send the data to any of the clients by choosing the client unique ID as mentioned above and once the data is sends to the client, it is stored in the client database against the server name, number of packets send and the client ID.

Receive data

Servers can receive the data from the clients as well and to achieve this, a separate button is provided to the users against the server icon. Once this button is clicked server can select the desired client from where the data should be received and once selected the corresponding data is stored across the server database table.  Total number of packets received can also be calculated across this module.

Link status

Link status from the server to the client and client to server can be checked using module. Status of the link can be checked by clicking on a button before sending or receiving data and if the status is On, then the sending or receiving is done successfully and if the status if Off, the corresponding process are terminated.  Users can check the status of the link at any point of time and if anything goes wrong across the modules, the link status is automatically set to Off and this indicates that there are some failures across the distributed networks and these failures are detected in this project and an alternative fault tolerance system is developed to set the link status again On for a continuous communication mechanism.

Add clients

Users can add more clients with the help of the button available against the server icon and whenever a client is added to the network a unique ID is provided to the client and it can be accessed through the ID.  Once the client is added, a separate row is created in the database table and the client details are maintained in the table and sever can send data or receive data from the client added. When the Add client button is clicked by the user, they are provided with an option to choose the desired server to which the clients should be added. 

This paper is written and submitted by sai

Posted on

Distributed Networks Project abstract on Mobile Agent Based Fault Tolerance System

Distributed networking is widely used these days and apart from the list of advantages provided with the distributed networks, there are few limitations across these networks and the key among them are faults that occur frequently across the networks.

Among these faults link failures and switching the mode of distributed networking are important to be considered and there are many fault recovery techniques across the literature and most of them are static in nature and can’t detect the dynamic link failures across the network.

The main aim of this project is to evaluate the role of mobile agent based fault tolerance system for the distributed networks and to make this proposed application, a simple java based application is used. Swings framework is used to create the user interface and Oracle SQL is used as the database to handle the tables.

Two servers and a master server are created and each server can handle two clients and the faults like link failures and distributed network off are inserted in this project and from the results it is clear that the mobile agent can handle the dynamic link failures and improve the overall performance of the distributed network.

This paper is written and submitted by sai