Think about the information that is found on a Visa or Mastercard. As you have seen in your readings and videos this week, object diagrams represent what an object $$is$($the information it holds$)$ and what it $$does$,$ how it changes and distributes that information. You may have seen the terms $$accessors$$ and $$modifiers$,$ or $$sets and gets.$$ These refer to what an object does.

Since a credit card is an inanimate object, we have to $$pretend$$ that the credit card can give the information it has. The first step is to design a UML class diagram for a Visa or Mastercard. $($Hint: the chip on newer cards and the magnetic strip are meaningless in this exercise, so don$$t bother with them.$)$

Microsoft Visio, which you might have, has diagram collections for UML. If you want to use this, that$$s okay, but don$$t waste an inordinate amount of time with it$.$ Hand$-$drawn diagrams will be accepted if they are done well with a straight$-$edge.

Next, and this may take some research, design a class in Python, Java, or C$++$ to reflect this UML diagram.

Finally, imagine you are buying something online using the credit card. Using two entities, your PC and the card, draw a sequence diagram to represent the process of entering the card information. To clarify, to the best of your recollection indicate in the diagram the order in which you enter the details of the credit card. Below is and example from a sequence diagram:

Note that the function, getCCnumber$()$ should belong to the credit card in your object diagram.

Submit screenshots and$/$or pictures of your diagrams AND your object code to the space provided in uLearn.