Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
32 views4 pages

Developing & Testing: Davin, Darren, William, Juan

The document outlines the process of developing and testing a system. It describes finalizing the system design, testing the data storage and links, and validating data transfers. User interfaces are created and the system undergoes rigorous testing to ensure correct functioning and identify improvements before retesting. Testing strategies include using normal, extreme, and abnormal data values to check for expected and unexpected outcomes.

Uploaded by

Jeremy Evans
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
32 views4 pages

Developing & Testing: Davin, Darren, William, Juan

The document outlines the process of developing and testing a system. It describes finalizing the system design, testing the data storage and links, and validating data transfers. User interfaces are created and the system undergoes rigorous testing to ensure correct functioning and identify improvements before retesting. Testing strategies include using normal, extreme, and abnormal data values to check for expected and unexpected outcomes.

Uploaded by

Jeremy Evans
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Developing & Testing

Davin, Darren, William, Juan


Process
• Finalizes of the system
• Checks what type of data is being stored in each field, length of each
field, which field will be the key field, how the data files will be linked,
etc.
• System is fully tested for correct data, robustness, etc.
• Validation routine and verification methods are done regularly to
make sure accurate paper-to-electronic data transfer
• User interface is made
Testing Strategies
• The system is tested to ensure it functions correctly and it may lead to
improvements and it is fully tested again
• This is a very time-consuming process
Example
• Date. Must be in the form dd/mm/yyyy
• Normal: this is data which is acceptable/valid and has an expected (known) outcome, e.g.
the month can be any whole number in the range 1 to 12.
• Extreme: this is data at the limits of acceptability/validity, e.g. the month can be either of
the two end values i.e. 1 or 12.
• Abnormal: this is data outside the limits of acceptability/validity and should be rejected or
cause an error message. For example, all the following values are not allowed as inputs for
the month:
• negative numbers (e.g. –1, –15)
• any value greater than 12 (e.g. 32, 45)
• letters or other non-numeric data (e.g. July)
• non-integer values (e.g. 3.5, 10.75).

You might also like