How does QAFE behave in an MS .Net environment? 
QAFE is written in Java, so it will run on any J2EEJEE Appserver or even the lightweight Tomcat/Jetty. The logic that is written in .NET can be accessed through WebServices. The .NET developer needs to provide the WSDL.
 
We have a heterogeneous ICT landscape, using multiple GUIs, databases and operating systems. How will QAFE fit in?
As long as the GUI is using web technologies, it’s quite easy to incorporate them into the QAFE Desktop. The logic in the database can definitely be reused. The operating system really doesn’t matter as long as JDK1.5 or higher is supported. 
 
We’re running several applications on a mixture of handhelds and PC browsers. What possibilities does QAFE offer here? 
QAFE relies for the GUI/Presentation part on the technologies provided by Google and Adobe. The Google WebToolkit supports all major browsers and the Adobe plugin runs in many browsers and is available on many platforms. For handheld devices, the GWT solution would be the best, since this is native HTML/Javascript. 
 
We’re developing in Java using, for example, Struts, Hibernate, and Spring. What added value does QAFE provide? 
Well, Struts is a typical Web 1.0 technology, i.e. it assumes a Page-Oriented Approach. Hibernate and Spring are tied together and most probably used on the back-end. QAFE can easily use the logic on the back-end. The front-end can be replaced by a QAFE Presentation tier which will result in much more interactive and intuitive experience for the end user.  
 
What does QAFE’s infrastructure look like, client and server-side? 
Just like any other web application written for JEE/J2EE platforms.
 
What does the software architecture of a QAFE application look like? 
The software architecture that is used in QAFE is the result of years of experience in the field, best practices, and software engineering theory. The architecture is divided into four clear layers, each with its own function:

  • Presentation tier (the GUI),
  • Business tier (for combining several services and functioning as the bridge between the presentation-tier and the service),
  • Service tier (where you specify the API on the lower level resource that you want to use),
  • Resource tier (where you define the lower level resource on which you want to work!)