UML and Inheritance

OOP Assignment 6

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 this 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.  The example used here will be very similar but not identical to the one you have coded in class.

Learning goals:

• Creating UML Diagrams
• Introducing inheritance for complex projects

Part 1: Introduction (40%)

Read this very short introduction to inheritance: What is inheritance?

You can do this in Lucid Chart or just a regular Google Doc.  Regardless, create the new document called BankAccount UML and share it with your teacher.  Need help with Lucid Charts?  See the last page for screenshots.

Create a title called Inheritance and UML

Define inheritance as it relates to OOP.  If you copy and paste a definition, add a link to the source.  

In a few sentences written in your own words, explain how it could relate to one of the following:

• a program about biology (such as mammals, human, cows)
• a game with different types of bad guys.

Part 2: Superclass UML (30%)

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

Simple Example of the Style

Part 3: SubClasses UML (30%)

There are no right or wrong answers for this part.  Your goal is to show me you have a basic understanding of inheritance by thinking about how it might work.  You will NOT need to code subclasses for now so do not worry about how complex they might be.

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 for this assignment are to:

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

They should be set up as follows:

Want to use Lucid Chart?

In Google Drive… New… Lucid Chart… select UML (see image)... Blank UML

To add text

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