Software Development
How software is built in practice: life cycles, testing strategies and maintenance.
- Click the stages below in the order they happen.
//Testing strategies, separated clearly
White box tests the internal logic — you design tests to cover every path. Black box tests only inputs and outputs — you ignore how it works inside. Alpha testing is done in-house; beta testing is done by real users outside the company; acceptance testing is the customer deciding whether to accept the delivered system.
//Three kinds of maintenance
Corrective: fixing bugs found after release. Adaptive: changing the software because the environment changed — new hardware, new law, new OS. Perfective: improving performance or adding features that users asked for.
//Waterfall vs iterative
Waterfall goes through the stages once, in order — simple to manage, but a mistake found late is expensive and the customer sees nothing until the end. Iterative builds a working version, gets feedback and repeats — changes are cheaper and the customer is involved throughout, but it is harder to plan and cost.
CHECK YOURSELF
1.Testing that ignores the internal code and checks only inputs against outputs is:
2.The software is changed because a new law requires it. Which maintenance is this?
3.What is the main weakness of the waterfall model?