Please enable JavaScript.
Coggle requires JavaScript to display documents.
APPLICATION CONTROLS, Minimum Keying of Info, Screen Prompts &…
APPLICATION CONTROLS
Input
- Username & Password only allow a limited no. of alphanumeric characters
- Screen Dialogue & Prompts to Communicate with the user
- Date Input format: YYYY/MM/DD
- Contain Mandatory fields where keying of information will not continue unless filled.
- E-mail address: .co.za (Invalid emails should be identified)
- Indicate mandatory fields with asterix - Field presence check (Name, surname, e-mail, cellphone no, etc)
- ID no: Year, Month, Day -> Screen format should be able to pick up invalid ID no's
- Provide an example(s) on which fields should be mandatory
- Screen should be FORMATTED to receive essential data and information in the format/order in which it is required.
- SHADING of certain fields
-
-
-
-
- To check validity of information keyed in by user via OTP Pins
- Minimum Keying of information
-
-
- performed by the application to match certain data to that which is already in the database
- E.g. Username & Password matched to the one in the database, profile in masterfile
- DATA APPROVAL / AUTHORISATION Checks
- be performed by the application to test the input against certain pre-set conditions
- Example: Age.. Remember Sinethemba could not be admitted to UJ because of her age
-
- to ensure that the data entered falls within a certain range and reasonable limit
-
-
-
- Field-size check --> ID no 13 digits
-
- Sign Check --> e.g., +ve Sales
-
PROCESSING
-
-
-
-
-
-
-
-
-
-
-
-
If processing happens at a particular time, limit/block transactions till processing is done.
-
-
-
-
-
Exception reports - Mention on what should exception reports be generated. e.g On control totals that do not balance
-
-
-
-
-
PASSWORD CONTROLS
-
-
-
-
-
-
-
-
-
-
-
-
Upper, Lowercase, alphanumeric
-
-
-
Minimum Keying of Info
Automatic retrieval of standing data e.g names, surnames etc
-
-
-
-
-
-
-
-
-
-
-
-
-