Book a Demo

Author Topic: EA's implementation of UAF  (Read 4690 times)

Hurra

  • EA User
  • **
  • Posts: 183
  • Karma: +0/-0
    • View Profile
    • Find me at LinkedIn!
EA's implementation of UAF
« on: May 28, 2018, 06:27:40 pm »
Hello!

I have some questions regarding EA's implementation of UAF. I'm not really sure if I'm using some parts wrong or there is something with the MDG.

I have a high-level operational scenario described in an Operational Structure view, UAF Operational::Structure, composed of OperationalPerformers.

I show information transfer with OperationalExchange and with OperationalPorts.

Now I want to detail an OperationalPerformer to show internal parts, thus using OperationalRole-elements, and the UAF Operational::Structure diagram. However, this is not an IBD and can't show ports on the border/boundary of the block-diagram.

I can create an IBD, but then the diagram is not UAF Operational::Structure. Can I create an UAF Operational::Structure and convert to IBD? How can I place ports on the boundary if the diagram is not IBD?

Am I implementing UAF wrong?

Thanks for any guidance.

always learning!

freek

  • EA Novice
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: EA's implementation of UAF
« Reply #1 on: July 25, 2018, 06:48:12 pm »
I am also struggling to use EA with UAF.  EA still has serious bugs with it's UAF implementation which makes it nearly unusable, unless you disable validation and not use Quicklinks and not try to use UAF::Dictionaries and...

That being said, UAF recommends the Operational structure be implemented in SysML BDD or SysML IBD.  One way to do this is to create a HighLevelOperationalConcept and add an IBD to it, or a Composite Diagram.  The BDD describes the composition and the IBD the exchanges.  Don't know if this helps?