sistem analysis design-LMS portal

System Analysis And System Analysis And DesignDesign

System Analysis And System Analysis And DesignDesign

Learning Management SystemLearning 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.

• Learning portals organize information making on-line learning easy to access. The learning contents organized and provide a variety of course offerings from various locations on a single web site. E-learning portals top the list of effective training and educational strategies.

• Essentially, an e-learning portal is a virtual environment set up by an organization to give users access to knowledge. These portals have also been called e-learning centers, online education centers, internal portals, corporate universities and virtual universities. Whatever they are called, they are merely vessels, frameworks, or infrastructures for training, learning and assessing knowledge and competency.

Main functions of the System

• Manage notes Lecturers can upload, remove and edit all

the notes anytime and student can view and download the notes given anytime.

• 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.

• Contact lecturer through e-mail Students and lecturers can be connected

through email. In many cases students can ask questions and discuss problems with lecturers

• Update and view profile The student’s information can be edit,

update and view online.

• Manage announcement Lectures can upload, remove, edit and

update the announcements, while students can open and get the announcements.

Use Case Diagram

Lecturer

Register Subject

Subscribe Subject

Upload Notes

Download Notes

Upload Assignments

Download Assignments

Upload Quiz

Upload Announcements

Open Announcements

Manage Profile

Send E-mail

Student

Log in

<<include>>

<<include>>

<<include>>

<<include>>

<<include>>

<<include>>

<<include>>

<<include>>

<<include>>

<<include>>

<<include>>Take Quiz

<<include>>

USE CASE: UPLOAD NOTES (LMS_04)

LecturerUpload notes

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.3 CHARACTERISTIC OF ACTIVATION• Event Driven (on lecturer’s demand)

4.4 FLOW OF EVENTS

4.4.1 Basic Flow • This use case begins when the lecturer click

the subject button.• The system will display description of the

subject.• The lecturer will click note button. • The system will display list of notes.

• The lecturer will click upload button. (A-1: Click view button) (A-2:Click remove button)

• The system will show a form that needs the lecturer to insert title and note. Then they will click upload button. (A-3:Cancellation)

• The system will upload the note and show the note.

4.4.2 Alternative Flow A-1: Click view button (LMS_04_02)• The lecturer can click view button to view selected

notes. The system will view the full notes.

A-2: Click remove button (LMS_04_03)• The lecturer can click remove button to remove

selected notes. The system will remove the notes

A-3: Cancellation (LMS_04_04)• The system will cancel to upload note.

4.4.3 Exceptional Flow• Not applicable.

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)

StudentDownload notes

• 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.3 CHARACTERISTIC OF ACTIVATION• Event Driven (on student’s demand)

FLOW OF EVENTS5.4.1 Basic Flow (LMS_05_01)• This use case begins when the student click

the subject button. • The system shall display information of the

subject.• The student will click note button. • The system will display notes on the screen.• The student will click save button. (A-1:Click

view button) (A-2: Click remove button). • The system will save the notes.

Alternative Flow A-1: Click view button (LMS_05_02)• The student can click view button to view

selected notes. The system will display full notes.

A-2: Click remove button (LMS_05_03)• The student can click remove button to

remove selected notes. The system will remove the notes.

5.4.3 Exceptional Flow• Not applicable

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)

: LecturerSystem Manager : System Manager

Subject Interface : Subject Interface

Note : Note

1: Press note button

2: send( )

3: display( )

4: Press upload button

5: send( )

6: display( )

7: Insert data

8: Press upload button

9: send( )

10: upload( )

11: display( )

Sequence Diagram

View note

(Student)



Note : Note

1: Press view button

2: send( )

3: view( )

Sequence Diagram

Remove Note

(Lecturer)



Note : Note

1: Press remove button

2: send( )

3: promptConfirmation( )

4: Press Yes button

5: send( )

6: remove( )

Sequence Diagram

Cancellation

: Lecturer

System Manager : System Manager


1: Press cancel button

2: send( )

3: cancel( )

Sequence Diagram

Download Note (Student)

: StudentSystem Manager : System Manager


Notes : Note

1: Press note button

2: send( )

3: display( )

4: Select note

5: Press save button

6: send( )

7: save( )

A-1:Press view button

A-2:Press remove

Sequence Diagram

View Note (Student)

: StudentSystem Manager : System Manager


Note : Note

1: Press view button

2: send( )

3: view( )

Sequence Diagram

Remove Note (Student)

: Student

System Manager : System Manager


Note : Note

1: Press remove button

2: send( )

3: promptConfirmation( )

4: Press Yes button

5: send( )

6: remove( )

Class Diagram

Register Subject Interface

display()cancel()promptConfirmation()

<<boundary>>Subject Interface

display()promptConfirmation()cancel()send()

<<boundary>>

E-mail Interface

display()cancel()

<<boundary>>

Profile Interface

display()

<<boundary>>

E-mail

send()display()

<<entity>>

Quiz

upload()view()remove()

<<entity>>

Announcement

upload()remove()

<<entity>>

Assignment

upload()remove()save()view()

<<entity>>

Account

retrieve()

<<entity>>

Note


<<entity>>

Subject

register()subscribe()

<<entity>>

System Manager

send()validate()calculate()

<<control>>

1..*

1

1..*

1

1..*

1

1..*

1

1..*

1

1..*

1

1..*1 1..*1

1..*

1

1..*

1

1..*

1

1..*

1

1..*

1

1..*

1

1..*

1

1..*

1

1..* 11..* 1

1..*

1

1..*

1

1..*

1

1..*

1

Main Interface

display()

<<boundary>>

1

1..*

1

1..*

Class Diagram(package)

LMS Interface LMS Entity

LMS Manager

LMS interface

Register Subject Interface

display()cancel()promptConfirmation()

(from Logical View)

<<boundary>>

Subject Interface

display()promptConfirmation()cancel()send()

(from Logical View)

<<boundary>>

Profile Interface

display()

(f rom Logical View)

<<boundary>>

E-mail Interface

display()cancel()


<<boundary>>

Main Interface

display()


<<boundary>>

LMS Entity

Subject

register()subscribe()


<<entity>>

Note



<<entity>>

Assignment



<<entity>>

Quiz

upload()view()remove()


<<entity>>

Announcement

upload()remove()


<<entity>>

E-mail

send()display()


<<entity>>

Account

retrieve()


<<entity>>

LMS Manager

System Manager

send()validate()calculate()

(from Logical View)

<<control>>

Activity Diagram(Student)

start

Display login interface

Insert Username and Password

Display main interface

valid Password?

Select profile

Select email

select subject

Display profile interface

Display email interface

Display Subject interface

Select menu

Select Note

Select quiz Select announcement

Select assignment

Download note

Download quiz

Download announcement

Download assignment

end

[ No ]

[ Yes ]

Activity Diagram (Lecturer)

start

Display login interface

Insert Username and Password

Display main interface

valid Password?

Select profile

Select email

select subject

Display profile interface

Display email interface

Display Subject interface

Select menu

Select Note

Select quiz Select announcement

Select assignment

Uploadnote

uploadquiz

Uploadannouncement

Upload assignment

end

[ No ]

[ Yes ]

State Chart Diagram

(Take Quiz)

Start

Displayed

/ selectQuiz ()

Answered

[ timeDue=10 minutes ] / takeQuiz ()

Submitted

/ submitAnswer ()

Checked

/ calculateMark()

Cancelled

/ cancelQuiz()

Removed

/ removeQuiz()

NewState

/ displayTotalMark()

quizDeleted()

when[ time<10 minutes ]

sistem analysis design-LMS portal

Documents

Transcript of sistem analysis design-LMS portal