The process cycle test is a technique that is applied in particular to the testing of the quality characteristic of suitability (integration between the administrative organisation and the automated information system). The test basis should contain structured information on the required system behaviour in the form of paths and decision points. The test basis for the process cycle test consists mainly of descriptions of procedures and related forms. Preferably, flow charts should be added to the procedure descriptions. The following checklist can be used to check the procedure descriptions present:
• Have all manual procedures to be executed by users been described?
• Has the responsibility as well as authority for each manual task been described?
• Has a description been made of the individual tasks?
• Have the security aspects of this procedure been described?
• Is the “triggering event” clearly indicated? (In other words, when should the procedure be started?)
• Has it been indicated which data (forms) are to be used and what their source is?
• Have the activities to be carried out been described, including exceptions and checks?
• Is the result of every procedure clear?
• Have the various decision points been described, including any related conditions?
• Has a distinction been made between end user procedures and system user procedures?
• Have the relationships between the automated and the non-automated part of the information system been described?
• Is the (draft) user manual available?
• Have all manual procedures to be executed by users been described?
• Has the responsibility as well as authority for each manual task been described?
• Has a description been made of the individual tasks?
• Have the security aspects of this procedure been described?
• Is the “triggering event” clearly indicated? (In other words, when should the procedure be started?)
• Has it been indicated which data (forms) are to be used and what their source is?
• Have the activities to be carried out been described, including exceptions and checks?
• Is the result of every procedure clear?
• Have the various decision points been described, including any related conditions?
• Has a distinction been made between end user procedures and system user procedures?
• Have the relationships between the automated and the non-automated part of the information system been described?
• Is the (draft) user manual available?
Thanks
0 comments:
Post a Comment