I showed you how to turn your program idea into a Use Case. Then we turned the Use Case into a Domain Model. Then I showed you how to turn the Use Case into a Sequence Diagram. Then we made the Sequence Diagram into a Class Diagram. Now I’m going to show you how to convert the Sequence Diagram into working code.
I make part of the code in this video. The rest will be made in part 9 of my Object Oriented Design Tutorial. All of the code follows the video to help you learn. To get the other diagrams, just click the associated links above.
If you like videos like this, tell Google [googleplusone]
Sharing is always welcome [nttfblike]
Code From the Video
TestATM.JAVA
Account.java
Card.java
Customer.java
Transaction.java
Great tutorials! I’m porting this to C# for practice and noticed you don’t have BankComputer, BankNetwork, or ATM classes defined in the example code here.
My bad, obviously these are with the next video where they are covered. Forgot these were split across two instances. Thank you!
Not a problem. I should have pointed that out better.
Hi Derek,
what if we have case where two or more classes have reference point to same class? For example, BankComputer and Customer might have reference to Account class, or any other class. Do we need to avoid this, beacuse from BankComputer or Customer we can access to Account?
That really isn’t an issue because objects are just passing values when they pass the objects rather then a reference to the objects.
Sorry Derek but I don’t understand.
Feel free to ask questions