Setting the "status" for diagrams

[stevesavage]

I'd like to be able to set a status attribute for diagrams, the same way I can for elements in the repository.

Currently there is no way to indicate that a diagram has been reviewed and approved etc.

[qwerty]

I'd like to be able to set a status attribute for diagrams, the same way I can for elements in the repository.

Currently there is no way to indicate that a diagram has been reviewed and approved etc.

May I join and additionally ask for tagged values?

q.

[Paolo F Cantoni]

I'd like to be able to set a status attribute for diagrams, the same way I can for elements in the repository.

Currently there is no way to indicate that a diagram has been reviewed and approved etc.

May I join and additionally ask for tagged values?

q.

In other words, you want diagrams to be first class citizens of the repository...

(So do I).

Paolo

[Uffe]

Yes! Please!

[Geert Bellekens]

The problem with all these things is that they would be UML.
In UML a diagram is hardly defined, and it sure is not an Element. So anything added to diagrams (like tagged values) would be a pure EA extension.

Geert

PS. I'm not saying they should add it, just pointing out a potential problem.

[qwerty]

If you allow diagrams then this is an extension to UML anyway. OMG does not detail diagrams in mathematical terms like the rest. But they just assume them to exist per se. Nothing that hinders you to treat diagrams as first class citizens too.

q.

[stevesavage]

I wasn't thinking in terms of UML, I was thinking in terms of an architecture repository made up of catalogs, matrices and diagrams.

I use diagrams to capture view points for my clients, and I want to use the status attribute to support the approval workflow we use for these diagrams.   Currently I have to track the approval using a separate spreadsheet.  

Similarly I'd like to be able to store an object or bookmark visible in the project browser that represents a specific instance of a matrix (matrix profile + target + source), and be able to have notes, status etc. attributes associated with the specific instance.  (if you can already do this let me know)

Same reason, I want to be able to review the matrix with clients to verify the connections, and then flagged the relationship was approved.    

Without these capabilities, we may have to start looking for another solution as the size of our Architecture catalog grows.   Either moving from EA, or investing in a custom extension.

For the other tech heads.

As long as the "last modified date" is set in response to any changes to the diagram/matrices attributes, we can work the SQL to identify when the matrices and diagrams would need to be reviewed, due to changes in underlying elements and connectors.  e.g. last modified date of diagram is older than last modified date of a connector/element represented in the diagram.

[stevesavage]

I should have mentioned, I know you can view the profiles in the Resource browser, I just find the implementation awkward when it comes to using them as part of a project review.

[Doug Blake]

You could overcome this by creating a new Diagram Element an instance of which sits in each diagram and has all the properties you want.

[stevesavage]

@Doug Blake

Good idea for a workaround, i guess that's what I'll have to do for now.

[Paolo F Cantoni]

You could overcome this by creating a new Diagram Element an instance of which sits in each diagram and has all the properties you want.

We use the Diagram Notes element as a surrogate for the diagram.  Works well enough...

HTH,
Paolo