• Identify as many process-agnostic functions as possible that can be isolated as reusable code, within the constraints of the project's objectives and timeframe.

• Identify any dependencies that tie the logic to the current process or to its position within that process.

Determine if there are any input values or parameters that require business rules, decision points, formulas, conditional statements, or other types of workflow logic that will cause dependency (task-centric services).

• Keep application service candidates as generic as possible to foster reuse.

• Review the decomposition of the business processes to determine if a service candidate should be modeled as a service composition.

• Identify the boundaries of the logical units of work so that autonomy can be achieved.

• Model service candidates so that are properly partitioned and are modeled according to:

  • Business requirements

  • Consistent standards

  • Industry conventions

• Categorize services based on their role.

Be clear as to how different types of service candidates relate to each other and how you identify and compose service candidates so that the models are consistent.

• Apply service orientation principles to each grouping of service task candidates and application service task candidates.