Virtual classroom system

Submitted in partial fulfillment of the requirements for the award of the degree of Bachelor of
Technology in Information Technology Engineering under Dr. Babasaheb Ambedkar
Technological University, Lonere.
)

ACKNOWLEDGEMENT

Kartik Kashinath Deore

Jeet Jagdish Muley
Prasanna Prashant Meshram
Rohit Dinkar Gaykawad
Department of Information Technology
Contents
 Software Requirements Specification

Scope:
   This project has a lot of scope for future development. Developing a virtual classroo
m system to promote a greater count of students to splurge into the field of Education.

1.1 Purpose:

The purpose of the virtual classroom system is to integrate the benefits of a physical cla
ssroom with the convenience of a “no-physical-bar” virtual learning environment. It
 will usher in the immense flexibility and sophistication in the existing learning
platform structures, with the perfect blend of synchronous and asynchronous
interaction. It provides a means of collaborative learning for the students.

1.2 Definitions, Acronyms, and Abbreviations:

 HTML (Hyper Text Markup Language): It is used to create static web pages.

 JSP (Java Server Pages): It is used to create dynamic web content

 J2EE (Java 2 Enterprise Edition): It is a programming platform, belonging to t
he Java platform, which is used for developing and running distributed java
applications.

 HTTP (Hyper Text Transfer Protocol): It is a transaction oriented client/ serve
r protocol between a web browser and a server.

 XML (Extensible Markup Language): It is a markup language that was design
ed to transport and store data.

 MySql: It is a database management system that provides a flexible and efficient
database platform to raise a strong “ on demand” business applications.

 J2EE (Java 2 Enterprise Edition): It is a programming platform, belonging to t
he Java platform, which is used for developing and running distributed java
applications.

 Java: Application Architecture.

 XML: Extension Markup Language.

 MySql: It is a database management system that provides a flexible and efficient
database platform to raise a strong “on demand” business applications.

1.1 Overview :

Overall Description : 

Developing a virtual classroom system to promote a greater count of students to splur
ge into the field of Education. It integrates the benefits of a physical classroom with
the convenience of a ‘no-physical-bar’ virtual learning environment, minus the
commuting hazards and expenses. It will usher perfect blend of synchronous and
asynchronous interaction. It provides a means of collaborative learning for the
students.

Specific Requirements:

Users of the System :

1. Students

2. Faculties

3. College Management (Dean, HODs, Principal)

4. Administrator

1. Students:

 Students can choose courses, attend lectures, take exams, view their attend
ance records, progress report etc as per their convenience.

 Registration for multiple courses.

 Attend lectures either at the scheduled time or on request view lecture at a l
ater time.

 There can be forums, blogs etc to discuss various queries and to put up sug
gestions posted both by students and teachers.

 Students can take up various quizzes which can help them to realize their i
nbuilt talents in various fields.

2. Faculties :

 Faculties can take lectures, upload assignments, announcements, evaluate a
nswer sheets and also can upload lectures and other discussions in various
formats as in videos, power point presentation etc.

 Upload and Download of various assignments, college notices, student's no
tices, journals, videos.

 There can be forums, blogs etc to discuss various queries and to put up sug
gestions posted both
by students and teachers.

3. Administrator :

Administrator can generate reports, log files, backup/recovery of data at any time 
and create user, department and courses.
 4. Dean :

 Can view all actors details.

1.0 Product Perspective :

The   virtual   classroom   system   promotes   a   greater   count   of   students   and  
minus   the communicating hazards and expenses.

1.1 Software Interface:

 It should be possible for Elearning tool to be implemented in both 
Windows and Linux Operating System environments.

 The GUI and other parts of the E-learning tool software are to be done in
JAVA and J2EE.

 The output of this software will need a web browser for viewing it.

1.2 Hardware Interface:

 Monitor screen – the software shall display information to the user via the monitor scree
n.

 Mouse – the software shall interact with the movement of the mouse and the mouse butto
ns.
The mouse shall activate areas for data input, command buttons and select options from
menus.

 Keyboard –   the software shall interact with the keystrokes of the keyboard. The keyboa
rd will input data into the active area of the database.

1.3 Product Function :
  Only Registered users can access the courses.

 Users must have valid User id and Password to access the system.

  In this system  students can choose their courses and view their Attendance Records,G
rades in quizzes, internal tests and assignments.

 Students can share their resources through forums.

  Faculty can upload the syllabus,lesson plan, session plan,class notes and question ban
k for the courses.
  Students can get alert information about due date of quizzes.

 Administrator can generate reports or recovery of data at anytime.

 System provides 24x7 availability.

1.4 User Characteristics:

Each User has a valid user name ,passwd ,User id ,which department he/she belongs,
duration (in years), Age, Grade, User Role, etc…

2.8 Use Case Model Description:

Definitions:
A Use Case specifies the behavior of a system or a part of the system and is a description 
of a set of sequences of actions, including variants, which a system performs to yield an
observable result of value to an actor. Use cases provide a way for the developers to come
to a common understanding with the system’s end domain experts. Graphically, a use
case is rendered by an ellipse. A use Case diagram is just a special king of diagram and
shares the same common properties as do all other diagrams – a name and graphical
content that are a projection into a model. In a use case diagram, there is boundary and
the actors stay outside the boundary and the use cases are kept inside the boundary. Use
Case diagrams commonly contain

            • Use cases

            • Actors

            • Dependency, generalization, and association relationships
3.0 Supplementary Requirements

 Have Hours of Operation that are 24*7:Because System Can be authenticated it can
stay open for 24 hours a day.
 Reduce the cost of sales transaction: To the extend one can automate the sales
process through this system ,one can start to reduce the sales of that sales transaction.
 Make the existing website more Dynamic in nature: Many early web implementation
consisted of static HTML pages. This because it becomes difficult to manage if the
number of pages get too large. Application should serve dynamic user based customized
web pages to its client from server.
 Tie the existing website into the existing enterprise system: Any existing website
that relies from the manual duplication of data from another system is one that can be
improved.
 i. System Requirements:
In this stage, the system services, constraints and goals are established by consolation
with system users. It defined in detail and serves as a system specification.

ii. System and Software Design:

In this stage, we will conceptualize overall system architecture.in design phase involves
fundamental system abstraction and their relationships.

iii. Implementation and Unit testing:

In this stage, the software design realized as a set of programs or a program units .In unit testing we
will verify that each unit must meet its specifications.

iv. Integration and system testing:

In this stage, the system individual program units or programs are integrated and tested to the
complete system that ensure software requirement have been met. After testing, the software
system developed to the customer.

v. Operating and Maintenance:

In this stage, this is the longest phase of software life cycle.
Maintenance means correcting errors which were not discovered in earlier
stages of development.

Data
Figure 3 is the data flow diagram showing information exchange at the student user level. The
diagram contains lectures modules, answer questions and view solution modules, check
performance module, contributed to forums, view discussion, and forum messages modules.

Student Personal
performance
messages

\ Cover lecture modules. Answer question and view

solutions. Check performance. Contribute to
Study activities. forums.
Answers to Discussion
View discussion forum messages.
question forum
Contribution to messages

Students Performance
answer score Discussion
Lecture Student’s
coverage forum
modules
data store

Questions Student’s Student’s

data store coverage
Performance
data store data store