You are on page 1of 8

TMC6054 Object-Oriented Application Development

Laboratory 1 : UML Modeling Rational Rose


Case Study: Student Grading System
Student Grading System is required, in which student can ask the system about grade
they obtain for certain course, courses that they take for that semester, and view course
description. Lecturer also can access the same information as students do, in addition the
lecturer can update student grade.
Exercise 1: Use Case
Task 1:
Create use case model for the Student Grading System.
Use case name: Get Grade, View Courses, (you can name more read case study)
Actor: student, lecturer.

Task 2:
1

Write documentation, or use case scenario in the documentation window for each of the
use case in Exercise 1, Task 1.
1. Student Register Course for that semester.

2. Student can View Course description that are offered in that semester and list of
courses that they had register for that semester.

3. Student can check or view their grade for the courses that take in this Get Grade
option.

4. Lecturer can view course that the student had registered in that semester

5. Lecturer can get or view the students grade.

6. Only the lecturer can update the students grade

Exercise 2: Sequence Diagram


Task 1:
Create sequence diagrams for each of use case in Exercise 1, Task 1, which shows the
interaction among objects Lecturer, Student, Course and Grade.
a) Sequence diagram for student request for grade

b) Sequence diagram for lecturer ask for students grade

c) Sequence diagram for student view all courses that s/he registered

d) Sequence diagram for lecturer view courses registered by student.

Task 2:

For each message in sequence diagrams in Exercise 2, Task 1 (a-d), assign messages
name which depict the operation name to be invoked in the receiving object.
1.
2.
3.
4.

request grade()
request student grade based on courses()
request view courses()
request view registered courses()

Exercise 3: Class Diagram


Task 1:
Create class diagram to represent the relationships (e.g., association, aggregation or
generalization) among objects in the student Grading System. If the relationship is
association or aggregation, specify the cardinality (multiplicity).

Task 2:
For each class in Exercise 3, Task 1, insert attributes, which specify its visibility, name,
type and initial value (if any).

Task 3:
For each class in Exercise 3, Task 1, insert operations, which specify its visibility, name,
arguments (if any), and return type.

Exercise 4: Activity Diagram


Task 1:
Choose one operation from class Student. Define the operation algorithm of the selected
operation by using activity diagram. Enter the activity name.
Activiti diagram register course.

Task 2:
For each transition, enter the event name, event arguments.

You might also like