0% found this document useful (0 votes)

787 views30 pages

Web-Based Student Registration System

Q: Examine how the use of Remote Method Invocation (RMI) and JDBC technologies contributes to the system's performance and usability.

The use of Remote Method Invocation (RMI) and JDBC technologies significantly enhances the performance and usability of the student registration system. RMI allows for distributed applications that are platform-independent and enables the invocation of methods across a network as if they were local calls, thus providing flexibility and scalability in the system's architecture . JDBC, on the other hand, facilitates the connection to and interaction with databases, enabling seamless retrieval and update of student records. This integration allows for real-time processing and immediate reflection of changes, thereby improving the system's efficiency and user experience by allowing multiple logins and data accessibility from anywhere globally .

Q: Analyze the benefits and potential pitfalls of having the admin module cancel student accounts if irregularities are detected.

The admin module's capability to cancel student accounts if irregularities are detected offers several benefits and challenges. On the positive side, this approach enhances the system's security and integrity by ensuring only genuine applications progress through the registration process, reducing the risk of fraudulent enrollments . However, the potential pitfalls include the possibility of false positives where legitimate student accounts could be incorrectly flagged and cancelled, leading to administrative challenges and possibly legal repercussions. It also places a significant burden on administrators to accurately identify irregularities, which could require complex algorithms and a robust human oversight system to balance efficiency and fairness .

Q: How might the dual accessibility of the system (client-side by students and server-side by university) impact its operational efficiency and security?

The dual accessibility of the system—client-side for students and server-side for the university—can significantly enhance operational efficiency and security. This architecture allows students to access and manage their registration process conveniently over the internet, making the system user-friendly and accessible from remote locations . For the university, restricting server-side access to the intranet enhances security by limiting external access to sensitive data and operations, thus protecting the system from unauthorized interventions and potential cyber threats . This separation ensures that while users benefit from broad accessibility, core system operations remain secure and manageable, reducing the risk of data breaches and enhancing overall system reliability.

Q: Discuss how the system's merit list publication process impacts student decision-making during admissions.

The automated publication of the merit list in the proposed registration system speeds up the decision-making process during admissions. By quickly normalizing test results and releasing merit lists, the system provides prospective students with timely results on their admission status, allowing them to make informed decisions regarding their acceptance of offers . This immediacy helps in reducing the stress and uncertainty associated with lengthy admission processes and minimizes the waiting period for students, which can be crucial in competitive and time-sensitive admission cycles . The efficient dissemination of this critical information ensures that students can proceed with subsequent plans such as securing accommodations or applying to multiple institutions as needed.

Q: Analyze the potential impacts of using Internet banking for the first fee payment on student experience.

Utilizing Internet banking for the initial fee payment in the student registration system can substantially enhance the student experience by offering a convenient and secure method of transaction. Students can complete payments from anywhere, eliminating the need for physical presence or manual transactions, which can be time-consuming and prone to errors . This method also benefits the university through streamlined payment processing, immediate transaction confirmations, and reduced cash handling risks. However, potential challenges include ensuring robust cybersecurity measures to protect sensitive financial information and providing support for students without access to suitable banking facilities . These considerations are crucial to prevent data breaches and to ensure all students can utilize this payment method.

Q: How does the integration of a testing module streamline the student admission process?

The integration of a testing module streamlines the student admission process by automating the scheduling, execution, and evaluation of admission tests. After prospective students successfully upload and validate their necessary documents, they can conveniently schedule their tests through the online portal. The tests are conducted either on the university premises or at regional centers and require user authentication, ensuring secure and controlled testing conditions. The results are normalized, and scores are published immediately, allowing for prompt decision-making and publication of merit lists . This automation reduces manual workload, minimizes errors, improves response time, and enhances the overall efficiency of the admission process .

Q: Evaluate the advantages of having a centralized system for uploading and validating student documents compared to the prior system of manual submissions.

The centralized system for uploading and validating student documents offers considerable advantages over manual submissions. Firstly, it significantly reduces paperwork by digitizing the document flow, which decreases the likelihood of lost or misplaced documents and reduces storage needs . Additionally, automated validation of documents can drastically cut down on processing time and human resource requirements, allowing for a more streamlined operation . Furthermore, prospective students can submit their documents from anywhere, increasing accessibility and convenience, which are especially beneficial for international applicants. Meanwhile, potential challenges include ensuring document upload security and maintaining efficient support systems for any technical difficulties users might face .

Q: How does the proposed student registration system enhance security compared to the existing system?

The proposed student registration system enhances security by requiring prospective students to create a user account at the administration block of the university, which is the only part of the system that mandates face-to-face interaction. This step is intended as a security measure to prevent the creation of false user IDs. This is a contrast to the existing system, where there might not be such stringent security checks built into the registration process. Once a nationally approved photo ID is verified, a user account is created, and a scanned copy of the ID proof is uploaded. This step ensures that only verified individuals can proceed with the registration process .

Q: What are the technological components required to implement the proposed student registration system?

The proposed student registration system requires software and hardware components for its implementation. The software includes Windows XP, Apache Tomcat Web Server, Oracle, Java, and J2EE. On the hardware side, the requirements are a hard disk with 2 GB storage, 1 GB RAM, a dual-core processor or above, a mouse, a keyboard, and a monitor. These components ensure the system's basic operational functionality .

Q: What role does user interaction play in ensuring the integrity and security of the student registration system?

User interaction is crucial in ensuring the integrity and security of the student registration system. By necessitating in-person creation of user accounts at the university's administration block, the system minimizes the risk of fraudulent registrations, ensuring that only individuals with verified nationally approved photo IDs can create accounts . This step incorporates human oversight into the system, adding a layer of verification that automated processes alone might miss. Additionally, such interactions provide opportunities for prospective students to address any issues or questions before proceeding, further enhancing the system's reliability and user trust .

This document describes a proposed student registration system that would automate the student registration process for a university. The system would allow prospective students to create an account, upload documents, schedule tests, view merit lists and admission offers, accept admission offers, pay fees, and complete the registration process to become a registered student. It would eliminate paper-based processes and reduce processing times. The system would be web-based with a client-side interface for students and a server-side interface restricted to the university intranet. It includes modules for administration, prospective students, testing, and new student registration.

Uploaded by

siva_438241764

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

787 views30 pages

Web-Based Student Registration System

Uploaded by

siva_438241764

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

Existing System
Abstract
Proposed System
Requirements
Modules
Output
Client Login Source Code
Client Main Page Source Code
Server Source Code
Server Interface Source Code
Student Registration System Project in Java

Student Registration System

ABSTRACT
The aim of this project is to build a student registration system that will completely
automate the process of new student registration in a university. The system will handle the
document submission, testing process and registration of new students.
The system will be web based and will have two implementations i.e. client side
(student) and server side (university). The server side implementation can only be accessed
over the university intranet while the client side can be accessed over the internet.
The process begins when prospective students wish to enrol in the university. If they
express interest in any course they will be required to visit the university and can create a user
account at the administration block. This is the only part of the system where every user has to
have human interaction, this is intended as a security measure to prevent the creation of false
user IDs. After verification of any nationally approved photo ID proof a user account will be
created and a scanned copy of the ID proof will be uploaded into the profile. After this the user
can upload all necessary documents on the portal from the convenience of their home. The
system will automatically validate all the documents and the prospective student will be able to
schedule a test date after successful validation. The test will be conducted on the premises of
the university or at regional test centres and will require the authentication of user credentials.
The test results will be normalised and a score will be immediately published. After the
completion of all tests the system will automatically publish a merit list to indicate which
students have gained admission.
Students will be able to accept or decline offers of admission using this portal. After
accepting admission the documents uploaded will be scrutinized by university authorities and
any discrepancies notified. After all error flags are cleared the student will be able to make the
first fee payment via internet banking through the system, following which the system will
assign the student a unique roll number and register them as a student of the university. This
system will automatically update the new student details into the university student database.

Existing System
The existing system of registration requires many documents and application forms to
be filled out. Data has to be repeatedly entered at each stage of the process and multiple files
are made for each student. Documents are verified with multiple copies made for record and
the testing process is conducted independently which again compounds the paperwork
required. The amount of data processing required for each stage of the process ensures that
the process of new student admission takes a long time.

Proposed System
The proposed system will eliminate the paper trail required for the completion of
various formalities. The entire process of prospective student registration till new student
registration can be handled by this system. The testing process can be done entirely on the
system and results can be quickly judged and shared. The presence of this system will remove
ambiguity in the process that can confuse tense prospective students.

Modules
Admin: The admin will be able to create prospective student profiles after verification of
nationally approved photo IDs of the user. The admin will be able to cancel student accounts if
irregularities are detected.
Prospect: The prospective student will use this module to upload documents and schedule test
dates. The rank list can also be accessed through this module.
Testing: The testing module can be used by the student during the testing phase. A total score
will be displayed at the end of the test and results will be stored centrally.
New registration: Once a prospective student achieves an acceptable rank and accepts the
offer of admission they will be shifted to the new registration module and allotted a unique roll
number. The admin will scrutinize the documents of users in the new registration module and
notify them about discrepancies. The new student will be able to pay initial fees through this
module and will be notified about the next process through this module. This module will
automatically update the student database with the details of the new student.

Software Requirements
 Windows XP
 Apache Tomcat Web Server
 Oracle

Technology Used
 Java
 J2EE

Hardware Requirements
 Hard Disk – 2 GB
 RAM – 1 GB
 Processor – Dual Core or Above
 Mouse
 Keyboard
 Monitor
 Printer
OUTPUT
This software project is just a part of Student Management System. The software is used by the
students to register their courses in the semester through Internet and/or LAN. Remote Method
Invocation (RMI) and JDBC technologies are involved here. It supports multiple login and
registration status anytime and from ANY part of the WORLD.

Compile :
From the folder ‘server’, double click on ‘[Link]’ file to run.

Run :
Server Side:

1. From the folder ‘server’ open ‘[Link]’ file using Notpad or any other editor.
2. Change the path as required in the first line:
set PATH=D:\jdk\bin

3. Save and exit from the editor.

4. Double click on ‘[Link]’ file to run.

Client Side:

1. From the folder ‘client’ open ‘[Link]’ file using Notpad or any other editor.
2. Change the path as required in the first line:
set PATH=D:\jdk\bin

3. Change the second line:

java ClientLogin [Link]

replace the [Link] with the server IP. Say:

java ClientLogin [Link]

or if you want to test it locally in the same machine leave it as it is.

4. Save and exit from the editor.
5. Double click on ‘[Link]’ file to run.
6. When username and password asks, try the following:
Username: zim
Password: 123

Username: admin

Password: 1234

7. You may see a window like the following:

8. Try the following student IDs and press Enter:

03-03666-1, 01-01111-1, 02-02222-2, 03-03333-3

9. Now use however you like.

CLIENT LOGIN SOURCE CODE
import [Link].*;

import [Link].*;
import [Link].*;
import [Link].*;

public class ClientLogin extends JFrame implements ActionListener,

KeyListener
{
private JButton btnCancel;
private JButton btnOK;
private JPasswordField txtPass;
private JTextField txtName;
private JLabel lblPass;
private JLabel lblName;
private static ServerIntf rmiObj;

public ClientLogin()
{
//Setting up JFrame (ClientLogin)..
super("preAdvising Client Login");
Container con = getContentPane();
[Link](null);

//Setting up JButton (btnCancel)..

btnCancel = new JButton("Cancel");
[Link](154, 123, 84, 25);
[Link](btnCancel);

//Setting up JButton (btnOK)..

btnOK = new JButton("OK");
[Link](63, 123, 84, 25);
[Link](btnOK);

//Setting up JPasswordField (txtPass)..

txtPass = new JPasswordField();
[Link](95, 79, 144, 21);
[Link](txtPass);

//Setting up JTextField (txtName)..

txtName = new JTextField();
[Link](95, 44, 144, 21);
[Link](txtName);

//Setting up JLabel (lblPass)..

lblPass = new JLabel("Password:");
[Link](24, 79, 64, 17);
[Link](lblPass);

//Setting up JLabel (lblName)..

lblName = new JLabel("Name:");
[Link](51, 44, 60, 17);
[Link](lblName);
[Link](this);
[Link](this);
[Link](this);
[Link](this);

setSize(277, 210);
setLocation(100, 100);
setResizable(false); // Set MAX button and Resizing
disabled
setVisible(true);
}

public void keyPressed(KeyEvent e)

{
if([Link]()==KeyEvent.VK_ENTER)
{
String u = [Link]();
String p = new String([Link]());

if([Link]("") || [Link](""))
{
[Link](null, "Type
username and password.", "Warning!",
JOptionPane.WARNING_MESSAGE);
return;
}
try
{
if([Link](u, p))
{
ClientMain cm = new ClientMain(rmiObj);

[Link](JFrame.EXIT_ON_CLOSE);
setVisible(false);
}
else
[Link](null,
"Invalid username and/or password.", "Error!",
JOptionPane.WARNING_MESSAGE);
}
catch(Exception ex)
{
[Link](ex);
}
}
}

public void keyReleased(KeyEvent e) {}

public void keyTyped(KeyEvent e) {}

public void actionPerformed(ActionEvent e)

{
if([Link]()==btnCancel)
[Link](0);
if([Link]()==btnOK)
{
String u = [Link]();
String p = new String([Link]());

if([Link]("") || [Link](""))
{
[Link](null, "Type
username and password.", "Warning!",
JOptionPane.WARNING_MESSAGE);
return;
}

try
{
if([Link](u, p))
{
ClientMain cm = new ClientMain(rmiObj);

[Link](JFrame.EXIT_ON_CLOSE);
setVisible(false);
}
else
[Link](null,
"Invalid username and/or password.", "Error!",
JOptionPane.WARNING_MESSAGE);
}
catch(Exception ex)
{
[Link](ex);
}
}
}

public static void main(String args[])

{
try
{
ClientLogin app = new ClientLogin();

[Link](JFrame.EXIT_ON_CLOSE);

rmiObj =
(ServerIntf)[Link]("rmi://"+args[0]+"/preAdvisingServer
");
}
catch(Exception e)
{
[Link](e);
}
}
}
CLIENT MAIN PAGE SOURCE CODE

import [Link];
import [Link].*;
import [Link].*;
import [Link].*;

public class ClientMain extends JFrame implements ActionListener, KeyListener, ItemListener

{
private JButton btnCancel;
private JButton btnReg;
private JButton btnRef;
private JButton btnRem;
private JList lstSub;
private JButton btnAdd;
private JComboBox cmbSubList;
private JTextField txtID;
private JLabel lblSubList;
private JLabel lblStudID;
private JLabel lblTaken;

private ServerIntf rmiObj;

private Vector takenSub;

public ClientMain(ServerIntf rmiObj)

{
//Setting up JFrame (ClientMain)..
super("preAdvising Client Main");
Container con = getContentPane();
[Link](null);

//Setting up JTextField (txtID)..

txtID = new JTextField();
[Link](123, 40, 144, 21);
[Link](txtID);

//Setting up JButton (btnCancel)..

btnCancel = new JButton("Cancel");
[Link](285, 325, 84, 25);
[Link](btnCancel);

//Setting up JButton (btnReg)..

btnReg = new JButton("Register");
[Link](false);
[Link](103, 325, 84, 25);
[Link](btnReg);

//Setting up JButton (btnRef)..

btnRef = new JButton("Refresh");
[Link](194, 325, 84, 25);
[Link](btnRef);

//Setting up JButton (btnRem)..

btnRem = new JButton("Remove");
[Link](false);
[Link](376, 143, 84, 25);
[Link](btnRem);

//Setting up JButton (btnAdd)..

btnAdd = new JButton("Add");
[Link](false);
[Link](285, 111, 84, 25);
[Link](btnAdd);

//Setting up JList (lstSub)..

lstSub = new JList();
JScrollPane splstSub = new JScrollPane(lstSub);
[Link](51, 143);
[Link](318, 171);
[Link](splstSub);

//Setting up JComboBox (cmbSubList)..

cmbSubList = new JComboBox();
[Link](123, 71, 247, 21);
[Link](cmbSubList);

//Setting up JLabel (lblSubList)..

lblSubList = new JLabel("Subject List:");
[Link](51, 75, 76, 17);
[Link](lblSubList);
//Setting up JLabel (lblStudID)..
lblStudID = new JLabel("Student ID:");
[Link](55, 40, 92, 13);
[Link](lblStudID);

//Setting up JLabel (lblTaken)..

lblTaken = new JLabel("Subjects taken in this semester:");
[Link](51, 127, 255, 17);
[Link](lblTaken);

[Link] = rmiObj;

[Link](this);
[Link](this);
[Link](this);
[Link](this);
[Link](this);
[Link](this);
[Link](this);

setSize(505, 408);
setLocation(100, 100);
setResizable(false); // Set MAXIMIZE button and Resizing disabled
setVisible(true);
}
public void itemStateChanged(ItemEvent e)
{
if([Link]()==1)
// tmpSub = (String)[Link]();
;
}

public void keyPressed(KeyEvent e)

{
Vector v = new Vector();
if([Link]()==KeyEvent.VK_ENTER)
{
try
{
v = [Link]([Link]());
if([Link]()<1)
{
[Link](null, "Incorrect ID.",
"Warning!", JOptionPane.WARNING_MESSAGE);
[Link](new Vector());
[Link]();
[Link]("");
[Link](false);
[Link](false);
[Link](false);
}
[Link](new Vector());
[Link]();

for(int i=0; i<[Link](); ++i)

[Link]([Link](i));

if([Link]()>0)
[Link](true);

takenSub = [Link]([Link]());
[Link](takenSub);
if([Link]()>0)
{
[Link](true);
[Link](true);
}
}
catch(Exception ex)
{
[Link](ex);
}
}
}

public void keyReleased(KeyEvent e) {}

public void keyTyped(KeyEvent e) {}
public void actionPerformed(ActionEvent e)
{
if([Link]()==btnCancel)
[Link](0);

if([Link]()==btnRef)
{
[Link]("");
[Link]();
[Link](new Vector());
}

if([Link]()==btnAdd)
{
if([Link]()==-1)
{
[Link](null, "You have to select a
subject first to add.", "Warning!", JOptionPane.WARNING_MESSAGE);
return;
}
for(int i=0; i<[Link](); ++i)

if([Link](i).toString().equals([Link]().toString()))
{
[Link](null, "You already have
added this subject in the list.", "Warning!", JOptionPane.WARNING_MESSAGE);
return;
}
[Link]([Link]().toString());
[Link](takenSub);
if([Link]()>0)
[Link](true);
}

if([Link]()==btnReg)
{
if([Link]().equals(""))
{
[Link](null, "You have not entered
student ID.", "Warning!", JOptionPane.WARNING_MESSAGE);
return;
}

try
{
[Link](takenSub, [Link]());
}
catch(Exception ex)
{
[Link](ex);
}
}

if([Link]()==btnRem)
{
if([Link]()==-1)
{
[Link](null, "You have to select a
subject first from the list to remove.", "Warning!", JOptionPane.WARNING_MESSAGE);
return;
}

POLICY
grant
{
permission [Link];
};
SERVER
SERVER SOURCE CODE:

import [Link];
import [Link].*;
import [Link].*;
import [Link].*;

class ServerImpl extends UnicastRemoteObject implements ServerIntf

{
public ServerImpl() throws RemoteException
{
super();
}

public void regSub(Vector v, String sid)

{
[Link]("* Client: void regSub(Vector, "+sid+")");

try
{
[Link]("[Link]");
Connection con =
[Link]("jdbc:odbc:db","","");
Statement stm = [Link]();
[Link]("UPDATE sub SET status='Not done'
WHERE sid='"+sid+"' AND status='Taken'");
for(int i=0; i<[Link](); ++i)
[Link]("UPDATE sub SET status='Taken'
WHERE sid='"+sid+"' AND sub='"+[Link](i)+"'");
[Link]();
[Link]();
}
catch(Exception e)
{
[Link](e);
}
}

public Vector retNotDoneSubList(String sid)

{
Vector v = new Vector();
[Link]("* Client: Vector retNotDoneSubList("+sid+")");

try
{
[Link]("[Link]");
Connection con =
[Link]("jdbc:odbc:db","","");
Statement stm = [Link]();
ResultSet rs = [Link]("SELECT sub FROM sub
WHERE sid='"+sid+"' AND status='Not done' ORDER BY sub");
while([Link]())
[Link]([Link]("sub"));
[Link]();
[Link]();
}
catch(Exception e)
{
[Link](e);
}
return v;
}

public Vector retTakenSubList(String sid)

{
Vector v = new Vector();
[Link]("* Client: Vector retTakenSubList("+sid+")");

try
{
[Link]("[Link]");
Connection con =
[Link]("jdbc:odbc:db","","");
Statement stm = [Link]();
ResultSet rs = [Link]("SELECT sub FROM sub
WHERE sid='"+sid+"' AND status='Taken' ORDER BY sub");
while([Link]())
[Link]([Link]("sub"));
[Link]();
[Link]();
}
catch(Exception e)
{
[Link](e);
}
return v;
}

public boolean validUser(String user, String pass)

{
boolean res = false;
[Link]("* Client: boolean validUser("+user+",
"+pass+")");

try
{
[Link]("[Link]");
Connection con =
[Link]("jdbc:odbc:db","","");
Statement stm = [Link]();
ResultSet rs = [Link]("SELECT * FROM Users");
while([Link]())
if([Link]("User").equals(user) &&
[Link]("Pass").equals(pass))
res = true;
[Link]();
[Link]();
}
catch(Exception e)
{
[Link](e);
}
return res;
}
}

public class Server

{
public static void main(String args[])
{
try
{
ServerImpl obj = new ServerImpl();
[Link]("preAdvisingServer", obj);
}
catch(Exception e)
{
[Link](e);
}
}
}

SERVER INTERFACE SOURCE CODE:

import [Link].*;
import [Link];

public interface ServerIntf extends Remote

{
public boolean validUser(String user, String pass) throws
RemoteException;
public Vector retNotDoneSubList(String sid) throws RemoteException;
public Vector retTakenSubList(String sid) throws RemoteException;
public void regSub(Vector v, String sid) throws RemoteException;
}

POLICY:

grant
{
permission [Link];
};
Student Registration System Project in Java
Student Registration System

Project Objective

The aim of this Student Registration System project is to build a student
registration system that will completely automate the process of new student registration
in a university. The system will handle the document submission, testing process and
registration of new students. The system will be web based and will have two
implementations i.e. client side (student) and server side (university). The server side
implementation can only be accessed over the university intranet while the client side
can be accessed over the internet.

The process begins when prospective students wish to enrol in the university. If
they express interest in any course they will be required to visit the university and can
create a user account at the administration block. This is the only part of the system
where every user has to have human interaction, this is intended as a security measure
to prevent the creation of false user IDs. After verification of any nationally approved
photo ID proof a user account will be created and a scanned copy of the ID proof will be
uploaded into the profile. After this the user can upload all necessary documents on the
portal from the convenience of their home. The system will automatically validate all the
documents and the prospective student will be able to schedule a test date after
successful validation. The test will be conducted on the premises of the university or at
regional test centres and will require the authentication of user credentials. The test
results will be normalised and a score will be immediately published. After the
completion of all tests the system will automatically publish a merit list to indicate which
students have gained admission.

Students will be able to accept or decline offers of admission using this portal.
After accepting admission the documents uploaded will be scrutinized by university
authorities and any discrepancies notified. After all error flags are cleared the student
will be able to make the first fee payment via internet banking through the system,
following which the Student Registration System will assign the student a unique roll
number and register them as a student of the university. This Student Registration
System will automatically update the new student details into the university student
database.
Existing Student Registration System

The existing Student Registration System of registration requires many

documents and application forms to be filled out. Data has to be repeatedly entered at
each stage of the process and multiple files are made for each student. Documents are
verified with multiple copies made for record and the testing process is conducted
independently which again compounds the paperwork required. The amount of data
processing required for each stage of the process ensures that the process of new
student admission takes a long time.

Proposed System

The proposed Student Registration System will eliminate the paper trail required
for the completion of various formalities. The entire process of prospective student
registration till new student registration can be handled by this system. The testing
process can be done entirely on the system and results can be quickly judged and
shared. The presence of this system will remove ambiguity in the process that can
confuse tense prospective students.

Student Registration System Modules

Admin: The admin will be able to create prospective student profiles after verification of
nationally approved photo ID’s of the user. The admin will be able to cancel student
accounts if irregularities are detected.

Prospect: The prospective student will use this module to upload documents and
schedule test dates. The rank list can also be accessed through this module.

Testing: The testing module can be used by the student during the testing phase. A
total score will be displayed at the end of the test and results will be stored centrally.

New registration: Once a prospective student achieves an acceptable rank and

accepts the offer of admission they will be shifted to the new registration module and
allotted a unique roll number. The admin will scrutinize the documents of users in the
new registration module and notify them about discrepancies. The new student will be
able to pay initial fees through this module and will be notified about the next process
through this module. This module will automatically update the student database with
the details of the new student.

Software Requirements

 Windows XP
 Apache Tomcat Web Server
 Oracle

Technology Used

 Java

Hardware Requirements

 Hard Disk – 2 GB
 RAM – 1 GB
 Processor – Dual Core or Above
 Mouse
 Keyboard

Common questions