[Corelinux-public] AbstractFactory again...

[Frank V. C. <fr...@co...>]

Upon further consideration the change yesterday:

                               1     uses >     1.*
AbstractFactory[key:Identifier]<>----------------->Allocator
                                     -theAllocators

this UML implies that the AF has a collection Allocators.

While this works, it also implies a keyed association (e.g. std::map)
which I was going to happily implement. I don't think that is desirable
in light of the fact that as a class library we would better serve
users/developers by allowing them their choice of allocator storage once
the derive to their problem domain.

Therefore I am recommending we take out the association at AF and
provide a implementationClass stereotype in the diagram that shows a
association without semantics, then AbstractFactory becomes abstract
with pure virtual get, set, remove protected methods.

Can I get a amen?

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux