Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Thelonius

Pages: [1] 2 3 ... 15
General Board / Re: .rtf documentation
« on: April 29, 2016, 01:15:26 pm »
Thanks guys for responses - very helpful!

Yes - I would like to know how to store either a .rtf or a .docx in the Sparx model - which means I should be able to link to that document in a variety of ways. I presume I can edit that document outside of EA? Have found "Linked Documents" content. Presumably I have a bit of choice about where in the project browser tree I am able to store .docx docs? Wondering where and how I'd add them to a model. Drag and drop?

I'm still considering alternative approaches - one of which would be to show a hyperlink in a diagram - possibly connected to an element - and the document is retained in the corporate SharePoint environment. I presume the hyperlink option only opens the document - it does not allow # URL "anchors" to designated a specific point within the document?

The "Artifact" icon looks potentially useful - but it doesn't seem to allow me to draw a connector between it and an element in a diagram. Presumably the connector is known only in the specific scope of a single diagram - ie if I placed that element in a new emptly diagram and selected "insert related elements" - the Artefact would not appear? 

What I originally wanted / how I wanted to do it doesn't seem possible. But - in the short term - it looks like I will be able to put some kind of link or link object in a diagram, connect it to one or more elements somehow - and the link will open the linked document.

I have given up trying to get the .rtf generator to generate .rtf output from a model that I can use. Creating a template that only generates a minimal amount of the types of content I want is too hard. Too many nested tickboxes. I don't seem to be able to eliminate certain text from the output. Documentation is a bit sparse.

It would be nice if the Archimate icons behaved like the UML element icons do wrt indicating a linked document with the small red "A" icon.

Archimate is getting kind of popular out here in user land (finally). I'm currently contracting in a very large AU gov agency that is using Sparx. Everyone's using Archimate. I think a lot of business analysts and non-software-engineer / architects are starting to realise that UML is probably most relevant for application software technical design and MDA generation of code for application scaffolding and DDL. Sparx appears to be continuing to focus most development effort on UML. The Archimate implementation could be improved IMHO :-)

Are Sparx working closely to assist Biner to further develop their BEASI plug-in? Or is that an arms-length relationship?

Thanks again for your assistance!


General Board / .rtf documentation
« on: April 28, 2016, 11:52:09 am »
I'm starting to think that putting documentation in .rtf documents in the repository is a good idea.

However, I have not yet figured out how best to use .rtf documents in Sparx. I searched for - but did not find - specific recommendations or help files.

Specific questions:

Once you've created a .rtf document - how do you find it again? How can you create a hyperlink to it that you can put into multiple diagrams?

If I create a .rtf document for an element - say an Archimate application component - can the icon for that element be made to graphically indicate the existence of an .rtf document? So that I can see that there's something there?

Where in the project browser are .rtf documents to be found?

Thanks :-)

Suggestions and Requests / Re: Linked document indicator
« on: April 13, 2016, 05:21:29 pm »
Me too.

Sparx Archimate 'Hide Connector' Defect Reproducibility Narrative:

01. Connect an Archimate data object to an Archimate application component using the 'accesses' relationship - relationship is shown on diagram. Be happy.
02. Nest the data object in the application component - relationship is drawn from edge of application object to the data object
03. Note that this looks a bit naff
04. Select accesses relationship. Select 'Visibility' > 'Hide Connector' to hide accesses relationship when data object is nested.
05. Confirm relationship still exists in the project browser - it does.
07. Drag the data object outside of the application component. Relationship connector should be displayed. It does not display. Note that "Composition" relationship does display when nesting other Archimate elements.
08. Wonder why.
09. Select data object.
10. Select "Insert Related Objects..." and click check boxes to get relationship to display on diagram when data object is _not_ nested
11. Confirm via investigation that the 'accesses' relationship does, in fact, continue to exist in the project browser, but refuses to display.
12.  Delete data object on diagram. Drag data object from project browser to diagram. 'Accesses' relationship appears.
13. Wonder why.
13a. Experiment to reveal that 'hide connector' appears to be permanent when invoked, and the only way to get ANY connector to appear again to ANY object - even when not 'nesting' - is to delete the object on a diagram and drag the object onto the diagram again from the project browser.
13b. Speculate that this may be unintended behaviour by Sparx developers.
14. Raise topic in Sparx Systems Forum.
15. Wait for illuminating comments - or sympathetic murmurs - from forum contributors.

Suggestions and Requests / Re: 8.0 diagram enhancements
« on: July 15, 2010, 08:27:52 am »
Some of us are listening, as KP has demonstrated. However, once you have aired and refined your wishlist, you will have to submit it to Sparx Support as a feature request (or several, thereof) in order for them to log and sanction the requests.

Roy - that may be the case - but in past when I (and others, from what I read on this forum) have lodged bug reports or feature requests - it seems that these simply go into a black hole. Sparx doesn't even send an automated response saying "thanks - got it". This, plus the total silence from Sparx on the roadmap or product strategy for EA - has led me to form the impression (right or wrong) - that Sparx may not be developing a roadmap or product strategy. As I watch the perfectly valid suggestions coming from the user base - I don't hear anything encouraging or substantive coming back from Sparx. A few diligent Sparxians are monitoring the forum and contributing excellent suggestions for how to use the tool and implement workarounds, but that's not sufficient to keep me recommending Sparx to my customers or TOGAF 9 students.

I'll put it bluntly to you, Roy, and to whomever is in charge of the Sparx EA product:

Sparx has got to lift it's game. Especially when it comes to communicating to it's customers.

I'm moving on to Orbus iServer with my company. I'll continue to use Sparx as a personal UML / Archimate tool. I regret having to say that I think iServer is going to significantly erode a highly profitable (and loyal) segment of Sparx's market that Sparx has been relying on for so many years.

I hope I'm wrong. :(

Suggestions and Requests / Re: 8.0 diagram enhancements
« on: July 07, 2010, 01:52:14 pm »

But nobody from Sparx is listening anyway, so who cares?

Suggestions and Requests / Re: 8.0 diagram enhancements
« on: June 23, 2010, 08:00:39 am »
Santa is off sailing his yacht - leaving the oil well problem for others to solve ...

And ... no indication of professional courtesy or 'customer centred' product strategic thinking directed toward the good people who pay for their licenses.

As in 'We acknowledge your concerns and we intend to do something about it in release n.n'.

Wouldn't that be nice.

I don't mind the god-awful inconsistency of presentation and function as much as I mind the lack of concern with customer communication.

Good point, Skiwi. I've noticed this too.

Reason probably is there were 2 different people programming these two functions.

Suggestions and Requests / Re: 9.0 diagram enhancements
« on: September 21, 2011, 08:04:36 am »
Thanks for your persistence, skiwi. You're a better man than I am.

Suggestions and Requests / Re: Multiple instances of element in diagram
« on: August 30, 2012, 12:51:49 am »
This idea has been suggested many times before.

It gets my vote, but I've given up hoping for it.

Suggestions and Requests / Re: Multiple instances of element in diagram
« on: February 23, 2009, 08:36:55 pm »

What if the 'duplicate' was merely a 'ghost' image - not a real component / element - just a replicant that referred back to the single 'real' element?

How would that be different to the (exisiting) "instance of" type?  ;)


Not sure, Oliver. But let me use an example to find out what you're referring to.

So if I have a 'Component' element in a busy, large, complex diagram, and it would be really useful to have a copy of the same element on the same diagram just for presentation purposes - with connectors from the copy to certain other components - how can I create an 'instance of' one of the Components and have both on the same diagram?

Or does my question belie my lack of understanding of the nuances of UML?

Suggestions and Requests / Re: Multiple instances of element in diagram
« on: February 22, 2009, 12:36:54 pm »
Then remove the non-UML model types from EA. I'm talking about flowcharts, and analysis diagrams where you just need to get your artifacts on a diagram to help present a picture of your enterprise to a bunch of executives.

Sean, I accept your motivation and see your issue. However the problems of duplicate elements will remain, especially when it comes to connecting elements together, changing appearance, creating references or searching in diagrams. This is regardless the type of elements or diagrams you are creating and I assume that the efforts of implementing a clean solution (touching various aspects in the model and diagram handling) which is satisfactory for most application are rather high not justifying the cause.


No arguments here, it's a modeling tool not a presentation tool. However as you climb the chain in an organization eventually you need presentations that even numb minded executives with marketing degrees can 'understand'. Visio it is for now.

What if the 'duplicate' was merely a 'ghost' image - not a real component / element - just a replicant that referred back to the single 'real' element?

Even connections from other elements to the 'ghost replicant' would - in terms of the UML model and repository - show up as being connected to the one single 'real' element?

Thinking laterally here ... we need to preserve the integrity of UML - but it would be nice to be able to create simpler presentation material for 'numb minded executives'  ;)

Suggestions and Requests / Re: Set label visibility for all connectors
« on: February 28, 2012, 04:25:04 pm »
Yes, your furniture very nice. Post pictures your furniture to see here.

Suggestions and Requests / Re: Archimate 2.0
« on: February 23, 2012, 09:05:03 am »
Yes, that would be wonderful, wouldn't it? Don't hold your breath. The Sparx implementation of ArchiMate needs a re-think. The ArchiMate meta model is strongly typed, especially the relationships. Sparx EA is UML-centric. UML meta models are relaxed and casual. With the Sparx ArchiMate implementation, you can connect anything to anything, unfortunately. The relationship rules are voluntary, and you have to memorise them. Which is not a good idea. Then there's the quality of the graphics in Sparx. Other ArchiMate tools enforce the strong meta model rules of ArchiMate. Have a look at Archi - which is free, but is being used by professional architects. ArchiMate is looking like a growth skill for solution architects. Sparx should give their support for ArchiMate considered thought. I am the eternal optimist. :)

Pages: [1] 2 3 ... 15