Beruflich Dokumente
Kultur Dokumente
Design
Learning Management System
Introduction
• Learning Management System (LMS) integrates
content delivery, management of learning, access to
learners, and access for content development and
management of learning. The LMS can provide the
infrastructure to plan, deliver and manage your
training programs, but only after careful review up in
front of existing and future studies is conducted.
• An LMS must be capable of handling various
delivery modes online. In addition an LMS must
automate the cumbersome process of learner
enrollment, registration, records, transcripts,
schedule and reports. It must incorporate evaluation,
assessment and testing capabilities.
• The LMS portal tracks learning content or courses
the user is taking and his progress. The LMS ties all
other e-learning components together. The LMS is
the infrastructure or framework used to track,
support, manage, and measure e-learning activities.
An LMS helps manage and measure the entire
learning process.
• Manage assignments
Lecturers can upload, remove and edit all
the assignment anytime. All the assignment
can be view and download by students
without miss any important information.
Besides, the assignment given will confirm
delivered. The assignment also can be
submitted on time.
• Manage quizzes
Lecturers can upload the quizzes and
students can open and do the quizzes online
anytime without wasting the time in class.
Students also can get their marks
automatically on that time.
• Manage announcement
Lectures can upload, remove, edit and
update the announcements, while students
can open and get the announcements.
Use Case Diagram
Regis ter Subject
<<include>>
<<include>>
<<include>>
<<include>>
<<include>>
<<include>>
Upload Quiz
Student
<<include>>
Manage Profile
Upload notes
Lecturer
4.1 BRIEF DESCRIPTION
• This use case is initiated by the lecturer. This use
case will enable the lecturer to insert, view and
remove notes.
4.2 PRE-CONDITIONS
• The user account is verified.
4.5 POST-CONDITIONS
• The lecturer uploads notes.
4.6 RULE(S)
• Not applicable
4.7 CONSTRAINT(S)
• The lecturer can upload one note at one time
USE CASE: DOWNLOAD
NOTES (LMS_05)
Download notes
Student
• 5.1 BRIEF DESCRIPTION
• This use case is initiated by the student. This use
case will enable the student to save, view and
remove notes.
• .
• 5.2 PRE-CONDITIONS
• The user account is verified.
5.5 POST-CONDITIONS
• The students download notes.
5.6 RULE(S)
• Not applicable
5.7 CONSTRAINT(S)
• The students can save one note at one time
Sequence Diagram
Upload note
(Lecturer)
Subject Int erface : System Manager : Note : Note
: Lecturer Subjec t Int erface System Manager
2: send( )
3: display( )
5: send( )
6: display( )
9: send( )
10: upload( )
11: display( )
Sequence Diagram
View note
(Student)
Subject Interface : System Manager : Note : Note
: Lecturer Subject Interface System Manager
2: send( )
3: view( )
Sequence Diagram
Remove Note
(Lecturer)
Subject Int erface : Sy stem Manager : Note : Note
: Lecturer Subject Interface System Manager
2: send( )
3: promptCo nfirmation ( )
5: send( )
6: remove( )
Sequence Diagram
Cancellation
Subject Interface : System Manager :
: Lecturer Subject Interface System Manager
2: send( )
3: cancel( )
Sequence Diagram
Download Note
(Student)
Subject Interface : System Manager : Notes : Note
: Student Subject Interface System Manager
2: send( )
3: display( )
A-1:Press
4: Select note view button
6: send( )
7: save( )
Sequence Diagram
View Note
(Student)
Subject Interface : System Manager : Note : Note
: Student Subject Interface System Manager
2: send( )
3: view( )
Sequence Diagram
Remove Note
(Student)
Subject Interface : System Manager : Note : Note
: Student Subject Interface System Manager
2: send( )
5: send( )
6: remove( )
Class Diagram
<<boundary>>
Subject Interface
<<boundary>>
Register Subject Interface dis play()
<<entity>> prom ptConfi rm ation()
Subject c ancel ()
display()
s e nd()
cancel()
regi s te r( )
promptConfirmation()
s ubs cr ibe()
1..* 1..*
1..* <<boundary>>
<<entity>>
E-mail Interface
Not e
upload() display()
rem ove() cancel()
s ave() 1 1..*
view() 1..* 1
1
<<control>>
System Manager <<boundary>>
<<entity>> 1 1 Profil e Interface
Account
send() 1 1..*
1 validate() display()
1..*
retrieve()
calculate() 1
1
1 1 1
<<boundary>>
1..* Main Interface
<<entity>> display()
Announcement 1..*
1.. *
upload() 1..*
<<entity>>
remove() 1..* <<entity>>
Assignment <<entity>>
E-mail
Quiz
upload()
s end()
remove() upload()
dis play()
save() view()
view() rem ove()
Class Diagram(package)
LMS Manager
LMS interface
<<boundary>>
Main Interface
(f rom Logical View)
<<boundary>>
Register Subject Interface
(from Logi cal Vi ew) display()
display()
cancel() <<bou ndary >>
promptConfirmation() Profil e Int erface
(f rom Logical View)
dis play()
<<bo undary>>
prom ptConfirm at ion()
E-mail Interface
cance l() (f rom Logical View)
s end()
display()
cancel()
LMS Entity
<<entity>> <<entity>>
Quiz <<entity>> <<entity>>
Subject Announcement
(f rom Logical View)
(f rom Logic al View) Account
(f rom Logical View)
(f rom Logical View)
register() upload()
view() upload() retrieve()
subscribe() remove()
remove()
<<entity>> <<entity>>
Note <<entity>>
As signment
(f rom Logical View) E-mail (f rom Logical View)
(f rom Logical View)
upload() upload()
remove() send()
remove()
save() display()
save()
view() view()
LMS Manager
<<control>>
System Manager
(f rom Logi cal Vi ew)
send()
validate()
calculate()
Activity Diagram
(Student)
s tart
Display login
interface
Insert Username
[ No ] and Password
[ Yes ]
Display main
interface
Select
menu
end
Activity Diagram
(Lecturer)
s tart
Display login
interface
Insert Username
[ No ] and Password
[ Yes ]
Display main
interface
Select
menu
end
State Chart Diagram
(Take Quiz)
when[ time<10 minutes ]
Start
/ selectQuiz ()
/ submitAnswer ()
Chec ked
/ cancelQuiz()
/ removeQuiz()
Cancelled
/ displayTotalMark()
Removed NewState
quizDeleted()