1. What you need to know about UML Not much but you need to know something

2. Go To The Argo UML Editor (it’s in the links sections of Sakai) CLICK HERE

3. UML Stands for Unified Modeling Language Has notations for a great variety of diagrams But we will only discuss two in this class: – Class Diagrams – Sequence Diagrams

4. Most Important Point The purpose of a diagram is not to be an complete description of the system. The purpose of a diagram is to explain how some part of the system works. Therefore: 1.Know what you are trying to convey 2.Leave off irrelevant details

5. A Class Person String name int height DBObject cacheData + getUniqueID(): void - loadDBCacheData(): DBObject Every variable and method should not usually be depicted.

6. Representing a Variable Person String name int height DBObject cacheData + getUniqueID(): void - loadDBCacheData(): DBObject Person String name int height + getUniqueID(): void - loadDBCacheData(): DBObject DBObject String DBname - loadDBCacheData(): DBObject

7. B has 1 to any number of A objects

9. Sequence Diagram