New Printed

MTU E-Learning System 2017/18
MIZAN TEPI UNIVERSITY

SCHOOL OF COMPUTING AND INFORMATICS
DEPARTMENT OF INFORMATION TECHNOLOGY
Project Title: - MTU E-learning system
Group members
Name Id _NO
1. SHUMI GENEMO SCIR/290/07
2. MISANESH ASSEFA SCIR/227/07
3. SENIYA NEGASH SCIR/284/07
4. BIRKE WUBSHET SCIR/080/07
5. ABYE ABABEW SCIR/019/07
Advisor Name Mr.Habtewoled D
Co-Advisor Name Mr. Abraham D
A senior project
Submitted to Department of Information Technology, School of Computing and Informatics,
Mizan Tepi University, in Partial fulfillment for the requirement of the Degree of Bachelor
Science in Information Technology
Tepi, Ethiopia
June, 2018
School of Computing and Informatics Dep’t of IT Final project Page

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 have been duly acknowledged.
Name Signature
1. Shumi Genemo
2. Misanesh Assefa
3. Seniya Negash
4. Birke Wubshet
5. Abye Abebaw
Schoool: School of computing and informatices
Department : Information technology
Project title: MTU E-learning system

I certify that this project satisfies all the requirements as a project for the degree of Bachelor of
Science.
------------------------------------- -------------------------------------
Name of Department Head Signature
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 thesis for the degree of Bachelor of Science in information technology
------------------------------------- ---------------------------------------
Name of Advisor Signature
Examining committee members Signature Date

1.
2.
3.
It is approved that this project has been written in compliance with the formatting rules laid
down by the Advisor.
School of Computing and Informatics Dep’t of IT Final project Page i

ACKNWOLEDGEMENT
First of all, we would like to praise our God who helps us to accomplish this project
documentation successfully. Our Next deepest gratitude will go to Mr.Habtewoled D. and Mr.
Abraham D. is our advisor. They gave us a chance to acquire more detailed knowledge about the
project and he helps us in any confusion that was happening during the documentation
development. This makes us more knowledgeable about the project named E-Learning System.
Thank you! Teacher
School of Computing and Informatics Dep’t of IT Final project Page ii

ABSTRACT
This document basically deals about automating of MTU Learning System. This document
contains five necessary chapters. In the first chapter it include introduction, existing system,
problem of the existing system, proposed system, objective, methodology, scope, and time
schedule as well as risk assumption of the project .The second chapter deals with about the
system future, work flow of the existing system it includes the function and non function
requirements. The third chapter deals about the use case diagram with its description, activity
diagram and sequence diagram for analyzing the requirements. The fourth chapter deals about
the design of the system; it contains the deploy diagram, class diagram. The last chapter deals
about conclusion. Generally this document was done to solve the problem of the MTU Learning
System, from manual system to E-Learning System or computerized (automated) system.
School of Computing and Informatics Dep’t of IT Final project Page iii

ACRONYM
E-learning Electronic Learning

MTU Mizan Tepi university
PHP Hypertext Preprocessor
RAM Rand access memory
UC and CSS Use Case and Cascading Style Sheet
ICT Information communication technology
Pc Personal computer
BR Business rule
UML Unified modeling language
HOD Head of department
School of Computing and Informatics Dep’t of IT Final project Page iv

1 Contents
CHAPTER ONE ....................................................................................................................................... 1
INTRODUCTION .................................................................................................................................... 1
1.1 Introduction ................................................................................................................................... 1
1.2. Background of the Study.................................................................................................................... 1
1.3. Statement of the Problem ................................................................................................................... 2
1.4. Objectives of the Project .................................................................................................................... 2
1.4.1. General Objectives ...................................................................................................................... 2
1.4.2. Specific Objectives ..................................................................................................................... 2
1.5. Scope and Limitation of the Project ................................................................................................... 3
1.5.1. Scope of the Project .................................................................................................................... 3
1.5.2. Limitation of project ................................................................................................................... 3
1.6. Risk assessment and Management ..................................................................................................... 3
1.7. Significance of the Project ................................................................................................................. 4
1.8. Methodology of the project development .......................................................................................... 4
1.8.1. Data collection method ................................................................................................................... 5
1.8.2. Interview ..................................................................................................................................... 5
1.8.3 Observation .................................................................................................................................. 5
1.9 System Development Tools ................................................................................................................ 5
1.9.1 Hardware Tools ............................................................................................................................ 5
1.9.2 Software Tools ............................................................................................................................. 6
1.10. Feasibility study ............................................................................................................................... 6
1.10.1 Technical Feasibility .................................................................................................................. 7
1.10.2 Operational Feasibility ............................................................................................................... 7
1.10.3 Economic Feasibility.................................................................................................................. 7
1.10.4Budget Schedule ......................................................................................................................... 8
1.10.5 Schedule Feasibility ................................................................................................................... 8
1.11. Schedule of the project ......................................................................................9
CHAPTER TWO .....................................................................................................10
2 Requirement Elicitation and Analysis ...............................................................10
2.1 Introduction ................................................................................................................................. 10
2.2 Description about the Existing System ....................................................................................... 10
2.3 Overview of the Proposed System .............................................................................................. 10

School of Computing and Informatics Dep’t of IT Final project Page v
2.4 Business Rule .............................................................................................................................. 11
2.5 Requirement Specification .......................................................................................................... 11
2.5.1 Functional Requirements .................................................................................................... 11
2.5.2 Non-Functional Requirements ............................................................................................ 12
2.6 System Requirement ................................................................................................................... 12
2.7 Hardware Requirements.............................................................................................................. 12
2.8 Software Requirements ............................................................................................................... 13
CHAPTER THREE..................................................................................................14
3 System Analysis Model .....................................................................................14
3.1 Introduction ................................................................................................................................. 14
3.2 System Requirement Specification (SRS) .................................................................................. 14
3.3 Actor identification ..................................................................................................................... 14
3.4 Use-case Identification................................................................................................................ 15
3.5 Use Case Diagram....................................................................................................................... 16
3.6 Sequence Diagram ...................................................................................................................... 26
3.9 Activity diagrams .............................................................................................................................. 31
3.7 Class diagram .............................................................................................................................. 39
CHAPTER FOUR ....................................................................................................41
4 System Design ...................................................................................................41
4.1 Introduction ................................................................................................................................. 41
4.2 Class Type Architecture (System Architecture) .......................................................................... 41
4.3 Deployment Modeling ................................................................................................................ 43
4.4 User Interface Design.................................................................................................................. 45
4.5. Boundary condition .......................................................................................................................... 47
4.5.1 Internal flow of the system............................................................................................................. 48
4.6. System Testing ................................................................................................................................. 52
4.6.1. Security testing.......................................................................................................................... 52
4.6.2. Unit testing ................................................................................................................................ 53
4.6.3 Integration testing ...................................................................................................................... 53
4.6.4. Validation testing ...................................................................................................................... 54
CHAPTER FIVE......................................................................................................55
5. IMPELMENTATION AND TESTING ..............................................................55

5.1 Introduction ....................................................................................................................................... 55
School of Computing and Informatics Dep’t of IT Final project Page vi
5.2. Implementation ................................................................................................................................ 55
5.3. Final testing of the system ............................................................................................................... 55
5.4 Hardware software acquisition.......................................................................................................... 58
5.5 User manual preparation ................................................................................................................... 58
5.6 Training ............................................................................................................................................. 58
5.7 Sample code for create account ........................................................................................................ 58
5.8 Sample code for view account .......................................................................................................... 62
5.9 Sample code for view Course result ................................................................................................. 64
CHAPTER SIX ........................................................................................................67
6. CONCLUSIONS AND RECOMMENDATION ................................................67
6.1 Conclusion ........................................................................................................................................ 67
6.2 Recommendation .............................................................................................................................. 68
Reference ................................................................................................................................................ 69
School of Computing and Informatics Dep’t of IT Final project Page

vii
List of Tables
Table 1Hardware tools .................................................................................................................... 5
Table 2 Software tool ...................................................................................................................... 6
Table 3 Budget Schedule ................................................................................................................ 8
Table 4 Time Schedule ................................................................................................................... 9
Table 5Use Cases of the system. ................................................................................................... 15
Table 6Descriptions and Identification of use cases. .................................................................... 16
Table 7 Use case description for login .......................................................................................... 18
Table 8Use case description for manage user account ................................................................. 19
Table 9Use case description for Post forum ................................................................................. 20
Table 10Use case description for download material resource..................................................... 20
Table 11 Use case description for upload material resource ....................................................... 21
Table 12Use case Description for post grade................................................................................ 22
Table 13Use case description view feedback ............................................................................... 22
Table 16Use case description Participate forum ......................................................................... 23
Table 17Use case description view class schedule ....................................................................... 23
Table 18Use case description Send feedback ............................................................................... 24
Table 19Use Case Description of Assign Instructor ..................................................................... 25
Table 20Use Case Description Set schedule ................................................................................. 25
Table 21 Unit testing ..................................................................................................................... 53
Table 22 Integration testing .......................................................................................................... 54
Table 23 Validation testing ........................................................................................................... 54
Table 24 Unit testing .................................................................................................................... 56
Table 25 Integration testing .......................................................................................................... 57
Table 26 Validation testing ........................................................................................................... 58
School of Computing and Informatics Dep’t of IT Final project Page vii

List of Figures
Figure 1.System development methodology................................................................................... 4
Figure 2Descriptions and Identification of use cases. .................................................................. 17
Figure 3Sequence diagram for Login ........................................................................................... 26
Figure 4Sequence diagram for Upload Course Material .............................................................. 27
Figure 5Sequence diagram for Download Material ...................................................................... 28
Figure 6Sequence diagram for view feedback .............................................................................. 29
Figure 7Sequence diagram for send feedback .............................................................................. 30
Figure 8Sequence diagram for post forum .................................................................................... 31
Figure 9Activity diagrams for Login ............................................................................................ 32
Figure 10Activity diagrams for download course material .......................................................... 33
Figure 11Activity diagrams for View feedback ............................................................................ 34
Figure 12Activity diagrams for Manage Account ........................................................................ 35
Figure 13Activity diagrams for upload material ........................................................................... 36
Figure 15Activity diagrams for send feedback ............................................................................. 37
Figure 16Activity diagrams for post forum .................................................................................. 38
Figure 17 Class diagram of the systems ...................................................................................... 40
Figure 18Class Type Architecture of the system .......................................................................... 42
Figure 19Deployment modeling of the system ............................................................................. 44
Figure 20User Interface Design .................................................................................................... 46
Figure 21 Home page interface .................................................................................................... 47
Figure 22 Login page interface ..................................................................................................... 48
Figure 23 Create account page interface ....................................................................................... 49
Figure 24 Post Course of result ..................................................................................................... 50
Figure 25 Upload assignment Qes ................................................................................................ 51
Figure 26 Assign Instructor .......................................................................................................... 52
School of Computing and Informatics Dep’t of IT Final project Page viii

CHAPTER ONE
INTRODUCTION
1.1 Introduction
The growth of Information and Communication Technology has significant effects on all people
around the world. With this growth, people are able to connect with each other, especially
through the Internet. The approach of E-Learning and teaching support system has become a
powerful way to deliver knowledge considering the increase in online users. E-learning systems
are considered an essential application in educational institutions today.
The learning process needs techniques and tools to present the knowledge (from different
resources) interact with it and share it with others. In this context, E-Learning is becoming an
important tool to support and achieve the teaching and learning process. Its aim is to create an
augmented learning environment where technology is used to deliver a combined range of
teaching techniques aimed at maximizing the individual's participation in the learning process.
Generally, the internet is new media, it has been spread in a recent time, furthermore, the E-
Learning is very recent tool, and so this sector needs more and more researches. E-learning, like
many terms in Internet, does not have current definition which can be accepted by all.
1.2. Background of the Study

Education can be formal or informal. Formal education is the one with hierarchically structured,
chronologically graded education system, running from Kindergarten up to university. The
informal education is truly an endless process whereby every one gains attitude, values, skills
and knowledge from daily experience in the environment. The formal education is a rapid and an
organized one, when compared with that of the informal education.
E-Learning: - is the delivery of a learning, training or education program by electronic means’-
learning involves the use of a computer or electronic device in some way to provide training,
education or learning material.
E-learning is the computer and network-enabled transfer of skills and knowledge. E-learning
applications and processes include Web-based learning, computer-based learning, virtual
School of Computing and Informatics Dep’t of IT Final project Page 1

education opportunities and digital collaboration. Content is delivered via the Internet, since our
project is done for Mizan Tepi University the current system MTU a lot of many problems and
the new proposed system will be able to solve problem on the current system.
1.3. Statement of the Problem

At present MTU has no E-learning system that is available for all courses and introduces
students with the technology .The campus course coordinators distributed modules to instructors,
and instructors provide these modules to students based on their department type. It is
compulsory to prepare such modules year by year to continue teaching-learning process on the
MTU. In order to prepare such modules tones of papers, high human power and other module
preparation equipment is also needed. This module distribution system leads the MTU teacher’s
educational and vocational training MTU to great crisis of economy. The students also waste
time, money and effort in always going back to their instructor to submit assignments and to
view the result of course including quizzes, tests and assignments. Also most of the MTU
students have no computer skill that is expected from the MTU students. Overburden of work on
the employee of the college is also another problem during preparing, duplicating and
distributing modules. Therefore, we will need to improve existing system by eliminating the
above problems to increase satisfaction of teaching-learning system.
1.4. Objectives of the Project
1.4.1. General Objectives

The general objective of this project is to develop E-learning System for Mizan Tepi University.
1.4.2. Specific Objectives

 To understand the existing system
 To gather information related to the system.
 To Analysis the gathering information required for proposed system.
 To planning information related to the system.
 To Design and developing the proposed system
 To Implementing the system
 To Test and provide maintenance and support

1.5. Scope and Limitation of the Project
1.5.1. Scope of the Project

The project has a great scope to address the student and teacher problem as well as the teaching
and learning process easier and efficient. It is well known that in Mizan-Tepi University students
as well as teacher are facing internet problems. Using the current MTU ICT infrastructure we can
host the project locally and we can give the service all the time with internet connection is
available. The system provides to assign instructor, post grade, post forum, send feedback, view
feedback, and participate forum. And also manage account such as update, delete, create and
view feedback. It provides course materials online that students can access anywhere inside
campus and it provides asset schedule, view class schedule.
1.5.2. Limitation of project

 The project will be simulated on local machine.
 It is Limited for MTU Students only.
 The project will not doing online examination.
 The project will not doing online registration.
 The project will not doing online video conference.
1.6. Risk assessment and Management

When we will develop this system we also think about some risks. Some of these are:-
 The team member was not present because of different problems

 Scarcity of resources or required materials
We have also the alternative solutions for the above risks. These are:-
 All team members cover the tasks

 We have a backup on different computers
 Use the available resources in efficient manner

1.7. Significance of the Project
After completion of this project, the system will provide the following significant functionality’s
for MTU.
 Allowing students to receive and submit their assignment with short period of time.
 Reduce wastage of the University and students resource.
 Minimize work overload of the Teachers as well as students.
 To easily access of uploaded resource
 The students can download learning materials (module) and assignments
 Providing full access of course material for students.
 Enabling students to use today’s ICT technology.
1.8. Methodology of the project development

In any software development project, a systematic methodology, or process, should be followed
through the life cycle of the project to ensure consistency and completeness.
For this project, we use the System development life cycle.
The systems development life cycle (SDLC) is a conceptual model used in this project for
management that shows the stages involved in development of this web based system from an
initial problem identifying until maintenance of the completed application.
For this project, we use the System development life cycle. The life cycle includes the following
phases: planning, analysis, design and development, implementation, testing and maintenance.
Figure 1.System development methodology

1.8.1. Data collection method
The data collection process to conduct this project includes both the qualitative and quantitative
data. This will be done through the use of instruments such as observations, interviewing and the
Internet. From these three data gathering tools, interview will be used to collect data from the
office of the registrar and from the instructors. Observation will also be used to oversee the
required things in the college.
1.8.2. Interview
Interview is a conversation or questioning, for the purpose of eliciting information for
publication, the available statement so elicited. To get the basic information and background
information about the existing system, some team members has interviewed the Teacher and
some students about the services that are given to them, and the problems associated with that
environment.
1.8.3 Observation
Observation is the other instrument that will use to collect data which will be necessary for our
web-based system project for the college. In this process we will try to investigate the
information by making our selves participates in the process. And observations will also helping
us to relate the information obtained from the interviewee by looking to the reality of the college.
1.9 System Development Tools

For the new system to be efficient there are a tools for specific hardware and software. [6]
1.9.1 Hardware Tools

No. Hardware tool name Description
1 Memory Store data permanently

2 Hard disk To keep the permanent data
3 Flash disk transfer data from one PC to
Another PC.
4 Printer To have a hard copy for the data.
5 Laptop/Desktop To work our project easily.
Table 1Hardware tools

1.9.2 Software Tools
The client PC running the system may use any of the following software.
No. Software Description
tool
1 Browsers Like : Internet Explorer , Mozilla Firefox , Google

chrome
2 Operating system MS-window 2012 for the system.
3 MySQL To implement the database.
4 MS Word we use to edit documentation
5 PhpMyAdmin We choose PHP scripting language which aims at

providing the user with an interface that is easy to
learn and attractive.
6 Notepad++ to edit the PHP code
Table 2 Software tool
1.10. Feasibility study

The feasibility study is applied to test whether the proposed system is worth being implemented.
Feasibility study is a test of proposed system regarding its work ability To start our project first
we should have to clearly notify the feasibility of the system that we are going to implement,
because without fulfilling feasibility factors (the economical, technical, operational and schedule
feasibility) our proposed system cannot be said a good web page. So in all angles the new system
should have to be feasible. The proposed system can be seen according to the following literals.
The feasibility factors of our project are:
 Economic feasibility

 Technical feasibility
 Operational feasibility
 Schedule feasibility
1.10.1 Technical Feasibility

Technological feasibility measures the practicality of a specific technical solution to the problem.
It is also a measure of the availability of technical resources and expertise. Technical feasibility
is assessing the organization‘s ability to construct the system. Since This online system for
educational purpose need technical resources to implement, like computer with network, Php,
MySQL server. We expect that, the system can be operated in simple way and all users can
access easily by giving some training for them.
1.10.2 Operational Feasibility

The system to be developed will provide accurate, active, secured service and decreases labor of
workers (reduce effort). And also it is platform independent i.e. it run’s in all operating system.
So our project operational feasible
1.10.3 Economic Feasibility

It is possible to develop the proposed system in minimum cost and also can be hosted in lower
price. Our project is economical feasible.
Generally the system that we will develop brought a number of tangible and intangible benefits.
Tangible benefits: are benefits derived from the creation of an information system.
 Give to 24 hour service

 Reduce resource requirements or unnecessary wastage of resource paper, pen
Intangible benefits: are benefits derived the creation of an information system that cannot be
easily measured in birr and consistency. The intangible benefits of the new system are
 Knowledge gain by project developer.
 Increase Employee Moral
 Increase efficiency.
 Increase communication speed.
 Give better and effective service.

1.10.4 Budget Schedule
For the purpose project we required to budget for different resources as Shown below: -
NO. Material Amount Price(ETB) Total

1. Paper 1 pack 90birr 90birr
2. Pane 5 5birr 25birr

3. Removable Disk 1 200birr 200birr
4. Pencil and Eraser 3 1birr 3birr
5. Laptop 1 12,000 12,000 birr
6. Print 60 or above 2 120 birr
7. Other - - 300 birr
Total 12738
Table 3 Budget Schedule
1.10.5 Schedule Feasibility

Schedule Feasibility is defined as the probability of a project to be completed within its
scheduled time limits, by a planned due date. This project is expected to be completed in two
semesters of 2010 academic year. Some parts of the project component to be completed in the
first semester are up to design and the rest of activities such as implementation, testing and other
would complete in the next semester. Generally the time that take to accomplish this system is
summarized by figure as follows:

1.11. Schedule of the project
2010 EC
ID Task name Dec 0 6,2010 - Dec 11,2010 - Jan Jan 12,2010 - March 1,2010-
May 18,2010
-
Dec 10,2010 11,2010 Feb 30,2010 May 17,2010
june 05,2010
1 proposal Proposal
2
Analysis and Analysis and
gather gather
3 Design Design
4
Implementati Implementati
on on
5 Testing Testing
Table 4 Time Schedule

CHAPTER TWO
2 Requirement Elicitation and Analysis

2.1 Introduction
This chapter generally deals about the issues related with current teaching and learning process
of MTU and the way we are going to solve as well. Further, Description about the existing
system, business rules, constraints and actors of the system will be discussed
2.2 Description about the Existing System

The existing system performs all tasks manually. Student register offline, in other word they register
using slip in each semester. Instructors use paper to control student assessment, exam and announcement.
Registrar post student grade and other urgent notice using announcement board, Instructor gives
handout for students. In other word, Overload of work on the University’s employee is also seen
on the current system of the organization during duplicating and distributing modules, since each
course has its own module to be distributed per student. Students also submit their assignment to
their instructor in hard copy, and they view result of the course such as quizzes, tests and
assignments by going back to their instructor. Such process leads students to waste their time,
effort, money and make them unsatisfied. Generally, those problems can be defined as:
 Wastage of University’s resource

 Time consuming because of it is manually operated
 Lack of consistency of data
 Work overload on University’s employee
2.3 Overview of the Proposed System

The proposed system that we analyze can solve some portion of the existing system. When we
see the solution, making the college computerized system, it will solve most of the problems in
the teaching-learning process. This project has much significance
 Reduce the extravagancy of the MTU resource.

 Reduce the time and task required to perform the operation within the college.
 It will provide speed, efficient, Flexibility and reliability system.

 For students, better satisfaction of the speed provided by the instructor in course material
distributing, seeing course result and submitting assignment.
 To easily manage and perform any task performed by MTU
2.4 Business Rule

This part specifies and gives understanding of activities which are being done in the existing
system in terms of business rule.
BR1: New entry students must have educational document.
BR2: If student is above first year first semester he/she must score promotion grade for
registration
BR3: The registrar Determines registration date and clarify required criteria.
BR4: Student should be registered on the specified registration date.
BR5: Each student should have unique identification card to be identified.
BR6: Choice for field of study is based on the student’s interest.
BR 7: Anyone who use the system should be MTU student
BR 8: Registrar has to post student grade to be registered
2.5 Requirement Specification

This requirement specification is defined as what things are performed by the system that we
developing the system. It consists two things these are: -
 Functional requirement of the system

 Non-functional requirement of the system
2.5.1 Functional Requirements

A functional requirement specifies what the system should do to perform some task. The system
consists of the following the functional requirements:
 Uploading course Material: Enables the instructors and student to login to the system
and upload Course materials.

 Downloading Course Material: Enables the students and Instructor to access course
material.
 Student view grade: the student can be view their own grade.
 Manage accounts: Enables Administrator to create, update and delete accounts.
 Participate forum: it enables the student can be participate forum
 Assign instructor: the HOD can assign instructor to the student course.
 Post grade: the instructor computive student grade.
 View class schedule: the student can be view class schedule posted by instructor.
 Set schedule: the HOD can be prepare the time learning and teaching process
 View feedback: the admin can be view the feedback sent by student
 Send feedback: it enables the student may be send comment(feedback) to the admin
2.5.2 Non-Functional Requirements

Those requirements which are not the functionalities of a system but are the characteristics of a
system are called the non-functionalities. Non-functional requirement includes; system
performance, availability, usability, Portability and Reliability.
 Usability: -The system is easy to learn and operate. The User interface for this system ]
 will be simple and clear. The E-Learning services are easy to gain and use i.e. the service
doesn’t require special training.
 Availability: -This system is available in everywhere (where internet service reach) and
at all time for those who have access to use the system.
 Performance: - The system will have good performance i.e. fast response time and
optimal workload.
 Reliability: - The system is effective and consistent in that integrity of information is
maintained and supplied to the system.
 Portability:-The system is machine independent and software system independent so it
can be moved to different target platforms.
2.6 System Requirement
2.7 Hardware Requirements

According to [6] we can put our hardware requirements as follow.

 Memory: Recommendation: 4GB RAM
 Hard disk: To keep the data and to take backup use 500GB
 Flash Disk: Minimum of 4GB to store and it used transfer data from one PC to another
PC.
 Printer: To have a hard copy for the data.
2.8 Software Requirements

The client PC may use one of the following browsers:
 Internet Explorer,
 Mozilla Firefox
 Google chrome
 Baidu
 Opera
But the system needs to fulfill the following software:
 Operating system: MS-window 2012 server will be used for the system.
 Database management software (DBMS): is the mandatory one for the new
system. To implement the database easily, use MySQL.
 PhpMyAdmin: choose PHP scripting language which aims at providing the user
with an interface that is easy to learn and attractive.
 Notepad++: to edit the PHP, CSS, and Jscript codes.
 Microsoft office word and power point: Used to prepare project proposal
presentation and document.
 Microsoft office Visio 2007 and Edraw max: for UML drawing diagrams.

CHAPTER THREE
3 System Analysis Model

3.1 Introduction
The purpose of design is to determine how the system is going to be built and to obtain
information needed to drive the actual implementation of the system. It focuses on understanding
the model how the software will be built. This chapter mainly focuses on the design part of MTU
E-learning system. In order to make the implementation of the system the design is very
important.
3.2 System Requirement Specification (SRS)
3.3 Actor identification

The following actors that are interact with the system.
Actor: Student
Description: is a person who downloads and upload materials for instructor, view grade, view
class schedule, participate forum, send feedback to admin.
Actor: Instructor
Description: teaches or instructed the student by uploading and downloading course material,
create course assessment and computive grade.
Actor: Administrator
Description: a person who organizes the teaching learning process, and also person who
manage user account.
Actor: HOD
Description: A person who assign instructor and set schedule for learning process.

3.4 Use-case Identification
Identifying the activities that are mainly performed on the proposed system is the basic thing in
analyzing a new system. The following use cases have been identified from the system
specification. The use cases of the system are list below:
 Login  Post forum

 Manage account  View grade
 Change user password  response forum
 Upload Course material  Assign Instructor
 Download Course materials  post grade
 Set schedule  Logout
 View feed back  Send feedback
 View class schedule
Table 5Use Cases of the system.
Use case Use case Description

identifier
Login UC#1 This use case allows the User to login to the
system
Manage user account UC#2 Used to administrator manages users’ account
Post forum UC#3 Allows the admin activate the system and access
the home pages that address the course material
resource to the student
Download UC#4 This process can be performed by an instructor

and student can download material resource
Upload UC#5 This process can be performed by an instructor

and student can upload material resource
View feedback UC#6 It used to correct the learning teaching process

base on their feedback

change password UC#7 Allow the user can change the password that can
be used.
Assign instructor UC#8 Used to assign instructor to the course of student
View grade UC#9 Student can be view grade result upload by

instructor
post grade UC#10 The instructor can calculate the student grade
including test, quiz, assignment, final exam
Participate forum UC#11 The user can be view the forum if it is available
to the user the it can be participate this forum.
View class schedule UC#12 It allows student can be see the schedule for a
week
Set schedule UC#13 The HOD can set the time schedule for a week.
Send feed back UC#14 Student sent the feedback to the admin for the
purpose of correcting teaching process.
Table 6Descriptions and Identification of use cases.
3.5 Use Case Diagram

Use case diagram are consists of actors, use case, and their relationship to each other. A single
use case diagram captures a particular functionality of the system. Use case diagram for the
proposed system are used to represent the basic functionalities of the system as use cases focus
on the behavior of the system. In our project the major actors that plays major role out of the
system are administrator, registrar and student instructor the use cases incorporated in the system
are: Upload and Download Course material, Upload Download assignment questions and View
course result. The following figure specifies the use case model of the system.

MTU E-Learning System View assigned

nc
course
Manage Create «include»
Account Account Upload
«extends»
Update view class
view/delete Account Logout schedule
«extends»
feedback nclu Instructor
Administrator «include»
«include» Delete e Down load
Account
Manage user de «include»
«inIncclluuddee» Post Course
«include»
«extends» Grade
«extends» «include» «include»
n ud
«include»
deactvated
Actvated View Course
Login «include» Grade
«include»
«inlucdlude»
post Forum «include» Download
«include»
«include»
«include»
«include» Upload
set schedule «include»
HOD «include» View Class
Assing schedule Student
Instructor
send
feedback
view respons Participated

forum
Figure 2Descriptions and Identification of use cases.
3.7 Use Case Description

The descriptions briefly explain how the functionalities precede using natural language in a step
wise manner. Use case of every activity is stated below:

Use Case Name Login
Use case Identifier UC#1
Description This use case allow the user login to the system
Actor Administrator, HOD, Instructor and student.

Pre-condition The user must be have user account
Flow of events Step1: user start home page.
Step2:Click the login link
Step3: The system displays the login form
Step4: Fill user name and password
Step5:Click login button
Step6: system Validate user name and password.
Step7: The system displays the appropriate user page.
Alternative Flow 5.1 If the username and password is incorrect .Then

system displays incorrect user name and password
message
5.2 Go to step4.
Post- condition The authenticated user gets the appropriate page.

Table 7 Use case description for login

Use Case Name Manage user account
Description Administrator manages users’ account.

This use case describe create , delete ,update user
account
Actor Administrator
Pre-condition An Administrator should have to enter a valid user name
and password in order to create, update and delete user

account.
Flow of events 1. login to the page
2. Administrator should have to choose account
item order to create, update and delete user
account.
3. Then click on the selected account item.
4. The Administrator should have to create, delete,
and modify the user’s account.
5. Displayed successfully message.
Alternative Flow 1. If administrator full incorrect, system display
error message.
2. Use-case resume at step 3 of basic flow of events
Post-condition You update, create and delete user account successfully
message will be displayed.
Table 8Use case description for manage user account
Use Case Name Post forum
Description: Allows the HOD activate the system and access the home
pages then post the forum
Actor HOD
Pre-condition The user should have to enter a valid user name and
password.
Flow of events 1. User login to the page and click post forum link
2. System display forum page
3. User fill post forum
4. User click post button.
5. The systems validate the form
6. The system display successful message.

Alternative Flow 3.1 If the user fill incorrect form of forum then the
system display error message
3.2 Go to step3
Post-condition Post forum successfully.
Table 9Use case description for Post forum
Use Case Name download material resource
Description Allows the students activate the system and access the
home pages and also download the available course
material resource
Actor Student, Instructor

Pre-condition Instructors must upload materials
Flow of events 1. user login to the page

2. Clicks on download material link.
3. The system displays list of material.
4. Selects the required material.
5. Click download.
6. Downloaded successful.
Alternative Flow 5.1 If materials not download immediately.

5.2 Go to step4
Post-condition Download the material resource successful.
Table 10Use case description for download material resource
Use Case Name Upload material resource


Description Allow the instructor and Student uploads course material
to the student and instructor.
Actor Instructor, Student
Pre-condition Instructor, Student must prepare assignment questions,
assignment answer to upload.
Flow of events 1. User login to the page
2. Clicks on upload link.
3. The system displays the upload form.
4. Select file to upload.
5. Click upload button.
6. Upload successful
Alternative Flow 4.1 If not upload.

4.2 Go to step4
Post-condition The uploaded successfully

Table 11 Use case description for upload material resource
Use Case Name post grade
Description The instructor may be calculate the student grade

including test ,quiz , assignment, final exam
Actor Instructor
Pre-condition The instructor must be login to the system
Flow of events 1. login to the home page
2. Click Computive grade link.
3. The system display computive grade form.
4. Fill student’s grade.
5. Click Computive button.
6. The system validates the student grade.
7. System display successful Computive grade.
Alternative Flow 4.1 If the Instructor fills incorrect id the system display
error message.
4.2 Go to step4

Post-condition Instructor should be computive grade result successfully
messages display.
Table 12Use case Description for post grade
Use Case Name View feed back

Description The students can send the feedback to admin
Actor Admin
Pre-condition the admin must login to the system

Flow of events 1. Admin login to the page
2. Admin clicks on view feedback link.
3. Admin click on view feedback button
4. Displayed feedback
Alternative Flow 3.1 If Admin use incorrect process the system
display error message.
3.2 Go to step2
Post-condition The feedback will be displayed successfully

Table 13Use case description view feedback
Use Case Name Participate forum
Description It allows the stakeholder of the system to be sharing their

own idea with the other.
Actor Student
Pre-condition The user must have valid user name and password.
Flow of events 1. The user login to the page

2. Enter username and password.
3. Click login link.
4. User clicks on view forum.
5. The system display the forum form
6. The user write their idea
7. Then users click on send button.
8. The system displayed send successfully
Alternative Flow 2.1 If the user enter invalid username and password to
system. The system display error message.
2.2 go to step2
Post-condition The user participate successfully
Table 14Use case description Participate forum
Use Case Name View class schedule
Description Student can be see the time schedule for a week
Actor Student
Pre-condition student must be login to the system
Flow of events 1. The student login to the page

2. Click view class schedule link
3. The student click on view class schedule button
Alternative Flow 4.1 If student use incorrect process the system display
error message.
4.2 Go to step4
Post-condition Display class schedule

Table 15Use case description view class schedule
Use Case Name Send feed back

Description Student send feedback to the admin in order to correct
the teaching process
Actor Student
Pre-condition The student must be login to the system
Flow of events 1. The student login to the page
2. Click send feedback link
3. System display form
4. Student fills information.
5. Click send button.
6. The system validates information.
7. The system display successfully message
Alternative Flow 4.1 If the user enter incorrect information the system
display error message.
4.2 go to step4
Post-condition The student send feedback correctly

Table 16Use case description Send feedback
Use Case Name Assign instructor
Description Head of department (HOD) can be assign instructor with

in course.
Actor HOD
Pre-condition Allows the HOD check the status of instructor to assign
Flow of events
1. login to the page
2. Clicks instructor link.
3. The system display assigns instructor form.
4. Fills the assign form.
5. Click assign button.
6. The system validates the assign instructor
information
7. The system display successful assign instructor

message.
Alternative Flow 4.1 If the user fills incorrect form for assigning instructor
then the system display error message
4.2 go to step4.
Post-condition Successful assign instructor
Table 17Use Case Description of Assign Instructor
Use Case Name Set schedule
Description Head of department prepare time schedule for a week
Actor HOD
Pre-condition The user must be login to the system
Flow of events 1. The user login to the page

2. Click set schedule link
3. display set schedule form
4. Fill the time and course code
5. Click set schedule button
6. System validate message
7. The system display successfully message
Alternative Flow 4.1 If HOD fill in correct time and course code the
system display error message
4.2 Go to step4
Post-condition Set schedule successfully prepare.
Table 18Use Case Description Set schedule

3.6 Sequence Diagram
A sequence diagram links use case with objects. It shows the interaction between participating
objects in a given use case. It is helpful to identify the missing objects that are not identified in
the analysis object model. From the use case we can see the sequence diagrams of the system is
shown as follows. [2][3][1]
Sequence digram for Login

Home page Login link Login form Login Database
User <<UI>> <<UI>> <<form>> <<controller>> <<DB>>
User Action 1:login to home page
User (All user) 2:click login link()
Step 1: login to home send request()
Page
Step 2: click login link 3:display form()
step 3: the system 4: fill user name and
display login form password()
step 4: fill user name Send request() 6:validate()
and password 5:click login button()
Step 5:Click login button try again() Send()
Check
Step 6: System validate
user name and password
if the name and password
incorrect the system 7: display appropriate user page True
display incorrect user
name and password
message.
Step 7: The system
display appropriate user
page.
Figure 3Sequence diagram for Login

Sequence digram for upload course material

Home page Upload link Upload form Upload Database
User (Student) 2:click upload link()
Step 1: login to home send()
Page
Step 2: click Upload link 3:display form()
step 3: Display form 4:Select upload file()
step 4: Select upload file 5:click upload button() Send () 6:validate()
Step 5:Click Upload
button
try again() Send() Check
Step 6: if file not upload
system display error
message.
Step 7 :Uploaded True
successfully 7:Upload successfully
Figure 4Sequence diagram for Upload Course Material

Sequence digram for Download material

Home page Download link Download form Download Database
student <<UI>> <<UI>> <<form>> <<controller>> <<DB>>
User (Student) 2:Click Download link()
Step 1: login to home send()
Page
Step 2: Click 3:display form()
Download link 4:Selectrequired material()
step 3: Display form 5:click Download button() Send () 6:validate()
step 4: Select required
material
Step 5:Click Download try again() Send()
Check
button
Step 6:If material is not
download the system True
display error message 7:Downloaded successfully
Step 7 :Downloaded
successfully
Figure 5Sequence diagram for Download Material

Sequence digram for View feedback

Admin page Send feedback Feedback form Feedback
Admin 1:login to <<UI>> Database
link <<form>> <<controller>>
User Action Admin page <<UI>> <<DB>>
User (Admin) 2:Click link()

Step 1: login to
3: Send ()
Student Page
Step 2:click Feedback 4:Display form()
link
step 3: send 5:Click View Feedback button() 6: Sent request()
Step 4:Display the 7:Validate()
from
Step 5 :Click view Invalid()
feedback button Try again()
Step 6: Send request Send()
Step 7:validate in
system 8: Feedback sent
step 8: display
Feedback
Figure 6Sequence diagram for view feedback

Sequence digram for Send feedback

Student page Send feedback Feedback form Feedback
Student <<UI>> Database
1:login to link <<form>>
User Action <<controller>> <<DB>>
Student page <<UI>>
User (Student) 2:Click link()
Step 1: login to
3: Send ()
Student Page
Step 2:click Feedback 4:Display form()
link 5:Enter the basic information()
step 3: send 6:Click Feedback button() 7: Sent request()
Step 4:Display the 8:Validate()
from
Step 5: Fill the basic Invalid()
information 9:Try again()
Step 6 :Click 10:Send()
Feedback button
step 7:sent request 11: Feedback sent
Step 8: Validate,if
invalid system
Step 9 :try again
Step 10:send
step 11:Feedback sent
Figure 7Sequence diagram for send feedback

Sequence digram for Post forum

Home page Post forum link post forum form Post forum Database
User (User) 2:click post forum link()
Step 1: login to home send ()
Page
Step 2: click post forum 3:display form()
link 4:User fill post forum()
step 3: Display form 5:Click post button() send information() 6:validate()
step 4: User fillpost
forum try again()
Step 5: Click post button Send() Check
Step 6: if user fill
incorrect post
information the system
7:display successfully posted() True()
display error message
Step 7: The system
display successfully
posted
Figure 8Sequence diagram for post forum
3.9 Activity diagrams

Activity diagram is another important diagram in UML to describe dynamic aspects of the
system. Activity diagram is basically a flow chart to represent the flow form one activity to
another activity. The activity can be described as an operation of the system. So the control flow
is drawn from one operation to another. This flow can be sequential, branched or concurrent.
Activity diagrams deals with all type of flow control by using different elements like fork, join
etc. [4] [5]. The following activity diagrams are specified in the new system of MTU E-Learning
System.

Activity Digram of MTU E-learning system for
login
System User
Browser website
Click login link
Enter user name

and password
Click login button
No
is validate ?
Yes
Display available
page
Figure 9Activity diagrams for Login


Download Course Material
student Login to
page
Click download link
Select download
course material
No
Is validate?
Yes
Download
Figure 10Activity diagrams for download course material

Activity Digram of MTU E-learning system for View

feedback
Admin
click Browser Display click login
link home page link
Enter username and

password
click login button

Display error
message
No
is validate ?
Yes
Display Admin
page
Click view
feedback link
No
Click feedback
button is validate ? Display feeddback
Yes
Figure 11Activity diagrams for View feedback

Activity Digram of MTU E-learning system for manage account

Administrator
login to Page
Click manage
account link
Select
update,create,delete
link
Display the form
Fill information
Click update,delete
No
and create button
Is validate ?
Yes
Display successfully
message
Figure 12Activity diagrams for Manage Account


Upload Course Material
Instructor
login to page
Click upload link
Click browser
button
Select file
To large
File not found

File
File found
Small
Click upload button Check Upload
Figure 13Activity diagrams for upload material

Activity Digram of MTU E-learning system for send

feedback
Student
click Browser Display click login
link home page link
Enter username and

password
click login button

Display error
message
No
is validate ?
Yes
Display Student
page
Click send
feedback link
No
fill theform
Click feedback Yes

Display successful
button is validate ?
massage
Figure 14Activity diagrams for send feedback

Activity Digram of MTU E-learning system for Post

forum
Registrar
login to Page
Click post forum link
Display form
Fill information
Cilck post grade

button
No
Is validate ?
Yes
Display successful
message
Figure 15Activity diagrams for post forum

3.7 Class diagram
A Class diagram for creating objects and implementing behavior in a system. In UML, a class
represents an object or a set of objects that share a common structure and behavior. They're
represented with a rectangle that includes rows of the class name, its attributes, and its
operations. When drawing a class diagram on a class diagram, only the top row must be filled
out the others are optional if you would like to provide more detail.
 Name - the first row in a class shape.
 Attributes - the second row in a class shape.
 Methods - the third row in a class shape. Also known as operations. Also known
as operations.[2][3]
Our class Diagram contains the following Class

 Student
 Assignment
 Course material
 Account
 Administrator
 HOD
 instructor

CLASS DIAGRAM
Student
Take
Create
1 * 1
Administrator Account -First Name string
-Last Name string
-First Name string -Student Id int
1 use
-Last Name string -Name string 1
-Sex string -Password int +View Result()
-Address string Use Give Feedback()
+manage account() 1 +Create Account() create
+ view feedback() +Delete Account() 1 1
*
1 +Update Account()
1
Control
doing
Assign 1 HOD
Manag
e -first Name string
Manag -last name string 1 *
e - id number int
*
*
+Assign instructor() give
1 * Assignment
* 1
* 1 * -Assignment Name string
Give
Instructor * -Course Code int
Schedule
-First Name string Course Material Doing +Upload()
-Last Name string * * +Download()
-Sex string *
-Material Name string
+Give Assignment() -Material Code int
+computive grade() *
+Upload()
+Download()
*
Figure 16 Class diagram of the systems

CHAPTER FOUR
4 System Design
4.1 Introduction
System design is the transformation of the analysis model into a system design model. System
design is the first part to get into the solution domain in a software development. This chapter
focuses on transforming the analysis model into the design model that takes into account the
nonfunctional requirements and constraints described in the problem statement and requirement
analysis sections discussed earlier. [1]
4.2 Class Type Architecture (System Architecture)

Since our system modeling approach is object oriented, we have to describe the system in terms
of its architecture. In this section we have demonstrated different types of class type
architectures; that represent a high-level layering strategy for software application. The various
layers are represented by the rectangles and collaboration between layers indicated by the
arrows. The primary name of the layer is indicated first, and other common names indicated in
parenthesis.
1. Interface: This layer wraps or covers access to the system and system interface. There
are two categories of interface class-user interface (UI) classes that provide people access
to the system and system interface (SI) classes that provide access to external systems to
the system. XAMP server used to implement UI classes with in php and html. Web server
used to implement SI classes
General this Layer is the form which provides the application to either programmer or end user.
The user interface layer of MTU-Learning system includes the following classes
 Home page
 Admin, instructor, student and HOD page
2. Control/process layer: This layer represents controller/process class that implements
business logic that involves collaborating with several business or domain classes or even
other process classes.

3. Domain: This classes implements the concepts of our business domain focusing on the
data aspects of the business objects, plus behaviors specific to individual objects. This
layer is used to transfer data from application layer or presentation layer to data layer.
4. Persistence/Data layer: This layer is used to encapsulate the store their data in one or
more data stores. Often implement between our system object and our system database.
This layer is also a class to get or set data to the database queries back and forth
5. System layer: This layer is used to represents system class that provides operating
system specific functionality for the applications, isolating the software from the
operating system (OS) by wrapping OS specific feature, , increasing the portability of our
system application.
Interface
(User interface,System interface)
process System
(Application, controller) (Infrastructure
platform)
Domai
n
(Busines
s)
Persistent
(Database)
MTU E-learning
database
Figure 17Class Type Architecture of the system

4.3 Deployment Modeling
The name Deployment itself describes the purpose of the diagram. Deployment diagrams are
used for describing the hardware components where software components are deployed.
Component diagrams and deployment diagrams are closely related. Component diagrams are
used to describe the components and deployment diagrams shows how they are deployed in
hardware.

Application
Manage
DeploymentDiagram Account DATABASESERVER
Uploade
MYSQL
post grade
Client Computer PHP
Post Forum
Web
browser Download
MTUE-LEARING
Sendfeedback DATABASESYSTEM
Biadu
browser setschedule
Participate
forum
viewfeedback
Figure 18Deployment modeling of the system

4.4 User Interface Design
User interface design focuses on what user need to do and ensuring that the interface has
elements that are easy to access. The goal of user interface design is to make the user’s
interaction as simple and efficient as possible, in terms of accomplishing user goals.

user interface design
Login
Home About As Contact As Gallery
Instructor
Student HOD
Administrator post result
Upload Post forum
Manage account
View schedule
Download Assign
Download Instructor
View users
View class
schedule Upload Set schedule
Manage user
View result
Logout Logout
Logout
Send feedback
participate
forum
Logout
user interface design
Login
Home About As Contact As Gallary
Instructor
Student HOD
Adminsterator post grade
Upload Post forum
Manage account View schedule
Download Assign
Download Instructor
View feedback View class
schedule Upload Set schedule
Manage user
View grade
Logout Logout
Logout
Send feedback
participate
forum
Logout
Figure 19User Interface Design

4.5. Boundary condition
Describe the start-up, and error behavior of the system. Some boundary conditions of the user
interface include:
Home page: At the time the user starts to use the system first home page will be displayed and it
contains some links as well as some descriptions which are about the system.
Figure 20 Home page interface
Login page: The login page contains an option such as administrator, instructor, HOD and
student login then each option contains user name and password and users should enter the
correct user name password and their privilege correctly to get the page.

Figure 21 Login page interface
4.5.1 Internal flow of the system

After login in to the system it can perform different activities such activities include:
Create Account page: This activity only performs by the administrator, the administrator can
create account for instructor, student and HOD

Figure 22 Create account page interface
Post Course of result: Instructor can perform these activities that can Post Course of Resultfor
student

Figure 23 Post Course of result
Upload Assignment Qes: Instructor can perform these activities that can upload assignment
question for student.

Figure 24 Upload assignment Qes
Assign Instructor: HOD can perform these activities that can Assign instructor to the course of
student.

Figure 25 Assign Instructor
4.6. System Testing
4.6.1. Security testing

The system has a security protection by using authentication. User of the system will be
authorized by the system administrator and get their user name and password to enter into the
system. Unauthorized access will be detected when user wants to access the system. This is
done by authenticating user; user with user name and password can only enter into the system.
This security action is done in the login form.
Another method used to secure the system is by grouping user by privileges. Every user of the
system will enter to the system according to their privileges and access different menus when
they enter to the system. This security method is tested and user cannot enter to other person
privileges and access data. So the system is secured.

4.6.2. Unit testing
In unit testing each the data in the data base is tested through form or report with a specific data.
This test helps to trap output errors occur in the form or report. Each module is tested alone in
attempt to discover any error in its code.
Table Unit testing
Tested Test Case Pass Fail

Form
Login Form Validate user name Display a new user page Display tries again a
and password entry when the user fills correct message when the user
as an input from user name and password. fills incorrect user name
each end users or password.
All other Validate the fill Display either a new page Display tries again a
forms form entry data as or user perform successful message when the user
an input from each task when user insert fills incorrect data.
end users task. correct data in to the form
try to save on data base.
Table 19 Unit testing
4.6.3 Integration testing

The process of bringing together all of the modules that a program comprises for testing
purposes. Modules are typically integrated a top-down incremental fashion. In this testing
mechanism each form is tested by a general data.
Table Integration testing
Tested Form Test Case Expected Result
Login Form Check the correctness of the Display administrator or system

form to be displayed after login members menu
is succeeded
Administrator menu check proper display of selected Display the selected form from

options to be accessed the administrator form as menu
General information check whether the information The selected information

form will be generated or not
will be displayed
All forms check the navigation The form required will be

displayed
functionality
Table 20 Integration testing
4.6.4. Validation testing

When we say valid it is to mean that the software functions as it is intended. The group team
can test by giving real data and get real information from the software.
Tested from Test case Expected Actual result
result
Login form To validate the proper To user will be authenticated and

functionality of login by authenticate if user is authorized enter to the
inserting username and user system else confirm invalidity
password
View from To validate the View result Either the requested record exist
functionality of view display the result or it doesn’t
form exist display the message about
the status
All forms To validate the To provide The form is presented and the
functionality of each the function required function can operated
form required by using the form
the form
Table 21 Validation testing

CHAPTER FIVE
5. IMPELMENTATION AND TESTING
5.1 Introduction
The purpose of this part of the document is to provide the highlight of the issues deal with
the implementation phase. Testing assesses is the quality of the product. Software testing
is a process that should be done during the development process. In other words software
testing is a verification and validation process.
5.2. Implementation
This phase, the implementation is a phase where all the work during analysis and design will
be turn off to a functional system prototype for the project proposed; it is divided into three
parts
 User interface Implementation: it is designed and documented in the

previous chapter (chapter four) in which users are interface with the system.
It can make the user's interaction as simple and efficient as possible, in terms of
accomplishing user goals.
 Logical Implementation: - is the part in which the implementation of the

functionality of the system and.
 Database implementation: - the database implementation is now the team
members are goes to develop in this phase but it is also designed in the
previous chapter.
5.3. Final testing of the system

Our system will be tested based on the following testing procedures.
 Requirement analysis test: the requirement analysis that we gather through interview,
will be tested by the team members.
 Design test: the design will be tested by the members in the way it meets the requirement
analysis.

 Implementation test: the implementation is tested in three steps
as follows:-
 Unit testing: In unit testing each the data in the data base is
tested through form or report with a specific data. This test helps
to trap output errors occur in the form or report. Each module is
tested alone in attempt to discover any error in its code
Tested Test Case Pass Fail

Form
Login Form Validate user name Display a new user page Display tries again a
and password entry when the user fills correct message when the user
as an input from user name and password. fills incorrect user name
each end users or password.
All other Validate the fill Display either a new page Display tries again a
forms form entry data as or user perform successful message when the user
an input from each task when user insert fills incorrect data.
end users task. correct data in to the form
try to save on data base.
Table 22 Unit testing
 Integration testing: the unit parts are integrated together and then tested by the
members
The process of bringing together all of the modules that a program comprises for testing
purposes. Modules are typically integrated a top-down incremental fashion. In this
testing mechanism each form is tested by a general data.
Tested Form Test Case Expected Result
Login Form Check the correctness of the Display administrator or system

form to be displayed after login members menu
is succeeded

Administrator menu check proper display of selected Display the selected form from
options to be accessed the administrator form as menu
General information check whether the information The selected information

form will be generated or not
will be displayed
All forms check the navigation The form required will be

displayed
functionality
Table 23 Integration testing
 Performance Testing: Performance testing is the testing to assess the speed and
effectiveness of the system and to make sure it is generating results within a specified
time as in performance requirements
 Security testing: The system has a security protection by using authentication. User
of the system will be authorized by the system administrator and get their user name
and password to enter into the system. Unauthorized access will be detected when user
wants to access the system. This is done by authenticating user; user with user name
and password can only enter into the system. This security action is done in the login
form.
Another method used to secure the system is by grouping user by privileges. Every user of the
system will enter to the system according to their privileges and access different menus when
they enter to the system. This security method is tested and user cannot enter to other person
privileges and access data. So the system is secured.
 Validation testing: When we say valid it is to mean that the software functions as it is
intended. The group team can test by giving real data and get real information from the
software.
Tested from Test case Expected Actual result
result
Login form To validate the proper To user will be authenticated and
functionality of login by authenticate if user is authorized enter to the
inserting username and user system else confirm invalidity
password

View from To validate the View result Either the requested record exist
functionality of view display the result or it doesn’t
form exist display the message about
the status
All forms To validate the To provide The form is presented and the
functionality of each the function required function can operated
form required by using the form
the form
Table 24 Validation testing
5.4 Hardware software acquisition

Before trying to do anything first we need a web server to which the web application is
going to be deployed, secondly there are certain things that should be taken into account.
To mention some we need to have installed in that web server. After the server is installed
then the database is attached to this server. But if the server is already installed we will
only attach the database.
5.5 User manual preparation

We have prepared a manual for how to use this site in our help link. There is a help link
for each user type meaning we have prepared help link for administrator, student, HODr
and instructor in their respective home page.
5.6 Training
After this site is deployed on a web server, we will give training for the user until they became
familiar with the system.
5.7 Sample code for create account

<form name="myForm" action="createaccount.php" method="post" name="createaccount.php"
onsubmit="return check()">
<fieldset><legend align="center"><font size="+3"face="monotype corsiva"size="+4"
color="blue"><strong> Create Account For New User</strong></font></legend>
<table width="500">
<tr>
<td width="50%">First Name:<br/><br/></td>

<td><input type="text" name="fname" id="fna">
</td>
</tr>
<tr>
<td width="50%">Last Name:<br/></td>
<td><input type="text" name="lname"id ="lname">
</td>
</tr>
<tr>
<td width="50%">Id number:<br/></td>
<td><input type="text" name="id" id="id">
</td>
</tr>
<tr>
<td width="50%">Age<br/></td>
<td><input type="text" name="age" id="age" size="20%"
onkeypress='return event.charCode>= 48 &&event.charCode<= 57'>
</td>
</tr>
<tr>
<td width="50%">sex<br/></td>
<td><select type="dropdown" name="sex"id="sex">
<option selected >..select..</option>
<option>Male</option>
<option>Femal</option>
</select>
</td>
</tr>
<tr>
<td width="50%">department<br/></td>
<td><select name="rol" id="dpt">
<option selected>..select..</option>
<option>none</option>
<option>IT</option>
<option>CS</option>
<option>IS</option>
<option> CIVILE</option>
</select></td>

</tr>
<tr>
<td width="50%">Course<br/></td>
<td><select type="dropdown" name="cou" id ="cou">
<option>java</option>
<option>andoriod</option>
<option>english</option>
<option> Php</option>
</select></td>
</tr>
<br>
<tr>
<td width="50%" >year </td >
<td><select type="dropdown" name=" year" id="yes">
<option>I</option>
<option>II</option>
<option>III</option>
<option>V</option>
<option>IV</option>
</select>
</td >
</tr>
<tr>
<td width="50%" >Semister</td >
<td><select type="dropdown" name=" Semister" id="sm">
<option>I</option>
<option>II</option>
</select>
</td >
</tr>
<tr>
<td width="50%">User Name:<br/></td>

<td><input name="name" id="uname"></td>
</tr>
<tr>
<td width="50%">Email:<br/></td>
<td><input name="email" type="text" id ="email" placeholder='xxx@gmail.com' ></td>
</tr>
<tr>
<td width="50%">Password<br/></td>
<td><input name="pass" type="password" id="passe">
</td>
</tr>
<td width="50%" valign="middle">Role:</td>

<td><select name="role" id ="rol">
<option>Student</option>
</select></td>
</tr>
<tr>
<td></td>
<td>
<button class="button_small" name="submit" type="submit"

type="submit">Submit</button>
<button class="button_small" class="submit" type="reset">Reset</button></br>

</td>
</tr>
</table>
<?php
if(isset($_POST["submit"])){
$a=$_POST["fname"];
$b=$_POST["lname"];
$c1=$_POST["id"];
$c=$_POST["age"];

@$d=$_POST["sex"];
$d1=$_POST["rol"];
$d2=$_POST["cou"];
$e2=$_POST["Semister"];
$e4=$_POST["year"];
$h3=$_POST["name"];
$h=$_POST["email"];
$f=base64_encode($_POST["pass"]);
$g=$_POST["role"];
$status='on';
mysql_select_db("mtu");
$result= mysql_query ("INSERT INTO
newaccount(fname,lname,idnumber,age,sex,Coursename,rol,Semister,year,username,email,password,role,
status,updateddate) VALUES('$a', '$b', '$c1','$c', '$d','$d2','$d1', '$e2','$e4', '$h3','$h', '$f','$g','$status',
now() )");
if (!mysql_query($result))
{
echo'<p class="success"><font face="monotype corsiva" size="+2"> successfully
created</font></p>';
echo'<meta content="9;createaccount.php" http-equiv="refresh"/>';
}
else
{
echo'<p class="wrong"><font face="monotype corsiva" size="+2"> Something

wrong!! </font></p>';
echo'<meta content="9;createaccount.php" http-equiv="refresh"/>';
}}
mysql_close($con)
?>
</fieldset>
</form>
5.8 Sample code for view account
<?php
include("connection.php");
require("session.php");
?>
<td width="700" height="80" rowspan=4 align="center"valign="top" bgcolor="#FFFFFF"
class="one"><br>

<table width="400">
<tr>
<td>
<form action="" method="POST" name="add">
<center><font size="+3" color="#0000CD"><i><strong>Update From Existing

File</strong></i></font></center><br><br><br>
Enter name   <input type="text" name="title" >
              &n
bsp;             &nbs
p;       <button class="button_small" name="search"
type="submit" type="submit">search</button>
</form>
<table border ="1"id='vtable' style='width:520;border:1px solid #336699;border-
radius:10px;' align='center'><font color=white>
<form action="delet_res.php" method="post">
<tr>
<td bgcolor="#336699"><font color='white' size='3'>ID</td>
<td bgcolor="#336699"><font color='white' size='3'>fname</td>
<td bgcolor="#336699"><font color='white' size='3'>lname</td>
<td bgcolor="#336699"><font color='white' size='3'>age</td>
<td bgcolor="#336699"><font color='white' size='3'>sex</td>
<td bgcolor="#336699"><font color='white' size='3'>user name</td>
<td bgcolor="#336699"><font color='white' size='3'>password</td>
<td bgcolor="#336699"><font color='white' size='3'>role</td>
<td bgcolor="#336699"><font color='white' size='3'>Update</td>
<td bgcolor="#336699"><font color='white' size='3'>Delete</td>
</tr>
<?php
require("connection.php");
if(isset($_POST['search']))
{
$content=$_POST['title'];
$count=1;
$query="SELECT * FROM newaccount
WHERE fname LIKE '%{$content}%' OR lname LIKE '%{$content}%'";

$result = mysql_query($query) or die ("Error in query: $query. " . mysql_error());
$i=0;
while($row = mysql_fetch_assoc($result)) {
$i++;
$color=($i%2==0)?"lightblue":"white";
?>
<trbgcolor="<?php echo $color?>"><td align="center">
<?php echo $count; ?>
</td><td align="center">
<?php echo $row["fname"]; ?>
<?php echo $row["lname"]; ?>
<?php echo $row["age"]; ?>
<?php echo $row["sex"]; ?>
<?php echo $row["username"]; ?>
<?php echo $row["password"]; ?>
<?php echo $row["role"]; ?>
<a href="updateaccounnt.php?id=<?php echo $row["id"]; ?>"><img width="50" height="30"
src="shumi/edit.jpg"/></a></td>
<td align="center">
<a href="delete.php?id=<?php echo $row["id"]; ?>"><img width="50" height="30"
src="shumi/delete.jpg"/></a></td></tr>
<?php $count++;
}
}
?>
</form>
5.9 Sample code for view Course result
<form action="course result.php" method="post" name="upload"enctype="multipart/form-data"

onSubmit="return check()">
<fieldset><legend align="center" ><font size="5" color="#0000CD"><i><strong>Enter #ID Number To
See Your Result</strong></i></font></legend><br>

<span class="w"><span class="w">
Id Number:    <input type="text" name="id" id="id" size="20%" ><br><br>
<input type='submit' value='view' name='view' id="view" />

</fieldset>
<?php
if(isset($_POST['view']))
{
$id=$_POST['id'];
$result_set = mysql_query("SELECT * FROM result WHERE studentid='$id' ");
if(!$result_set)
{
die("query is failed".mysql_error());
}
if(mysql_num_rows($result_set)>0)
{
echo "<table id='vtable'border='1' style='width:650px;border:1px solid #336699;border-radius:10px;'

align='center'><font color=white>
<br>
<tr>
<thbgcolor='#336699'><font color='white' size='2'>student id</th>
<thbgcolor='#336699'><font color='white' size='2'>course name</th>
<thbgcolor='#336699'><font color=white size='2'>Quizz</th>
<thbgcolor='#336699'><font color=white size='2'>Test</th>
<thbgcolor='#336699'><font color=white size='2'>individual Assi</th>
<thbgcolor='#336699'><font color=white size='2'>Group Ass</th>
<thbgcolor='#336699'><font color=white size='2'>Final</th>
<thbgcolor='#336699'><font color=white size='2'>Total</th>
<thbgcolor='#336699'><font color=white size='2'>Grade</th>
</tr>";
while($row=mysql_fetch_array($result_set))
{
echo"<tr>";
echo"<td>";echo $row["studentid"]; echo"</td>";
echo"<td>";echo $row["coursename"]; echo"</td>";
echo"<td>";echo $row["quizz"]; echo"</td>";
echo"<td>";echo $row["test"]; echo"</td>";

echo"<td>";echo $row["individuaiassignment"]; echo"</td>";
echo"<td>";echo $row["groupassignment"]; echo"</td>";
echo"<td>";echo $row["final"]; echo"</td>";
echo"<td>";echo $row["total"]; echo"</td>";
echo"<td>";echo $row["grade"]; echo"</td>";
echo"</tr>";
}
echo "</table>";
//echo' <meta content="27;courseresult.php" http-equiv="refresh" />';
}
else
{
echo '<center>';
echo'<p class="wrong"><font face="monotype corsiva" size="+3">Result not found !!</font></p>';
echo'<meta content="7;course result.php" http-equiv="refresh"/>';
echo '</center>'; }
}
mysql_close($con);
?>
</div>

CHAPTER SIX
6. CONCLUSIONS AND RECOMMENDATION
6.1 Conclusion
This project which has two phases; the first phase concerned with the analysis phase
of the life cycle, the design phase and the next phase is about implementation. As the end
of the first phase, we need to review that we have covered in accordance with what we
have planned at the beginning. We began our work by identifying the significance of
automated system for the overall techniques to be used in the development process. This
involved defining the system development methodology, identifying process. This
involved defining the system development methodology, identifying resource and cost
requirements, and setting the deliverable and scheduled for the project.
The analysis helps the team to well understand the major functional areas and processes
of the system. Through this method we evaluate the existing system weakness and strength.
After that, we performed requirements elicitation to discover user and system

requirements. This phase consisted of drawing the functional as well as non-functional
requirements of the system. Then we have undertaken a major phase in system
development process: object oriented Analysis. Here, we tried to model the new system
we proposed using UML diagrams: Use case, sequence, and activity and class diagrams
Also, we designed the new system user interface prototype.

6.2 Recommendation
The system that we have tried to automate is not the whole system of E-learning system. Because
of time limitation and budget we can’t develop all parts of the system, but we tried to automate
some sub systems and functionalities
The following functionalities can’t be automated because of the limitations that we have
discussed above.
 Online examination
 Online video learning
 Online registration
Therefore, others are interested individuals to develop on E-learning system can get some initial
idea about the system and no need of more data gathering process the only need will be
improving the system.

Reference
[1] Brueghel, Bernd (2000) Object oriented Software Engineering Conquering Complex and
Changing System.Upper Saddle River: Prentic Hall.
[2] The Object primer: The application Developers Guide to Object Oriented andthe UML.2nd
rev. Ed England: The Colombia University.
[3] Scott, W. A. The Object Primer: “The Application Developer’s Guide to Object
Orientation and the UML”, 2001.
[4] Castro, J., Kolp, M., &Mylopoulos, J. “Towards requirements-driven information systems
engineering: the Tropos project”, Information systems, Vol.27 (6), pp. 365-389, 2002.
[5] Fengzhu, L. I., Bao, S., &Sijun, L. I. “Applications of Lean Logistics on Engine
Manufacturing Planning”. SAE International Journal of Materials and Manufacturing, Vol.
7, pp. 308-312, 2014.
[6]https://www.google.com/#q=hardware%20and%20software%20requirements
%20for%20system%20development

New Printed

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

New Printed

Caricato da

Copyright:

Formati disponibili

MTU E-Learning System 2017/18

MIZAN TEPI UNIVERSITY

Project Title: - MTU E-learning system

Advisor Name Mr.Habtewoled D

Co-Advisor Name Mr. Abraham D

School of Computing and Informatics Dep’t of IT Final project Page

Department : Information technology

Project title: MTU E-learning system

Examining committee members Signature Date

School of Computing and Informatics Dep’t of IT Final project Page i

School of Computing and Informatics Dep’t of IT Final project Page ii

School of Computing and Informatics Dep’t of IT Final project Page iii

E-learning Electronic Learning

School of Computing and Informatics Dep’t of IT Final project Page iv

2.3 Overview of the Proposed System .............................................................................................. 10

5. IMPELMENTATION AND TESTING ..............................................................55

School of Computing and Informatics Dep’t of IT Final project Page

School of Computing and Informatics Dep’t of IT Final project Page vii

School of Computing and Informatics Dep’t of IT Final project Page viii

1.2. Background of the Study

School of Computing and Informatics Dep’t of IT Final project Page 1

1.3. Statement of the Problem

1.4. Objectives of the Project

1.4.1. General Objectives

1.4.2. Specific Objectives

School of Computing and Informatics Dep’t of IT Final project Page 2

1.5.1. Scope of the Project

1.5.2. Limitation of project

1.6. Risk assessment and Management

 The team member was not present because of different problems

 All team members cover the tasks

School of Computing and Informatics Dep’t of IT Final project Page 3

1.8. Methodology of the project development

Figure 1.System development methodology

School of Computing and Informatics Dep’t of IT Final project Page 4

1.9 System Development Tools

1.9.1 Hardware Tools

1 Memory Store data permanently

School of Computing and Informatics Dep’t of IT Final project Page 5

1 Browsers Like : Internet Explorer , Mozilla Firefox , Google

2 Operating system MS-window 2012 for the system.

3 MySQL To implement the database.

4 MS Word we use to edit documentation

5 PhpMyAdmin We choose PHP scripting language which aims at

Table 2 Software tool

1.10. Feasibility study

School of Computing and Informatics Dep’t of IT Final project Page 6

1.10.1 Technical Feasibility

1.10.2 Operational Feasibility

1.10.3 Economic Feasibility

 Give to 24 hour service

School of Computing and Informatics Dep’t of IT Final project Page 7

NO. Material Amount Price(ETB) Total

2. Pane 5 5birr 25birr

1.10.5 Schedule Feasibility

School of Computing and Informatics Dep’t of IT Final project Page 8

Table 4 Time Schedule

School of Computing and Informatics Dep’t of IT Final project Page 9

2 Requirement Elicitation and Analysis

2.2 Description about the Existing System

 Wastage of University’s resource

2.3 Overview of the Proposed System

 Reduce the extravagancy of the MTU resource.