Best Practices: GoalsThis section presents a set of best practices intended to minimize risks to projects, improve system resiliency, allow developers to achieve higher productivity and improve BPM development processes.
The intent is not to prescribe a rigid approach or implementation methodology because we do not believe there is a unique and singular approach to SOA-based BPM implementation. Rather, BPM projects should be managed and governed by the same set of software engineering methodologies and project management principles adopted by an organization and deemed appropriate to meet the delivery needs, scale, criticality and complexity of the project. What we highlight are those factors and aspects that are unique to a BPM-based implementation using ActiveVOS. These best practices should serve as input to various phases of a project.
- Design considerations that help identify risks early to avoid surprises at later stages of a project
- Quality assurance practices, an integral part of any development effort, that need to be planned for
- Manageability and governance that should not be considered as an afterthought
This article is especially helpful to anyone who is involved in the scoping, implementation, deployment and management of a BPM application.