test software use case
DESCRIPTION
Use case driven test softwareTRANSCRIPT
![Page 1: Test software use case](https://reader036.vdocuments.site/reader036/viewer/2022082410/5492dc2db47959514d8b46d8/html5/thumbnails/1.jpg)
![Page 2: Test software use case](https://reader036.vdocuments.site/reader036/viewer/2022082410/5492dc2db47959514d8b46d8/html5/thumbnails/2.jpg)
![Page 3: Test software use case](https://reader036.vdocuments.site/reader036/viewer/2022082410/5492dc2db47959514d8b46d8/html5/thumbnails/3.jpg)
![Page 4: Test software use case](https://reader036.vdocuments.site/reader036/viewer/2022082410/5492dc2db47959514d8b46d8/html5/thumbnails/4.jpg)
• By performing test analysis, testers can identify all quality concerns they need to
address is system testing
![Page 5: Test software use case](https://reader036.vdocuments.site/reader036/viewer/2022082410/5492dc2db47959514d8b46d8/html5/thumbnails/5.jpg)
The purposes of test analysis
• Is to develop ideas about what in general can go wrong with this kind of system.
Crosscutting Quality Concerns (CQC)- Correspond to supplemental requirements, for example, GUI, concurrency requirements that are scattered across the application and crosscut multiple use cases
![Page 6: Test software use case](https://reader036.vdocuments.site/reader036/viewer/2022082410/5492dc2db47959514d8b46d8/html5/thumbnails/6.jpg)
Documenting the Test Analysis Results
“Standard for Test Documentation” IEEE Std. 829– Test Plan Document– Test Design Specification– Test Case Specification– Test Procedure Specification
![Page 7: Test software use case](https://reader036.vdocuments.site/reader036/viewer/2022082410/5492dc2db47959514d8b46d8/html5/thumbnails/7.jpg)
Example of a Test Analysis Specification Template
• Title page• Use Case Short Description• Use Case Relationships• Realization of Crosscutting Quality Concerns• Use Case Decomposition into Vertical Slices• Quality Risks not to be Tested• Test Analysis Matrix
![Page 8: Test software use case](https://reader036.vdocuments.site/reader036/viewer/2022082410/5492dc2db47959514d8b46d8/html5/thumbnails/8.jpg)
Benefits of the Test Analysis Specification
• Help us perform test effort estimation• Provides a road-map for detailed test design• Help us perform impact analysis when
requirements have changed
![Page 9: Test software use case](https://reader036.vdocuments.site/reader036/viewer/2022082410/5492dc2db47959514d8b46d8/html5/thumbnails/9.jpg)
Dealing with the Iterative Evolution of the Use-Case Model
• The use-case model can frequently change in the course of a project for the following common reasons:– New use cases can be incrementally added to the
existing use-case model in a new project iteration– Mode details can be added to the existing scenarios– Developers can periodically refactor the use-case
model to make its structure easier to understand and maintain
![Page 10: Test software use case](https://reader036.vdocuments.site/reader036/viewer/2022082410/5492dc2db47959514d8b46d8/html5/thumbnails/10.jpg)
Tips and Guidelines
• Test Planning.- follow the use-case-driven concept, and provide an estimation per use case.
• Test Design.- focus on producing high-level test analysis and test design specifications, as opposed to low-level test case specifications.
• Implementing Version Control.- periodically create project baselines that incluSde artifacts of the use-case model and the corresponding test models.