Test your UML knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/12Score 0
What is the purpose of an "interface" notation in UML class diagrams (often shown with a `<<interface>>` stereotype label), and how does a class "implementing" an interface differ visually from a class "inheriting" from another class?
In this round
What is the purpose of an "interface" notation in UML class diagrams (often shown with a `<<interface>>` stereotype label), and how does a class "implementing" an interface differ visually from a class "inheriting" from another class?
What is a UML "activity diagram" used for, and how does it conceptually relate to a traditional flowchart?
What is the difference between "association", "aggregation", and "composition" as three related but distinct relationship types in UML class diagrams?
What is UML (Unified Modeling Language)?
What is the purpose of a "package diagram" in UML, and what does it help communicate about a larger software system's organization?
What is a reasonable strategy for a team deciding how much UML documentation to actually maintain for an ongoing, evolving software project, given the earlier-noted risk of documentation becoming outdated?
What is a reasonable comparison between a UML class diagram and an Entity-Relationship (ER) diagram, given that both are used to model structured relationships between data entities?
What is a reasonable justification for choosing to sketch a UML diagram on a whiteboard during a design discussion, rather than always immediately creating a polished, tool-generated diagram using dedicated UML software?
What is a UML "component diagram" used for, and at what level of a system does it typically operate?
What is a reasonable justification for using a sequence diagram specifically to design (rather than only document after the fact) a complex interaction between multiple services in a distributed system, before writing the actual implementation code?
What is a reasonable justification for a development team using UML diagrams during the DESIGN phase of a project, before writing actual implementation code?
What is the purpose of a UML "use case diagram", and who is it typically most useful for communicating with?