CHAPTER 1

INTRODUCTION
THIS PROJECT IS AIMED AT DEVELOPING E-LEARNING PLATFORM FOR STUDENTS
AND TEACHERS. IT IS AN APPLICATION WHICH CONNECTS STUDENTS AND
TEACHERS, WHERE STUDENTS CAN REGISTER FOR THEIR INTERESTED COURSE
WHEREAS TEACHERS CAN DISPLAY THE CONTENT WITH DIGITAL DEVICE THAT IS
HELPING TO QUICK ACCESS TO OTHERS. TODAY’S LEARNERS WANT RELEVANT,
MOBILE, SELF-PACED AND PERSONALIZED CONTENT. THIS NEED IS FULFILLED WITH
E-LEARNING; HERE, STUDENTS CAN LEARN AT THEIR OWN COMFORT AND
REQUIREMENT. THE ONLINE LEARNING METHOD IS BEST SUITED FOR EVERYONE.
ONLINE EDUCATIONAL COURSES CAN BE TAKEN UP BY OFFICE GOERS AND
HOUSEWIVES TOO, AT THE TIME THAT SUITS.

E-learning refers to the use of various kinds of electronic media and information and
communication technologies (ICT) in education. E-learning is an inclusive terminology that
encompasses all forms of educational technology that electronically or technologically support
learning and teaching. Depending on whether a particular aspect, component or delivery method
is given emphasis, eLearning may be termed technology-enhanced learning (TEL), computer-
based training (CBT), internet-based training (IBT), web-based training (WBT), online
education, virtual education, or digital educational collaboration. E-learning includes numerous
types of media that deliver text, audio, images, animation, and streaming video, and includes
technology applications and processes such as audio or video tape, satellite TV, CD-ROM, and
computer-based learning, as well as local intranet/extranet and web-based learning. Information
and communication systems, whether free-standing or based on either local networks or the
Internet in networked learning, underlay many e-learning processes. E-learning can occur in or
out of the classroom. It can be self-paced, asynchronous learning or may be instructor-led,
synchronous learning.

1.1 PROJECT DESCRIPTION:

The E-learning system enables the student login into his account and creates a profile,
update profile. He/she can search for their interested course then they can register for the
course and learn at their own comfort and requirement with the lectures provided by the
expert teachers so the students can easily acquire the skills and knowledge through these
lectures. Whereas the teachers can build a course curriculum and customize the vast
courses into short and crisp modules using E-learning advanced and robust tools.

This E-learning system is a computer based educational tool or system that is developed for
a specific end user. The system was built after collecting the requirements by the specific
end user. It was tested by the user several times and changes suggested.
CHAPTER 2

LITERATURE SURVEY

2.1 INTRODUCTION TO EXISTING SYSTEM

Existing system is based on manual work and all the process are done manually, so they
maintain records and files for creating a new report. They maintain the records of students,
so they keep each and every information regarding them manually in books. They maintain
the record of the courses so they keep each and every information regarding the courses.
Building reliable statistics and preparing and updating student details manually Add a lot of
pressure and the lack of time doubles it

PROBLEMS FACED BY EXISTING SYSTEMS:

The phase of system analysis process deals with problems that are affecting in the current
manual system. The problems are those, which are affecting the organization in daily
routine work.

As the growing trend in InfoTech World of computers need of accuracy, perfectness, speed
and high memory data storage is a must. Each and every problem must be solved with a
least amount of time and energy.

The problems faced by existing system are described as below

1. Lack of Time for Planning.

2. Distraction.

3. Lot of paperwork.

4. Editing of Data.

LACK OF TIME FOR PLANNING:

Unlike in the past when teachers can't just finish off their syllabus and typically evaluate
the students. The situations are more challenging today. They will have to handle multiple
roles in the classroom

Updating the subject to new demands, correcting materials, content presentations,

managing field trips as well as bringing in new creative approaches to meet the present
educational trends are a few among them. Teachers are finding it really challenging to
handle multiple roles as they lack enough of time for planning.
DISTRACTION:

Updating the subject to new demands, correcting materials, content presentations,

managing field trips as well as bringing in new creative approaches to meet the present
educational trends are a few among them. Teachers are finding it really challenging to
handle multiple roles as they lack enough of time for planning.

LOT OF PAPERWORK:

In addition to preparing quality teaching content, it is common for school management to

hand them with many additional roles including psycho-educator, social worker, counsellor
and a lot more.Building reliable statistics and preparing and updating student growth
indicators are one of the important classrooms challenges they have to handle in addition to
teaching notes. Such excessive paper works take a lot of time out of their regular schedules.
This can seriously impact the quality of work they deliver.

EDITING OF DATA:

Manual written data cannot be changed or edited once written. If there is a mistake and if
we try to rub and write it again it makes the register very dirty and untidy, which creates a
bad impression of the business. If data if entered incorrect the whole documents get
incorrect while editing wrongly entered data cannot easily solve errors.

Proposed System:

In this paper we have proposed a Ontology based E Learning Management System where basic
tools administration, Instructor, Learner are interrelated through Learning Resource (RDF) and
Ontology-based Contextual Knowledge (OWL). Where each tool contains several elements that
are given in the fig-1.This model is designed with six subsections , that are marked(1,2,3..6) in
our Proposed ontology based E-LMS model in fig2. Fig. 1: Elements of Proposed ontology
based E Learning

Advantages of E-learning Management System:

1. Easy in maintaining information.

2. Less work for admin.

3. Quick delivery of lessons.

4. Less time consuming

The main features of E-learning Management System are given below:

1. As computer can store large amount of data it is very useful to store information of
such a large database.

2. Inconsistency caused due to changes in the database is removed as a separate database

can be maintained for total number of customers. So, the database is directly updated in
response to the any change taking place and we don't have to go through all the forms
once again.

3. The admin can easily store and alter students and teachers details whenever new
student and teacher get registered with E-learning system.

4. Enables to view large volume of data in a short period of time.

5. Reduce storage space.

6. Helps to make well formatted reports.

7. It provides better security.

8. It tracks all information of students, teachers, courses etc.

9. E-learning helps in creating and communicating new training, policies, concepts, and
ideas whether it is for formal education or entertainment, eLearning is very quick way of
learning.

10. E-learning is the way to provide quick delivery of lessons. As compared to

traditional classroom teaching method, this mode has relatively quick delivery cycles.

11. E-learning enables educators to get a higher degree of coverage to communicate the
message in a consistent way for their target audience. This ensures that all learners
receive the same type of training with this learning mode.

12. E-learning is cost effective as compared to traditional forms of learning. The reason
for this price reduction is because learning through this mode happens quickly and easily.

2.3 E-learning tools and technologies used in online training

E-learning makes use of many technologies – some of which have been developed specifically for it,
whilst others conveniently complemented the learning process, for example, computer games.

Communication technologies are also widely used in e-learning. Starting with the use of email and
instant messaging, message forums and social networks, we see a plethora of tools that any internet
user would use in any case.There are also some technologies that work in a complementary manner to
other software and enable new features, for example software that adds a whiteboard on your video
conferencing tool to allow you or your peers to make changes on other people’s work for review, or
screen-sharing which allows someone to make a presentation while still making comments and giving
input using the microphone.

E-learning makes good use of database and CMS (Content Management System) technologies. These
two work hand in hand to store your course content, test results and student records. The data is stored
in the database and the CMS provides a user

interface for you to add, update and delete data. A good LMS will often provide reporting tools to
generate and store progress reports.

Elearning tools and technologies used to improve the quality of content are manifold. Software like
Flash and PowerPoint will help you make your presentations slick and interesting, with high quality,
graphically rich content. There are word processing packages and HTML editors available these days
that make formatting your text or web pages a breeze, removing a lot of the complexity. There are also
lots of online services available that you can use to create interactive elements for your courses such as
quizzes and games.

2.4 HARDWARE AND SOFTWARE REQUIREMENTS

SOFTWARE REQUIREMENTS:

OPERATING SYSTEM
WINDOWS 10
FRONT END VISUAL STUDIO
BACKEND ORACLE

HARDWARE REQUIREMENTS:

MONITOR DELL
KEYBOARD QWERTY KEYBOARD

MOUSE WIRELESS OPTICAL

RAM 4GBRAM

SSD 256 SSD

PROCESSOR RYZEN3AMD
CHAPTER 3

Software Requirement Specification:

The production of the requirements stage of the software development process is Software
Requirements Specifications (SRS) (also called a requirements document). This report
lays a foundation for software engineering activities and is constructing when entire
requirements are elicited and analysed. SRS is a formal report, which acts as a
representation of software that enables the customers to review whether it (SRS) is
according to their requirements. Also, it comprises user requirements for a system as well
as detailed specifications of the system requirements.

The SRS is a specification for a specific software product, program, or set of applications
that perform particular functions in a specific environment. It serves several goals
depending on who is writing it. First, the SRS could be written by the client of a system.
Second, the SRS could be written by a developer of the system. The two methods create
entirely various situations and establish different purposes for the document altogether. The
first case, SRS, is used to define the needs and expectation of the users. The second case,
SRS, is written for various purposes and serves as a contract document between customer
and developer.

Following are the features of a good SRS document:

1. Correctness: User review is used to provide the accuracy of requirements stated in the
SRS. SRS is said to be perfect if it covers all the needs that are truly expected from the
system.

2. Completeness: All essential requirements, whether relating to functionality,

performance, design, constraints, attributes, or external interfaces.

3. Consistency: The SRS is consistent if, and only if, no subset of individual
requirements described in its conflict. There are three types of possible conflict in the
SRS:

4. Unambiguousness: SRS is unambiguous when every fixed requirement has only one
interpretation. This suggests that each element is uniquely interpreted. In case there is a
method used with multiple definitions, the requirements report should determine the
 implications in the SRS so that it is clear and simple to understand.

5. Ranking for importance and stability: The SRS is ranked for importance and
stability if each requirement in it has an identifier to indicate either the significance or
stability of that particular requirement.
6. Modifiability: SRS should be made as modifiable as likely and should be capable of
quickly obtain changes to the system to some extent. Modifications should be perfectly
indexed and cross-referenced. Verifiability: SRS is correct when the specified
requirements can be verified with a cost effective system to check whether the final
software meets those requirements. The requirements are verified with the help of
reviews.

7. Traceability: The SRS is traceable if the origin of each of the requirements is clear
and if it facilitates the referencing of each condition in future development or
enhancement documentation.

3.1Functional Requirements:

General description of inputs and outputs. The system has basically a menu driven input format.
The officer has to choose from the menu, the appropriate options.

3.2External Interface Requirements:

User interface is of the most important parts of the effective software. A menu driven
system is to be developed using which the user does it. The interface should reinforce.

Hardware and Software Specifications:

Hardware Specification:

Processor Clock Speed 1.80 GHz or Above

RAM

Hard Disk 2.00 GB or Above

System Type 80GB or Above
Monitor
32 - bit Operating System or Above
Input Type
Any Display Unit
 Any Input
Devices

• Software Specification:

Operating Windows 7 or Above

System
Framework
.Net
Frontend VB

Backend SQL Server

Chapter 4

Software Development Life Cycle (SDLC):

SDLC is a systematic process for building software that ensures the quality and
correctness of the software built. SDLC process aims to produce high-quality software
that meets customer expectations. The system development should be complete in the
pre-defined time frame and cost. SDLC consists of a detailed plan which explains how to
plan, build, and maintain specific software. Every phase of the SDLC life Cycle has its
own process and deliverables that feed into the next phase. SDLC stands for Software
Development Life Cycle and is also referred to as the Application Development life-
cycle.

Phases of SDLC are:

• Requirement Analysis

• Design
• Implementation

• Testing

• Evolution

1. Requirement Analysis:

The requirement is the first stage in the SDLC process. It is conducted by the senior team
members with inputs from all the stakeholders and domain experts in the industry.
Planning for the quality assurance requirements and reorganization of the risks involved
is also done at this stage
 2. Design:

In this phase, the system and software design documents are prepared as per the
requirement specification document. This helps define overall system architecture.

High-Level Design (HLD)

• Brief description and name of each module

• An outline about the functionality of every module

• Interface relationship and dependencies between modules

Low-Level Design (LLD)

• Functional logic of the modules

• Database tables, which include type and size

• Complete detail of the interface

3. Implementation:

Once the system design phase is over, the next phase is coding. In this phase, developers
start build the entire system by writing code using the chosen programming language. In
the coding phase, tasks are divided into units or modules and assigned to the various
developers. It is the longest phase of the Software Development Life Cycle process.

4. Testing:

Once the software is complete, and it is deployed in the testing environment. The testing
team starts testing the functionality of the entire system. This is done to verify that the
entire application works according to the customer requirement. During this phase, QA
and testing team may find some bugs/defects which they communicate to developers.
The development team fixes the bug and send back to QA for a re-test. This process
continues until the software is bug-free, stable, and working according to the business
needs of that system.

5. Evolution:

Once the system is deployed, and customers start using the developed system, following
3 activities occur

• Bug fixing - bugs are reported because of some scenarios which are not tested at all

• Upgrade - Upgrading the application to the newer versions of the Software

Waterfall Model (Linear Sequential Model):

The Waterfall model-is a sequential development process that flows like a waterfall
through all phases of a project (analysis, design, development, and testing, for example),
with each phase completely wrapping up before the next phase begins.

It is said that the Waterfall methodology follows the adage to "measure twice, cut once." The
success of the Waterfall method depends on the amount and quality of the work done on
the front end, documenting everything in advance, including the user interface, user
stories, and all the features' variations and outcomes. With the majority of the research done
upfront, estimates of the time needed for each requirement are more accurate, and this can
provide a more predictable release date. With a Waterfall project, if parameters change
along the way, it's harder to change course than it is with Agile methodology.

Requirement
Waterfall Model
Analysis
System
Design
I

Implementation

Deployment

Maintenance

The Waterfall methodology follows a chronological process and works based on fixed
dates, requirements, and outcomes. With this method, the individual execution teams
aren't required to be in constant communication and, unless specific integrations are
required, are usually self contained. Team members also tend to work independently and
aren't expected to provide status reports as often as with the Agile approach. Usually, one
phase doesn't begin until the previous one is finished.

1. Requirements:
The Waterfall methodology depends on the belief that all project requirements
can be gathered and understood upfront. The project manager does their best to
get a detailed understanding of the project sponsor's requirements. Written
requirements, usually contained in a single document, are used to describe each
stage of the project.
 2. Design:
Here, software developers design a technical solution to the problems set out by
the product requirements, including scenarios, layouts, and data models. First, a
higher level or logical design is created that describes the purpose and scope of
the project, the general traffic flow of each component, and the integration points.
Once this is complete, it is transformed into a physical design using specific
hardware and software technologies.

3. Implementation:
Once the design is complete, technical implementation starts. This might be the
shortest phase of the Waterfall process, because painstaking research and design
have already been done. In this phase, programmers code applications based on
project requirements and specifications, with some testing and implementation
taking place as well. If significant changes are required during this stage, this may
mean going back to the design phase.
4. Verification:
Before a product can be released to customers, testing needs to be done to ensure the
product has no errors and all of the requirements have been completed, ensuring a good
user experience with the software. The testing team will tum to the design documents,
personas, and user case scenarios supplied by the product manager to create their test cases.
5. Deployment:
The deployment phase is the final step in the software development life cycle and delivers
the final product to the customer in a live production environment

6. Maintenance:

Once the software has been deployed in the market or released to customers, the maintenance
phase begins. As defects are found and change requests come in from users, a team will be
assigned to take care of updates and release new versions of the s0ftware.
Advantages of Waterfall Model:

• Developers can catch design errors during the analysis and design stages, helping them
to avoid writing faulty code during the implementation phase.

• The total cost of the project can be accurately estimated, as can the timeline, after
the requirements have been defined.

• With the structured approach, it is easier to measure progress according to clearly

defined milestones.
 Disadvantages of Waterfall Model:

• Projects can take longer to deliver with this chronological approach than with an
iterative one, such as the Agile method.

• Clients often don't fully know what they want at the front end, opening the door to
requests for changes and new features later in the process when they're harder to
accommodate.

• Clients are not involved in the design and implementation stages.

CHAPTER 5

ER DIAGRAM

(Entity - Relationship)

ENTITY RELATIONSHIP DIAGRAM:

An entity-relationship model (or ER model) describes interrelated things of interest in a

specific domain of knowledge. A basic ER model is composed of entity types (which
classify the things of interest) and specifies relationships that can exist between entities
(instances of those entity types).

software engineering, an ER model is commonly formed to represent things a business

needs to remember in order to perform business processes. Consequently, the ER model
becomes an abstract data model, that defines a data or information structure which can be
implemented in a database, typically a relational database.

Entity-relationship modelling was developed for database and design by Peter Chen and
published in a 1976 paper,[1] with variants of the idea existing previously.[2] Some ER
models show super and subtype entities connected by generalization-specialization
relationships,[3] and an ER model can be used also in the specification of domain-specific
ontologies.
 Data Flow Diagram:

Username Password

Create Create Update

Update Student Teacher Upload Files

Enroll For View

Courses
Students

View View
Courses Teachers

CHAPTER 6
Implementation:

Implementation is the stage of the project when the theoretical design is turned out into a
working system. Thus, it can be considered to be the most critical stage in achieving a
successful new system and in giving the user, confidence that the new system will work
and be effective. The implementation stage involves careful planning, investigating of the
existing system and its constraints on implementation, designing of methods to achieve
used over and evaluation of changeover methods.
Technologies used:

VB.NET

• It is an object-oriented programming language that follows various oops concepts such

as abstraction, encapsulation, inheritance, and many more. It means that everything in
VB.NET programming will be treated as an object.

• This language is used to design user interfaces for window, mobile, and web-based

• It is not a case sensitive language like other languages such as C++, java, etc.

• It supports Boolean condition for decision making in programming.

• It also supports the multithreading concept, in which you can do multiple tasks at the
same time.

• It provides simple events management in .NET application.

SQL Server:

• Its main purpose is to build and maintain databases.

• It is used to analyze the data using SQL Server Analysis Services (SSAS).

• It is used to generate reports using SQL Server Reporting Services (SSRS).

• It is used to perform ETL operations using SQL Server Integration Services (SSIS).

DATABASE MANAGEMENT SYSTEM (DBMS):

A DATABASE MANAGEMENT SYSTEM IS A COLLECTION OF PROGRAMS THAT ENABLES
USER TO CREATE AND MAINTAIN A DATABASE. THE DBMS FACILITATES THE PROCESS
OF DEFINING, CONSTRUCTING AND MANIPULATING DATABASE FOR VARIOUS
APPLICATIONS. DEFINING A DATABASE INVOLVES SPECIFYING, DATABASE
STRUCTURES, TYPES AND CONSTRAINTS FOR THE DATA TO BE STORED IN THE
DATABASE, BASED ON THE MINI-WORLD BEING MODELLED

Constructing the database is the process of storing the data itself on some storage
medium that is controlled by the DBMS. Manipulating a database includes functions
such as querying the database to reflect changes in the mini world, generating the reports
 from the data. The primary objective of a DBMS to provide environment to retrieve and
store database information. Database system supports multi user environment. It is an
integrated collection of related files along with details of the interpretation of the data
contained therein data and facts where conclusion can be drawn.

CHARACTERISTICS OF DATABASE MANAGEMENT SYSTEM:

1. It represents complex relationship between data.

2. Keeps tight control of data redundancy

3. Enforces user - defined rules to ensure the integrity of data.

4. Has centralized data dictionary for storage of information pertaining data

its manipulation
5. Ensures that the data can be shared across application.

6. Enforces data access authorization.

7. Has different interfaces via which user can manipulate the data.

ADVANTAGES OF DBMS:

1. Controlling Redundancy.

2. Restriction of unauthorized access.

3. providing storage structure for efficient query processing.

4. Providing multi user interface.

5. Sharing of data.

6. Data security.

Disadvantages of DBMS:

1. High initial investment in hardware, software and training.

2. Overhead for providing security, concurrency control, recovery and

integrity function.
3. The database and its application are simple, well defined and not
expected to change.

CREATE A BLANK DATABASE:

1. On the getting started with Microsoft office Access page, under New
Blank Database, click Blank Database
 2. In the blank Database pane, type a file name box. If we do not file name
extension, access adds it for us. To change the location of the file form the
default, click browse for a location to put our database, browse to the new
location, and then click ok.
3. Click creates

4. Begin typing to add data, or we can paste data from another source, as
described in the section.

PropertyDescription:

Field size: For text fields, this property sets the maximum number of characters that can be
stored in the field. The maximum in 255. For number fields, this property sets the type of
number that will be stored. For most efficient data storage, it is recommended that you
allocate the least amount of space that we think we will need for the data. We can adjust the
value upwards later, if our needs change.
Format: This property sets how the data is displayed. It does not affect the actual data as it
is stored in the field. We can select a predefined format or enter a custom format.

Input Mask: Use this property to specify a pattern for all data that will be entered in this
field. This helps ensure that all data is entered correctly, and that it contains the required
number of characters. For help about building an input mask.
Required: This property sets whether a value is required in this field. Property to yes,
access does not allow us to add a new record unless a value INS entered for field.

SQLServer

Microsoft SQL Server is a relational database management system developed by Microsoft. As a database
server, it is a software product with the primary function of storing and retrieving data as requested by
other software applications-which may run either on the same computer or on another computer across a
network (including the Internet). Microsoft markets at least a dozen different editions of Microsoft SQL
Server, aimed at different audiences and for workloads ranging from small single-machine applications to
large Internet-facing applications with many concurrent users. The protocol layer implements the external
interface to SQL Server. All operations that can be invoked on SQL Server are communicated to it via a
Microsoft-defined format, called Tabular Data Stream (TDS). TDS is an application layer protocol, used to
transfer data between a database server and a client. Initially designed and developed by Sybase Inc. for
their Sybase SQL Server relational database engine in 1984, and later by Microsoft in Microsoft SQL
Server, TDS packets can be encased in other physical transport dependent protocols, including TCP/IP,
named pipes, and shared memory. Consequently, access to SQL Server is available over these protocols.
In addition, the SQL Server API is also exposed over web services. The main mode of retrieving data from
a SQL Server database is querying for it. The query is expressed using a variant of SQL called T-SQL, a
dialect Microsoft SQL Server shares with Sybase SQL Server due to its legacy. The query declaratively
specifies what is to be retrieved. It is processed by the query processor, which figures out the sequence of
steps that will be necessary to retrieve the requested data. The sequence of actions necessary to execute
a query is called a query plan. There might be multiple ways to process the same query. For example, for a
query that contains a join statement and a select statement, executing join on both the tables and then
executing select on the results would give the same result as selecting from each table and then executing
the join, but result in different execution plans. In such case, SQL Server chooses the plan that is expected
to yield the results in the shortest possible time. This is called query optimization and is performed by the
query processor itself.

SQL Server Analysis Services (SSAS) adds OLAP and data mining capabilities for SQL
Server databases. The OLAP engine supports MOLAP, ROLAP and HOLAP storage
modes for data. Analysis Services supports the XML for Analysis standard as the
underlying communication protocol. The cube data can be accessed using MDX and LINQ
[45] queries.[46] Data mining specific functionality is exposed via the DMX query
language.
Command:

• SELECT - extracts data from a database

• UPDATE - updates data in a database

• DELETE - deletes data from a database

• INSERT INTO - inserts new data into a database

• CREATE DATABASE - creates a new database

• ALTER DATABASE - modifies a database

• CREATE TABLE - creates a new table

• ALTER TABLE - modifies a table

• DROP TABLE - deletes a table

• CREATE INDEX - creates an index (search key)

• DROP INDEX - deletes an index

 DATABASE CONNECTIVITY

Imports
System.Data.SqlClient
Public Class Forml

Inherits
System.Windows.Forms.Form
'Create ADO.NET objects.

Private myConn As
SqlConnection Private myCmd
As SqlCommand Private
myReader As SqlDataReader
Private results As String

myConn = New SqlConnection("Initial Catalog=Northwind;"

& _ "Data Source=localhost;Integrated Security=SSPI;")

myCmd = myConn.CreateCommand

myCmd.CommandText = "SELECT FirstName, LastName FROM

Employees" 'Open the connection.

myConn.Open()

.Net: Framework
The .NET Framework (pronounced as "dot net") is a proprietary software framework developed by
Microsoft that runs primarily on Microsoft Windows. It was the predominant implementation of the
Common Language Infrastructure (CLI) until being superseded by the cross-platform .NET project. It
includes a large class library called Framework Class Library (FCL) and provides language interoperability
(each language can use code written in other languages) across several programming languages.
Programs written for .NET Framework execute in a software environment (in contrast to a hardware
environment) named the Common Language Runtime (CLR). The CLR is an application virtual machine
that provides services such as security, memory management, and exception handling. As such,
computer code written using .NET Framework is called "managed code". FCL and CLR together constitute
the .NET Framework.

FCL provides the user interface, data access, database connectivity, cryptography, web
application development, numeric algorithms, and network communications. Programmers
produce software by combining their source code with .NET Framework and other
libraries. The framework is intended to be used by most new applications created for the
Windows platform. Microsoft also produces an integrated development environment for
.NET software called Visual Studio.

.NET Framework began as proprietary software, although the firm worked to standardize
the software stack almost immediately, even before its first release. Despite the
standardization efforts, developers, mainly those in the free and open-source software
communities, expressed their unease with the selected terms and the prospects of any free
and open-source implementation, especially regarding software patents. Since then,
Microsoft has changed
.NET development to more closely follow a contemporary model of a community-
developed software project, including issuing an update to its patent promising to address
the concerns.

VISUAL BASIC (.NET):

VISUAL BASIC (VB), ORIGINALLY CALLED VISUAL BASIC .NET (VB.NET), IS A MULTI-PARADIGM,
OBJECT ORIENTED PROGRAMMING LANGUAGE, IMPLEMENTED ON .NET, MONO, AND
THE .NET FRAMEWORK. MICROSOFT LAUNCHED VB.NET IN 2002 AS THE SUCCESSOR TO ITS
ORIGINAL VISUAL BASIC LANGUAGE, THE LAST VERSION OF WHICH WAS VISUAL BASIC 6.0.
ALTHOUGH THE ".NET" PORTION OF THE NAME WAS DROPPED IN 2005, THIS ARTICLE USES
"VISUAL BASIC [.NET]" TO REFER TO ALL VISUAL BASIC LANGUAGES RELEASED SINCE 2002, IN
ORDER TO DISTINGUISH BETWEEN THEM AND THE CLASSIC VISUAL BASIC. ALONG WITH C#
AND F#, IT IS ONE OF THE THREE MAIN LANGUAGES TARGETING THE .NET ECOSYSTEM. AS OF
MARCH 11, 2020, MICROSOFT ANNOUNCED THAT EVOLUTION OF THE VB.NET LANGUAGE HAS
CONCLUDED.[4]

Microsoft's integrated development environment (IDE) for developing in Visual Basic is

Visual Studio. Most Visual Studio editions are commercial; the only exceptions are Visual
Studio Express and Visual Studio Community, which are freeware. In addition, the .NET
Framework SDK includes a freeware command-line compiler called vbc.exe. Mono also
includes a command-line VB.NET compiler.

Visual Basic is often used in conjunction with the Windows Forms GUI library to make
desktop apps for Windows. Programming for Windows Forms with Visual Basic involves
dragging and dropping controls on a form using a GUI designer and writing corresponding
code for each control.

CODING:
Login:

Imports
System.Data.SqlClientImports
System.Data

Public Class login

Private Sub Button2_Click(sender As Object, e As EventArgs) Handles Button2.Click

homel.Show()

Me.Hide()
End Sub

Private Sub btnlogin_Click_l(sender As Object, e As EventArgs) Handles btnlogin.Click

en.Open()

cm = New SqlClient.SqlCommand("select * from register where UserName like "' &

txtusername.Text & "'and Password like"' & txtpassword.Text & ""',

en) dr =

cm.Execute Reader If
dr.HasRows < 0 Then

studentprofile.Show()
Me.Hide()

Else

MsgBox("No Username or Password found")

End If
en.Close()

End Sub

Private Sub Label2_Click(sender As Object, e As EventArgs) Handles Label2.Click

adminlogin.Show()

Me.Hide()
End Sub
 Private Sub CheckBox1_CheckedChanged_1{sender As Object, e As EventArgs) Handles
CheckBox1.CheckedChanged

txtpassword.PasswordChar = 1111

End Sub
End Class

Loading screen:

Public Class loading

Private Sub Timerl_Tick(sender As Object, As EventArgs) Handles

Timer1.Tick lbl.Text = pb1.Value & 11%11

pb1.Value += 1

If pb1.Value =
100 Then
home1.Show()
Me.Hide()
Timer1.Dispose()

End
If End
Sub End
Class

Home page:

Public Class home1

Private Sub Buttonl_Click(sender As Object, e As EventArgs) Handles

Button1.Click login.Show()

Me.Hide()
 End Sub

Private Sub Button2_Click(sender As Object, e As EventArgs) Handles Button2.Click

Forml.Show()
End Sub

End Class

Registration:

Public Class Forml

Private Sub login_Click(sender As Object, e As EventArgs) Handles

login.Click en.Open()

cm = New SqlClient.SqlCommand("insert into register

(UserName,Password,FullName,Email,PhoneNo)
values(@UserName,@Password,@FullName,@Email,@PhoneNo)", en)

With cm

.Parameters.AddWithValue("@FullName", txtfullname.Text)

.Parameters.AddWithValue("@Email", txtemail.Text)

.Parameters.AddWithValue("@PhoneNo", txtphone.Text)

.Parameters.AddWithValue("@UserName", txtusername.Text)

.Parameters.AddWithValue("@Password", txtpassword.Text)
cm.ExecuteNonOuery()

End With
en.Close()
 MsgBox("Register
successfully") End Sub

Private Sub Button2_Click(sender As Object, e As EventArgs) Handles Button2.Click

login.Show()

Me.Hide()
End Sub

End Class

Student profile:

Imports System.Data.SqlClient
Public Class studentprofile

Dim con As New

SqlConnection Dim cmd As
New SqlCommand

Private Sub Buttonl_Click(sender As Object, e As EventArgs) Handles

Buttonl.Click

homel.Show()
Me.Hide()

End Sub

Public Sub Button2_Click(sender As Object, e As EventArgs) Handles

Button2.Click

cmd = con.CreateCommand()
cmd.CommandType = CommandType.Text

111 , 111 111

cmd.CommandText = "insert into stdpro values( + txtsudent.Text + +

111 111 111 111

txtstdname.Text + ,
+ DateTimePickerl.Text.ToString()
,
+ +
txteducation.Text

111 111 11
+ , + txtuniversity.Text + ' )"
 cmd.ExecuteNonQuery()
MessageBox.Show("Data saved Successfully")

End Sub

Private Sub studentprofile_Load(sender As Object, e As EventArgs) Handles

MyBase.Load

con.ConnectionString = "Data Source=SANJU-STRAIGHT-;lnitial

Catalog=msdb;lntegrated Security=True"

If con.State = ConnectionState.Open Then

con.Close()
End If
con.Open()

End Sub
End Class

Faculty enrolment:

Imports
System.Data.SqlClient
Public Class
uploading_files

Dim con As New

SqlConnection Dim cmd As
New SqlCommand

Private Sub Button2_Click(sender As Object, e As EventArgs) Handles

Button2.Click cmd = con.CreateCommand()

cmd.CommandType = CommandType.Text
 cmd.CommandText = "insert into faculty2 values("' + fname.Text + "',"' + fid.Text + "',"' +
planguage.Text + "')"

cmd.ExecuteNonQuery()
MessageBox.Show("Data
saved Successfully")

End Sub

Private Sub uploading_files_Load(sender As Object, e As EventArgs) Handles

MyBase.Load

con.ConnectionString = "Data Source=SANJU-STRAIGHT-;lnitial

Catalog=msdb;lntegrated Security=True"

If con.State = ConnectionState.Open Then

con.Close()
End If
con.Open()

End
Sub End
Class

Faculty info:

Imports
System.Data.SqlClient
Public Class faculty

Dim con As New

SqlConnection Dim cmd As
New SqlCommand

Private Sub Button2_Click(sender As Object, e As EventArgs) Handles

Button2.Click cmd = con.CreateCommand()
 cmd.CommandType = CommandType.Text

cmd.CommandText = "insert into faculty values("' + facid.Text + "',"' + fullname.Text

+ "',"' + DateTimePicker2.Text.ToString() + "')"

cmd.ExecuteNonQuery()

MessageBox.Show("Your Plot Booked

Successfully") End Sub

Private Sub faculty_Load(sender As Object, e As EventArgs) Handles MyBase.Load

con.ConnectionString = "Data Source=SANJU-STRAIGHT-;lnitial

Catalog=msdb;lntegrated Security=True"

If con.State = ConnectionState.Open Then

con.Close()

End If
con.Open()

End Sub

Private Sub Button2_Click (sender As Object, e As EventArgs) Handles Button2.Click

homel.Show()

Me.Hide()
End Sub

End Class

FORGOT PASSWORD:

Imports
System.Data.SqlClient
Public Class
forgot_password

Dim con As New SqlConnection("Data Source=SANJU-

STRAIGHT-;lnitial Catalog =msdb;Integrated Security=True")
 Private Sub CheckBox1_CheckedChanged (sender As Object, e As EventArgs)
Handles CheckBoxl.CheckedChanged

txtpassword.PasswordChar =
"" End Sub

Private Sub btnlogin_Click(sender As Object, e As EventArgs) Handles

btnlogin.Click Dim cmd As New SqlCommand("update tablel set Password =
"' + txtusername.Text +

"'where UserName ="' + txtpassword.Text + ""',

con) con.Open()

cmd.ExecuteNonQuery
()
MsgBox("Password
Updated")

End
Sub End
Class

Admin view:

Imports
System.Data.SqlClient
Imports

System.Data

Public Class admin_view

SNAPSHOTS
SYSTEM DESIGN:
SYSTEM DESIGN IS THE MOST CREATIVE AND CHALLENGING PHASE IN THE SYSTEM LIFE
CYCLE. DESIGN THE FIRST STEP INTO THE DEVELOPMENT PHASE FOR ANY ENGINEERED
PRODUCT OR SYSTEM. DESIGN IS A CREATIVE PROCESS. A GOOD DESIGN IS THE KEY TO
EFFECTIVE SYSTEM DESIGN TRANSFORMS A LOGIC REPRESENTATION OF WHAT IS
REQUIRED TO DO INTO THE PHYSICAL SPECIFICATION. THE SPECIFICATION IS
CONVERTED INTO PHYSICAL REALITY DURING DEVELOPMENT.

Architectural Design:

The architectural design of a system emphasizes the design of the system architecture that
describes the structure behaviour and more views of that system and analysis.
Logical Design:

The logical design of a system pertains to an abstract representation of the flows, inputs and
outputs of the system. This often conducted via modelling, using an over abstract (and
sometimes graphical) model of actual system. Logical design includes entity relationship
diagrams (ER diagrams).

Physical Design:

The physical design related to the actual inputs and outputs processes of system that is
input output requirements, storage and processing requirements.

Input Design:

Input design deals with what data should be given as input, how the data should be
arranged or code, the dialogue to guide the operating personnel in providing input, methods
for preparing input validations and steps to follow when error occur. Input design is the
process of converting a user - oriented description of the input into a computer - base
system. This design is important to avoid errors in the data input process and show the
correct direction to the management for getting correct information from the computerized
system. It is achieved by creating user- friendly screens for the data entry to handle large
volume of data. The goal of designing input is to make data entry easier and to be free from
errors.

INTERFACES OF THE SYSTEM:

This section refers to the various types of interfaces which the user has to face during
operating the computerized System of "E-LEARNING MANAGEMENT" with vb6. The
section refers with entire interface [Screens] a user will have to face while operating the
current system. It shows the various screens appearing for different transactions.
The different screens shown here are in the below given order:

1. Login Screen.
2. Loading Screen.
3. Home page.
4. Registration.
5. Student profile.
6. Faculty enrolment.
7. Faculty info.
8. Faculty view.
9. Admin login.
10. Admin view.
11. Forgot password.
Screens:
1. Login screen:

1. Loading screen:

loading - D X

E-LEARNING MANEGEMENT
1. Home page:

1. Registration:
1. Student profile:
1. Faculty enrolment form:

1. Faculty info:
1. Faculty view:

1. Forgot password:

forgo password
1. Admin login:
 2. Admin view:

008 EOOC m
17-03-2023
16-03-2023 boo
sdc1 b11.1
sdc12332 01
b11.1
sdc I'll

sdc
boo
8731
bl'll

boo

CHAPTER.7

SOFTWARE TESTING

Introduction

Software testing is the act of examining the artifacts and the behaviour of the software
under test by validation and verification. Software testing can also provide an objective,
independent view of the software to allow the business to appreciate and understand the
risks of software implementation.
 Types of Testing

Unit tests

Unit tests are very low level and close to the source of an application. They consist in
testing individual methods and functions of the classes, components, or modules used by
your software. Unit tests are generally quite cheap to automate and can run very quickly
by a continuous integration server.

Integration tests

Integration tests verify that different modules or services used by your application work
well together. For example, it can be testing the interaction with the database or making
sure that microservices work together as expected. These types of tests are more
expensive to run as they require multiple parts of the application to be up and running.

Functional tests

Functional tests focus on the business requirements of an application. They only verify the
output of an action and do not check the intermediate states of the system when
performing that action.

There is sometimes a confusion between integration tests and functional tests as they
both require multiple components to interact with each other. The difference is that an
integration test may simply verify that you

End-to-end tests

End-to-end testing replicates a user behaviou0072 with the software in a complete

application environment. It verifies that various user flows work as expected and can be
as simple as loading a web page or logging in or much more complex scenarios verifying
email notifications, online payments, etc...

Acceptance testing

Acceptance tests are formal tests that verify if a system satisfies business requirements.
They require the entire application to be running while testing and focus on replicating
user behaviours. But they can also go further and measure the performance of the system
and reject changes if certain goals are not met.
 Performance testing

Performance tests evaluate how a system performs under a particular workload. These
tests help to measure the reliability, speed, scalability, and responsiveness of an
application. For instance, a performance test can observe response times when executing
a high number of requests, or determine how a system behaves with a significant amount
of data. It can determine if an application meets performance requirements, locate
bottlenecks, measure stability during peak traffic, and more.

Smoke Testing

Smoke tests are basic tests that check the basic functionality of an application. They are
meant to be quick to execute, and their goal is to give you the assurance that the major
features of your system are working as expected

Types of Manual Testing

1. White Box Testing

White box testing involves testing the product's underlying structure, architecture,
and code to validate input-output flow and enhance design, usability, and security.
2. Black Box Testing

Black box testing involves testing against a system where the code and paths are
invisible

CHAPTER 8

CONCLUSION:

The project entitled "E-LEARNING MANAGEMENT SYSTEM" was completed on time

with total satisfaction after testing with possible sample data. The performance was found
to be efficient and error free. This is a user-friendly package application which is very
easy to access and understand. Anyone with knowledge of computer will find it very easy
to use this software and perform various operation on it. In this project, first an attempt
has been made to find the need of the system. To fulfil the needs, a detailed study has
been conducted to find the various requirement of the system. This particular system has
been designed in an attractive manner, so that even a user with minimum knowledge can
be able to operate the system easily.

This software combines the best of both the world i.e; programming language (VB.NET),
and framework with database (SQL) providing easy accessibility and security. It was
developed to benefit the organization and the customers. Finally, the system was tested
 with real data and everything worked successfully. Thus, the system has fulfilled all the
objectives identified and is able to replace the existing system.

Goals Achieved

• Reduce maintaining register books

• Data security

• User Friendly screens to help non - technical users

• Portable

CHAPTER 9

FUTURE ENHANCEMENTS:

Every project whether large or small has same limitations no matter however diligently
developed. In some cases, limitations is small while in other cases they may be broad
also The major areas where modification can be done are as follow.

• In future, the software can be further enhanced by providing videos about the programming

• It can be improved in such a way that students can also get Internship opportunity.

• It can be improved by providing Training sections to crack interviews

• Live chats messenger, where teachers and students can communicate with each other.

• More security towards the project will be implemented in future.

• In future project, more modules will be included.

• Future modules will have elaborate reports for teachers and student's details.

BIBLOGRAPHY
 REFERENCES:

Books

1. Dependency Injection in .NET by Mark Seemann.

2. Programming Entity framework by Julia Lerman

3. VB.NET Language Pocket Reference by Steven Roman.

4. VB.NET Language in a Nutshell: A Desktop Quick Reference by Ron Petrusha.

WEB FORUMS

1. https://dotnet.microsoft.com/

2. https://www.w3schools.com/

3. https://www.geeksforgeeks.org

4. https://www.stackoverflow.com/
E-LEARNING MANAGEMENT SYSTEM
E-LEARNING MANAGEMENT SYSTEM
E-LEARNING MANAGEMENT SYSTEM