User Tools

Site Tools

Introduction To Authoring

Who are Authors?

An EASAP Author should be:

  • An experienced user of an underlying software application
  • Knowledgeable about the needs of the user community within their organization
  • Trained in the use of EASA Authoring tools

An EASAP Author does not need:

  • Software development experience
  • Training in GUI programming (eg. Java, C++, HTML)
  • Expertise in User Interface design

Obtaining Author-level User ID

Contact an EASA Administrator to get a user name and password.

A list of EASA Administrators is found under:

  • EASA→Help→Support

If you think that you fit the profile of an Author and would like to generate EASAPs of your own, an Administrator may add Author privileges. In addition, you may want to attend an EASA Author training course to become eligible to receive technical support as an Author direct from EASA Technical Services.

Authoring Tutorials‌

Overview of Author Mode

In Author mode, your main focus will be creating EASAPs to be published for use by others in your organization. All the tools required to create, test, document and Publish an EASAP are found on the EASA Web Pages in Author mode.

When to Create an EASAP

It will not always make sense to create an EASAP to run software applications. There are certain characteristics of use that need to exist before creating an EASAP will be worth the effort. These characteristics are:

  • A recurring need to perform similar analysis
  • A potential User base exists
    • → Identify decision-makers that would benefit from being able to use advanced software
  • A commonly used software application has a complicated interface that could streamlined
  • Prior analyses need to be retrieved, modified, and rerun
    • → Create a functional archive of past runs

A common theme in the above list is the idea of repeated need. Creating an EASAP will not make sense for the one-off problem-solving cases. In general, an EASAP is useful for recurring processes.

Page Tools