Products

Home › Forums › eaDocX queries › Conveyed information items

Home › Forums › eaDocX queries › Conveyed information items

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • 11 May 2015 at 12:51 pm #8088
    Chris Pearce
    Participant

    I know for a while that people have asked about displaying the content of conveyed information items on a diagram report as part of the connector information has this been added to eaDocX?

    Ie if i have two objects and a connector diagram and the connector conveys an information item, can that information item be reported?

    11 May 2015 at 5:17 pm #8089
    eadocX Support
    Participant

    Yes.
    When you are “adding attributes of a related element”, when you select a Relationship Type of ‘Information Flow’ then you get two additional attributes in the drop-down for ‘Attributes of the Relationship’.
    These are:
    Information Items – which prints the names of the conveyed items
    Info Items – hyperlinked – which prints hyperlinks to the info items, where they are printed elsewhere in the document(this seems the most reliable technique)

    31 January 2016 at 7:45 am #8090
    jopirx
    Participant

    But “conveyed items” can be defined not only for connectors with the InformationFlow type. At least actually in EA so. How to be in this case?

    31 January 2016 at 1:05 pm #8091
    eadocX Support
    Participant

    What are your conveyed type So? If they are associated with the connectors, then seen above. If they are elements, then print as an element.
    What exactly does your model look like?And what do you want your document to look like? Easier to answer the question if we know what you are trying to do 🙂

    31 January 2016 at 5:04 pm #8092
    jopirx
    Participant

    It isn’t difficult to explain (but, my English isn’t really good, sorry :blush: ).

    In our case in model it is necessary to define references between a business process step, the participant (actors) of this step and “use cases” of system which is applied by the participant (actor) within this step.
    In an attachment simple, but not absolutely typical Use Cases diagramm (2.png). The problem that as the triple connector isn’t possible in EA (as well as in UML), sense of binding “operation” – “participant/actor” – “use options” exists only in the context of concrete the diagramm.
    Any attempt to unload from rather big model the description of UseCase in a look “use case” – “actors”- “operations in which actors participate” won’t be correct as not in all operations the actor uses this option of use.
    Unloading on logic of a chain “use case” – “operations in which it is used” – “actors who participate in operation” also isn’t correct as not all participants of operation use this “use case”.

    It turns out it is necessary to bring use context in at least one of scheme connectors. An example in attachment (1.png). As besides in EA there is no universal opportunity to link an element to a context of connector (of course noa as connector source or target) (well or I don’t know it), the good candidate is Information Flow Realize which in fact ties to a connector practically any type essence with sense “is transferred on this connector”. Application of course not really beautiful, however what to do?

    Now a question if I want to construct unloading in the document of use case by means of “attributes of related elements” – as I am able to do it? Information Flow Realize not avaible for “association” type connector (4.png).

    20 February 2016 at 6:27 am #8093
    jopirx
    Participant

    Up topic. 🙂

    22 February 2016 at 3:25 pm #8094
    eadocX Support
    Participant

    If I understand you correctly, the your first screen-shot shows two different ways of saying the same (similar?) thing:
    – one where you have an Actor, linked to a Process, linked to a use case
    – one where the Actor is linked to the Use Case, and the Process is a ‘conveyed item’ of that link.

    Assuming that this is true, I’m not sure this is what ‘Conveyed Item’ if for. Just because it’s allowed in EA doesn’t make it a good way to do things. I don’t know if UML allows for conveyed items on any connector type apart from ‘Information Flow’. I think if I saw your second type of model, I would be confused 🙂

    What exactly is the problem with the first way of doing things, with an Actor, linked to a process/operation, linked to a Use Case? This is how I always model this problem, and eaDocX is happy to model ‘multi-hop’ relationships like this.

    24 February 2016 at 9:28 am #8095
    jopirx
    Participant

    If I understand you correctly, the your first screen-shot shows two different ways of saying the same (similar?) thing:
    – one where you have an Actor, linked to a Process, linked to a use case
    – one where the Actor is linked to the Use Case, and the Process is a ‘conveyed item’ of that link.
    …

    Not some things.I described a difference as could. I, of course, will try to make an example of model and the document. But it will demand some time.

  • Author
    Posts
Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.

Compare licence prices

Choose the licence that’s right for you and your team

Prices

Download a free trial

Download eaTeamWorks today for several free for life features, plus no obligation, 30-day trials of all the products: eaDocX, ea Revision Manager, eaSheets, Model Expert and PortfolioManager. Discover for yourself why we sell the world’s best-selling Enterprise Architect extension.

Download