Final Edited Elearnig System

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 82

BAHIR DAR UNIVERSITY

BAHIRDAR INSTITUTE OF TECHNOLOGY


FACULITY OF ELECTRICAL AND COMPUTER
ENGINEERING

DEPARTMENT OF COMPUTER ENGINEERING

Project on

Web based E-Learning system for BiT


NAME ID

1. Yibeltal Ayele ……………………………………………… 0503466


2. Wassihun Worku……………………...………………….… 0503448
3. Yonas Yirga …………………….…………………………. 0503471
4. Zerihun Abebe ……………………………………………... 0503483
5. Tigist T/Mariam ………….….……....…………………...... 0503430

February 2017 /2009


Advisor: Mr. Adugna Necho
BAHIR DAR, ETHIOPIA
E -Learning system for bit

DECLARATION
The Project is our own and has not been presented for a degree in any other university and
all the sources of material used for the project/thesis have been duly acknowledged. (Name
and Signature up to the number of the project group members)

Name Signature
Yibeltal Ayele ---------------------

Wassihun Worku ----------------------

Zerihun Abebe ---------------------

Yonas Yirga ---------------------

Tigist T/Mariam ----------------------

Faculty: FACULITY OF ELECTRICAL AND COMPUTER ENGINEERING


Program: COMPUTER ENGINEERING
Project subject: Web Based E-Learning System for BIT

This is to certify that I have read this project and that in my opinion it is fully adequate, in
scope and quality, as a project for final year project.

------------------------------------- ----------------------------------
Name of Advisor Signature

Examining committee members signature Date


1. Examiner 1. ____________ ___________ ___________
2. Examiner 2 ____________ ____________ ___________

i
E -Learning system for bit

ACKNOWLEDGEMENT
First, we would like to thanks for our God that has helped us in every difficult condition.
Then we would like to express our deep thanks and gratitude to our advisor Mr. Adugna
Nechofor his support and guidance in carrying out the project.

ii
E -Learning system for bit

TABLE OF CONTENT

DECLARATION.....................................................................................................................................................i

ACKNOWLEDGEMENT.....................................................................................................................................ii

TABLE OF CONTENT........................................................................................................................................iii

LIST OF TABLES.................................................................................................................................................v

LIST OF FIGURES..............................................................................................................................................vi

ACRONYMS........................................................................................................................................................vii

ABSTRACT.........................................................................................................................................................viii

CHAPTER ONE.....................................................................................................................................................1

1. INTRODUCTION......................................................................................................................................1
1.1 Background of the project.....................................................................................................................1
1.2 Statement of the problem......................................................................................................................2
1.3 Objective of the project.........................................................................................................................3
1.4 Scope of the project’.............................................................................................................................3
1.5 Limitations............................................................................................................................................4
1.6 Methodology of the project...................................................................................................................4
1.8 Estimated budget...................................................................................................................................5
1.9 Tasks and Time schedule......................................................................................................................6
1.10 Significance of the project................................................................................................................7
1.11 Benefits of the system......................................................................................................................7
1.12 Organization of the project document..............................................................................................8

CHAPTER TWO....................................................................................................................................................9

2. SYSTEM FUTURES...................................................................................................................................9
2.1 Existing system description..................................................................................................................9
2.2 Proposed system..................................................................................................................................10
2.3 Functional Requirements....................................................................................................................11
2.4 Use case model....................................................................................................................................13
2.5 Description of use case diagram.........................................................................................................14
2.6 Non-Functional requirements.............................................................................................................36
iii
2.7 Analysis models..................................................................................................................................37

CHAPTER THREE.............................................................................................................................................44
E -Learning system for bit

3. SYSTEM DESIGN....................................................................................................................................44
3.1 Introduction.........................................................................................................................................44
3.2 Design goals........................................................................................................................................44
3.3 Hardware and software architecture...................................................................................................44
3.4 Class diagram......................................................................................................................................46
3.5 Deployment Diagram..........................................................................................................................47
3.6 User interface......................................................................................................................................48
3.7 Data base Design (Persistent Data modeling).....................................................................................54

CHAPTER FOUR................................................................................................................................................60

4. IMPLEMENTATION...............................................................................................................................60
4.1 Introduction.........................................................................................................................................60
4.2 Algorithm Design................................................................................................................................60
4.3 Coding.................................................................................................................................................64

CHAPTER FIVE..................................................................................................................................................67

5 SYSTEM TESTING..................................................................................................................................67
5.1 Introduction.........................................................................................................................................67
5.2 Objective.............................................................................................................................................67
5.3 Testing by Scope.................................................................................................................................68
5.4 Resource..............................................................................................................................................69
5.5 Schedule..............................................................................................................................................69
5.6 Feature to be tested or not to be tested................................................................................................69
5.7 Pass/fail criteria...................................................................................................................................70
5.8 Approach.............................................................................................................................................71
5.9 Test case specification........................................................................................................................71

CHAPTER SIX.....................................................................................................................................................73

6 RESULT, CONCLUSION AND RECOMMENDATION.........................................................................73


6.1 Result..................................................................................................................................................73
6.2 Conclusion..........................................................................................................................................74
6.3 Recommendation................................................................................................................................75

Reference.................................................................................................................................................................1

iv
E -Learning system for bit

LIST OF TABLES
Table 1.1 to show hardware cost....................................................................................5
Table 1.2 tasks and time schedule..................................................................................6
Table 2.1 log in description..........................................................................................14
Table 2.2 logout description.........................................................................................15
Table 2.3 approve student description.........................................................................16
Table 2.4 Admin update student description................................................................17
Table 2.5 Admin delete student description.................................................................18
Table 2.6 Admin search student description................................................................19
Table 2.7 admin add instructor description..................................................................19
Table 2.8 Admin delete instructor description.............................................................20
Table 2.9 Admin search instructor description............................................................21
Table 2.10 Admin update instructor description..........................................................22
Table 2.11 Admin add department description............................................................23
Table 2.12 Admin update department description.......................................................24
Table 2.13 Admin search department description........................................................25
Table 2.14 Admin delete department...........................................................................26
Table 2.15 Admin add course description....................................................................27
Table 2.16 Admin search course description...............................................................28
Table 2.17 Admin update course description...............................................................29
Table 2.18 Admin delete course description..............................................................30
Table 2.19 instructor uploads file description...........................................................31
Table 2.20 instructor add exercise description.............................................................32
Table 2.21 instructor delete exercise description.........................................................32
Table 2.22 instructor delete upload file description.....................................................33
Table 2.23 change password description.....................................................................34
v
Table 2.24 forum description.......................................................................................35
Table 2.25 students download files description...........................................................36
Table 5.1 Tasting schedule table..................................................................................69
Table 5.2 pass and fail criteria table.............................................................................71
E -Learning system for bit

Table 5.3 Estimated risk and contingency plan...........................................................73

LIST OF FIGURES
Figure 2.1 use case diagram.........................................................................................13
Figure 2.2 login sequence diagram..............................................................................38
Figure 2.3 add department sequence diagram..............................................................38
Figure 2.4 upload sequence diagram............................................................................39
Figure 2.5 delete student sequence diagram................................................................39
Figure 2.6 add exercise sequence diagram...................................................................40
Figure 2.2.7 download sequence diagram....................................................................40
Figure 2.8 forum sequence diagram............................................................................41
Figure 2.9 administrator activity diagram....................................................................42
Figure 2.10 Student activity diagram...........................................................................43
Figure 2.11 Instructor activity diagram........................................................................43
Figure 3.1 System architecture for E-learning system.................................................45
Figure 3.2 class diagram..............................................................................................46
Figure 3.3 deployment diagram...................................................................................47
Figure 3.4 user interface flow diagram........................................................................48
Figure 3.5 home interface............................................................................................49
Figure 3.6 log in interface............................................................................................49
Figure 3.7 admin log in................................................................................................50
Figure 3.8 admin home page........................................................................................50
Figure 3.9 student home page......................................................................................51
Figure 3.10 add department interface...........................................................................51
Figure 3.11 instructor list of course interface..............................................................52
Figure 3.12 add question interface...............................................................................52
Figure 3.13 instructor add announcement interface.....................................................53
Figure 3.14 e book interface.........................................................................................53
Figure 3.15 course table...............................................................................................56
vi
Figure 3.16 department table........................................................................................56
Figure 3.17 faculty table..............................................................................................57
Figure 3.18 file table....................................................................................................57
E -Learning system for bit

Figure 3.19 instructor table..........................................................................................58


Figure 3.20 student table..............................................................................................58
Figure 3.21 video table.................................................................................................59
Figure 6.1 uploading video in the system....................................................................74
Figure 6.2 uploaded video in the database...................................................................74

ACRONYMS
PHP …............................... Hypertext Pre-processor
XAMPP…………………. Cross plat form Apache MySQL PHP Perl
HTML……………………. Hypertext Markup Language
CSS…................................. Cascading Style Sheet
SQL………………………. Standard Query Language
MS ….................................. Microsoft
BiT ……………………… Bahirdar institute of Technology
DB …................................. Database

vii
E -Learning system for bit

ABSTRACT
E learning is the use of Internet technologies as well the pedagogical approach of
advancing the scalability of knowledge and performance. Due to the fastest growth of
Information and Communication Technology, the impact of E-learning for the
contribution of quality education become vital, leading to a great paradigm shift for higher
educational institution in general and Bahir Dar university Institute of Technology in
particular.

This study examines the impact of e learning to enhance quality of education through
implementing it as a blended learning approach for boosting the learning teaching process
within the academic settings. This study also confirms that the application of e-learning in
BiT extensively facilitates e learning as a tangible asset to build up the students’ intension
and perception to technology as well as fostering the quality of education via assisting
them to improve their learning knowledge and skills by accessing their particular courses’
materials online.

By using the secondary data a source of information to conduct the analysis, the study
verified that, the application of e-learning trainings for Instructors and delivering their own
courses on the e-learning platform have contributed a lot for positively influencing both
stakeholders achieving the prospective successes and significant effects on improving
the momentum of providing greater access to the students, enhance an institution’s
reputation and enrich the teaching and learning experiences.

This work has enabled the delivery of learning materials to be efficient and it has also
achieved inter exercise among students and instructors. Furthermore, it has established the
support education based learning theory along with the collaborative based to be
applicable for the BiT.

viii
E -Learning system for bit

CHAPTER ONE

1. INTRODUCTION
1.1Background of the project
Bahir Dar University is found in Bahir Dar Town, the capital of the Amhara National
Regional State. The University is a combination of two smaller institutes formed earlier,
after the departments were gradually raised to a degree level starting from 1996. Poly
campus is one of the branches of Bahir Dar University the name is changed to Bahir Dar
institute of technology. High-qualified 460 teachers, more than 150 technical assistance
and about administrative staffs support the institute’s teaching-learning system, research
and community service activity and there are five faculties in BiT.

 Faculty of Chemical and food Engineering


 Faculty of Civil and water resource Engineering
 Faculty of Computing
 Faculty of Electrical Engineering
 Faculty of Mechanical and Industrial Engineering

Teaching and Learning process is the major part of the university and the way to sharing
knowledge between instructor and students.

Now a day technology is having a major impact on growing use of computer. Among the
contribution of technology, software development technology for task play a critical role
in almost all areas where computer is used. The influence of technology is currently
globalized for computer based information system for their personal and organizational
tasks. Thus, our project team was initiated to work Design and implement e-learning
system in Bahirdar institute of technology (BiT).

Because E-learning is giving stiff competition to the classroom learning technique. The
reasons are many. More and more Students are using Internet these days. The use of
Internet has given rise to the various educational learning modes such as online learning. E
learning is gradually becoming an easier way of imparting knowledge.

Many institutes promote their e-learning courses. Lot of students is adopting this method
as a preference over traditional classroom method of learning. E learning is a flexible form
of learning. This is the reason why more and top institutes are adopting e learning. It is a
E -Learning system for bit

step towards accepting technology with education. It is expected that in near future the e-
learning method with the help of e-notes will replace the publishing methods.

E Learning has substantial benefits and offers unique opportunities for people who might
otherwise have limited access to education and training. It incorporates innovative and
creative approaches to instruction and provides unprecedented access to resources and
information.

Some of the benefits are summarized below:

E Learning is student centered. The learner is the core of any e-Learning system. Materials
and activities are designed with the needs and interests of the learner in mind. Students
assume control of their learning experience and use it to suit their specific needs.

E Learning is self-directed and self-paced. Students control the amount of time spent on a
topic. This allows learners to skip material they already understand or to spend additional
time on difficult areas. This individualized approach usually allows learners to complete
their education and training faster than in traditional courses.

E Learning is interactive and hands-on. The use of a variety of multimedia increases


student involvement and reinforces the learning experience. This leads to increased
retention and a stronger grasp of the subject at hand.

E Learning is flexible. Learning can take place anytime and anywhere, if the necessary
equipment is available. The logistics and expense of face-to-face education and training
can be extremely limiting when students are separated by distance.

E Learning also allows physically or otherwise challenged students to more fully


participate.

1.2Statement of the problem


The statement of problems with the manual system is the instructors may not be available
at the time when the student is convenient, all learning material is not available for the students
at a time, which means each leanings distribution process is slow, expenditures of resources
like: papers, printer, handouts and worksheets also there are many problem in this system
including the all-important resource prepared on hard copy is difficult in the business
angle, lack of exercise for student and few contact between the instructor and student.

If a student is registered for the first time (as a beginner), he has to bring his original
documents and it will be returned after checking or if the student is senior, he have to
E -Learning system for bit

come to the department office to take a slip and most of the time there is no reference
books in the library for students and they don’t have access to refer other course material
other than their handouts.

1.3Objective of the project

1.3.1 General objective


The general objective of this project is to develop E-Learning system for BIT

1.3.2 Specific objective


We describe the specific objective as below: -

 Review the current system and its problem


 Study each activity of the current system to identify related problem
 Gather and analyze the requirements for the e-learning system and
provide a medium for discussion and communication between student and student
or student and teacher.

 Identify functional and non-functional requirement


 Model the new system
 To develop a prototype model or design
 To implement a solution
 Helps students master their subject matter by providing multimedia learning tools
(e-library, videos, demonstrations)

1.4Scope of the project’

The scope of the Project is mainly focused on developing E-Learning System for BIT that
largely focuses on developing web based application system including the following
functionalities:

 Uploads of learning resources (handout, reference, and teaching videos)


 Downloads of these learning resources (handout, soft copy, video teachings)
 Add exercise.
 View the result of exercise
 Add user (student and instructor)
E -Learning system for bit

 Add department and course


 Online Chat room service for all users
 Discussion forum used for discussion between students with course and content
manager in academic issues.
 E-Book’s system

1.5Limitations

Limitation is what we have not included to our Project or what we do not going to
implement in this project. Those are:

 No attendance
 Regarding with teaching and learning process even if some different activities, we
focus only with resource distribution and what we have explained under the scope
of the project.
 The system only displays the result of exercise only as soon as the student submits.
 No time schedule

1.6Methodology of the project

1.6.1 Data gathering methodology

For gathering data and information the following tools are employed

 Document analysis
 Observation
1.6.2 Data analysis methodology

In this project, we will use object-oriented methodology to model the functionality of


the system, to organize the objects, classes, to identify the relationship between each
objects and classes and the behavior of the objects. Because object oriented
methodology enables us to reuse, maintain, modify design and code of the system and
it increases consistency among analyzer, designer and taste

1.7Software requirements

Software is any set of machine-readable instructions that directs a computer's processor to


perform specific operations. Some software, which used to project:
E -Learning system for bit

 MySQL as database storage.


 MS-Visio-used to design like system use case, class diagram and the likes.
 XAMPP is the most popular PHP development environment and the place, which
link to the database.
 JavaScript: - JavaScript is very interesting language used to validate data and
develop different messages.
 Notepad ++: - is a source code editor for Windows.
 MS-word- used to prepare project proposal and document.

Hard ware requirement

Minimum hardware requirements for the system server


 Any computer
 3.4GHz CPU
 GB RAM
 100 GB hard disk

Minimum requirement for the desktops/ client machines/.


 Any computer
 32MB RAM
 40 GB hard disk

Implementation methodology
The software’s used are:-

 For the front end:- adobe Dreamweaver cs6, phpstorm


 For the back end:-MySQL

1.8Estimated budget

The estimate budget for the proposed system is 12,282 Ethiopian birr
Material Quantity Unit price in birr Price in birr
Paper 1ream A4 30 30
Pen 3 4 12
Flash 1(8GB) 120 120
Computer 1 12,000 12,000
Paper copy 120 1200 1200
E -Learning system for bit

Total 12,282 birr


Table 1.1 to show hardware cost

1.9Tasks and Time schedule.

Time evaluation is the most important consideration in the development of project. The time
schedule required for the development of this project is very important since more
development time effect machine time, cost and cause delay in the development of the
systems.Regarding our current source, technology and our ability the time that takes to
complete

This system successfully will be. (7 months.)

Tasks Months

N Steps Oct.20- Dec.1- Juan.2- Juan.16 Feb.16- May.1- May.16


o Nov.30 Juan.1 Juan.1 - April.30 May.1 -June.5
5 Febr.15 5

1 Proposal
preparation and
Presentation

2 Data collection
and Requirement
specification

3 System analysis

4 System design

5 Implementation

6 Testing

7 Documentation

To Overall project
tal time
Table 1.2 tasks and time schedule
E -Learning system for bit

1.10 Significance of the project


The main benefit of this project is to help the BIT teaching and learning support system
process:

 To perform their works faster, efficiently and accurately.


 To reduces costs in both the students and the institution side.
 To speed up the service teaching process of BIT.
 To easy access of uploaded resources.
 Secure and with wise use of resources available.
 Protect unauthorized access.
 To easy access of exercise.
 Helps to administer learning system.
 To helps student to developed with technology.

1.11 Benefits of the system


The Bahir Dar Institute of technology established with the objectives, to produce
technically sound and practically competent, job creators with relevant knowledge, skills
and attitude that would contribute to the development of the country.

This institute consists around 5000 students in regular and distance education students. To
provide this learning program the institute uses the following system:

 Registration
 Courses
 Exams

Registration

To register student and begins learning in the Bahir Dar institute of technology the student
should bring his original and copy of documents needed for his registrar office. Then the
institute validates his documents and if the student is qualified, he will fill a registration
form. After that, his documents and records will be transported to the Registrar office. The
Registrar office checks the document of the student again and recorded it into data. But
currently most of the students have registered.

Regular Lecture Class

Regular lecture class is the main methods used by the institute for teaching and learning
process. This method is run in the classroom by face-to-face contact with the instructor.
E -Learning system for bit

Even though, it is good opportunity to discuss the course in detail the teaching and
learning process limited to the traditional classroom method of learning with the absence
of flexibility form of lecture method.

Course materials

Course materials are prepared in the form of hard copy for all courses. Some courses have
additional references book in the library even if, not enough in the number and absence of
originality.

1.12 Organization of the project document


This document contains three chapters the first chapter (chapter one) is brief description of
background information of the project, method of data collection and analysis, also the
second chapter (chapter two) is description of the existing system, modeling and design of
the new system or proposed system and the last chapter (chapter three) is thedesign of the
abstraction solution; it is the general description of the solution to a problem without a
detail.
E -Learning system for bit

CHAPTER TWO

2. SYSTEM FUTURES
2.1Existing system description
An existing system compromises different players to carry out its job. Among those
different actors (players), the most common are Dean of school: the person who manages
the individual schools, Instructors: They produce some learning resources and teach
students and Students: Peoples who get the learning services.

Even though the department is near to the technology, the teaching and learning process is
not still supported by electronic learning. The most faculties use the hard copy for all
courses and sometimes use soft copy that are not suitable for all students. The existing
system also has many problems on different way, for example

 Performance related problem

Performance related problem could be measured by using throughput. These are


throughput of different processes in the existing system.

 Economic

This is the one problem in the existing system. This term indicates the loose of many for
prepare, copy and print the resource.

 Efficiency related problem

There is also an efficiency problem with the existing system. Workers waste their time due
to redundantly input data.

 Service
 The system is inflexible to new or exceptional situations
 The system is inflexible to change
 The system is not coordinated with other systems (standalone system)

To solve the existing problems, we attempt to build a computer based learning system for
BIT, which can perform efficiently handling Student information, to upload and download
any resources and Give exercise.
E -Learning system for bit

2.2Proposed system
As we stated the current system and all the identified problems in Bahir Dar Institute of
Technology. We state our proposed system relative the current system as follows.

 Registration

In the current system, if a student wants to register, he/she must come and register in the
Department office, but to avoid this face-to-face registration system we proposed online
registration. This is done by login into the official website of this proposed system
supports and fills the registration form and sends it with his documents needed through
the website.

 Course materials and tutorials

The institution is now spending much more money to prepare the course materials. As
they told us, they are now affected by the current economic crises. When we come to this
shows that the problems are also affecting the students and we believe that our proposed
system will overcome the problems.

This proposed system will provide online course materials that students can read and
download easily. Tutorials are kept in a video format, so they can download it in a format
they want to (even they can use it in any VCD/DVD players when they are at home). By
this system students can access the tutorials at any time they want. The handouts are also
kept in a PDF format therefore; the students can download and print it whenever he wants.

 Forum

The current system of department doesn't have any forum therefore if a student has a
question in his mind that has not been answered by any materials he has accessed the last
choice of the student is going to be leaving his question but the system we have proposed
doesn't support the student to keep quiet since it has a forum the student can post his
question and his question can be answered by various teachers and students in different
systems and ways.

 E- Library

There is a library found in the campus but there are no full materials for the students, and
this limits students to get a further knowledge by accessing the library. Therefore, most
students are dependent on only their handouts that are provided by the department, and we
proposed digital library system to overcome the above problems. This digital library
E -Learning system for bit

system has e-books, reference materials and researches that the students can read and
download easily.

 Online Chat room service

In the current system of the department, there is no such kind of service that provides
student and teachers to communicate each other there is only a direct or face-to-face
contact. However, the system we are going to develop is going to solve this kind of
problems by providing online contact with each other.

Preferred solution

After we discuss over the available solution our team decide to implement web-based
system using different kinds of system software.

2.3Functional Requirements
Functional requirements are describing the interaction between the environment and
independents of its implementation. The newly existing system has supposed to give
different computerized function and service to the employees and the students.

We are three actors in our system

 Administrator: Is Person who has a big authority on the system and managing
exercise over the system and manages the user (instructor and student).
 Instructor Is a person who has the privilege of uploading, and updating any
learning resources and adds exercise for students.
 Student Person who uses the system to download file and use what was uploaded
by instructor.

In this system, the functional requirements are:

 Log in: every user of the system must log in to get service from the system.

 Add exercise: The system should able to store the exercise into the database and
the student can take it when needed.

 Add student and instructor: The system helps administrator to add user.

 Delete student and instructor: The system helps the administrator to delete user.

 Uploads of resources: The system helps instructor to upload any necessary files
and documents that are usable for education purpose only.
E -Learning system for bit

 Downloads of resources: The students can download any documents that are
uploaded by the instructors.

 Add faculty: the admin can add faculty to the system.

 Add department: the admin can add department to the system.

 Add course: the admin can add course to the system.

 Add exercise: the instructor can add exercise to the system database.

 Update faculty: the admin can update faculty information.

 Update department: The admin can update instructor information.

 Update instructor: The admin can update instructor information.

 Update student: The admin can update student information.

 Update course: The admin can update course information.

 Delete exercise: The instructor can delete the exercise from the system database.

 Delete faculty: the admin can delete faculty.

 Search course, department, student and instructor: the admin search to update and
delete.

 Forum: this functional requirement is for all the system actors to discuss each
other.

 Logout: The system shall logout administrator, instructor and student

Depending on the actors and use case names listed above we have drawn the following use
case diagram. The description of use case is explained in the use case description.
E -Learning system for bit

2.4Use case model

Figure 2.1 use case diagram


E -Learning system for bit

2.5Description of use case diagram


Each use case we have used in this project is explained in the following tables.

Use case name: Login


Actor: Administrator, Instructor, Student
Purpose: This use case allows the Administrator, Instructor
and student to log in to the system
Pre-condition: The administrator, Instructor and student has an
account to log in
Flow of events 1.This use case is

Initiated when the administrator, Instructor and


student selects login form and inserts username and
password.

click on login button

3. The system check the password and inserted user

name to identify whether the user is authorized or


not

The system displays the administrator, Instructor and

Student homepage if the

User is legal user.


Post-condition: The administrator, Instructor and student logged in
to the system and perform what he/she want.
Alternative events: 3: If the User name and password is not valid,

3.1 send error notification to the administrator,


Instructor and student

3.2 administrators, Instructor and student re-insert


user name and password again.

3.3 click log in


Table 2.3 log in description

Use case name: Logout


E -Learning system for bit

Actor: Administrator, Instructor, Student


Purpose: This use case allows the Administrator, Instructor
and student to logout to the system
Pre-condition: The administrator, Instructor and student has login
into the system
Flow of events 1.This use case is

Initiated when the administrator, Instructor and


student select

Logout

click on logout button

3. The system return into the login page

Post-condition: The administrator, Instructor and student logout


from the system
Table 2.4logout description

Use case name: Approve Student


Actor: Administrator
Purpose: This use case allows the Administrator to activate
Student account in to the system.
Pre-Condition: The administrator login to the system and browse
manage Student
Flow of events action

1: This use case starts when the administrator browse


manage Student.

2: The system displays the Activation link.

3: Then he/she click on approve link

4: The system activate students account.

5: The system notifies the as the Student is activated


E -Learning system for bit

Post-condition: The administrator Activate the new Student.


Alternative events:
Table 2.5 approve student description

Use case name: Update Student


Actor: Administrator
Purpose: This use case allows the Administrator to change
some information about the Student.
Pre-Condition: The administrator login to the system and select and
identify the updated information
Flow of events action

1: This use case starts when the administrator browse


Update Student.

2: admin click on update

3: The system displays the Update Student form.

Enter the id of the student to be update

The system search the student and display the detail

: Then admin update the necessary information.

Then he/she click on button

The system checks the inserted information whether


valid or not.

The system notifies the as the Student is update

Use case ends after the confirmation is sent for the


administrator.
Post-condition: The administrator updates the student information.
Alternative event1 If the student not in the system

5.1 the system display message nonexistence of the


student

5.2 The admin try to insert the real id.


Alternative event2 8: The system determines the invalidation of the
inserted information
E -Learning system for bit

8.1 send notification to the admin to re-insert


information again

8.2 click on the update button.


Table 2.6 Admin update student description

Use case name: Delete Student


Actor: Administrator
Purpose: This use case allows the Administrator to remove
student from the system in different problem.
Pre-Condition: The administrator login to the system and select the
delete student.
Flow of events action

1: This use case starts when the administrator login


the system and selects delete Student.

The admin enters the id no of the student to be delete

The system searches the student from the system by


id no and displays the detail info about the student.

4: click on delete button.

5: The system notifies the as the Student is deleted.

6: Use case ends after the confirmation is sent for the


administrator.
Post-condition: The Student deleted from system.
Alternative events: 3: if the student not in the system

3.1 the system display notification to the admin

3.2 the admin try to insert the exact id of the student

3.3 click on search button


Table 2.7Admin delete student description

Use case name: Search Student


Actor: Administrator
E -Learning system for bit

Purpose: This use case allows the administrator to search the


Student from the system.
Pre-Condition: The Administrator should have to know the Student
id.
Flow of events action

1: This use case is initiated when the admin login and


select search student action.

2: insert id of the student to be searched

3: click search button.

4: The system process search functions for inserted


Student id.

5: Use case ends after the Student detail is display for


the administrator.
Post-condition: The system displays the searched Student detail.
Alternative events: 4: if the student id is not reachable or not in the
system

4.1 The system notifies the non-existence of


Student with the inserted Student id.

4.1 the system allows to enter the id again

4.2 the admin try to insert the real id again

4.3 click on search button


Table 2.8 Admin search student description

Use case name: Approve Instructor


Actor: Administrator
Purpose: This use case allows the Administrator to Activate
Instructor account in to the system.
Pre-Condition: The administrator login to the system and browse
Manage Instructor.
Flow of events action
E -Learning system for bit

1:This use case starts when the administrator browse


Activate Instructor.

2: The system displays Activation link.

3: Then he/she click on Activation link

4: The system notifies the as the Instructor is


Activated
Post-condition: The administrator Approve the new Instructor.
Alternative events:
Table 2.9 admin add instructor description

Use case name: Delete Instructor


Actor: Administrator
Purpose: This use case allows the Administrator to delete
unwanted Instructor from the system.
Pre-Condition: The administrator login to the system and select
delete

Instructor.
Flow of events action

1: This use case starts when the administrator login


the system and selects delete instructor.

2.The admin enter the id no of the instructor to be


delete

3. The system search the instructor from the system


by id no and display the detail info about the
instructor.

4: click on delete button.

5: The system notifies the as the instructor is deleted.

6: Use case ends after the confirmation is display for


the administrator.
Post-condition: The Instructor deleted from system.
E -Learning system for bit

Alternative events: 3: if the instructor not in the system

3.1 the system display notification to the admin

3.2 the admin try to insert exact id of the instructor

3.3 click on search button


Table 2.10Admin delete instructor description

Use case name: Search Instructor


Actor: Administrator
Purpose: This use case allows the administrator to search the
Instructor from the system
Pre-Condition: The Administrator log in and should have to know
the Instructor id to be searched.
Flow of events action

1: This use case is initiated when the admin login and


select search instructor action.

2: insert id of the instructor to be searched

3: click search button.

4: The system process search functions for inserted


instructor id.

5: Use case ends after the instructor detail is sent for


the administrator.
Post-condition: The system displays the searched Instructor.
Alternative events: 4: if the Instructor id is not reachable or not in the
system

4.1 The system notifies the non-existence of


Instructor with the inserted Instructor id.

4.1 the system allows to enter the id again

4.2 the admin try to insert the real id again

4.3 click on search button


Table 2.11 Admin search instructor description
E -Learning system for bit

Use case name: Update Instructor


Actor: Administrator
Purpose: This use case allows the Administrator to Update
Instructor information.
Pre-Condition: The administrator login to the system and select and
identify the updated information
Flow of events action

1: This use case starts when the administrator browse


Update Instructor.

2: admin click on update

3: The system displays the Update Instructor.

4. Enter the id of the Instructor to be update

5. The system search the Instructor and display the


detail

6. Then admin update the necessary information.

7. Then he/she click on button

8. The system check the inserted information whether


valid or not.

9. The system notify the as the Instructor is update

10. Use case ends after the confirmation is sent for


the administrator.
Post-condition: The administrator updates the instructor information.
Alternative events1 5. If the Instructor not in the system

5.1 the system display message nonexistence of the


instructor

5.2 The admin try to insert the real id.


Alternative events2 8: The system determines the invalidation of the
inserted information

8.1 send notification to the admin to re-insert


E -Learning system for bit

information again

8.2 click on the update button.


Table 2.12 Admin update instructor description

Use case name: Add Department


Actor: Administrator
Purpose: This use case describes the process of add
Department information.
Pre-Condition: The system must verify the user to add the content.
Flow of events Action

This use case initiated by when administrator login


and click on add department.

2. The system display form

3.admin fill information

4.click on button add

5. Add will record on the system.

6. Use case ends.


Post-condition: Admin can view added department.
Alternative events: 4. Post condition is failing

4.1 the system will display an error message

4.2 The admin return to check the existence of


pre-condition.
Table 2.13 Admin add department description

Use case name: Update Department


Actor: Administrator
Purpose: This use case allows the Administrator to Update
information about the department.
Pre-Condition: The administrator login to the system and select and
identify the updated information
E -Learning system for bit

Flow of events action

1: This use case starts when the administrator browse


Update Department form. 

2: The system displays the Update Department form.

3. Enter the name of the Department to be update

4. The system search the Department and display the


detail

5. Then admin update the necessary information.

6. Then he/she click on button

7. The system checks the inserted information


whether valid or not.

8. The system notify the as the Department is update

9. Use case ends after the confirmation is sent for the


administrator.
Post-condition: The administrator updates the department
information.
Alternative events1 4. If the department is not in the system

4.1 the system display message nonexistence of the


department

4.2 The admin try to insert the real department


name.
Alternative events2 7: The system determines the invalidation of the
inserted information

7.1 send notification to the admin to re-insert


information again

7.2 click on the update button.


Table 2.14 Admin update department description

Use case name: Search Department


E -Learning system for bit

Actor: Administrator
Purpose: This use case allows the administrator to search the
wanted Department from the system
Pre-Condition: The Administrator log in and should have to know
the Department name to be searched.
Flow of events action

1: This use case is initiated when the admin select the


search Department and browse.

2: insert department name

3: click search button.

4: The system process search functions for inserted


Department name.

5: The system displays the Department

6: Use case ends the administrator selects the


Department from displayed Department.
Post-condition: The system displays the searched Department.
Alternative events: 4: if the department is not in the system

4.1The system notifies the non-existence of


Department with the inserted Department name

4.2 the system allows to enter the department name


again

4.3 the admin enters the valid department


Table 2.15 Admin search department description

Use case name: Delete Department


Actor: Administrator
Purpose: This use case allows the Administrator to Delete
unwanted department.
Pre-Condition: The administrator login to the system and select
delete department
Flow of events action
E -Learning system for bit

1: This use case starts when the administrator login


the system and selects delete department button.

2.The admin enter the code no of the department to


be delete

3. The administrator searches the department from the


system by code no and displays the detail info about
the department.

4: click on delete button.

5: The system notifies the department is deleted.

6: Use case ends after the confirmation is sent for the


administrator.
Post-condition: The department find to delete was deleted
Alternative events1 3: if the department is not in the system

3.1 the system display notification to the admin

3.2 the admin try to insert real code of the


department

3.3 click on search button


Table 2.16 Admin delete department

Use case name: Add Course


Actor: Administrator
Purpose: This use case describes the process of add course in
to the system.
Pre-Condition: The Administrator log in and go into course
Flow of events Action

1. This use case initiated by the administrator when is


browse add course.

2: administrator insert course name and course code


then click button.
E -Learning system for bit

3. Add will record on the system.

4. Use case ends after the course is add to the system.


Post-condition: Admin can view added course and the course is
adding to the database.
Alternative events: 4. Post condition is failing

4.1 the system will display an error message

4.2 The admin return to check the existence of


pre-condition.
Table 2.17Admin add course description

Use case name: Search Course


Actor: Administrator
Purpose: This use case allows the administrator to search the
Course from the system
Pre-Condition: The Administrator log in and should have to know the
Course code.
Flow of events action

1: This use case is initiated when the admin login and


select search course.

2: insert id of the course to be searched

3: click search button.

4: The system process search functions for inserted


course code.

5: Use case ends after the course detail is sent for the
administrator.
Post-condition: The system displays the searched Course.
Alternative events: 4: if the course code is not reachable or not in the
system

4.1 The system notifies the non-existence of course


E -Learning system for bit

with the inserted course code.

4.1 the system allows to enter the code again

4.2 the admin try to insert the real code again

4.3 click on search button


Table 2.18Admin search course description

Use case name: Update Course


Actor: Administrator
Purpose: This use case allows the Administrator to Update
information about the course.
Pre-Condition: The administrator login to the system and select and
identify the updated information
Flow of events action

1: This use case starts when the administrator browse


Update course form.

2: admin click on update

3: The system displays the Update course form.

4: Enter the course code to be update

5. The system search the code and display the detail

6. Then admin update the necessary information.

7. Then he/she click on button

8. The system checks the inserted information


whether valid or not.

9. The system notify the as the course is update

10. Use case ends after the confirmation is sent for


the administrator.
Post-condition: The administrator updates the course information.
Alternative events1 4: if the course is not in the system

4.1The system notifies the non-existence of course


with the inserted course code
E -Learning system for bit

4.2 the system allows to enter the department name


again

4.3 the admin enters the valid department


Alternative events2 8: The system determines the invalidation of the
inserted information

8.1 send notification to the admin to re-insert


information again

8.2 click on the update button.


Table 2.19 Admin update course description

Use case name: Delete Course


Actor: Administrator
Purpose: This use case allows the administrator to delete the
add Course by the course code if not needed so far
Pre-Condition: The administrator log in and the course code needed
to be deleted should exist.
Flow of events action

1: This use case starts when the administrator login


the system and selects delete course button.

2.The admin enter the code no of the course to be


delete

3. The system search the instructor from the system


by code no and display the detail info about the
course.

4: click on delete button.

5: The system notifies the as the course is deleted.

6: Use case ends after the confirmation is sent for the


administrator.
Post-condition: The course find to delete was deleted.
Alternative events: 3: if the course is not in the system
E -Learning system for bit

3.1 the system display notification to the admin

3.2 the admin try to insert real code of the course

3.3 click on search button


Table 2.20 Admin delete course description

Use case name: Upload file


Actor: Instructor
Purpose: This use case allows the Instructor upload the
learning resources and other necessary documents to
the system
Pre-Condition: The instructor should have to prepare resources to be
uploaded.
Flow of events action

1: This use case is initiated when the Instructor


selects the Upload resources button.

2: The system displays the Upload form.

3: The Instructor fill name of course, course code and


selects the documents to be uploaded and click on
upload

4: Use case ends the system process and uploads the


resources.
Post-condition: The document will be uploaded on the data base.
Table 2.21instructor uploads file description

Use case name: Add exercise


Actor: Instructor
Purpose: This use case is used for the instructor to add exercise
in to the system.
Pre-Condition: The instructor should have to prepare the exercise
that he wants to add.
Flow of events action
E -Learning system for bit

1: First the Instructor login to the system and click on


the add exercise button.

2: The system displays the add exercise form.

3: The Instructor selects the course and gives the


exercise name and insert how many questions he/she
want add.

4: The instructor adds the activities.

5: click add button

6: The system process the added exercise.

7: The system notifies the exercise successfully


added.

8: Use case ends after the notification is sent for the


Instructor.
Post-condition: The exercise will be added.
Table 2.22 instructor add exercise description

Use case name: Delete exercise


Actor: Instructor
Purpose: This use case allows the instructor delete the added
exercise by the course code if not needed so far.
Pre-Condition: The course code of exercise needed to be deleted
should exist first.
Flow of events action

1: This use case is initiated when the instructor insert


the course code and click button

2: The system searches the course code with inserted


course code.

3: The system deletes the exercise.


E -Learning system for bit

4: The system notifies the as the exercise was deleted.

5: Use case ends after the instructor seen deleted


confirmation.
Post-condition: The exercise find to delete was deleted.
Alternative events: 2: The system notifies the non-existence of course
with the inserted code.
Table 2.23 instructor delete exercise description

Use case name: Delete upload file


Actor: Instructor
Purpose: This use case allows the Instructor delete the
uploaded resources by the course code if not needed
so far.
Pre-Condition: The course code of exercise needed to be deleted
should exist first.
Flow of events action

1: This use case is initiated when the Instructor insert


the course code and click button

2: The system searches the resource with inserted


course codes.

3: The system deletes the resource.

4: Use case ends after the Instructor seen deleted


confirmation.
Post-condition: The resource find to delete was deleted.
Alternative events: 2:The system notifies the non-existence of resources
with the inserted code.
Table 2.24 instructor delete upload file description

Use case name: Change password


Actor: Instructor, Admin and student
Purpose: This use case allows the instructor, admin and student
E -Learning system for bit

to change the default password.


Pre-Condition: The instructor, admin and student had to be valid
user, they had to valid account.
Flow of events action

1: This use case starts when the instructor, admin and


student selects change password and browse.

2: The system allows filling the form...

3: The instructor, admin and student fill the form

4: Validate the filled information

5: The system notifies the change is complete.

6: Use case ends after the notification is sent for the


instructor, admin and student.
Post-condition: The instructor, admin and student change the default
user name and password.
Alternative event 4: the system allows the instructor, admin and
student to enter the valid information again.
Table 2.25 change password description

Use case name: Forum


Actor: Instructor and student
Purpose: This use case allows the instructor and student to
communicate and discus each other
Pre-Condition: The instructor and student must log in to the system
Flow of events action

1: The instructor and student asks the system to log in

2: The system displays the Log in form

3: The instructor and student inputs the required


Information

4: The system Accepts input

5: The system checks input


E -Learning system for bit

6: The instructor and student log in to the system if


system allows to access

7: They asks the system to display the discussion


forum

8: The system displays the discussion forum per the


instructor and student.

9: The instructor and student post his idea or give a


comment to the provided comment area

10: The instructor and student closes the system after


finishing his Discussion forum
Post-condition: Use forums
Alternative event 5: If the instructor and student enters an invalid login
account then:

5.1The system displays a message indicating that


the login is invalid and asking the instructor and
student to enter a different Login ID.
Table 2.26 forum description

Use case name: Download files


Actor: Student
Purpose: This use case allows the Student to download
resources.
Pre-Condition: The Student must be valid user, they must valid
account.
Flow of events action

1: This use case starts when the Student selects


download button.

2: The Student inserts the course code he/she wants to


download and click on button.

3: The system displays the resources with inserted


course code.
E -Learning system for bit

4: The selects the document he/she want to download


and click on download button

5: The system process downloading.

6: The system notifies the download completed.

7: Use case ends after the notification is sent for the


student.
Post-condition: The Student downloads the document he needs.
Table 2.27 students download files description

2.6Non-Functional requirements
A. Security

Our system is secured with different secure mechanisms. In another way authentication is
provided to all the users, only authenticated users can use. In every application before the
user uses it there is an authentication with user name and password. If a student needs to
use a resources or forum the students must login first unless the resources and the forum
parts are not active and the course and Teacher have to log in first to upload resources this
Teacher account is created by the system administrator also this system administrator have
password and user name he must login first before he does any works, this system
administrator also creates account for the students. The security is used to protect
unauthorized persons.

B. User Interface

The developed system provides web application user interfaces that are compatible with
browsers like Internet explorer, Mozilla Firefox, Google chrome.

C. Reliability

Any new system that is going to be developed should not be subject to failure during its
operational stage. In other words, the system should operate smoothly without causing
any unexpected failure. Therefore, the system that we are going to develop is expected to
address this issue. Our system can address issue to the addressable body detail of the
failure of the system and problems occurred there and the reference how to fix the problem
by guessing.
E -Learning system for bit

D. Accuracy

Any system user needs an accurate and correct data from the system that he/she uses for
the preparation of reports as well as to make sound and relevant decisions. We can easily
imagine the consequences of any decision that made inaccurate and incorrect data their
basis. Implementing several validities checks on the number validity on the person
entering the data as well as the data that is going to be entered to the records of the system.

E. Simplicity

Since these users are expected to have a little knowledge expertise about computers and
not to the specific system, the system should be easy to use and simple to manipulate.
This could be made possible through use of different user- friendly interfaces

F. Resources

The system must be compatible with specified hardware and software environment.

G. Pseudo requirement

One of the many good qualities of any system is it is in Dependency of hardware


platforms. Meaning a system’s functionality should not depend on the type of computer
used and type of operating system running. The user should be to take and implement it
wherever and whenever he/she has the desire of doing so.

2.7Analysis models

2.7.1 Sequence diagram


A sequence diagram is a form of interaction diagram, which shows objects a lifeline
running down the page time and their interactions over there represented, or message
arrows.

Arrows shows from the source lifeline to the target lifeline. Sequence shows object
communicate with each other and what messages trigger for those communications

Log in sequence diagram

This sequence diagram is belonging to login use case that show the sequence of action to
make

The user log in to the system and perform the task he/her privileged.
E -Learning system for bit

login Sequence diagram

Homepage Loginform Logincontrol Bit DB

open()

display()

fill_information()

click_login_button() validate()
check()

invalid()

invalid()

fill_correctly()

Log in successfully()

Figure 2.2login sequence diagram

Add department sequence diagram

The below sequence diagram is indicating the flow of the action that the administrator
how to add the department to the system database.

add department sequence diagram

admin_homepage add button add form add control Bit DB

open()

click_add_button() display()

write_department_name()

click_add_button()
validate()

invalid()
added()

saved to DB()

successfully_uoloaded_acknowledgment()

Figure 2.3 add department sequence diagram

Upload sequence diagram

Uploading file to the system is the role of the instructor this sequence diagram show the
action performs on upload file to the system. After the entire file is stored on, the database
and the sequence completed.
E -Learning system for bit

upolad sequence diagram

course page upload btn upload form upload control Bit DB

open()

click_upload_button()
display()

select the_document_to_be_uploaded()

click_upload_button() validate()

invalid()
uploaded()

savded to DB()

successfully_uploaded_acknowledgment()

Figure 2.4 upload sequence diagram

Delete student sequence diagram

This is the task of the administrator of the system. As we see from the above diagram the
admin first login in to the system, select the delete button, and enter the id number of the
student to be deleted from the system after the system search the student allow to the
admin to delete the student. After all the student delete from system database.

Delete student sequence diagram

admin page delete_btn form form control

open()

click_delete_button()
display()

inter_valid_stud_id_no()

click_delete_button() validate()

invalid()
delete()
Re_enter_stud_id_no()

student_info_deleted()

successfully_student_deleted()

Figure 2.5 delete student sequence diagram


E -Learning system for bit

Add exercise sequence diagram

This sequence diagram use for the instructor to upload exercise to the system database
used for the student to take and exercise them. This action go thought the sequence above
as indicated finally the exercise added to the system database to temporarily store.

Add exercise squence diagram

ins homepage add ex button add ex form controller Bit DB

open()

click_on_add ex_button()
display()
select_course()

inter_the_ex_name()

inter_number_of_question() validate()

insert_the_question() save to DB()

click_on_button()

invalid()

saved to DB()

successfully added_to_db_acknowledgment()

Figure 2.6 add exercise sequence diagram

Download sequence diagram

This sequence diagram shows the flow of the action use for the user to download file from
the system database.

Download Sequence diagram

Student Studentpage Download.btn Download form Download control BiT server

open()

click_download_button()
display

inter_course_code()

click_download_button() validate()

invalid()
Process download()
inter_the_correct_one()

Downloaded()

Successfully_download_acknowledgement()

Figure 2.2.7 download sequence diagram


E -Learning system for bit

Forum sequence diagram

This allows the users to communicate each other and make a network between them. This
strength the relationship between the user of the system and allow the user to ask what
they want concerning to their learning and teaching process only.

Forum sequence diagram

home page login form account controller account forumpage Bit DB

open()

inter_info()
pass_info()

checked()

validate()

Re_fill_the_information() invalid()

upload comment()

successfully_message()

Figure 2.8forum sequence diagram

2.7.2 Activity Diagram


Administrator Activity diagram

This activity diagram belongs to administrator of the system. It is flow of action to log in
to the administrator page. First the system check the user name and password of the admin
after that if the user name and the password is valid the system display the admin home
page else back and allow the admin to enter the valid one.
E -Learning system for bit

Administrator activity diagram

Admin login

insert username&password

[ no]

Is user name
&password
correct?

[yes]

adminstrator home page

Figure 2.9 administrator activity diagram

Student activity diagram

This diagram is belonging to student log in use case. It is flow of action that log in to the
system. The system check whether the user name and the password of the student and if it
is authenticating user it displays the page of the student else back and allow the student to
enter the exact user name and password.
E -Learning system for bit

Student activity diagram

Student Login

insert username&password

[no]

Is username
&password
correct?

[yes]

Student home page

Figure 2.10 Student activity diagram

Instructor log in activity diagram

This diagram is belonging to instructor log in use case. it is flow of action that log in to the
system. The system check whether the user name and the password of the instructor and if
it is authenticating user it displays the page of the instructor else back and allow the
instructor to enter the exact user name and password.

Instructor activity diagram

Instructor Login

insert username&password

[ no]

Is user name &


password
correct?

[yes]

display home page

Figure 2.11 Instructor activity diagram


E -Learning system for bit

CHAPTER THREE

3. SYSTEM DESIGN
3.1Introduction
Design is the abstraction of a solution; it is the general description of the solution to a
problem without a detail. Design is view pattern seen in the analysis phase to be a pattern
in a design phase. After design phase, we can reduce the time required the implementation.

3.2Design goals
The design goals represent the desired qualities of E-learning system and provide a
consistent set of criteria that must be considered when making design decisions. Based on
non-functionality requirements the following design goals should achieved to qualify the
system as successful:

Robustness: the system must be robust enough to manage any valid input from the users.

Reliability:

 The system should perform the E-learning system operations with no errors.
 The website developed should be extremely reliable and secure so that information
about any users in the system

Security: the system security is one of the most important non-functional requirements.

Availability:

 Students can access the system anywhere and anytime internet service is available.

 System should be able handle multiple users.

 This system must run on multiple operating systems and it has cross platform

3.3Hardware and software architecture

3.3.1 Proposed Software Architecture


Here we design the conceptual model for the proposed system that describes the
relationship major participant in E-learning system.
There is a client and the administrator who would like to use a computerized learning
system.
E -Learning system for bit

The administrator provides the necessary technical and financial infrastructure to facilitate
computerized learning system.
E-learning system: The proposed software has the following layers of architecture. These
are
Interface: There are two categories of interface class – user interface (UI) classes that
provide people access to your system and system interface (SI) classes that provide access
to external systems to your system.
Domain: This layer implements the concepts relevant to our business domain, focusing on
the data aspects of the business objects, plus behavior’s specific to individual objects.

Process: The process layer implements logical system that involves collaborating with
several domain (system) classes or even other process classes in the system.
Persistence (data): Persistence layers encapsulate the capability to store, receive and
delete Objects/data permanently without revealing details of the system.

System: System classes provide operating-system-specific functionality for the


applications, isolating the software from the operating system (OS) by wrapping OS-
specific features, increasing the portability of the application.

Business External
logic System

Web forms
Web server
<Web
Data store
browser> <Apache>
MYSQL

Business class
Interfaces

Figure 3.12 System architecture for E-learning system


E -Learning system for bit

3.4Class diagram
Our class diagram includes all the system class name, attribute and method together and
the classes have relation between them and relation name. Class name include
-administrator, instructor, exercise, course, department and forum. Each class has attribute
and method we discuss detail below with a diagram.

Figure 3.13 class diagram


E -Learning system for bit

3.5Deployment Diagram
The deployment diagram shows how our system will be physically deployed in the
hardware environment. Its purpose is to show where the different components of the
system will physically run and how they will communicate with each other. Since the
diagram models the physical runtime, a system's production staff will make considerable
use of this diagram. The notation in a deployment diagram includes the notation elements
used in a component diagram, with a couple of additions, including the concept of a node.
A node represents either a physical machine or a virtual machine node (e.g., a mainframe
node).

:Application Server

:DB Server
:Web Server
:Container
Student
E-Learning * *
Adminstrator Persistance
* *
*

Instructor *
BiT DB

Student

<<Deployment Spec>>
E-learning

Execution: thread
* *
nested Transaction
:true

Persistence
<<infrastructure>>

E-Learning
System
<<Web services>>

Figure 3.14 deployment diagram


E -Learning system for bit

3.6User interface

3.6.1 User interface flow diagram


User interface flow diagram shows the relationships between the major user interface
elements (screens, reports, and so forth) that compose our application. User interface flow
diagrams are typically used for one of two purposes. First, they are used to model the
interactions that users have with our software, as defined in a single use case. Second, they
enable us to gain a high-level overview of the user interface for our application.

Figure 3.15 user interface flow diagram


E -Learning system for bit

Home page interface

Figure 3.16 home interface

Login interface

Figure 3.17 log in interface


E -Learning system for bit

Admin login interface

Figure 3.18 admin log in

Admin home page interface

Figure 3.19 admin home page


E -Learning system for bit

Student home page interface

Figure 3.20 student home page

Admin add department interface

Figure 3.21 add department interface


E -Learning system for bit

Instructor list of course interface

Figure 3.22 instructor list of course interface

Instructor add question interface

Figure 3.23 add question interface

Instructor announcement interface


E -Learning system for bit

Figure 3.24 instructor add announcement interface

Digital library interface

Figure 3.25 e book interface


E -Learning system for bit

3.7Data base Design (Persistent Data modeling)

Among the various types database design models Relational database management system
is used so it needs to work on persistent modeling. Relational databases do not completely
support object-oriented concepts, so the design of the database is different from the design
of class diagram. Persistence models enable to design the schema of the database.

It is divided into three phases: conceptual, logical and physical modeling.

Conceptual – is the process of constructing a model of the information, independent of


physical considerations.

Logical – is the process of constructing a model of the information based on a specific


data model.

Physical – is the process of producing description of the database on the


secondary storage.
In BiT E learning system, the following tables are used to store information:

1. admin: to keep information about the admin

2. announcement: used to keep information announcement

3. Assignment: used to store instructor upload assignments.

4. comment: used to store comments of file

5. contact: used to keep information of contacts


6. course: used to keep course information

7. course_description: used to keep information about description courses


8. Department: used to keep information about department
9. EBook: used to store books and its information

10. Exam: used to store title of exercises

11. Faculty: used to keep information about faculty

12. File: used to store uploaded files and its information.

13. Forum_answer: userd to store forum answers

14. Forum_questions:used to store forum questions

15. Instructor: used to keep information about instructors


E -Learning system for bit

16. Question:used to store exercise questions

17. Student: used to keep information about students

18. Student_answer: used to store student answers and session of students

19. Student_result: used to store exercise result of student

20. Sub_assignment: used to store submitted assignments

21. Teacher_course: used to store information about instructor’s course

22. User: used to store information about the users

23. Video: used to store uploaded videos

3.7.1 Conceptual Database Design


This includes identification of entities, relationship types, attributes, determination of key
attributes, specialization/ generalization of entity types and modeling Entity-Relationship
diagram.

Identify Entity types

Entities are simply classes that have data, but no functionality. It represents groups of
objects possessing the same properties.

Entities are:
- Admin - Student - Course
- Instructor -Forum -Exercise
- Department - faculty -eBook

3.7.2 Logical Database Design

This deals with process of translating the conceptual representation to the logical structure
of the database and designing the relations. It also includes refining mapping the
conceptual data models to logical data models and then to derive a set of relations.

- Admin manage instructor M:M - Admin manage student M:M


- Admin manage faculty M:M-Admin manage department M:M
- Admin manage course M:M - Instructor teach courses M:M
- Instructor add exercises 1:M -Instructor use forum M:M
- Student has faculty M:1 - Student has department M:1
- Student use forum M:M -Student refer e book M:1
E -Learning system for bit

- Student take exercise M:M -Faculty has department 1:M


- Department has course M:M -Course has exercise 1:M

3.7.3 Physical data base design (modeling) Class to table mapping


Course table

Figure 3.26 course table

Department table

Figure 3.27 department table


E -Learning system for bit

Faculty table

Figure 3.28 faculty table

File table

Figure 3.29 file table


E -Learning system for bit

Instructor table

Figure 3.30 instructor table

Student table

Figure 3.31 student table


E -Learning system for bit

Video table

Figure 3.32 video table


E -Learning system for bit

CHAPTER FOUR

4. IMPLEMENTATION
4.1Introduction
Implementation in the system includes implementing the attributes and methods of each
object and integrating all the objects in the system, to function as a single system. The
implementation activity spans the gap between the detailed object design model and a
complete set of source code files that can be compiled together. Testing is checking for
system faults with invalid inputs, and during sub system integration. A test which returns
much number of errors is good testing. This chapter presents Algorithm design, coding &
testing.

4.2Algorithm Design
For controller class member function algorithm are designed. This design enables to see
every steps and flow of logic in each function. This design part is important in the coding
part of implementation. Some of the algorithms are:

Algorithm for Add Department

Select manage department

Click add button

Enter department code

Enter department name

Select faculty

Click submit

If (empty form found) {

Please fill all filled

} Else{

Successfully add

}
E -Learning system for bit

Algorithm for admin login page

Go to admin login page

Enter user name

Enter password

Click submit

If (empty user name & password)

Please enter name & password

} Else

If ($user name $password not found in db.) {

Please enter correct user name & password

} Else {

Go to admin page

Algorithm for instructor upload file

Display instructor home page

Click file Manu

Display file upload page

Fill necessary information

If the field input file invalid

Display error message

Else

Upload file successfully

End if
E -Learning system for bit

Algorithm for instructor uploads video

Display instructor home page

Click file Manu

Display file upload page

Click add video Manu

Display video upload page

Fill necessary information

If the field input video invalid

Display error message

Else

Upload video successfully

End if

Algorithm for student view assignments

Select assignment page

Selects course

If (assignment not upload) {

No assignment found

} Else {

View assignment

Algorithm for student takes exercise

Display student page

Click exercise Manu

Display course

Select course

Display select exercise page


E -Learning system for bit

If found exercise

Display exercises

Else

Display error message

End if

Select exercise

If no question for exercise

Display error message

Else

Display question

While question number less than or equal to total question number -1

Click next question

If no select answer

Display error

Else

Question number +1

End if

End while

If question number =total question number

Click result

If no selected answer

Display error message

Else

Display result page

End if

End if
E -Learning system for bit

4.3Coding

//add file code

<?php include('session.php');

include ('connect.php');

error_reporting(1); ?>

<?php

$out="";

$out1="";

if(isset($_POST['submit'])) {

$title = $_POST['title'];

$course = $_POST['course'];

$des = $_POST['des'];

$image = $_FILES['pdf']['tmp_name'];

$image_name = $_FILES['pdf']['name'];

$type = explode('.', $image_name);

$type = end($type);

$image_size = $_FILES['pdf']['size'];

if($course=='select course'){

$out = "<div class='alert alert-danger'>please select course</div>";

}else {

if ($type != 'PDF' && $type != 'pdf' && $type != 'docx' && $type != 'pptx' && $type !=
'ppsx') {

move_uploaded_file($image, "uploads/document/" . $image_name);

$location1 = $_FILES["pdf"]["name"];

if ($location == '') {

$out = "<div class='alert alert-danger'>please select file </div>";

} else {

$location = "uploads/document/" . $_FILES["pdf"]["name"];


E -Learning system for bit

$sql = "INSERT INTO bitelearning.file(title,course,file,description)


VALUE('$title','$course','$location','$des');";

$res = mysql_query($sql);

if ($res) {

$out = "<div class='alert alert-success'>successfully register as :</div>";

} else {

$out = "<div class='alert alert-danger'>failed to register </div>";

} else {

$out = "<div class='alert alert-danger'>select unsupported file </div>";

if(isset($_FILES['video'])) {

$name = $_FILES['video']['name'];

$image_size = ($_FILES['video']['size']/1024);

$type = explode('.',$name);

$type = end($type);

$size = $_FILES['video']['name'];

$random_name=rand();

$tmp=$_FILES['video']['tmp_name'];

$title = $_POST['title'];

$course = $_POST['course'];

$des = $_POST['des'];

if($course=='select course'){

$out1 = "<div class='alert alert-danger'>please select course</div>";

}else {

if ($type != 'mp4' && $type != 'MP4' && $type != 'flv' && $type != 'swf' && $type != 'flv') {
E -Learning system for bit

$out1 = '<div class="alert alert-danger">file type not correct</div>';

} else {

$up = 'uploads/' . $random_name . '.' . $type;

$nn = move_uploaded_file($tmp, $up);

if ($nn) {

mysql_query("INSERT INTO bitelearning.video(title,course,video,description)


VALUE('$title', '$course', '$random_name.$type', '$des')");

$out1 = '<div class="alert alert-success">successfully uploaded</div>';

} else {

?>

CHAPTER FIVE

5 SYSTEM TESTING
5.1Introduction
System testing is simply testing the BiT eLearning system as a whole; it gets all the
integrated modules of the various components from the integration-testing phase and
combines all the different parts into a system, which is then tested. Testing is then done
E -Learning system for bit

on the system as all the parts are now integrated into one system and the testing phase
will now have to be done on the system to check and remove any errors or bugs occurred
in integration of the modules.

In the system, testing phase the whole BiT eLearning system will be checked not only to
find errors but also to see if the system does what was intended at the user requirement
phase, the system functionality and if it is, what the end user expected it to be.

5.2Objective
This phase determine the error that is the non-functional component in the BiT eLearning
system. If there is an error or non-functional component then it must be removed or get
fixed before delivery of the project. For determining errors various types of test action
are performed.

The major objectives of System testing are as follows:

 Finding defects, which may be created by the programmer while developing the
software.
 Gaining confidence in and providing information about the level of quality.
 To prevent defects.
 To make sure that the end result meets the business and user requirements.
 To ensure that it satisfies the BRS that is Business Requirement Specification and
SRS that is System Requirement Specifications.
 To gain the confidence of the users by providing them a quality service.
System testing helps in finalizing the System or product against business and user
requirements. It is very important to have good test coverage in order to test the System
completely and make it sure that it is performing well and as per the specifications.

5.3Testing by Scope

5.3.1 Unit testing


Each unit in are tested separately before integrating them into modules to test the
interfaces between modules. While implementing the code In PHP programing language
all small components such as directory creation, conditional statements, loops and others
E -Learning system for bit

were tested. For example, while an instructor upload file in to the system. if the file type
is incorrect the system will indicate that there an error uploading file then it recommends
the instructor to check the file again, this assure that the PHP lines of codes that are
designed to verify the file type is working perfectly.

5.3.2 Integration testing


Integration testing identifies problems that occur when units are combined. Class-
Integration Testing has been made based on the relationships and the respective
cardinalities that appear on the class diagram. After unit testing, our system is also tested
whether every unit is integrated to every other unit.

5.3.3 System testing


The system is functionally tested based on the use case model developed during the BiT
eLearning system analysis phase, because they describe the exact behavior of how the
users work with the application. The entire system is tested and approved, since it
addresses all the user requirements such as accepts the data, process the data, stores the
data, notify data entry errors and retrieve stored data. By doing so, the system is working
in line with the user’s requirements.

5.4Resource

There are some resources used during testing BiT eLearning system there are software
and hardware resources.
Hardware resources
- Computer

Software resource

- XAMP server

5.5Schedule

Type of testing Date of testing Tested by

Unit testing Starting from June 01, 2017 All group members

Integration testing Starting from June 5, 2017 All group members


E -Learning system for bit

System testing Starting from June 9, 2017 All group members


Table 5.28Tasting schedule table

5.6Feature to be tested or not to be tested

5.6.1 Feature to be tested


The feature to be tested is the integration of the system is tested this means the
combination of one program to another program is tested this is because of one module
can have an adverse effect on another sub-function when combined. In addition, the unit
testing such as interface, error handling is tested.

5.6.2 Feature not to be tested


Features not be tested includes the feature of the application which cannot be measured
directly or indirectly. These features cannot make serious damage to system but indirectly
have an influence on our application performance and acceptance. These features
includes-

 User satisfaction of the system

 Exact response time of the system

5.7Pass/fail criteria
 completion of the function of the system

 performance criteria

5.7.1 Pass/Fail criteria


Pass fail criteria will be created by each project team based on scenarios and test cases.
E -Learning system for bit

Criteria Pass Fail


Student registration Pass

Instructor registration Pass

Admin registration Pass

Login Pass

uploading files Pass

Account Activation Pass

Add courses Pass

Add Department Pass

Add Faculty Pass

Table 5.29 pass and fail criteria table

5.8Approach

5.8.1 Black box testing:


It is also called behavioral testing or Partition testing. This kind of testing focuses on the
functional requirements that are described in chapter 2 of the BiT eLearning system. It
enables one to derive sets of input conditions that will fully exercise all functional
requirements for a program. In the BiT eLearning system if a proposal evaluator inputs the
status of a proposal to be pass that proposal will be automatically become a project.

5.8.2 GUI Testing:


GUI testing will includes testing the user interface of The BiT eLearning system. It covers
making easy to navigate and for use, look and feel, error messages, and GUI guideline
violations. In the BiT eLearning system all the user interface are constant and uniform and
also change the size of the UI component as the size of the display increase or decrease.

5.9Test case specification


Test case: Activate instructor account: admin is responsible
Purpose: Enabling lecturers to access the system
1. First, the admin should be successfully logged in to the system using provided
username and password.
E -Learning system for bit

2. Then the admin will see activation request and approve it


3. Finally, instructor will get username and password and can login to the system.

Expected result

Test successful: account will be activate for instructor.

Test failure: account activation will be rejected

Test case: add courses

Purpose: making different courses available for students and instructors

1. First, the admin should be successfully logged in to the system using provided
username and password.
2. Click add course and fill necessary information and the course will be added to the
system

3. Instructor and students can access the course using his/her account.

Expected result

Test successful: course is added

Test failure: course will not be added

Test case: add file and video


Purpose: making different file and video available for students uploaded by instructors

First instructor will login to the system


1. After successful login he/she will fill information and select files upload to the
system
2. Instructor uploaded the files

3. Students can access files using his/her account

Expected result

Test successful: the file uploaded successfully

Test failure: the file will not uploaded

Test case: adding exercise titles

Purpose: making different exercises available for students uploaded by instructors

1. Instructor successful login to the system.


E -Learning system for bit

2. He/she will fill necessary information to add a new exercise titles.


3. Exercise will be available for students.

Expected result

Test successful: exercise will be added.

Test failure: exercises will not be added to the system.

Estimated risk and contingency plan

Estimated Risk Contingency plan

1.The BiT eLearning system fails at The department should use the existing
some point manual system until the system failure is
fixed.

2.If login failure The student should come up to receive their


new account detail

Table 5.30Estimated risk and contingency plan

CHAPTER SIX

6 RESULT, CONCLUSION AND RECOMMENDATION


6.1Result
The result is here to show how the inserted data in the system is stored in to the database
system

 there will be fields to fill the necessary information to the system and after the data
is added the data will show in the data base system as shown below:-
E -Learning system for bit

Instructor upload video in the system

Figure 6.33 uploading video in the system


Uploaded video in database

Figure 6.34 uploaded video in the database

6.2Conclusion
As we come to end of our system development, it is time to reiterate the work previously
have been done and check against our success indicators set at the beginning of the project
to determine whether the endeavor was a success. The system developed in this project
BiT E-learning system. The BiT e-learning system facilitates registration of new
instructor, students, and update and delete their information &it provide easy and fast form
and annual leave requisition and approval method.

The project began by laying out the foundation that dictates the development process. This
involved defining the system development methodology, identifying resource
E -Learning system for bit

requirements, and setting the project schedule. We performed requirements analysis to


discover the needs of the new solution to proposed system. This phase consists of drawing
out functional and non-function requirements of the system. Then we performed object-
oriented analysis and object oriented design. In analysis, we tried to model the new and
proposed system using UML diagrams: use case diagrams, sequence diagrams, Class
diagrams, Activity diagrams.

Our development team believes that we have at large accomplished what we set out for in
the beginning of this project. We set to develop a working system prototype that would
solve the problems in the beginning of our project. The problems, which existed in the
earlier system, have been removed largely. Moreover, it is expected that this project will
go a long way in satisfying user’s requirements.

6.3 Recommendation
Now a day technology is having a major impact on growing use of computer. Among those
technologies, E-learning is one of them.E learning is the use of Internet technologies as well
the pedagogical approach of advancing the scalability of knowledge and performance. Due to
the fastest growth of Information and Communication Technology, the impact of E-learning
for the contribution of quality education become vital, leading to a great paradigm shift for
higher educational institution in general and Bahir Dar university Institute of Technology in
particular.

In general, this project contributes an initial work on E-learning system for


BiT. This work is not an end, and that needs to be matured in other similar projects
in the future to scale up it to more sophisticated technologies and techniques. From
different the various fact that constituents the project, the following recommendations are
suggested.

 Bahir Dar University will take these opportunities to entertain such an alternative
E-learning system.
 Serious attention should be given for the introduction of the new system.
 Also it is recommended that a university should develop such system from
this initiation
E -Learning system for bit

Reference

1. Chrysostomos Chrysostomou and George Papadopoulos, “Towards an


Object-Oriented Model for the Design and Development of Learning
Objects”, International Jl. on E-Learning (2008) 7(2), 219-243

2. Eduworks, “Learning Object Tutorial”, 2010.

3. “Bahirdar university” WikiVisually Wikimedia Foundation, Inc.8 Mar. 2013. Web.


30 Mar. 2013.

4. “Using PHP from the command line” PHP My PHP.net 3 Sep. 2012. Web. 30 Jan.
2012

5. “Customize Bootstrap's components,” bootstrap http://getbootstrap.com/5 Dec. 2015.

You might also like