Getting started with workflow development

This section presents a compilation of techniques, methodology, experience, and research that promotes the successful development of BMC Atrium Orchestrator workflow processes. Some of the techniques and methodologies used in the development of workflows include:

• An iterative development process: Uses an incremental methodology to progress in small stages, to maintain a focus on manageable tasks, and to ensure that earlier stages are successful before the later stages are attempted.
• A requirements management process:  Addresses the problem of creeping requirements, a situation in which the client requests additional changes to the product that are beyond the scope of what was originally planned. To guard against this common occurrence, requirements management employs strategies, such as documentation of requirements, sign-offs, and methodologies, such as the use case.
• Quality control: Is a strategy that defines objective measures for assessing quality throughout the development process in terms of the product's functionality, reliability, and performance.
• Change control: Is a strategy that seeks to closely monitor changes throughout the iterative process to ensure that records are intact for changes that have been made and that unacceptable changes are not undertaken.

The topics in this section describe a well-defined method that contributes to a successful step in the development of solutions using BMC Atrium Orchestrator workflow processes:

• Workflow basics
• Requirements recommendations
• Workflow coding recommendations