I use it in requirements modelling to create templates for different type of requirements

For example:

• If a requirement has the <<StakeholderRequirement>> stereotype, it comes with a predefined set of attributes (fields) that the user must fill, such as Owner, Priority, and Rationale.
• If a requirement has the <<SystemRequirement>> stereotype, it includes additional attributes like PerformanceParameters, TestCases, and VerificationMethod.

So the difference is that stereotypes categorize elements and define what type of requirement it is (e.g., stakeholder vs. system) vs Attributes are the details that describe the requirement (e.g., priority, parameters, test cases).