• slide1

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

  • slider3

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

  • slider2

    Generalized Enterprise Function Framework  (GEFF)

  • slider4

    ABODE™ business transformation methodology  founded on EA3.0

Testing Cases

In the Netherlands there are two types of cases:

  1. Cases as mentioned and used in CMMN1.1. Examples are Workflows or Work Processes like those managed by an internist at a hospital that initiates different researches on your health: each time the results of a investigation are available the flow of activities can change in a different way then foreseen before
  2. Cases that contain relevant information for the Actor that initiated the Workflow or Work Process. For example client requesting the status of a complaint about products he/she ordered.

Problems and Solutions

Defining Workflows for the two types of cases is even more complex than the earlier mentioned Workflows. Besides the there mentioned complexity the complexity of type 2 Cases is higher because for each processed workflow step the case number and the case status should be logged for the client. The Enterprise Architects solves this in a likewise way as mentioned before.

 

Tools to support Case testing

To support Case testing for type 1 and type 2 Cases is solved by Enterprise Architects in the same way as for Workflows.

 

Advantages of the Enterprise Architects approach

Also the same advantages of testing Cases is corresponding to the Workflow Testing:

  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