Messages

1

Suggestions and Requests / Re: Flow chart

« on: April 18, 2008, 01:50:52 pm »

Hey David and Simon,
   Thanx for the advice.  I'll go back and look at activity diagrams again.  I know some of the symbols are available in activity diagrams, though I'm not sure the meanings of the shapes exactly match standard flowchart symbology.  And, I like the roll-your-own UML extendability of EA.  (So that's how you do it.)  Excellent guys.

2

Suggestions and Requests / Flow chart

« on: April 18, 2008, 05:53:31 am »

We're specifically trying to link a flowchart to a use case.  We can use Visio and link the file to our use case in EA, but it would be nice to do the flow chart directly in EA and link though a composite, etc...

Thanx,
Cosmo

3

General Board / Re: How to structure huge EA project?

« on: April 23, 2008, 07:01:19 am »

Hey guys,
   Thanx for the tips.  I continue to bang my head on this.

   Our object model is arranged in one flat directory/namespace structure.  If I put the objectmodel package under version control (to prevent accidental changes to it) everything comes to a screeching halt.
   For example, I can drag class A from the locked objectmodel package and drop it onto a new sequence diagram in another package that is not under version control. I can repeat the same process with a different class B from the same locked objectmodel.  But, when I try to map a call from class A to class B, I immediately receive a locked package warning from EA.  It appears that my attempt to map the call is updating the objectmodel--which is read-only (not checked out).
   This actually makes sense, but I don't have any solution to my problem yet.  I am researching EA security but I'm not sure what that will get me unless I do strict locking.

Any ideas?

Thanx,
Cosmo

4

General Board / How to structure huge EA project?

« on: April 18, 2008, 02:49:47 am »

All,
   I'm trying to get a handle on a very large VS200x project with EA:
-topmost VS200x solution has 30+ projects, totaling 7000+ files
  -one project has majority of object model
  -one project has majority of WinForm classes
-over 10 developers
-using SVN
-trying to bring in UML to get better handle on this monster (blame previous architects, not me!)

   We have effective source file version control practices between VS200x and SVN/Tortoise.  But in moving to UML, trying to understand how to structure a manageable EA project that shadows this existing codebase right now.  Once we have enough stuff documented, I'll flip the development process upside down (UML first, code second--instead of re-engineer UML from existing code)

Questions:
1) How can I create an EA project that so many developers can effectively do concurrent diagramming?  For example, all devs will be working to document their respective object model classes/behavior.  I can't afford to have only one dev checking out the EA object model project, while the rest wait their turn.  How can I get some parallel attack on this problem?

2) If I split into multiple .EAP files like the help files suggest, while I have cross-file visibility?  For example, if ClassX in the Foo1 process is in Foo1.EAP and Class X is also in the Bar2 process in Bar2.EAP (a separate file), will my developers be able to know that ClassX is used in both processes?  Right now it looks like I have to keep opening up each .EAP file to see if ClassX is used.  Which also means I have to document its use in multiple places, and the documentation will degrade over time.  Can I make a master file that pulls all of the little .EAP files together, so that developers branch or check out just a little piece but effectively see each others collective changes (without bumping into each other)?

   Surely someone on this group can point me in the correct direction.  I would appreciate any advice that can be given.

Thanx,
Cosmo

5

General Board / Removing unwanted version control 'Unique ID'?

« on: April 22, 2008, 01:23:55 am »

Does anyone know how to remove an unwanted 'Unique ID' from the version control settings dialog?

6

General Board / Re: C# property setter

« on: March 04, 2008, 11:04:37 am »

Hey Simon, thnx for the quick response.  I guess I should have clarified that my question was more on EA's UML class diagram than it was on the generated code.  But that certainly answered the other question that I didn't ask.  Very cool!

But when using the UML class diagram to convey some of the underlying model to other developers/companies, the getter signature displayed in the UML class diagram isn't clear that one should implement just a getter, or a setter, or both.

I like using the property checkbox from the attribute popup, but if the class diagram doesn't show the setter signature, then I'm left wondering if this is a UML 2.1 limitation, a tool limitation, or a spot where I should not use the tool feature and come up with my own stereotypes (where the operation signature is to be ignored because of a 'perceived' tool limitation).

7

General Board / C# property setter

« on: March 03, 2008, 07:21:28 am »

When doing a property implementation for an attribute in C#, the operation signature isn't what I expected (? correct ?).  Perhaps this is just an issue with not understanding how to make the tool do what I want.

For example, the attribute '- _Foo : decimal', might need to be associated with a setter property '+ Foo (decimal) : void'.  Despite unchecking the 'read' checkbox and only leaving the 'write' checkbox checked, only the signature for the getter was created.  Why didn't it create a signature that reflects an assignment instead of a value fetch?  Also in those cases where the property is read/write, why aren't both get and set signatures present?