DistanceLearning system

CONTENTS

1.ABSTRACT

2. INTRODUCTION

3. PROJECT DICTIONARY

3.1. DATAFLOW DIAGRAMS

3.2. E-R DIAGRAMS

4. FORMS & REPORTS

4.1. I/O SAMPLES

1. ABSTRACT

The aim of this project “Distance Learning system” is to design and

develop an automated package named Distance Learning system for

managing the distance learning process of CMC limited via Internet.

The system consist of registration module for the employee to login

and also a new signup where the new employee can register

themselves and also provide option for forget password, incase the

employees forget their password. The employees who successfully can

access the library in which books are arranged in hierarchy and take a

test based on the book they have accessed and an administration who

has the authority to add and delete books in the library and also can

add question to the test.

While accessing the books there is a condition as the books are

arranged in the form of levels a employee who accessed the first level

can have a test in that particular level and is not eligible to take a test

in the other levels.

The future scope of this project would be an addition feature of CHAT

where in the employees can get their doubts clarified by the professors

at the specified time.

2. INTRODUCTION

Definition

Distance Learning System deals with the various levels of

training and development of skills to the employee and will account

the performance of the employee in training to validate working ability.

Description

Distance Learning system will give an extra spin to train the

employee’s through networking and communication technology. This

innovation will give many benefited to organization in training the

employees. It is user-friendly projects were user could work in there

own place and in convenient time. This system mainly consists three

different roles.

Organizer: Monitors the whole system.

Administrator: Send response to the employee and maintains

repository

Employee: User of the system, trained to the organization requirement.

General task

Administration

Client registration

Accessing of books

Request for exam

Request for extra time

Administration: -

This is a system, which accepts the employee’s requests, and

sends the response through updating the registration, assign the

password, assignment of books, exam date and also allocates the

extra time to assess the books on request. He has the authority to add

or delete the books form repository.

Employee registration

The employee by giving his valid information can apply for the

Distance learning. After proper verifications by administrator response

is sent back when information is updated. If the user wants to login, he

is required to enter employee id and password.

Accessing of books

Every employee can access all the books of the level he has selected

with in the time specified to him. His time for accessing the books is

updated with every login and logout of the account.

Request for exam

Every employee can request for the exam either he finish the time or

may not finish the time for access the books.

Request for extra time

Employees can request for extra time if they failed to finish the

training in the given time. If the employee request for the extra time

their performance level will descries.

Resource Availability

The resources, which are common to any system, consist of

human effort, information and development resource. Developing any

system with out satisfactory resources is inappropriate and impossible.

The design development team for this project consists of three

members or roles that are responsible for software development and

internal testing and its usage. Information assembly is vital to this

project. Various sources of information are available.

Organizer

This actor in the system is given higher authority Monitors the whole

system. I.e. maintains and coordinates all the activities of

administrator and employee.

Administrator

This actor is a second and final authority of the system. The role of this

actor is to monitor the request from the employee. This actor also has

the responsibility to follow the orders of the organizer. This actor is

responsible to update the repository.

Employee

This actor is the user in the system. This actor in the system can

access and avail the facilities in the system with a veiled registration.

This actor in the system can choose for any option with every login.

While accessing the books user needs to work in the available time.

Operational Feasibility

The system is operationally feasible; it is made so easy that operator

will not encounter any problem during working, as it is very user-

friendly. Operational feasibility checks the scope of the system. The

system under consideration should have enough operational research.

It is observed that the proposed system would provide a very

interactive means to share information and have a far and wide range.

The proposed system would make the information more interactive.

Thus operation feasibility of the proposed system is found to be high.

2. DESIGN PRINCIPLES & EXPLANATION

2.1. MODULES

There are 4 modules in the project. They are as follows.

(a). Administration Module

(b). In-house Fabrication Module

(c). External Large Fabrication Module

(d). External Small Fabrication Module

2.2. MODULE DESCRIPTION

In administration module, the authorized persons can only

access the project by entering username and password. Unauthorized

persons cannot access the project at all. It also maintains the

component information, employs information etc. It is also having the

flexibility to add new component/item, add or modify user details.

In in-house module, the employee place orders to his own

workshop as the material is supplied from his own factory. The order

placed by the employee is accepted only if the requested material is

available in the factory.

In the external fabrication there are two types namely

external large fabrication module and external small fabrication

module.

In external large fabrication module the employee place

order to outside workshop for large quantity of items as the material is

supplied from outside itself. When the required material is not

available in the factory, the employee places orders to outsiders for

fabricating/manufacturing the required items. The employee also

checks the availability of the funds. If the funds are not available, then

organization sanctions funds.

In external small fabrication module the orders are

placed for small quantity of items. In this module also material is not

supplied from the factory. The products are checked for the quality and

an inspection report is generated.

The process logic is used to describe all flow model processes that

appear at the final level of refinement. The content of the process logic

can include narrative text, a program design language (PDL)

description of the process algorithm, tables, diagrams or charts.

Administration Module:

In this module we give username and password

depending on the cadre of the personality. Here the process logic is to

get the data from the database to check whether the user is valid or

not.

In-house Module:

In this module the entire process logic depends on

placing work orders, material issuing. Each component is given a name

and unique drawing number is maintained. The material is supplied

from the own factory.

External Large Fabrication Module:

In this module the process logic depends on placing

demand orders, funds sanction and material issuing. This material is all

supplied from outside. The overall cost for manufacturing the list of

items is also estimated.

External Small Fabrication Module:

In this module the employee places orders to his own

workshop from outside. The overall cost for manufacturing the list of

items is also estimated.

External Small Fabrication Module:

In this module the process logic depends on placing job

contracts. Here the orders are placed for small quantity of items, an

inspection is conducted for the quality of the produced items. The

overall cost is estimated.

3. PROJECT DICTIONARY

3.1. DATAFLOW DIAGRAMS

Data flow diagrams can be used to provide a clear

representation of any business function. The technique starts with an

overall picture of the business and continues by analysing each of the

functional areas of interest. This analysis can be carried out to

precisely the level of detail required. The technique exploits a method

called top-down expansion to conduct the analysis in a targeted way.

Data flow diagrams are used to represent the flow of data in the

system. This gives the total representation of data flow from start to

end. Data Flow Diagram has certain symbols to represent the flow in

diagrammatic form. This representation can be done in several levels.

The symbols that we use are

Rules

External Entities

It is normal for all the information represented within a system to have

been obtained from, and/or to be passed onto, an external source or

recipient. These external entities may be duplicated on a diagram, to

avoid crossing data flow lines. Where they are duplicated a stripe is

drawn across the left hand corner, like this.

The addition of a lowercase letter to each entity on the diagram

Processes

when naming processes, avoid glossing over them, without really

understanding their role. Indications that this has been done are the

use of vague terms in the descriptive title area - like 'process' or

'update'.

The most important thing to remember is that the description must be

meaningful to whoever will be using the diagram.

Data Flows

Double headed arrows can be used (to show two-way flows) on all but

bottom level diagrams. Furthermore, in common with most of the other

symbols used, a data flow at a particular level of a diagram may be

decomposed to multiple data flows at lower levels.

Data Stores

Each store should be given a reference letter, followed by an arbitrary

number. These reference letters are allocated as follows:

'D'- indicates a permanent computer file

'M'- indicates a manual file

'T'- indicates a transient store, one that is deleted after

processing.

In order to avoid complex flows, the same data store may be drawn

several times on a diagram. A double vertical bar on their left hand

edge indicates multiple instances of the same data store.

Data flow Diagram for Employee:

Employee

Registration

Login

ChangePassword

AccessBooks

Request For Exam

LogoutHome page

Data Flow diagram for administrator

Administrator

Home page Login

Exam Date

UpdatingRegistration

AssignBooks

Add/delbooks

Give password

Logout

3.2. E-R DIAGRAMS

E-R DIAGRAMS

Entity Relationship Diagram give the structural representation of the

relationship between entities in the system. This representation of

relations gives the clear understanding how the data flow between

entities. This diagram also explains how many members involved in

the system.

The symbols we use in this representation is

Entity

Week Entity

Relationship

Attribute

* ***

11

* 1 1 1

* ** 1

* *

1

Employee

Administrator

Organizer

Assigning Books

Assigning Books

Issue Exam date

Issue Exam date

Book

Add/DelBooks

Add/DelBooks

Accept to add

Accept to add

Req new bookkkk

Req new bookkkkAssign

new password

Assign new password

E_Id PWD

Level

U_id PWD

4. FORMS & REPORTS

4.1. I/O SAMPLES