Each service candidate can be modeled as a stereotyped UML class, where the stereotype reflects the layer to which the service candidate is assigned (for example, <<EntityCentricService>>). Service task candidates may be modeled as UML operations in each of these classes.

Service composition in this early analysis view may be modeled as UML aggregation relationships, preferably in a hierarchical (tree) notation.

Although not essential, it may be helpful to arrange the service candidates (classes) in horizontal swimlanes, with one lane for each of the architectural service layers (orchestration in the top swimlane, and utility application services in the bottom swimlane).