This document attempts to illustrate the basic flow of our ever-growing SAFS Framework Architecture. This document will grow with information as our development moves forward.
See also: Java Interface, SAFSDEV Project
Fig. 1: SAFS Framework Architecture Flow
Figure 1 shows the existing SAFS Framework tools and STAF services. The upcoming Selenium engine is also shown. The completion of this engines is tentatively expected in the first quarter of 2008.
Note: IBM Rational Robot (SAFS/RRAFS) currently cannot be run as a standalone SAFS/STAF engine. It can be a Driver, it is its own engine, and it can talk to or drive other SAFS/STAF Engines like IBM Rational Functional Tester (SAFS/RobotJ). However, currently IBM Rational Robot cannot be externally driven as a standard SAFS engine by another Driver like the TID (SAFSDRIVER).
Note: WinRunner (SAFS/WRAFS) is a standalone execution engine that cannot call other SAFS engines and it cannot be externally driven by another Driver like the TID (SAFSDRIVER).
Note: The Java JVMAgents and Abbot are essentially the same. Abbot is a subclass implementation exploiting the tool-independent JVMAgents. Abbot has minimal support implemented for proof-of-concept until such time as a greater need arises and resources are dedicated.
Fig. 2: SAFS Framework Application Environment Support
Figure 2 shows the existing SAFS Framework support. This is intended to show which types of application environments are supported by specific toolsets.