Features and benefits

Top  Previous  Next

There are a host of reason for using eaForms.  The table below is a summary of key features of eaForms and some of the benefits - see Another list of features for more




Designer defines the content of the form

Content matches need with tailored forms that are relevant to the project and the specific user

Reduces complexity by eliminating unnecessary stuff

Makes the forms easier to understand

Can include content that may exist on multiple forms within EA

Support for links to other elements

Forms can combine information that would otherwise mean accessing multiple forms to increasing productivity for the experienced user

WYSIWYG form builder

See and test the form as you build it

Designer defines look and feel (layout, colour, font)

Use of colour and/or layout to assist with the flow for data entry /editing

Simple forms can be reduced

Makes EA more accessible to new EA users

Designer defines work flow

Helps user by leading through optimal sequence

Define navigation through different forms

Able to extend data entry/editing across multiple forms to break work into manageable steps

Enhanced controls allow the presentation of information into single place for viewing and editing

Reduces the need for users to look across several data sources, minimising time and potential confusion

Access to other element forms within context on current form

Edit related elements within current context rather than switching between elements

Maintain a library of Form Definitions

Keep a set of Form Definitions in a library

Export sub-sets of Form Definitions

Create a sub-set of Form Definitions targeted to specific users

Mandate input for desired items

Ensures that users provide required input

and can help drive consistency across model(s)

Help drive standards of modelling by ensuring required content is input

Restrict input to pre-defined values

Supports consistency across model

Can help with profiles where there are a large number of optional tagged values

Forms can be target at elements defined by Element Type and none, one or more stereotypes

Ability to provide forms that are tailored to specific modelling elements

Different forms for different modelling elements

Auto configure from central servers

Minimises administration and supports automatic updates for form definitions

Autoload of run time forms

User management minimal (if at all)

Access to element editor same as normal EA properties editor

No change needed in user behaviour

Support for MDG's - with relevant data

Helps designer selecting and setting values

Option to include button to switch to EA provided editor

Allows experienced users to use eaForms whilst not compromising their ability to access other information as and when needed