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

Pages: [1] 2
Suggestions and Requests / Embed reference data in MDG technology
« on: January 19, 2013, 02:11:21 am »
I created a custom model including some documentation packages and RTF templates. These RTF templates also use some project constants to create a proper front page with authors etc.
Creating the technology and reusing it through the model wizard works fine.
But how can I embed the project constants (reference data) in the MDG technology (or MTS file)? At the moment I can only think of seperately importing the reference data from XMI seperately from adding the model package to a model.

Thanks in advance

Suggestions and Requests / Adding auto name counter to requirement elements
« on: September 23, 2008, 06:31:26 pm »
When creating a requirement through an element (lets say a use case element) and making it an external requirement after that, auto name counting is not applied to that requirement. This could mess up the requirements naming of the project when adding requirements again from the project browser.

In my opinion, when creating requirements from within an element, the auto name counter should be added to the requirement name when it is made external.

While Sparx asked me what I would suggest for a feature request, I would like to know what your opinion is about this?

Now I'm playing a little more with this auto name counting... Wouldn't it be nice to make auto name counting available for element stereo types instead of UML types only!?
In my case, I can make custom stereo types and give them there own auto counting. Like "FR 001-" for requirements which are of stereo type "Functional" and "NFR 001-" for requirements which are of stereo type "Non functional".

Suggestions and Requests / "RealisedBy" RTF option for elements
« on: October 08, 2008, 12:59:51 am »
I'm trying to work around not being able to simply add a relationship matrix to RTf documentation. I wanted to do this by specifying a template for only the relationship matrix in which you can sum all of the requirements from the model and show all elements that realize the requirement next to it (with a 2 columned table or something).

Now I could find a way to sum all elements which "Realise" some other element, but that's not what I want. I want to show it the other way around, by which elements a specific (requirement)element is "Realized by".

That way, you could iterate all (Requirement)elements in the RTF generator and just list the elements that the (requirement)element is  "Realise by".

What I would like:
RequirementRealised by
FR 1.0UseCase 1
UseCase 2
FR 1.1UseCase 3
UseCase 4
FR 2.0UseCase 1
UseCase 5

What I won't like:
RequirementRealised by
UseCase 1FR 1.0
FR 2.0
UseCase 2FR 1.0
UseCase 3FR 1.0
FR 1.1
UseCase 4FR 1.1
UseCase 5FR 2.0

Anybody any idea if, and if so, how I could do this with build 832?

Suggestions and Requests / Extended auto name counters
« on: September 22, 2008, 11:06:02 pm »
I'm using auto name counters on requirements. All goes well until I delete an element (ctrl + del). Then the auto name counter just carries on increasing its number while I would suspect it to adjust its auto numbering to the amount of elements that are in the model.

So, for instance.

I add 3 requirement elements with auto prefix FR-001 FR-002 and FR-003.
When I now ctrl + del requirements FR-002 and add a new one after that, the new requirement gets auto numbered FR-004 where I would like it to make it FR-002.

I would say this is not that much a bug, but just limiting functionality of the auto name counters. In this version it is just a number increasing with every element add of that type. I would like to see it has a little more intelligence and look which numbers are not used in the model (not present in the project browser).

General Board / Howto properly document element relations (RTF)
« on: May 02, 2013, 11:55:10 pm »
I would like to document all links to an element, but not document the element itself. This is the way I'm trying:

[highlight]element >[/highlight]
Element {Element.Name} targets Element: [highlight]connector >[/highlight][highlight]target >element >[/highlight]{Element.Name}
[highlight]< element< target< connector[/highlight]
[highlight]< element[/highlight]

Problem here is that the RTF generator just takes a connector which is attached to the element, and documents its source or target (depending on the section chosen). That way you always end-up with the element being linked to... itself.

To clarify:

Element a (source) has an association with element B (target). Documenting all connector targets of elements A and B ends up nicely telling:

Element A targets: Element B

But for Element B it says:

Element B targets: Element B

And that's not what I want. Element B doesn't target anything, it only has a connector connected with it's target point to it.

Hope you can help

General Board / Increased heading level diagram elements
« on: February 08, 2013, 12:19:50 am »

I'm generating reports from diagrams containing elements from the package where the diagram is in as well as elements from external packages.
In the RTF template editor, I added sections package -> diagram -> Element (left empty) and Package -> Element in which I format the layout of the elements.

Now when I give the elements Name a heading level, it seems that the heading levels of the external elements is 1 higher than those of the internal elements... Strange because then you get things like:

1 Package_Heading_level_1
   1.1 Package_Heading_2 External_diagram_element_1 External_diagram_element_2
        1.1.1 Internal_diagram_element_1
        1.1.2 Internal_diagram_element_1

How can I overcome this?

General Board / Document a package reference
« on: January 23, 2013, 12:48:21 am »
Packages generated from model documents only process elements modelled in the package which is added to the document model. All goes well in that way.

Something like:

 |->Package1 <-- documenting only this complete package works fine
 |     |->Elements
 |     |->Package2
 |     |     |->Elements
 |     |->Package3
 |     |->Elements
 |     |->Package5

I have a package with some child packages.
Now, what I like to do is to document Package4 like it was a child package of Package3, but I do not want to move or copy the package to avoid modeling things twice.
So something like a reference from package3 to Package4 or something?

Anyone any ideas?

Thanx in advance

General Board / Howto couple a DB project to GIT repo (EA 9.3.932)
« on: August 08, 2012, 05:46:00 pm »
I am setting up a project environment for multiple projects in which I want to control project data and code in GIT and use EA for designing the projects.
To do that in a suitable way, I want to be able to put my EA design in GIT as well. Now as GIT is not supported by EA, I'm trying to figure out another way to do this but haven't found it yet.

What I have is 1 EA SQL Server in which each model represents a project.

What I want is to be able to put all relevant data per project (read: EA model) to be exported and checked in in GIT along with the version of the project relating to the design.

The problem with exporting to XMI is that I can't seem to add baselines in them (baselines next to GIT, because I do want to see what differences are being made between baselines which is not possible using GIT).

What is the best way to do this?

General Board / [Small note] Using status colors on actors
« on: January 24, 2011, 06:56:49 pm »
If you've enabled some status colors for actors, note that the color doesn't show up when using an actor showed in rectangular view. This is because the element itself seems to have become a 'class'-type in rectangular view somewhere under the hood while it still is shown as an <<actor>>.
So if you still want these rectangular actors to show their status color, go to 'Settings' -> 'General types' -> 'Applies to' and check 'Class'. Then the colors do show up.

Not that much of a problem, but might just be handy to keep in mind.

(Using EA 8.0.864)

General Board / Pictures in page header
« on: October 16, 2010, 12:02:55 am »

I intend to use a master document for generation of a requirements document.

Fact is that I imported a Word rtf-template with headers, footers, table of contents etc in the master template. Then generate the requirements paragraph next to it.

The first problem is that pictures in the header (and first page header) are showing up proeperly in the template editor. Though when I generate the master document, the pictures do not seem to be put in the document. All other information in the footer (page numbers, document information etc.) is present as it should.

Does anyone have any idea why this doesn't seem to work?

I'm using the corporate edition, floating license, version 8.0.857 together with word 2007.

Best regards,

General Board / Inserting document author in RTF
« on: July 08, 2008, 06:46:01 pm »
What I want to do is probably quite simple, but I can't find a solution.

I'm trying to simply add an author to a small summary on the front page of an RTF document. Though you can assign an author to a package in EA, it wont let you insert it in the package filed in the RTF templates (rightclick between the package-identifiers and note no author there).

I also tried inserting field names, but I don't really know where in the model they get there data from.

How should I do this? It can't be that hard...

General Board / RTF Child package formatting
« on: September 25, 2008, 12:25:24 am »
Is there a way for the RTF generator templates to generate child packages just like all other packages, but then with (for instance) a page break before?

If I enter a pagebreak only to the child package section of th RTF template, it logically only shows the page break in the word document and forgets about all the elements in this child package.

If I enter a pagebreak in the normal package section, it interferes with the package name which I would like to enter as a "Heading 1". Problem is that this Heading 1 style in the Word document, allready has a page break before. So the generated RTF document will show 2 page breaks. And that is also not what I want.

I can't seem to work this out.

General Board / Relationship matrix in RTF
« on: September 16, 2008, 10:15:40 pm »
I haven't found a direct way to include a relationship matrix in a generated RTF document. Is there a way to do this other than exporting to CSV or PDF and copy-pasting it in a Word-document?

Bugs and Issues / Bug: Incorrect conversion file link in note field
« on: January 15, 2013, 09:28:35 pm »
In the note field of an element, there is an option to add a hyperlink to a word or some text. Select text -> Click hyperlink symbol on the note editor and select File link. Browse to the file using the provided browse button and select the file (in my case mapped drive for a location on the network (Z:\bla\dir1\somefile.doc maps to \\server\documents\bla\dir\somefile.doc).
The hyperlink looks ok in here. When adding a hyperlink to a file to a word in a note (showing Z:\bla\dir1\somefile.doc). Click ok and hoover over the hyperlinked text in the note field. Also here ok, hold ctrl + click the link and the file is opened.

Now when I generate this elements note through the RTF editor, it seems the link is changed in the RTF doc to: \\server\documents\bladirsomefile.doc. So somewhere half way down the link, the box with backslashes seem to have been depleted or so.
Next to that, I also have the same file linked to a package (package properties -> files) to add it to a reference section of the document to generate. In this context, the file hyperlink is generated properly.

Hope someone is able to reproduce and sparx is able to fix.

Bugs and Issues / Bug in RTF generator
« on: January 15, 2013, 03:00:13 am »
Again a bug in the RTF template editor.

Create a new template and insert section model -> glosary.

Generate the document and all seems fine.

Add section packages to the template, save and generate.

All seems fine.

Deselect the Child packages section (which were automatically added by EA when adding the packages section), save and generate. Wow, there are section headers in the RTF file instead of them being interpreted...

Add the child packages section again and the modules section is interpreted properly again.

Please Sparx, things like these are going wrong in the RTF editor for so long now. Please thorougly review the RTF generator.

Best regards.

Pages: [1] 2