Complete thesis - Murdoch University

assembled into a model bit by bit. So I see stories asend-to-end interaction sequences; you work both up and down fromthem. I note that I and the other people who’ve replied to yourquestion have written mostly about ‘user requirements’.Specifications are more likely to work in a relatively top-downway simply because it’s safer to do so once the user reqts arereasonably well-known. However I concur with Suzanne Robertson’sview that you have to work ‘top-down, bottom-up, andmiddle-every-which-way’Ian Alexander (UK)27 April 2004 There are at least two very good reasons whysome form of top-down approach is normally seen in successful projects, regardless ofhow the actual process happened in practice.What I was suggesting tends to be something like: workingupwards from middle/bottom fragments (including scenarios), thenworking top-down, then validating (partial) against thefragments.Andrew Gabb (Australia)28 April 2004 It occurs to me that most tools intentionally support top-down,but unintentionally support bottom-up as well, sincemost analysts operate opportunistically.Scott Overmyer (New Zealand)28 April 2004 This reminds me of David Parnas and Paul Clements’s classicpaper ‘A Rational Design Process: How and Why to Fake It’.Although I suspect this wasn’t the intent.Even if the information is gathered bottom-up, it is better presented top-down as thatis the easiest way for us to navigate around.Keith Collyer (USA)56