The test basis for the syntactic test consists of the syntactic rules, which specify how an attribute should comply in order to be accepted as valid input/output by the system. These rules actually describe the value domain for the relevant attribute. If a value outside this domain is offered for the attribute, the system should discontinue the processing in a controlled manner – usually with an error message. Syntactic rules may be established in various documents, but they are normally described in: the ‘data dictionary’ and other data models, in which the characteristics of all the data are described and in the functional specifications of the relevant function or input screen, containing the specific requirements in respect of the attributes. The following checklist can be used:
• Have any applicable standards been described at system level?
• Have any applicable standards been described at subsystem level?
• Have the layouts of the screens, menus and dialogs been described?
In this context, has any attention been given to the following aspects:
o field length of the items;
o location of items on the screen;
o distinction between input and output items;
o primary input checks (not resulting from domain definition);
o error handling;
o mandatory and non-mandatory items;
o possible function keys, help screens and selections?
• Have the “screen items” and/or attributes been included in the data model?
• Have the types (numeric, alphanumeric, date) and the domains of the input and output data been described?
• Are the specified mandatory and non-mandatory items consistent with the options from the data model?
• Do the described screen layouts comply with the standards?
• Have the layouts of the reports been described?
In this context, has any attention been given to the following aspects:
o field length of the items;
o location of items in the report?
• Have the “report items” and/or attributes been included in the data model?
• Do the described report layouts comply with the standards?
• Have any applicable standards been described at system level?
• Have any applicable standards been described at subsystem level?
• Have the layouts of the screens, menus and dialogs been described?
In this context, has any attention been given to the following aspects:
o field length of the items;
o location of items on the screen;
o distinction between input and output items;
o primary input checks (not resulting from domain definition);
o error handling;
o mandatory and non-mandatory items;
o possible function keys, help screens and selections?
• Have the “screen items” and/or attributes been included in the data model?
• Have the types (numeric, alphanumeric, date) and the domains of the input and output data been described?
• Are the specified mandatory and non-mandatory items consistent with the options from the data model?
• Do the described screen layouts comply with the standards?
• Have the layouts of the reports been described?
In this context, has any attention been given to the following aspects:
o field length of the items;
o location of items in the report?
• Have the “report items” and/or attributes been included in the data model?
• Do the described report layouts comply with the standards?
Thanks
0 comments:
Post a Comment