ABSTRACT

Education over the Internet is the latest concept in spreading

education to every one. The conveniences of learning on line are
numerous. Students and those interested in learning over the
computer and can choose their own timing that is convenient to them
and the classes can be taken at their own place

This Interactive Classroom System is designed in such a way that the

student i.e. client can communicate with the server when it is logged
on and the client can retrieve the text files from the server by issuing
the request. Clients have his or her own login name and password,
which help them to get connected with the server. Here the students
are provided with the facility of attending the class of their choice
and can choose the faculty according to their wish

In the Interactive Classroom System, when we take the view of the

teacher i.e. the server. It has the following features and functionality.

1. The teacher can pass text files to all the students present in the
classroom.
2. Student can communicate one to one with the teacher.
3. Teacher can have a view about the attendance of the class.
4. Teacher has the right to permit or reject a student’s request to leave
the classroom.
5. The text typed by the teacher is reflected on all the students system.
6. When the teacher leaves the classroom the students can’t
communicate with the server.

The student module of the Interactive Classroom System can

communicate with the server and retrieve the information from it. It
has the following functionality

1. The students can enter into the classroom by issuing a request.

2. He has the facility to store all the notes issued by the teacher.
3. He is permitted to leave the class only after getting the permission
from the teacher.
4. The student can ask the doubt to the teacher and it won’t be
reflected in other students system.
 HARDWARE AND SOFTWARE REQUIREMENTS

Software Requirements

JDK1.4.1_01
SWINGS
RMI
NETWORKING
ORACLE

Hardware requirements

Pentium-IV
256 MB RAM
40 GB Hard disk

Purpose: The purpose of this document is to describe all external

requirements for the Interactive Classroom System. It also describes
the interfaces for the system. It is

a. To implement Interactive Classroom System we need

RMI (Remote Method Invocation), which is used to access invoke a
method of an object that is running on remote machine. So we call
that object as remote object.

b. As a user interface, we used some screens developed

using swings. Because it is user-friendly and makes coding easy to
access any kind of resources.
c. Using swings, RMI and basic java i.e. core java are used
to develop our project. Code details can see later in this
documentation.

1.1 Scope: This document describes the requirements of the

system. It is meant for use by the developers, and will also be the
basis for validating the final system. Any changes made to the
requirements in the future will have to go through a formal change
approval process. The developer is responsible for asking for
clarifications. When necessary and will not make any alterations
without the permission of client.

This project work intends to design a classroom in such a way that the
student i.e. client can communicate with the server when it is logged
on and the client can retrieve the text files from the server by issuing
the request. Clients have his or her own login name and password,
which helps them to get connected with the server. Here the students
are provided with the facility of attending the class of their choice. All
the basic features are developed in very effective manner.

1.2 Definition: Interactive Classroom System is mainly

designed to provide a virtual room to which both the lecturer and the
student can login from anywhere.

1.3 Reference: Not Applicable.

1.4 Developers Responsibilities overview: The points that
mentioned in system requirements specification are

1. An introductory nature describing mainly the

 Purpose of the system requirements specifications

document.
  Outlining the scope of the envisaged application.

2. Describes the iterations of the system with its

environment without going into the internals of the system. Also
describes the constraints imposed on the system. Thus it is out side the
envisaged application. The assumptions made are also listed. It is
supported by the
 UML Diagrams
 E-R Diagrams

3. It also describes the internal behaviour of the system in

response to the inputs and while generating the outputs.

This document is also supported with detailed level UML diagrams

and E-R Diagrams, list of inputs, process explanation and list of
output.

4. Contains external interface requirements, which includes

the user, hardware and software interfaces.

5. Deals with performance requirements of the system.

Contains the design constraints composing of software constraints and
hardware constraints.

2. General Description

2.1 Product function’s overview: The functional view of our

product is like this:

Learning is an on going process and this online classroom is intended

to make education convenient and easy for all.
For any system to function well security is needed. This classroom is
designed such that it provides security for the whole system. Only the
administrator has the right to add new faculty and faculty has the right
to add new students. The students can enter the system only by using
their login name and password and the student can change his
password at his own decision.

Any no of students can log on to the server system at a time and they
can communicate with the server. The administrator has the right to
modify the student and faculty details and the faculty can monitor the
whole classroom.

Constraints

For a student enter into the class, he has to have his own login name
and password and also the IP address of the server to which he has to
get connected.

2.2 User Characteristics: In our project users are Super user

(administrator), a Lecturer and a Student. No need to have the
computer knowledge to work on this system because that kind of user
interface we have provided. This is very easy to navigate and
omnipresent help is provided. In our each user have some limitations
to do. So one can do the operations as per the constraints defined to
him. He can’t do any operation, which is basically not pertaining to
him. In such a way we provide the security in our system. Only
authorized users can access or use the resources.

2.3 General constraints: The system should run on Pentium,

under windowsNT/2000 professional or server or forward versions of
Microsoft operating systems with minimum 16 MB RAM for better
performance. We can deploy this web application on any server. And
can access even from smart terminals, which is provided net facility.

2.4 Assumptions and Dependencies:

a. It is assumed that the RMI is programme running on a
machine is a Server. Resource and required information already
existed with the system.
b. It is assumed that all data on which we process is
dummy. And we test this by placing both server and client on same
machine.
c. All the details produced by the user are correct.
d. We must depend on internet work.