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 />

- <strong>The</strong> running capabilities of the product must be checked in the planned<br />

usage environment; this comprises in particular a check of screen editing,<br />

printer output, mouse support, networking capability, etc.<br />

- <strong>The</strong> completeness of the product (programs and manuals) must be checked,<br />

e.g. by comparing with the inventory, the product specification or similar.<br />

- Short tests of program functions should be performed which are not<br />

explicitly mentioned in the requirements, with regard to function,<br />

plausibility, freedom from error, etc.<br />

Functional tests<br />

<strong>The</strong> functional requirements which were placed on the product in the<br />

Requirements Catalogue must be examined in terms of the following aspects:<br />

- Existence of the function by calling up in the program and evaluation of the<br />

items of program documentation.<br />

- Freedom from error or correctness of the function<br />

In order to guarantee the freedom from error or correctness of the function,<br />

depending on the test level various test procedures should be used during<br />

the check such as black box tests, white box tests or simulated production<br />

running.<br />

<strong>The</strong> test data and test cases created in the initial phase are used in the<br />

functionality test. During the functionality test it is necessary to compare<br />

the test results with the specified requirements. In addition, a check should<br />

be made on how the program reacts in the case of faulty input parameters<br />

or faulty operation. <strong>The</strong> function must also be tested with the limit values<br />

of the intervals of input parameters and with exceptional cases. <strong>The</strong>se must<br />

be detected accordingly and correctly handled.<br />

- Suitability of the function<br />

<strong>The</strong> suitability of the function is distinguished by the fact that the function<br />

- actually fulfils the task to the required extent and in an efficient<br />

manner and<br />

- can be integrated easily into normal work processes.<br />

If the suitability of the function is not obvious, the solution is to test this in<br />

a simulated production operation, but still in the test environment.<br />

- Consistency<br />

<strong>The</strong> consistency of the separate functions must be checked, in each case<br />

between the Requirements Catalogue, the documentation and the program.<br />

Any contradictions must be documented. Discrepancies between the<br />

documentation and the program must be recorded in such a way that they<br />

can be incorporated into the additions to the documentation when the<br />

product is used later.<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!