Sequencing Framework for SCORM Content 

 

Problem Definition 

            The purpose of this Sequencing Framework for SCORM Content  project is to develop a framework for sequencing SCORM content obtained from multiple existing courses. The author uses the pick and chooses capability to do the same.

Technology Used

•  Java, XML

Platform Used 

•   Windows

Software and Hardware Requirements 

•     OS Windows
•     Microsoft VC++ 6.0 package
•     Sound and LAN card drivers
•     Minimum 200MHz Pentium PC
•     64 MB RAM

 

Project Description 

            The aim of our Sequencing Framework for SCORM Content project is to design a SCORM compliant framework in order to structure and sequence the course content obtained from a pre-existing content generator or from existing multiple courses and provide it to an existing LMS to create a customized course.            

Sequencing Framework Working 

            Every course has an imsmanifest.xml file at its root which describes the organization, metadata and the resources, which in turn describe the various assets and their hierarchical arrangement in the package. In order to create a new course we have to either alter the existing course structure (in case of a single course) or create an altogether new course structure by pick and choose ability. The GUI enables the author to open content from various courses and display it as a Jtree, which can be then manipulated with using the Java Drag and Drop API. The Jtree is internally saved as a DOM tree, which helps in treating the XML elements as objects. The changes being made are actually being mapped to this DOM tree. Now this DOM tree is again converted to XML and saved at the root of the new package.

Implementation of Project

            The algorithm followed by us for the implementation of the project can be described with the help of the following modules:

XML to Jtree

 In this module, the XML document is represented as a JTree which is the JAVA equivalent of the Tree model. It represents the XML file as a collapsible tree structure.

XML to DOM

In this module every element of the XML file is treated as an object in the memory which can be subjected to manipulation using various functions provided. The manipulations thus made can be saved to create an altogether new document structure.

Manipulation of the JTree using Drag and drop API

The Drag and Drop API of Java is used to allow the author to pick and choose the course content and drop it in the area for the new course. This API provides the necessary classes and interfaces to implement the same

Mapping the manipulations to the DOM tree

The manipulations are directly made to the JTree, which have to be mapped to the DOM tree, so that actual changes take place in the objects of the DOM tree. Here we use the class DOMTreeFull to do the same.

DOM to XML

Finally the new DOM tree is again converted into XML. This document is then saved at the root of the new course package.

Download Sequencing Framework for SCORM Content 

Download Project Here

Mail Server Final Year Project Idea

Our Mail Server Final Year Project aims at building a mail server application which includes a client and a server. The basic requirement is to let the application work on the client and the server side. The client i.e. the user is given the functionalities to send, receive and forward mails. The server i.e. the administrator maintains information about the total number of users, the space allocated to each user and various privileges provided to them. The administrator also maintains the user profiles. The sending and receiving of mails is implemented using the SMTP and POP3 protocol respectively. We intend to implement the following functionality:-

• Authentication.
• Address Book
• Compose
• Attach File
• Reply
• Forward
• Receive/View
• Change Password
• Profile

Technology Used

•  Java Platform

Platform Used 

•   Windows XP

 

Software and Hardware Requirements 

•  Java 2 SDK
• Tomcat Web Server
• Jakarta-tomcat 4.1.31
• Oracle
• Microsoft Windows NT 4.0, 2000 or higher on Intel hardware.
• Pentium II or higher processor
•  Minimum 128 MB RAM (256 MB RAM recommended).

Project Description 

            Our Mail Server Final Year Project aims at building a mail server application which includes a client and a server. The basic requirement is to let the application work on the client and the server side. The client i.e. the user is given the functionalities to send, receive and forward mails. The server i.e. the administrator maintains information about the total number of users, the space allocated to each user and various privileges provided to them. The administrator also maintains the user profiles. The sending and receiving of mails is implemented using the SMTP and PO9P3 protocol respectively.

            The project is divided into 2 parts – Programs that run on the Client machine and Server machine(administrator). The roles of the programs are as follows:

• Client Programs :

The various functionalities implemented at the client side are:

• Authentication.
• Address Book
• Compose
• Attach File
• Reply
• Forward
• Receive/View
• Change Password
• Profile

 

• Server Programs:

                The various functionalities implemented at server side are:

• User information
• User profiles
• Blocked users
• Privileges given to the user
• Memory assigned to the users

Working Mail Server

             There will be three modes of operation of the Mail Server Final Year Project: the system operator(administrator), the Database manager and the user. The user has the capability to register for the e-services. In turn, the user can have an access to his account details and have the ability to make changes to his settings. He is having access to various services provided by Mail Service program. The database manager has all the authority to make changes in the database. Finally the System Operator has to interact with the system in order to implement various functionalities. The mails are sent and received using SMTP and POP3 protocols. The user is the client and the administrator is the server.

            We have used JSP to implement our project as its Platform independent, robust, object oriented.

Mail Server Implementation 

              The client and the server machines are connected over the LAN (Local area Network).There exists a GUI on the client machine which has been made using JSP.

The client i.e. the user is given the functionalities to send, receive and forward mails. The server i.e. the administrator maintains information about the total number of users, the space allocated to each user and various privileges provided to them. The administrator also maintains the user profiles. We have used Apache Tomcat Server as it is open source. The sending and receiving of mails is implemented using the SMTP and POP3 protocol respectively.

     These modules have been written in Java language. Each module is responsible making the appropriate setting & initialization to execute the particular functionality. We have implemented the following functionalities:-

1. Authentication– This checks whether the entered username & password is valid or not.

2. Address Book – Here you can add the address of your friends or other persons.

3. Compose – By this you can write mail and also append or attach other documents.

4. Attach File – User can also attach files with the mail before sending.

5. Reply – A user can directly reply to the person whose mail is being read.

6. Forward – A user can forward a message along with his own additional mail and   attachments to one or more persons

7. Receive/View – This shows your inbox and you can read any mail that you have received from here.

8. Change Password – A valid user can change his login password from here.

9. Profile – The user can change his details from here.

10. User information

11. User profiles

12. Blocked user

13. Privileges given to the user

14. Memory assigned to the users

Download Project Abstract 

Download Mail Server

E-Learning Management System

 

Problem Definition 

            “e-Learning Management System” is a web based Learning Management System that helps students to    interactively learn a new course, allow course experts to publish new courses on different  subjects, allow evaluators to evaluate the students on any available course and  management to obtain various type of reports.

Technology Used

• Java
• JSP
• Oracle 8i

Platform 

• Windows XP

Software and Hardware Requirements

• JSDK1.5
• WebSphere Application Developer(WSAD)
• Tomcat 4.1
• Oracle 8i
• Ethernet Adapter
• 512 MB Ram

Project Description 

            The purpose of this E-Learning Management System project is to develop a back-end application for e-learning applications and queries using graphical user interface. It allows for flexible data format and deliver of its data so that each analysis application can receive only the information it needs and in the format required.

            The project is divided into 3 modules – student, course expert and administrator. The roles of the modules are as follows:

• Student : The student selects from various courses available.The student takes a test on a course. There might be courses, which has only test modules. Each question has multiple choices with only one correct answer. The test will be time bound. Student can see the test schedule. New Users will be able to register themselves in the system as students. All students will be able to modify their own profile. Student views previous test reports, receives feedback for a test taken Student can go to the discussion board and browse through questions and answers and discussing solutions of questions asked in test. Student can chat with course expert. Student can also send messages to the course expert.

• Course Expert : Creating test questions for the course, test questions will reside in the Draft area if either it is saved while creating/modifying or it has been rejected by admin. Modifying test questions, deleting the entire test, browse through the tests that students have submitted, just as a student would., view the results of those students that have taken test for his courses. Replying back to the messages from students.

• Administrator: Publish tests submitted by Course Experts. Before publishing test questions it is customary to get it reviewed by admin. After going through its content either it gets approved or gets rejected. Modify the profile of other users registered in the system. Change user status from inactive to active.

Working of E-Learning Management System

 A student has to register his profile for a course, by authentication and authorization and chat with others. A student can join discussion forums, send mail to instructor(s) of the course and provide feedback about the test given. A student can view test schedule, take test to assess his knowledge,view test report and edit his/her profile.

A course expert creates a test for the course, test questions will reside in the Draft area if either it is saved while creating/modifying or it has been rejected by admin. Modifying test questions, deleting the entire test, browse through the tests that students have submitted, just as a student would., view the results of those students that have taken test for his courses. Replying back to the messages from students.

 Publish tests submitted by Course Experts. Before publishing test questions it is             customary to get it reviewed by admin. After going through its content either it gets approved or gets rejected. Modify the profile of other users registered in the system. Change user status from inactive to active

Implementation of Project

Java script is a scripting language used to enhance the functionality of the browser. Java script is integrated with HTML and navigator 2.02. Java script facilitates the developer with properties related to document windows, frames, loaded documents and link. The J2EE platform specifies the logical application components within a system and defines the role played in the development process.

The J2EE platform uses a distributed multitiered application model for enterprise applications.

Java Server Pages (JSP) is a technology based on the Java language and enables the development of dynamic web sites. JSP was developed by Sun Microsystems to allow server side development. JSP files are HTML files with special Tags containing Java source code that provide the dynamic content.

Tomcat started off as a servlet specification implementation by James Duncan Davidson who worked as a software architect at Sun. He later helped in making the project open-source and in its donation by Sun to the Apache Software Foundation.

Oracle is a trade mark of Oracle Corporation and in common usage refers to the database engine (which actually looks for the data) and the range of front end products. Oracle 8i is the largest selling SQL-based RDBMS and a most commercially useful product.

Download Project

E-Learning Management System

Detection of Virus Patterns in Emails 

Description of Problem Statement

The detection of unknown viruses is beyond the capability of many existing virus detection approaches. The objective of the project is to develop a prototype system, that will detect the virus which spread via email which have no signatures i.e new and lethal to today’s internet community by using proactive customization of system behaviors at email server. This project also aims to find the signature of the newly found virus (virus having no signature) to help curb the spread of virus at its juvenile phase.

Scope of Definition

The damage caused by computer viruses is more serious than ever in today’s society,

where personal communication, corporate business, and social infrastructures heavily depend on computer networks.

Unfortunately, email attachments have become a popular method of spreading malicious codes over the network. It has lead to the rise of anti-virus industry and it is now almost obligatory for us to have anti-virus programs on personal computers and/or email servers. Yet we keep hearing reports on new viruses and warnings that we have to update pattern files to avoid infection and further spread.

The main reason is that current anti-virus programs rely on byte-to-byte comparison between files, where binary strings taken from previously captured viruses are used as unique signatures. Since a file is recognized as a virus only if it contains matching signatures in the pattern file, it is impossible to detect previously unknown viruses.

This project aims to tackle the problem by running suspicious programs in a virtual isolated & monitored computer environment. The monitored resources in the environment are those which are common to virus for spreading itself (like address book etc). This project further go ahead to extract the signature of newly found virus to help the internet community to curb it.

 Architecture Of Our Proposed Solution

Detection of Virus Patterns Implementation 

The prototype prevents e-mail containing new and unknown outbreak viruses from  spreading to unsuspecting users, working with  SMTP-based e-mail server to:

• Intercept e-mail at the network edge.
• Execute and monitor the e-mail in a secure, virtual environment, and
• Quarantine any e-mail exhibiting malicious behavior before delivery to the target user.

 The above mentioned steps are implemented as follows:

 Stage 1:

             When the email with attachments arrives at the e-mail server it is delivered to the mail content filtering tool which extracts the attachments and transports it to the virtual machine.

Stage 2:

            The attachment is executed & monitored in the secure isolated environment of virtual machine running on the same host. The malicious activities is intercepted by hooking the various resources that virus may infect or use to spread it effect.

Stage 3:

Once the malicious activity is detected in the virtual machine it is reported back to the mail server which then quarantines the e-mail containing the concerned attachment and than tries to extract signature for the scanner antivirus so next time it can be caught without having need to check its behavior.

Key benefits are as follows

•  Executes e-mail and attachments in a virtual environment at the network edge, before reaching the target user.
•  Observes the attempted behavior of suspect e-mail to determine its intent
• Quarantines e-mail demonstrating suspicious or malicious behavior
•  Enables quarantined e-mails to be analyzed and cleaned by an administrator for future delivery.

 Hardware Requirement

Linux 9 with a minimum configuration as follows

• Processor         : P IV 1.5 GHz 
• RAM               : 256 MB
• Hard disk        : 40 GB
• Monitor           : 14 inch SVGA color
• Peripherals       : Mouse, 101 key board, 3.5 inch floppy drive, 32X  CD-ROM drive.
• Utilities           :  SMTP.

Workstations with a minimum configuration as follows 

• Processor         : P III – 800 MHz or equivalent
• RAM               : 128 MB 
• Hard disk        : 10 GB
• Monitor           : 14 inch SVGA color
• Peripherals       : Mouse, 101 key board

 Software Requirement                       

1. Linux (9 or above ) , Windows  X P.
2. VMware.

 

.

Web Service for Multiple clients Project

Web Service for Multiple clients Definition 

To create a  web service that can be consumed by multiple clients. The clients will be such that they will be able to adapt themselves if there is any incremental change in the server database or the data format resulting in change in WSDL. The web service generator may provide a special service that provides the delta corresponding to incremental change

Software Requirements

• J2EE application server.
• XML.
• WSDL.
• HTML.
• JFrame.

Hardware Requirements:

A minimum configuration PC supporting Windows platform and supports web service. It should support J2EE application server.

Technology Used: Web services

Project Descriptions

To create a  Web Service for Multiple clients. The clients will be such that they will be able to adapt themselves if there is any incremental change in the web server database or the data format. The data exchange process between client and server will have the following features –

• Client and the server will connect to each through WSDL which will act as an end point to both client and the server.
• Data transaction will be in XML.
• Generally HTTP is used as an underlying protocol to exchange data.
• In case there is some change in the database format or the any other change in the data, as soon as the client comes to know about the change it tries to adapt itself according to the changes done.

Procedure

• Client sends a query to the server according to the pre-defined contract (WSDL).
• The server sends the output. If the output is in accordance with the previous contract the client consumes the data sent by the server.
• If the data sent is not in the format specified by the contract, the client is not able to consume the data in its original form.
• The client then checks for the changes in the previous contract.
• If there are some changes it upgrades itself according to the new changes.

For e.g. If according to the previous contract the output is O. According to the new contract if the output is O+DELTA O, then the corresponding change in the output is DELTA O.

Now the new contract will exist between the client and the server where the output will be O+DELTA O. This will be the new contract between the two and this output will be the new O for the system.

This procedure will continue for all subsequent changes in the contract.

Linux Package Manager Project Idea

 

Our goal is to introduce a Linux Package Manager Project for Source Code Installation in Linux distributions. This Package Manager would itself take care of maintenance of complete system, which so far has been a very cumbersome job for any administrator. This Linux Package Manager Project along with a Registry would provide an alternative back-end for various text configuration files.

Thus, instead of each application having its own text-configuration files, our Linux Package Manager Project application provides a universal, hierarchical, fast & consistent namespace & infrastructure to access configuration parameters through a key-value pair mechanism.

This would include creation of separate entities:-

• A local database for local machine administration & maintenance.
• A registry for local as well as remote administration of the machine configuration.

Architecture

• I386 Architecture Machines
• Red Hat Linux 9.0 Operating System.

Project Requirements

 The Linux Package Manager Project has some hardware & software requirements that are described as follows:-

 Software Requirements

• Red Hat Linux 9.0 with kernel(2.4.23)
• Linux GUI builder package – QT
• A C/C++ IDE for Linux –  Anjuta
• Elektra API’s

Hardware Requirements

• Two PC’s with usual configurations (128/256RAM P4 Processors etc.)
• LAN connection b/w the machines.

The Problem

It has been long desired to have some kind of Linux Package Manager Project in existing Linux environment. Due to the pre-existing feature of being Open Source, any package can be installed & used, almost anywhere in a Linux system (be it Personal/Server configuration).

Today’s GNU/Linux systems are a sum of independent components collected from Open Source Community. Each of them already has a working, but selfish configuration system.

A Basic Scenario

One of the Linux Package Manager Project system (maintained by an administrator X) has an Apache package (say version 1.4) installed from source (instead of RPM distribution).After some time a new administrator (say Y) starts maintaining that system. Suppose he comes to know that Apache (version 1.4) has a serious security flaw and he installs a newer version (2.0). Now to clean the system more efficiently he has to effectively delete all the files (main files as well as support files) from various locations which become a very tedious task itself.

Thus we realize that the overall maintenance of complete Linux system is a highly cumbersome process which any administrator has difficulty in carrying out, both efficiently & effectively.

How the problem has been attacked

Now that the problem at hand is very much clear, the next & foremost step is as to how the information about various packages, getting installed on the system, needs to be track down & stored. One of the most important design issues that needs utmost attention is:-

• The existing system should not change. It means that we cannot go about changing the entire installation methodology, just for the sake of obtaining the desired information. The reason is if the existing system changes, there is a high probability that the newer system is not at all welcomed by the existing developer & user society.

Thus after considering various other issues, the solution that has been finalized is as follows:-

• We need to trap the information when & where it is getting created & moved into the existing system.
• This information then has to be stored & later on retrieved in an efficient & effective way that would suite our project requirements.

Thus the complete project now gets divided into 4 different stages. They are:-

1. Collection of all the data.
2. Extraction of Information.
3. Efficient storage of the information.
4. Effective retrieval of this information.

Architectural Design