Examining the UML Models: Static Models - Summary
(Page 13 of 13 )
In Chapter 4, you learned about the behavior diagrams, and you saw how the behavior diagrams serve two purposes: they give you an overview of the solution you’re planning, and they enable you to create the structural diagrams, because they provide you with information about what happens in your solution.
In this chapter, you’ve learned about the structural UML models, which describe the static structure of your solution. You’ve learned how to generate code for your solution by creating the static structure diagram–—the class diagram. You’ve also seen how the structural diagrams directly build on the information you’ve gathered for your solution during the creation of the behavioral diagrams. Finally, you’ve seen how the UML elements map to .NET code and declarations.
You’ve now learned about the UML diagrams in detail. In the next chapter, you’ll learn how to plan an enterprise solution with the knowledge you’ve just obtained.
Footnotes:
1. Static structure diagrams can be class diagrams or another diagram
type covering the static structure (for example, an object diagram
showing physical real-life objects).
2. This is true for all UML CASE tools and not just a disadvantage for
VEA users.
3. In VEA, events are operations, because of UML 1.2 compliance.
However, this isn’t the case in UML 1.4 and later.
4. Methods are functions by default in C#.
5. In C#, this is a method with the void keyword in the signature to
indicate that it doesn’t return a value.
6. Well, your code wouldn’t work as intended if not, would it?
7. With garbage collection, the Finalize method isn’t really a
destructor in the true sense, but we’ll stay with the OOP
terminology.
8. Shadowing means that the operation in the base class with the
same name as an operation in the derived class is hidden, but still
accessible. A shadowed operation can be called directly from the
caller of the derived class, unlike an overridden operation, which
can be called only on the derived class.
9. .NET assemblies can consist of one or more physical files, or even
be in dynamic assemblies that are contained in memory. However,
for the sake of this discussion, an assembly equals one physical file.
10. “DLL hell” refers to the annoying struggle of registering and
unregistering the different versions of .dll files in the Registry,
often resulting in a DLL version incompatible with the application
being registered. .NET solves this by making the assemblies
(DLLs) selfdescribing through the use of a manifest, which means
that registration is no longer necessary, and allows the use of side-
by-side assemblies, or private assemblies.
11. VEA allows you to generate code without assigning your classes
to components. You simply choose the physical file names when
generating code.
12. To some extent, this will prevent you from distributing your
classes to different physical machines. This isn’t entirely true,
however, because the same component can be running different
machines at the same time.
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |
|
 This article is excerpted from Enterprise Development with Visual Studio .NET, UML, and MSF written by John Erik Hansen and Carsten Thomsen (Apress, 2004; ISBN: 1590590422) Buy this book now.
|
|
