Please enable JavaScript.
Coggle requires JavaScript to display documents.
5.2 Understand testing in a project - Coggle Diagram
5.2 Understand testing in a project
5.2.1 Explain the importance of software quality assurance.
Introduction
: The system design specification serves as a blueprint for constructing the new system. The initial task is application development
Software Engineering
: Capability Maturity Model (CMM) , Capability Maturity Model Integration (CMMI) , Process improvement ,CMMI tracks an organization's processes, using five maturity layers .
International Organization for Standardization (ISO)
: Many firms seek assurance that software systems will meet rigid quality standards. Example (ISO 90003:2004 , ISO requires a specific development plan)
5.2.2 Differentiate the types of software testing
Three types of software testing
Unit Testing
: Unit testing involves individually testing unit of code separately to make sure that it works on its own, independent of the other units. Eg: Testing a function; whether loop or statement in a program is working properly or not than this is called as unit testing.
Integration Testing
: Test the modules to ensure whether they are integrating properly or not by combining the modules and tested as a group. Eg: Tester have to test the keyboard of a computer than it is a unit testing but when tester have to combine the keyboard and mouse of a computer together to see its working or not than it is the integration testing. It is prerequisite that for performing integration testing a system must be unit tested before.
System Testing
: Tester test the complete system as a whole to check whether the system is properly working or vice versa as per the requirements or not. Testers always have to concentrate on both functional and non-functional testing like performance, load, stress, security and recovery testing. In summary: in system testing the testers test the complete system as a whole. Example: Test the whole functionality and non functionality of the system interactions between all module in Laundry Management System as one single system. It is prerequisite that for performing system testing a system must be unit tested and integration tested before.
5.2.3 Differentiate between program, system, operations, and user documentation.
Program documentation
describes the inputs, outputs, and processing logic for all program modules.
System documentation
describes the system’s functions and how they are implemented. System documentation includes data dictionary entries, data flow diagrams, object models, screen layouts, source documents, and the systems request that initiated the project.
Operations documentation
contains all the information needed for processing and distributing online and printed output.Operations documentation should be clear, concise, and available online if possible.
User documentation
consists of instructions and information to users who will interact with the system and includes user manuals, Help screens, and tutorials.
Effective online documentation is an important productivity tool. Written documentation material also is valuable
