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 - Martin Terreni

Pages: 1 ... 46 47 [48] 49 50 51
Bugs and Issues / Linked document short cut for packages
« on: January 30, 2008, 07:12:40 am »
When right clicking on package within diagram it is possible to choose "linked document". this option it option is not available for packages from the project tree.
For other elemets it is avaiable for both.

bug issued

Bugs and Issues / Re: Can't make vertical fork from activity
« on: January 20, 2008, 08:50:43 pm »
Thank you for your bug report. I have fixed this for the next release of EA.

Bugs and Issues / Can't make vertical fork from activity
« on: January 19, 2008, 09:56:41 pm »
More EAUI godies  :P

When using autolink from "Initial activity" you have the option to create either vertical or horizontal join, but when doing the same from an activity you have are given no choise, just horizontal join.

God the things you find when you work ;)

Bugs and Issues / Re: BUG in version control handling?
« on: December 20, 2007, 02:39:12 am »
Good work Michael!

Uml Process / Re: Packaging Components vs UML
« on: April 21, 2009, 01:42:16 am »
Sapevo!  ;D

Uml Process / Re: Packaging Components vs UML
« on: April 17, 2009, 05:58:22 am »
Just an irrelevant question - do all users with Italian family names use the same avatar?
Are we a conspiracy?.... :o

Uml Process / Re: Packaging Components vs UML
« on: April 17, 2009, 05:55:44 am »
I think it will be great to be able to add the package component suplyed\required interfaces, or at list to be able to mark some nested interfaces as such (even better this option).

Actually the second option would be grate from bottom up  modeling. you create your interfaces, mark some methods as supplied interfaces. state the required ones and then you can see it in the package component!

hooo boy, am I a dreamers...

Uml Process / UML Fever: Diagnosis and Recovery
« on: May 22, 2008, 01:15:28 am »
Very insteresting (though old) assay:

I'm in charge of UML implementation in my company and I do have to fight to keep it simple. people have the tendency to require 200 diagram types where actualy 4-6 are required (for the whole supper duper development process top to buttom inlcuding busines process analisys) the may reuse a ton of code, but not a single diagram frustrating....

Uml Process / Re: Componenet package?
« on: May 08, 2008, 01:29:00 am »
in deed it is a little problematic, this was the reason that from I wanted to put packages under the component, so it wil hold its own design.

Uml Process / Re: Componenet package?
« on: May 07, 2008, 11:03:21 pm »
still the package containing the components essence will be just linked to the component instead of being the component it self. Though with the lack of other options this is a good one.

Uml Process / Re: Componenet package?
« on: May 07, 2008, 10:01:45 pm »
You are right about that and in deed we tend to be less requirements oriented and more architecture oriented.

Uml Process / Re: Componenet package?
« on: May 07, 2008, 09:39:09 pm »
I guess the problem is that my point of view design == code, I don't see our design as a document, but as a reflection of the system. If the classes under package X are the classes realizing component X and the UI in package X is the UI of component X - then package X== component X. The component hsould exist in one and only one place in the model (project tree), I don't like the concept of having the definition of the component in one place and its logical symbol in another. It also makes the component element, as stated, just a symbol, since the actual content\interfaces\signatures and such - are actually define in a package elsewhere.
A component is a whole independent world, if I export it and import it into another model it should work seamlessly and I should be able to use the imported package as is , without the need to create a local representation of it.

I think I find it hard to explain my wholeistic view of the design as equal coding. I would expect the component desing to be like a JAR package I can move independently from place to place - begin able to see its external interfaces or its inside definition.

Hope I'm making sence.

Uml Process / Re: Componenet package?
« on: May 07, 2008, 07:08:44 pm »
1) From your quote it seems that the component may own a package.
2) EA indeed allow you to mark a package as nested under a component, it is just not possible to nest it in the project browser.
 That seem to leave us with something that is just a technical EA problem.
Please correct me If I misunderstood your quote.

Uml Process / Re: Componenet package?
« on: May 07, 2008, 06:45:36 pm »
In UML v2 they have clean-up the concepts of packages and components. A package is now only a grouping of model elements, and a component now can contain other model elements and act as a namespace.

This is exactly the problem. I want to have under the component a package for the classes, a package for the table, a package for algorithms, a package for UI... all those things that really ARE the component.
Since I can't have packages placed under components - that I have to use packages as componenets.

Uml Process / Re: Componenet package?
« on: May 07, 2008, 06:06:17 pm »
The issue is the the whole package (with it sub packages) is realizing the component.

Thanks though.

Pages: 1 ... 46 47 [48] 49 50 51