Software development is usually done incrementally. With multiple iterations, there is a release after an iteration, each adding new features (and defects too!) to the product. Say, if there are two features, F1 and F2, where in F2 depends on F1. In such a scenario, given the progressive development, the features are ordered such that F2 is planned in the release after F1. Or, if you have the luxury of sufficient testing cycles, both are clubbed in the same release.

If software developers are to build an airplane, more likely they would resort to the same life cycle. Having said that, lets say, F1 corresponds to 'TakeOff' and F2 being 'Landing', By same logic, F2 occurs in a later iteration than F1 - for the airplane cannot land without taking off. Poor Tester! (whoever is assigned to test F1; it has 'Take Off' feature, but no 'Landing' feature).