OOAD is Object Oriented Analysis & Design - everything up to coding. UML is a good notation for recording certain parts of analysis and design. A lot of other stuff lives as plain text, pictures, etc.
Use cases are not really object oriented, and could be used for purely procedural systems. But they are often used in OOAD, and I'd buy the
test answer.
I think of UML as more than a visual presentation standard. It is a language with complex semantics that represents different aspects of a common underlying model. It can be (but is not always) linked to a concrete underlying model by a drawing tool.
UML defines
thirteen diagrams as artifacts. The use case diagram with a symbol for use case is one of them, but I agree that use case itself is not a UML artifact.
[ June 30, 2003: Message edited by: Stan James ]