The following built-in stereotypes may prove useful in helping you define components :
The ‚ «entity ‚ » stereotype signifies persistent information related to a particular business concept.
The ‚ «process ‚ » stereotype signifies that the component is transaction based.
The ‚ «service ‚ » stereotype signifies that the component is stateless and that its only purpose is to compute some value.
The ‚ «implement ‚ » stereotype signifies that the component implements a class identified by a specification (see the section "Other Stereotypes on Classes" in Chapter 1).
The ‚ «buildComponent ‚ » stereotype, when assigned to a set of components, signifies that the components have been grouped for organizational or system-level development purposes.