Hello Logout


Development of a Repository and Search Engine for Alumni of College (RASE)


Title of the project

Development of a Repository and Search Engine for Alumni of College (RASE)

Abstract of the project

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.


Generic Technology keywords

Databases, Connection, Web Server, Programming

Specific Technology keywords

MS-SQL server, Java, Advanced Java, Java AWT,JSP

Project type keywords

Analysis, Design, Implementation, Testing, User Interface

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.

Steps to start-off the project

There are a couple of alternatives to implement such a system.

A.    Core java, Advanced Java and backend as MS Access / SQL Server.

B.     Web Based using JSP and backend is kept the same. The Web Server used can be Apache Tomcat.

The following steps will be helpful to start off the project.

1.      Study and be comfortable with technologies such as

a.       Java and Advanced Java Concepts and SQL server.

b.      JSP’s and Web Server Technology, etc.

Some links to these technologies are given in the ‘Guidelines and References’ section of this document

2.      Decide on the validation to be done on the front end save page i.e., the format of date to be entered and the roll number format, etc.

3.      Make a database for storing the student details.

4.      Create the help-pages of the system in the form of Q&A or FAQ (Frequently Asked Questions). This will help you also when implementing the system.


Hardware requirements



Alternatives (If available)


PC with 2 GB hard-disk and 256 MB RAM





Software requirements



Alternatives (If available)


Windows 95/98/XP with MS-office

Not Applicable


MS-SQL server



Apache Tomcat Server

Not Applicable

Manpower requirements

3 to 4 students can complete this in 2 – 3 months if they work fulltime on it.

Milestones and Timelines


Milestone Name

Milestone Description





Week no. 

from the start

of the project





Requirements Specification

Complete specification of the system (with appropriate assumptions). A document detailing the same should be written and a presentation on that be made.


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


Technology familiarization

Understanding of the technology needed to implement the project.


The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective.


Database creation

A database having a table to add the student details should be created.


It is important to finalize on the database at this stage itself so that development and testing can proceed with the actual database itself.


High-level and Detailed  Design

Listing down all possible scenarios cancellation, and then coming up with flow-charts or pseudo code to handle the scenario.


The scenarios should map to the requirement specification (ie, for each requirement that is specified, a corresponding scenario should be there).


Implementation of the front-end of the system

Implementation of the various screens to be added.


During this milestone period, it would be a good idea for the team (or one person from 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

The front-end developed in the earlier milestone will now be able to update the student database. In short, the system should be ready for integration testing.




Integration Testing

The system should be thoroughly tested by running all the testcases written for the system (from milestone 5).


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 (or appropriate reasons given for not fulfilling the same)


Guidelines and References


http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnasp/html/asptutorial.asp (ASP tutorial)


http://www.functionx.com/sqlserver/ (SQL-server tutorial)


http://jakarta.apache.org/tomcat/tomcat-5.0-doc/index.html (Documentation on Tomcat 5.0)

http://www.jsptut.com/  (for JSP tutorial)


http://www.cise.ufl.edu/~jhammer/classes/Oracle/Intro_JDBC.htm(for JDBC tutorial)


http://jakarta.apache.org/tomcat/tomcat-5.0-doc/building.html (Documentation on Building Tomcat 5.0) 

Tags :
Your rating: None