Object-Oriented Modeling Assignment

WKES 2304 Object Oriented Modeling Report

Title: No 9, Distance Learning System

1.1    Project Description

        Distance learning system enable collaboration between two or more learners at a distance. This system consist of 3 users which are the System Administrator, Lecturer and User. System Administrator's responsible to define registration schedule, manage system maintenance, do information renewal, update course information and update user information. The lecturer will be able to register lecturer information, login, update course content, review learning progress, respond to question and request and define coursework deadline. The learner can register learner information, login, access course content, perform learning activites, perform dialogue and group discussion and collaborate synchronously and asynchronously.

1.2   Project Team

Our Team members consist of:

      TIM YEN NI WEK 080080 yenni104@live.com.my

      SHARIFAH KHAIRIN BT SYED MOHD ALI WEK 080069 khairin21@gmail.com

      WONG LAP FOONG WEK 080083 james_lf@hotmail.com

      CHONG WEI JIE WEK 080014 chongweijie88@gmail.com

1.3   Log Activities

Tim Yen Ni - Use Case Diagram, State Diagram
Sharifah Khairin - Class Diagram, Activity Diagram

Wong Lap Foong - Sequence Diagram, Package / Subsystem Diagram
Chong Wei JIe - Collaboration / Communication Diagram , Component Diagram

Do together - Problem Statement, Deployment Diagram, Translating the design into code, Presentation slides for the presentation of the group project

2.1   Use Case diagram

       Use cases are used during requirement elicitation and analysis to represent the functionality of the system. Use case focus on the behavior of the system from an external point of view. Below are the use case diagram we designed for our distance learning system. There is 3 separate package, which are System Administrator, Learner and Lecturer. For each separate package, we define an actor, as well as respective use case that defines the functions of the system visible by the actor.

2.2   Use Case Description

1. The name of the use case is unique across the system
2. Participating Actors which state actors who interact with the use case
3. Brief Condition basically describe the main function of the use case involved.
4. Entry / Precondition are conditions needed to be satisfied before a use case is initiated
5. Exit / Postcondition are conditions that are satisfied after the completion of the use case
6. Flow of events describe the sequence of interactions of the use case. There are 2 columns where the left column explain the steps accomplished by the user and the right column explain the steps accomplished by the system. Each pair of actor-system steps represent an interaction.

Below are the use case description we had done according the our use case diagram: