Scribd
Upload
43 views10 pages

7.3 Development and Testing

The document outlines the importance of testing in system development, detailing the processes involved in validating data structures, file structures, input methods, output formats, and validation routines. It emphasizes modular software development, where individual modules are tested separately before system-wide testing to identify and resolve issues. Additionally, it describes the creation of a test plan that includes various data types for testing, such as normal, abnormal, and extreme data, as well as the necessity of live data testing to ensure system accuracy against known outcomes.

Uploaded by

nguntinpar.noami
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
43 views10 pages

7.3 Development and Testing

The document outlines the importance of testing in system development, detailing the processes involved in validating data structures, file structures, input methods, output formats, and validation routines. It emphasizes modular software development, where individual modules are tested separately before system-wide testing to identify and resolve issues. Additionally, it describes the creation of a test plan that includes various data types for testing, such as normal, abnormal, and extreme data, as well as the necessity of live data testing to ensure system accuracy against known outcomes.

Uploaded by

nguntinpar.noami
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/ 10

0

3
Development and Testing
Testing
The need for Testing
• System creation and testing begins after
design is completed
• File structure:
• Finalize database structure (data types, field
length, key fields, links)
• Test thoroughly to ensure it's robust when live
• Data validation and verification:
• Ensure correct data types and rules are followed
• Test validation and verification routines to catch
errors and ensure accurate transfer from paper to
electronic systems
• User interface:
• Identify how screens and input devices collect
data and present output
• If specialist hardware is needed (e.g., for
disabilities), finalize usage and test thoroughly for
user-friendliness
Testing Design
• Test designs ensure all system aspects are
tested:
• Testing the Data structures
• Testing the File structures
• Testing the Input methods
• Testing the Output formats
• Testing the Validation rules
Testing Designs

Ensure data is stored in the correct format


Data Structures (e.g., tables holding data correctly)

File Structures Test that files store and retrieve data properly

Validate that all input formats (e.g., date entries) are


Input Formats correctly entered

Ensure screen outputs and reports match input data and


Output Formats are clear

Test to confirm that validation routines (e.g., rejecting


Validation Routines incorrect data) work as expected
Testing Strategies
• Modular software development:
• Software is broken into smaller parts (modules)
developed by individual programmers or teams
• Module testing:
• Each module is tested separately for functionality
• If issues arise, modules are modified and retested
• System testing:
• After individual module testing, the entire system is
tested with all modules combined
• Possible issues: data clashes, incompatibility,
memory problems
• Improvements and retesting:
• Input/output methods, file/database structures,
validation, and verification may need adjustments
• Full testing is repeated to ensure everything is
correct before using live data
• Time-consuming but essential for system success
Module Testing
Test plan, test data and live data
• Test Plan: Created after determining test designs
and strategy for each module
• Includes:
• List of tests to be performed
• Data to be used for testing
• Type of test data (normal, abnormal, or extreme)
• Live data to be used
• Expected outcomes from the tests
• Compare actual outcomes with expected results
• Test Data Types:
• Normal data: Regular, expected input
• Abnormal data: Incorrect or invalid input
• Extreme data: Data at the boundaries of what
the system should handle
Test plan, test data and live data

• Normal data:
• Valid data with expected outcomes (e.g., month is
a whole number between 1 and 12)
• Extreme data:
• Data at the limits of validity (e.g., month values 1
or 12)
• Abnormal data:
• Invalid data that should be rejected or cause an
error, including:
• Values less than 1 (e.g., 0, -1)
• Values greater than 12 (e.g., 32, 45)
• Non-numeric data (e.g., "July")
• Non-integer values (e.g., 3.5)
Test plan, test data and live data
• Live data testing:
• Use real data with known outcomes to test the system
• Compare new system results with those from the old system
• If outcomes differ, modifications may be needed

You might also like