Messages

1

General Board / Modeling Object for Reports

« on: April 13, 2018, 06:41:53 pm »

Hi!

This may be a silly question? but I am wondering how people represent report objects in models. I have searched the EA documentation and my friend "Google", but all the references to "reports" have to do with reporting information contained in EA not report objects for the system being documented.

I can represent them as a Class (with attributes for the fields), but I was wondering if there is a specific object/element/stereotype which is generally used. I have searched through the entire catalog of elements, and I did not see anything.

I thought the EAReportSpecification stereotype might be what I was looking for, but that seems to relate to EA generated documentation.

I can use an "Artifact", but I didn't see a stereotype for soemthing like "system output report".

I hope this question makes sense.

Thanks for any input/assistance.

2

Suggestions and Requests / Re: Relationship between/to Attributes

« on: December 12, 2017, 06:06:39 pm »

Thanks, guys!

I appreciate the information.

3

Suggestions and Requests / Relationship between/to Attributes

« on: December 01, 2017, 06:59:27 am »

Hi everyone!

Bear with me, as I am somewhat inexperienced with EA.

I have defined a set of Data Entities as a Class type, with the Attributes representing the fields associated with the entity. So far, seems like the right way of doing things.

I am now looking to be able to model the data handling for a set of interfaces. What I would like to be able to do is to create a connection between Entity A.name and Entity B.name. It seems this would be easy to accomplish using a Relationship Matrix, but I don't seem to be able to get the Attributes as either a source or a target in the matrix. It seems to be restricted to elements. Am I expecting too much?

In the same way, I would like to be able to report on relationships between my Attributes and my System Use Cases, where a specific use case uses or modifies Entity A.name. I can model this (somewhat) by associating the Entity with the Use Case and attaching the connector to an Element Feature (the Attribute). The problem I have with this method is that I need to create a separate connection for each Attribute (a lot of work!).

One thing I can do, is to model the interaction between the Entity and the Use Case and suppress the Attributes which are not used using the Features & Visibility functionality. While that makes a nice diagram, I don't seem to be able to reproduce that in an extract document. (Note that I am using eaDocX to generate documents, and they have already indicated that they don't have this functionality available.)

Going the route of making individual connections for each Attribute/field, allows me to get what I need (sort of), but I'm not sure it's worth the work.

Anyone have any suggestions (particularly using the Relationship Matrix, if that's possible)?

Thanks!!

Tom