E-Learning University Project 2

COLLEGE OF COMPUTING AND
INFORMATICS
DEPARTMENT OFINFORMATION TECHENOLOGY
OOSAD PROJECT
TITLE: E-LEARNIG SYSTEM

PREPARED BY:
Name Id NO
1. Dinku Boru ……………………………………….360/08
2. Eden Yirga……….............................................362/08
3. Kalid Said……………………………….…….….….382/08
4. Mohammed Timam…………………….……..…1546/07
5. SimboSileshi…………………………………...……402/08
HU E-LEARNING SYSTEM PROJECT Page 1

Submitted to: Mr. Abdulaziz M.
Table of Contents
UNITE ONE...................................................................................................................................................2
1. INTRODUCTION...................................................................................................................................2
1.1Background.........................................................................................................................................2
1.2 Statement of the Problem.................................................................................................................2
1.3 Objective............................................................................................................................................3
1.3.1 General Objective.......................................................................................................................3
1.3.1 Specific Objective........................................................................................................................3
1.4 Methodology.....................................................................................................................................3
1.5 Feasibility study.................................................................................................................................3
1.6 Project Scope and limitation..............................................................................................................4
1.7 Significance of the project.................................................................................................................5
UNITE TWO..................................................................................................................................................5
2.1 Existing system..................................................................................................................................5
2.1.1 Existing system description.........................................................................................................5
2.1.1 Business Rule..............................................................................................................................6
2.2 New system.......................................................................................................................................6
2.2.1 Non Functional Requirements and constraints...........................................................................6
2.2.2 Functional Requirement.............................................................................................................7
2.2.3 Use case Diagram........................................................................................................................7
2.2.4Use case documentation.............................................................................................................9
2.2.5 Sequence diagram....................................................................................................................23
2.2.6 Activity diagram........................................................................................................................39
2.2.7 Class diagram............................................................................................................................55

UNITE ONE
1. INTRODUCTION
1.1Background
Haramaya University was established through a series of transformations since
its establishment as a higher learning institution. The agreement signed between the Imperial
Ethiopian Government and the Government of the United States of America on May 15, 1952
laid the foundations for the establishment of Jimma Agricultural and Technical School and the
Imperial College of Agricultural and Mechanical. In addition to this information ICT was
established in 2003 for the purpose of developing electronic learning and to distribute
computerized system in the university.
Until 1963, the college was virtually dependent on Oklahoma State University, both
administratively and academically; however, after 1966, when the first Ethiopian dean was
appointed, the role of Americans was limited to advisory and technical support. The College
became a chartered member of Addis Ababa University (the Haile Selassie I University),
following the contractual termination of Oklahoma State University in 1968.
1.2 Statement of the Problem

 Lack of data storage
 Lack of data retrieval
 Losing of time
 Wastage of stationary material
 Student lose a lot of money for hard copy
 Overburden work for the departments during providing the service to the students.
 Students don’t have the opportunity to get up to date information on time.
 All the topics covered in the class will not be thought if the student miss the class
 Proposed system
 All the largest amounts of data are store on the database.
 Students get any early data by searching from online.
 Students submit assignment, project and others through online so it is punctual.
 Access any information from online which is related with learning and teaching
process so no need hard copy.
 Departments easy to provide the service to students by upload to online.
 Make learning available anytime and anywhere by access from online.

1.3 Objective
1.3.1 General Objective
The general objective of this project is to develop web based E- learning system for Haramaya
University.
1.3.1 Specific Objective

To achieve the general objective we use the following specific objectives:
 To study the different characteristics of the E-learning system process.

 To make learning available anytime, anywhere
 To Study and analyze the existing system.
 Identifying the problem under the existing system
1.4 Methodology
To accomplish this project the system requirement will follow methods, tools, models and
development of software life cycle techniques.
Requirement Gathering method: The methods we used to gathering data in this project are by
interview of students and employee.
Requirement modeling: In developing this system we follow an object oriented analysis

method. Because to develop the system which has potential to produce safer, more reliable
and maintainable code.
1.5 Feasibility study

Economic Feasibility
To determine the cost benefit of our project, the team has done cost benefit analysis. In cost benefit
analysis we have identified tangible and intangible benefit .After cost benefit analysis the project team is
agreed up on that the project is economically feasible.
Tangible benefit:-Benefits that are easily quantified.
Intangible benefit:-Unquantifiable benefits

Technical feasibility
Since the proposed system doesn’t require much technical expertise and can be integrated with other
company information systems it is technically feasible. Specific technical solution and the availability of
technical resources are measured by technical visibility. .
Therefore, the university has enough capability to be easily applied the proposed system and the
technology is able to handle new report and forms required of the new system. Because of this the
project is technically feasible.
Time feasibility
We try to make this project timely feasible by working with relationship and cooperatively working of
the developing team.
1.6 Project Scope and limitation

Project Scope
Scope in
 Create account
 Add department
 Post class schedule
 Post exam schedule
 Generate report
 Login
 Logout
 Add exercise
 Upload material
 View class schedule
 View exam schedule
 Download material
 Upload grade
 Take exercise
 View grade
 Add course
 Scope out
 Register

Limitation
 A person who has no user name and password cannot use this system
 If there is no connection impossible to use the system
 For a person has eye problem may difficulty to access because too much time spent in front of a
computer screen may be harmful.
1.7 Significance of the project

 Enables students to become thinkers/learners/risk takers in a sheltered environment.
 Learn not to rely on the teacher be accountable themselves and become independent.
 Broadens the horizons of many students as it exposes students to the world outside
their city or country town.
 Allows a computer and mobile learning environment – anywhere, anytime.
 Inspires students to seek more from school.
 Gets kids to go to school.
UNITE TWO
2.1 Existing system
2.1.1 Existing system description

 Coordinator gives the application form for students and hour submission forms for
instructors.
 Coordinator verifies application form and supporting document.
 Coordinator assigns the instructor for student and gives payment for them and assigns
the courses to instructors.
 Instructors give course for students and the students take the courses.
 Students learn from hard copy by going to the class every day and do exam,
assignment and any other job
2.1.1 Business Rule

The following rules are identified in the current system of Haramaya University.
 Every student and Instructor must register in the system at beginning of each year.

 User password and username are given by the administrator for instructors and student of.
 Students and instructors are if out of the member cannot be access the
 E-learning system.
 If students or instructors are forgot password and username they have to report for the
administrator.
 If students cannot access materials they have to report for the teacher.
 In order to secure the E-learning system all members of the e-learning system must be needed
username and password.
2.2 New system
2.2.1 Non Functional Requirements and constraints

Non Functional Requirements
 Economic: This E-learning system reduces cost and increase profit by reducing the
hard copy of materials.
 Security: Our E-learning system has a user account and password to login into the
system for administrating where student and instructors cannot access another user.
 Efficiency: The E-learning system is very fast and has capability of high data.
 Usability: The E-learning system will be easy to learn, operate and navigate using clear
word.
 Reliability: This E-learning notifies the user if there an incorrect input to the system.
 Performance: The E-learning system must have a short response time that triggers on
a press of a single button.
Constraints
 Resource constraint: There is lack human skill power during the development this project and
May there is lack of equipment.
 Time constraints: There was shortage of time in doing the project because we are student and
as such we learn, so time could not use properly as the reason of midterms and assignments.

2.2.2 Functional Requirement
 Upload resource: the Instructor upload the learning resources and other necessary
documents to the system
 Login: The all actors can interact with system through login.
 View schedule: the student and instructor view schedule posted by administrator.
 Download resource: the Student download resources from database.
 Add exercise: the instructor adds activities for students.
 Create account: Administrator creating account for user to login to the system.
 Add course: the process of add course.
 Add department: This is describes the process of add Department.
 Take exercise: the student take the exercise and submit it.
 Upload grade: it is allows the Instructor to upload the student grade
 Logout: it is the process of logout from the system.
2.2.3 Use case Diagram
Actors
 Administrator
 Instructor
 Student
 department
Use case
 Create account
 Add department
 Post class schedule
 Post exam schedule
 Login
 Logout
 Add exercise
 Upload material
 View class schedule
 View exam schedule
 Download material
 Upload grade
 Take exercise

 View grade
 Add course

2.2.4Use case documentation
Use case description for create account
Use case name Create account

Actor Administrator
Description Administrator creating account for user to login to the system.
Pre-condition Prepare password
main flow of event Actor action System response
1. The Administrator click create account 2. The system displays

button on home page. create account page.
3.The administrator enters information 5. The system
4. Click create button. validates the create
account information on
theaccounttable in the
database.
Alternative flow of event 5.1. If the insert information is mismatch, show error message.
Post-condition Account will be created.

Use case description for log in
Use case name: Login
Actor: Administrator, instructor and student
Description This use case allows the Administrator, instructor and student to log in to the system
Pre-condition: The users have password
main flow of events Actor action System response
1. User clicks login button on homepage. 2. The system displays the

login page.
5. The system validates

3. User enters password and name.
the login information
4. Click login button. against theaccounttable in
the database.
Alternative events: 5.1: if the user name and password is not valid, show error message.
Post-condition: The actors logged in to the system and select tasks.

Use case description for Post class schedule
Use case Code: Post class schedule
Actor: Administrator.
Description This use case describes the process of uploading class schedule for
student and instructor
Pre-condition Administrator prepare schedule
Administrator click post class schedule 2. The system displays post

button on home page. schedule page.
3. Administrator insert schedule. 5. The system notifies

schedule will record on the
4. Click on ok.
post table in database.
Post condition User can view Uploaded class schedule.

Use case description for Add department
Use case Add Department

Name:
Actor: Administrator.
Description This use case describes the process of add Department information.
Pre-condition The system must verify the user to add the content.
main flow of Actor action System response

event
1. The administrator click on add department on 2. The system displays add
home page. department page.
3. Administrator fill information 5. Add will record on the add

table in database.
4. Click on ok button.
Post condition Admin can view added department.

Use case description for Post exam schedule
Use case Code: Post exam schedule
Actor: Administrator
Description This use case describes the process of uploading exam schedule for student and
instructor.
Pre-condition The administrator prepare exam schedule
Main flow of event Actor action System response
1. Administrator click on post exam schedule 2. The system display form of

button on home page. exam schedule on post page.
3. Administrator Wright exam schedule on 5. Post exam will record on the

the displayed form. post table in database.
4. Then click post button
Post condition user can view Uploaded exam schedule

Use case description for upload material
Use case name: Upload Material
Actor: Instructor
Description This use case allows the Instructor to upload the learning resources and
other necessary documents to the system
Pre-condition: The instructor should have to prepare resources to be uploaded.
1. Instructor clicks the Upload resources button 2. The system displays the
on home page. Upload page.
3. The Instructor fill name of course, course 5. The system record

code and selects the documents to be upload resources on
uploaded. upload table in database.
4. Then click on upload.
Alternative event 5.1. If the information not correct; the system will display an error message.
Post condition The document will be uploaded on the data base.

Use case description for Add exercise
Use case name: Add exercise
Actor: Instructor
Description This use case is used for the instructor to add activities.
Pre-condition The instructor should have to prepare the exercise that he wants to add.
Actor action System response
main flow of 1. The Instructor click the add exercise button on home page. 2. The system displays the
event add exercise page.
3. The instructor adds the activities.
5. The system notifies the
4. Then click ok button.
exercise successfully added
on add table in database.
Post condition The exercise will be added.

Use case description for upload grade
Use case name: Upload grade
Actor: Instructor
Description This use case allows the Instructor to upload the student grade
Pre-condition: The instructor should have to prepare grade to be uploaded.
1. Instructor clicks the Upload grade button on 2. The system displays the Upload
home page. grade page.
3. The Instructor fill grade of student. 5. The upload grade store on

upload table in database.
4. Then click on upload button.
Post condition The grade will be uploaded on the data base.

Use case description for view class schedule
Use case name: View class schedule
Actor: Student ,instructor
Description This use case is help for the student/instructor to view schedule posted by
administrator
Pre-condition The users have to be valid user, they have to valid account.
Student/instructor clicks on view class schedule button 2. The system displays

on home page. schedule from post table on
view schedule page.
3. Then user views the schedule.
Post condition Student and instructor view posted class schedule.

Use case description for view exam schedule
Use case View exam schedule

name:
Actor: Student ,instructor
Description Used to view exam post by administrator
Pre-condition The Student and instructor have to be valid user, they have to valid account

event
Student/instructor clicks on view exam schedule button 2. The system displays schedule
on home page. from post table on view exam
page.
3. End use case.
Post condition Student and instructor view posted exam schedule.

Use case description for download material
Use case Download resource

name:
Actor: Student
Description This use case allows the Student to download resources.
Pre-condition The Student have to be valid user, they have to valid account.

event
1. The Student click download button on home 2. The system displays course
page. code form on search engine
page.
3. The Student inserts the course code he/she
wants to download. 5. The system searches and
display the resource from
4. Then click ok button.
upload table on download page.
6. Click download button.
7. notifies complete message
Alternative 5.1: If the insert code is incorrect, error message will displayed.
event
Post condition The Student downloads the document he needs.

Use case description for Take exercise
Use case Take exercise

name:
Actor: Student
Description This use case is help for the students to take the exercise and submit it.
Pre-condition The Student have to be valid user, they have to valid account.

event
1. The student click on take exercise button on home 2. The system displays the search
page. engine page.
3. The student insert name of course. 5. The system display exercise

from add table on exercise page.
4. Then click on ok button.
8. System notifies as the answer
6. The student answers the question.
store on answer table in
7. Then click submit button. database.
Post condition The student took the exercise.

Use case description for View grade
Use case name: view grade
Actor: student
Description Used to view grade of student.
Pre-condition: The Student have to be valid user, they have to valid account.
1. The user click grade-report button. 2. Web displays the grade

report page.
3. The student fills UID on the form.
5. Displays the uploaded grade
4. Then click on the ok button.
report from upload table on
6. The student views the report grade. view grade page.
Alternative event 5.1. If filled UID is incorrect; the system will display an error message.
Post condition The grade is displayed for the user.

Use case description for Add course
Use case Add course

Name:
Actor: Department
Description This use case describes the process of add course.
Pre-condition The department has information about course.

event
1. The administrator click on add course on home 2. The system displays add
page. course page.
3. Administrator fill information 5. Add will record on the add

table in database.
4. Click on ok button.
6. Use case ends.
Post condition Course is added.

Use case description for logout
Use case name Logout
Actor Administrator, Instructor and Student
Description used to logout from the system
Pre-condition the actors do some activity in the system
Main flow of event actor action system response
Users click on logout button. 2. The system display login page
3. Then exit the window.
Post condition The actor logout from the system.

2.2.5 Sequence diagram
Sequence diagram for creating account
Create account
create account
Administrator Home page account table
page
Click create
Account ()
Display ()
Enter information
Click ok Verify info
<<Create>>
Success

Sequence diagram for login
Login
Administrator Home page Login page Account table
Click login ()
Display ()
Enter password
And username
Click ok
Check info
Success

Sequence diagram for add department
Add department
add department
Administrator Home page add table
page
Click add
Department ()
Display ()
Insert information
<<Create>>
Success

Sequence diagram for post exam schedule
Post exam
Schedule
post exam
Administrator home page post table
schedule page
Click add
Department ()
Display ()
Insert information
Click ok
Post
Success

Sequence diagram for post class schedule
Post class
Schedule
post class
Administrator home page post table
schedule page
Click post class

Schedule ()
Display ()
Insert information
Click ok
Post
Success

Sequence diagram for upload material
Upload material
Instructor Home page Upload page Upload table
Click upload
Material ()
Display ()
Insert information
Click ok
Upload
Success

Sequence diagram for upload grade
Upload grade
upload grade
instructor home page upload table
page
Click upload
Grade ()
Display ()
Insert information
Click ok
Upload
Success

Sequence diagram for add exercise
Add exercise
Add exercise
Instructor Home page Add table
Page
Click add
Exercise ()
Display ()
Insert information
Click ok
Add
Success

Sequence diagram for view exam schedule
View exam
Schedule
Instructor and View exam

Home page Post table
Student Schedule page
Click view exam

Schedule ()
Search
Display ()

Sequence diagram for view class schedule
View class
Schedule
Instructor and View class

Home page Post table
Student Schedule page
Click view class

Schedule ()
Search
Display ()

Sequence diagram for view grade
View grade
Search engine View grade

Student Home page Upload table
Page Page
c lick view grade()

dis p lay ()
Enter UID
Click ok
Search
Display ()

Sequence diagram for add course
Add course
Add course
Department Home page Add table
Page
Click add course
Display ()
Insert information
<<Create>>
Success

Sequence diagram for take exercise
Take exercise
Search engine
Student Home page Exercise page Add table Answer table
Page
Click take
Exercise ()
Display ()
Insert course
Name
Click ok
Search
Display ()
Answer question
Click submits ()
Store
Success

Sequence diagram for download material
Download
Material
Student Home page Download page Upload table
Click download
Material ()
Display ()
Enter course
Code
Click download
Download
Complete

Sequence diagram for logout
Logout
Users Current page Login page
Click logout ()
Display ()

2.2.6 Activity diagram
Activity diagram for create account

Activity diagram for login

Activity diagram for post class schedule

Activity diagram for add department

Activity diagram for post exam schedule

Activity diagram for add course
Click add
Course
Enter information
Course is
Added

Activity diagram for upload grade

Activity diagram for upload material

Activity diagram for add exercise

Use case for upload grade

Activity diagram for view class schedule

Activity diagram for view exam schedule
Activity diagram for download material

Activity diagram for take exercise

Activity diagram for view grade

Activity diagram for logout

Click logout
Logged out

2.2.7 Class diagram
Employee student
Name: string
id: integer
Sex: char id:integer
Address: varchar () name: string
sex: char()
Teach * address:varchar
login: varchar()
login;varch
view class schedule:varchar()
downloadmaterial:varchar()
takeexam:varchar()
viewgrade:varchar()
1 1
1...* 1...* * 1...*
Administrator
Instructo
r
1...*
add
1
Upload material: varchar () give
Create account: varchar () View class schedule: varchar ()
Exercise Take
post class schedule: varchar() add exercise: varchar()
post exam schedule:() No of exercise
Upload grade: varchar ()
add department:()
Blank Enroll
Choose T or F
space Work for 1 1..*
Create 1...*
Course
add Department
1 Coursename:string
add 1...*
Account Name: string Coursecode: integer
Name Password id: integer Pre-requisitevarcha
Email: varchar () Ceredithour: integer
Password: varchar () addcourse: string
login: varchar()

E-Learning University Project 2

Uploaded by

Document Information

Original Title

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 University Project 2

Uploaded by

Copyright:

Available Formats

COLLEGE OF COMPUTING AND

TITLE: E-LEARNIG SYSTEM

1. Dinku Boru ……………………………………….360/08

HU E-LEARNING SYSTEM PROJECT Page 1

HU E-LEARNING SYSTEM PROJECT Page 2

1.2 Statement of the Problem

HU E-LEARNING SYSTEM PROJECT Page 3

1.3.1 Specific Objective

 To study the different characteristics of the E-learning system process.

Requirement modeling: In developing this system we follow an object oriented analysis

1.5 Feasibility study

Tangible benefit:-Benefits that are easily quantified.

Intangible benefit:-Unquantifiable benefits

HU E-LEARNING SYSTEM PROJECT Page 4

1.6 Project Scope and limitation

HU E-LEARNING SYSTEM PROJECT Page 5

1.7 Significance of the project

2.1.1 Existing system description

2.1.1 Business Rule

HU E-LEARNING SYSTEM PROJECT Page 6

2.2 New system

2.2.1 Non Functional Requirements and constraints

HU E-LEARNING SYSTEM PROJECT Page 7

2.2.3 Use case Diagram

HU E-LEARNING SYSTEM PROJECT Page 8

HU E-LEARNING SYSTEM PROJECT Page 9

Use case name Create account

main flow of event Actor action System response

1. The Administrator click create account 2. The system displays

Post-condition Account will be created.

HU E-LEARNING SYSTEM PROJECT Page 10

Use case name: Login

Actor: Administrator, instructor and student

Pre-condition: The users have password

main flow of events Actor action System response

1. User clicks login button on homepage. 2. The system displays the

5. The system validates

Post-condition: The actors logged in to the system and select tasks.

HU E-LEARNING SYSTEM PROJECT Page 11

Use case Code: Post class schedule

Pre-condition Administrator prepare schedule

main flow of event Actor action System response

Administrator click post class schedule 2. The system displays post

3. Administrator insert schedule. 5. The system notifies

Post condition User can view Uploaded class schedule.

HU E-LEARNING SYSTEM PROJECT Page 12

Use case Add Department

main flow of Actor action System response

3. Administrator fill information 5. Add will record on the add

Post condition Admin can view added department.

HU E-LEARNING SYSTEM PROJECT Page 13

Use case Code: Post exam schedule

Pre-condition The administrator prepare exam schedule

Main flow of event Actor action System response

1. Administrator click on post exam schedule 2. The system display form of

3. Administrator Wright exam schedule on 5. Post exam will record on the

4. Then click post button

Post condition user can view Uploaded exam schedule

HU E-LEARNING SYSTEM PROJECT Page 14

Use case name: Upload Material

Pre-condition: The instructor should have to prepare resources to be uploaded.

main flow of event Actor action System response

3. The Instructor fill name of course, course 5. The system record