The document discusses types and roles in UML. Types are conceptual classes used during analysis to identify possible object types in a system. They do not have methods or instances. Roles represent the behaviors of entities in particular contexts. An object can play different roles depending on the context, presenting different properties based on its role. Types and roles are modeling concepts in UML used to describe the abstraction of classes and behaviors before implementation.

1. TYPES AND ROLES
in UML
Presented By : Suravase Pratima S.
Roll No : 86
Class : TE-IT

2. Types
• A type is a class that may have attributes,
associations, and operations, but does not have
any methods
• Types are commonly used during analysis
activities within a development process to
identify the kinds of objects a system may
require. You can think of types as conceptual
classes, because they are ideas for possible
classes. Also, because types do not have methods
and represent roles only, they do not have
instances.

3. Figure. Types
<<type>>
TProjectManager
<<type>>
TResourseManager
<<type>>
TSystemManager
<<type>>
THumanResourse

4. Roles
• A Role is a behaviour of an entity participating in a
particular context.
• OR, a Role is the face that an abstraction presents to
the world. For example, consider an instance of the
class Person.
• Depending on the context, that Person instance may
play the role of Mother, Payer Of Bills, Employee,
Customer, Manager, Pilot, Singer, and so on. When
an object plays a particular role, it presents a face to
the world, and clients that interact with it expect a
certain behaviour depending on the role that it plays
at the time.
• For example, an instance of Person in the role of
Manager would present a different set of properties
than if the instance were playing the role of Mother.

5. Figure : Role

6. THANK YOU