The EASA system supports the creation of a web-enabled application called an EASAP→ an EASA APPLICATION.

• The functional utility of an EASAP is derived from pre-existing 'underlying software' which may include,
  • a Microsoft Excel spreadsheet
  • a numerical simulation code
  • a running database instance with stored procedures
  • a MATLAB application
  • a batch script that takes input files and creates output files

An EASAP provides a simplified, interactive and web-accessible interface to the underlying software.

• An EASAP life cycle has two distinct stages,
  1. An EASAP under development,
     • An Author uses the EASAP Builder to,
       • Create an EASAP
       • Modify→Save→Test the EASAP over successive iterations
  2. An EASAP deployed into production,
     • A User may,
       • Select and run the EASAP
       • Set inputs
       • Submit a run
       • Obtain formatted data output and figures

Explore these EASAP Examples.

An EASAP will encapsulate into a network application the domain-specific expertise of a specialist, and, transmit this functional knowledge to a decision-maker elsewhere.

In EASA parlance the expert or specialist is given the role of Author.

Conversely, a User may have less knowledge or expertise or might be restricted from accessing intellectual property within a spreadsheet. Nevertheless via an EASAP interface a User may access restricted functionality or conduct advanced computation.

An Author creates a simplified interface to expose to the User a subset of the functionality provided by the underlying software.

• An Author may be motivated,
  • To conceal trade secrets such as proprietary pricing models or risk-benefit regressions
  • To hide configuration complexity and mitigate the potential for input error and erroneous results
  • To automate the workflow involved in doing some kind of analysis

Whatever the motivation, an Author will need to learn how to develop an EASAP in the interactive development environment referred to as the EASAP Builder, see EASAP Builder)

Once development and testing are complete an Author will Publish an EASAP on EASA Server, a User may access it via a web browser.

The EASA Server manages all aspects of a deployed EASAP's operation in production.

• For example,
  • A Published EASAP may be hosted via a cluster of EASAP Servers.
    • → The EASA Server redirects the User to a machine with the lightest load.
  • A User sets inputs and submits them for processing.
    • → The EASA Server automatically creates a results folder for .txt, .html or .pdf files.
    • → The User may view output values directly in a web browser.
  • Database connectivity is configured centrally on the EASA Server
  • The EASA Server archives input and output data in case a result needs to be audited for accuracy.
  • A User records and stores informal notes alongside particular submission output.
  • An EASAP may generate and store text, HTML, images and PDF files in the results folders.
  • Newer updated versions of an EASAP may be Published with descriptive text.

Three completed EASAP's are distributed with EASA to illustrate the development and production deployment of an EASAP.

• Mortgage Calculator
• Stock Screener Tool
• Cantilever Plate Loading Analysis

A brief description and a screen shot of each user interface are provided below.

Play around with an example EASAP, open one and examine it in the EASAP Builder, test it, and Publish it to illustrate the life cycle of an EASAP. (See Get started with EASA Evaluation on Windows)

The Mortgage Calculator runs a finance calculation in an Excel spreadsheet.

The Stock Screener Tool searches a database and builds and runs custom SQL queries from user inputs.

The Cantilever Plate Loading Analysis runs a Windows batch application to simulate a user-selected load on a plate with variable dimensions.