4GL's - Development software

Problems and pitfalls

Overview | Problems & pitfalls | Standards

Overview

There is still resistance to 4GL's though this is steadily being eroded as 4GL's mature.

Once of the most common reasons given by "traditional" computer users is that since 4gls encourage the use of prototyping, no formal specifications are designed.

This section deals with the problems and pitfalls that may be encountered when using a 4GL.

Problems & pitfalls

Lack of controls

Due to inexperienced end-users.
Data dictionary integrity needed.
Easy to reinvent parts of the system.

Prototyping forever

changing and improving the system easy.
The temptation is for perfectionists to engage in a lifelong project!, or the technically minded to explore bold new horizons!

The "settling down" period is still going on

Lack of analysis

Data relationships fuzzy, and non-normalised (in a relational sense)
Earlier 4GL's (and some current products) were more suited to the development of small systems

Performance

Slow when compared to a 3GL
Problems of inefficiencies

Internal company politics

DP Departmental control v's end-user control!
Eliminate DP dependency
Impartial help & advice are not available to potential purchases
The need for changes within an organisation (sometimes radical)

Treated like a 3GL

Satisfactory use may depend on the approach adopted

Are user friendly

[Cartoon: User friendly keyboard]

Often require sophisticated end users, and often training needs are unidentified

Standards

Why are standards important ?

As a general rule, standards are intended to:

Improve efficiency
Improve effectiveness
Allow control & supervision
Enable training
Allow clear communication
Encourage good practices
Promote ideas
Show what (ideally) should be done
Satisfy legalities
Assist in safety measures

With 4GL's the situation is different:

No language standards exist. Some standardisation has "crept in".
For example, where the 4GL uses a query language, this is often now SQL.

Documentation standards are often seen as being part of the traditional systems life-cycle approach, and hence are considered inappropriate for 4GL's.

Organisational standards should at least be set to cover areas such as:

Documentation
Database design
Format/style of code/procedure produced.
Content of procedure
Naming of procedures, data items etc.
Creation of data files