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.


Topics - YogaMatt

Pages: [1] 2
1
Is it possible to use the in-built report generator to report on a selection of classes dotted around my model, so that their operations' signatures are tabulated like so:

Class NameOperationNameParam Name and TypeReturn Type
Class 1OperationX(Rows of parameters)integer

Or similar
Namaste

2
I won't post the message until I know it is OK to do so. Don't want to misuse the forum.

3
General Board / Untapped Feature: "Element Decisions"
« on: August 14, 2017, 09:32:03 pm »
Hi All
Sparx 13 has a feature under Design->Element->Decisions that brings up a Decision Table window in the diagram tab, focussed around the current element.
It has a single Scenario tab with a top pane to add a number of unique scenarios / conditions / not sure?
The tab also has a bottom pane to add a number of conclusions.
F1 / context sensitive help no longer works since I installed the local help files (just take me to the help front page i.e. has lost context sensitivity).
So I'm at a loss about the value and use of this. Anyone have any experience of it and can say what it is good for
Namaste
YogaMatt

4
General Board / Glossary in Version 13
« on: March 11, 2017, 12:57:29 am »
I just can't find it! Help doesn't help! Can one of you kind souls?
Namaste
YogaMatt

5
Automation Interface, Add-Ins and Tools / Archimate 3 model exchange format
« on: February 16, 2017, 01:09:26 am »
Does V13 support ArchiMateŽ Model Exchange File Format for the ArchiMate 3.0 Modeling Language?

http://www.opengroup.org/xsd/archimate/3.0/

Many thanks,

M

6
Having model elements to represent TFS stories, features etc in Sparx EA will support traceability and agile modelling.
We want to avoid rekeying and dual maintenance of the stories, etc in TFS and EA.
So, does Sparx EA integrate with TFS in such a way that TFS stories, etc are synchronised with model elements in Sparx EA? That is, model elements which are the stories and features, etc.


For anyone else reading this post later, and for completeness, does Sparx EA integrate with TFS for:
  • For versioning the code generated from the model?
  • For versioning of the model elements?

7
General Board / Changing Stereotypes
« on: December 06, 2016, 03:31:03 am »
Several hundred model elements were stereotyped "PhysicalDataComponent" (PDC) when they should be "PhysicalApplicationComponent". (PAC)
Manually changing them is one option  ;D

Updating the value in Stereotype field in the SQL t_object table gets you some of the way there. But there seems to be some 'hangover' where the old PDC stereotype still exists as a second stereotype in the browser. It will switch off if I manually go to the element properties and disable that PDC stereotype. Again, manually changing them is one option  ;D

Back to SQL I found that the t_objectproperties table held entries for each element, which were for the tags that came with the PDC stereotype. Deleting these entries cleared the PDC stereotype from about half of my elements. But not all. And now I'm wondering if anyone out there knows the underlying schema well enough to suggest where this ghost is hiding, please?

8
Modelling has proceeded with relationships being drawn between classes.
We want instantiate the classes into objects such that:
  • the classes to become architectural building blocks as defined by TOGAF: the classes should not retain the relationships - they are building blocks and should be freely available to instantiate within baseline and target architectures.
  • the instances retain the relationships that existed between the classes, and the instances appear on the diagrams that the classes had appeared on
The manual effort is onerous. Does this require scripting or is there a pre-canned solution in EA?
Thank you.
 

9
Does anybody know ...

Why does EA enforce a root node to have a second level of "views" before you can add a package to the third level?
Or, put another way, why can't packages be placed directly under nodes? What's the essential difference between packages and views in the browser?

Thanks in advance.

10
General Board / Show Connectors IDs on diagrams
« on: May 18, 2016, 08:33:16 pm »
Connectors have IDs. Is it possible to show them on a diagram?
Any workarounds it not?
Thanks in advance.

11
I'd like to thank very much, everyone involved in making the conference the gem it was: the organisers, the sponsors, the presenters, the delegates and the venue. I had a brilliant time and had plenty of very useful take-home messages.

12
Suggestions and Requests / Locate Classifier from Instance
« on: April 29, 2016, 07:04:38 pm »
Scenario:
Instances of a classifier are in a different location to the classifier in the project structure.
From an instance on the diagram, can locate the classifier (either right click and find classifier, or shortcut Ctrl-Alt-G).

Issue:
When viewing the instance in the browser, Ctrl-Alt-G does not locate the classifier, nor is there a context menu.

Am I missing the trick, or is a feature request in order?

Cheers

Yoga

13
Uml Process / TOGAF and Model Structure
« on: April 28, 2016, 02:01:18 am »
Our team are debating. Faced with the template "TOGAF-ADM" package structure generated from the TOGAF MDG, where do we put stuff? The differing views:

  • Model elements (ABBs/SBBs) all to exist within the appropriate ADM phase folder.
  • Model elements (ABBs/SBBs) all to exist outside the phase folders in a central repository, but artefacts which draw together those elements published in their appropriate ADM phase's folder.

Other considerations are:
  • elements are re-used (and embellished) throughout the phases;
  • so are some artefacts;
  • both baseline and target architecture(s) to be managed in the same model.

Any prior art / experiences, please?

14
Anybody done any integration between EA and EPF?

15
Hi All

There are two very different types of ModelView in EA. One is a model element, accessible from the toolbar on most diagram types, under Artifacts. The other is the Ctrl-Shift-5 "Model Views" window.
I'm asking about is the model element type, which we're currently using to display interface catalogues (see the TOGAF model template for an example).

They work nicely. But the document generation capability in EA disregards it. I can create a template to output the interface connectors, so that's not a major problem. But stakeholders want an output which looks very much like the one you can see in the model. We could do that by running the SQL script directly on the database and export the results to Excel. But that's not joined up when it comes to managing complete documents from place.

Any ideas?

Cheers

YM

Pages: [1] 2