Waterfall is a perfectly valid method of developing software I woudl hope that a degree program woudl cover a number of models of software development.
Back in the day I got a recognition award for two projects in a row first was a classic waterfall project (a management system for the Uk's SMDS network) the next was full on RAD/DSDM (early web development).
Can you elaborate what you mean by waterfall? Did you have a prototype? I am confused because to my knowledge it has only ever been described as a way not to do things.
"The first formal description of the waterfall model is often cited as a 1970 article by Winston W. Royce,[4][5] although Royce did not use the term "waterfall" in this article. Royce presented this model as an example of a flawed, non-working model."
Actually it was BT's own ISO 9000 based system we spent about 7/8 months on the design/spec stage then 2 of us plus an oracle contractor did the development in a 12 week sprint - so it was a sort of hybrid approach.
SMDS/ATM was fairly new at the time our system was designed to manage the kit in the exchanges so that you didn't have some one accidentally shutdown the entire janet university network.
Back in the day I got a recognition award for two projects in a row first was a classic waterfall project (a management system for the Uk's SMDS network) the next was full on RAD/DSDM (early web development).