Project name changed with File/Save-as Change Top-level package name in its properties (by selecting the package in the Navigator pane) Ditto for "class diagrams" To add new objects, click on the toolbar item, then in the Editor pane (or double click on toolbar item and click away in Editor pane) TOOLBAR ITEMS FOR CLASS OBJECTS two-pane window = class 3-pane window, middle pane shadowed = attribute 2-pane window, bottom pane shadowed = operation Detail pane style tab prettifies objects in Editor pane In one of the tutorials, http://argouml.tigris.org/tours/bdClassDiagram10.html they say to place a new Interface then add an association "between the Course and the new interface". Yet the next step says that Realize (dashed triangle arrow) means "implement". WTF??? Perhaps they mean that Course contains an attribute of the interface type? (If so, then this has-a relationship normally inside the Class object is shown with an association for some reason). The demos point out lots of points about notes and documentation that don't work. May want to just stick to JavaDocs until they get that worked out. Very tentative here, but I think it makes sense for us to use the Diagram-centric perspectives, in order to concentrate on the base UML diagrams instead of ArgoUML-specific stuff. ArgoUML Features Code import doesn't work with 1.4.0 (I think) XMI is a UML portability protocol. Rational Rose can write Xmi files, and Xmi files are inside of .argo files (which are zip files). However, apparently nobody has ever tried to read a RR file with ArgoUML! DB support. Only mySql support possible now, and even that doesn't store "graphical information". What the hell is the point? DESIGN REPRESENTATIONS: Graphs, Text, or Table. I think that you have to download optional jars in order to use anything other than Graphs. (Tab to lower left of Edit pane). CHECKLIST EDITOR: This is about the most useful thing about ArgoUML, but the docs say that it isn't implemented yet. OCL: Object Constraint Language. Puts restrictions on objects via expressions. I guess this is not very widely accepted, since it doesn't ever make an appearance in the index of the Reed book. Therefore, don't use it (besides, according to the tutorials, it isn't implemented yet anyways). Default mode in Edit pane is select (the mouse-cursor icon). Changed if you double-click another toolbar icon. Just click the mouse-cursor icon to return to select mode. WHAT TO READ ON THE argo.org SITE Quick Guide is a waste of time (just launching the program will teach you more). Viewing the feature list is unnecessary. Read Section 2.3 of the User Manual. http://argouml.tigris.org/documentation/defaulthtml/manual/ch02s03.html Tutorials http://argouml.tigris.org/tours/index.html Go through everything above "Interactive demonstrations", skipping only the last item, State Diagram. (The Interactive Demos suck really bad. They don't show much useful stuff, spend most of their effort showing you performance monitors of your PC and explaining over and over again that your screen is updating, etc. You have no way to slow down or pause the demo). Gleanings from Section 3 of User Manual First they give a very simplistic and primitive definition of Vision Document. They later (section 3.3.1) explain it very closely to Reed. NAVIGATION (regular arrow-heads) Default (no arrow-heads) for Use-case diagrams is two-way initiation "Active" Actors initiate interaction with system. Shown by a normal arrow FROM Actor TO Use-case "Passive" Actors participate in an action initiated by the system. Reverse the arrow. MULTIPLICITY (Often not shown unless important to understanding) Number of instances on each side. Default is 1. MUST SPECIFY AS A RANGE Ranges specified as x..y. ArgoUML specifically is too stupid to understand that * == 0..* or that 2..2 == 2. INCLUDE Dashed regular arrow with <> label. (Just like a dependency line, but with the label. Very diff. purpose.). One Use-Case can "include" others (like Use ATM = Withdraw cash + Depos...) (Note that Reed says it is <> with an s) EXTENSION The extension "extends" (points to) the base Use-case. Just like INCLUDES, but label is <> with criteria along-side, and main Use-case graphic specifies the attachment point label (of descrip) GENERALIZATION/SPECIALIZATION is a solid arrow with tri head An Extension but no specification of why or where. Try to avoid (in Use-Cases) HEIRARCHICAL USE CASES Labels can be supplied, but are not displayed SUPPLEMENTARY REQUIREMENTS SPECIFICATION ArgoUML recommends putting all non-functional specs here. None in Use-case specs. Speed (response times, etc.) Size (capacities) Ease of Use (training time, help system features) Reliability Robustness Portability Environment Standards compliance ASSOCIATIONS Can create them by clicking and dragging the tiny handles on Actors and Case-uses. They say that names are usually not necessary. If 2nd point of your association is over blank space, a peer for the 1st point will be created. STEREOTPES not much implemented in Argo (These are like user-defined association subtypes. No relation to Reed's class stereotypes). DOCUMENTATION Intended for just references for real notes or documentation. WTF???