Messages

1

Uml Process / Re: Keeping an overlook in class diagrams

« on: December 11, 2008, 09:55:47 pm »

Thank you Oliver.  You helped a lot.

When deleting connectors, EA is asking if it has to be deleted or just hidden from the view. There is also an option "visibility" in the connectors  context menu.

To hide class elements from the view, the solution isn't to search in the elements context menu, but in the class context menu (feature visibility). My mistake was to search in the options of the methods and attributes.

The problem is solved.  

2

Uml Process / Keeping an overlook in class diagrams

« on: December 09, 2008, 10:28:11 pm »

Hello,

in my current project I have to build a 100% consistent uml model to the code. While modelling the class diagram I observed an increasing chaos in the overlook.
For example there is a package with 5 GUIs(written in Java) in it. When I drag the class from the EA Project Browser into the modelling window the graphic shows every attribute of the class. Since there are many components like buttons or textfields, the graphical representation of such a class is very huge. For generating as much as possible code it's necassary that I have these elements already in the EA.

Is there a possibility to have a better overlook without deleting attributes? I'm searching for a way to hide these elements from the graphical view.  

Thanks for your help.

3

Uml Process / Re: Reducing complexity in Use-Case-diagrams

« on: May 29, 2008, 06:35:47 pm »

If your Use Case diagrams resemble spider webs consider a re-design of you UCs. It's most likely a wrong design. Read the standards about UC design.

It isn't realy a spider web. I think that it's recommanded as a design pattern to extract functionality that is shared by different use cases in a single use case that can be included instead of declaring the functionality at serveral places.

But I always think about solutions for a better design.

4

Uml Process / Re: Reducing complexity in Use-Case-diagrams

« on: May 29, 2008, 06:28:36 pm »

Hey,

your advice is helping me a lot, thank you.  "Cross-cutting use cases" seems to be a good keyword for further research.

I created use cases on a high abstraction level in a package. But I'm still not sure how to model in a manner that avoids redundancy.

For example there is a use case "XY" that has to be included in the composite diagrams of the Use Cases A,B and C. If one want to avoid redundancy, there must be a link to Use Case XY from within two of A,B and C. If XY was first created as original in A, the link could be copied to to B and C but I don't see a reason why the "original" XY should be declared in A while B and C refer to it. It could also be declared in one of the two other use cases.

You wrote: "You can simply drag a use case from the Project Browser tree onto a diagram, regardless of where the use case or the diagram reside in the project hierarchy."
So, I don't care where I declared XY at first and just copy the link when and where I need it?

Thanks,
Tim

5

Uml Process / Reducing complexity in Use-Case-diagrams

« on: May 29, 2008, 01:55:36 am »

Hello,

based on a list of requirements I extracted a Use Case diagram. I read that as a "best practice" it is recommend that ther aren't more than 10 Use Cases in one diagram but in my diagram there are about 40 Use Cases.
Between the Use Cases exist a lot of associations like <include> or <extend> so that it is different for me to describe them separetly.

I have two ideas for a solution:
1.) The first idea is to put the Use-Cases into different packages. The requirements to the system can be described from 3 views, so that I would use one package per view.
But how can I represent the Use-Cases that are used by an <include> from different packages in a good way? There isn't something like an interface where I could offer them.

2.) The second idea seems a little bit better to me. Each view could be represented by an individual Use Case diagram. In these diagrams one could copy references to the Use Cases that are includes from diffenent views. But from where can I include them? :-(

I would be very thankful for every kind of help. Perhaps to my concrete problem but also for a general advice how to reduce the complexity of Use Case diagrams would great.

Thanks a lot and sorry for my bad english skills.