E-Learning System

E_LEARNING SYSTEM FOR SODO ATVET COLLEGE 2015
Wolaita Sodo University

College of Natural and Computational Science
Department of Computer Science and Information Technology
Title: E-Learning System for Wolaita Sodo ATVET College
A senior project Submitted to the Department of Computer Science and IT,

college of Natural and Computational Science, wolita soddo University, in partial
fulfillment for the requirement of the Degree of Bachelor Science in Information
Technology.
Group members ID No
1. Gemeda Gebre NSC/R/505/04
2. Demelash Somaw NSC/R/354/04
3. Lidet eyob NSC/R/ 702 /04
4. Emnet zewudu NSC/R/416/04
5.Haimanot Yirga NCS/R/579/04
Advisor: Habtamu F. Wolaita Sodo, Ethiopia

Submission date 06/02/2015
I
Acronyms
ATVET=Agricultural Technical and Vocational Educational Training.
NNP=Nation Nationality of People
ILT=Instructor Led Training.
SQL=Structure Query Language.
HTML=Hyper Text Markup Language.
DHTML=Dynamic Hyper Text Markup Language.
XML=Extensible Markup Language.
II
Acknowledgment
First of all we like to glorify our almighty God for help us in all our life movement.
We would like to express our deepest appreciation to those people who helped even in the
smallest way in making the completion of this project entitled “SODO ATVET COLLAGE.
To instructor Mrs. Habtamu F. who never failed to guide us and give important advices
regarding our project. And most of all, to our follow teachers, who gave us valuable comments
and suggestions that helped us move further with the project we had in mind.
III
Abstract
The main objective of this project is to design and develop an E-learning system for Wolaita
Sodo ATVET College that can assist the teaching learning process . The implementation of our
project, using PHP, MySQL, and HTML is in such a way that a server, in our case WAMP
respond for any request from clients and then responds back to the user in faster and accurate
way.
The web site that we want to develop e_learning system for wolaita sodo ATVET College
with simple graphical user interface, so that users can use and interact with the system in a
simple way and user friendly manner. The group members initiated to do this project to
implement what we have learned in the past four years and to solve the problem that we
observed in wolaita sodo ATVET College.
The traditional methodology of teaching learning process both the teacher and the students need
to be in the same place for the learning teaching process.
E-Learning is an umbrella term that describes learning done at a computer, usually connected to
a network, giving us the opportunity to learn almost at any time and at anywhere.
IV
Table of Contents
Acknowledgment..........................................................................................................................III
Chapter One...................................................................................................................................1
1.1Introduction...............................................................................................................................1
1.2. Background of organization..................................................................................................2
1.3. Statement of the problem.......................................................................................................2
1.4. Team composition...................................................................................................................3
1.5. Objective..................................................................................................................................4
1.5.1 General objective..................................................................................................................4
1.5.2 Specific objective...................................................................................................................4
1.6. Scope of the project................................................................................................................4
1.7. Methodology............................................................................................................................5
1.7.1 Data source............................................................................................................................5
1.7.2 Fact finding techniques........................................................................................................5
1.7.3 design approach....................................................................................................................5
1.8. System development tools......................................................................................................6
1.9. Required resource with cost..................................................................................................6
1.10. Limitation of the project......................................................................................................7
1.11. Task and schedule.................................................................................................................7
1.12. Risk and assumption 8
a) Risks.........................................................................................................................................8
1.13. Constraints............................................................................................................................8
1.14. Benefit of the project............................................................................................................9
Chapter Two.................................................................................................................................10
Description of the Existing System.............................................................................................10
2.1 Introduction of the Existing System.....................................................................................10
2.2 Players in the existing system...............................................................................................10
2.3 Major Functions of the existing system.................................................................................11
2.4 Business rule...........................................................................................................................12
2.6 Bottlenecks of the existing system........................................................................................15
2.6.2 Information.........................................................................................................................15
V
2.6.4 Security and Control..........................................................................................................16
2.6.5 Efficiency.............................................................................................................................16
2.6.6 Service-.................................................................................................................................16
The students cannot get education material whenever they need...........................................16
2.8 Alternative options to address problems of the existing system........................................17
2.8.1 Options analysis and the proposed new system...............................................................17
2.9. Requirements of the Proposed System...............................................................................17
2.9.1 Functional Requirements...................................................................................................17
2.9.2. Non-Functional Requirements.........................................................................................17
Chapter Three..............................................................................................................................19
System Analysis............................................................................................................................19
3.1 Introduction............................................................................................................................19
2.2 System Requirement Specifications (SRS).....................................................................19
3.2.1 Use case diagrams........................................................................................................19
3.2.2 Use case Documentation...............................................................................................20
3.2.3 Sequence Diagram..............................................................................................................29
3.2.4 Activity Diagram.................................................................................................................39
3.2.5 Analysis level class diagram (conceptual modeling)..................................................46
3.2.6 User Interface Prototyping................................................................................................47
3.2.7 Supplementary Specifications......................................................................................48
Chapter Four................................................................................................................................49
Design............................................................................................................................................49
4. 1 Introduction...........................................................................................................................49
4.2 Class type Architecture.........................................................................................................49
4.2.1 Business classes.................................................................................................................51
4.2.2 User interface layer...........................................................................................................52
4.2.3 Persistent layer....................................................................................................................52
4.2.4 System layer........................................................................................................................52
4.3 Class Modeling........................................................................................................................53
4.4 .State chart modeling.............................................................................................................54
4.5. Collaboration modeling.........................................................................................................56
VI
4.6 .Component Modeling............................................................................................................59
4.7 Deployment Modeling...........................................................................................................60
4.8. Persistence modeling.............................................................................................................60
4.9 User Interface design..............................................................................................................62
Chapter Five.................................................................................................................................64
Implementation and Testing.......................................................................................................64
5.1. Introduction 64
5.2. Coding 64
5.3. Final testing of the system 64
Chapter six...................................................................................................................................73
Recommendation and Conclusion..............................................................................................73
6.1 Conclusion 73
6.2. Recommendations 73
Reference.......................................................................................................................................74
VII
Chapter One
1.1Introduction
Learning is the way of acquiring knowledge from education and it has brought great
individual and societal growth in the world and everybody giving more attention to the
educational sector, electronic learning is needed to develop for more effective learning process
to get more knowledge.
E-Learning (Electronic learning) is an umbrella term that describes learning done at a

computer, usually connected to a network, giving us the opportunity to learn almost at any time
and at anywhere.
The traditional methodology of teaching learning process both the teacher and the
students need to be in the same place for the learning teaching process. This method may
require some power.
1
1.2. Background of organization
As we know in Ethiopia there are many public and private educational institutes that
include so many colleges among those colleges which are under the administration of the
government, Wolaita Sodo Agriculture Technical and Vocational Education Training
(ATVET) College is one.
The college was established in 1994 E.C. Before this year it was running as institute. The
college now trains trainees who are delegated from different woredas those are found in
different Nations Nationalities and People (NNP) of the different Ethiopian region on
different departments such as plant science, animal science and natural resource
management.
1.3. Statement of the problem
Wolaita Sodo Agriculture Technical and Vocational Education Training (ATVET) College has
many problems which are obstacle to teaching learning process.
 Instructor led Training(ILT) which is traditional method

 The manual method requires a lot of manpower
 Wastage of resource
 Instructors may not enter the class on time
The students also face many problems among which
 There is no sufficient educational resources regarding to the courses in hard copy

 There is a problem students may not get timely information
Due to this reason we want to develop the new proposed E-Learning system to solve the above
mentioned problems. The new system gives various benefits for the Collage to eliminate the
problems.
2
1.4. Team composition
The E-learning system developing team is composed of five members.All the team members
have collaborative responsibility in the development of this project.
Project E-Learning system for Wolaita Sodo ATVET Responsibility

title
Prepared 1. Haimanot Yirga NSC/R/579/04
by Group haimanotyirga21@gmail.com implementation
6 2. Gemeda Gebre NSC/R/505/04
gebregemeda@gmail.com
3. Demelash Somaw NSC/R/354/04 Analysis
demelashgashu@gmail.com
4. Eminet Zewdu NSC/R/416/04 Design
emnifeven@gmail.com
5. Lidet Eyob NSC/R/702/04
Proposal
lideyob86@gmail.com
Date 15/03/2007
Advisor Habtamu F.
3
1.5. Objective
1.5.1 General objective

To design and develop an E-learning system for Wolaita Sodo ATVET College that can assist
the teaching learning process.
1.5.2 Specific objective

 To enable easy communication between the studies and teacher by developing a web
based E-Learning system.
 To provide an opportunity for the students to make them follow their classes at any
time and place.
 To provide the chance for users to use books or necessary material at any time and any
place.
 To increase income for the collage by reducing printing and duplicating materials.
 To introduces the new technology to the college.
 To reduce the need for classroom training
 To reduce time away from the job
1.6. Scope of the project

 The proposed system concentrates on Wolaita Sodo Agriculture Technical and
Vocational Education Training (ATVET) College E-learning for those students which
included in regular programs.
 Assignments and exams are also prepared by the instructor and are released in the
system.
 After working their exam and assignment they can submit back to their teacher by
using their account.
 Student can see their result
4
1.7. Methodology
1.7.1 Data source

For this project the team member gathered information. Firstly, from basic Science office, the
office secretary give us many data in which the team instantiated to do the project effectively.
Secondly, from some professional persons take the information in whichwe operate this project
and efficiently working and for all needed availability of the proposed project.
1.7.2 Fact finding techniques

 Interview:-To identify problems in the existing system, to identify data they use to do
their work and he will help us to get answers for questions will be raised while
interviewing.
 Document analysis:- reading different written documents

 Observation:- The team will used observation to get information that cannot be gained
using the above methodologies (Interview) such as the behavioral response of the user,
the way they deliver the course to the students
1.7.3 design approach.

 Object oriented approach
5
1.8. System development tools
Activities Tools/programs
Client side coding HTML/DHTML/XML
Client side scripting Java script
Platform MS Windows
Data base server SQL server
Web server Apache
Browsers Internet explorer, Mozilla Firefox
Editors Macromedia Dreamweaver
Documentation MS Word
User training MS Power Point
1.9. Required resource with cost
No Item type Quantity Cost
1 Paper 1desta 80 birr

2 Pen 4 10 birr
3 DVD-R 3 120 birr
4 Licensed SQL 1 400 birr
5 Flash disk 2 360 birr
Total 11 970 birr
1.10. Limitation of the project
The project does not include online registration and grading system. If we include that, the
project will be so vast and we do not have sufficient time to develop the system.
6
The system we want to develop only focuses on online learning.
1.11. Task and schedule
The following table shows the schedule of our project that describes the first phase of industrial
project -1(first phase)
Tasks Nov 4-15,2007 Nov 17-Dec 02, Dec 03-Dec Dec 29-Jan 12,
2007 27, 2007 2007
Proposal writing
Requirement specification
Analysis
Systems Design
1.12. Risk and assumption

a) Risks
The team analyzes and lists some of the risks for the AMU E-learning system. Risks
analyzed are as follows:-
o The system working environment can fail.
7
o The data collected may be attacked by virus.
o Disagreement between the team members.
o Not get expected satisfaction or benefits from the project.
o Not complete with estimate accurate project cost.
o Not complete the system on the proposed schedule or project duration.
1.13. Constraints
For the development of this project there are some restrictions on the degree of freedom the
team have in providing a solution. Constraints are effectively global requirements, such as
limited development resources or a decision by senior management that restricts the way we
develop a system. Some of the constraint which limits the performance of the system in relative
to its goal is:-
 Resource material is not available.
 Lab materials are not sufficiently available.
1.14. Benefit of the project
The system has a great significance for student, instructor and college. The team has identified
some of the significance the project has for the user and listed as follows:-
Students
8
 Students can get timely information
 They have the opportunity to follow the studies at any time and place
 Provide the chances for users to use books or necessary material at anytime and
anyplace.
 They can use their time effectively.
College
 Constructing the building for student dormitory and class room is minimized
 Introduces the current technology to college
 Preparing module with the hard copy is reduced
 Increase the performance of the college
 It increases income for the college
Instructor
 The instructor can follow student’s performance by giving exam and short assignments
from anywhere with no geographical limit.
 He/she can communicate easily with college members especially with student having the
chance to access the students question and comment.
9
Chapter Two
Description of the Existing System
2.1 Introduction of the Existing System
This chapter describes what the existing system dealing and how it operates in all the
teaching learning process. In this the Wolaita Sodo ATVET College in which every activities
operation is the manual saving of students’ document.
2.2 Players in the existing system
Wolaita Sodo ATVET College has the following players or actors. From them some of them
are:-
 Instructor
The role of Instructor is to teach the students according to the class schedule. Some of
the tasks of the instructor are:-
 Preparing exam,
 Preparing assignment
 Preparing exam
 Students
The main roles of the student in the system are:-
 Take the available exam,
 Do their assignment.
 Submit assignment, and See their result.
10
2.3 Major Functions of the existing system
The existing system has the following functionalities
 Registration
 Course material distribution
 Tutorial class
 Examination
Because it clearly shows the input, process and output of a given process, we selected
IPO(Input Process Output) method to identify function in the existing system.
A. Student Registration
Input
 Student information
 Year of admission
 Department
 Academic information
 Registrations slip form.
Process
Every student must register at the beginning of each term for courses he/she take in order
to keep her/his file active. The student will be registered by filling the registration slip. After the
students fill the registration slip, the branch center coordinator verifies whether each student has
fulfilled the prerequisites for the courses the student wants to register. After the coordinator
validates the registration slip, the student will complete his/her tuition fee .Finally, Student ID
card will be renewed for that particular semester.
Output
 Registrations slip and ID.
11
B. Course Material Distribution
Input
 Course name its credit hour.
 Course number or course code
Process
The department distributes the course material to the branch office. The branches provide
course material to the students. The course materials are distributed directly to the student
through instructor.
Output
 Student’s result
2.4 Business rule
The business rule of the Organization is as follows:-
Identifier BUSINESS RULE -1
Name Result computing rule
Description Result is computed on the basis of mark.
Example Student who got “60” and above that on course she/he will pass to next
Level, in each level the student take coc
Source ATVET College rules and regulation
Related rules ATVET College rules and regulation.
12
Identifier BUSINESS RULE-2
Name Requirement for registration
Description To register in each term the student must acquire at least pass mark of
GPA that is set by the departments of the College
Attachment letter and medical certificate bring from their wereda
Example If a student has less mark than the pass mark, he will not be registered
for the term; he will be readmitted or dismissed from the campus.
Source ATVET College rules and regulation
2.5 Forms, documents used in the existing system

The following are the major forms and documents used in the existing system:-
1 Student Application Form: this form is used to facilitate the registration process so as the
student information is going to be captured.
2 Registration Slip: this form help to register in Wolaita Sodo ATVET College students.
13
14
Fig 2.5.2 level one registration form

2.6 Bottlenecks of the existing system
PIECES framework is a check list for identifying problems with an existing Wolaita Sodo
ATVET College. We classify the problem according to PIECES frame work as follows.
2.6.1 Performance:
We can measure the performance of the system from two perspectives
 Throughput: the amount of work a system can do on a specified period of time.

This is not relevant in the existing system because the system is not totally automated.
And it takes longer time to do one specific job.
 Response time: the time a system takes to react to a given input.
This is not also relevant in the existing system because for example a student may
not get reading material at any time
2.6.2 Information
We can see this from two perspectives
15
o Problem with Stored Data
 The existing system is poor in managing the students’ data. Student’s data is
captured redundantly because of poor communication between different work
units.
 There is not accurate data .the data contains errors because the existing system
is not fully automated and it may be subjected to human errors.
o Problem with Outputs
 Irrelevant and redundant information because of the above problem occurred

by the stored data.
 Information that is not accurate because there is a probability to capture wrong

input information so the output is also wrong.
2.6.4 Security and Control

 Data Privacy Regulations and Guidelines: the College does have policies
on client's files, but some of this information may be exposed to unauthorized
people. Example, student’s mark. Hence there is also a problem in control and
security.
2.6.5 Efficiency
 A lot of wastage of time because data is stored redundantly .
2.6.6 Service-
The students cannot get education material whenever they need.
2.8 Alternative options to address problems of the existing system

 Automating the system by developing web based System.
16
2.8.1 Options analysis and the proposed new system
The alternative option that we have listed above is the only option that we can rely on
because it is supposed to address the problem of the existing system. It has also the
following advantages
 Information exchange will be easy and takes less time.

 Can address student requirements.
 There will be higher interaction among systems.
2.9. Requirements of the Proposed System
2.9.1 Functional Requirements

The functional requirements focus on the main functions that the new system will provide. The
functional requirements of the new system include information related to:
 Uploading necessary information about some subject and assignments.

 Showing necessary information about the student like mark
 Allowing download of education materials.
 Giving exam for students.
 Allow students to check their results.
2.9.2. Non-Functional Requirements

These requirements do not directly affect the performance of the system but they are important.
A non-functional requirement relates to the technical aspects our system must fulfill, such as
performance-related and reliability issues.
 Security and Access permissions: - The system must confidentially be controlled from
being accessed by unauthorized students.
 Backup and Recovery: - The system should store a backup database daily the system
may face some errors on the data base server.
17
 Availability: - The system should easily be available at any desired time. If by any
chance the system fails, students will get difficulties on getting course materials and other
information.
 Performance: - The system should be fast in order to access the required information and course
material easily.
 Desiccation forms:-
Chapter Three
System Analysis
18
3.1 Introduction
This chapter describes what the proposed system will looks like and how it carries out its
activities. These include use case diagrams, use case documentation, sequence diagram, activity
diagram, analysis level class diagram (conceptual modeling), user interface prototyping,
supplementary specifications.
1.2System Requirement Specifications (SRS)
3.2.1 Use case diagrams

It is used to describe the functionality of the system from an external point of view. The use case
model is one which is considered as a functional model. It summarizes who uses your application
or system, and what they can do with it. The following diagram depicts the use case model.
e learning
Post News
Upload Reading
Resource
Manage
Department Upload
Assignment
Admin
Manage Course
login
Download Instructo
Assignment r
View Result Use Case
Upload
Assignment
Student
Download Reading
Material
Take Exam
Download
Assignment
3.2.2 Use case Documentation

Table 3.1 Use case documentation of Login
Use case name Login
19
Use case number Use case #1
Actor(s) Student, instructor, administrator
Description Helps to control the system from unauthorized persons to access the
system
Typical course action Actors action: System response:
Step1.The actor access the home Step2. In the home page a login
page. option displayed.
Step3.The actor enters user Step5. The system verifies the

name and password authority.
Step4.The user click login Step6. The system displays the main
button page
Alternate course of action Step7.If the actor enters invalid user name or password, the system
displays error message and goes to step 3.
Pre-condition: The actor must be registered first and the list must be found in the
database
Post-condition: The actor can do anything in the main page with his/her privileges.
Table 3.2 Use case documentation of Take Assignment
Use case name Take Assignment

20
Actor(s) Student
description Helps the student to download Assignments.
Step 1. The student tries to views Step2. The system checks whether
and downloads the available Assignment is uploaded or not.
Assignment.
Step3. The system displays
Step4. The student Downloads the Assignments.
assignments.
Step 5. The system responses suc
download message.
Alternate course of action Step6. If there is no assignment uploaded, the system displays a message
shows the absence of assignment and step 2.
Pre-condition: The student must be registered first and the list must be found in the database
Post-condition: The students take assignment and do and upload it within a given time.
Table 3.3 Use case documentation of Download Reading Resources
Use case name Download Reading Resources
21
Actor(s) Student
Description Helps the student to follow the courses which he/she registered to take, read
all materials which are essential to the course that he/she takes.
Step1. The student wants to Step2. The system displays all reading
download reading materials. materials and videos of lab works.
Step3. The student selects from the Step4. The system validates and
displayed lists, which things to responses with a message with
download and clicks on downloading progress.
“Download” button.
Alternate course of action Step5. If there is problem with downloading, the system displays a message
and asks to try again.
Pre-condition: The student must be registered first and the list must be found in the database
The related instructor has to upload a reading resource.
Post-condition: The student can see the videos if there is any.
Table 3.4 Use case documentation of View Result
22
Use case name View Result
Actor(s) Students
Description Helps the students to view their result.
Step 1. Student wants to view his/her Step2. The system displays the Student
result. page.
Step3. The student selects his or her Step4. The system validates and
privilege and enters User name and displays student page.
password.
Step6. The system displays all his/her
Step5. The student clicks on “View grade.
result” button.
Step7. The student views his/her
grade.
Alternate course of action Step8. If student enters incorrect user name and password, the system displays
the message indicating the invalid information and redirects to step3.
Pre-condition: A student must be the member of Wolaita Sodo ATVET College and he/she
must found in the database.
Post-condition: The students can view their result.
Table 3.5 Use case documentation of Assignment submission
Use case name Assignment submission

Actor(s) Student
23
Description Helps the student to submit assignments and teachers to accept assignment.
Step1. The student enters to the

Step3. The system checks the deadline
assignment submission page. of submission and whether the
assignment is uploaded successfully or
Step2. The student browses and not.
uploads the assignment.
Step4. The system displays a success
message.
Alternate course of action Step5. If there is a problem with uploading the assignment, the system
displays an error message and go to step 2.
Pre-condition: The student must be registered first.

There has to be an assignment given by the instructor.
Table 3.6 Use case documentation of Upload Reading Resource
Use case name Upload Reading Resource

Actor(s) Instructors
24
description Helps the instructor to upload reading materials to the students
Step 1. The instructor tries to Step2. The system displays the
upload reading resource to uploading page to attach files.
students. Step4. The system verifies and
Step3. The instructor browse file displays the message to show the
and clicks on “upload” button. given file is Uploaded.
Alternate course of action Step5. If the reading resource is not uploaded the system shows error
message and redirects to step 3.
Pre-condition: The instructor must be registered first and the list must be found in the
database
Post-condition: The instructor can upload assignment to his students.
Table 3.7 Use case documentation of Give marks for the exams
Use case name Manage Student’s Mark
Actor(s) Instructor
Description Helps the instructor to give marks to student & know who is active in
the course.
Step 1. The instructor wants to Step2. The system displays page

manage the students mark. that contains the student’s answer.
Step3. The instructor checks Step4. The system displays

the answer of the student and message of successfully the mark is
saves to the database. checked and saved to the database.
Alternate course of action Step5. If there is no exam taken, the system displays a message that
shows the absence of an exam taken and redirects to exam page.
Pre-condition: The student must be registered first and the list must be found in the
database
Post-condition: The Instructor can check the student’s answer and give value or mark
to them.
Table 3.8_Use case documentation of Manage Courses
Use case name Manage Courses
25
Administrator
Actor(s)
Helps the Manager to manage the Courses.
Description
Step 1. Manager wants to manage the Step2. The system displays the Home
courses. page.
Step3. The Manager selects his or her

privilege and enters User name and
password. Step4. The system validates and
displays Manager’s page.
Step5. The Manager clicks on “show
courses”. Step6. The system displays all the
courses.
Step7.Manager update course information
and then click on “save “button. Step8. The system validates and
response with a message.
Alternate course of Step9. If the Manager enters incorrect user name and password, the system displays
action the message indicating the invalid information and redirects to step 3.
Pre-condition: The Manager must be the member of WSATVETC and he/she must been in the data
base.
Post-condition: The Manager manages the Courses.
Table 3.9_ Use case documentation of Post News
Use case name Post News
26
Actor(s) Administrator
Description Helps the Administrator to Post Current News.

Step 1. Manager wants to Post Step2. The system displays the

Current News. Home page.
Step3. The Administrator selects

his or her privilege and enters
User name and password. Step4. The system validates and
displays Administrator’s page.
Step5. The Administrator clicks
on “Write News” button. Step6. The system displays page
to write news.
Step7. The Administrator writes
news and clicks on “Post News Step8. The system validates and
“button on the form. response with a message.
Alternate course of action Step9. If the Administrator enters incorrect user name and password,
the system displays the message indicating the invalid information
and redirects to step 3.
Pre-condition: The Administrator must be the member of WSATVETC and he/she

must be registered as Administrator.
Post-condition: The Administrator posts current news.
Table 3.10 Use case documentation of Manage Account
Use case name Manage Account
27

Administrator
Actor(s) Helps to create, delete, and deny user account for users of the system
and sets privilege to them.
description
Step 1. The administrator wants Step2.The system includes login

to update Account of a user page.
Step4. The administrator selects Step 3. The system displays “Main

“Accounts" on main menu menu page”
Step6. The administrator selectsStep5.The system displays

a user, for whom to create “Account management Page”.
account.
Step6. The system verifies validity
Step7.The administrator selects of the student information and
“Create account”. response with success message.
Step8. The administrator fills
user name, password, and Step9. The system determines the
privilege and clicks the create account is valid according toBR-03
button. check account and updates the
account record.
Alternate course of action Step7. If the entered incorrect user name and password, the system
displays an error message and goes to step 3
Step5.If the entered information is not valid the system displays an

error message and goes to step 5.
Pre-condition: The Administrator is an employee in WSATVETC.
Post-condition: The Administrator will update user account.
3.2.3 Sequence Diagram
28
Sequence diagram is a diagram which shows how the system processes operate with other and
in what order they operate. And this diagram shows a message passed in the process.
Home page Login page User page
User
User name,password
user select home page
User
name,password
open()
User
name,password
1. User want to login into the system

2. The system display the login form
3. User enter user name and password
4. System validate user name and password
5. System display home page
Fig. 3.1 Sequence diagram for “Security Login" use case
29
Instructor
Login Home Page Upload Page Data base
Page
Instructor
User name,password
User name,password Validate()

Display()
[User
name,password]
Upload()
Initiate()
Open()
Upload()
Submit()
Save()
[Upload()]
1. The instructor wants to upload reading resource for the student

2. System include login to instructor
3. Instructor selects "uploading “resource
4. System displays the "upload" form
5. Instructor selects the course and uploads reading resource

6. System uploads the resource
Fig. 3.2 Sequence diagram for “Upload reading material" use case
30
Administrator Account
Login Home page Data base
Page Page
AdministratorUser
name,password
User Validate()
name,password
Open()
User
name,password
Account()
Open()
Modify()
Save()
Submit()
Update()
1. Administrator want to manage account

2. The system display login page
3. The Administrator fill user name and password
4. The system verifies and displays “Administrator Page”
5. The Administrator click on “Administrator Account “Button
6. The system display all account on ”Account Page”
7. The Administrator update account and clicks on save button
8. The system verifies and response successfully managed
Fig. 3.3 Sequence diagram for “Manage Account" use case
31
Administrator
Login Syste m page Data Base
Page
Administrator User
name,password
User Validate()
name,password
Display()
User
name,password
Update() Save()
Submit()
Submit()
Update()
1. Administrator want to manage course

5. The manager click on “Manage Course “Button
6. The system display all course on ” Course Page”
7. The Administrator update course information and clicks on save button
8. The system verifies and response successfully managed
Fig. 3.5 Sequence diagram for“Manage Course" use case
32
Login Home page Data base
Student
User
name,password
User Validate()
name,password
Open()
[User
name,password
]
Fill Answer()
Submit()
Success()
1. Student want to take exam

3. The student fill user name and password
4. The system verifies and display “Exam page”
5. The student fill the answer and send
6. The system responses the acceptance of the answer
Fig. 3.6 Sequence diagram for “Take Exam" use case
33
Login Home page Data Base
Student User
name,password
User Validate()
name,password
Open()
[User
name,password
]
Download()
1. Student wants to download Assignment

3. The student fills user name and password
4 .The system checks the availability of the assignment
5. The student downloads the Assignment
Fig. 3.7 Sequence diagram for “Download Assignment" use case
34
Student
User
name,password
User Validate()
name,password
Open()
[User
name,password
]
download()
Browse
Assignment()
Success()
1. Student want to submit Assignment

4. The system verifies and display “Assignment Page”
5. The student upload the assignment
6. The system response success
Fig. 3.8 Sequence diagram for“Submission of Assignment" use case
35
Login Page Home Page Data Base
Student
User name,password
Valid()
User name,password
View Mark
Thank you()
1. Student want to view result

4. The system verifies and displays “Result Page”
5. The student views the result
6. The system responses you viewed your result
Fig. 3.9 Sequence diagram for “View Mark" use case
36
Login Home page Student Page Data Base
Instructor User
name,password
User Validate()
name,password
Display()
[User
name,password
]
Update() Save()
Submit()
Submit()
Success()
[Update()]
1. Instructor want to check student mark

3. The Instructor fill user name and password
4. The system verifies and displays “Instructor Page”
5. The Instructor click on “Student Mark menu “
6. The system display” Student Page “
7. The Instructor updates Student mark
8. The system verifies and response successfully updated
Fig. 3.10 Sequence diagram for Basic course of action “Manage Student Mark" use case
37
Administrator
Page
Administrator User
name,password
User Validate()
name,password
Display()
[User
name,password
]
Post()
PostNews()
Submit()
Submit()
Success()
[PostNews()]
1. Administrator want to post News

5. The Administrator click on “Post News menu “
6. The system display” Post News Page “
7. The Administrator post the News
8. The system verifies and response successfully posted
Fig. 3.11 Sequence diagram for Basic course of action “Post News" use case
38
3.2.4 Activity Diagram
In this phase activity diagram is used for modeling business processes as well as for
describing control flows in software that developed by the team member.
User
User Want to login
Enter
Enter User
name,password
[Enter]
Check
Not Valid
Is valid? reject
Valid
User Page
Exit
Activity diagram for user to login to system
39
Instractor
Instructor Want to
Upload Reading
Material
Enter
Enter User
name,password
Check
Not Valid
Not Valid Is valid?
Valid
Choose file
Upload
Upload
Exit
Activity diagram of Instructor for upload the reading resources for student
40
Student
Student Want to Enter Enter User
Download assignment name,password
[Enter]
Check
Valid Not Valid

Is valid? reject
Downloa
Choose d
Download
Assignment
Exit
Activity Diagram for student to download assignment
41
Student
Student Want to
Submit assignment
Enter User
name,password
[Enter]
Valid Not Valid

Is valid? Reject
Assignment Upload Upload Assignment

page
No
assignment
Reject
submitted?
yes Exit
Upload
Exit
Activity diagram for student “Uploading assignment” to instructors
42
Student
Student Want to View
Result
Enter
Enter User
name,password
Check
Valid Not Valid

Is valid? not valid
Exit
Student Page View Result
Activity Diagram of student to View their mark
43
Instructor
Instructor Want to
Mark Student mark
[Enter]
Enter
Enter User
name,password
Check
Not Valid
Valid Student page
reject Is valid?
Exit Mark Student Mark

mark
Activity diagram of Instructor to manage the student mark
44
Administrator
Administrator Want to Enter Enter User
Manage Course name,password
[Enter]
Check
Valid
Manager's Not Valid

Is valid? reject
page
Update
Update Update Course
Exit
Activity diagram of manager to manage course of the department

Administrator
Administrator Enter Enter User
Want to Manage name,password
Department [Enter]
Check
Valid
Manager's Not Valid

Is valid? not valid
page
Update Update [Update]

Update
Department
Check
No Update Exit
Valid? Department
Yes
Exit
Update
Department
Activity diagram of manager to manage department
45
Administrator
Administrator Want Enter Enter User
to Post News name,password
[Enter]
Check
Manager's Valid Not Valid

Is valid? reject
page
Write
Post
Write News Exit
Post
Activity diagram for post news Activity
3.2.5 Analysis level class diagram (conceptual modeling)
We are use Conceptual modeling in order to describe the structure of the system in terms of the objects,
classes, attributes, operations and their associations.
has take
manage
1 * 1 1
* Student
Instructor Administrator
InstructorID<<pk>> Department AdminId<<pk>> 1 Post
InstructorName DepartmentId StudentId<<pk>> AdminName
* has 1
Department DepartmentName StudentName
Department *
Upload Reading Resource() Assign Instructor ManageCourse()
1 MangeDepartment() News
1 Upload Assignment() Take Course()
1 give ManageAccount() NewsName
Upload Exam() NewsContaint
1 1 1 PostNews()
1 give
1 1 1 UpdateNews()
*
manage
ReadingResource Assignment can Take
give *
AssignmentNum manage
ResourceNum<<pk>> Exam
<<pk>> *
ResourseName AssignmentName * * *
Course *
ResourseUpload() AssignmentDate ExamNum<<pk>>
ResourseDownload() Account
UploadAssignment CourseCod<<pk>> UserId<<pk>>
* * () CourseName PrepareExam()
DownloadAssignment() UserName
CreditHour UpdateExam
()
SearchStudent() CreatAccount()
AddStudent()
*
give
Fig. 3.2.5 Conceptual modeling
46
3.2.6 User Interface Prototyping
Home Page
Administrtor Instructor Student
Login
Login
Login
Download
Manage Account Upload
Submit Assignment
Manage Department Prepare Quiz
View Question
Manage Course
View Mark
Take Exam
Post News
Manage mark
Fig. User interface prototype
47
3.2.7 Supplementary Specifications
For the supplementary specification the team member identified some business rule that
defines or constrains some aspect of the business for the proposed system. It is intended to assert
business structure or to control or influence the behavior of the business.
Table 3.17 Supplementary specification (business rule)
Identifier Rule Description Source

RULE I Account checking The system must check an account before College policy
and after the administrator creates new and
account delete or grant some privilege for regulation.
the user.
RULE II Educational course 1. The original copies of the past College rule
educational course must be present and
to the College. regulation.
2. The documents must be present to
the registrar’s office before the
deadline set.
RULE III No duplicate course in the There should not be more than one course College rule
College with the same Credit Hour ,Course and
Number and Course Title regulation.
RULE IV Validate the form When user of the system fill details in the Rule and
form the system validate the form regulation
RULE V Determine eligibility to Users of the system should have a unique Rule and
enter to the system username and password to enter to the regulation
system.
RULE VI Eligibility to assign grade The instructor must be given privilege to College policy
assign a result to his students and regulation
48
Chapter Four
Design
4. 1 Introduction
This project is designed in a manner that solves the problems of Wolaita Sodo ATVET
by minimizing the work load of the existing system and employee. The team member are design
the process of the art of defining the architecture, modules, interfaces, and data for a system to
satisfy specified requirements. It provides more efficient, reliable and time saving system. In this
project design the team members are tried to show:-
 How the project is designed

 What are tasks done under the whole project
Generally, the project of the team member is designed by addressing all of the above
criteria of project design. It is designed to simplify functions of the manual system and it is
capable of doing large amount of works in short period of time with more accuracy and
reliability. Generally this project design describes how the project is designed, what tasks done
under this project.
The objectives of designing are to model a system with high quality. Implementing of a
high quality system depends on the nature of design created by the designer. If one wants to
make changes to the system after it has been put in to operation depends on the quality of the
system design. So if system is designed perfectly, it will be easy to make changes to it.
4.2 Class type Architecture

The class type Architecture is the architecture used to distribute the subsystem decomposition
in terms of its responsibilities, dependencies ,mapping to hardware and major policy decisions
such as control flow ,access control & data storage.
49
The description of class type architecture
Interface layer
This layer binds access to the logic of our system. There are two categories of interface
classes .These are user interface(UI) classes that provide people access to our system and system
interface(SI) classes that provide access to external systems to our system.
Process Layer
The process layer implements business logic that involves collaborating with several domain
classes or even other process classes. The business logic is the key elements that determine the
workflow in the system. The process layer works in collaboration with other layers to do its
activities.
Data Access Layer: The data access layer provides a simple API for accessing and manipulating
data. The components in this layer abstract the semantics of the underlying data access
technology thus allowing the business layer to focus on business logic. Each component typically
provides methods to perform Create, Read, Update, and Delete (CRUD) operations for a specific
business entity.
Data Stores: Enterprise applications store their data in one or more data stores.
System layer: System classes provide operating system and communication software.
Generally, system classes provide operating-system-specific functionality for our applications, isolating
our software from the operating system (OS) by wrapping OS-specific features, increasing the portability
of our application. For instance in this project, we use MS –WINDOWS 7.
50
Interface
(User interface, system interface)
Process
(Application, controller)
System
Domain (Infrastructure,
(Business) platform)
Persistence
(Data)
Data
source
Fig. 4.1 Class type architecture diagram

sssssss(Sourc
es)
4.2.1 Business classes
 Instructor
 Upload reading resource and assignment
 Prepare examination
 Inputs students grade
51
8
89
 Forward answer
Administrator
 Post news
 Manage account
 Register student
 Manage Users
 Student
 Take course
 Take Exam
 Take assignment
 Download reading resource and assignment
 View grade
 Submit assignment
4.2.2 User interface layer

 Menu
 Home page
 User interface
 Instructor page
 Student page
 Admin page
4.2.3 Persistent layer

 Student data base
 Administrator data base
 Instructors data base
4.2.4 System layer

 Login page
52
 User name
 Pass word
4.3 Class Modeling
The static structure of the system is built in the class modeling part. It indicates the internal
structure and relationship of things such as classes and types. Classes are show as boxes, the top one
indicates the name of the class, the middle one lists the attributes of the class, and the third one lists the
process of the activity in this class.
has
take
manage
* 1 1
1
Student
Instructor * Administrator
Department
InstructorID<<pk>> AdminId<<pk>> 1 Post
StudentId<<pk>>
InstructorName * has 1 DepartmentId AdminName
Department DepartmentName StudentName
Department *
Upload Reading Resource() ManageCourse()
Assign Instructor News
1 Upload Assignment() 1 Take Course() MangeDepartment()
1 give ManageAccount() NewsName
Upload Exam()
PostNews() NewsContaint
1 1 1
1 give
1 1 1 UpdateNews()
*
manage
ReadingResource Assignment can Take
give *
manage
ResourceNum<<pk>> AssignmentNum<<pk>> Exam
ResourseName * * *
AssignmentName *
Course
ResourseUpload() AssignmentDate * ExamNum<<pk>>
ResourseDownload() Account
UploadAssignment() CourseCod<<pk>>
* UserId<<pk>>
* DownloadAssignment() CourseName PrepareExam()
UserName
CreditHour UpdateExam()
SearchStudent() CreatAccount()
AddStudent()
*
give
53
Fig .4.2 class modeling
54
4.4 .State chart modeling

State chart used to show the dynamic behavior of a single class for the proposed system.
The following are some of the state chart diagrams.
user name
&password
session exist
login security
state chart
login exit
Fig .4.3 State Chart diagram for loin
user name &

password
check
department department Error

management notification
state chart
success
Exit
update Exit
department info
Fig .4.4 State Chart diagram to Manage Department
55
user name &

password
check
choose
required data
upload reading upload
resource check
state chart existence of
resource
exist
upload reading
resource
Fig .4.5 State Chart diagram to Upload Reading Resource
Post News user name &

password
check()
post News Not post Not posted

state chart News notification
post exit()
News posted
Exit
Fig .4.6 State Chart diagram to post news
56
user name
&password
check()
account error
notification
update
account
state chart
success
update
account
Fig .4.7 State Chart diagram to Update Account
4.5. Collaboration modeling
A collaboration diagram shows the objects and relationships involved in an interaction,

and the sequence of messages exchanged among the objects during the interaction. The
collaboration diagram illustrates messages being sent between classes and objects (instances) in
the project. A diagram is created for each system operation that relates to the current
development cycle (iteration).
1:User want to login

:User :Login:Login
4:validate
5:<<Create>>
:Authenticate Login:Login
Fig .4.8 Collaboration Modeling for user to login to system
57
1:User want to download reading

resource Download RR 2:<<User>>
:Student
:Download RR Login:Login
<<Unspecified>>
<<Unspecified>>
5:d
o wn
4:g loa
etd d file >>
o wn () eate
loa < Cr
df
ile 3:<
()
Download RR
:Download RR
<<Unspecified>>
Fig .4.9 Collaboration Modeling for Download reading resource
1:User want to download assignment 2:<<User>>

:Student Download assignment
:Download assignment Login:Login
<<Unspecified>>
<<Unspecified>>
5:d
ow
nlo
4:g
>
ad
te>
etd
as
rea
ow
sig
C
:<<
nm
nlo
3
en
ad
t()
as
sig
nm
en
Download assignment
t()
:Download assignment
<<Unspecified>>
Fig .4.10 Collaboration Modeling for Download assignment
58
1:User want to upload reading

resource Upload RR 2:<<User>>
:Instractor
:Upload RR Login:Login
<<Unspecified>>
<<Unspecified>>
5:u
plo
ad
4:s file >>
ele ()
eate
ct
file < Cr
() 3:<
Upload RR
:Upload RR
<<Unspecified>>
Fig .4.11 Collaboration Modeling for Upload reading resource
Post news
:Post news
3:<
<C
st() re
etpo ate
4:g >>
s()
stnew
o
5:p
1:User want post news 2: <<User>>

:Adminstrator Post news
<<Unspecified>> Login:Login
:Post news
Fig .4.12 Collaboration Modeling for Post news
59
4.6 .Component Modeling
The component model is illustrates the software components that will be used to build the
system. These may be built up from the class model and written from scratch for the new system,
or may be brought from other objects. Components are high level aggregation of smaller
software pieces, and provide a “black box” building block approach to software construction.
Data Access
<<Application>>
Admin Administrator
Administrator
Managment
Data
<<Application>> Access
Student Account Account Encryption
Management
Data Access Security
<<Application>>
<<>infrastructure>
Course Student Student
Management
Access control
Data Access
<<Application>> Presistance
Result Course
Course <<infrastructure>>
Management
Data Access
Presistance
<<Application>> Result
News Result
Management Data Access DB
Data Base
<<Application>>
Assignment News News
Management E_laerning DB
Data Access <<DataBase>>
<<Application>>
Reading Resource Assignment Assignment
Management
Data Access
<<Application>>
Reading
Exam RR Resourse
Management
Data Access
<<Application>> Exam Exam

Instructor
Management
Data Access
Instructor
Instructor
Fig .4.13 Component modeling
60
4.7 Deployment Modeling
In this project the deployment diagram (DPD) shows a configuration of run-time processing
elements and the components and objects that run on them. You can use a deployment diagram,
for example, to show the configuration and routing of components and objects in a distributed
system. A deployment diagram represents all or part of process architecture of a system. It
provides a detailed model of the way components will be deployed across the system
infrastructure.
:Application Server
Account
Exam
:Database Server
Course
Result presistance
:Client Browsre <<infrastractur
e>>
News
DB
E_learning DB
TCP Assignment
<<infrastructure
>>
Reading
Resourse
Fig .4.14 Deployment diagram
4.8. Persistence modeling

Persistence modeling is used to communicate with the design of the data base, the
user and other developers. This modeling used to depict the design of the database. The
persistent classes are used to store most important and permanent information of the system. In
persistent modeling the team member will perform the following activities.
Persistent modeling is used to depict the design of data base. Identifying keys
 Identifying entities
 The methods of classes
 Data type and initial sizes.
61
has
1 1
Instructor Department Administrator
inst_id:int News Login
inst f_name:char 1 dep_name:string username:string login_id:int
inst l_name:char has dep_id:int news_id:int
* password:int 1 post username:char
gender:char title:string
status:string password:string
age:int * news:string
dep_id:string Update() post_news() Login()
manage_account Update_news() logout()
username:string *
password:string give () Post-news() 1
1
status:string 1
has 1
*
Upload_RR() has Student
Manage_mark() * take 1
1 stud_id:int
1 * f_name:char
Course l_name:char
Reading Resource
cour_id:int Exam dept_id:int
* Assignment rr_id:int cour_name:string gender:char
give ass_id:int
rr_course:char cour_code:string age:int
title:char exam_id:int
rr_dep:char creadit_hr:int username:string
dept:char title:string
rr_title batch_no:int password:string
entry_date:int course_code:string
description:char dep_no:int status:string_
score:char Discription:string
Upload() Add() Upload_Asigmt()
Upload() Drop() Modify() Upload_exam
Download()
Update() Prepare() Download_RR()
* 1
1 * 1 *
has can
Fig .4.15 Persistence Modeling
62
4.9 User Interface design
Fig 4. 16 User Interface Model for home page
63
Fig 4. 17 User Interface Model for login
Fig 4.19 User Interface Instructors Upload Assignment For Student
64
Chapter Five
Implementation and Testing
5.1. Introduction
The purpose of this part of the document is to provide the highlight of the issues dealt with the
implementation phase.
5.2. Coding
This phase, the coding 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.
 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 going 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,
document analysis 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: each unit of the system is tested by the group members
65
 Integration testing: the unit parts are integrated together and then tested by the
members.
 System testing: after all the testing’s performed, the system will be tested by
professionals.
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 Microsoft SQL server 2005 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. Then anyone can access the site.
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 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. Installation
Installation process of this project makes the current system to be replaced by the new system. This
includes conversion existing data, software, documentation, and working procedure to this consistent with
the new system.
66
5.8. Start-up strategy
System conversion
System conversion involves migrating from the existing system to the proposed system
Direct conversion: - This involves directly dropping the existing system and finding the
solution for it.
Parallel conversion:-Involves running the existing system and the new system hand- in-hand
for some time.
Pilot conversion: - This involves deploying small component of the system, testing them to
the user satisfaction, and incorporating them to the system.
The project team used the Pilot conversion technique for conversion. We reduced the
scope and decided to automate the distance learning of AMU by providing web based alternative
to it. But during in the requirement gathering phase we gather different problems from academic
institute of distances learning offices so if our system is implemented in AMU successfully, it
will implement in other academic institute also because the problems are most likely the same.
Sample code
///code for the home page
<div id="menubar">
<ul id="menu">
<li class="current"><a href="index.html">Home</a></li>
<li><a href="ourwork.html">About Us</a></li>
<li><a href="contact.html">Contact Us</a></li>
<li><a href="projects.php">Admin</a></li>
<li><a href="inst.php">Instractor</a></li>
67
<li><a href="stud.php">Student</a></li>
<li><a href="index.html">Logout</a></li>
</ul>
</ul></li>
</ul>
</div>
</div>
<div id="site_content">
<div class="sidebar_container">
<div class="sidebar">
<div class="sidebar_item">
<h2>Elearning Website</h2>
<p>Welcome to our elearning web site. Please have a look around, any feedback is
much appreciated.</p>
</div>
</div>
68
<img src="../images/elearning-stock-photos.jpg" />
<h2>Mission Of ATVET College </h2>
<p>In every year the college conducts a research and innovate new seeds for
farmers.The students involve in research gains practical knowledge.</p>
<h2>Contact</h2>
<p>Phone: +251987567891</p>
<p>Email: satvet@yahoo.com</a></p>
69
</div>
<div class="slideshow">
<ul class="slideshow">
<li class="show"><img width="680" height="250" src="imags/elearninghome.jpg"

alt=""Enter your caption here"" /></li>
<li><img width="680" height="250" src="../images/download.jpg" alt=""Enter

your caption here"" /></li></li>
</ul>
</div>
<div id="content">
<div class="content_item">
/////sample code for user to login to system
<?php
$submit=0;
$loginid=$_POST['firstname'];
$pass=$_POST['password'];
extract($_POST);
70
if(isset($submit))
include("../database.php");
$rs=mysql_query("select * from mst_admin where loginid='$loginid' and

pass='$pass'",$cn) or die(mysql_error());
if(mysql_num_rows($rs)<1)
echo "<BR><BR><BR><BR><div class=head1> Invalid User Name or

Password<div>";
exit;
$_SESSION['alogin']="true";
else if(!isset($_SESSION[alogin]))
echo "<BR><BR><BR><BR><div class=head1> Your are not logged in<br> Please

<a href=index.php>Login</a><div>";
exit;
?>
71
Chapter six
Recommendation and Conclusion
6.1 Conclusion
This new project is aimed to give the opportunity for Wolaita Sodo ATEVET College and
student to use this technology. The developed website has a more advantage for the society,
organization and the member of the College.
E-learning of Wolaita Sodo ATEVET College website gives the chance to people to learn
from anywhere at every time through the use of internet and other additional technologies.
Through this project the student who is registered for one specific department can take the course
and take the available exam by downloading the reading resources which is uploaded by the
course teacher. Depend up on the exam answer for the course/subject the teacher can give the
right result. The administrator can post the current news for the concerned instructors and
student.
6.2. Recommendations
The team member has a recommendation towards the project for modification of some
features to make the system perfect and more efficient. So anyone who have the intension to
update, change or modify this project to contact us. The features recommended to add are:-
 Voice chatting
 Video chatting
 Add/ Drop of course for student
 Chatting through networking
In addition to these, any user to use this system, he/ she have to know some knowledge
how to use this system and any concerning organ have to connect internet for the use of system.
72
Reference
https://www.trainingindustry.com/articles/.
http://www.siriusformation.com/e_learning
http://www.about.com/english/e_learning
http://www.webogedia.com/TERM/e_learning.html
73
Title: E-Learning System for Wolaita Sodo ATVET College

Group members ID No
1. Gemeda Gebre NSC/R/505/04
2. Demelash Somaw NSC/R/354/04
3. Lidet eyob NSC/R/ 702 /04
4. Emnet zewudu NSC/R/416/04
5.Haimanot Yirga NCS/R/579/04
Submitted to the Department of Computer Science and IT, college of Natural and
Computational Science, wolita soddo University, in partial fulfillment for the
requirement of the Degree of Bachelor Science in Information Technology
Wolaita Sodo University
Department of CSIT
Approval: Signature: Date:
Advisor: _________________ ________ ________
Examiner 1:_______________ ________ ________
Examiner 2:_______________ ________ ________
74
75

E-Learning System

Uploaded by

Copyright:

Available Formats

E-Learning System

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

E-Learning System

Uploaded by

Copyright:

Available Formats

E_LEARNING SYSTEM FOR SODO ATVET COLLEGE 2015

Wolaita Sodo University

A senior project Submitted to the Department of Computer Science and IT,

Advisor: Habtamu F. Wolaita Sodo, Ethiopia

NNP=Nation Nationality of People

ILT=Instructor Led Training.

SQL=Structure Query Language.

HTML=Hyper Text Markup Language.

DHTML=Dynamic Hyper Text Markup Language.

XML=Extensible Markup Language.

E-Learning (Electronic learning) is an umbrella term that describes learning done at a

1.3. Statement of the problem

 Instructor led Training(ILT) which is traditional method

The students also face many problems among which

 There is no sufficient educational resources regarding to the courses in hard copy

1.4. Team composition

Project E-Learning system for Wolaita Sodo ATVET Responsibility

1.5.1 General objective

the teaching learning process.

1.5.2 Specific objective

1.6. Scope of the project

1.7.1 Data source

1.7.2 Fact finding techniques

 Document analysis:- reading different written documents

1.7.3 design approach.

1.9. Required resource with cost

No Item type Quantity Cost

1 Paper 1desta 80 birr

Total 11 970 birr

1.10. Limitation of the project

1.11. Task and schedule

1.12. Risk and assumption

o The system working environment can fail.

1.14. Benefit of the project

Description of the Existing System

2.1 Introduction of the Existing System

2.2 Players in the existing system

The main roles of the student in the system are:-

 Take the available exam,

 Submit assignment, and See their result.

 Course material distribution

 Registrations slip form.

 Registrations slip and ID.

 Course name its credit hour.

 Course number or course code

Identifier BUSINESS RULE -1

Name Result computing rule

Description Result is computed on the basis of mark.

Level, in each level the student take coc

Source ATVET College rules and regulation

Related rules ATVET College rules and regulation.

Identifier BUSINESS RULE-2

Name Requirement for registration

Attachment letter and medical certificate bring from their wereda

Source ATVET College rules and regulation

2.5 Forms, documents used in the existing system

Fig 2.5.2 level one registration form

We can measure the performance of the system from two perspectives

 Throughput: the amount of work a system can do on a specified period of time.

o Problem with Outputs