uml

UML is most commonly used for modelling system by using C++. In my projects C is the implementation language. I am looking for resources on UML strategies which are applicable for C. I want to use UML during design and represent the different aspects of the system. I don't know of any existing resources that discuss using UML specifically for C. As others have mentioned, UML is language-agnostic. Keep in mind that with UML, you can have a model for the problem domain, and another for the implementation. Try not to model the problem domain in terms of C, but rather as high-level OO. Once you

I have an application written in Java. In is stored in several files. It uses different classes with different methods. The code is big and complicated. I think it would be easier to understand the code if I have a graphical model of the code (some kind of directed graph). Are there some standard methods for visualization of code. I am thinking about usage of UML (not sure it is a correct choice). Can anybody recommend me something? ADDED: I consider two possibilities: Creating the graph by hands (explicitly). Creating graph in an automatic way. For example to use some tools that read the

I am reviewing my knowledge in object-oriented programming. Under the relationship between classes topic, I have encountered some relationships which are a bit ambiguous to me. I know dependency "uses-a" and inheritance "is-a" but I'm a bit unfamiliar with Aggregation, Composition, Association and Direct Association; also, which of them is "has-a" relationship. Some use Aggregation interchangeably with Association. What is Direct Association? Also, what is Composition? In UML diagrams, the arrows that represents them are different. I would be really thankful if you could clear these things out

I have a problem with taking a class diagram for a game. The world in which the game takes place, can be represented by fields. Each field is identified by the coordinates x and y. The field may be convenient to establish a settlement or not. If there is a settlement on the field, the only one. Each field is linked to a landscape as a bitmap. In some fields, there may be resources (eg coal, ore), or other artifacts which are not proprietary. Each player is the ruler of a principality. May belong to the Duchy of many settlements. The Principality of nationality and citizenship designates

I've always avoided using aggregation because it seems so subjective which one-to-many relationships should be classed as aggregations. But I'm reviewing a model produced by someone else in which aggregations are used for many-to-many relationships (as in: a course consists of several modules, a module may be part of several courses). That strikes me as plain wrong, but I can't find a definitive rule against it. What's the official ruling? A good website for this is http://www.uml-diagrams.org/class-diagrams.html If you search there for "Shared and Composite Aggregation" you will read, that

Unified Modeling Language (UML)又称统一建模语言或标准建模语言，它是一个支持模型化和软件系统开发的图形化语言，为软件开发的所有阶段提供模型化和可视化支持，包括由需求分析到规格，到构造和配置。 UML分类 （1）静态模型（系统结构）： 用例图、类图、对象图、构件图、部署图 （2）动态模型（系统行为）：状态图、活动图、顺序图、协作图 UML中有4种事务： （1）结构事务：名词、静态部分、物理元素。 （2）行为事务：动词、动态部分、行为。 （3）分组事务：包。 （4）注释事务：注解。 用例图： 用例图是指由参与者（Actor）、用例（Use Case），边界以及它们之间的关系构成的用于描述系统功能的视图。用例图（User Case）是外部用户（被称为参与者）所能观察到的系统功能的模型图。用例图是系统的蓝图，用于需求分析阶段。用例图呈现了一些参与者，一些用例，以及它们之间的关系，主要用于对系统、子系统或类的功能行为进行建模。 用例之间的关系 （1）包含 (include) 关系 父用例包含子用例，父用例执行，子用例必然被执行 当两个或多个用例中共用一组相同的动作，这时可以将这组相同的动作抽出来作为一个独立的子用例，供多个基用例所共享。因为子用例被抽出，基用例并非一个完整的用例，所以include关系中的基用例必须和子用例一起使用才够完整，子用例也必然被执行