Use Case Diagram for Bank Accounts

The assignment is for CDOP3103 Introduction to Object-Oriented Approach, and students are required to draw a use-case diagram representing the actors and use-cases of a case study about different types of bank accounts. The diagram should include features such as account number, customer's name and address, deposit and withdrawal capabilities, interest rates, overdraft limits, and report generation for authorized bank officers.

PENYERAHAN DAN PENILAIAN TUGASAN
ASSIGNMENT SUBMISSION AND ASSESSMENT
_________________________________________________________________________
CDOP3103
INTRODUCTION TO OBJECT-ORIENTED APPROACH
SEPTEMBER 2017
_________________________________________________________________________
INSTRUCTIONS TO STUDENTS
1. This assignment contains only ONE question that is set in both Malay and English.
2. Answer in Malay or English.
3. Learners are to submit assignment only in Ms-Word format unless specified otherwise.
Please refrain from converting text/phrases into picture format such as .gif / .jpeg / print
screen / etc.
4. Download the language version of the assignment template concerned from the
myINSPIRE for preparation and submission of your assignment. Your assignment
should be typed using 12 point Times New Roman font and 1.5 line spacing.
5. You must submit your assignment ONLINE via the myINSPIRE. Refer to the portal for
instructions on the procedures to submit your assignment online. You are advised to keep
a copy of your submitted assignment for personal reference.
6. You can submit your assignment ONCE only in a SINGLE file.
7. Your assignment must be submitted between 30th October until 2nd November 2017.
Submission after 2nd November 2017 will NOT be accepted.
8. Your assignment should be prepared individually. You should not copy another person’s
assignment. You should also not plagiarise another person’s work as your own.
9. Please take note that PENALTY will be imposed on late submission of assignment as
specified in the Registrar’s Office circular 6/2012 (Refer to Registrar’s Announcement in
myINSPIRE).
10. Please ensure that you keep the RECEIPT issued upon submisson of your assignment as
proof of submission. Your assignment is considered as NOT submitted if you fail to
produce the submission receipt in any dispute arises concerning assignment submission.

EVALUATION
This assignment accounts for 50% of the total marks for the course and shall be assessed
based on the Rubrics attached .
You would be given feedback on the assignment before the Final Semester Examination
commences.
PLAGIARISME: POTONGAN MARKAH / PLAGIARISM: MARKS DEDUCTION
Warning: The submitted assignment will automatically undergo a similarity check. If
plagiarism is detected, marks would be deducted as follows:
No. % Kumpulan Pertindihan
(Similarities Group)
% Potongan Markah (Marks
Deduction)
1 0 – 30 0
2 30.01 – 50 5
3 50.01 – 70 10
4 70.01 – 100 100
Assignments found to have similarities under any of the categories above; will not be entitled
to apply for appeal. For learners who fall into the 70.01-100 similarities group, the access
for online appeal for assignment remarking of the subject will be disabled from the appeal
options.

ASSIGNMENT QUESTION
PURPOSE
The purpose of this assignment is to increase the learner’s knowledge and
understanding on use cases.
REQUIREMENT / ASSIGNMENT QUESTION
Consider the following case study:
A bank offers their customers a different types of accounts. All accounts have certain
features such as account number, customer’s name and address, and all customers must
be allowed to deposit and withdraw money. The saving accounts needs to have an
interest rate. Current accounts have an overdraft limit. The withdrawal procedure for
saving accounts is different from that of current accounts. Saving accounts withdrawal
is allowed as long as it does not exceed the limit. On the other hand, current accounts
withdrawal is allowed if it is below the overdraft limit. At any point in time, the bank
officer can check the customers’ accounts and print the details. Only an authorised
bank officer is allowed to generate reports detailing total withdrawal amount and total
deposit amount plus a performance indicator for the bank.
Draw a use-case diagram to represent the actors and the use-cases of the above case
study.
(50)
END OF PAGE

ATTACHMENT
ASSIGNMENT RUBRICS
CDOP3103 INTRODUCTION TO OBJECT ORIENTED APPROACH /SEPTEMBER 2017
Criteria
Weig
ht-
age
Excellent Above average Fair Low Weak Max
Mar
ks
4 3 2 1 0
System boundary:
 Illustration of the system
boundary with proper system
name in the use case diagram.
1
Provided
correct
illustration
with the proper
system name
within the
system
boundary.
Provided
correct
illustration, but
the system
name is not
suitable or out
of the system
boundary.
Provided
correct
illustration, but
without the
proper system
name.
Provided
partially
correct
illustration
such as wrong
placement of
actors/use
cases.
No illustration
or wrong
illustration was
given.
4
.
Actors/Roles:
 Illustration of suitable
actors/roles in the use case
diagram. 3.5
Provided at
least 3 correct
actor/role
illustrations.
Provided only 2
correct
actor/role
illustrations.
Provided only 1
correct
actor/role
illustrations.
Provided not
accurate
actor/role
illustration.
No illustration
or wrong
illustration was
given. 14
Use cases:
 Illustration of all the use cases
in the use case diagram based
on the system functional
requirements.
4 Provided at
least 5 use case
illustrations
with correct
association.
Provided 3-4
use case
illustrations
with correct
association.
Provided 2 use
case
illustrations
with correct
association.
Provided 1 use
case
illustrations
with correct
association.
No illustration
or wrong
illustration was
given.
16

Use case details:
 The details of Savings
Account and Current Account
cases.
 Include Primary actor,
Secondary actors, Pre-
condition, Post-condition,
Main flow.
4
Provided
correct and
complete use
case details.
Provided
correct use case
details, but
with minor
mistakes such
as
wrong/missing
dependency
line/label.
Provided only 1
complete/corre
ct use case
details.
Provided vague
or incomplete
use case details.
No details or
wrong details
was given.
16
Total 12.5 50