Book a Demo

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

Pages: [1]
1
Suggestions and Requests / Re: Sequence Diagrams and Parameters
« on: March 01, 2007, 05:23:46 am »
Never mind, I found the constraints.  I'll think about this one.  It may be what I was looking for.  Thanks, bjones.

2
Suggestions and Requests / Re: Sequence Diagrams and Parameters
« on: March 01, 2007, 05:21:23 am »
>> Have you tried the putting cacheList := false in the constraint box on the properties page?   or attaching a constraint to the method? <<

I do not see any constraints on the message.. Am I missing something?  A constraint on the method is certainly not what I'd want to use.  The parameter value is not constant, it depends on the exact message context in which it is used.

Here is an example to illustrate;  Suppose you had a sequence along the lines of:

--ConfigureRefreshMode(allowUpdate:=false)-->
--UpdateDisplay()--------------------------->
--ConfigureRefreshMode(allowUpdate:=true)--->

If I need to include another bool parameter for the ConfigureRefreshMode, and decide to require it (as opposed to include another overload):  ConfigureRefreshMode(allowUpdate:bool,suspendPaint:bool), EA goes and destroys the information concerning the allowUpdate parameter I entered in the sequence above.

If you go and look at the sequence again, you may not be able to easily determine what the parameter value was supposed to be to ensure the detailed sequence works correctly; you have to go and re-analyze the sequence, as opposed to tweaking it to account for the new parameter.

3
Suggestions and Requests / Sequence Diagrams and Parameters
« on: May 18, 2005, 12:15:50 pm »
We use Sequence Diagrams extensively to detail our designs.  We run into several problems with EA and sequence diagrams, as illustrated by the following example:

1. While creating a sequence, I'll discover the need for a method, GetCategoryList( bool cacheList ).

2. I'll use this method in a sequence diagram, and change the argument text so that the message reads as:

 GetCategoryList( cacheList := false )

3. I'll create several sequences, using the above pattern and appropriate value for where cacheList appears.

4. I'll send these diagrams off to be reviewed and implemented.

5. Testing will find some sequence variation that requires an alternative flow to correct a fault with the use case.

6. I'll design an alternate flow, and realize that I need additional parameters, say:

  GetCategoryList( bool cacheEntry, out int cacheEntryCount, out WarningBits warnings )

7. As soon as I update GetCategoryList, EA destroys all those nice arg text values that were used in all those other sequences.  If you go look at those other sequences, the messages now read:

  GetCategoryList( cacheEntry, cacheEntryCount, warnings )

Someone who needs to know whether cacheEntry should be passed in as true or false is sort of screwed -- they either need to try to figure out original intent, or send it back to the developer.


Is there...

A. A way around this problem?

B. A way to figure out which sequence diagrams a particular method is used on.

 - at least worst case, I can open all sequences that use a particular method, get a snapshot, add the parameter, then correct all the diagrams?

C. Any other ways to work around this deficiency?

 - I could attach a note to the method to specify parameters, rather than use the argument text field.  This is ugly, but at least it works.  This looks like, after all the steps above, as:

   GetCategoryList( cacheEntry, cacheEntryCount, warnings ) ---- [NOTE: "Set cacheEntry := false" ]

D. Any plans to correct this problem in future EA versions?  It should not be touching text values I have spent time to manually add, even if it doesn't quite match the message signature.  It would be nice to give me a warning that some don't match, and extra nice if it popped up a dialog that would let me navigate to each diagram that needs to be corrected.

--
 Trent

4
General Board / nvarchar(max) data type?
« on: March 04, 2007, 04:32:51 pm »
We are beginning a new product, and are targetting SQL Server 2005.

Reading thru the documentation, we'd like to use the nvarchar(max) datatype for open ended text strings, rather than ntext.

It did not seem I could either use this data type in the table elements in EA; I suspect because the EA version I'm using (6.1 build 790) does not have SQL 2005 support?

I did not see anything indicating any subsequent release supports this feature; Am I missing something?  If it is not supported, is there an easy way to add support, or is there any plans to adding this support in a future release?

Thanks for any responses.

--
Trent

Pages: [1]