Testing & implementation system 2-wm
Download as PPTX, PDF0 likes46 views
The document discusses different types of testing conducted throughout the software development life cycle. It describes software development models, the V-model, and different testing levels including component testing, integration testing, system testing, and acceptance testing. Component testing checks individual software components, integration testing tests interfaces between components, system testing evaluates the full system against requirements, and acceptance testing validates user needs are met.
Testing & implementation system 2-wm
- 1. WIWIK MUSLEHATIN 11453201902 CHAPTER 2 Testing Throughout The Software Life Cycle Departement of Information System Faculty of Science and Technology UIN SUSKA RIAU 2017
- 2. AGENDA : Software Development Models V- Model Component testing System testing
- 3. Software Development Models In every development life cycle, a part of testing is focused on verification testing and a part is focused on validation testing. Verification is concerned with evaluating a work product, component or system to determine whether it meets the requirements set. Validation is concerned with evaluating a work product, component or system to determine whether it meets the user needs and requirements.
- 4. V-Model Although variants of the V-model exist, a common type of V-model uses four test levels. The four test levels used, each with their own objectives, are: component testing: searches for defects in and verifies the functioning of software components (e.g. modules, programs, objects, classes etc.) that are separately testable; integration testing: tests interfaces between components, interactions to different parts of a system such as an operating system, file system and hard ware or interfaces between systems; system testing: concerned with the behavior of the whole system/product as defined by the scope of a development project or product. The main focus of system testing is verification against specified requirements; acceptance testing: validation testing with respect to user needs, require ments, and business processes conducted to determine whether or not to accept the system.
- 5. V-Model Graham, et al. 2011
- 6. Component testing Definition : Component testing, also known as unit, module and program testing, searches for defects in, and verifies the functioning of software (e.g. modules, programs, objects, classes, etc.) that are separately testable.
- 7. Integration Testing Definition : Integration testing tests interfaces between components, interactions to different parts of a system such as an operating system, file system and hardware or interfaces between systems. Note that integration testing should be differentiated from other integration activities. Integration testing is often carried out by the integrator, but preferably by a specific integration tester or test team.
- 8. Integration Testing There may be more than one level of integration testing and it may be carried out on test objects of varying size. For example: component integration testing tests the interactions between software com ponents and is done after component testing; system integration testing tests the interactions between different systems and may be done after system testing. In this case, the developing organiza tion may control only one side of the interface, so changes may be destabilizing. Business processes implemented as workflows may involve a series of systems that can even run on different platforms.
- 9. System Testing Definition : System testing is concerned with the behavior of the whole system/product as defined by the scope of a development project or product. System testing should investigate both functional and non-functional requirements of the system. Typical non-functional tests include performance and reliability.
- 10. Acceptance Testing The goal of acceptance testing is to establish confidence in the system, part of the system or specific non-functional characteristics, e.g. usability, of the system. Acceptance testing is most often focused on a validation type of testing, whereby we are trying to determine whether the system is fit for purpose. Finding defects should not be the main focus in acceptance testing. Although it assesses the system's readiness for deployment and use, it is not necessarily the final level of testing.
- 11. The user acceptance test is performed by the users and application managers. The operational acceptance test may include testing of backup/restore, disaster recovery, maintenance tasks and periodic check of security vulnerabilities. Acceptance Testing
- 12. Referensi : Graham, Dorothy, et al. “Foundation of software Testing ISTBQ Sertification”. Chapter 1 Fundamentals of Testing. 2011