uml

问题 Some time ago I was a TA in a introductory programming course on Java. We used an IDE called BlueJ which had the nice feature that the overview of your development files was a light-weight UML diagram with 'usage' pointers and inheritance pointers drawn in, this made it easy to see the structure of the program. My question is the following, Is there a similar framework for c++? or at least a tool that I can have running next to my editor to keep a clear view of my files and how they are

问题 I have a super class, that 40 other clases inherit, at this point I would like to simplify the diagram, to be exact all the inheritance relations (40 relations point to a single class) all these "arrows" just make the diagram a complete mess, Is it posible to simplify this? 回答1: There is no direct way to simplify such case in UML Specs, but really 40 classes to inherit from one class? I think you may need to re-consider your design again. In general, you can omit attributes and methods from

问题 Can I use bidirectional arrows in Process/Activity UML diagram? Any example? I am preparing a process diagram with swimlanes. what I encountered that many processes are cross referencing across the swim lanes. Not a good as-is design. Just want to know is it ok to use bidirectional arrows to represent such process diagram? What are the disadvantages? 回答1: The UML specs is hard to digest here. Activities/actions are connected with ControlFlow s (see p. 418 of the specs). A ControlFlow itself

问题 In UML diagrams when considering composition. Should we use it in logical or implementation sense. Examples for both terms: Implementation - An airport will contain a reference to the country. In other words, a country is part of the Airport. Logical - A country can have zero or many airports. In other words, an airport is part of the country. From diagram above, which case shows correct usage of composition? NOTE: if neither of these cases are good, please suggest other ways to show

问题 Having a bit of trouble coming with a class diagram using the following information: A person owns zero or more houses. A mortgage has a start date and an end date. A mortgage has a total and consists of monthly payments. The bank stores information on the National Insurance Number and salary of each person, that request a mortage for a house. A mortgage belongs to one person. A house can have zero or more mortgages on it but it is owned by only one person. A house has a value and acts as a

问题 Could you please tell me if my diagram is correct? I especially care about relations between PaymentService and Customer , Payment , Customer I guess that: class Customer { private List<Payment> payments; //.. public boolean pay() { return PaymentService.pay(this.payments); // calling the static method of the class PaymentService } } interface Payment { // knows nothing about Customer } class PaymentService { public static boolean pay (List<ayment> payments) { // the magic here is return

问题 I know it is possible to specify the multiplicity within the same class box, without having to draw the link to another class. My question is, Where should the multiplicity go, after the name or after the type? Is it: visibility name multiplicity : type as + clients [0..n] : Client or visibility name : type multiplicity as + clients : Client [0..n] I have two books (Applitying UML and Patterns by Larman and UML and the Unified process by Arlow and Newstadt ) but they differ 回答1: Pulled from

问题 I'm looking for an example of an activity diagram where one action is a Call Operation Action and is calling another action with more than one parameter being passed. I have search quite a few uml books, search online and gone through the uml2 specification but cannot find an example representing the above. This question is similar to my previous question, but is much more specific hence I don't think it is a duplicate question. 回答1: I don't have the rights to post examples of my own work,

问题 Some classes in my class diagram need to reference specific instances of other classes or themselves. Should I just model those the same way i would in an object diagram or is there a better option? In general: Can one combine class and object diagrams, since object diagrams are themselves class diagrams? thanks! 回答1: UML2 introduced Composite Structure Diagram exactly to solve this issue. In a Composite Structure Diagram you can show classifiers (e.g. Classes) together with theirs internal

问题 Aggregation is a whole/part relationship. If whole does not exist no longer, but part will still exist But in composition If whole does not exist no longer, but part will no longer exist For example, a university owns various departments (e.g., chemistry), and each department has a number of professors. If the university closes, the departments will no longer exist, but the professors in those departments will continue to exist. Therefore, a University can be seen as a composition of