• slide1

    Enterprise Architecture 3.0 (EA3.0) - the third wave in Enterprise Architecture approaches

  • slider4

    ABODE™ business transformation methodology  founded on EA3.0

  • slider3

    A3 KAM - Triple A(Architectural, Actionable and  Augmented) Knowledge Assets Management

  • slider2

    Generalized Enterprise Function Framework  (GEFF)

Testing Workflows

Problems and Solutions

Defining Workflows is often a complex test because not only the authentication and authorization of users must be tested, but also the performance of the workflow, complete with finding bottlenecks in the process model, the ability to move tasks from one agenda to another, temporarily give users belonging to other teams other authorizations, etc. besides the functionality of the App(lication)s.

 

With the Enterprise Architects approach the following distinctions can be made:

  1. Testing the Workflow only
    • Simulating the Workflows automatically with (for Performance Testing to find bottlenecks, etc.) predefined Events and Event-related contents without Authorization of the Users and their Roles
    • Testing the Workflows on the sequence and conditions of how and when the different App(lication)s are actually used
  2. Testing the Workflow including the correct functioning of the App(lication)s – this is how the actual operation will take place

 

Tools to support Workflow testing

To support Workflow testing Enterprise Architects delivers the following tools:

  • APM/VCA/Process Simulation
 Simulating the Workflow based on one of the two modes (BPMN only) and different ways of Value Creation like time, throughput, money (costs, revenue, profit, etc.), etc. So this is related to above mentioned situation 1.1
  • APM/VCA/Workflow Simulation
 Simulating the Workflow without actual users including the different Value Creation vectors. So situation 1.2
  • APM/Workflow Execution
 Executing the Workflow with actual users including the different Value Creation vectors. This is the “Real Life” execution with Users with their Roles, including Authorization, Agenda Management, etc. So situation 2.

Advantages of the Enterprise Architects approach

  1. Based on the necessity of correctly simulating or executing different situations the Enterprise Architects approach offers completely different possibilities after which the results can be used to improve the workflows.
  2. The SAFe™ Core Values are safeguarded and improved as follows
    • Alignment
    • Built-in Quality
    • Transparency
    • Program Execution