Requirements

pdlNoRQlabelRQpdl 0RQheight .4pt depth 0pt width .5em

1

The configuration file must be in a human readable format.

Rationale

When the configuration file is in a human readable format, it can be edited in any plain text editor by any human. This relinquishes the needs for a GUI to edit configuration files and can be done quite easily remotely.

NoRQlabelNoRQlabelRQNoRQlabel 0RQ

height .4pt depth 0pt width .5em

1

The configuration file must support comments.

Rationale

The configuration file becomes more readable by adding comments. This should lead to a better interpretation of the file and reduce the number of errors made.

NoRQlabelNoRQlabelRQNoRQlabel 0RQ

height .4pt depth 0pt width .5em

1

The configuration language must support for more than one policy rule.

Rationale

By allowing several smaller policy rules, instead of one huge rule, the readability of the configuration file is enhanced and thereby reducing the number of errors.

NoRQlabelNoRQlabelRQNoRQlabel 0RQ

height .4pt depth 0pt width .5em

1

A policy must be reusable inside another policy.

Rationale

By allowing policy rules to contain policy rules, one reduces the amount of double policy rules. Thus limiting the number of errors. Should an error be discovered and fixed, it is fixed for all policy rules. No fixes are forgotten this way.

NoRQlabelNoRQlabelRQNoRQlabel 0RQ

height .4pt depth 0pt width .5em

1

The language must support both a TRUE and FALSE path, when a part of the policy rules fails.

Rationale

Policy modules return either TRUE or FALSE. When a module succeeds or fails, two different paths can be taken to complete the policy. The language must reflect this behaviour.

0