It looks to me like designing the interface back-end, not the businessokay, cool
logic. Anyway I don't think it's very important for now... After the
version 3 we can talk about, again.
By the way, I'm not an UML expert, so I have a lot of doubts about the useit's not /the /book on UML, but anyway one that will get you kick-started: Uml Syntax and Usage (Pocket reference) from O'Reilly <http://www.amazon.com/exec/obidos/tg/detail/-/0596004974/qid=1074526203/sr=1-1/ref=sr_1_1/103-4939975-2917429?v=glance&s=books>, you find info on this little book here:
of the diagrams, and I will be very happy if you or somebody suggest
books, tutorials and examples about the use of the state/activity diagrams
(portugese, english or spanish, please).
after reading it it might be easier to decide what /serious/ book to purchase
good luck
ps: if the link doesn't work try this one instead (it's the same)
http://www.amazon.com/exec/obidos/tg/detail/-/0596004974/qid=1074526203/sr=1-1/ref=sr_1_1/103-4939975-2917429?v=glance&s=books
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Andromda-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user
