Online Course Material Management System

Project Report
By

Mahesh kumar ray

Reg no-2205298080
Roll no-25
&
Rahul kumar
Reg no-2205298120
Roll no-36
MCA(GENIUS)
 Acknowledgement
First I express my heartiest thanks and gratefulness to almighty God for His
heavenly blessing makes me possible to complete the my project successfully.

We really grateful and wish our profound our indebtedness to Assistant Professor,
Department of MCA of Gift autonomous college. Deep Knowledge & keen interest
of our supervisor in the field of “Web Application” to carry out this project. His
endless patience ,scholarly guidance ,continual encouragement , constant and
energetic supervision, constructive criticism , valuable advice ,reading many
inferior draft and correcting them at all stage have made it possible to complete
this project.

I would like to manifest my heartiest gratitude to Sasmita Tripathy and Head,

Department of MCA, for his kind help to finish our project and also to other
faculty member and the staff of MCA department.
 ----------------------

Project Abstract
This project “Online Course Material Management System” is a web based
application which is useful for users. This system mainly deals to manage the
online courses for users. This application has been designed and developed a
comprehensive web-based system to better support the users benefit and
requirement. By using this application will make the users less wasted time, and
they will be able to easily get all the studies information. As a result, they will be
able to continue their studies better. Using this platform users can view and read
the material according to their needs. By using this application users will be able
to check which new reading material is available for their studies.

Project Objective
The project objective will be focused on developing an online course material to
ensure the effectiveness of the flow of course materials. Moreover, the system will
offer a complete management system that integrated with the online course
material to help the users for maintaining the flow process of the course.

By using this application users will be able to check which new reading material is
available for their studies.
 Introduction
Introduction:-
The application named “Course Material Management System” which is a
webbased application. This application will be most convenient for user’s study
purpose and they will be benefited most. Because this application has beneficial
and helpful feature are exist which will be use the user. In this application there
have two panel i.e., Admin and User panel.

Admin Panel:

Dashboard: In this section, admin can view all the detail in brief like Total Courses,
Total Classes, Total Subject and Total Registered Users.

Class: In this section, admin can manage the class(Add/Delete/Update).

Subject: In this section, admin can manage the subject(Add/Delete/Update).

Course: In this section, admin can manage the course(Add/Delete/Update).

Reg Users: In this section, admin can view the registered users’ details.

Reports: In this section, admin can view the details of course uploaded in
particular period according to class.

Admin can also update his profile, change the password and recover the
password.
User Panel

User(User) can log in with registered mobile number or email and password. User
can view and download any course according to their class course.

User can also update his profile, change the password and recover the password.

Purpose:-
The purpose of project is to build an application program to reduce manual work
for managing the course through internet. This application has good appearance
and easy to operate. It is very simple and easy to access. This project provides lots
of features to manage in very well manner. This project contains advance modules
which make the backend system very powerful.

Scope:-
1. Online Course Material Management System project is developed as a web
application and it will work over web.
2. Using this project user can see and save their class materials.
3. This project will only applicable for educational institutions.
 Requirement Specification

Hardware Configuration :

Client Side:
RAM 512 MB

Hard disk 10 GB

Processor 1.0 GHz

Server side:
RAM 1 GB

Hard disk 20 GB

Processor 2.0 GHz

Software Requirement:
Client Side:

Google Chrome or any compatible

Web Browser browser
Operating System
Windows or any equivalent OS

Server Side:

Web Server APACHE

Server side Language PHP5.6 or above version

Database Server MYSQL

Google Chrome or any compatible

Web Browser browser

Operating System Windows or any equivalent OS

APACHE
The Apache HTTP Server Project is an effort to develop and maintain an
opensource HTTP server for modern operating systems including UNIX and
Windows. The goal of this project is to provide a secure, efficient and extensible
server that provides HTTP services in sync with the current HTTP standards.
The Apache HTTP Server ("httpd") was launched in 1995 and it has been the most
popular web server on the Internet since April 1996. It has celebrated its 20th
birthday as a project in February 2015.
PHP

• PHP stands for PHP: Hypertext Preprocessor.

• PHP is a server-side scripting language, like ASP.

• PHP scripts are executed on the server.

• PHP supports many databases (MYSQL, Informix, Oracle, Sybase, Solid,

Generic ODBC, etc.).

• PHP is an open source software.

• PHP is free to download and use.

MYSQL

• MYSQL is a database server

• MYSQL is ideal for both small and large applications
• MYSQL supports standard SQL
• MYSQL compiles on a number of platforms

• MYSQL is free to download and use

• How to access MySQL:

http://localhost/phpmyadmin
 Analysis and Design

Analysis:

This application will be most convenient for user’s study purpose and they will be

benefited most. Because this application has beneficial and helpful feature are

exist which will be use the user.

Disadvantage of present system:

• Not user friendly: The present system not user friendly because data is not

stored in structure and proper format.

• Manual Control: All report calculation is done manually so there is a chance

of error.
 • Lots of paper work: Visitors maintain in the register so lots of paper require

storing details.

• Time consuming

Design Introduction:
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
UML Diagrams:
Actor:
A coherent set of roles that users of use cases play when interacting with the
use `cases.

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.

USECASE 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.

USECASE DIAGRAM: 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 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.

Use Case Diagrams:

Admin
 Signin

Dashboard

Manage Class

Manage Subject

Manage Course

Generate Report

View Reg Users

Update Profile

Change Password
User

Sign Up

Signin

Dashboard

View Courses

Update Profile

Change Password

Class Diagram:
A description of set of objects that share the same attributes operations,
relationships, and semantics

ER Diagram:

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
EntityRelationship 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 specific database management
software.

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.

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

Mandatory existence is shown by the bar (looks like a 1) next to the entity for an
instance is required. Optional existence is shown by placing a circle next to the
entity that is optional.

Data Flow Diagram

Data Flow Diagrams

A Data Flow Diagram (DFD) is a traditional visual representation of the information

flows within a system. A neat and clear DFD can depict the right amount of the
system requirement graphically. It can be manual, automated, or a combination of
both.

It shows how data enters and leaves the system, what changes the information,
and where data is stored.

The objective of a DFD is to show the scope and boundaries of a system as a

whole. It may be used as a communication tool between a system analyst and any
person who plays a part in the order that acts as a starting point for redesigning a
system. The DFD is also called as a data flow graph or bubble chart.

The following observations about DFDs are essential:

1. All names should be unique. This makes it easier to refer to elements in the
DFD.
2. Remember that DFD is not a flow chart. Arrows is a flow chart that
represents the order of events; arrows in DFD represents flowing data. A
DFD does not involve any order of events.
3. Suppress logical decisions. If we ever have the urge to draw a
diamondshaped box in a DFD, suppress that urge! A diamond-shaped box is
used in flow charts to represents decision points with multiple exists paths
of which the only one is taken. This implies an ordering of events, which
makes no sense in a DFD.
4. Do not become bogged down with details. Defer error conditions and error
handling until the end of the analysis.

Standard symbols for DFDs are derived from the electric circuit diagram analysis
and are shown in fig:

Circle: A circle (bubble) shows a process that transforms data inputs into data
outputs.

Data Flow: A curved line shows the flow of data into or out of a process or data
store.
Data Store: A set of parallel lines shows a place for the collection of data items. A
data store indicates that the data is stored which can be used at a later stage or by
the other processes in a different order. The data store can have an element or
group of elements.

Source or Sink: Source or Sink is an external entity and acts as a source of system
inputs or sink of system outputs.

Zero Level DFD

Class Subject
Management Management

Password Course
Management
Management

Login OCMMS Administrator

Management
Management

Registration User
Management Management
First Level DFD
 Class Subject
Management Management

Password Generate
Management Report

Administrator
Login OCMMS
Management
Management

User
Registration Management
Management

Course Password
Recovery
Management Management
 Conclusion:
This Application provides a computerized version of Online Course Material
Management System which will benefit the schools, educational camps, corporate
training programs, and online training programs.

The Application was designed in such a way that future changes can be
done easily. The following conclusions can be deduced from the development of
the project.

• Automation of the entire system improves the productivity.

• 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.