Therefore, it is very important that all the other elements
of the model, such as aggregations, compositions,
generalizations, interfaces, enumerations, etc., should not
be used for conceptual analysis. Keeping it simple enables
even UML novices to understanding it after getting a little
explanation. Additionally, we can provide textual
descriptions for each of these concepts and generate
printable or navigable domain vocabularies. We believe
this should be the first artifact since it sets up the
vocabulary, which should be used for defining other
requirement model elements, cases, etc.