Scribd
Upload
3 views7 pages

System Development and TestingSummary

The document outlines the stages of system development, testing, and implementation in software projects, detailing the methodologies, inputs, outputs, and tools used. It describes various types of system tests, such as unit, integration, and system testing, and emphasizes the importance of testing to ensure user requirements are met and bugs are fixed. Finally, it discusses system deployment strategies and the need for user training post-implementation.

Uploaded by

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

System Development and TestingSummary

The document outlines the stages of system development, testing, and implementation in software projects, detailing the methodologies, inputs, outputs, and tools used. It describes various types of system tests, such as unit, integration, and system testing, and emphasizes the importance of testing to ensure user requirements are met and bugs are fixed. Finally, it discusses system deployment strategies and the need for user training post-implementation.

Uploaded by

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

Summary:

System Development and Testing


This topic explains the stages involved in developing, testing, and implementing a
system/application in research or software projects.

1. System Development
System development explains:
• How the system/application was created
• Software and tools used
• Interfaces used
• Development methodology used (e.g., prototyping)
It should also describe:
• Inputs
• Processing
• Outputs
• System boundaries
Reports should include:
• Screenshots/print screens of the system
• A user guide explaining how each screen/page is used
2. System Testing
Before a system is used, it must be tested to:
• Ensure it meets user requirements
• Confirm it solves the identified problem
• Detect and fix bugs/errors in the software
3. Types of System Tests
a) Unit Testing
• Tests individual modules/components
• Example: testing a single webpage or form
b) Integration Testing
• Tests whether different modules work together properly
c) System Testing
• Tests the complete system
• Checks whether business/user requirements are met
d) Volume Testing
• Tests whether the system can handle large amounts of data
e) Other Tests
• Validation testing
• Stress testing
• Alpha testing
• Beta testing (acceptance testing)
4. Results of System Testing
Only tests actually performed should be included in reports.
The report should show:
• Tests conducted
• Results obtained
• Bugs/errors identified
• Corrections made to fix the bugs

5. System Implementation / Deployment


After successful testing, the system is deployed.
Important Points
• State the conversion strategy used
• Give reasons why that strategy was selected
Possible implementation approaches:
• Direct conversion
• Parallel conversion
• Pilot conversion
• Phased conversion
User Training
If training was conducted, explain:
• How users were trained
• Results of the training
Sometimes implementation is not done due to time limits and may be written as a recommendation
in the report.

Quick Exam Notes


Important Definitions
Know:
• System Development
• System Testing
• Unit Testing
• Integration Testing
• System Implementation
Common Exam Questions
1. Explain types of testing.
Mention:
• Unit
• Integration
• System
• Volume
• Stress
• Alpha/Beta testing
2. Why is system testing important?
• Detects bugs
• Ensures system meets requirements
• Confirms system effectiveness
3. What should be included in system development?
• Methodology used
• Inputs/processes/outputs
• Screenshots
• User guide
4. Explain system implementation.
• Deployment of the system
• Conversion strategy
• User training
Easy Memory Trick for Testing Types
“UISV”
• U → Unit Testing
• I → Integration Testing
• S → System Testing
• V → Volume Testing
Remember:
“Use Integrated Systems Very carefully.”

You might also like