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 - peterc

Pages: [1] 2
General Board / Re: Creating a Navigation Cell from a Matrix Profile
« on: January 11, 2018, 10:46:40 pm »
They have probably been designed for diagrams but do work for a matrix.

I've just found a quicker way of generating them:
  • Drop a hyperlink onto the diagram, selecting the desired matrix
  • Change the Stereotype to NavigationCell

The only disadvantage is that it is not possible to select the images that diagram navigation cells have.

Not sure about action pins specifically, but on some elements the source of an element is hidden by unchecking "Show Namespace" found by right clicking on the diagram, select properties and then the Diagram selection and then within Appearance.

I was dropping ValueType elements, so I have changed and dropped a Property on - all works now.

If anyone else comes across this in the future, it is necessary to change the Type by opening the Property element and in the dialog under Properties - Property selecting a Value Type. Confusingly, the Type in the Properties window (not the dialog that is visible when opened from the element in the Project Browser) is not editable. That's too many uses of the word Type in windows/dialogs labelled Property but doing different things for my mind to cope with!

General Board / Creating a Navigation Cell from a Matrix Profile
« on: January 05, 2018, 02:03:12 am »
What is the correct way to generate a Navigation Cell for a matrix?

If I create a Navigation Cell from a diagram and and a Matrix hyperlink, I can then copy the link in the hyperlink onto the Navigation Cell so that the Navigation Cell opens the Matrix rather than the diagram. But... in doing so the nice image of the Navigation Cell disappears (and I shouldn't really have to copy the hyperlink!). There is a nice matrix image available in the Navigation Cell image library so hopefully there is a better way.

So, I have added Value Type elements to the diagram and they are in the Project Browser, but when I delete them off the diagram they do not appear in a "values" compartment. I do have "ports" and "parts" compartments (and they correctly follow the behaviour that if the element is on the diagram then it is not listed in the compartment; as soon as I delete them from the diagram then they appear in the compartment).

I think I am doing something wrong in dropping the ValueType element onto the Block - the parts and ports are constrained in the diagram to be within the boundary of the Block. The ValueType elements can be dragged anywhere on the diagram. Where they are on the diagram determines where they are in the Project Browser (they become a sub-element of the Block when dropped on top of it).

According to page 21, Block elements can display any number of compartments. A ValueType element should appear in a "values" compartment.

I have turned on everything I can find under the Diagram Properties and the element's Features & Properties dialogues but cannot get ValueTypes to appear in a "values" compartment. I can get the ports compartment to display (if I delete the port from the diagram after creation). I can create a new Port by right-clicking on the element and selecting New Child Element. Similarly flow properties that are created as a child and deleted from the diagram show in a "flow properties" compartment.

I can't create a ValueType as a child element from that menu, but having created a Value Type I have moved it manually to make it a child of my Block element, but even then it doesn't appear in a compartment. There might be a clue in not being able to create a ValueType from the right-click menu, but that then also contradicts the SysML Models Guide.

I am using SysML 1.4, but have tried 1.3 as well and that is no different.

General Board / Re: Exclude connector type has no effect
« on: December 15, 2017, 12:22:30 am »
Are you using a "Defined Document" that you have created and "Auto Generate"? I have raised a bug report with Sparx that doing that the filters are not obeyed, with an acknowledgement that it will be fixed in a future release. They work fine if you first select from the Defined Document "Generate Document" and then "Generate".
If you have excluded all connectors then anything that you are reporting on in relation to connectors ought to have been filtered out.
I also seem to recall seeing some incorrect effects introduced on some of the version 13 beta releases in relation to document generation, but subsequently fixed after I reported them. So it might be worth trying a different version (either the latest or an older one depending on your current version) to see whether it behaves differently - it may be that you are correctly specifying the filter but it is not being obeyed in whichever version of EA you have installed.

General Board / Re: Adding Borders
« on: December 12, 2017, 11:59:54 pm »
That's ok - it's what the forum is for (and I've had my share of answers before).

General Board / Re: Adding Borders
« on: December 12, 2017, 02:16:43 am »
Did you want the border on the diagram in the model, or when it is exported? There is an option to add the border and diagram name to exported images? I think the name is on the top left (but stand to be corrected) - the option is in the Preferences under Diagram - Diagram Frames.
Just wondering as you mention fragments so you might be referring to saving the model as images.

I may have got the wrong end of the stick...

I presume that you have some parameter (e.g. Element Name) with a Paragraph Style of Heading 1 or Heading 2 etc.

If you have two templates then you can start from a different Paragraph Style in each.

For example, if you have a package called Requirements and in one template set the Paragraph Style to be Heading 2 and include Element Name in the heading then (assuming you use numbered headings) you will have something like "1.1 Requirements".

If you then choose in your other template Heading 3 as the Paragraph Style then the package name would be "1.1.1 Requirements".

As I said, I may have misunderstood your need.

General Board / Defining the paragraph indent level
« on: July 27, 2017, 06:45:08 pm »
I have copied and modified the Use Case Details template that is provided with EA.

Having modified it for my purposes, some of the tables have different indent levels. In the output I can edit the indent level in Word and some are 0.48cm and others 0.95cm. Even removing the indent (by selecting Align Left) and then using "indent left" under paragraph, I cannot get the indent levels that have been used.

I cannot find the equivalent to the Word paragraph dialog where the indent level can be typed in precisely, which would allow me to type the indent amount.

Does anyone know how to set the precise indent?

All the lines have the same style.

I appreciate that this is an old topic, but I have the same issue - I want to include the Use Case diagram within my document as a child diagram of the Use Case. Not being able to include the diagram within the child elements section, I have generated a template that includes the Element Name in the heading, text extracted from specific parts of the Use Case element and the image of any diagram.

When it processes the child element it includes the Activity diagram, but also the auto-generated name of that, e.g. "Use Case_ActivityGraph", in my case as a heading one level lower.

In order to exclude documentation of all the elements on the Activity diagram, the best option that I have come up with is to use the option under the Structured Specification to generate an Activity with Action diagram. When I generate the document I use an Exclude Filter to exclude the elements I don't want to report on, e.g. Action, ActivityFinal, ActivityInitial, FlowFinal. (I have to use Activity with Action diagram - if I choose just Activity, then it is not possible to use a filter to separate the type of diagram from the type of element on the diagram).

Has anyone found a better way to include a Child Diagram?

What I would really like to avoid is the child Name appearing in my document output as well, but that appears because I am including the Element.Name, which is obviously wanted.

General Board / Re: Specific Diagram in Template
« on: May 25, 2017, 07:18:44 pm »
Do you need it to be dynamically generated from SQL?
If you need is satisfied by static diagrams then you can drag and drop the diagrams you want onto another diagram - Choose the Diagram Frame option when you drop it.

General Board / Re: best practice for baseline and target arch models
« on: April 20, 2017, 06:42:34 pm »
I suggest that you have a look at the Time Aware modelling concept recently introduced (EA13 I think but I stand to be corrected). I have used it to track changes to requirements not Archimate elements so you'd need to see if it works for you the way you expect to make changes. Time Aware models certainly save you copying everything over as they use your existing model except for where you introduce changes.

General Board / Re: SysML Requirements - Copy relationship
« on: March 17, 2017, 12:34:24 am »
Not sure if this is the answer, but have you noticed that the SysML text field is "<memo>" and you edit it manually by clicking it on the ellipsis ...? Does you script write into the memo within the SysML1.4 "text" tag or directly into the tag? Hopefully it still has <memo> and the ellipsis after your script. Just wondering whether you are accessing the tag correctly or whether while you are storing the text it's in the wrong place.
Might be worth posting your script (or at least a fragment of how you are accessing the element).
Might also be worth writing a script that just accesses both your script modified element and a manually created requirement to display the text - you should obviously expect the script to display the "text" field value the same regardless of whether your script has written to it or you have manually created a requirement. If they don't then it would start to point at how the script is accessing the tag.

Pages: [1] 2