Uml distilled a brief guide to the standard object modeling language (third edition) part 2
➤ Gửi thông báo lỗi ⚠️ Báo cáo tài liệu vi phạmNội dung chi tiết: Uml distilled a brief guide to the standard object modeling language (third edition) part 2
Uml distilled a brief guide to the standard object modeling language (third edition) part 2
Chapter 5Class Diagrams: Advanced ConceptsThe concepts described in Chapter 3 correspond to the key notations in class diagrams. Those concepts are th Uml distilled a brief guide to the standard object modeling language (third edition) part 2 he first ones to understand and become familiar with, as they will comprise 90 percent of your effort in building class diagrams.The class diagram technique, however, has bred dozens of notations for additional concepts. I find that I don’t use these all (he time, but they are handy when they are ap Uml distilled a brief guide to the standard object modeling language (third edition) part 2 propriate, m discuss them one at a time and point out some of the issues in using them.You’ll probably find this chapter somewhat heavy going. The gooUml distilled a brief guide to the standard object modeling language (third edition) part 2
d news is that during your first pass through the book, you can safely skip this chapter and come back to it later.KeywordsOne of the challenges of a Chapter 5Class Diagrams: Advanced ConceptsThe concepts described in Chapter 3 correspond to the key notations in class diagrams. Those concepts are th Uml distilled a brief guide to the standard object modeling language (third edition) part 2 an. So rhe UML often tries to reduce the number of symbols and use keywords instead. If you find that you need a modeling construct that isn’t in the UML but is similar to something that is, use the symbol of the existing ƯM1. construct bur mark it with a keyword to show that you have something diff Uml distilled a brief guide to the standard object modeling language (third edition) part 2 erentAn example of this is rhe interface. A ƯML interface (page 69) is a class that has only public operations, with no method bodies. This correspondUml distilled a brief guide to the standard object modeling language (third edition) part 2
s to interfaces in Java, COM (Component Object Module), and CORBA. Because it’s aChapter 5 Class Diagrams: Advanced Concepts https://khothu i .comspecChapter 5Class Diagrams: Advanced ConceptsThe concepts described in Chapter 3 correspond to the key notations in class diagrams. Those concepts are th Uml distilled a brief guide to the standard object modeling language (third edition) part 2 ative to keywords, you can use special icons, but then you run into the issue of everyone having to remember what they mean.Some keywords, such as {abstract}, show up in curly brackets. Its never really clear what should technically be in guillemets and what should be in curlies. Fortunately, if you Uml distilled a brief guide to the standard object modeling language (third edition) part 2 get it wrong, only serious ƯML weenies will notice—or care.Some keywords are so common that they often get abbreviated: «interface» often gets abbrevUml distilled a brief guide to the standard object modeling language (third edition) part 2
iated to «1» and {abstract} to {A}. Such abbreviations are very useful, particularly on whiteboards, but nonstandard, so if you use them, make sure yoChapter 5Class Diagrams: Advanced ConceptsThe concepts described in Chapter 3 correspond to the key notations in class diagrams. Those concepts are th Uml distilled a brief guide to the standard object modeling language (third edition) part 2 nd describing what is and isn’t a stereotype is beyond the scope of this book. However, because of ƯMI. 1, many people use rhe term stereotype to mean the same as keyword, although that is no longer correct.Stereotypes are used as part of profiles. A profile takes a part of the ƯML and extends it wi Uml distilled a brief guide to the standard object modeling language (third edition) part 2 th a coherent group of stereotypes for a particular purpose, such as business modeling. The full semantics of profiles are beyond this book. Unless yoUml distilled a brief guide to the standard object modeling language (third edition) part 2
u arc into serious meta-inodel design, you’re unlikely to need to create one yourself. You’re more likely to use one created for a specific modeling pChapter 5Class Diagrams: Advanced ConceptsThe concepts described in Chapter 3 correspond to the key notations in class diagrams. Those concepts are th Uml distilled a brief guide to the standard object modeling language (third edition) part 2 it’s handy to show responsibilities (page 63) on a class in a class diagram. 'rhe best way to show them is as comment strings in their own compartment in the class (Figure 5.1). You can name the compartment, if you wish, bur 1 usually don’t, as there’s rarely any potential for confusion.Static Oper Uml distilled a brief guide to the standard object modeling language (third edition) part 2 ations and AttributesThe ƯML refers to an operation or an attribute that applies to a class rather than to an instance as static. This is equivalent tUml distilled a brief guide to the standard object modeling language (third edition) part 2
o static members in C-based languages. Static features are underlined on a class diagram (see Figure 5.2).Aggregation ane Figure 5.1 showing responsibChapter 5Class Diagrams: Advanced ConceptsThe concepts described in Chapter 3 correspond to the key notations in class diagrams. Those concepts are th Uml distilled a brief guide to the standard object modeling language (third edition) part 2 st frequent sources of confusion in the ƯML is aggregation and composition. It’s easy to explain glibly: Aggregation is the part-of relationship. It’s like saying that a car has an engine and wheels as its parts. This sounds good, but the difficult thing is considering what the difference is between Uml distilled a brief guide to the standard object modeling language (third edition) part 2 aggregation and association.In the pre-UML days, people were usually rather vague on what was aggregation and what was association. Whether vague orUml distilled a brief guide to the standard object modeling language (third edition) part 2
not, they were always inconsistent with everyone else. As a result, many modelers think that aggregation is important, although for different reasons.Chapter 5Class Diagrams: Advanced ConceptsThe concepts described in Chapter 3 correspond to the key notations in class diagrams. Those concepts are th Uml distilled a brief guide to the standard object modeling language (third edition) part 2 Reference!.Chapter 5 Class Diagrams: Advanced Concepts Figure 5.3 AggregationFigure 5.4 CompositionAs well as aggregation, the ƯML has rhe more defined property of composition. In Figure 5.4, an instance of Point may be part of a polygon or may be the center of a circle, but it cannot be both. The g Uml distilled a brief guide to the standard object modeling language (third edition) part 2 eneral rule is that, although a class may be a component of many other classes, any instance must be a component of only one owner. The class diagramUml distilled a brief guide to the standard object modeling language (third edition) part 2
may show multiple classes of potential owners, but any instance has only a single object as its owner.You’ll note that I don’t show the reverse multipChapter 5Class Diagrams: Advanced ConceptsThe concepts described in Chapter 3 correspond to the key notations in class diagrams. Those concepts are th Uml distilled a brief guide to the standard object modeling language (third edition) part 2 hat it can have only one other class as its owner.The “no sharing" rule is the key to composition. Another assumption is that if you delete the polygon, it should automatically ensure that any owned Points also are deleted.Composition is a good way of showing properties that own by value, properties Uml distilled a brief guide to the standard object modeling language (third edition) part 2 to zalue objects (page 73), or properties that have a strong and somewhat exclusive ownership of particular other components. Aggregation is strictlyUml distilled a brief guide to the standard object modeling language (third edition) part 2
meaningless; as a result, I recommend that you ignore it in your own diagrams. If you see it in other people's diagrams, you’ll need to dig deeper toChapter 5Class Diagrams: Advanced ConceptsThe concepts described in Chapter 3 correspond to the key notations in class diagrams. Those concepts are th Uml distilled a brief guide to the standard object modeling language (third edition) part 2 based on other values. When we think about a date range (Figure 5.5), we can think of three properties: rhe Starr date,Chapter 5Class Diagrams: Advanced ConceptsThe concepts described in Chapter 3 correspond to the key notations in class diagrams. Those concepts are thGọi ngay
Chat zalo
Facebook