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

Pages: 1 [2] 3 4 ... 13
Suggestions and Requests / Re: Multi-diagram page support
« on: July 03, 2008, 10:49:05 am »
It just isn't as easy as I'd like. I have to carefully segment my diagram according to page boundaries, hide line segments that cross page boundaries, find a way to label the stubbed lines (page number and gird), indicate directionality in a way, ...

I'm working with Composite and State Chart diagrams in particular. The other UML diagrams segment more nicely and don't really need multilpe pages. I suppose Deployment diagrams could get complex enough.

If you look at a set of schematics for a typical circuit board you'll see lots of the features I'm talking about.

Thanks for asking,

Suggestions and Requests / Multi-diagram page support
« on: July 03, 2008, 05:41:20 am »
Call me old school but I'd like to see support for one diagram spanning multiple pages. I suppose no one prints anything out anymore but I do. I would like to use 11x17 paper rather than D size so I need line continuation from page to page. Even D size can get cramped.

Purists that would say that if I need more than one page to describe the design it is too complex. Save it. I'm not building a coffee machine.


Is there a way to designate the segment of a transtion that the label should be anchored to? I would like transition labels to be close to the *from* state. The labels can be dragged anywhere but when you move the achore segment the label also moves. Sometimes the label then appears to be associated with a different transition entirely.


It would be nice to switch between state diagram and table representations without having to check out the package.


Suggestions and Requests / Improve Compare with Controlled Version
« on: May 24, 2008, 04:07:11 am »
Perforce is the CM software.
Use Package Control to check out a package
Make changes (not necessary to see the hang but this is the use case)
Try to review your changes before submitting
Package Control->Compare with Controlled Version... hour glass...

I think a work-around is to configure p4 to clobber the package file but I'm certain that will eventually cause me to lose work. I know I will Get Latest at the wrong moment and, even though it pops up warnings, I'll wipe out some brilliant changes.

Here is the request: Automatically compare against a temporary version of the file from the repository.

Thanks, DanG

See "Local Paths support for any file type" for related request.

Regards, DanG

Suggestions and Requests / Re: Local Paths support for any type
« on: May 24, 2008, 02:58:35 am »
I'm having good results using EA as a tool to implement specific practices in CMMI RD and REQM process areas. This feature would make it a lot easier to link to artifacts created outside of EA. In my case, none of the user-generated artifacts are EA elements.

Suggestions and Requests / Local Paths support for any type
« on: May 23, 2008, 10:23:20 am »
Is there a way to specify a local path for linked files?

Web links don't quite meet my needs and I use p4 to version control the documents and, by side effect, distribute them. If I could define a local path type then I could link to file just like I link to source code.

A visio drawing has a very useful graphic in it and I'd like to link it to a use case element. The visio file is checked into perforce and I see it at D:\dev\ProjectX\Models\Requirements\foo.vsd. Other colaborators see it in different local paths but always under ...\Models\Requirements. Thus, I'd set MODEL_REC_DOCS to D:\dev\ProjectX\Models\Requirements. Other colaborators would set MODEL_REC_DOCS according to their local tree. Thus, the links would work for us all.


General Board / Show Behavior in Diagram Formatting
« on: July 26, 2013, 02:16:39 am »
Does anyone know how to make behavior text show nicely in state charts? I'm talking about the result of entering text in the Behavior in an operation properties dialog and ticking the "Show Behavior in Diagram" box. The text is rendered with leading white space removed.

Managing the code in the Behavior box is terribly inconvenient. Does anyone have a plug-in? An action language editor integration?


General Board / Re: State machine internal transitions
« on: September 30, 2010, 02:36:20 pm »
I created two new stereotypes: <<internal transition>> and <<internal transition target>>. <<internal transition>> marks the transition from the super state to the pseudo sub-state that is marked with <<internal transition target>>. These markings will allow the code generator (my own) to emit the right code corresponding to internal transition semantics. I made the line color white for the transition and was able to make a diagram that looked pretty good.

Transition lines from super to sub have a mind of their own. Initially, place the sub near the left side of the super state. That seems to convince the transition lines to go from left edge of super to left edge or sub. Pin both ends to keep that sucker from moving. Slide the pseudo state over until the transition labels look nice.

The diagram looks okay and the transition is really a transition in the model. The EA state machine code gen won't do the right thing with this notation. I'd still like Sparx to support the notation directly but I submitted the request for 7.0 and for 8.0 but no luck.

General Board / Re: State machine internal transitions
« on: September 30, 2010, 12:45:00 am »
Thank you for trying. I was away from my workstation and couldn't try. I'll will fiddle some more this morning. Next try is to make an internal exit pseudo state in the sub-state.

A flaw with this approach is that a transition from the super to any sub means exit from active sub hierarchy. Orthogonal region for internal transitions doesn't work either. I think the event is dispatched to each region by super. That means the event goes to both the active sub and the internal transitions region. What is needed it the event triggers the internal transition iff the active sub hierarchy doesn't handle the event.

To address this, the do activity of the non-internal-transition region could generate evX_NotHandled events. The internal transition region could use these events as triggers. The do-action is supposed to execute only when there is nothing else to do so the initial event will make its way through the non-internal-transition region and then the do can re-dispatch. How will the do-logic know what to do? Check a flag. How will the flag-setting action be triggered? Internal transition in the non-internal-transition region! I cannot win...

I hope these ideas "trigger" another idea that actually works.

General Board / Re: State machine internal transitions
« on: September 29, 2010, 03:47:58 pm »
I've been bugged by the lack of direct support for internal transitions for a long time. The other discussion made me think about it differently. Here is what I'm thinking:
1. Create an anonymous sub-state (no exit, entry)
2. Connect an transition from the super-state to the anonymous one
3. Assign the trigger and action like normal
4. Connect the sub-state to the super-state w/o any trigger

I think that is equivalent to a internal transition for the super-state. A little fiddling and it might not look too bad. Make each anonymous sub-state tiny and maybe make the transitions lines the same color as the background.

I don't know how that state machine code generator will handle this way of specifying. I use Quantum Frameworks to implement my state machines.

I've been using Operation to depict internal transitions. It looks okay but is clearly a hack. At least this latest idea is a meaningful representation. Thanks for helping me think of a new idea.

HTH, Dan

General Board / Re: SysML flow ports compartment suppression
« on: May 06, 2012, 05:52:08 am »
Duh. Thank you for being willing to play "Mr. Obvious." I looked at that dialog box so many times but it took you saying that the option was there for me to see it.

General Board / SysML flow ports compartment suppression
« on: May 05, 2012, 05:32:08 am »
How can I suppress the SysML Block flow ports compartment? When I show the block with embedded elements visible I don't need the compartment on.


General Board / Re: AUtomatically Refresh Diagrams
« on: December 04, 2010, 03:08:28 pm »
I really hate it when people suggest that I have a problem I should not have rather than helping me solve it. Now, I'm about to do that to you. Sorry. I mean no disrespect and I am only interested in the use case.

I use the diagrams as input mechanisms. The only diagrams I have are the ones I used to figure out what I intend to do. When it comes time to change functionality, the first thing I do is look at and change the diagrams. If the diagrams are not useful for this purpose, I do not create them.

What benefit do your diagrams provide above and beyond what you already get from the spreadsheets? Examining diagrams in order to make design changes is a manual process. It seems you are already able to make design changes based on the spreadsheets w/o looking at the diagrams.

I just wonder about the use case and if it is one I have overlooked.


Pages: 1 [2] 3 4 ... 13