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

Pages: [1] 2 3 ... 6
Suggestions and Requests / Re: Embed reference data in MDG technology
« on: January 29, 2013, 12:09:15 am »
Besides that, it might be beneficial to have a similar peace of functionality on a document basis (Document constants). That way, Things like for instance Author, Document version, etc could be defined from outside the document template which makes it possible to create different documents with their different metadata.

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

Hmmm, ok. I don't have a really good idea about how they implement such a feature request in this case. I had the idea that Sparx will take a look in this thread, combine all ideas together and implement them in future releases.

On the other hand it could harm to explicitly suggest the other features as well.

I'll notify them.

You're right. That's what I meant.  ;)

Simon made this one a feature request allready. They'll look in this thread for other features concerning auto name counting, so I guess posting to support is not needed specifically.

Hi Marcel,

Thanks for the reply.

Adding the auto name as a prefix could be an option.  I will log the
feature request with the forum link so other suggestions can also be
taken into account.

Best Regards,

Simon Cotching

O, I understand. Sounds very nice!
I guess I could allready post these options to Sparx. Who knows, it might be even suitable for build 833.

Implement a configuration menu in "Settings" -> "Auto name counting" configuring options below:
  • The allready available "Activate button"
  • Enable auto-naming for elements created otherwise then dragging from the toolbox (Though I think this should always be done)
  • the ability to back fill deleted names
  • stereotype auto-naming

Profiling doesn't sound very bad.
Though one question here. You're thinking about a disable option. But isn't this allready implemented as with the "Activate" chackbox on the right side of the "Auto name counter" configuration?
Do reinform me if this is not what you meant!

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 / Re: "RealisedBy" RTF option for elements
« on: October 08, 2008, 09:36:29 pm »
Ok, then I'll wait for build 833. Is there allready an idea when this build is expected?

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).

Suggestions and Requests / Re: Some needs in documentation generation
« on: September 18, 2008, 02:38:44 am »
I think you're right that document generation can be boosted with some additional or more flexible functionality.

Though, I think some subjects in your post are allready covered.

- hability to follow "relationship": for example,the hability to find all object which are aggregating (or agregate this element). This is a real problem in usecase report, when i whant to know whitch arctor is linked to my useCase...

If I'm right you should be able to do something like this with an element called: "model document". This element has a tagged value called: "Searchname" and "Searchvalue". I'm still exploring this functionality myself as well, but it sounds like a possible match for your issue.

- more flexible recursivity in package : i maybe need only 1 level under, not all levels... i need flexibility in titles numbering too, the level are not corresponding to model levels...

Recursivity in packages is not really flexible, though you can deside not to generate RTF for child packages or child elements. But I guess that's where flexibility stops as well.
I don't actually understand what you mean by synchronising the title numbers to level numbers. Why would you want to synchronise these?

General Board / Re: Poor Visual Quality of Diagrams generated to W
« on: December 12, 2014, 01:07:25 am »
Same problem here.
Problem occurs on a virtual machine on which wide-screen displays are connected. Set resolution is 1920x1080 and documents are generated with diagram format set to 'metafile'. When generating a document, the elliptical use case elements show up as rounds. So the image seems to be generated with proper height, but smaller in width.
When setting the screen resolution to 1280x1024 and generating the same document without any changes whatsoever, the images are being generated as expected.

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 / Re: RTF Template show Aggregation?
« on: May 03, 2013, 12:34:04 am »
You do have the option in the RTFtemplate (or the document generation dialog) to filter out all other connectors but the one you want to document.

To do that: Right click on the RTF template, select 'File..' -> 'Document options'. In the exclude connector type field, you can enable only your connectors.

Don't know if this is exactly what you want, but hope it is!

General Board / Re: RTF templates...
« on: February 26, 2013, 08:30:55 pm »
It totally depends on how you design your template(s).

I think that you want to use a master document, but it's hard to say with the limited info on your model and template(s).
But, if you create a master document with for instance 2 model documents, you could make model document 1 create some title page with whatever content you would require. The second could layout your content in another way.

Besides that, check out the manuals. There's a fairly great amount of proper manuals about RTF templates.

Hope this helps.

Pages: [1] 2 3 ... 6