Software Engineering Stack Exchange is a question and answer site for professionals, academics, and students working within the systems development life cycle. It only takes a minute to sign up.
Sign up to join this community
For teaching purposes, I'm trying to replicate in a more faithful way from this conceptual UML (from wikipedia):
In a "so-so" real world example, in my case, families of Loans and Insurances:
So, can it be considered a valid GOF Abstract Factory?
Have I followed all the original principles? Or does it needs any kind of fix?
Your diagram corresponds to an abstract factory according to the GoF.
In the original GoF, the diagrams did not use UML but a slightly modified version of Rumbaugh's OMT, which did not make difference between class inheritance and interface realization.
From an UML point of view, the dotted arrow already represents the interface realization. There is no need to add an «extend» keyword which in UML is meant for use-cases and means something different. Morevoer in java extends is used for class inheritance, which would add to the confusion in your diagram. Simply let this keyword out.
It's not necessary, but I'd show the keyword «use» for the dependency between the client and the abstract factory, and «create» for the products, because it helps the diagram to better understand the purpose. But this is a stylistic comment that you can ignore.
