Nicely done :) Question: Wouldn't Application->Fuseaction be an aggregate as well? Take away all Fuseactions and you don't have an application from a FB perspective....
Cheers, Keith. >>> [EMAIL PROTECTED] 04/10/02 09:22am >>> For those interested, I have made a very rough attempt at a UML class diagram to describe the relationships between Circuits, Fuseactions, etc: http://bjork.net/index.cfm/fuseaction/content.display/page/architecture.htm ----- Original Message ----- From: Lee Borkman No. Look out, Dan. John mistyped. It's the English weather - freezes up the joints. It should be "a Circuit is an application like userManager and a fuseaction would be addUser, which has one or many fuses." Just remember... App -> Circuit -> Fuseaction -> Fuse LeeBB ----- Original Message ----- From: Schweitzer,Dan Okay so a Circuit is an application "usermanager" and a fuse would be "addUser", which has one or many fuseactions. ... ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
