A UML diagram can represent structural information, or general types of behavior. Structure diagrams help document architecture of software systems. There are many types of structure diagrams, One case is a class diagram that represents attributes and relationships. Another case is a component diagram that represents how components split into software systems.
They can help to show the different objects in a system, their attributes, their operations and the relationships among them. For our example, it will be based around the winner object. All of the different attributes will be things like age, marriage status, birth place etc. The relationships will depend on which attribute for example age will be related to birthplace.
A use case is a list of actions or event steps typically defining the interactions between a role and a system to achieve a goal. I think it basically lists a path for every action and then reaction that the system/user can have. Based on what the user does, the system will respond in one way and so on.
UML
Use case 1 - Turing award winner
Actor - Professor
Basic Flow - Professor wants to know information about Turing award winners
Alternative flow - professor wants to know where and when the winner was born
Alternative flow - professor wants to know about the education of the winner
Alternative flow - professor wants to know their current status/occupation
