uml

If I create a conceptual class diagram such that each class captures 'name' and 'attributes' but not 'operations', have I not basically created what would be otherwise considered an ERD? I'm trying to gain an understanding of what the differences are between creating a conceptual class diagram as I have described versus calling it a ERD? If these are still two different animals, can somebody please explain what the differences are? There´s little difference in the expressiveness of both (if we just focus on the attributes, classes and associations part) if you use Extended Entity Relationship

Actually, make that a couple of amateur UML questions! When creating a UML diagram to model some domain concepts and you come across a domain concept that "holds" some information about another concept, is it better to hold a stamp/reference to that entity or hold the whole entity in the model itself? Please bear in mind that this is relating to creating a simple high-level model - I'm sure in the implementation stage things would be slightly different. For example, which of the two models below is actually correct? The first one has a composition relationship, with FlightBooking holding the

这周做的事 继续自学UML和java； 去pta平台练习基础编程； 学习html; 下周将做的事： 1.进入PTA平台进行程序的编写； 2.阅读java程序设计 用java练习一些小程序; 3.每天自学1-2个小时的JAVA; 4.自学html和UML; 来源： https://www.cnblogs.com/zzmds/p/11371451.html

本周完成了部分暑假作业，学车，锻炼，自学了一点UML，花在学习上的时间大约20小时，3小时编程，0小时解决问题。 下周打算完成暑假作业，学车，锻炼，自学UML，加快完成进度。 来源： https://www.cnblogs.com/zql-42/p/11371414.html

I watched a video with xcode 3, that shows a button "Design" that displays a UML diagram, but I can't find how to do it with xcode 4. Try Omnigraffle This has templates for UML diagrams. If you drop an Xcode4 project file onto its dock icon, it will generate a UML diagram from that. What it doesn't do is generate code from diagrams. Paul W Search for "Xcode Design Tools" in Help. That will show you a tutorial that will walk you through creating a diagram. EDIT >>> It looks like the instructions are actually for XCode 3 and that UML Modeling was removed from XCode 4. The only modeling I could

I am modeling a class diagram. An attribute of a class is an enumeration. How do I model this? Normally you do something like this: - name : string But how does one do this with an enum? They are simply showed like this: _______________________ | <<enumeration>> | | DaysOfTheWeek | |_____________________| | Sunday | | Monday | | Tuesday | | ... | |_____________________| And then just have an association between that and your class. If your UML modeling tool has support for specifying an Enumeration, you should use that. It will likely be easier to do and it will give your model stronger

前言 我们目前已经学习了设计模式的7种设计原则。下面本该是直接进入具体的设计模式系列文章。 但是呢在我们学习设计模式之前我们还是有必要了解一下uml图。因为后续的设计模式文章不出意外应该会很多地方使用到uml图。如果你连uml图都看不懂的话，那么学习起来肯定会有一定的难度。 所以说，这一节就作为承上启下的章节，让我们来了解一下uml图吧。（当然如果你已经会UML图了，你完全可以跳过这个章节） 介绍 按照惯例，我们还是要让大家知道什么是UML图： UML有很多种类，什么用例图，静态结构图，动态行为图。 而作为java程序猿，我们最关注的的还是静态结构图中的类图即可，所以你只需要记住这一句话就可以了： UML图就是用来描述各个类，接口之间的关系图 。 我们下面包括今后的UML类图都是用IntelliJ IDEA自带的类图工具来展示 ，每个软件的画图风格会有一点点区别，但是核心的东西是不会变。 好的，我开始进入主题 类之间的关系 类与类之间的关系我们可以分为以下几点： 由于我们大部分时间使用的是idea自带的工具Uml Support来生成的uml图（快捷键：ctrl+alt+shift+u）。虽然大体类图线条的画法是相同的，但是IDEA生成的UML图的聚合关系和组合关系稍稍有点不同，我们接着往下看. 依赖 只要是在类中用到了对方，那么他们之间就存在依赖关系。 依赖关系包含其他5中关系