SYSTEM Requirement and DESIGN For HU On-Line Grading System and Part E-Learning

SCHOOL OF INFORMATICS
INFORMATION TECHNOLOGY PROGRAM
INDUSTRIAL PROJECT ONE: PROJECT DOCUMENTATION
ONLINE GRADING SYSTEM AND PART

E-LEARNING
Prepared by:
NAME ID EMAIL PHONE

YIMER AMEDIE IT/523/02 yimer523@gmail.com +251914058187
ZERIHUN SEYFU IT/549/02 Zerihun549@gmail.com +251921259446
TESHOME GEBRE IT/552/02 tesh53@gmail.com +251911540043
Submitted to: Mr Simon Tiruneh
rec_sim@yahoo.com
simont@hu.edu.et
Submitted Date: Feb 11/2013
i
HU-OLGS AND PART E-LEARNING 2012/201
3
Acknowledgement
First of all we would like to thank our advisor Mr. Simon Tiruneh for his constructive comments
for the successful completion of the first phase of the project.
Secondly, we would like to thank Hawassa University School of Informatics staff for their
assistance in different situation.
Lastly, the thanks go to all our friends who contribute a lot in financial and academically
supports for this project.
Team members,
3
Table of Content
Contents page
Acknowledgement...............................................................................................i
Table of Content..................................................................................................ii
List of Figures......................................................................................................iv
List of Tables........................................................................................................v
CHAPTER ONE......................................................................................................1
1.0 Introduction.......................................................................................................................................1
1.1 Background..................................................................................................................................2
1.2 Statement of the Problem...........................................................................................................3
1.3 SCOPE AND LIMITATION OF THE PROJECT...................................................................................4
1.4The Overall Description......................................................................................................................4
1.4.1Over view of the existing system.................................................................................................4
1.4.2 Overview of the new system......................................................................................................5
1.5 Objectives of the project...................................................................................................................5
1.5.1 General objectives......................................................................................................................5
1.5.2 Specific objective........................................................................................................................6
1.6 Methodology and Tools.....................................................................................................................7
1.6.1 Method of data collection..........................................................................................................8
1.6.2 Interview.....................................................................................................................................8
1.6.3 Observation................................................................................................................................9
1.6.4 Development Tools.....................................................................................................................9
1.7 Schedule of the project....................................................................................................................11
CHAPTER TWO.............................................................................................13
3
SYSTEM REQUIREMENT SPESIFICATION..............................................13

2.0 Introduction.....................................................................................................................................13
2.1 Requirement Analysis......................................................................................................................13
2.1.1 FUNCTIONAL REQUIREMENT....................................................................................................13
2.1.2 NON- FUNCTIONAL REQUIREMENT..........................................................................................14
2.3 Understanding the domain..............................................................................................................15
2.3.1 Glossary....................................................................................................................................16
CHAPTER THREE.................................................................................................17
SYSTEM DESIGN.................................................................................................17
3.0 Introduction.....................................................................................................................................17
3.1 System Modeling.............................................................................................................................18
3.1.1 Business Model.........................................................................................................................18
3.1.2 System Use Case Diagram.........................................................................................................19
3.1.3 Use case identification..............................................................................................................20
3.1.4 Use case Diagram......................................................................................................................20
3.1.5 Use Case Documentation..........................................................................................................22
3.2 Logical Data Modeling.....................................................................................................................33
3.2.1Class Diagram............................................................................................................................34
3.3 Dynamic Model................................................................................................................................36
3.3.1 Activity Diagram........................................................................................................................36
3.3.2 Sequence diagrams...................................................................................................................50
3.4 Navigation Tree or Site Map............................................................................................................64
3.5 Deployment Diagram.......................................................................................................................65
CHAPTER FOUR..................................................................................................66
4.0 Database Design.......................................................................................66
4.1 Database Tables...............................................................................................................................66
4.2 Design Interface...............................................................................................................................72
References.........................................................................................................77
3
List of Figures
Fig 1.1 Agile software development methodology......................................................................................8
Fig3. 1 system workflow...........................................................................................................................17
Fig 3.2 Prototype process model for the proposed system.........................................................................19
Fig 3.3 use case diagram of the system......................................................................................................21
Fig 3.4 Class diagram for HU-OLGS & PART E-LEARNING................................................................35
Fig 3.5 Activity diagram for login.............................................................................................................37
Fig 3.6 Activity diagram for Registration..................................................................................................37
Fig 3.7 Activity diagram for posting grades..............................................................................................38
Fig 3.8 Activity diagram for viewing grades.............................................................................................39
Fig 3.9 Activity diagram for creating report card......................................................................................40
Fig 3.10 Activity diagram for recording grade..........................................................................................41
Fig 3.11 Activity diagram for adding quizzes/assignments.......................................................................42
Fig 3.12 Activity diagram for taking quizzes.............................................................................................43
Fig 3.13 Activity diagram for accessing course materials.........................................................................44
Fig 3.14 Activity diagram for submitting assignments..............................................................................45
Fig 3.15 Activity diagram for submitting grades.......................................................................................46
Fig 3.16 Activity diagram for approving grades........................................................................................47
Fig 3.17 Activity diagram for uploading course materials.........................................................................48
Fig 3.18 Activity diagram for downloading/viewing course materials......................................................49
Fig 3.19 Sequence diagram for registration...............................................................................................51
Fig 3.20 Sequence diagram for login.........................................................................................................52
Fig 3.21 Sequence diagram for posting grades..........................................................................................53
Fig 3.22 Sequence diagram for viewing grades.........................................................................................54
Fig 3.23 Sequence diagram for creating repot card...................................................................................55
Fig 3.24 Sequence diagram for recording grades.......................................................................................56
Fig 3.25 Sequence diagram for adding quizzes/assignments.....................................................................57
Fig 3.26 Sequence diagram for taking quizzes..........................................................................................58
Fig 3.27 Sequence diagram for downloading/viewing course materials....................................................59
Fig 3.28 Sequence diagram for submitting assignments............................................................................60
Fig 3.29 Sequence diagram for submitting grades.....................................................................................61
Fig 3.30 Sequence diagram for approving grades......................................................................................62
Fig 3.31 Sequence diagram for uploading course materials.......................................................................63
Fig3.32 Navigation tree.............................................................................................................................64
Fig3.33 Deployment diagram....................................................................................................................65
3
Fig 4.2.1 Home page.................................................................................................................................72

Fig 4.2.2 Interface for registration: Student..............................................................................................73
Fig 4.2.3 Interface for registration: Instructor and committee...................................................................74
Fig 4.2.4 Interface for login: Student.........................................................................................................75
Fig 4.2.5 Interface for login: Instructor and committee.............................................................................76
List of Tables
Table 3.1 use cases and actors identification.............................................................................................21
Table 4.1.1 Student Table..........................................................................................................................66
Table 4.1.2 Instructor Table.......................................................................................................................67
Table 4.1.3Committee Table.....................................................................................................................67
Table 4.1.4 Admin Table...........................................................................................................................68
Table 4.1.5 Job Table................................................................................................................................68
Table 4.1.6 Course Table...........................................................................................................................68
Table 4.1.7 Grade Table............................................................................................................................68
Table 4.1.8 Report card Table...................................................................................................................69
Table 4.1.9 User account Table.................................................................................................................69
Table 4.1.10 Student Grade Table.............................................................................................................69
Table 4.1.11 Instructor Course Table........................................................................................................70
Table 4.1.12 Quiz Table............................................................................................................................70
Table 4.1.13 Assignment Table.................................................................................................................71
Table 4.1.14 Question Table......................................................................................................................71
Table 4.1.15 Period Table..........................................................................................................................72
Table 4.1.16 Semester Table.....................................................................................................................72
Table 4.1.17 Department Table.................................................................................................................72
3
CHAPTER ONE
1.0 Introduction
Hawassa University is one of the fastest growing Universities in Ethiopia with new opportunities
rising continually in hundreds of different fields with more than 25000 students with one
institute, ten schools, and five departments. There are also many specializations under the
institute, schools and departments.
Registrar is one of the major parts of the university and its part of work is posting grades for
students. In essence, grading is an exercise in professional judgment on the part of instructors. It
involves the collection and evaluation of evidence on students' achievement or performance over
a specified period of time, such as two months, an academic semester, or entire learning year.
Through this process, various types of descriptive information and measures of students'
performance are converted into grades or marks that summarize students' accomplishments. So
that grading System is design to provide inducement reward for the achievement and assists in
identifying problems of the students. It is the most commonly used in identifying problems of the
students. It is the most commonly used in computing and analyzing the performance, talent and
skills of students, the important record to keep even for the longest time for the referral and
credentials of the students to enter the next level of attaining their goals. It is also used for
analyzing one’s attitude and values.
The system also provides E-Learning service which includes electronically supported learning
methods. In E-Learning students can study anywhere they have access to a computer and Internet
connection. Students may have the option to select learning materials that meets their level of
knowledge and interest. Develops knowledge of the Internet and computers skills that will help
students throughout their lives and careers.
3
Generally, Hawassa University Online Grading System and Part E-learning will be used for
submission of all final course grades. The system also provides instructors with a flexible and
user-friendly interface for posting final course grades to student records. Grade can be entered
using the basic online screens or uploaded from an Excel spreadsheet. Online Grading System
and Part E-learning is a web-based application that can be used to create account for students,
used to post the grades of the students, used to provide quizzes and course materials for students
online.
1.1 Background
H
awassa University was established at Hawassa in April 2000.Since 1976 the different
colleges of HU had been operational starting with the college of Agriculture. The
University has been formed by merging three colleges in Southern Ethiopia: Awassa
College of Agriculture (ACA), Wondogenet College of Forestry and Dilla College of Teacher
Education and Health Sciences. The university has upgraded its capabilities, adding new
colleges, institutes and departments, programs and research facilities. Today, HU is a
comprehensive university engaged in the provision of all-round education, research, training, &
community service through its diversified areas of academic units. HU is actively engaged in
expansion activities to increase its intake capacity.
Registrar is the major part of the university and showing grades for students is one of the major
tasks in the registrar of the university. Because the university gives the registrar office to have a
responsibility for helping student such as solving grade and course related problems during their
stay in the university. To carry out their tasks they set a rules and regulation.
The registrar office highly recommended that students should know these rule and regulation
carefully and familiarize themselves with them. Hawassa University has registrar office for each
schools and departments that post the grade of students on the notice board and submits the grade
report of the students after printing it. Also the university assigns courses for students which they
take and for instructors they give the course. Hawassa University also needs to make the system
to be online and provide solution for some of the problem that was happening.
3
1.2 Statement of the Problem
At present Hawassa university have no online grading system .They are trying to cope the
existing system, which is normally release the students grade list and grade report in a delayed
time. Because they compute it using Microsoft Excel electronic spreadsheet and then manually
compute the students grades list to double check. This causes the students to waste time and
effort in always going back to registrar just to view their grades and to get their grade report.
Also students get course materials in hardcopy form the instructor which requires more money
and time to duplicate. The university also has no e-learning service that is available for all
courses and introduce students with the technology. As a result most of the university students
have no the required computer skills that expect from the university students. Because they use
computers only for the common course (Introduction to IT) when they are freshman.
Therefore, we will need to improve existing systems by eliminating manual works and increase
the speed of process and able to make it available to be online to give the service. So that HU-
OLGS AND PART ELEARNING allows students to view their grades, take quizzes and to
access course materials online.
Project Initiation
 To contribute a role to make our university competent with other foreign university
which are using today’s technology.
 To seek one of the university vision to reach the mission of tomorrow.
 Now a days we are in ICT ages where everything is solved easily by using different
technologies. Beyond that we prefer OLGS AND PART E-LEARNING SYSTEM to be
applied in our university to solve problem of time and effort that challenges students.
 To make grading process convenience and time saving.
 To avoid lack of course material
3
1.3 SCOPE AND LIMITATION OF THE PROJECT
The scope of this project is:
 Show grades for students online without going to their instructors.

 Provide proposed grade submission by instructors to grade approval committee
 Student registration.
 Admin of the registrar post grades for students online.
 Enable students to gain course materials online in proper order.
 Online quizzes for students.
 Course registration of students and instructors.
 User authentication
 Provides web-based service to help advance education through standards-based learning
Limitation of this project is:
 It doesn’t generate CGPA of students.

 Online attendance and online evaluation of students is not included in the system.
 No mechanism of controlling students from chatting in case of online quizzes.
 Available with internet connection.
 Students may feel isolated from the instructor and classmates (no means of collaborating
Instructors and students together.)
1.4The Overall Description
1.4.1Over view of the existing system

3
At present Hawassa University has no online grading system. In this existing system instructors
submit the proposed grade of students to the grade approval committee then student grades
approved by the committee send back to the instructors.
After that instructors submit the hardcopy of the approved grade for the registrar, the students
come to the registrar office and they see their marks on the notice board and they take hard copy
after it is printed.
The university also has no e-learning system that provides quizzes and course materials online.
The instructors provide handouts for students. Students duplicate the handout by their own
money and prepare for exam based on the handouts .Students also can get hardcopy books in
libraries, for most of the students these books are the only reference material. Most of the time,
the required book is not found in the library. Because of lack of books and shortage of books
that are used as additional references, students lose grades. These kinds of problems are broad
especially in school of informatics.
Hawassa University e-Learning also officially launched on march 2010 with four online courses
by the title of Hawassa university e-courses using one of open source course management system
which is Moodle (Modular Object-Oriented Dynamic Learning Environment).
1.4.2 Overview of the new system
Our new system is an interactive and user-friendly that contains registration and login forms. The
system enables instructors to submit student grades for grade approval committee and the
registrar online within less time and energy. Students view their grades online and they get a lot
of course materials online without fee .Also the system provides online quizzes for students that
are available within limited period of time and provide course materials as part of e-learning.
1.5 Objectives of the project
1.5.1 General objectives
The overall goal of this project is to design and to develop an Online Grading System and part e-
learning for HU to provide the capability to allow students to view their grades, to utilize course
3
materials or other online service that the existing systems will need using simple, secure
efficient, attractive and user-friendly web based system that will have the ability to solve the
problem of the existing system.
1.5.2 Specific objective
The specific objective of this project is:
 Develop web-based system which provides online grading and learning service that will
be used to reduce wastage of time and energy.
 The system provides direct links to other sources of information such as free online
journal sites, best educational sites, online tutorials sites, entertainment site and other
sites that are used to increase student skills.
 Create a system of reliable and accurate to compute grades in all different courses.
 Provide fast access of information of grades; generate reports and information of the
input of instructors.
 Design the project using HTML for Client Side and PHP for Server Side which helps in
understanding different technologies.
 Eliminate tons of papers used in computerized grading sheet, grading sheet per semester
and summary sheet.
 Enable students to have the option to select learning materials that meets their level of
knowledge and interest
 Develops knowledge of the Internet and computers skills that will help learners
throughout their lives and careers
 Eliminate the problems such as wastage of time, lack of reference materials ,shortage of
reference materials ,wastage of tons of papers and others that faces the existing system
and deliver the best alternative proposed solution.
 Enable students to get other references online
 Providing online test or quiz for students.
3
 Provide course materials online so that students can access it about everywhere, at all
time.
 Enable the team members to gain analytical and problem-solving skills.
 Guide the content materials and the teaching methods.
 Increase the use of internet and the technology of the day.
1.6 Methodology and Tools

This project follows or uses agile software development methodology which is object-oriented
paradigm with greatest values such as:
 Individuals and interactions over processes and tools

 In agile development, self-organization and motivation are important, as are
interactions like co-location (i.e. face-to-face conversation is the best form
of communication) and pair programming (an agile software development
technique in which two programmers work together at one workstation)
over processes and tools.
 Working software over comprehensive documentation:
 Working software will be more useful and welcome than just presenting
documents to clients in meetings.
 Responding to change over following a plan:
 Agile development is focused on quick responses to change and continuous
development.
Agile software development methodology also has the following justifications
 Continuous attention to technical excellence and good design

 Modularity: Agile methods break tasks into small increments with minimal
planning and do not directly involve long-term planning.
 Agile methods emphasize face-to-face communication over written documents
when the team is all in the same location.
3
 Saves cost, time and efforts by following iterative incremental work delivery
and thereby identifying deviations early.
 Agile facilitates smooth flow of knowledge sharing
 Increases cohesion between the teams to deliver on time. So project teams are
involved more actively in all the stages.
 Simplicity: agile making things simple and free to change.
 Provides the end result of higher quality of the software delivered and a highly
satisfied customer.
Fig 1.1 Agile software development methodology
1.6.1 Method of data collection
The data collection process to conduct this project includes both the qualitative and quantitative
data. This will be done through the use of instruments such as observations, interviewing and the
Internet. From these three data gathering tools, interview will be used to collect data from the
office of the registrar and form the instructors. Observation will also be used to oversee the
3
required things in the university. And the internet used to collect data from the website of the
university and other online resources
1.6.2 Interview
Interview is a conversation or questioning, for the purpose of eliciting information for

publication, the published statement so elicited.
Interview Procedures
 First we will decide to interview to the registrar manager.

 We will schedule the interview and confirm the meeting time and date a day before
conducting the Interview.
 We will critically look as much as possible about the topic of interview before conducting
the interview.
 We will prepare all materials required for the interview like note books, pencil or pen and
if there is audio recorder.
 Conducting the Interview by fulfilling all criteria’s required for the interview
 Examining the interview by preparing a written summary of the key points discussed in
the interview that are relevant to our topic.
 Finally, we will determine its usefulness by analyzing whether the information obtained
from the interviewee is useful, contribute, correct for the development of our topics.
1.6.3 Observation
3
Observation is the other instrument that will use to collect data which will be necessary for our
web-based system project for the university. In this process we will try to investigate the
information by making our selves participates in the process. And observations will also helping
us to relate the information obtained from the interviewee by looking to the reality of the
university.
1.6.4 Development Tools
Developing HU_OLGSAND PART E-LEARNING needs a number of tools that makes the
process easy and fast. These development tools are hardware tools and software tools both
collaboratively work to achieve specific goals. Hardware tools are all tools that we touch and feel
and help to work with the project. Software tools are programs or instructions that help us to
simplify work. Here are some development tools:-
Hardware tools
 Personal computer(Pc)
 Web server machine
 Digital camera
 Pen and paper
 Hard disk with minimum of 512GB
 RAM with minimum of 2GB
 Processor with Pentium IV
 Flash
Software tools
 Web browser (Mozilla Firefox, Google chrome, opera, IE8): So we can check the system
across a variety of platforms.
 Operating system of window7 to develop the system
3
 Adobe Photoshop: for editing images and icons for the interface of the system.
 Jquery :coding language
 Gantt chart
 Dream weaver
 XAMP with PHP and MY-SQL, apache server
 Widow notepad
 html, css, Java script, xml
1.7 Schedule of the project
This project is expected to be completed in two semesters of 2012/2013 academic year. Some
parts of the project component to be completed in the first semester are up to design and the rest
of activities such as implementation, testing and maintenance would complete in the next
semester including other minor activities.
Project Review: In this phase we formally examine the project and provide concept notes based
on the review.
Concept Notes: In this phase we provide whole concepts about the project and achieve the
required idea to begin the project.
Generally, the schedule of the project is provided for the purpose of doing the tasks on time. So
we represent the schedule of the project using Gantt chart as follows.
3
3
No_ Tasks Sta En D 2012 2013
rt d u Dec Jan Feb Mar April May June
Dat Dat r 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4
e e a
ti
o
n
1 Project De De 3
review c-3 c-6
2 Concept De De 4
note c-4 c-8
3 Problem De De 8
Identific c-7 c-
ation 15
4 Proposal De De 1
Writing c-7 c- 6
21
5 Require De Jan 4
ment c- -30 7
Analysis 14
6 Specifica Jan Jan 2
tion -8 -31 3
7 System Jan Fe 1
Design -14 b-1 7
8 Implem Fe Jun 1
entation b- -7 1
22 1
9 Integrati Jun Jun 1
on and -8 -22 4
Testing
10 Docume Jun Jun 8
ntation -22 -30
11 Closing Jun Jun 2
-28 -30
Page | 19
3
CHAPTER TWO
SYSTEM REQUIREMENT SPESIFICATION
2.0 Introduction
The purpose of this SRS document is to write the functional and non functional system
requirements that represent the characteristics of HU-On-Line Grading System & Part E-
Learning.
2.1 Requirement Analysis

Once the aims of the project have been established, the work of eliciting, analyzing and
validating the system requirements can commence. This is crucial to gaining a clear
understanding of the problem for which the system is to provide a solution and its likely cost.
The requirement phase translates the ideas in the minds of the clients into a formal document.
The requirements engineer must strive for completeness by ensuring that all the relevant sources
of requirements are identified and consulted.
To help the analysis of the system requirements, conceptual models of the system are
constructed. These aid understanding of the logical partitioning of the system, its context in the
operational environment and the data and control communications between the logical entities.
This section includes functional and non-functional requirements of the system described below.
2.1.1 FUNCTIONAL REQUIREMENT
HU-OLGS and part E-Learning has the following functionalities:
 Registration: Enables the instructors, grade approval committees and students to

register to the system.
 Viewing grades: Enables the students to login to the system and view their grades.
 Accessing E-learning services (Downloading or Online Viewing): Enables the
students to login to the system and gain access to E-learning services such as use
Page | 20
3
course materials and other references online or downloading it for later use, doing and
submitting assignments and quizzes.
 Uploading: Enables the instructors to login to the system and upload course
materials, assignments and quizzes for students.
 Posting grade: Enables the administrators to registered and login to the system and
calculate GPA of students and post grades for students.
 Record Information: System will record information about students and E-Learning
services like course material sources, descriptions and lessons.
 Taking Quizzes: Enables the student to take quizzes online.
 Providing answers and result: The system will provide answers for quizzes. A
system can be given a mark by checking the students answers, and give the result as
soon as students finish his/her quiz.
 Updating: Student will update its information.
 Authentication: The system will be verified by denying unauthorized user from
using the system.
 Notice: The system will display information needed for the students on time. Like
Final exam schedule, date of registration for next semester and other notices.
2.1.2 NON- FUNCTIONAL REQUIREMENT
HU-OLGS & PART E-LEARNING has the following non-functional requirements to achieve
its functionality.
 NFR1: Usability:-The system is easy to learn and operate. The User interface for
this system will be simple and clear. The student information will be easy to read,
understand and access. The E-Learning services are easy to gain and use i.e. the
service doesn’t require special training.
 NFR2: Availability (ubiquity): – This system is available in everywhere (where
internet service reach) and at all time for those who have access to use the system.
 NFR3: Performance-The system will have good performance i.e. fast response
time and optimal workload.
Page | 21
3
 NFR4: Security: – The system will be secured as much as possible so that there
is permissible information flow regarding to who can do what.
So it is designed to be very secure by providing a login feature which
authenticates the user by means of a user name and password with which user will
be able to login to his/her respective pages and use the system as required.
 NFR5: Portability:-The system is machine independent and software system
independent so it can be moved to different target platforms.
 NFR6: Reliability: – The system is operational and consistent in that integrity of
information is maintained and supplied to the system.
 NFR7: Documentation: –The system contains the required documents needed to
implement the project.
2.3 Understanding the domain
Domain requirements show the environment in which the system operates so, when describe
an application domain that is the environment of online grading system and part e-learning.
Domain requirements may be expressed using specialized domain terminology or reference
to domain concepts. Understanding the domain is necessary concept because they often show
fundamentals of the application domain. If these requirements are not satisfied, it may be
difficult to make the system what we want it does. Sometimes characteristics of the
application domain mean that the requirements specification that includes a description of
how to carry out some computations. It uses domain-specific terminology (glossary).
Page | 22
3
2.3.1 Glossary
# Short name description

1 HU-OLGS Hawassa University On-Line Grading System
2 Comprehensive Complete including all or nearly all elements or
aspects of the project.
3 Software The programs and other operating information

used by a computer.
4 E-Learning electronic learning
5 Web-based Application An application that is usable only with an active
internet connection and that uses http as its
primary communication protocol.
6 Business model A business model describes the justification of

how an organization creates, delivers, and captures
value
7 Interaction Reciprocal action or influence
8 System A set of things working together as parts of a
mechanism or an interconnecting network
9 GPA grade point average

10 CGPA Cumulative grade point average
11 NFR Non-Functional Requirement
12 Admin Administrator
Page | 23
3
CHAPTER THREE
SYSTEM DESIGN
3.0 Introduction
The designer’s goal is to produce a model or representation of an entity that will later be built.
Beginning, once system requirement have been specified and analyzed, system design is the first
of the three technical activities -design, code and test that is required to build and verify software.
The importance can be stated with a single word “Quality”. Design is the place where quality is
fostered in software development. In this chapter we are introduce system workflow, activity
diagram, sequence diagram and class diagram.
Start
Student Instructor
LOGIN
LOGIN Admin
LOGIN
Test Material
Test
POST
GRADE Grade
DOWNLOAD ADD
OR READ Grade ASSIGNMEN
MATERIAL VIEW TEST T
ADD TEST Submit
GENERATE grade
Find His REPORT
Grade CARD
UPLOAD
TAKE TEST
MATERIAL
VIEW
RESULT
VIEW VIEW
RESULT RESULT
LOGOUT
STOP
Page | 24
3
Fig3. 1 system workflow
3.1 System Modeling
The system modeling deals with analyzing the proposed system. It includes the system use case
diagrams, the use case descriptions (scenarios), sequence diagrams, object model, dynamic
model and activity diagrams.
After identifying the actors and use cases, the use cases are developed and textual descriptions
(Scenarios) are stated. The Sequence diagram is depicted based on the use cases which are
developed for the proposed system. Activities will be represented by the activity diagrams.
3.1.1 Business Model
It describes the justification of how the system creates, delivers, and captures value. Business
Process Model typically has a broader and more inclusive range than just the software system
being considered, it also allows the analyst to clearly map what is in the scope of the proposed
system and what will be implemented in other ways (e.g. a manual process).We describe the
business model in use case documentation of the system
Page | 25
3
Requirement
Gathering
Quick
Design
Build
Refine prototype
Requirement
Not Accepted User

Evaluation
prototype
Accepted
Design
Implementation and
testing
Maintain
Fig 3.2 Prototype process model for the proposed system
3.1.2 System Use Case Diagram
Use case is a list of steps, typically defining interactions between a role and a system, to achieve
a goal. This use case used to identify the process that takes place in the new system. It helps to
decide what will be design in the design phase. Also this system use case has high level
implementation decision. It describes actors and use case documentation and describes sequence
of action to actors. The purpose of design this use case is to indicate which actors participate to
which use case.
Page | 26
3
3.1.3 Use case identification
Actors Use cases

 Student Register
 Instructor Login
 Administrator(Registrar’s office) Post Grade
 Grade Approval Committee View Grade
Create Report Card
Record Grade
Add Quizzes
Take Quiz
Access Course Materials
Add Assignments
Submit Assignments
Submit Grade
Approved Grade
Upload course Material
View Course Material
Download course Material
Table 3.1 use cases and actors identification
3.1.4 Use case Diagram
Page | 27
3
Record
Take Grade
quiz Download
materials
Upload
<<extend>>
course
Access material
course
Student material
<<extend>>
Add Quiz
View Instructor
online
Submit
assignment Add
Assignment
Login
Submit
Grade
<<include>> Committee
Post
Grade
View
Grade
Admin
Approve
Register
Grade
Create
Report card
Fig 3.3 use case diagram of the system
Page | 28
3
3.1.5 Use Case Documentation
The above listed use cases are described in detail in this section
Use case name: Register
Description: Students, Instructors, Administrator and grade approval committee s are registered
to the system.
Actors: Users (Student, Instructor, Administrator and grade approval committee).
Precondition: Users request for registration and fills the registration form.
Normal Course:
1) Users select the register menu from the home page.

2) System displays the registration form.
3) The users select registered as Student or Instructor or Administrator or grade approval
committee.
4) System displays the requested registration form.
5) The system registers Student, Instructor, Administrator and grade approval committee
6) Use case ends
Alternative Course
1) The user enters invalid information

2) The system informs she or he can’t register or already registered user.
3) The system return to step 2 of normal course
4) Use case ends
Post condition: Users are registered.
Use case name: Login
Page | 29
3
Description: login is authenticating Students, Instructors, Administrator and grade approval
committees to grant privilege.
Actors: Users (Student, Instructor, Administrator and grade approval committee)
Precondition: Users enters user name and password in order to login and display home page.
Normal Course:
1) Users need to enter the system.

2) System displays login form
3) Users enter user name & password and click OK
4) The system cheeks the user name & password and approved
5) The system display appropriate page for user
6) Use case ends
Alternative Course: Login failed
1) The system determines the invalidity of information(user name and password)

2) The system informs the user name and password entered is invalid and reenter
4) use case ends
Post condition: The Students, Instructors, Administrator and grade approval committee login to
the system
Use case name: Post Grade
Description: The registrar office posts the grade of students
Actors: Administrator
Precondition: Administrator logged into the system.
Normal Course:
Page | 30
3
1) Administrator selects the post grade option
2) System displays post grade page
3) Admin select which course grade to be posted
4) The system posts the grade
5) Use case ends
Alternative Course: The admin enter incorrect information
1) System check the data entered

2) System inform to the admin ,you enter incorrect data or empty data and reenter
4) use case ends
Post condition: The grade posted into student interfaces
Use case name: View Grade
Description: Students has to view grades
Actors: User (Student, Instructor, Administrator and grade approval committee)
Precondition: The users logged into the system.
Normal Course:
1) Users selects the view grade option

2) System request what the user needs
3) The user select the course grade to be displayed
4) The system displays the request grade automatically
5) The user view the grade
6) Use case ends
Alternative Course:
1) The requested course grade is not complete to be viewed
Page | 31
3
2) The system prompts the student the request grade is not complete
4) Use case ends
Post condition: The requested grade is viewed
Use case name: Create report card
Description: Creating report card used for administrator to prepare all course grades together for
students at the end of each semester.
Actors: Administrator
Precondition:
o Administrator logged into the system

o All course grades must be provided by instructors.
Normal Course:
1) Admin selects the create report card option

2) System request what the admin needs
3) The admin adds the course to create report card
4) The system create report card
5) Use case ends
Alternative Course:
1) Admin enters invalid course and grade

2) System inform ,you enter wrong data
4) Use case ends
Post condition: The student receives report card .
Page | 32
3
Use case name: Record Grades
Description: Recording grades helps the instructors to keep student results for long period of
time.
Actors: Instructor
Precondition: Instructor logged into the system
Normal Course:
1) The instructor selects the record grade option

2) System request what the instructor need
3) The instructor adds the course grade to be recorded
4) System record the course grade
5) Use case ends
Alternative Course:
5) Instructor enters invalid course grade

8) Use case ends
Post condition: The instructor keeps the student grade permanently.
Use case name: Add Quizzes
Description: Quizzes are used for instructors to provide student grades
Actors: Instructor
Precondition:
o Instructor logged into the system

o Quizzes are prepared
Page | 33
3
Normal Course:
1) The instructor selects the Add quiz option

3) The instructor select the course for quiz
4) System Add the quiz
5) Use case ends
Alternative Course:
6) Instructor enters empty quiz

9) Use case ends
Post condition: Quizzes are available for students
Use case name: Take Quizzes
Description: Quizzes are used to measure student’s preparedness for courses
Actors: Student
Precondition: Student logged into the system
Normal Course:
1) The student selects the Take quiz option

2) System request what the student need
3) The student selects the course for quiz
4) System displays the requested course quiz
5) Students take quizzes
6) Use case ends
Page | 34
3
Alternative Course:
1) The requested course quiz is not complete to be taken

2) The system prompts the student the request course quiz is not complete
4) Use case ends
Post condition: The requested quiz is taken.
Use case name: Access Course Materials
Description: Course Materials are useful resources for students to prepare for exam and to gain
additional knowledge regarding to that course.
Actors: Student
Precondition:
o Student logged into the system
Normal Course:
1) The student selects the courses

3) The student selects the course for reading or downloading
4) System displays the requested course
5) Students gain access to the course
6) Use case ends
Alternative Course:
1) The requested course material is not prepared

2) The system prompts the student the request course material is not prepare
4) Use case ends
Page | 35
3
Post condition: Course material available to the student
Use case name: Add Assignments
Description: Assignments are given for students for the purpose of students to refer and read
more things when they do the assignment.
Actors: Instructor
Normal Course:
1) The instructor selects the Add assignment option

3) The instructor select the course for giving assignment
4) System Add the assignment
5) Use case ends
Alternative Course:
1) Instructor enters empty assignment

4) Use case ends
Post condition: Assignments are available for students
Use case name: Submit Assignments
Description: Assignments are given for students for the purpose of students to refer and read
more things when they do the assignment.
Actors: Student
Page | 36
3
Normal Course:
1) The student selects the submit assignment option

3) The students select the course for submitting assignment
4) System submit the assignment
5) Use case ends
Alternative Course:
1) Student enters empty assignment

4) Use case ends
Post condition: Assignments answers are available for instructors
Use case name: Submit Grade
Description: grading is an exercise in professional judgment on the part of instructors.
Actors: Instructor, Grade Approval Committee
Precondition:Instructor and Grade Approval Committee logged into the system
Normal Course:
1) The user selects the submit grade option

2) System request what the user need
3) The user select the course grade for submitting
Page | 37
3
4) System submit the grade
5) Use case end
Alternative Course:
1) User enters invalid grade

4) Use case ends
Post condition: Student grade available for registrar office
Use case name: Approve Grade
Description: grading is an exercise in professional judgment on the part of instructors and

approved by grade approval committee.
Actors: Grade Approval Committee
Precondition: Grade Approval Committee logged into the system
Normal Course:
1) The Grade Approval Committee selects the approve grade option

2) System request what the Grade Approval Committee need
3) The Grade Approval Committee select the course grade for approval
4) System approve the grade
5) Use case ends
Alternative Course:
1) Grade Approval Committee enters invalid data

4) Use case ends
Page | 38
3
Post condition: Instructors get the approved grade
Use case name: Upload course material
Actors: Instructor
Normal Course:
1) The instructor selects the Upload course material option

3) The instructor adds the course material to be uploaded
4) System upload the course materials
5) Use case ends
Alternative Course:
1) Instructor enters invalid course materials

4) Use case ends
Post condition: Course materials are available for students
Use case name: View Course Materials
Actors: Student
Page | 39
3
Normal Course:

3) The student selects the course for reading
4) System displays the requested course
5) Students view or read the course
6) Use case ends
Alternative Course:

4) Use case ends
Post condition: The requested course material is viewed or read by students
Use case name: Download Course Materials
Actors: Student
Normal Course:

3) The student selects the course for downloading
4) System downloads the requested course
5) Students save the course for later use
6) Use case ends
Page | 40
3
Alternative Course:

4) Use case ends
Post condition: The requested course material is downloaded by students
3.2 Logical Data Modeling
A logical model is a static view of the objects and classes that make up the design/analysis space.
Typically, a Domain Model is a looser, high level view of Business Objects and entities, while
the Class Model is a more rigorous and design focused model.
3.2.1Class Diagram
Class diagram shows the static structure of data and the operations that act on the data, i.e. it
shows the static structure of an object-oriented model the object class, their internal structure,
and the relationships in which they participate. Class diagram represents a detailed view of a
single use case, shows the classes that participate in the use case, and documents the relation ship
among the classes. It is a logical model, which evolves into a physical model & finally becomes
functioning information system.
Page | 41
3
Grade Report Card

1..*
+gradeId:string +CardId:string 1
1..* +gradeChar:string 1..* +CardName:string
+gradeValue:float +Description:string
has
1
Course
Student
+courseId:string 1..*
+courseName:string 1..* -StudentID:string
1..* 1..*
+credits:int - FirstName:string
- LastName:string
User account - PhoneNumber:int 1..*
- EmailAddress:string
+Username:string 1
t
pos
+Password:string
+Role:string +RegisterStudent()
1 1..*
1..* 1..* +viewGrade()
has
1
+TakeQuize()
Instructor 1 +verify user() +AccessMaterial()
+SubmitAssignment()
-InstructorID:string
- FirstName:string
1..* - LastName:string
- PhoneNumber:int Assignment
- EmailAddress:string 1..*
1..* 1..* assigned +assignmentId:int
- JobTitle:string
+Assignmentname:s
+RegisterInstructor() tring
+RecordGrade() provide 1..* +SubmisionDate:dat
take
+AddQuiz() e
+AddAssignment() 1..*
Quiz +NoOfQuestion:int
+UploadMaterial()
+SubmiGrade()
+QuizId:int
+viewGrade()
+User_Answer:string
+Mark:int
1..* +QDate:Date
1..*
manage provide 1..*
Admin
+Admin_Id:int
+First_Name:string
1 +Last_Name:string 1 manage
+Email:string
+Phone:int
1 +postGrade() 1 create
+CreateReportCard()
+AdminRegistration()
+viewGrade()
Fig 3.4 Class diagram for HU-OLGS & PART E-LEARNING
Page | 42
3
3.3 Dynamic Model
The dynamic model is used to express and model the behavior of the system over time. It
Includes support for activity diagrams, sequence diagrams and extensions including business
process modeling.
3.3.1 Activity Diagram
Activity diagram is a diagram which used for modeling the logic captured by single use case
usage scenario. It also helps to model the internal logic of complex operations of the system. In
addition to this, it shows the work flow from start point to end point details and many decision
parts that exist in progression of event contain in activity.
Page | 43
3
Open home page
Login form display
Enter user name and

password
correct not correct
Appropriate page for user

displayed
Fig 3.5 Activity diagram for login
Page | 44
3
Open home page
Select register menu
Save Users registration

information
System display registration

option
correct info
Select register as Users

not fill correctly
Fill form and

System display registration submit
form
Fig 3.6 Activity diagram for Registration
Page | 45
3
Open Admin page
Needs to post
grade
Appropriate entry
not appropriate
System post grade
View grade
(success message)
Fig 3.7 Activity diagram for posting grades
Page | 46
3
Open User page
Needs to view
grade
Appropriate entry
not appropriate
System displays grade
View grade
Fig 3.8 Activity diagram for viewing grades
Page | 47
3
Open home page
Needs to create
report card
Appropriate
not appropriate
System create
report card
View
report card
Fig 3.9 Activity diagram for creating report card
Page | 48
3
Open Instructor
page
Needs to record
grade
Appropriate entry
not appropriate
System record grade
grade recorded
(success message)
Fig 3.10 Activity diagram for recording grade
Page | 49
3
Open Instructor
page
Needs to add
quizzes/Assignments
Appropriate entry
not appropriate
System add
quizzes/Assignments
Quiz/Assignment added
(success message)
Fig 3.11 Activity diagram for adding quizzes/assignments
Page | 50
3
Open student
page
Needs to take quizzes
added
not added
System display
quizzes
Take
quizzes
Fig 3.12 Activity diagram for taking quizzes
Page | 51
3
Open student
page
Needs to access
materials
prepared
not prepared
System displays materials
Gain to access materials
Page | 52
3
Fig 3.13 Activity diagram for accessing course materials
Open student
page
Needs to submit
assignments
appropriate
not appropriate
System submit assignment
Assignment submitted
(success message)
Fig 3.14 Activity diagram for submitting assignments
Page | 53
3
Open Instructor/
committee
page
Needs to submit
grade
appropriate entry
not appropriate
System submit grade
grade submitted
(success message)
Fig 3.15 Activity diagram for submitting grades
Page | 54
3
Open committee
page
Needs to approve
grade
appropriate entry
not appropriate
System approved grade
grade approved
(success message)
Fig 3.16 Activity diagram for approving grades
Page | 55
3
Open Instructor
page
Needs to upload
materials
appropriate entry
not appropriate
System upload
materials
Materials uploaded
(success message)
Fig 3.17 Activity diagram for uploading course materials
Page | 56
3
Open student
page
Needs to download/View
materials
prepared or upload
not prepared
System downloads/Views
materials
Materials
downloaded/Viewed
Fig 3.18 Activity diagram for downloading/viewing course materials
Page | 57
3
3.3.2 Sequence diagrams
Sequence diagram describe behavior as a sequence of messages exchanged among a set of

objects. Sequence diagram which is also known as interaction diagrams are one of the diagrams
used in UML, for modeling the dynamic aspects of the system. It shows an interaction consisting
of a set of objects and their relationship including message that may be dispatched among them.
It emphasizes the time ordering of messages. It shows an interaction arranged in time sequence.
In particular, it shows the instances participating in the interaction by their “lifelines” and the
stimuli that they exchange arranged in time sequence.
Page | 58
3
:Registraion :Registraion : Registraion

Form Controller
:Registration Menu
Users
1. Click on registration
menu
2. Display registration
option
3. select register as student or

Instructor or Admin or 4. Display registration
Committee form
5. Fill the form and Click resister button
6. activate controller
7. Make sure necessary data is fill
8. check for redundancy
9. Registration fail
10. save record
11. Display success message
Fig 3.19 Sequence diagram for registration
Page | 59
3
:LoginForm :LoginControler :UserAccount
Users
1. open home page
2. View login form
3. enter username and password

4. Get Data
5. return data
7. Logon Failed 6. check

account
8. Login successful
(Display users page)
Fig 3.20 Sequence diagram for login
Page | 60
3
:Course
:PostGrade
:AdminPage Controller
Admin
1. open Admin page
2. select post
grade
3. post grade Display
4. Admin select the course
5. Activate controller
6. check course
7. Fail
8. Grade post
8. success message (Grade successfully posted!)
Fig 3.21 Sequence diagram for posting grades
Page | 61
3
Select Course Select Grade View

Course: Master: Grade: Master: Grade:
Users
Needs to view grade
Request Course verify
Invalid course
Inactive course If accept

Verify
Unavailable grade
Unavailable grade If accept
User view grades and finish
Page | 62
3
Fig 3.22 Sequence diagram for viewing grades
Select Course Select Report Report Card Create report

Course: Master: Card: Master: card:
Admin
Needs to take quiz
Invalid course

Verify
Unavailable data
Unavailable data If accept
Administrator create report card and finish
Page | 63
3
Fig 3.23 Sequence diagram for creating repot card
Select Course Select Grade Record

Instructor
Needs to record grade
Invalid course

Verify
Unavailable grade
Instructor record grades and finish
Page | 64
3
Fig 3.24 Sequence diagram for recording grades
Select Course Select Add Quiz Quiz/Assig Add Quiz/

Course: Master: /assignment: Master: Assignment:
Instructor
Needs to add quiz/assignment
Invalid course

Verify
Unavailable data
Instructor adds quizzes/assignments and finish
Fig 3.25 Sequence diagram for adding quizzes/assignments
Page | 65
3
Select Course Select Question Start Store Result

Course: Master: Question: Master: Quiz in DB:
Student
Needs to take quiz
Invalid course

Verify
Unavailable question
Unavailable question If accept
Return result and finish the quiz
Fig 3.26 Sequence diagram for taking quizzes
Page | 66
3
Select Course View/Download

Course: Master: Materials:
Student
Needs to view/download materials
Invalid course
If accept
Inactive course
Student view/download materials and finish
Fig 3.27 Sequence diagram for downloading/viewing course materials
Page | 67
3
Select Course Select Assignment Submit

Course: Master: Assignment: Master: Grade:
Student
Needs to submit assignment
Invalid course

Verify
Unavailable assignment
Unavailable assignment If accept
Student submit assignments and finish
Page | 68
3
Fig 3.28 Sequence diagram for submitting assignments
Select Course Select Grade Submit

Instructor/
Committee
Needs to submit grade
Invalid course

Verify
Unavailable grade
Instructor/committee submit grades and finish
Page | 69
3
Fig 3.29 Sequence diagram for submitting grades
Select Course Select Approve grade Approve

Course: Master: Approve grade Master: grade:
Committee
Needs to approve grade
Invalid course

Verify
Unavailable data
Grade approval committee approve grade and finish
Fig 3.30 Sequence diagram for approving grades
Page | 70
3
Select Course Upload

Course: Master: Materials:
Instructor
Needs to upload materials
Invalid course
If accept
Inactive course
Instructor upload materials and finish
Fig 3.31 Sequence diagram for uploading course materials
Page | 71
3
3.4 Navigation Tree or Site Map
Home
Registration Courses Grades Login Submission About Us

E-Learning
Registered as Read Course

Student View Grade Materials
Online Login as
student Address/(Em
ail/Phone)
Download Help
Registered as
Instructor/C Course
Login as
ommittee Post Grade Materials
Instructor/C
ommittee
Assignments
Faculty/Scho
ol Quizzes
All Courses
Grades
Specialization/Pro
gram
Page | 72
3
Fig3.32 Navigation tree
3.5 Deployment Diagram

Deployment diagrams show the hardware for the system, the software that is installed on that
hardware, and the middleware used to connect the disparate machines to one another and show
how the hardware and software components work together. According to our system we use
computer as hardware, web server (Apache) as soft ware and mysql connector as connectors.
Page | 73
3
Web Server Database Server

Client
The System
Student File database
Browser HTTP Mysql connection
<<Database>>:MYSQL
HU-OLGS &PART E-LEARNING Course File
Grade Files
Instructor File
Fig3.33 Deployment diagram
Page | 74
3
CHAPTER FOUR
4.0 Database Design

Data base design separate interfaces depending on the type of the user logged in, all
mandatory fields are pre checked ,all data that are specific to a user type made available
and database normalization done where appropriate
4.1 Database Tables
Table 4.1.1 Student Table

Description: Detail of student
Field Name Description Constraint Data Type Size

Student _ID Unique student Id is given to Primary key Varchar 20
each student
First _Name First name of the student Not Null Varchar 20
Last _Name Last name of the student Not Null Varchar 20
Phone _Number Phone number of the student Not Null Integer 16
Email _Address Email Address of the student Not Null Varchar 20
Department _ID Unique Id of the department Foreign key Varchar 20
Table 4.1.2 Instructor Table

Description: Detail of Instructor

Instructor _ID Unique Instructor Id is given Primary Varchar 20
to each Instructor key
First _Name First name of the Instructor Not Null Varchar 20
Last _Name Last name of the Instructor Not Null Varchar 20
Phone _Number address Not Null Integer 16
Email -Address address Not Null Varchar 30
Department _ID Department id Foreign Varchar 20
key
Page | 75
3
Table 4.1.3Committee Table

Description: Detail of Committee
Field Name Description Constraint Data Size

Type
Committee _ID Unique Committee Id is given to Primary Varchar 20
each Committee key
First _Name First name of the committee Varchar 20
Last _Name Last name of the committee Varchar 20
Phone _Number address Integer 16
Email -Address address Not Null Varchar 30
Department _ID The department id Foreign Varchar 20
key
Table 4.1.4 Admin Table

Description: Detail of Admin

Admin _ID Unique admin Id is Primary Varchar 20
given to each admin key
First _Name First name Not Null Varchar 20
Last _Name Last name Not Null Varchar 20
Email _Address address Not Null Varchar 30
Card _ID The unique id of the Foreign Integre 6
report card key
Table 4.1.5 Job Table

Description: Detail of Job
Field Name Description Constraint Data type Size

Instructor _IDUnique Instructor Id is given Foreign key Varchar 20
to each Instructor
Admin _ID Unique admin Id is given to Foreign key Varchar 20
each admin
Committee _ID Unique Committee Id is Foreign key Varchar 20
given to each Committee
Job _Title The job of the instructor and Not Null Varchar 30
committee
Page | 76
3
Table 4.1.6 Course Table

Description: Detail of Course

Course _ID Unique course Id is Primary Varchar 20
given to each course key
Department _ID Department id Foreign Varchar 20
key
Course _Name The name of the course Not Null Varchar 20
Credits Credit hour of the Not Null Integer 6
course
Table 4.1.7 Grade Table

Description: Detail of Grade

Grade _ID Unique grade Id is given to Primary Varchar 20
each grade key
Grade _Char Character grade like A,B,B+ Not Null Char
etc
Grade _Value Number value of grade like Not Null float 6
4.0,3.7,3.3 etc
Table 4.1.8 Report card Table

Description: Detail of Report card

Card _ID Unique report card Id is Primary Varchar 20
given to each report card key
Card _Name The name of the report card Not Null Varchar 20
Description Description of the report card Not Null Varchar 30
like semester dins list etc
Page | 77
3
Table 4.1.9 User account Table

Description: Detail of User account

User Name User name of the user Primary key Varchar 20
Password password Not Null Varchar 20
Role The roles like Not Null Varchar 20
student/Instructor/committee
Table 4.1.10 Student Grade Table

Description: Detail of student and grade

Grade _ID Unique grade Id is given to each Foreign Varchar 20
grade key
Student _ID Unique student Id is given to each Foreign Varchar 20

student key
Course _ID Unique course Id is given to each Foreign Varchar 20
course key
Period _ID Unique period Id is given to each Foreign Varchar 20
period key
Table 4.1.11 Instructor Course Table

Description: Detail of Instructor Course

Instructor _ID Unique instructor Id is given Foreign key Varchar 20
to each instructor
Course _ID Unique courser Id is given to Foreign key Varchar 20
each course
Table 4.1.12 Quiz Table

Description: Detail of Quiz
Page | 78
3
Quiz _ID unique quiz id is given to each quiz Primary Integer
key
Question _ID question id of the question attended Foreign Integer
by the student key
Course _ID Course id in which the question Foreign Varchar
attended by the student is listed key
User _Answer answer selected for the question by Not Null Varchar 10
the student
Marks marks obtained by the student for Not Null Integer 3
answering the question
Quiz _Date date on which the student had Not Null Date Time
appeared for the quiz
Table 4.1.13 Assignment Table

Description: Detail of Assignment
Field Name Description Constraint Data Size

Type
Assignment _ID Unique assignment Id is Primary key Integer 20
given to each assignment
Course _ID The unique Id of the course Foreign key Varchar 20
Assignment The assignment that is given Not Null Varchar 100
Answer The answer of the Varchar 100
assignment
Active Is the assignment active Not Null Boolean
or no
Table 4.1.14 Question Table

Description: Detail of Question
Question _ID unique question id is given to each Primary Integer 6

question key
Course _ID Course id in which the question is Foreign Varchar 20
listed Key
Question The question that is to be taken Not Null Varchar 100
Answer1 First option for the question Not Null Varchar 50
Answer2 Second option for the question Not Null Varchar 50
Answer3 Third option for the question Not Null Varchar 50
Answer4 Fourth option for the question Not Null Varchar 50
Correct _Answer Correct answer to the question Not Null Varchar 50
Page | 79
3
Active Is the question active or no Not Null Boolean
Table 4.1.15 Period Table

Description: Detail of Period

Period _ID Unique period Id is given to each Primary Number 15
period key
Start _Date Start date of the assignment or quiz Not Null Date
End _Date end date of the assignment or quiz Not Null Date
Table 4.1.16 Semester Table

Description: Detail of Department

Period _ID Unique period Id is given to each Primary key Number 15
period
Semester The semester that is first semester, Not Null Varchar 40
second semester
Year Year the course given Not Null Integer 20
Table 4.1.17 Department Table

Description: Detail of Department

Department _ID Unique department Id is given to Primary key Number 15
each department
Department _Name The name of the department Not Null Varchar 20
Email _Address address Not Null Varchar 60
Page | 80
3
4.2 Design Interface

Hawassa
University Online Grading System &
Part E-Learning
Home Registration Courses Grading E-Learning Login Submission About Us
Sub links
About Hawassa
Reference to University
other sites
News
W3schools
Some Facts related
Grading
Top E-learning site
Online grading system and part e-learning is in Hawassa

University is useful for students and instructors in different aspects.
Home|Registration|Courses|Grading|E-Learning|Login|Submission|About Us |Site Map

copyright@2012/2013
Fig 4.2.1 Home page
Page | 81
3
Fig 4.2.2 Interface for registration: Student

Hawassa
Part E-Learning

As Student
As Instructor/committee
You are registered as student. Please fulfill the following form appropriately
and register.
Student ID:
First Name:
Middle Name:
Last Name:
E-mail:
Phone Number:
Register Reset
Page | 82
3
Fig 4.2.3 Interface for registration: Instructor and committee

Hawassa
Part E-Learning

As Student
As Instructor/committee
You are try to register as Instructor or committee. Please fulfill the following
form appropriately and register.
Inst/Comm ID:
First Name:
Middle Name:
Last Name:
E-mail:
Phone Number:
Job Title
Register Reset
Page | 83
3
Page | 84
3
Hawassa
Part E-Learning
You are try to Login as Student.

Role:
Student
Instructor/Committee
User Name
Password
Login Reset
Forgot Password
Fig 4.2.4 Interface for login: Student
Page | 85
3
Hawassa
Part E-Learning
You are try to Login as Instructor or committee.

Role:
Student
Instructor/Committee
User Name
Password
Login Reset
Forgot Password
Fig 4.2.5 Interface for login: Instructor and committee
Page | 86
3
References
[1] SIMON BENNETT, STEVE McROBB & RAY FARMER, Object Oriented System Analysis
and Design Using UML, 2nd edition, McGraw-Hill Education Publishers, 2002.
[2]. ‘Background-Hawassa University ‘ 27 Oct 2011.Viewed on 17 Dec 2012
http://www.hu.edu.et/hu/index.php/about-hu/background
[3] ALL ABOUT AGILE – BY KELLY WATERS ‘ AGILE METHODOLOGY. What Is Agile? (10
Key Principles of Agile).’ Viewed on 14 Dec 2012 http://www.allaboutagile.com/what-is-agile-
10-key-principles/
[4] ‘10 Advantages Of Agile SDLC | | BootStrapToday BootStrapToday’ 9 Feb 2012. Viewed on
Dec 19 2012 http://blog.bootstraptoday.com/2012/02/09/10-advantages-of-agile-sdlc/
[5] ‘Guidance and Methodology -Data collection methodology’ 31 Dec 2005. Viewed on 19 Dec
2012 http://www.ons.gov.uk/ons/guide-method/method-quality/general-methodology/data-
collection-methodology/index.html
[6] ‘Iterative and incremental development - Wikipedia, the free encyclopedia’ 27 Feb 2008.
Viewed on 21 Dec 2012 http://en.wikipedia.org/wiki/Iterative_and_incremental_development
Page | 87

SYSTEM Requirement and DESIGN For HU On-Line Grading System and Part E-Learning

Uploaded by

Copyright:

Available Formats

You might also like

SYSTEM Requirement and DESIGN For HU On-Line Grading System and Part E-Learning

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

SYSTEM Requirement and DESIGN For HU On-Line Grading System and Part E-Learning

Uploaded by

Copyright:

Available Formats

SCHOOL OF INFORMATICS

INFORMATION TECHNOLOGY PROGRAM

INDUSTRIAL PROJECT ONE: PROJECT DOCUMENTATION

ONLINE GRADING SYSTEM AND PART

NAME ID EMAIL PHONE

Submitted to: Mr Simon Tiruneh

Submitted Date: Feb 11/2013

SYSTEM REQUIREMENT SPESIFICATION..............................................13

Fig 4.2.1 Home page.................................................................................................................................72

1.2 Statement of the Problem

1.3 SCOPE AND LIMITATION OF THE PROJECT

The scope of this project is:

 Show grades for students online without going to their instructors.

Limitation of this project is:

 It doesn’t generate CGPA of students.

1.4The Overall Description

1.4.1Over view of the existing system

1.4.2 Overview of the new system

1.5 Objectives of the project

1.5.1 General objectives

1.5.2 Specific objective

The specific objective of this project is:

1.6 Methodology and Tools

 Individuals and interactions over processes and tools

 Continuous attention to technical excellence and good design

Fig 1.1 Agile software development methodology

1.6.1 Method of data collection

Interview is a conversation or questioning, for the purpose of eliciting information for

 First we will decide to interview to the registrar manager.

1.6.4 Development Tools

1.7 Schedule of the project

SYSTEM REQUIREMENT SPESIFICATION

2.1 Requirement Analysis

2.1.1 FUNCTIONAL REQUIREMENT

HU-OLGS and part E-Learning has the following functionalities:

 Registration: Enables the instructors, grade approval committees and students to

2.1.2 NON- FUNCTIONAL REQUIREMENT

2.3 Understanding the domain

# Short name description

3 Software The programs and other operating information

6 Business model A business model describes the justification of

9 GPA grade point average

Fig3. 1 system workflow

3.1 System Modeling

3.1.1 Business Model

Not Accepted User

Fig 3.2 Prototype process model for the proposed system

3.1.2 System Use Case Diagram

3.1.3 Use case identification

Actors Use cases

Table 3.1 use cases and actors identification

3.1.4 Use case Diagram

Fig 3.3 use case diagram of the system

3.1.5 Use Case Documentation

Use case name: Register

Actors: Users (Student, Instructor, Administrator and grade approval committee).

1) Users select the register menu from the home page.

1) The user enters invalid information