Object-Oriented Programming Assignment 3 - UML Diagrams: Bank Account
 

Unified Modelling Language (UML) Diagrams are used for 2 reasons:
 

• To plan large scale projects
• To share the design of already planned project with your team

We will be focusing on one type of UML called the UML Class Diagram.
Watch 3-minute video. It seems to be a bit unprofessional, at first, but is actually a VERY effective description of 

UML Class diagrams: https://www.youtube.com/watch?v=Vy_gLkxuCnw
In this assignment, you will using a UML Diagram to PLAN a simple banking program.
Make

• Creating UML Diagrams
• Introducing inheritance for complex projects
   

Part 1: Introduction
It may be a good time to review the introduction video to lesson 4.13 on CodeHS if you are a little rusty on how
inheritance works.

 

Lesson 4.13:https://youtu.be/XtEaCJt8Paw

Please use Lucid Chart to make this diagram. You will want to make a new document that you will eventually hand in as a PNG image file with the name OOP3_UML_LastName.png.
 

1. Create a title called "Part 1: What is inheritance?"
2. Define inheritance as it relates to OOP. If you copy and paste a definition, add a link to the source.
3. In a sentence or two, explain how inheritance could relate to or be used in one of
the following:

 

a. a program about school courses (such as science, biology, chemistry 20, physics 30 AP, etc.)
b. a game with different types of bad guys.
 

Part 2: Superclass UML
To help you get started, have a look at the instructions on how to access the UML shapes at the bottom of this
document, and check out the first 5:10 of Lucid Chart's own UML Diagram video: https://youtu.be/UI6lqHOVHic
Consider the following BankAccount superclass:
 

Every bank account needs 5-7 instance variables:
 

• account ID
• client name
• balance
• 2-4 others of your choice

Every bank account needs the following methods:
 

• deposit
• withdraw
• getBalance
• chargeFees
• one other of your choice

Create a UML Diagram for this BankAccount class. Your diagram must include the following. Below the list is an
example of the style you should use:
 

• Private (-) or public (+) indicators. You can decide how you feel they should be used but be sure to at least have
  one of each type.
• For variables, indicate the variable name and type
• For methods, indicate a parameter type and return type if either apply
   

 

Part 3: SubClasses UML

There are many types of possible child classes of the BankAccount class:
 

• savings account
• chequing account
• student account with low fees
• investment account
• high interest account with a minimum balance and high fees
• others?

Your goal is to choose 2 of these sub accounts and add a UML class Diagrams for each. The requirements are to:
 

• add 1 or more new variables
• add or alter 3 methods

Once you have made your subclasses, be sure to connect them to your BankAccount superclass with arrows to indicate inheritance. (Don't worry about the style of the arrows. The default ones are fine. The arrows just need to point in the right direction.)

 

Using Lucid Chart:
To make regular text, drag the 'T' icon in the below image onto the diagram area to the right.

To access the UML shapes:

To make a UML , drag in the UML Class Diagram icon into the screen

Double click on the text inside to modify it.
 
 
 
 
 

Transcribed Image Text:

Simple Example of the Style Stuffed Animal + name: String + age: int -hasFur: boolean + setName(newName: String): void + isFuzzy(): boolean Simple Example of the Style Stuffed Animal + name: String + age: int -hasFur: boolean + setName(newName: String): void + isFuzzy(): boolean