<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=287945&amp;fmt=gif">

Implementing Workflow Reduces Development Cycle Time

Posted by Dileepa WIjayanayake on Sep 3, 2014 6:16:04 PM


Implementing Workflow Revisions Implementing Workflow Revisions


Using workflow to implement the business process layer of your custom applications can save time and money. With a hard-coded process layer, adapting to evolving business practices requires software developer resources to make application updates. You either rely on the original developer or have to find another developer who understands both the business domain and the code platform. And after the hard-coded changes are compiled, the application has to be tested and re-deployed to the production environment.

However, if your application business layer is implemented using one of today’s leading workflow products, domain experts instead of developers are able to tailor the applications to the day-to-day needs of their operations.

Cutting application development cycle time using workflow

Let’s take a simple example as the “debt collection workflow”.  In this workflow, the following steps are taken:

  • Review debt case
  • Contact the debtor and try to resolve
  • Debtor pays the full amount
  • Debtor pays using installment plan
  • Debtor agrees not to pay, send to legal action
  • Update the status of the case
  • End of the debt case

The above process may look graphically as follows:

Implementing Workflow Reduces Application Development Cycle Time

Given the above process, let’s say the application was built using the traditional development practices of hard coding the process to the application.  A month after deploying the application, let’s say the process changes to the following:

Implementing Workflow Reduces Application Development Cycle Time

In reference to the above graphic, the section with the dotted line represents the enhancement to the process.   If the application was developed using workflow, the processes can be easily enhanced without any development changes and deployed to production within hours or days.

Per the model-view-controller or three-tier software design pattern, typical application development can be divided into three parts – data access, business logic, and user interface. The table below estimates the percentage of development time spent on each of the tiers with and without workflow.


Implementing Workflow Reduces Application Development Cycle Time Development Time


As shown above, workflow implementation affords a significant savings of development time within the data access and business logic layers, allowing more focus to be given to the user experience.  Below are some of the feedback numbers we have received from our customers regarding time saved within their projects overall using cDevWorkflow.


Implementing Workflow Reduces Application Development Cycle Time Cycle Time Improvements with Workflow


As seen in the data in the above table, on average, customers have cut project implementation time in half by adding workflow to their application development.  Learn how to save time and money on your development projects today by implementing workflow.


A small sampling of the Workflow Technology for BPM Solutions contained within our cDevWorkflow product offering can be found here: Workflow Technology That Works.

[hs_form id="9"]

Learn more about our Process Automation & IT, QA Services or Software Development products and solutions on the Web!  Visit us at: Innovative Process Solutions


Topics: Blog, implementing workflow, Workflow Redesign, implementing workflow revision, implementing workflow edit, implementing workflow change, implement workflow revision, implementing workflow engine, implement workflow