Sie sind auf Seite 1von 25

1.

INTRODUCTION

1.1 INTRODUCTION TO PROJECT

The “E-Learning Management System” has been developed to override the

problems prevailing in the practicing manual system. This software is supported

to eliminate and in some cases reduce the hardships faced by this existing

system. Moreover this system is designed for the particular need of the company

to carry out the operations in a smooth and effective manner.

The application is reduced as much as possible to avoid errors while entering the

data. No formal knowledge is needed for the user to use this system. Thus by this

all it proves it is user friendly. E-Learning Management System can lead to error

free, secure, reliable and fast management system.

Every organization, weather big or small, has challenges to overcome and

managing the information to the cadet, course, assessment, course type. Every E-

Learning Management System has different course needs, therefore we design

exclusive employee management systems that are adapted to your managerial

requirements. This is design to assist in strategic planning, and will help you

ensure that your organization is equipped with the right level of information.

Also for those busy executives who are always on the go, our systems come with

remote access features which will allow you to manage your workforce. These

systems will ultimately allow you to better manage resources

1
1.2 OBJECTIVE

The main objective of this project on E-Learning Management System is to manage the detail
of the course, cadet, employee, assessment etc. The project is totally built at administrative
end and thus only the administrator guaranteed the access. It tracks all the details about the
employee, assessment, cadet..

1.3 PROBLEMS IN THE EXISTING SYSTEM

 It is less user-friendly.
 More men power
 It is having lots of manual work.

 The present system is very less secure.

 It is unable to generate different kinds of report.

 Less security system to prevent data.

1.4 PROPOSED SYSTEM


The development of the new system contains the following activities

 User friendliness is provided in the application with various controls.



 System needs store information about new entry of course, cadet, and employee.

 System needs to help the internal staff to keep information of student and find them as per
various quires. 

 System needs to maintain quantity record.

 System needs to keep the record of Employee.

 System needs to update and delete record.

 System also needs a search area.

 System also needs a security system to prevent data.

2
1.5 ADVANTAGES
 It generates the records in the form of pdf, doc, xls file.

 It stores the data in the database.

 It checks the assessment, and stores the Result.

 It makes Record book available to the cadet.

 Cadet can view his/her performance online.

3
2. SYSTEM ANALYSIS

2.1 STUDY OF THE SYSTEM:


System analysis is a process of gathering and interpreting facts, diagnosing problems and the
information about the E-Learning Management System to recommended improvements on
the system. It is a problem solving activity that requires intensive communication between
the system users and system developers. System study is an important phase of any
development process. The system is studied to the minutest detail and analyzed. The system
analysis plays the role of the interrogator. The system is view as a whole and the input to the
system are identified. The output from the organizations is traced to the various processes.
System analysis is concerned with becoming aware of problem. A detailed study of the
process must be made by various techniques. The data collected by these sources must be
scrutinized to arrive to a conclusion. The conclusion is an understanding of how the system
functions. The system is called the existing system. Now the existing system is subjected to
close study and problem areas are identified. The designer now functions as a problem
solver and tries to sort out the difficulties that the enterprise faces. The solutions are given as
proposal. The proposal is then weighted with the existing system analytically and the best
one is selected. The proposal is presented to the user for an endorsement by the user. The
proposal is reviewed on user request and suitable changes are made. This is loop that ends as
soon as the user is satisfied with proposal. Preliminary study is the process of gathering and
interpreting facts, using the information for further studies for the system. It does various
feasibility studies. In these studies a rough figure of the system activities can be obtained,
from which the decision about the strategies to be followed for effective system study and
analysis can be taken.

PERFORMANCE REQUIREMENTS:
It is very difficult to change the system once it has been designed and on the other hand
designing a system, which does not cater to the requirements of the user, is of no use.
The requirement specification for any system can be broadly stated as given below:
 The system should be able to interface with the existing system

 The system should be accurate.

 The system should be better than the existing system

 The existing system is completely dependent on the user to perform all the duties.

4
MODULES
The system after careful analysis has been identified to be presented with the following
modules:

The modules involved are:

 Administrator

 Employees

 Cadet

Modules Description:

 Administrator:-
The administrator is the organization user of this project. The admin can create new
Assessment, new cadet, new employee, new ship, new course etc and creates new question
and he assign no. marks to each question, and he can modifies the user, record book,
assessment. Admin can assign the course and ship to the cadet and can also assign the batch
and phase to the cadet. Admin can also assign the batch to the employee and also assign the
cadet to the Employee. The administrator has all the information about all the cadets,
Employees, ships and performance of the cadet.

 Cadet:-
This module contains all the information about the cadet. In this personal information cadet
can view his personal information and he can update his personal information (some
information is restricted to change.). Cadet can go inside the login and read the record book
and give the assessment. Cadet also sees the performance and submits the approval. Cadet can
see the days on board and days on ship. Cadet can see the information about the ship. Cadet
can print his performance certificate at any time.

5
 Employee:-
Employee can see the record book of every cadet on his batch and also see the detail of the
cadet on his batch. Employee can check the performance of the cadet. Employee can submit
the approval of the cadet. Employee can see the notification and send the notification to the
cadet.

INPUTS & OUTPUTS


The main inputs, outputs and major functions of the system are as follows.
Inputs:
 Admin enters his/her user id and password.

 Cadet enters his/her user id and password.

 Admin assign the batch to the Cadet.

 Admin can edit the personal details and so on.
 Cadet can submit assessment.
 Employee enters his/her user id and password.

Outputs:
 Admin receives personal details.

 Cadet receives the personal details.

 Cadet can see the slides and read all phases.

 Cadet receives the results of that assessment and all the results with that id.

 Displays Reports to the Admin.

6
2.2 SDLC MODEL:
SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model of
Software Development and Enhancement. This model was not the first model to discuss
iterative development, but it was the first model to explain why the iteration models.

As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase
starts with a design goal and ends with a client reviewing the progress thus far. Analysis and
engineering efforts are applied at each phase of the project, with an eye toward the end goal
of the project.
The steps for Spiral Model can be generalized as follows:
 The new system requirements are defined in as much details as possible. This usually
involves interviewing a number of users representing all the external or internal users and
other aspects of the existing system.

 A preliminary design is created for the new system.

7
 A first prototype of the new system is constructed from the preliminary design. This is
usually a scaled-down system, and represents an approximation of the characteristics of the
final product.

 A second prototype is evolved by a fourfold procedure:

1. Evaluating the first prototype in terms of its strengths, weakness, and risks.
2. Defining the requirements of the second prototype.
3. Planning a designing the second prototype.
4. Constructing and testing the second prototype.
 At the customer option, the entire project can be aborted if the risk is deemed too great.
Risk factors might involve development cost overruns, operating-cost miscalculation, or any
other factor that could, in the customer’s judgment, result in a less-than-satisfactory final
product.
 The existing prototype is evaluated in the same manner as was the previous prototype,
and if necessary, another prototype is developed from it according to the fourfold procedure
outlined above.

 The preceding steps are iterated until the customer is satisfied that the refined prototype
represents the final product desired.

 The final system is constructed, based on the refined prototype.

 The final system is thoroughly evaluated and tested. Routine maintenance is carried on a
continuing basis to prevent large scale failures and to minimize down time.

8
Fig. Spiral Model

9
3. FEASIBILITY STUDY
Preliminary investigation examine project feasibility, the likelihood the system will be
useful to the organization. The main objective of the feasibility study is to test the
Technical, Operational and Economical feasibility for adding new modules and debugging
old running system. All system is feasible if they are unlimited resources and infinite time.
There are aspects in the feasibility study portion of the preliminary investigation:
 Technical Feasibility
 Economic Feasibility
 Operation Feasibility

3.1. TECHINICAL FEASIBILITY:

This included the study of function, performance and constraints that may affect the ability to
achieve an acceptable system, as described in the System Requirement Specification and
checked if everything was possible using different type of front end and backend platform.

3.2 OPERATIONAL FEASIBILITY:


Not only must an application make economic and technical sense, it must also make
operational sense.

Operations Issues Support Issues

 What
 What tools are needed to documentation will
support operations? users be given?
 
 What skills will operators  What training will
need to be trained in? users be given?
 
 What processes need to be  How will change
created and/or updated? requests be manage

?

10
No doubt the proposed system is fully GUI based that is very user friendly. A proper
training has been conducted to let know the essence of the system to the users so that they
feel comfortable with new system. As far out study is concerned the client is comfortable
with new system. As far our study is concerned the clients are comfortable and happy as
the system has cut down their loads and doing.

3.3 ECONOMIC FEASIBILITY:

This is very important aspect to be considered while developing a project. We decided the
technology based on minimum possible cost factor
 All hardware and software cost has to be borne by the organization.
 Overall we have estimated that the benefits the organization is going to receive from the
proposed system will surely overcome the initial costs and latter on running cost for the
system.

11
4. ENVIRONMENT

4.1 Server:

 Operating System Server: Windows



 Database Server: MySQL

 Web Server: Apache Tomcat 7.0.65 server

 Client: Google chrome, Mozilla Firefox, android.

 Tools: Spring MVC

 User Interface: JSPX

 Code Behind: Java

4.2 Hardware Specification:

 Processor: Pentium 4 or above



 RAM: 1GB

 Hard Disk: 40 GB or above

4.3 Language Used:


 Front End: HTML, CSS, JavaScript, Bootstrap, JQuery, 

 Back End: MySQL.

12
5. SYSTEM DESIGN

5.1. DATA FLOW DIAGRAM:-


A Data Flow Diagram (DFD) is a graphical representation of the "flow" of data through an
Information System. A data flow diagram can also be used for the visualization of Data
Processing. It is common practice for a designer to draw a context-level DFD first which
shows the interaction between the system and outside entities. This context-level DFD is
then "exploded" to show more detail of the system being modeled.
A DFD represents flow of data through a system. Data flow diagrams are commonly used
during problem analysis. It views a system as a function that transforms the input into
desired output. A DFD shows movement of data through the different transformations or
processes in the system.

Dataflow diagrams can be used to provide the end user with a physical idea of where the
data they input ultimately has an effect upon the structure of the whole system from order
to dispatch to restock how any system is developed can be determined through a dataflow
diagram. The appropriate register saved in database and maintained by appropriate
authorities.

Data Flow Diagram Notation

Function

File/Database

Input/output

13
Flow

Data Flow Diagram:

14
5.2 E-R DIAGRAM:-
An entity-relationship (ER) diagram is a specialized graphic that illustrates the

interrelationships between entities in a database. ER diagrams often use symbols to

represent three different types of information. Boxes are commonly used to represent

entities. Diamonds are normally used to represent relationships and ovals are used to

represent attributes

An entity-relationship model (ERM) in software engineering is an abstract and

conceptual representation of data. Entity-relationship modeling is a relational schema

database modeling method, used to produce a type of conceptual schema or semantic data

model of a system, often a relational database, and its requirements in a top-down fashion.

Symbols used in this E-R Diagram:

Entity: Entity is a “thing” in the real world with an independent existence. An entity may

be an object with a physical existence such as person, car or employee. Entity symbol is

as follows:

Attribute: Attribute is a particular property that describes the entity. Attribute symbol is:

Relationship: Relationship will be several implicit relationships among various entity

types whenever an attribute of one entity refers to another entity type some relationship

exits. Relationship symbol is:

15
E-R Diagram

16
6. TECHNOLOGY & DESCRIPTION

6.1 Introduction to Spring


6.2 Spring MVC
6.3 Java
6.4 MySQL

6.1Introduction to Spring
Spring framework is an open source Java platform that provides comprehensive
infrastructure support for developing robust Java applications very easily and very
rapidly. Spring framework was initially written by Rod Johnson and was first released
under the Apache 2.0 license in June 2003. This tutorial has been written based on
Spring Framework version 4.1.6 released in Mar 2015.
Spring is lightweight when it comes to size and transparency. The basic version of
Spring framework is around 2MB.The core features of the Spring Framework can be
used in developing any Java application, but there are extensions for building web
applications on top of the Java EE platform. Spring framework targets to make J2EE
development easier to use and promotes good programming practices by enabling a
POJO-based programming model.

Spring could potentially be a one-stop shop for all your enterprise applications.
However, Spring is modular, allowing you to pick and choose which modules are
applicable to you, without having to bring in the rest. The following section provides
details about all the modules available in Spring Framework.

The Spring Framework provides about 20 modules which can be used based on an
application requirement.

17
Features of Spring:-
 Lightweight programming: Spring Framework is lightweight with respect to
size and transparency.
 Inversion Of Control: In Spring Framework, loose coupling is achieved using
Inversion of Control. The objects give their own dependencies instead of
creating or looking for dependent objects.
 Aspect Oriented Programming: By separating application business logic from
system services, Spring Framework supports Aspect Oriented Programming and
enables cohesive development.
 Container: Spring Framework creates and manages the life cycle and
configuration of application objects.
 MVC Framework: Spring Framework is a MVC web application framework.
This framework is configurable via interfaces and accommodates multiple view
technologies.
 Transaction Management: For transaction management, Spring framework
provides a generic abstraction layer. It is not tied to J2EE environments and it
can be used in container-less environments.
 JDBC Exception Handling: The JDBC abstraction layer of the Spring
Framework offers an exception hierarchy, which simplifies the error handling
strategy.

6.2 Spring MVC:-


The Spring Web MVC framework provides Model-View-Controller (MVC)
architecture and ready components that can be used to develop flexible and loosely
coupled web applications. The MVC pattern results in separating the different aspects
of the application (input logic, business logic, and UI logic), while providing a loose
coupling between these elements.
 The Model encapsulates the application data and in general they will consist
of POJO.

 The View is responsible for rendering the model data and in general it
generates HTML output that the client's browser can interpret.

 The Controller is responsible for processing user requests and building an


appropriate model and passes it to the view for rendering

18
6.3JAVA:-
Java programming language was originally developed by Sun Microsystems which was
initiated by James Gosling and released in 1995 as core component of Sun Microsystems'
Java platform.

The latest release of the Java Standard Edition is Java SE 8. With the advancement of
Java and its widespread popularity, multiple configurations were built to suit various
types of platforms. For example: J2EE for Enterprise Applications, J2ME for Mobile
Applications.

The new J2 versions were renamed as Java SE, Java EE, and Java ME respectively. Java
is guaranteed to be Write Once, Run Anywhere.

 Object Oriented − In Java, everything is an Object. Java can be easily extended


since it is based on the Object model.
 Platform Independent − unlike many other programming languages including C and
C++, when Java is compiled, it is not compiled into platform specific machine, rather
into platform independent byte code. This byte code is distributed over the web and
interpreted by the Virtual Machine (JVM) on whichever platform it is being run on.
 Simple − Java is designed to be easy to learn. If you understand the basic concept of
OOP Java, it would be easy to master.
 Secure − With Java's secure feature it enables to develop virus-free, tamper-free
systems. Authentication techniques are based on public-key encryption.
 Architecture-neutral − Java compiler generates an architecture-neutral object file
format, which makes the compiled code executable on many processors, with the
presence of Java runtime system.
 Portable − Being architecture-neutral and having no implementation dependent
aspects of the specification makes Java portable. Compiler in Java is written in ANSI C
with a clean portability boundary, which is a POSIX subset.
 Robust − Java makes an effort to eliminate error prone situations by emphasizing
mainly on compile time error checking and runtime checking.
 Multithreaded − With Java's multithreaded feature it is possible to write programs
that can perform many tasks simultaneously. This design feature allows the developers to
construct interactive applications that can run smoothly.
 Interpreted − Java byte code is translated on the fly to native machine instructions
and is not stored anywhere. The development process is more rapid and analytical since
the linking is an incremental and light-weight process.
 High Performance − with the use of Just-In-Time compilers, Java enables high
performance.
 Distributed − Java is designed for the distributed environment of the internet.
 Dynamic − Java is considered to be more dynamic than C or C++ since it is designed
to adapt to an evolving environment. Java programs can carry extensive amount of run-
time information that can be used to verify and resolve accesses to objects on run-time.
19
6.4 MYSQL:-
A database is a separate application that stores a collection of data. Each database has
one or more distinct APIs for creating, accessing, managing, searching and replicating
the data it holds.

Other kinds of data stores can also be used, such as files on the file system or large hash
tables in memory but data fetching and writing would not be so fast and easy with those
type of systems.

Nowadays, we use relational database management systems (RDBMS) to store and


manage huge volume of data. This is called relational database because all the data is
stored into different tables and relations are established using primary keys or other keys
known as Foreign Keys.

Some features of MS SQL Server:


 Enables you to implement a database with tables, columns and indexes.

 Guarantees the Referential Integrity between rows of various tables.

 Updates the indexes automatically.

 Interprets an SQL query and combines information from various tables.

20
7. OUTPUT SCREEN

21
22
8. CONCLUSION

This package shall prove to be a powerful package in satisfying all the

requirements of the organization.

 The description of purpose, scope and applicability.

 We define the problem on which we are working on the project.

 We describe the requirement specifications of the system and the action that

can be done on these things.

 We understand the problem domain and produce a model of the system,

which describes operations that can be performed on the system.

 We designed user interface and security issues.

 Finally the system is implemented and tested according to test cases.

LIMITATIONS:-

 Since it is an online project, cadet need internet connection

 People who are not familiar with computers can’t use this software.

23
9. FUTURE IMPROVEMENT
This web application involves almost all the features of the online E-Learning.
The future implementation will be online help for the cadet.

24
10. BIBLIOGRAPHY
 http://www.google.com
 http://www.wikipedia.org
 http://www.javaworld.com
 http://www.tutorialpoints.com/java-tutorila
 http://www.tutorialpoints.com/mysql/mysql-introduction.htm
 https://www.tutorialspoint.com/spring/index.htm

25

Das könnte Ihnen auch gefallen