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

Pages: 1 ... 12 13 [14] 15 16
General Board / C++ arrays, forward engineering problem - bug?
« on: September 02, 2002, 07:36:52 am »
So far, the only way I have been able to make EA generate code with arrays is to include the []'s in the name of the attribute, e.g.: "Var1[SIZE]". This generates correct code when forward engineering. However, the attribute declaration is duplicated every time I synchronize (forward). Is this a bug in EA, or is there another way to declare array attributes?

General Board / WMF/EMF-resizing while keeping aspect ratio?
« on: August 28, 2002, 05:34:56 am »
When I add a metafile image to my diagram (by associating an image to a boundary object), I normally need to resize it. Is there a way to resize the image while also keeping the exact original aspect ratio?

General Board / Re: Linking notes to elements not on same diagram
« on: August 15, 2002, 02:16:27 am »
I want to let those who may be interested know that I have found an answer to my own question.
It is so simple, I am a bit embarrassed I didn't think of it before.
Step by step:
1. Insert an empty note on the sequence diagram.
2. Drag the Use Case from the project browser onto the sequence diagram
3. Make a note link from the note to the use case
4. Select the link and choose "Link this Note to an Element feature" from the context menu.
5. Find the scenario to be displayed in the note, and clik OK
6. Delete the Use Case from the diagram. The link is still kept intact and working, so that any changes I make in the scenario text is reflected in the note.

General Board / Re: Linking notes to elements not on same diagram
« on: August 14, 2002, 07:38:12 am »
Jaime, thank you for the very thorough answer. However, it seems that I may have been a bit unclear in my formulation of the question. By "scenario" I mean the text descriptions that one enters in the Use Case Properties dialog, on the "Scenarios" tab. I would like to display this text in a note, without having to copy it manually every time it is changed.
I know how to do this if both the use case and the note are on the same diagram (make a note link from the note to the use case, select the link, then select "Link note to element feature" in the context menu). But I want the note to be on a sequence diagram, so that the text describing the sequence is visible. Therefore I cannot make a note link to the use case, because there doesn't seem to be such a thing as a "cross-diagram note link".


General Board / Linking notes to elements not on same diagram
« on: August 13, 2002, 03:39:46 am »
I would like to add a note containing a use case scenario to a sequence diagram. I know how to do this, if the use case itself were on the diagram, but that is not what I want. Can I somehow link a note to an element not on the diagram? Or is there another way to accomplish the same thing?

General Board / Import XMI from Together 6.0 into EA
« on: August 07, 2002, 04:29:29 am »
Import XMI from Together 6.0 into EA: has anyone done this succesfully? I keep getting a message "Unknown XMI Exporter or Version" from EA, regardless of the settings I choose when exporting from Together. Does EA have to know the program used to create the XMI? I was under the impression that large parts of the XMI format was standardized enough to support import/export from any program to any program.

General Board / Time frame for support for Version Control?
« on: August 05, 2002, 06:20:50 am »
We are at the brink of deciding which tool to use for the development of a new project. So far we have been very impressed with EA, considering its low price. However, one important argument against using it, is its poor support for version control/configuration management. We need to store our project files in CVS due to company policy. I have noted, that the intention is to add support for version control to EA. But when? And what granularity will be supported (package level, object level, or...)?

Uml Process / Re: Sense of UML
« on: October 11, 2005, 01:44:30 am »
I have an example from when I was helping an intern at our company.
I was helping him with his analysis model, but he was clearly having trouble abstracting from the coming software implementation.
We had found some various classes with responsibilities like "find employee from employee list", "find tasks in a project", and "find all tasks allocated to an employee".
The intern was equating these analysis classes with software classes, while I was trying to tell him that although the probably would be, they didn't have to be. The model was a valid abstraction of the application logic regardless of how it was implemented later.
The breakthrough in my explanation came when I gave each of the classes a human name: "This is Lisa and her responsibility is to find an employee from the employee list when Peter asks her". Suddenly he saw that if each of those classes was implemented as a person who was assigned the responsibilities of the class, the system would actually work! Expensively and slowly, of course, due to salaries and the amount of manual labour, but the abstraction was just as valid for humans as for software.

That is certainly an explanation I am going to use again.


Uml Process / Re: UML didn't trigger my brain
« on: October 27, 2005, 08:19:39 am »
Agreed. but that's why I would recommend using it to express concrete domain models and the stakeholder's clear statement of expectations.

Modelling a domain and stakeholders expectations is a discipline of its own. If you are already a master of this discipline using other notations or languages, the transition to UML might not be so hard.
But most programmers that I know are not familiar with modelling at all, in any language! Someone told them that they have to learn UML, but they can't readily think of any other use for UML than documenting their source code in detail. The analysis activity is not familiar to them at all.


Uml Process / Re: UML didn't trigger my brain
« on: October 26, 2005, 01:11:24 am »
For most people that I know, "learning UML" is very different from learning a new language.
When you learn a new language, like French or English, you already know what you want to express with that language.
Most programmers who try to "learn UML" are not used to the process of abstracting problems and turning them into abstract designs, which is what UML is so useful for.
These people have to learn both the process (what to express) and the language (how to express it).

This, IMHO, is the great challenge in "learning UML". Not only do you have to learn the language (that is the simple part), you also have to learn what to use it for and why.


Uml Process / Re: UML didn't trigger my brain
« on: October 18, 2005, 12:45:37 am »
The book that started me off really understanding UML was "Applying UML and Patterns" by Craig Larman, and I still recommend this book to everyone that asks. Check it out.


Uml Process / Re: UML didn't trigger my brain
« on: October 17, 2005, 06:33:09 am »
I think that the main point about UML that most people miss in the beginning is that it is just a language, a notation. The UML standard do not offer a methodology or a way to progress with a project.
In order to use UML in a meaningful way you must have a process that tells you what to use it for. An example could be the Unified Process or one of its many variants.
If there is a silver bullet to learning how to use UML in the context of a process, it would be to get expert help. Go to a good course and get a consultant to assist you along the way in your project to keep you on track. How to identify a good course and a good consultant?  :-/

Best regards,

Uml Process / Re: How to structure a project when using packages
« on: June 06, 2005, 08:23:36 am »
I think it still holds, although maybe only part of the way.

The way I would try to structure my packages, each package would probably result in one component.

Of course, if you have a large system with packages of packages of packages, you might need packages of components. However, I would like to caution you against making a deep tree. That goes for your source file directories on your disk too. If you are able to keep your structure flat, you are making it more likely that you are making reusable components.


Uml Process / Re: How to structure a project when using packages
« on: June 06, 2005, 07:41:12 am »
I think the answer is that you should not have the same kind of packages in the logical view and the use case view.

In the logical view, your packages are of an architectural sort.

In the use case view, your structure should be use case-oriented. Each use case will probably work across many different logical view packages. You may group your use cases in packages too, but they would not be the same packages.


Uml Process / Re: How to structure a project when using packages
« on: June 03, 2005, 08:19:08 am »
Peter, what you really need is to decide on a process. The process should have guidelines for how to structure your artifacts.

I could give you the outline that I am currently working on for a template project structure in my company, but if you don't follow the same process as us, this structure will not suit you.


Pages: 1 ... 12 13 [14] 15 16