Book a Demo

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

Pages: [1] 2
1
Structured scenarios in linked notes (e.g. on a ICONIX-style Robustness Dgr) would look much better if there were line breaks between the ahhm... lines, don't you think?

2
Suggestions and Requests / Re: shape scripring/eƶement properties
« on: February 27, 2007, 07:14:52 am »
Hi all

Has anything happened since your posts: Will the new properties be exposed to ShapeScript? Or have they been already?

Regards
Hermann

3
Suggestions and Requests / Read-only mode (per project) for EA full version
« on: February 14, 2006, 01:16:00 am »
It would be very helpful to have a read-only access mode in the full EA version. It should (imho) be on a per project basis, so that it would allow me to give certain users (and groups) only read access in a designated project (with security activated).

There are so many permissons that can be granted (or revoked), why not a general "edit model" permission. Today, you can only use an SQL server read-only
user for that, in which mode EA will present the user with a flood of useless SQL server warnings and make EA almost unusable for him (in addition to making him feel himself responsible for the errors, which he definitely isn't).

So, what do you think?

Kind regards
Hermann Pallasch

4
Suggestions and Requests / Re: Links/drag&drop import between different p
« on: January 26, 2005, 11:15:28 am »
You wouldn't sychronize and the source project wouldn't know either: Just a drag-and-drop import with the addition of the source beeing indicated in the imported item (similar to a link to an item from another package in the same project).

Hermann

5
Suggestions and Requests / Re: Links/drag&drop import between different p
« on: January 25, 2005, 06:55:37 am »
I think I have already "answered" your question in my posting (and in the mentionned discussion thread in the general forum):

Yes, different projects (as far as I know) are in differnt repositories.

EA needn't show the link (through a graphical representation), but just show the source of the imported element (see my UC flow description)

Hermann

6
Suggestions and Requests / Links/drag&drop import between different proje
« on: January 21, 2005, 01:39:41 am »
From a little discussion thread in the general forum I'd now like to make the following suggestion:

It might be useful to have links between items in different projects (which  would allow to split projects into levels in order not to let them grow too big).

IMHO the thing should/could work in the same way as it now works between the packages of the same project:

Use Case Basic Flow:

USER drags element from 'foreign' project onto diagram

SYSTEM shows dialog with 'Paste element options' (possibly the same as with a drag from

another 'internal' package: Simple Link; Instance of Element; New Child)

USER makes choice

SYSTEM places element on diagram, with subtitle "(from Package x in Project y)"


I don't think graphical representations of the link would be necessary. The whole feature now

to me seems more like an drag and drop-based import feature on the level of selected elements,

although tracebility back to the original element in its original project should be maintained

(assuming the element still exists there, otherwise we'd have an error message)
 
With this feature, we could start projects from elements available in other projects, e.g.  to

separate big business modelling projects from a group of smaller software projects based on

them (on their business actors and/or business use cases) without mangling everything into one

immense project.

7
General Board / Re: floating licence concurrent users and read-onl
« on: February 13, 2006, 07:06:53 am »
Hi Thomas

No, I don't think so: It's a repository-based shared model and some people (who do work with local EA fiels and the full version) should just read in the shared model.

The EA security meechanism doesn't offer a read.only setting, you can only use an SQL server read-only user, which then present the user with a great number of useless SQL server warnings and make EA almost unusable for him (in addition to making him/her feel  themselves responsible for the errors, which they definitely aren't).

What do you think?

Thanks and kind reagrds
Hermann

8
General Board / Re: floating licence concurrent users and read-onl
« on: February 13, 2006, 06:19:16 am »
It would be _very_ helpful to have a read-only access mode in the full EA version. It should (imho) be on a per project basis, so that it would allow me to give certain users (and groups) only read access in a designated project. There are so many permissons that can be granted (or revoked), why not a general "edit model" permission.

Kind regards
Hermann Pallasch

9
General Board / Re: Links between different projects?
« on: January 13, 2005, 01:58:18 am »
A drag and drop-interface that does the same thing (plus some annotations about the element's source and some tracing options) would sitll be nice, don't you think?

Hermann

10
General Board / Re: Links between different projects?
« on: January 12, 2005, 09:56:13 am »
Will do, THNX

Hermann

11
General Board / Re: Links between different projects?
« on: January 12, 2005, 05:28:42 am »
Thanks for your fast responses!

I'm afraid I wasn't too precise with my question concenting links elements form other projects ;-)

IMHO the thing should/could work in the same way as it now works between the packages of the same project:

Use Case Basic Flow:

USER drags element from 'foreign' project onto diagram

SYSTEM shows dialog with 'Paste element options' (possibly the same as with a drag from another 'internal' package: Simple Link; Instance of Element; New Child)

USER makes choice

SYSTEM places element on diagram, with subtitle "(from Package x in Project y)"


I don't think graphical representations of the link would be necessary. The whole feature now to me seems more like an drag and drop-based import feature on the level of selected elements, although tracebility back to the original element in its original project should be maintained (assuming the element still exists there, otherwise we'd have an error message)


With this feature, we could start projects from elements available in other projects, e.g.  to separate big business modelling projects from a group of smaller software projects based on them (on their business actors and/or business use cases) without mangling everything into one immense project.

What do you think?

Kind regards
Hermann Pallasch

12
General Board / Links between different projects?
« on: January 12, 2005, 03:21:00 am »
I'm relatively new to EA and need a bit of advice (beyond RTFM...) once in a while: does anybody know, whether it's possible to have links between items in different projects (which would allow to split projects into levels in order not to let them grow too big)?

Kind regards
Hermann

13
Uml Process / Re: Newbie question
« on: April 16, 2007, 03:10:36 am »
I absolutley agree with you in that the object instance in an activity - even if going through varius states - is one and  the same (and not, like it has to be expressed in EA, multiple    instances of the same class): The object's ID is/would be the same for all those representations.

So I strongly support the idea of (optionally) allowing multiple representations of an object on the same diagram: The clutter in activity object trees (and in their documentations on paper or in HTML!) will vanish at once!

Another efficient use of this (new) feature will be the use of the object on <<assembly lines>> in Erikson-Penker style diagrams.

So please Sparx give us the (configurable) option of showings objects (in different states) multiple times on a diagram.

Kind regards
Hermann Pallasch

14
...to the current element and linking it to the Element Note feature of that same element.

I'm sure, someone has already scripted this tedious task. I'd be immensely grateful!

Hermann

15
Thanks, Neil, I'll give it a try!

Hermann


Pages: [1] 2