Repository and Search Engine for Alumni of College (RASE)
Introduction:
This project is aimed at developing a repository for the alumni of
the college, which is of importance to a college. The Repository
and Search Engine (RASE) is an Internet based application that
can be accessed throughout the World. Any one can access the
search Engine to know about any Alumni of that college but can’t
able to add. Alumni can only update the database when they are in
the college.
Functional components of the project:
Following is a list of functionalities of the system. More
functionality that you find appropriate can be added to this list.
And, in places where the description of functionality is not
adequate, you can make appropriate assumptions and proceed.
1. A person should be able to
Click on a button or link to be taken to the specific application.
The first page of the application should provide the user
(student only) with the options of saving his/her details in the
database and searching for alumni.
2. The page through which the student enter his/her details should
allow saving of user details like name, year of passing, roll
number, contact number, present address, permanent address, etc.
This page will be having 2 buttons Save and Cancel.
3. The save page should have proper validation before allowing
the user to save user details into the database.
4. The cancel button should take the user back to the home page
(first page).
5. The search page should allow search on the basis of name of the
user or roll number. Partial search should be allowed.
The search application has 3 main functions
1. Search
2. Analyze data
3. Store data
The following functional requirements are taken from the
requirements specification document created for the search
application.
Functional Requirements
The search application divides into 3 main functions that
decompose further into smaller functions (see functional
decomposition):
1. Search
The search application must allow the end user to search the search domain
based on keywords. Searching is aided by additional sub-functions; the
search function decomposes as follows:
Incorporate meta data
The search application’s search function must use the data stored about
searches to help the end-user search for information. This function
decomposes into three processing tasks:
Extract data from database
Data about previous searches, commonly used keywords and categories to
find information on topics with the search domain must be extracted from
the database storing all search data.
Suggest Keywords
Using the data from the search database, the search application must suggest
keywords based on frequency and new information topics.
Suggest Categories
After the end user has entered a keyword and the search application returns
search engine results, the search application must be able to suggest similar
categories of web sites.
Initial Search
This is the function of being able to process the end user inputted keyword.
This process decomposes into two processing tasks:
Process User’s Input
The inputting of the end user’s keyword and running a search to find
matches in the search engine listings.
Output results
Outputting search engine listing matches and incorporating Meta data from
processes
View Database
This function is for the research purposes. The search application must be
able to allow end users to study the search database for analysis.
Search database to find Relevant data
The search application must allow end users to search the database results
and statistic graphs for research analysis (e.g. to draw conclusions from,
view correlations and patterns).
Output results
The search application must output the results of the above process.
2. Analyze Data
The search application must first analyse search and listings data before it
can be stored in the search database. There are two processes for different
cases where search data must be analysed:
Update Database
After a listing has been created the search engine may find additional listing
data for a web site after updates have been made to the it. Therefore the
search application must update existing listings and the existing listings data
in the database.
Process search data for database
After a new web site has just been spidered, it has to be analysed, filtered
before be added to the database.
3. Store Search Data
Data from search listing must be stored in a database that can later be
manipulated for research and statistical information:
Store Search data in database
Data from listings after being analysed must be made persistent in a database
that can be used and expressed for statistical use (graphs).
Generate Statistical data
When web listings are stored in the search database the search application
must update existing statistical data it has generated. The software must also
allow for the generation of statistics according to user criteria.
Technologies Used
Language : Java, JDBC, JSP
Backend : MySQL
IDE : Eclipse IDE
Database Setup
Step-1 :- Creating Database
Create Database rase;
Step-2 :- Creating Tables
Table_Name :- alulog;
Create table alulog(username varchar(20), password varchar(20));
Table_Name :- reginfo
Create table reginfo(name varchar(20), rollno
varchar(10),branch varchar(10), yop varchar(10), address
varchar(200), eid varchar(30),
Prestart varchar(30), comp varchar(200), cont varchar(12),
sal integer, infor varchar(500), addr varchar(100);
Table_Name :- Events
Create table events(type varchar(30), name varchar(20), location varchar(20), edate
varchar(50), etime varchar(30), desc varchar(500));