© 2010 Pearson Addison-Wesley. All rights reserved. Addison Wesley is an imprint of Appendix A: UML Java Software Structures: Designing and Using Data Structures Third Edition John Lewis & Joseph Chase

1-2 © 2010 Pearson Addison-Wesley. All rights reserved. 1-2 The Unified Modeling Language The Unified Modeling Language (UML) has become a standard notation for software design It is unified in the sense that it is the synthesis of three separate notations It is language independent It includes various types of diagrams which use specific icons and notations However, it is flexible – the details you include in a given diagram depend on what you are trying to capture and communicate

1-3 © 2010 Pearson Addison-Wesley. All rights reserved. 1-3 UML Class Diagrams UML class diagrams may include: –The classes used in the system –The static relationships among classes –The attributes and operations of each class –The constraints on the connections among objects An attribute is class level data, including variables and constants An operation is essentially equivalent to a method May include visibility details

1-4 © 2010 Pearson Addison-Wesley. All rights reserved. 1-4 LibraryItem class diagram

1-5 © 2010 Pearson Addison-Wesley. All rights reserved. 1-5 A UML class diagram showing inheritance relationships

1-6 © 2010 Pearson Addison-Wesley. All rights reserved. 1-6 A UML class diagram showing an association

1-7 © 2010 Pearson Addison-Wesley. All rights reserved. 1-7 One class shown as an aggregate of other classes

1-8 © 2010 Pearson Addison-Wesley. All rights reserved. 1-8 A UML diagram showing a class implementing an interface

1-9 © 2010 Pearson Addison-Wesley. All rights reserved. 1-9 One class indicating its use of another