Messages

1

General Board / Re: Level of version control

« on: September 26, 2007, 09:19:44 am »

I didn't see the correct answer here. So I'm adding my two cents.
The EAP file is a binary file. As such it is not subject to merging. SVN has facilities to merge text file sources but it has no way to merge binary files.

With that said, an EAP file would have to be checked out with a lock. This means the next person would not be able to work on it until it is checked back in.

2

General Board / Re: C++ code generation - vitual keyword on destru

« on: August 16, 2007, 11:33:43 am »

Thanks! That is what I was looking for.

3

General Board / C++ code generation - vitual keyword on destructor

« on: August 16, 2007, 07:55:41 am »

When I generate a C++ class the class destructor always has the virtual keyword as a prefix. Is there a way to turn this off?

4

General Board / Re: Imported classes have alphabetized attributes

« on: April 09, 2007, 01:22:28 pm »

Never mind. I found it.

Uncheck box:
Tools/Options/Objects/Sort Features Alphabetically

Import code into diagram.

5

General Board / Imported classes have alphabetized attributes

« on: April 09, 2007, 09:36:24 am »

Hi,
I am evaluating EA professional. I imported some C code that we have and I noticed that it alphabetized the attributes in the structs. Is there an option to turn this off as the code we use depends on the order. A no-no I know but that is how it works.
Ray

6

Uml Process / Re: Can Use Cases signify class objects

« on: September 27, 2007, 06:30:47 am »

Actually I have read "The Unified Modeling Language User Guide 2nd edition". On page 230 it states that "A use case describes a system (or a subsystem, class, or interface) does but it does not specify how it does it."

That statement made me assume a Use Case could represent a class.

However, maybe a package is the best way to represent classes?

7

Uml Process / Can Use Cases signify class objects

« on: September 26, 2007, 08:20:06 am »

I used a Use Case diagram to kind of get a feel for the types of class objects I needed for my design. Each Use Case ellipseoid represented a class object. I was told that this was the incorrect use of Use Cases. Is this correct?