Re: [Skunkworks] Cloud Structure of SkunkWorks KE in OOP design

And a clarification on my words above i.e conflict of interest. Before there is hulabaloo, negativity and assumptions about using such words, I use them in context of the drawing. Creating SkunksWorks as a super class would mean roles have to change and so would structure. This creates duplication and repetitiveness which is unnecessary. When using my drawing, consider it from an OOP view. For me, the case of skunkswork KE as an entity for further development is no longer a discussion. Good luck to others who may wish to re-define. Rgds. :-)