Sparx Systems Forum

Enterprise Architect => General Board => Topic started by: NC0866 on September 04, 2002, 07:24:03 pm

Title: Linking Use Case pathways to Activity Diagrams
Post by: NC0866 on September 04, 2002, 07:24:03 pm
Hi,

I have created a Use Case using EA that has one happy path and three alternate paths.  I would like to link each path to a different Activity Diagram.  How can I do that in EA?

Thank you.
Title: Re: Linking Use Case pathways to Activity Diagrams
Post by: Farfetch on September 05, 2002, 01:20:43 am
I'm not sure if this is what you're after, but assuming I understand what you are asking (and it may not be :) ), the way I link external diagrams to a new diagram is to click/drag/drop the image I want from the file browser onto the new diagram. Then I link it using a flow arrow (or similar). This will add an element to the diagram with the pages location (e.g. 'Business Process Model: diagram x' with a little picture of a page hierarchy by the side).

This may be what you're after, I don't know ??? :-/
Title: Re: Linking Use Case pathways to Activity Diagrams
Post by: jaimeglz on September 05, 2002, 07:32:46 am
Hi, NC.

I hope that what Farfetch is recommending is what you are looking for. But let me ask you: Is a "happy path" a sequence of events that is always executed, or that always takes place in a use case? Are "alternate paths" sequences of events that sometimes take place, and sometimes not?

Jaime Gonzalez



Title: Re: Linking Use Case pathways to Activity Diagrams
Post by: NC0866 on September 05, 2002, 09:16:14 am
Thank you for both the responses.  However, I am not exactly sure what farfetch recommended is what I want :).  

Jamie, a "happy path" is what is also called a Basic Course of Events (BCOE), and is the most travelled pathway through a use case.  An "alternate" path, on the other hand is a perfectly fine course of events (also a candidate for happy path), but is not the most travelled one.  There is another type of pathways, an "exception", which is basically an error condition that the system must respond to.

I have these pathways defined in a Use Case.  I know how I can link the whole Use Case to an Activity Diagram (that I also created in EA), however an Activity Diagram only needs to be linked to one of the pathways through the Use Case.  I hope I am making some sense here.

Again, thank you for your responses.

-NC
Title: Re: Linking Use Case pathways to Activity Diagrams
Post by: CJ on September 05, 2002, 10:24:40 am
G'day folks,

I'm a real newbie to EA and UML, so let me first ask: you've got multiple scenarios setup under the properties of a use case, right?  If so, then...

How about linking a note to the use case, "Link this note  to an element feature...", link the note to the specific scenario you're interested in, and then put the the activity diagram link directly on the note?

You'll have the use case shape linked to a note containing the scenario, and on the note the link to the activity diagram for the scenario (and even links to other diagrams too?).

Maybe another alternative would be to diagram the different scenarios with other uses cases that extend the basic use case?
Title: Re: Linking Use Case pathways to Activity Diagrams
Post by: NC0866 on September 05, 2002, 01:36:51 pm
Jason,

Thank you for your input.  Your solution actually sounds like something I can work with.  I am not sure, however, how "Link this note  to an element feature..." work.  Is it a context menu off of somewhere?  The only note element I can find is one on the toolbar, and its context menu does not have this option.

Thanks again, and I look forward to your response.

-NC.
Title: Re: Linking Use Case pathways to Activity Diagrams
Post by: jaimeglz on September 05, 2002, 03:03:49 pm
OK, NC: now I understand what you are looking for.

Forgive all the detail in what follows, but I just want to be sure we have a good conceptual "handshake".  

When I use the phone, my most general usage is as follows: I pick up the speaker, wait for the dial tone, dial, receive a "calling" tone, receive the answer from the other end, talk, and finish by hanging up. This is the most general usage (nice way of putting it: "happy path"), albeit the fact that in practice there are innumerable variations.

The particular executions or possibilities of a use case are formally called a "scenarios" in UML (no pedantry intended here); these are instances of use cases.

If you double click on your use case in an EA diagram, you can go to the Scenarios tab. This is where you can document the basic and alternate paths. (Since you are going to detail this Scenario in another diagram, you don't need to put much detail here; just give a name to this sequence of events, and choose Basic Path in the Type field).

You can do the same for your other scenarios (your alternate paths, that is), except that you will select Alternate in the Type field.

If you have exceptions, they should be documented in another use case, that should be linked by an <<extend>> relationship to your most general use case.

All of the above is important, because it will help you with your question, and it will also explain what the other forum members are trying to explain.

Now: once you have defined your scenarios, insert a note in your diagram (third icon from left in your tools menu, just underneath the little diskette icon). Link this note to your use case with a note link (I'm correcting Farfetch as well as a previous posting by myself on this one...), which you can obtain in the first item (the one with the arrow) in your tools menu.

Right click in the note link and choose "Link this note to element feature" (as Jason suggests). In Feature type choose Scenario, and click on the first scenario. The name and text associated with the scenario will automatically appear in your note.

From the Worspace (your project tree) now drag the icon diagram that corresponds to the scenario into the note. Voila!

You can now create notes and associate diagrams for your other scenarios.

Hope this is what you were looking for.

Jaime Gonzalez
Title: Re: Linking Use Case pathways to Activity Diagrams
Post by: Farfetch on September 06, 2002, 12:56:33 am
I've now been using EA for 5 days so I think I have much to learn.  :)

I'm going to try your solution to experiment with more of EA's features. Sounds interesting, even if I don't fully understand it yet. ;)

Just a further question - what version are you using? I am currently using 2.5 Desktop (not upgrading to the latest until we have trialed MS Visio 2002 as well) and I don't have the right click option ("Link this note to element feature") on the note link that you mentioned.

Is this a more recent addition?

I also don't seem to be able to access the following thing you mentioned:

In Feature type choose Scenario, and click on the first scenario. The name and text associated with the scenario will automatically appear in your note.

Finally, when I tried to "drag the icon diagram that corresponds to the scenario into the note." nothing happened, the icon diagram just added to the diagram and wouldn't appear in the note. Is this because the above features I mentioned don't exist in my version?
Title: Re: Linking Use Case pathways to Activity Diagrams
Post by: CJ on September 06, 2002, 04:54:52 am
G'day folks,

Back to "Link this note  to an element feature..."

Lookup in EA help "Linking Notes" and "How to Link a Note to an Element".

When you right-click on the context menu for the link between a note and an element, you get a menu item "Link this Note to an Element Feature" which brings up a dialog that lets you pick the type of feature (example: attribute, requirement, constraint, scenario) and the specific feature you want to appear on the note (in the example of scenarios, pick from the list which scenario you want to see on the note).

I'm using EA version 3.10 build 503.

Best regards.
Title: Re: Linking Use Case pathways to Activity Diagrams
Post by: mbc on September 06, 2002, 07:24:04 am
Farfetch - in my opinion EA is a tool that evolves so rapidly that in order to do a serious evaluation, you do not only need the latest version, but also the latest build (today it is 504).

Besides, the prices is so low that I see no reason at all for a professional software developer not to go for the full version of EA.
-
Mikkel
Title: Re: Linking Use Case pathways to Activity Diagrams
Post by: jaimeglz on September 06, 2002, 09:05:45 am
Hi, everybody!

I'm using EA 3.10 build 403 in this laptop. (I've just downloaded build 404 into the home desktop, where I am testsing it. I tell you this because I want to remind everybody that EA's license permits you to use the software in your home machine as well as on your laptop, which is ideal for some of us.)

Now to the point. Some weeks ago, mbc started a thread on "Linking notes to elements not on same diagram":

http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.cgi?board=general&action=display&num=1029235186

I think many of us were delighted with mbc's final solution (on which I have borrowed for what I have just recommended in this thread). Before mbc's solution, I had been been using a non-UML representation to link use cases and sequence diagrams (no big deal, but who knows if some rigoristic zealot might pick on your later for this; Iv'e had lots of trouble with rigorists, specially on big projects). And not only that, but mbc's solution to use the notes simplifies a lot of work, as Kelly eloquently explains in his Aug 16 post.

Basically, we have found a UML-compliant way of downing several stones with a single bird:

1. With the note, you are making visible in your diagram a scenario that is "inside" (so to speak) your use case.
2. If you make changes to your scenarios, they are automatically reflected in your note (except if you change the name of the scenario, in which case it disappears from your note!)
3. We can link the use case's basic path (or other scenarios) to diagrams. For instance, I have an "Account grouping" use case, for corporate reporting, and I have an "Account groping" sequence diagram that details the basic path. All I have to do to go from the use case to the sequence is to double click on the sequence diagram icon in my use case diagram. (In the sequence diagram I have the use case's diagram icon, so I can also go back).

No big methodological issue here; just something very practical for our work with EA.

Jaime Gonzalez

Title: Re: Linking Use Case pathways to Activity Diagrams
Post by: NC0866 on September 06, 2002, 09:19:43 am
Thank you everybody for your responses.  Jaime, I tried your step-by-step instructions and now I am all set.  Thanks again for your help.

On a separate note, I have so far used Visio, Rose (some of it anyway), and EA (for a few days now).  I have to say that EA is the best one available for its features, ease-of-use, and most definitely the price.  Once in a while a small software company comes along with the right skills, determination, and ability to produce outstanding products that leave the competition in dust.  Sparx definitely seems like one such company.  The last one I came across was DataDynamics with their ActiveReports product.

Keep up the good work Sparx -- this is what a software company should be!

-NC
Title: Re: Linking Use Case pathways to Activity Diagrams
Post by: Farfetch on September 09, 2002, 12:52:57 am
I'll have to explain a little :)

I'm on a placement year as the 3rd year of my degree (in Systems Analysis and Design) working as a Software Systems Analyst for a software design company.

My job is to help design and plan the projects they work on before they embark on all the coding so they know how to proceed and how the overal system will work.

We got EA as a free 'full' program on a magazine cover disk and are evaluating it and will be considering Visio et al before deciding which is best for what we need and purchasing a full license for that software.

Visio looks nice, and its links in with other MS products are obvious plus points but it may have some things missing that EA has. This will all be taken into account.

Take note also, this is only my 2nd week here, and I've only really scratched the surface of EA. For instance, I'd like to know how to print out all the listed requirements for an entity (as in, any shape) on the diagram, as well as several other things, but that will hopefully be found through experimentation. :)
Title: Re: Linking Use Case pathways to Activity Diagrams
Post by: mbc on September 09, 2002, 12:58:43 am
Farfetch, Have you noticed that you can download a fully functional 30-day evaluation version of EA for free from this site?
In my opinion, Visio is still just a drawing program, although it has UML stencils. EA is a CASE tool. And I still think that evaluating version 2.5 is not really an evaluation at all.
Title: Re: Linking Use Case pathways to Activity Diagrams
Post by: Farfetch on September 09, 2002, 03:45:20 am
As a member of the bottom rung of the ladder, I don't get to choose the programs, only advise :)

I'm happy using a full copy of EA2.5 for the moment until I have had time to fully evaluate it, which is the aim of getting the Visio trial software from MS.

I don't pay for the software, I leave that to the bosses ;)
Title: Re: Linking Use Case pathways to Activity Diagrams
Post by: mbc on September 09, 2002, 03:54:49 am
... but what is the point of evaluating obsolete software when there is a FULL version (i.e. not only the Desktop version) of the NEWEST release available for FREE download? It is not even a large download, it will only take a few minutes. It is allowed for an evaluator to advise his superiors that the software which is provided is not current. EA moves forward in significant steps in every single build. I can't even imagine how many important features are missing in version 2.5.

Don't get me wrong, I am just trying to help you find the right software. Trust me when I say that you will get an incorrect result of your evaluation if you do not get the newest release. It is like evaluating Windows 3.11 in order to decide whether to purchase Win2000.

I think I have made my point now, and if you still insist, that is up to you. Happy evaluating.

-
Mikkel
Title: Re: Linking Use Case pathways to Activity Diagrams
Post by: kelly_sumrall on September 09, 2002, 06:11:16 am
Farfetch,  do your team a favor and let those who spend the money see this post.  I don't think coparing a Model-T to a Porsche 926 is a fair comparison.  Also, I too have used Visio and have run into it's weaknesses.  If all you want is a drawing on a piece of paper, Visio will do that, you can probably get Word to do that as well.  If you want reports on the various UML diagrams, issues reports, time estimations, ..., you need a real CASE tool.  I challenge you to produce a Use Case report from Visio.  By report, I mean a document that displays  the heading information, scenarios, steriotype, tagged values, and all other user friendly (Management friendly) information that is tucked away inside the bubbles.  Last time I checked, there were only about 5 reports available from Visio (withoud coding one yourself).

I work for a company that is very reluctant to change and is Microsoft all the way.  I finally bought my own copy and couldn't be happier.  Get the current eval version and do some testing at home.
Title: Re: Linking Use Case pathways to Activity Diagrams
Post by: Farfetch on September 09, 2002, 08:51:05 am
We're about to have an ISO inspection, and we're not supposed to have unlicensed software on the computers. I've tried downloading Visio (naughty naughty I know, but it was at home not on company time ;)) but got nowhere with it.

While I'm not ignoring your opinions, the MD of the company had suggested to my immediate boss that they buy Visio for me to use, we just happen to have EA on a coverdisk, and as a full copy is allowed by the ISO people.

I'll happily download 3.0 at home (its laughable, but I have a faster connection at home than the office.. 1MBs Cable vs ISDN). However, at the moment, all I am using EA for, and indeed, all I can see myself using EA for is to draw diagrams and arrows between them as an outline of sotware development programs.

I've tried 3 different projects and have yet to actually use requirements etc. The times I've experimented with them they don't print out, so when I have a hard copy, all it shows is the icons and any text labels I add, this rendors the requirements etc useless for me, so in this example, all I'd need is this copy of EA.

While I appreciate the benifits of upgrading, I'm of the "if it ain't broke don't fix it" school, especially with so many problems with MS Windows Update corrupting things, so while I'll try the full trial version at home, unless I see anything wonderful about it, I'll wait till we can trial Visio and say for definate that we should buy EA.

Remember, I'm a student on a placement, I'm 21, I don't make business choices, I'll see what happens, and by all means if EA serves the purpose (and the fact it is cheaper is a + as well), I'll get it.

However, I've got no use for any of the programming tie ins, or the XML exports or any of that stuff, so what's easiest and best for me is what I'll choose, and that won't be influenced by people other than me, as I'm the one using it.
Title: Re: Linking Use Case pathways to Activity Diagrams
Post by: jaimeglz on September 09, 2002, 12:31:00 pm
About Farfetch's question:

"For instance, I'd like to know how to print out all the listed requirements for an entity (as in, any shape) on the diagram, as well as several other things, but that will hopefully be found through experimentation."

You can print requirements in your diagram in basically the same way we've been discussing for scenarios; namely, through the "Link this Note to an Element feature" feature. Just select Requirement as Feature type, and then select the object's responsibility you want to appear in the note.

Be sure to have filled your requirements in the "Resposibility" tab of your diagram object before you attemp the link.

Also note that you can use the Move External feature in the "Responsibility" tab to create a project Requirement with the object's responsibility. (See Help for more details.)

By the way: Could you keep us posted (under a different thread) on the comparison between Visio and EA?

Jaime Gonzalez
Title: Re: Linking Use Case pathways to Activity Diagrams
Post by: mbc on September 10, 2002, 12:39:39 am
Farfetch, I didn't think I would post about this again, but now I feel compelled to. A "30-day free evalution version" downloaded from the company website is not unlicensed software. It has a 30-day evaluation license.
"If it ain't broke, don't fix it", does that justify sticking to a mechanical typewriter while given the option to use a word-processor for free? Even the drawing parts of EA have improved within the last 10 builds. There are more than 500 builds between your version and the current one.
And you are not going to stick to version 2.5 if your evaluation turns out in favour of EA, are you? Anybody is allowed to make business suggestions, 21 or not, especially when they are good suggestions. Using the current version will also get you more support, because that is what everybody in this forum is using. Sparx Systems gave me unparallelled support, while I was working on a free 30-day license.
I swear this will be my last post on this topic.
Title: Re: Linking Use Case pathways to Activity Diagrams
Post by: Farfetch on September 10, 2002, 02:50:04 am
No need to be sarcastic mate.

But yes, I will upgrade to EA very latest version should we buy it. As I've said we're only trialing Visio (with the 30 day trial free from MS), and I believe I can make a valid assesment of that compared to EA 2.5 as currently it does everything I need.

Certainly the extra features may or may not be useful, but I believe in supporting companies and purchasing their software whenever possible.

The only thing that will lean me towards MS is if it does everything I need better than EA does. While some have said Visio is a drawing tool and nothing more, that is all I am using EA for, and perhaps all I will use it for, in which case it will be a direct comparison of features.

I like EAs features like the Requirement image feature, but I believe it should say "Requirement" on the diagram, like Process says "process" on the diagram.

In the end, I want software that is easy to do and does everything I need, and if that software is EA or Visio, that is what I will recommend we buy.
Title: Re: Linking Use Case pathways to Activity Diagrams
Post by: CJ on September 10, 2002, 05:36:03 am
Has this topic been beaten to death???  Actually, it's been a fun read.  Maybe we could summarize the gist of the conversation?

It looks to me like those who use EA love the product (me included) and would hate to see Visio win out over EA under any circumstance ... especially if comparisons were made between the latest version of Visio against an older (ancient?) version of EA.

Maybe some of us have a genuine/justified disdain for MS (or just Visio), and would vote for any alternative product every time, but it looks to me like this conversation shows, again, how great a product EA is, whether used as a true CASE tool or even used as pure drawing tool (it does make "pretty" diagrams).  A little bit fanatical is a good thing, me thinks.

As always, congratulations to Sparx Systems for a terrific product, and to the rest of you, thanks for making this forum wild, wacky, fun, informative, etc. etc. etc.
Title: Re: Linking Use Case pathways to Activity Diagrams
Post by: johnbeat on January 05, 2003, 11:48:36 am
Sorry to butt in so late in this thread, but I've been struggling for a while with this very problem of linking diagrams to use cases. Is it just me, or does it seem that this is about the only area in which EA is inferior to products like Visual UML? I think the proposed solution, while workable, is a bit of a hack compared to the simplicity of linking diagrams in Visual UML. Even better is objectIF, where you can keep the standard model flow of use case - activity diagram - sequence diagram - classes in total sync very easily and elegantly.

Come on Sparx! We know you can produce kick ass features when you want to. So many people are puzzled by this linking issue, won't you make it a bit easier on us? How about having diagrams appear in the link list, and make this accessible from the context menu of each item?