Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Develop formal designs

For each use case, create formal designs from the initial workflow sketches. This process accelerates the creation of the workflows in BMC Atrium Orchestrator, and ensures the highest content quality and performance. During this process other group members’ involvement might be required. Formal workflow designs should contain:

  • Identified systems required
  • System communication methods
  • Data required of each system
  • Business logic required
  • Data required for business logic
  • Inputs and outputs for each workflow/process
  • Identify required metrics for benchmarking orchestration activities
  • Measurement points

A sample formal workflow design is shown in the figure below.

Formal workflow design

Sample_formal_design.png

 

Recommendation

When developing the designs, analyze the designs for reuse possibilities. Consider where else basic automation, logic, or data might be applied in other use cases. Planning for reuse can avoid redeveloping workflow segments that are very similar.

Where to go from here

Automate-the-workflows

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*