From version 2.0 the previously independent tagged value is considered to be a stereotype attribute. The name tagged value is still kept. Each stereotype has zero or more tag definitions, and all stereotyped UML elements have the corresponding number of tagged values.
In UML, become is a keyword for a specific UML stereotype, and applies to a dependency (modeled as a dashed arrow). Become shows that the source modeling element (the arrow's tail) is transformed into the target modeling element (the arrow's head), while keeping some sort of identity, even though it may have changed values, state, or even class.
While UML 2.1 uses the «become» stereotype within the specification, it does not define it.
For example, three are used in the entity–control–boundary pattern (ECB or BCE pattern) and four in the robustness diagram (Boundary, Control, Entity and Actor).
Booch, Grady; Rumbaugh, James; Jacobson, Ivar (2005). The unified modeling language user guide: covers UML 2.0. The Addison-Wesley object technologies series (2 ed.). Upper Saddle River, NJ Munich: Addison-Wesley. ISBN 978-0-321-26797-9. 978-0-321-26797-9 ↩
Object Management Group, OMG® Unified Modeling Language® (OMG UML®), v2.5.1, p. 170, December 2017. /wiki/Object_Management_Group ↩