E-Learning Resource Locator

E-Learning Resource Locator
1.1 Overview
With the advancement of technology, the mode of education is experiencing an increasing need to
accommodate changes in the traditional method of teaching as well as learning. This caused the
emergence of e-learning, which in recent years has created a path for education for everyone. E-
learning is defined as the acquisition and use knowledge, distributed and facilitated primarily by
electronic means. The rapid growth of computers and access to internet made it possible to bring
the concepts like twenty four hour learning in reality. E-learning tools are establishing
communication between educators and learners, regardless of their geographical location.
“E Leaning-Resource Technology” is education based website/software , helping students to get

all resources & study materials of every courses available. It uses “E-Book” facility. It is reliable
& time efficient approach compared to all links of the website provided by any search engine while
searching for course materials.
The E Learning- Resource Locator is a collaborative teaching tool to assist the students to learn in
an interactive manner. It aims to complement the efforts of teachers to integrate technology into
their classrooms and link the students to the Internet in educationally productive ways and provide
them a stimulating, positive and enjoyable environment to study.
1.2 Purpose of the project
E-Learning Resource Locator is a web application designed exclusively for Students. The project
is intended for Computer Science department of the college. Using this application all registered
students can access the system. The users of the system can access the required learning materials.
All registered Professors can upload learning materials for students.
The system makes it possible for the students to access all learning materials from home and
interact with the Professors and clarify their doubts on different subjects. The students can access
notes on any subject. Notes are available for the students of all branches. Students can download
all notes, if they want to. Moreover, power point presentations on all topics can be uploaded in to
1
CUTM-CSE DEPT
the system. Publication House can also be allowed to upload the information or some materials to
the students for their learning process and students can also download those material. The students
can clarify their doubts with the Professors by posting their questions into the forum. Any
registered professors are allowed to answers or reply to any questions.
1.3 Goal of the project
The proposed E-Learning Resource System has the following features.
 Only registered students and Professors can access the system.

 Students can view and download all learning materials (notes, ppts).
 Students can view ppts of topics which help them to grasp the topics easily.
 Professors can upload all learning materials.
 Students are allowed to discuss their doubts with the professor.
 Students can post their questions into the discussion forum.
 Registers professors are allowed to answer to the students questions.
 Students are allowed to download the resources.
 More than one professors are allowed to answer to the students questions.
 Publication house also uploads some subject materials to the students.
 The students are also downloading those materials which are uploaded by the publication
house.
 Professors also download the materials which are uploaded by the publication house.
1.4 Scope of the project
It provides the user a distance learning methodology. The E-Learning can be implemented in
educational bodies such as:
1. Colleges
2. Schools
2
CUTM-CSE DEPT
3. Universities
4. Coaching Institutes
5. A Home User etc.
The basic users involved in this project is
 Students
 Teachers/Professors
 Mentors
 Toppers of the college
 Well known Publication House
Students after registering into this website they can download, upload & clarify their doubts.
They can interact with the toppers and Professors of University. They can access soft copy of
books with the help of well-known Publication Houses.
Professors give guidance to the students according to their related subjects. They can also
download books and upload materials into this website.
Toppers of university give guidance to the students and share their knowledge. They provide
materials and update their details.
Well known Publication House provides soft copies of the books. By using links Provided by
this publication houses. Students can download soft copies of books and materials.
Mentors are as serve a teacher trusted counselor. They Creates a safe learning environment. He
provides unique id and password to the users. He maintains all the information about the users. If
any problems occurred according to login or to modify any information he will provide guidance
to them.
3
CUTM-CSE DEPT
2.1 Implementation of environment
I. JSP
Architecturally, JSP may be viewed as a high-level abstraction of Java servlets. JSP pages are
loaded in the server and are operated from a structured special installed Java server packet called
a Java EE Web Application, often packaged as a .war or .ear file archive.
JSP allows Java code and certain pre-defined actions to be interleaved with static web markup
content, with the resulting page being compiled and executed on the server to deliver an HTML or
XML document. The compiled pages and any dependent Java libraries use Java byte-code rather
than a native software format, and must therefore be executed within a Java virtual machine (JVM)
that integrates with the host operating system to provide an abstract platform neutral environment.
JSP syntax is a fluid mix of two basic content forms: scriptlet elements and markup. Markup is
typically standard HTML or XML, while scriptlet elements are delimited blocks of Java code
which may be intermixed with the markup. When the page is requested the Java code is executed
and its output is added, in situ, with the surrounding markup to create the final page. JSP pages
must be compiled to Java byte-code classes before they can be executed, but such compilation is
needed only when a change to the source JSP file has occurred.
Java code is not required to be complete (self-contained) within its scriptlet element block, but can
straddle markup content providing the page as a whole is syntactically correct (for example, any
Java if/for/while blocks opened in one scriptlet element must be correctly closed in a later element
for the page to successfully compile). This system of split inline coding sections is called step over
scripting because it can wrap around the static markup by stepping over it. Markup which falls
inside a split block of code is subject to that code, so markup inside an if block will only appear in
the output when the if condition evaluates to true; likewise markup inside a loop construct may
appear multiple times in the output depending upon how many times the loop body runs.
Java Server Pages (JSP) is a technology that helps software developers created dynamically
generated web pages based on HTML, XML, or other document types. JSP may be viewed as a
high-level abstraction of Java servlets.
4
CUTM-CSE DEPT
II. J2EE
The Java Platform, Enterprise Edition (Java EE) is a collection of Java APIs owned by Oracle that
software developers can use to write server-side applications. It was formerly known as Java 2
Platform, Enterprise Edition, or J2EE.
Sun Microsystems (together with industry partners such as IBM) originally designed Java EE to
simplify application development in a thin-client-tiered environment. Java EE simplifies app
development and decreases the need for programming by creating standardized, reusable modular
components and by enabling the tier to handle many aspects of programming automatically.
Java EE applications are hosted on application servers, such as IBM's WebSphere, Oracle's
GlassFish or Red Hat's WildFly server, all of which run either in the cloud or within a corporate
data center. While Java EE apps are hosted on the server side, examples of Java EE clients include
an internet of things (IoT) device, smartphone, RESTful web service, standard web-based
application, WebSocket or even microservices running in a Docker container.
The Java EE architecture provides services that simplify the most common challenges facing
developers when building modern applications, in many cases through APIs, thus making it easier
to use popular design patterns and industry-accepted best practices.
For example, one common challenge enterprise developers face is how to handle requests coming
in from web-based clients. To simplify this challenge, Java EE provides the Servlet and JavaServer
Pages (JSP) APIs, which provide methods for activities like finding out what a user typed into a
text field in an online form or storing a cookie on a user's browser.
Another common task is how to store and retrieve information in a database. To address this goal,
Java EE provides the Java Persistence API (JPA,) which makes it easy to map data used within a
program to information stored in the tables and rows of a database. Also, creating web services or
highly scalable logic components is simplified through the use of the Enterprise JavaBeans (EJB)
specification. All of these APIs are well tested, relatively easy for Java developers to learn and can
greatly simplify some of the hardest parts of enterprise development.
III. HTML
HTML, which stands for Hyper Text Markup Language, is the predominant markup language for
web pages. It provides a means to create structured documents by denoting structural semantics
5
CUTM-CSE DEPT
for text such as headings, paragraphs, lists etc. as well as for links, quotes, and other items. It
allows images and objects to be embedded and can be used to create interactive forms. It is written
in the form of HTML elements consisting of "tags" surrounded by angle brackets within the web
page content. It can include or can load scripts in languages such as JavaScript which affect the
behavior of HTML processors like Web browsers; and Cascading Style Sheets (CSS) to define the
appearance and layout of text and other material. The W3C, maintainer of both HTML and CSS
standards, encourages the use of CSS over explicit presentational markup.
Hyper Text Markup Language (HTML) is the encoding scheme used to create and format a web
document. A user need not be an expert programmer to make use of HTML for creating hypertext
documents that can be put on the internet.
Most graphical e-mail clients allow the use of a subset of HTML (often ill-defined) to provide
formatting and semantic markup not available with plain text. This may include typographic
information like colored headings, emphasized and quoted text, inline images and diagrams. Many
such clients include both a GUI editor for composing HTML e-mail messages and a rendering
engine for displaying them. Use of HTML in e-mail is controversial because of compatibility
issues, because it can help disguise phishing attacks, because it can confuse spam filters and
because the message size is larger than plain text.
The Project is made using web technologies like JSP, HTML with proper documentation so that
the future person who will work under the same project can understand the code.
E Learning Resource Locator on courses is an essential element in quality assurance. The aim of
this is to save time for staff in academic departments and to allow the faculties to upload materials
and answer the questions asked by the students in an effective way. This recognizes that whilst
the information remains the property of the College.
Naming Convention - The most common filename extension for files containing HTML is .html.
A common abbreviation of this is .html, which originated because some early operating systems
and file systems, such as DOS and FAT, limited file extensions to three letters.
HTML Application - An HTML Application is a Microsoft Windows application that uses HTML
and Dynamic HTML in a browser to provide the application's graphical interface. A regular HTML
file is confined to the security model of the web browser, communicating only to web servers and
manipulating only webpage objects and site cookies. An HTA runs as a fully trusted application
6
CUTM-CSE DEPT
and therefore has more privileges, like creation/editing/removal of files and Windows Registry
entries. Because they operate outside the browser's security model, HTAs cannot be executed via
HTTP, but must be downloaded (just like an EXE file) and executed from local file system.
III. UML
Unified Modeling Language, or UML, provides an overview of the most important diagrams used
in the visual modeling of computing programs. The most useful, standard UML diagrams are: use
case diagram, class diagram, sequence diagram, state chart diagram, activity diagram, component
diagram, and deployment diagram. By using this UML diagrams one can easily understand about
any product or application.
Unified Modeling Language, is a standardized modeling language consisting of an integrated set

of diagrams, developed to help system and software developers for specifying, visualizing,
constructing, and documenting the artifacts of software systems, as well as for business modeling
and other non-software systems. The UML represents a collection of best engineering practices
that have proven successful in the modeling of large and complex systems. The UML is a very
important part of developing object oriented software and the software development process. The
UML uses mostly graphical notations to express the design of software projects. Using the UML
helps project teams communicate, explore potential designs, and validate the architectural design
of the software. In this article, we will give you detailed ideas about what is UML, the history of
UML and a description of each UML diagram type, along with UML examples.
As the strategic value of software increases for many companies, the industry looks for techniques
to automate the production of software and to improve quality and reduce cost and time-to-market.
These techniques include component technology, visual programming, patterns and frameworks.
Businesses also seek techniques to manage the complexity of systems as they increase in scope
and scale. In particular, they recognize the need to solve recurring architectural problems, such as
physical distribution, concurrency, replication, security, load balancing and fault tolerance.
Additionally, the development for the World Wide Web, while making some things simpler, has
exacerbated these architectural problems. The Unified Modeling Language (UML) was designed
to respond to these needs. The primary goals in the design of the UML summarize by Page-Jones
in Fundamental Object-Oriented Design in UML as follows:
7
CUTM-CSE DEPT
1. Provide users with a ready-to-use, expressive visual modelling language so they can
develop and exchange meaningful models.
2. Provide extensibility and specialization mechanisms to extend the core concepts.
3. Be independent of particular programming languages and development processes.
4. Provide a formal basis for understanding the modelling language.
5. Encourage the growth of the OO tools market.
6. Support higher-level development concepts such as collaborations, frameworks, patterns
and components.
7. Integrate best practices.
IV. Oracle
There are a large number of database management systems currently available, some commercial
and some free. Some of them: Oracle, Microsoft Access, MySQL and PostgreSQL. These database
systems are powerful, feature-rich software, capable of organizing and searching millions of
records at very high speeds.
Database administrator is the super user of database, he has unrestricted rights and privileges to
access database, grant permission to other database users. Database user is the person who uses
the database in a restricted privileges, provided by database administrator.
An Oracle database is a collection of data treated as a unit. The purpose of a database is to store
and retrieve related information. A database server is the key to solving the problems of
information management. In general, a server reliably manages a large amount of data in a
multiuser environment so that many users can concurrently access the same data. All this is
accomplished while delivering high performance. A database server also prevents unauthorized
access and provides efficient solutions for failure recovery.
Oracle Database is the first database designed for enterprise grid computing, the most flexible and
cost effective way to manage information and applications. Enterprise grid computing creates large
pools of industry-standard, modular storage and servers. With this architecture, each new system
can be rapidly provisioned from the pool of components. There is no need for peak workloads,
because capacity can be easily added or reallocated from the resource pools as needed.
8
CUTM-CSE DEPT
The database has logical structures and physical structures. Because the physical and logical
structures are separate, the physical storage of data can be managed without affecting the access
to logical storage structures.
2.2 Project Planning and Scheduling
Project planning is part of project management, which relates to the use of schedules such as Gantt
charts to plan and subsequently report progress within the project environment. Initially, the
project scope is defined and the appropriate methods for completing the project are determined.
Following this step, the durations for the various tasks necessary to complete the work are listed
and grouped into a work breakdown structure. The logical dependencies between tasks are defined
using an activity network diagram that enables identification of the critical path. Float or slack
time in the schedule can be calculated using project management software. Then the necessary
resources can be estimated and costs for each activity can be allocated to each resource, giving the
total project cost. At this stage, the project plan may be optimized to achieve the appropriate
balance between resource usage and project duration to comply with the project objectives. Once
established and agreed, the plan becomes what is known as the baseline. Progress will be measured
against the baseline throughout the life of the project. Analyzing progress compared to the baseline
is known as earned value management.
2.3 Project Development Approach
The software methodology followed in this project includes the object-oriented methodology and
the application system development methodologies. The description of these methodologies is
given below.
9
CUTM-CSE DEPT
Application System Development – A Life cycle Approach
Although there are a growing number of applications (such as decision support systems) that
should be developed using an experimental process strategy such as prototyping, a significant
amount of new development work continue to involve major operational applications of broad
scope. The application systems are large highly structured. User task comprehension and developer
task proficiency is usually high. These factors suggest a linear or iterative assurance strategy. The
10
CUTM-CSE DEPT
most common method for this stage class of problems is a system development life cycle modal
in which each stage of development is well defined and has straightforward requirements for
deliverables, feedback and sign off. The system development life cycle is described in detail since
it continues to be an appropriate methodology for a significant part of new development work.
The basic idea of the system development life cycle is that there is a well-defined process by which
an application is conceived and developed and implemented. The life cycle gives structure to a
creative process. In order to manage and control the development effort, it is necessary to know
what should have been done, what has been done, and what has yet to be accomplished. The
phrases in the system development life cycle provide a basis for management and control because
they define segments of the flow of work, which can be identified for managerial purposes and
specifies the documents or other deliverables to be produced in each phase.
The phases in the life cycle for information system development are described differently by
different writers, but the differences are primarily in the amount of necessity and manner of
categorization. There is a general agreement on the flow of development steps and the necessity
for control procedures at each stage.
The information system development cycle for an application consists of three major stages.
1) Definition.
2) Development.
3) Installation and operation.
The first stage of the process, which defines the information requirements for a feasible cost
effective system. The requirements are then translated into a physical system of forms, procedures,
programs etc., by the system design, computer programming and procedure development. The
resulting system is test and put into operation. No system is perfect so there is always a need for
maintenance changes. To complete the cycle, there should be a post audit of the system to evaluate
how well it performs and how well it meets the cost and performance specifications. The stages of
definition, development and installation and operation can therefore be divided into smaller steps
or phrases as follows.
11
CUTM-CSE DEPT
Definition
Proposed definition : preparation of request for proposed applications.
Feasibility assessment : evaluation of feasibility and cost benefit of proposed
System.
Information requirement analysis : determination of information needed.
Design
Conceptual : User-oriented design of application development.
Physical system design : Detailed design of flows and processes in applications
processing system and preparation of program specification.
Development
Program : coding and testing of computer programs.
Procedure development : design of procedures and preparation of user instructions.
Installation and operation

Conversion : Final system test and conversion.
Operation and maintenance : Month to month operation and maintenance
Post audit : Evaluation of development process, application system and
results of use at the completion of the each phase, formal
approval sign-off is required from the users as well as from
the manager of the project development.
12
CUTM-CSE DEPT
2.4 Project Plan
Once we examine that the project is feasible, we undertake project planning. The table below
describes how we planned our project.
Phases No. of days Deliverables of the

phase
Feasibility Analysis 6 Feasibility Report
document
Requirement Gathering 15 System Requirement
Study
Analysis 09
Design 07 Design document

Implement Coding 30 Implementation of
system
Testing 4 Testing Document
Final Evaluation 1 Report Submit
13
CUTM-CSE DEPT
3.1 Existing System
The World Wide Web (WWW or Web in short) E-Learning provides a simple ‘point and click’
means of exploring the immense volume of pages of information residing on the Internet.
Information on Web is presented on Web pages, which appear as a collection of text, graphics, and
pictures. In addition, a Web page can contain hyperlinks to other Web pages. Much of the Web’s
success is due to the simplicity with which it allows users to provide, use and refer to information
distributed geographically around the world.
DRAWBACKS:
 No authentication to access the data.

 No access control.
 No better security.
 It is not time efficient approach.
 No database security.
3.2 Problem Statement
The following drawbacks of existing system emphasize the need for computerization:
1. In existing applications provides materials and text books. But they cannot provide direct
links of the publications. By this it is difficult to search for the materials which we required.
2. This result in waste of time. In many of the applications they are not providing
communication between professors with the students.
3. In many of the applications they not provide legal links. They are not virus free also some
websites cannot provide permissions to download books.
3.3 Proposed System
14
CUTM-CSE DEPT
E learning resource locator is a collaborative teaching tool to assist the students to learn in an
interactive manner. It aims to complement the efforts of teachers to integrate technology into their
classrooms and link the students to the Internet in educationally productive ways and provide them
a stimulating, positive and enjoyable environment to study.
It contains the following elements:-
1. Student Login:
It enables a person to login as a student or sign up if he/she has not registered for the
classroom. Once logged in a student has the following features:-
 Edit Profile: It allows modifying the details
 Study Material & Video Lectures: It displays a list of ppts & interactive video
lessons categorized by subjects as posted by the faculty
 Ask doubts: It enables the students to ask questions
 Answers: It shows the answers by the teachers to the questions asked by various
students
2. Faculty Login:
It enables a person to login as a faculty member or sign up if he/she has not registered for
the classroom. Once logged in a faculty member has the following features:-
 Edit Profile: It allows modifying the details .
 Study Material & Video Lectures: It allows the faculty members to post & remove
ppts & video lessons.
 Doubts: It shows all the questions asked by the students.
 Answers: It enables teachers to answer the questions asked by the students .
3. Administrator Login :
The administrator is the ultimate controller of the application with the highest authority.
He/she has the following features:-
 Student/Faculty: It displays a list of students/faculty members registered for the
classroom.
 Student/Faculty request: It displays a list of students/faculty members whose sign
up request is still pending
15
CUTM-CSE DEPT
 PPT (pload/del)/Video(upload/del): It displays a list of ppts & videos posted by

the faculty members. The administrator has the power to remove ppts/videos from
the list and upload according to wish.
 Question/Answers: It displays a list of questions asked by students/answers to
questions by teachers. The administrator has the power to delete
questions/answers from the list.
3.4 Feasibility Study
Feasibility study is conducted once the problem is clearly understood. Feasibility study is a high
level capsule version of the entire system analysis and design process. The objective is to
determine quickly at a minimum expense how to solve a problem. The purpose of feasibility is
not to solve the problem but to determine if the problem is worth solving.
The system has been tested for feasibility in the following points.
1. Technical Feasibility
2. Economical Feasibility
3. Operational Feasibility.
I. Technical Feasibility
This study is carried out to check the technical feasibility, that is, the technical requirements of the
system. Any system developed must not have a high demand on the available technical resources.
This will lead to high demands on the available technical resources. This will lead to high demands
being placed on the client. The developed system must have a modest requirement, as only minimal
or null changes are required for implementing this system.
II. Economical Feasibility
This study is carried out to check the economic impact that the system will have on the
organization. The amount of fund that the company can pour into the research and development of
16
CUTM-CSE DEPT
the system is limited. The expenditures must be justified. Thus the developed system as well within
the budget and this was achieved because most of the technologies used are freely available. Only
the customized products had to be purchased.
III. Social Feasibility
The aspect of study is to check the level of acceptance of the system by the user. This includes the
process of training the user to use the system efficiently. The user must not feel threatened by the
system, instead must accept it as a necessity. The level of acceptance by the users solely depends
on the methods that are employed to educate the user about the system and to make him familiar
with it. His level of confidence must be raised so that he is also able to make some constructive
criticism, which is welcomed, as he is the final user of the system.
3.5 Software Requirement Specification
The purpose of the system is to develop Online Examination System., used to test the Domain
knowledge of the students, with respect to the particular technology. The manual procedure used
for conducting exam is time consuming process and error prone due to human limitations. The
main task is to simplify the process of conducting examinations for students to test their
knowledge. The student enters his/her details and then attempts the examinations for their specific
domain in the given time period. Coming to the hardware components we require a system with
certain capabilities which are specified under the hardware requirements.
3.5.1 Functional Requirements
It defines a function of a software system or its component. A function is described as a set of

inputs, the behavior, and outputs.
I. Input Requirements
After the program starts the student needs to enter his/her details such as name, registration
number, course name which is taught by the faculty.
17
CUTM-CSE DEPT
II. Applying Procedure

The student enters the necessary details and then tries to access the materials for his/her
specific domain in the given time period.
III. Output Requirements

Admin views the questions asked by the students and can analyze their queries.
IV. Database Requirements

In this project an Oracle database is used to store the feedback data which is given by the
students and professors for the sentiment analysis to be done and produces the updated
results.
3.5.2 Non Functional Requirements

The major non-functional Requirements of the system are as follows
I. Usability
The system is designed in such a way that the user gives the required details and is very
user friendly.
II. Reliability
The system is more reliable because of the qualities that are inherited from the chosen
platform. The code built by using JSP is more reliable.
III. Performance
This system is developing in the high level languages and using the advanced front-end
and back-end technologies it will give response to the end user on client system with in
very less time.
IV. Supportability
The system is designed to be the cross platform supportable. The system is supported on a
wide range of hardware and any software platform, built into the system.
3.5.3 Software Requirements

 Operating System : Windows
 Web-Technology : JSP
 Front-End : HTML,CSS,JAVASCRIPT
18
CUTM-CSE DEPT
 Back-End : Oracle
 Web Server : Apache Tomcat Server
3.5.4 Hardware Requirements
 Pentium-IV (Processor).
 256 MB Ram
 512 KB Cache Memory
 Hard disk 10 GB
 Microsoft Compatible 101 or more Key Board
19
CUTM-CSE DEPT
4.1 Introduction to design
Design is the first step in the development phase for any techniques and principles for the purpose
of defining a device, a process or system in sufficient detail to permit its physical realization.
Once the software requirements have been analyzed and specified the software design involves
three technical activities - design, coding, implementation and testing that are required to build
and verify the software.
The design activities are of main importance in this phase, because in this activity, decisions
ultimately affecting the success of the software implementation and its ease of maintenance are
made. These decisions have the final bearing upon reliability and maintainability of the system.
Design is the only way to accurately translate the customer’s requirements into finished software
or a system. Design is the place where quality is fostered in development. Software design is a
process through which requirements are translated into a representation of software. Software
design is conducted in two steps. Preliminary design is concerned with the transformation of
requirements into data.
4.2 UML Diagrams
Actor:
A coherent set of roles that users of use cases play when interacting with the use `cases.
20
CUTM-CSE DEPT
Use case:
A description of sequence of actions, including variants, that a system performs that yields an
observable result of value of an actor.
UML stands for Unified Modeling Language. UML is a language for specifying, visualizing and
documenting the system. This is the step while developing any product after analysis. The goal
from this is to produce a model of the entities involved in the project which later need to be built.
The representation of the entities that are to be used in the product being developed need to be
designed. There are various kinds of methods in software design.
They are as follows:
 Use case Diagram

 Sequence Diagram
 Collaboration Diagram
 Activity Diagram
 State chat Diagram
Use Case Diagrams:

Use case diagrams model behavior within a system and helps the developers understand of what
the user require. The stick man represents what’s called an actor. Use case diagram can be useful
for getting an overall view of the system and clarifying who can do and more importantly what
they can’t do. Use case diagram consists of use cases and actors and shows the interaction between
the use case and actors.
 The purpose is to show the interactions between the use case and actor.
 To represent the system requirements from user’s perspective.
 An actor could be the end-user of the system or an external system.
A Use case is a description of set of sequence of actions. Graphically it is rendered as an ellipse
with solid line including only its name. Use case diagram is a behavioral diagram that shows a set
21
CUTM-CSE DEPT
of use cases and actors and their relationship. It is an association between the use cases and actors.
An actor represents a real-world object. Primary Actor – Sender, Secondary Actor Receiver.
Register
Sign In
Search
Material
Resource
Download
Resource
Upload
Interaction
Association
SignOut
22
CUTM-CSE DEPT
Sequence Diagram:
Sequence diagram and collaboration diagram are called INTERACTION DIAGRAMS. An
interaction diagram shows an interaction, consisting of set of objects and their relationship
including the messages that may be dispatched among them. A sequence diagram is an introduction
that empathizes the time ordering of messages. Graphically a sequence diagram is a table that
shows objects arranged along the X-axis and messages ordered in increasing time along the Y-
axis.
a) Student:
b) Professors/ Mentors:
23
CUTM-CSE DEPT
Collaboration Diagram:
A collaboration diagram is an introduction diagram that emphasizes the structural organization of
the objects that send and receive messages. Graphically a collaboration diagram is a collection of
vertices and arcs.
Activity Diagram:
The user logs in to the system using his username & password. Then he selects a topic and views
the learning materials .During learning, he can use the chat facility to clear doubts. Then he can
take test by selecting the difficulty level. A timer is set at the start of the test. If he is not able to
complete within the given time period, then marks are given for the marked questions only. If he
completes within the given period, then evaluation is done on submitting. He can also view the
test record. If he wants to improve his marks, he can repeat the learning process again.
a) User Registration Diagram:
24
CUTM-CSE DEPT
25
CUTM-CSE DEPT
b) User Login:
Class Diagram:
Class is nothing but a structure that contains both variables and methods. The Class Diagram
shows a set of classes, interfaces, and collaborations and their relating ships. There is most
26
CUTM-CSE DEPT
common diagram in modeling the object oriented systems and are used to give the static view of a
system. It shows the dependency between the classes that can be used in our system.
The interactions between the modules or classes of our projects are shown below. Each block
contains Class Name, Variables and Methods.
Class:
A description of set of objects that share the same attributes, operations, relationships, and
semantics
27
CUTM-CSE DEPT
Documentation of Class Diagram:

Admin class:
Main class in an e-learning system is admin. Username, password/id and designation or email are
the main attributes of this class.admin_user() is the method for user login.registration_user() is
used for checking whether the username and password are valid.loging_user() is for logging in
ans valid_loging_out() is for logging out from the system.
Student class:
It has many attributes including username, password, usn no and email id. Download()method is
used to view or download the files or material from the database. search() method is used to
search the particular information by selecting some topic.
Professor’s class:
It has many attributes including username, password, staff code. Download()method is used to
view or download the files or material from the database. search() method is used to search the
particular information by selecting some topic. upload_file() is the method for uploading files.
Publication Class:
It has many attributes like document code, author id, userlogin, password, and file types which
should be uploaded by the house of publication using upload() function.
State Chart Diagram:
28
CUTM-CSE DEPT
4.3 Data Flow Diagram:
The DFD takes an input-process-output view of a system i.e. data objects flow into the software,
are transformed by processing elements, and resultant data objects flow out of the software. Data
objects represented by labeled arrows and transformation are represented by circles also called as
bubbles. DFD is presented in a hierarchical fashion i.e. the first data flow model represents the
system as a whole. Subsequent DFD refine the context diagram (level 0 DFD), providing
increasing details with each subsequent level. The DFD enables the software engineer to develop
models of the information domain & functional domain at the same time. As the DFD is refined
into greater levels of details, the analyst perform an implicit functional decomposition of the
system. At the same time, the DFD refinement results in a corresponding refinement of the data as
it moves through the process that embody the applications. A context-level DFD for the system
the primary external entities produce information for use by the system and consume information
generated by the system. The labeled arrow represents data objects or object hierarchy.
Rules for DFD:

 Fix the scope of the system by means of context diagrams.
 Organize the DFD so that the main sequence of the actions
 Reads left to right and top to bottom.
 Identify all inputs and outputs.
 Identify and label each process internal to the system with Rounded circles.
 A process is required for all the data transformation and Transfers. Therefore, never
connect a data store to a data Source or the destinations or another data store with just
a Data flow arrow.
 Do not indicate hardware and ignore control information.
 Make sure the names of the processes accurately convey everything the process is done.
 There must not be unnamed process.
 Indicate external sources and destinations of the data, with Squares.
 Identify all data flows for each process step, except simple Record retrievals.
 Label data flow on each arrow.
29
CUTM-CSE DEPT
 Use details flow on each arrow.

 Use the details flow arrow to indicate data movements.
DATAFLOW DIAGRAMS:
Context level DFD:
This shows the context level diagram of the system. The users of the system are
Professors, students, toppers of college and mentors.
Level 1
Student:
30
CUTM-CSE DEPT
Professors:
31
CUTM-CSE DEPT
Uploading files:
32
CUTM-CSE DEPT
View files:
4.4 E-R Diagrams:
The Entity-Relationship (ER) model was originally proposed by Peter in 1976 [Chen76] as a way
to unify the network and relational database views. Simply stated the ER model is a conceptual
data model that views the real world as entities and relationships. A basic component of the model
is the Entity-Relationship diagram which is used to visually represent data objects. Since Chen
wrote his paper the model has been extended and today it is commonly used for database design
for the database designer, the utility of the ER model is:
 It maps well to the relational model. The constructs used in the ER model can easily be
transformed into relational tables.
 It is simple and easy to understand with a minimum of training. Therefore, the model can
be used by the database designer to communicate the design to the end user.
 In addition, the model can be used as a design plan by the database developer to implement
a data model in a specific database management software.
Connectivity and Cardinality:
The basic types of connectivity for relations are: one-to-one, one-to-many, and many-to-many.
A one-to-one (1:1) relationship is when at most one instance of a entity A is associated with one
instance of entity B. For example, "employees in the company are each assigned their own office.
For each employee there exists a unique office and for each office there exists a unique employee.
33
CUTM-CSE DEPT
A one-to-many (1:N) relationships is when for one instance of entity A, there are zero, one, or
many instances of entity B, but for one instance of entity B, there is only one instance of entity A.
An example of a 1:N relationships is a department has many employees each employee is assigned
to one department.
A many-to-many (M:N) relationship, sometimes called non-specific, is when for one instance of
entity A, there are zero, one, or many instances of entity B and for one instance of entity B there
are zero, one, or many instances of entity A. The connectivity of a relationship describes the
mapping of associated.
ER Notation:
There is no standard for representing data objects in ER diagrams. Each modeling methodology
uses its own notation. The original notation used by Chen is widely used in academics texts and
journals but rarely seen in either CASE tools or publications by non-academics. Today, there are
a number of notations used, among the more common are Bachman, crow's foot, and IDEFIX.
All notational styles represent entities as rectangular boxes and relationships as lines connecting
boxes. Each style uses a special set of symbols to represent the cardinality of a connection. The
notation used in this document is from Martin. The symbols used for the basic ER constructs are:
 Entities are represented by labeled rectangles. The label is the name of the entity. Entity
names should be singular nouns.
 Relationships are represented by a solid line connecting two entities. The name of the
relationship is written above the line. Relationship names should be verbs
 Attributes, when included, are listed inside the entity rectangle. Attributes which are
identifiers are underlined. Attribute names should be singular nouns.
 Cardinality of many is represented by a line ending in a crow's foot. If the crow's foot is
omitted, the cardinality is one.
34
CUTM-CSE DEPT
 Existence is represented by placing a circle or a perpendicular bar on the line.
35
CUTM-CSE DEPT
5.1 Front End Implementation
I. HTML
Hypertext Markup Language (HTML) is the standard markup language for documents designed
to be displayed in a web browser. It can be assisted by technologies such as Cascading Style
Sheets (CSS) and scripting languages such as JavaScript.
Web browsers receive HTML documents from a web server or from local storage and render the
documents into multimedia web pages. HTML describes the structure of a web
page semantically and originally included cues for the appearance of the document.
HTML elements are the building blocks of HTML pages. With HTML constructs, images and
other objects such as interactive forms may be embedded into the rendered page. HTML provides
a means to create structured documents by denoting structural semantics for text such as headings,
paragraphs, lists, links, quotes and other items. HTML elements are delineated by tags, written
using angle brackets. Tags such as <img /> and <input /> directly introduce content into the page.
Other tags such as <p> surround and provide information about document text and may include
other tags as sub-elements. Browsers do not display the HTML tags, but use them to interpret the
content of the page.
HTML can embed programs written in a scripting language such as JavaScript, which affects the
behavior and content of web pages. Inclusion of CSS defines the look and layout of content.
The World Wide Web Consortium (W3C), former maintainer of the HTML and current maintainer
of the CSS standards, has encouraged the use of CSS over explicit presentational HTML since
1997.
II. CSS
Cascading Style Sheets (CSS) is a style sheet language used for describing the presentation of a
document written in a markup language like HTML.[1] CSS is a cornerstone technology of
the World Wide Web, alongside HTML and JavaScript.
36
CUTM-CSE DEPT
CSS is designed to enable the separation of presentation and content, including layout, colors,
and fonts. This separation can improve content accessibility, provide more flexibility and control
in the specification of presentation characteristics, enable multiple web pages to share formatting
by specifying the relevant CSS in a separate .css file, and reduce complexity and repetition in the
structural content.
Separation of formatting and content also makes it feasible to present the same markup page in
different styles for different rendering methods, such as on-screen, in print, by voice (via speech-
based browser or screen reader), and on Braille-based tactile devices. CSS also has rules for
alternate formatting if the content is accessed on a mobile device.
The name cascading comes from the specified priority scheme to determine which style rule
applies if more than one rule matches a particular element. This cascading priority scheme is
predictable.
The CSS specifications are maintained by the World Wide Web Consortium (W3C). Internet
media type (MIME type) text/css is registered for use with CSS by RFC 2318 (March 1998). The
W3C operates a free CSS validation service for CSS documents.
In addition to HTML, other markup languages support the use of CSS including XHTML, plain
XML, SVG, and XUL.
III. JavaScript
JavaScript , often abbreviated as JS, is a high-level, interpreted scripting language that conforms
to the ECMAScript specification. JavaScript has curly-bracket syntax, dynamic typing, prototype-
based object-orientation, and first-class functions.
Alongside HTML and CSS, JavaScript is one of the core technologies of the World Wide
Web. JavaScript enables interactive web pages and is an essential part of web applications. The
vast majority of websites use it, and major web browsers have a dedicated JavaScript engine to
execute it.
As a multi-paradigm language, JavaScript supports event-driven, functional,

and imperative (including object-oriented and prototype-based) programming styles. It
37
CUTM-CSE DEPT
has APIs for working with text, arrays, dates, regular expressions, and the DOM, but the
language itself does not include any I/O, such as networking, storage, or graphics facilities. It
relies upon the host environment in which it is embedded to provide these features.
Initially only implemented client-side in web browsers, JavaScript engines are now embedded in
many other types of host software, including server-side in web servers and databases, and in non-
web programs such as word processors and PDF software, and in runtime environments that make
JavaScript available for writing mobile and desktop applications, including desktop widgets.
The terms Vanilla JavaScript and Vanilla JS refer to JavaScript not extended by any frameworks
or additional libraries. Scripts written in Vanilla JS are plain JavaScript code.
Although there are similarities between JavaScript and Java, including language name, syntax,
and respective standard libraries, the two languages are distinct and differ greatly in design.
JavaScript was influenced by programming languages such
as Self and Scheme. The JSON serialization format, used to store data structures in files or
transmit them across networks, is based on JavaScript.
5.2 Back End Implementation
I. JSP
Java Server Pages (JSP) is a technology that helps software developers created dynamically
generated web pages based on HTML, XML, or other document types. JSP may be viewed as a
high-level abstraction of Java servlets.
II. AJAX
AJAX is a group of interrelated web development techniques used on the client-side to create
asynchronous web applications with Ajax, web applications can send data to, and retrieve data
from, a server asynchronously (in the background) without interfering with the display and
behavior of the existing page.
5.3 Modules Description
38
CUTM-CSE DEPT
5.3.1 Admin Module

 Register
To be authenticated first have to be registered.
 Login
Registered User Can be allowed to view inner details for which he permitted.
 Change Password and Forgot Password
User has rights to modify his login details & also be informed through mails if he is
unable to login.
 Student Modifying Details

Admin can be modified to change status of each user.
 Departments entering / Modifying Details
New departments adding and old department deletions are spend by this user.
 Professors Details – Modifying Details
According to staff he can add or delete Instructors for specific platform,
5.3.2 Module
 Register
To be authenticated firest have to be registered.
 Login
The Registered User Can be Allowed to view inner details for which he permitted.
 Change Password and Forgot Password
User has rights to modify his loging details& also be informed through mails if he is
unable to login
 Answer question – Department verifying
According to flow of questions & Technology he can add the answers into the database.
 Update answers – Department Verifying
If any corrections in data of answers he can modify them.
 Upload materials
He will be updating materials periodically.
39
CUTM-CSE DEPT
 Update materials
He has rights to modify materials.
 View query Details
Can view at attended students who has registered.
5.3.2 Student Module
 Register
To be authenticated first have to be registered
 Login
The Registered User Can be allowed to view inner details for which he permitted.
 Students can easily access learning materials from anywhere at any time.
 Download Notes and ppts on various topics available.
 Students can also discuss with the Professors to clear their doubts.
 Logout
After the process of examination he turned to Logout page.
5.4 Sample Code
I. Index
II. Admin
III. Login
IV. Logout
5.5 Database Tables
I. USER REG TABLE
40
CUTM-CSE DEPT
NAME NULL/NOTNULL TYPE KEY

ID NOTNULL INT PRIMARYKEY
NAME NULL VARCHAR(50)
DOB NULL DATETIME
GENDER NULL VARCHAR(10)
BRANCH NULL VARCHAR(20)
COLLEGE NULL VARCHAR(50)
UID NULL VARCHAR(50)
PWD NULL VARCHAR(20)
RPWD NULL VARCHAR(20)
UTYPE NULL VARCHAR(20)
QUE NULL VARCHAR(500)
ANS NULL VARCHAR(500)
41
CUTM-CSE DEPT
6. Introduction to Testing
Testing is a process of executing a program with the intent of finding an error. Testing is a
crucial element of software quality assurance and presents ultimate review of specification,
design and coding.
System Testing is an important phase. Testing represents an interesting anomaly for the software.
Thus a series of testing are performed for the proposed system before the system is ready for user
acceptance testing.
A good test case is one that has a high probability of finding an as undiscovered error. A
successful test is one that uncovers an as undiscovered error.
Testing Objectives:
1. Testing is a process of executing a program with the intent of finding an error
2. A good test case is one that has a probability of finding an as yet undiscovered error
3. A successful test is one that uncovers an undiscovered error
Testing Principles
1. All tests should be traceable to end user requirements
2. Tests should be planned long before testing begins
3. Testing should begin on a small scale and progress towards testing in large
4. Exhaustive testing is not possible
5. To be most effective testing should be conducted by a independent third party
The purpose of testing is to discover errors. Testing is the process of trying to discover every
conceivable fault or weakness in a work product. It provides a way to check the functionality of
components, sub-assemblies, assemblies and/or a finished product It is the process of exercising
software with the intent of ensuring that the
Software system meets its requirements and user expectations and does not fail in an unacceptable
manner. There are various types of test. Each test type addresses a specific testing requirement.
42
CUTM-CSE DEPT
6.1. Unit Testing
Unit testing involves the design of test cases that validate that the internal program logic is
functioning properly, and that program inputs produce valid outputs. All decision branches and
internal code flow should be validated. It is the testing of individual software units of the
application .it is done after the completion of an individual unit before integration. This is a
structural testing, that relies on knowledge of its construction and is invasive. Unit tests perform
basic tests at component level and test a specific business process, application, and/or system
configuration. Unit tests ensure that each unique path of a business process performs accurately to
the documented specifications and contains clearly defined inputs and expected results.
6.2. Integration Testing
Integration tests are designed to test integrated software components to determine if they actually
run as one program. Testing is event driven and is more concerned with the basic outcome of
screens or fields. Integration tests demonstrate that although the components were individually
satisfaction, as shown by successfully unit testing, the combination of components is correct and
consistent. Integration testing is specifically aimed at exposing the problems that arise from the
combination of components.
6.3. Functional Testing
Functional tests provide systematic demonstrations that functions tested are available as specified
by the business and technical requirements, system documentation, and user manuals.
Functional testing is centered on the following items

Valid Input - identified classes of valid input must be accepted.
Invalid Input - identified classes of invalid input must be rejected.
Functions - identified functions must be exercised.
Output - identified classes of application outputs must be exercised.
43
CUTM-CSE DEPT
Systems/Procedures: interfacing systems or procedures must be invoked.

Organization and preparation of functional tests is focused on requirements, key functions, or
special test cases. In addition, systematic coverage pertaining to identify Business process flows;
data fields, predefined processes, and successive processes must be considered for testing. Before
functional testing is complete, additional tests are identified and the effective value of current tests
is determined.
6.4. System Testing
System testing ensures that the entire integrated software system meets requirements. It tests a
configuration to ensure known and predictable results. An example of system testing is the
configuration oriented system integration test. System testing is based on process descriptions and
flows, emphasizing pre-driven process links and integration points.
6.5. White Box Testing
White Box Testing is a testing in which in which the software tester has knowledge of the inner
workings, structure and language of the software, or at least its purpose. It is purpose. It is used to
test areas that cannot be reached from a black box level.
6.6. Black Box Testing
Black Box Testing is testing the software without any knowledge of the inner workings, structure
or language of the module being tested. Black box tests, as most other kinds of tests, must be
written from a definitive source document, such as specification or requirements document, such
as specification or requirements document. It is a testing in which the software under test is treated,
as a black box .you cannot “see” into it. The test provides inputs and responds to outputs without
considering how the software works.
44
CUTM-CSE DEPT
6.7. Acceptance Testing
User Acceptance Testing is a critical phase of any project and requires significant participation by
the end user. It also ensures that the system meets the functional requirements.
Test Results: All the test cases mentioned above passed successfully. No defects encountered.
6.8. Test Cases
In general a test case is a set of test data and test programs and their expected results. A test case
in software engineering normally consists of a unique identifier, requirement references from a
design specification, preconditions, events, a series of steps (also known as actions) to follow,
input, output and it validates one or more system requirements and generates a pass or fail.
The mechanism for determining whether a software program or system has passed or failed such
a test is known as a test oracle. In some settings, an oracle could be a requirement or use case,
while in others it could be a heuristic. It may take many test cases to determine that a software
program or system is considered sufficiently scrutinized to be released. Test cases are often
referred to as test scripts, particularly when written. Written test cases are usually collected
into test suites. If a requirement has sub-requirements, each sub-requirement must have at least
two test cases. Written test cases should include a description of the functionality to be tested, and
the preparation required to ensure that the test can be conducted.
6.8.1. Test Case Format
Test Cases usually have the following components:

(i) Test Case Summary
(ii) Initial Condition
(iii) Steps to run the test case
(iv) Expected behavior/outcome
45
CUTM-CSE DEPT
6.8.1.1. TEST CASE 1
Test Aspect User enters the details
Intial condition Should select the registration page
Steps to run Provide the feedback
Expected Output To read text from the text box
Actual Output It is shown in the below example.
Form
_____
Error
_____
6.8.1.2. TEST CASE 2
Test Aspect Admin selects faculty name
Intial condition Select the admin option
Steps to run Analyze the data while submission
Expected Output Displays the admin page
Actual Output It is shown in the below example.
Admin Login Page

______
Error
46
CUTM-CSE DEPT
______
6.8.1.4. POSITIVE TEST CASE RESULT
S .No Test case Description Expected value Actual value Result
1 Student Module Updating Queries Showing the True

updated queries
2 Admin Module Analyze and show Updated queries True
the queries
Table 6.8.5. Positive Test Case Result
6.8.1.6. NEGATIVE TEST CASE RESULT
S .No Test case Description Expected value Actual value Result
1 Student Module Updating queries Doesn’t exit False
2 Admin Module Analyze and show Shows none False

queries
Table 6.8.6. Negative Test Case Result
47
CUTM-CSE DEPT
7.INTERFACES:
------------
48
CUTM-CSE DEPT
8. Maintenance
AS the number of computer based systems, grieve libraries of computer software began to expand.
In house developed projects produced tones of thousand soft program source statements. Software
products purchased from the outside added hundreds of thousands of new statements. A dark cloud
appeared on the horizon. All of these programs, all of those source statements-had to be corrected
when false were detected, modified as user requirements changed, or adapted to new hardware that
was purchased. These activities were collectively called software Maintenance.
The maintenance phase focuses on change that is associated with error correction, adaptations
required as the software's environment evolves, and changes due to enhancements brought about
by changing customer requirements. Four types of changes are encountered during the
maintenance phase.
o Correction
o Adaptation
o Enhancement
o Prevention
Correction:
Even with the best quality assurance activities is lightly that the customer will uncover
defects in the software. Corrective maintenance changes the software to correct defects.
Maintenance is a set of software Engineering activities that occur after software has been
delivered to the customer and put into operation. Software configuration management is a
set of tracking and control activities that began when a software project begins and
terminates only when the software is taken out of the operation.
We may define maintenance by describing four activities that are undertaken after a
program is released for use:
o Corrective Maintenance
o Adaptive Maintenance
o Perfective Maintenance or Enhancement
o Preventive Maintenance or reengineering
Only about 20 percent of all maintenance work are spent "fixing mistakes". The remaining
49
CUTM-CSE DEPT
80 percent are spent adapting existing systems to changes in their external environment,
making enhancements requested by users, and reengineering an application for use.
Adaptation:
Over time, the original environment (E>G., CPU, operating system, business rules, external
product characteristics) for which the software was developed is likely to change. Adaptive
maintenance results in modification to the software to accommodate change to its external
environment.
Enhancement:
As software is used, the customer/user will recognize additional functions that will provide benefit.
Perceptive maintenance extends the software beyond its original function requirements.
Prevention:
Computer software deteriorates due to change, and because of this, preventive
maintenance, often called software re-engineering, and must be conducted to enable the
software to serve the needs of its end users. In essence, preventive maintenance makes
changes to computer programs so that they can be more easily corrected, adapted, and
enhanced. Software configuration management (SCM) is an umbrella activity that is
applied throughout the software process. SCM activities are developed to
50
CUTM-CSE DEPT
9. Conclusion
The package was designed in such a way that future modifications can be
done easily. The following conclusions can be deduced from the development of the project.
 Automation of the entire system improves the efficiency

 It provides a friendly graphical user interface which proves to be better when compared
to the existing system.
 It gives appropriate access to the authorized users depending on their permissions.
 It effectively overcomes the delay in communications.
 Updating of information becomes so easier.
 System security, data security and reliability are the striking features.
 The System has adequate scope for modification in future if it is necessary.
51
CUTM-CSE DEPT
10. Future Enhancement
E-Learning Resource Locator provides an easy way to access this website and get study materials
and textbooks. This is time efficient when compared to other search engines. Here we can get
materials directly just by providing the publications name and can download any course materials.
By this it will be easy to the students, professors, and other users to access materials from
anywhere. In some websites they cannot provide permissions for downloading materials. This
problem is solved by using this application. In this application power point presentations can also
be available where users can understand it better.
This application avoids the manual work and the problems concern with it. It is an easy way to
obtain the information regarding the different subject’s information that are currently issued. Well
I and my team members have worked hard in order to present an improved website better than the
existing one’s regarding the information about the various activities. Still, we found out that the
project can be done in a better way.
52
CUTM-CSE DEPT
11. Bibliography
 BEGINNING PHP 5 ---DAVE MERCER
 BLACK BOOK HTML ---WILEY DREAMTECH
 PHP AND MYSQL WEB DEVELOPMENT --- LUKEWELLING,LAURA
 MICROSOFT SQL SERVER-2000 ---RANKIN, PAUL & JENSEN
 SQL SERVER-2000 ---DUSAN PETKOVIC
 PHP IN A NUTSHELL --- PAUL HUDSON
53
CUTM-CSE DEPT

E-Learning Resource Locator

Uploaded by

Copyright:

Available Formats

You might also like

E-Learning Resource Locator

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

E-Learning Resource Locator

Uploaded by

Copyright:

Available Formats

E-Learning Resource Locator

“E Leaning-Resource Technology” is education based website/software , helping students to get

1.2 Purpose of the project

1.3 Goal of the project

The proposed E-Learning Resource System has the following features.

 Only registered students and Professors can access the system.

1.4 Scope of the project

The basic users involved in this project is

2.1 Implementation of environment

Unified Modeling Language, is a standardized modeling language consisting of an integrated set

2.2 Project Planning and Scheduling

2.3 Project Development Approach

Application System Development – A Life cycle Approach

Installation and operation

2.4 Project Plan

Phases No. of days Deliverables of the

Design 07 Design document

3.1 Existing System

 No authentication to access the data.

3.2 Problem Statement

3.3 Proposed System

It contains the following elements:-

 PPT (pload/del)/Video(upload/del): It displays a list of ppts & videos posted by

3.4 Feasibility Study

II. Economical Feasibility

III. Social Feasibility

3.5 Software Requirement Specification

3.5.1 Functional Requirements

It defines a function of a software system or its component. A function is described as a set of

II. Applying Procedure

III. Output Requirements

IV. Database Requirements

3.5.2 Non Functional Requirements

3.5.3 Software Requirements

3.5.4 Hardware Requirements

4.1 Introduction to design

4.2 UML Diagrams

 Use case Diagram

Use Case Diagrams:

a) User Registration Diagram:

Documentation of Class Diagram:

State Chart Diagram:

4.3 Data Flow Diagram:

Rules for DFD:

 Use details flow on each arrow.

4.4 E-R Diagrams:

Connectivity and Cardinality:

 Existence is represented by placing a circle or a perpendicular bar on the line.

5.1 Front End Implementation

As a multi-paradigm language, JavaScript supports event-driven, functional,

5.2 Back End Implementation

5.3 Modules Description

5.3.1 Admin Module

 Student Modifying Details

5.3.2 Student Module

5.4 Sample Code

5.5 Database Tables