Service Allocation Diagram Anomaly using Business Architect

The method scope depends on the products. Therefore, it is expected behaviour that something created with SOA Architect will not be 100% the same in Business Architect. As you can see, the objects are not removed from the model, but you can't fully see them nor alter them. But no information is lost.

Fortunately, I am seeing different behavior today in Business Architect.  The Knowledge Category object is appearing in the Service Allocation Diagram (not as a "ghost") and I can associate it to a Capability as desired.



I will assume, for the time being, that the reason the object was excluded previously was the result of some unexplained product malfunction.  I will monitor for any future occurrences and pursue a resolution as required.   Thanks.

Hi Dick,

you probably just used a wrong filter while accessing your database...

I have done more investigating and I have substantiated the behavior I wrote about at first.  There is no filter explanation and I am confident it can be replicated by anyone using the licenses mentioned.

I would like to comment that it is conceptually perplexing why the Knowledge Category object is included on a Service Allocation Diagram with a SOA Architect license and excluded with a Business Architect license.  Any help providing a conceptual explanation about why this is the case would be appreciated  To me, definition and association of a Knowledge Category to the objects allowed in a Service Allocation Diagram is within the scope of both the Business Architect and SOA Architect.. 

The second item of interest is that I have correlated the change in behavior (ie re-appearance of the "ghost" object) with the specification of the license key.  I am able to start Business Architect with a SOA Architect license key.  When doing so and then opening a Service Allocation Diagram having an occurrence of a Knowledge Category object, I will see the Knowledge Category object as if I was working in SOA Architect.  If I change the license key to one that authorizes use of Business Architect, then the same Service Allocation Diagram will show the Knowledge Category object as a "ghost".

In short, I don't think it was intended that I be able to utilize Business Architect with a SOA Architect license key.