Messages

1

General Board / Re: Packaging Component auto dependencies

« on: January 27, 2014, 08:49:31 am »

Thank you! I'll give it a try and let you know!

2

General Board / Packaging Component auto dependencies

« on: January 25, 2014, 05:16:48 am »

Hi. If i have the following tree:

Root
--PackageComponent1
----Class1
--PackageComponent2
----Class2

and if class1 has an association with class2, how can I generate/mainain a new diagram which has the PackageComponent1 automatically depending on PackageComponent2, and if, later on, the class1 looses its association with class2, the connection of package1 and package2 is lost?

The goal is to know if the upper packages are dependents because there is some dependency in the tree underneath after a forward/reverse engineering.

Thank you

3

Uml Process / Re: Project changes and Application documentation

« on: November 09, 2012, 09:10:55 pm »

Thanks. I'm new in EA so I still have a long walk to do, but certainly you help me to find a path.

I invite everyone else to show the community how they address this issue: Design and know what changes happen in project revision X on an application Y using DRY principle.

4

Uml Process / Re: Project changes and Application documentation

« on: November 09, 2012, 02:41:19 am »

To both, thank you for your help.

Querty: The <<changes>> is almost the same as the putting annotations, so yes, it almost has the sames problems. At each new version it is required to clear that stereotype
Thank you for the "extend" issue, I've done it in a middle of a training session and didn't pay attention to this.

Geert: Glad to hear that others have address this problem and I'm not alone.  
Do you copy the changes to another document, like word or you create another EA project?
How do keep track the changes if the design takes several days so nothing is forgotten?
And, finally, how do you mark the changes? (probably this answers the second question)

Thank you.
/me

5

Uml Process / Project changes and Application documentation

« on: November 08, 2012, 10:41:23 pm »

Hi,

First of all thank you for reading this. I need your help on the following. In our company we follow CMMI level 3 maturity process and, one of the items that we must follow is to have the documentation about a project and the documentation about the application.
Imagine the scenario that we already have an app running for 3 years now and the customer asks that a functionality must be changed.
How can we in uml, and particular in EA, address this issue?

My solution are the following, none of them address all my requirements

* I can design changes in two different models, one for the actual changes and another the current state of the app. Not a DRY principle and can lead to errors.
* I use only one model and put annotations everywhere, but if the app is going to suffer plenty of changes there can be annotations everywhere.
* I use only one model and rely on the EA baselines. Unfortunately this is almost like doing a diff on a text file. I can't see, visually, the diagrams before and after, so the visual part of the uml gets lots.

For instance the image below shows the typical bank scenario where the system contains a withdraw functionality and the sponsor now asks that the customer might choose, or not, to print a receipt.



How can I design the diagrams so that the programmer knows what to implement and on the same time he knows what the system does as a whole?

Thank you