Edit

SDLC types

We, all WorkFusion practitioners, agree to follow such practices as we believe it is very important for automation delivery success. Aligning on exactly the same approach by all three parties: Customer, Partner, and WorkFusion will allow us "to speak same the technical language".

important

We recommend considering three patterns of how to build Software Development Life Cycle (SDLC) for WorkFusion deliveries based on use case complexity.

Simple SDLC

NO-CODE | ODF NOT APPLICABLE

Use case attributes to classify for Simple SDLC:

1. Use case doesn't have cognitive work automation (ML) in scope
2. Targeted business applications can be automated using WorkFusion Studio actions/RPA Recorder capabilities (possible with Custom Actions for workarounds)
3. Central server Control Tower deployment performed manually using Studio capability
4. For Production environment, it is sufficient to use either IA Cloud Developer or IA Cloud Business

The team uses IA Cloud Business with its Studio's actions/RPA Recorder to become the main development tool. In this type of implementation, teams expected to be small. In most of implementations, we expect to have SMEs/Junior Engineers as automation developers. Such teams are considered as low-skilled and recommended to follow a simplified development lifecycle. Such teams use Control Tower as the Business Process/Manual Tasks design tool. Bot Tasks can be designed one-by-one either in Control Tower or WorkFusion Studio and deployed to central Control Tower.

Advanced SDLC

CODE | LIMITED ODF

Use case attributes to classify for Advanced SDLC:

1. Use case doesn't have cognitive work automation (ML) in scope
2. Organization automates multiple use cases and teams are expected to reuse code
3. Developers create automation using Bot Tasks coding in Control Tower and WorkFusion Studio using Web-Harvest components and custom Groovy coding
4. ODF pre-packaged components are usable for use cases
5. Production operations expected to be driven by Analytics
6. For PRODUCTION environment, it is sufficient to use SPA Tier 1 (ML components not included)

Reusable components and deployment automation from ODF can be integrated with. There are converters between WH/Groovy and ODF. The team avoids heavy Java coding which is a part of ODF which gives all flexibility. So, this way still fits low team Java expertise and at the same time lets the team benefit from ODF.

Enterprise SDLC

CODE | ODF RECOMMENDED

Use case attributes to classify for Enterprise SDLC:

1. Use case has both RPA and cognitive work automation (ML) in scope
2. RPA part includes 3+ complex unstable various-type applications automation
3. Enterprise security is must have
4. Comprehensive exception handling is in scope
5. Production operations expected to be driven by Analytics
6. Organization automates multiple use cases, and teams are expected to reuse code
7. ODF pre-packaged components are usable for use cases
8. Production operations expected to be driven by Analytics
9. For PRODUCTION environment, it is sufficient to use SPA Tier 2 (ML components included)

We see this kind of complicated use cases in the majority of Enterprise clients. CI/CD, VCS, ODF, WorkFusion Studio as IDE: all proven Java development practices must be used.

ODF provides all the Enterprise tools in order to build convenient SDLC for Enterprise-grade WorkFusion deliveries. It is important to establish a clear technical way and process which defines code sharing between the organization's automation teams. ODF provides reusability by its design with guides defined and explained via various training channels.