• slider3

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

  • slider4

    ABODE™ business transformation methodology  founded on EA3.0

  • slide1

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

  • slider2

    Generalized Enterprise Function Framework  (GEFF)

Functional Testing tools

 

Tools to support Managing Functional Completeness

To support Managing Functional Completeness Enterprise Architects delivers the following tools:

  • ARC/Requirement Collection  
Collecting all functional and non-functional Requirements based on design readiness
  • ARC/Defining the status of Work Done
Calculating the status of the functional and non-functional Requirements
  • ARC/Reporting Work Done
Reporting the realization of the Delivery of Functionalities based on the status (As Is) and the planning (To Be)
  • ARC/Monitoring Dashboard 
Delivering individual, team and project dashboards of progress

Tools to support Service Testing

To support Service Testing Enterprise Architects delivers the following tools:

      1. ATM/Information and Technical Services  Enabling testing the functional Data Delivery of Information and Technical Services
      2. ATM/Information and Data Services  Enabling testing the functional Data Delivery of Information and Data Services
      3. ATM/Information and Presentation Services  Enabling testing the functional Data Delivery of Information and Presentation Services
      4. ATM/User Interaction Enabling the testing of the complete User Interaction and Experience

Tools to support User Interaction Testing

To support User Interaction Testing Enterprise Architects delivers the following tools:

  1. ATM/User Interaction Enabling the testing of the complete User Interaction through
    • Testing the functional correctness of buttons, widgets, error messages, etc.
    • Testing the HELP-windows [?]
    • Testing the triple A Knowledge windows with [!]
      • Architectural Knowledge components
      • Augmented Knowledge components
      • Actionable Knowledge components
  1. ATM/User Experience Enabling the testing of the complete User Experience through
    • Testing the cooperation of all of the above mentioned components in their relationship with each other

 

Tools to support Business RuleSet Testing

To test these Business Rules Enterprise Architects delivers the following tools:

  • ARM/RuleSet Management for                                         
    • Testing Business RuleSets interactively
    • Check the correct execution of the Business Rule Syntax and Semantics
    • Monitor the progress of the execution of Business RuleSets

The Rule Analyst can interactively define the contents of the different components like:

  • Input and Output Parameter attributes
 
  • Facts, or
 
  • Use the developed and tested
Services to automatically access the databases/data stores and use the contents for testing
  • ARM/RuleSet Source Management
Managing the content of the sources which the Business RuleSets are referring to
  • ARM/Technical execution 
Testing the Technical Services through protocols, etc.

Tools to support Knowledge Function Microflows

To test the Microflow Enterprise Architects delivers the following tools to test the execution of the Microflow:

  1. AFI/Defining the Knowledge Function Microflow After drawing the Microflow the different components can be tested on two screens:
    • A Screen with the User Interaction (Input/output) results when applicable
      The Screen Mode can be changed during testing
    • A Screen with the Debugging results
      The Requirements can be shown and comments can be added to the Debugging results
  2. AFR/Test Report 
    A Test report of the content form the different services, Business RuleSets, Microflow steps, Error Messages, etc.

 

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.