Please enable JavaScript.
Coggle requires JavaScript to display documents.
TOPIC 5.2 TESTING IN A PROJECT - Coggle Diagram
TOPIC 5.2 TESTING IN A PROJECT
Software Quality Assurance
A software testing and quality assurance company specifications and give you a report detailing out the findings.
Getting a software quality assurance test done before making your website live will help you in plugging in all the loopholes that could cause losses to your bussiness.
3 Types Of Software Testing
1. Unit testing
2. Integration testing
3. System testing
All processing options and outputs are verified by users and IT project development team to ensure that the system functions correctly
6 how the system was developed,system testing has the following major objectives:
Demonstrate that users can interact with the
system successfully
Verify that the system will handle all input data
properly, both valid and invalid
Perform a final test of all programs
Ensure that the IT staff has the documentation and instructions needed to operate the system properly and that backup and restart capabilities of the system are adequate.
Verify that all system components are integrated properly and that actual processing situations will be handled correctly.
Confirm that the information system can handle predicted volumes of data in a timely and efficient manner.
Testing two or more programs that depend on each other is called integration testing ,or link testing.
A testing sequence should not move to the integration test stage unless it has performed properly in all unit tests
The testing of an individual program or module is
called unit testing.
During testing, programmers can use software tools to determine the location and potential causes of program errors.
Documentation
describes an information system and helps the users,managers and IT staff who must interact with it.
4 Documentation includes:
1. program documentation
2. system documentation
3. operations documentation
4. user documentation
User documentation consists of instructions and information to users who will interact with the system and includes user manuals,help screens and tutorials.
10 User documentation
A system overview that clearly describes all major
system features, capabilities, and limitations
Description of source document content,
preparation, processing, and samples
1 more item...
Operations documentation contains all the information needed for processing and distributing online and printed output.
7 Typical operations documentation:
Program, systems analyst, programmer, and
system identification
– Scheduling information for printed output, such
as report run frequency and deadlines
1 more item...
System documentation describes the system’s
functions and how they are implemented.
7 System documentation includes
screen layouts
source documents
object models
data flow diagrams
the systems
request that initiated the project.
data dictionary entries
Program documentation describes the inputs,outputs ,and processing logic for all program modules.