19.12.2012 Views

IT Baseline Protection Manual - The Information Warfare Site

IT Baseline Protection Manual - The Information Warfare Site

IT Baseline Protection Manual - The Information Warfare Site

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Safeguard Catalogue - Organisation Remarks<br />

____________________________________________________________________ .........................................<br />

S 2.62 Software acceptance and approval Procedure<br />

Initiation responsibility: Head of <strong>IT</strong> section<br />

Implementation responsibility: Head of <strong>IT</strong> section<br />

<strong>The</strong> use of <strong>IT</strong> for dealing with certain tasks requires that computerised data<br />

processing works as perfectly as possible, as the individual results can in most<br />

cases not be checked. In the course of a software acceptance process,<br />

therefore, it is checked whether the software works without error, i.e. whether<br />

the software works with the desired degree of reliability and whether it creates<br />

any undesired side effects. With the subsequent approval of the software by<br />

the relevant body, permission is granted to use the software. At the same time,<br />

this body assumes the responsibility for the <strong>IT</strong> process implemented by the<br />

software.<br />

In regard to software acceptance, a distinction is made between software<br />

which was self-developed or developed by a third party and standard software<br />

adapted for special uses.<br />

Acceptance of self-developed software or software developed by third parties<br />

Before the order to develop software is placed internally or externally, the<br />

software requirements must be defined. <strong>The</strong>se are then used as the basis for<br />

the rough and detailed planning for implementation. Using these documents,<br />

the relevant body, not the body responsible for the software development,<br />

generally draws up an acceptance plan.<br />

In general, test cases and the expected results for the software are determined.<br />

Using these test cases, the software is tested and the difference between the<br />

calculated and expected result is used as an indication for the correctness of<br />

the software.<br />

In order to develop test cases and to implement these tests, the following<br />

should be observed:<br />

- <strong>The</strong> test cases are developed by the relevant body<br />

- No data of the actual operation should be used for test cases<br />

- Test data, particularly if these are compiled by copying actual data, may<br />

not contain any confidential information; person related data should be<br />

made anonymous or simulated<br />

- <strong>The</strong> implementation of the tests should have no effect on the actual<br />

operation; if possible, a test computer should be used which is logically or<br />

physically separate<br />

Acceptance should be denied if;<br />

- Serious errors are detected in the software<br />

- Test cases occur where the calculated results do not correspond to the<br />

estimated results<br />

- User manuals or operating instructions are not available or inadequate<br />

- Documentation of the software is not available or inadequate<br />

____________________________________________________________________ .........................................<br />

<strong>IT</strong>-<strong>Baseline</strong> <strong>Protection</strong> <strong>Manual</strong>: Oktober 2000

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!