V-Model
- ูู ุนุจุงุฑุฉ ุนู sequential model
- ูู ุจุชุญุงูู ุชุญู ุงูู ุดุงูู ุงููู ุดูููุงูุง ูู ุงู Waterfall Model ูู ุดููุฉ ู ู ุงูู ุดุงูู ู ุซููุง ูุงูุช ุงูู testing ุจูุชุฃุฎุฑ ูู ุงู lifecycle
Requirements
ุงุชูุณู ุช ูููุนูู ู ู ูู ูุณู ููู Business and technical
- BRD โ Business requirements document
- SRS โ Software requirements specification
BRD
- high-level requirements talks about what are we developing?
- Example: I need to develop an application that enables the user to sign up, order food, gives reviews, pay
- Caring about What part
- Caring about the client himself or the end customer, What will we deliver to him?
- Done by the business analyst
SRS
- Caring about the How part, How will we develop this functionality?
- Caring about the development team
- Done by the system analyst or the business analyst
Design
ุงุชูุณู ุฌุฒุฆูู Architecture and Detailed
Architectural
ุจุชูููู ุนู ุงูุตูุฑุฉ ุงูุนุงู ุฉ ููู ุดุฑูุน ูุงูู ู ุซููุง ูู ุง ุชุนู ู sign in ุงูู ุงููู ูุธูุฑูู ููุฏุง
Detailed
The detailed design is talking about each component or module on its own
Testing
- We have 4 levels of testing to solve waterfall disadvantages.
- Unit testing, Integration Testing, System Testing, Acceptance Testing
We will explain it in more details at Test levels (Draw)
Unit Testing
- You test each component or unit individually
- Anything that can be tested separately should be tested on its own
- Itโs the responsibility of the developer
Integration Testing
- You test the integration between different components or units
- Itโs the responsibility of the developer
System Testing
- You begin on testing the whole system
- Most of the software tester tasks are in system testing
Acceptance Testing
- Itโs the last step of testing that ensures that the application is ready for deployment or for usage by the end user
- Itโs the responsibility of the client or the product owner or the business analyst
What is the job for tester?
- ูู
ุง ุจุชุจุฏุฃ ุชูุชุจ ุงููrequirements ูู ุงูุฃูู ุฎุงูุต ุงููtester ุจูุจุฏุฃ ูุฑุงุฌุน ุงููrequirements ุฏู
- ููุชุฃูุฏ ุงู ู ููุด ambiguity , contradiction ุชูุงูุถ ูุฏุง ุจูุณู ูู static testing
- ูุจูุจุฏุฃ ูุนู ู ู ู ุฎูุงููุง ุงู Test Scenario or Test Case ูููุณุชุฎุฏู ูุง ูู ุง ุงูุจุฑูุงู ุฌ ูุจูุง ุฌุงูุฒ ูู ุฑุญูุฉ ุงู acceptance testing
- ุนูุฏูุง ููุนูู ู ู ุงู testing ุงููู ูู ุง ุงู static and dynamic
- ูุจุนุฏูุง ุจุฑุถู ุจุชุนู ู review ูู SRS ูู ุง ุจูุชูุชุจ ูุชุนู ู ุจุฑุถู Test Scenarios or test cases ูุฏู ุงููู ููุณุชุฎุฏู ูุง ูู ุงู system testing
- ูุจุชูู ู ุนูู ูุฏุง ุงูู ุจุชุดูู ุงูู ุฑุญูุฉ ุงููู ุงูุช ูููุง ูุชุฑุงุฌุน ุงูุดุบู ุงููู ุงุชุนู ู ูุชุนู ู test scenarios and test cases
- ูู ุงู SW testing ุนูุฏูุง ุญุงุฌุฉ ุงุณู ูุง analysis and design ูุญุงุฌุฉ ุงุณู ูุง execution ุจุงููุณุจุฉ ูู testing
- ุงููู ุนูู ุดู ุงู ุงู V ูู ุฏุง analysis and desing ุงู ุงูุญุงุฌุฉ ุจุชุชุนู ู ูุจุชุฌูุจ ุฃููุงุฑ ูุงูุญุงุฌุงุช ุงููู ููุชุนู ููุง testing ูุจูููู ุนูููุง Verification Verification is the process of checking that software achieves its goal without any bugs. Verification is simply known asย Static Testing.
- ุงููู ุนุงููู ูู ูู execution ุงูู ุจุฏู input ูุจูุทูุนูู output ูุฎุฏ ุจุงูู ุฏู ุจุชุชุนู ู ู ู ุชุญุช ูููู ุงูู ุง ุงูุชุงููุฉ ู ู ููู ูุชุญุช ุจุงูุชุฑุชูุจ ูุจูููู ุนูููุง Validation It is a validation of actual and expected products. Validation is simply known asย Dynamic Testing.
Disadvantage
- ุงูู ุนุจุงุฑุฉ ุนู sequential model ูุงูุนู ูู ุงู ุงู end user ููุฏุฑ ูุดูู ุงูุจุฑูุงู ุฌ ู ุฑุฉ ูุงุญุฏุฉ ูู ู ูู ูุจูุง ุงูููุช ุฏุง ู ุชุฃุฎุฑ ุงููุง ูุนู ู ุฃู ุชุนุฏูู ููู ุงูุนู ูู ุทูุจ ุชุนุฏูู ุจูุจุฏุฃ ุชุงูู ู ู ุงูู ุฑุญูุฉ ุงููู ุจุงุธุช ูููุง