Reasoning about Flaws in Software Design: Diagnosis and Recovery
Tamara Lopez, Thursday 3rd June, 12:30 pm - 12:45 pm, Student Presentations 2, JLB Meeting Room 1
Cloud created by:
28 May 2010
Full-time PhD student who started in February. Interestingly, she is reading a speech. She is going to talk about flaws in software design. She is going to talk about: how failure is talked about in literature
She mentions three eras: 1969, 1996 and 2005.
The current analytical perspective:
- Systemic analyses (What went wrong?) – analyses what went wrong – the catastrophic problem
- Means-oriented analysis – as they contribute to hinder the development of software (?) – is used to measure quality of the software
In order to convince people that the software is good is completely intertwine with the software design itself.
Her questions are about what constitutes a flaw what condition surrounds its occurrence and correction. Also trying to explain the phenomena of failure. She’ll be using a human-centred interaction approach.
You seem to be persisting on failure – why persist on this if it seems to be mostly quality? I may not persist in it but in talking about smaller errors you’ll need to connect up with failures (?) – this would be an ongoing exploration.
You mention bits of software that get discarded – this is usually because 1) the customer when he gets it realise the requirements are not met or 2) it just was not made well. Do you intend to look at both aspects or whether in failures in terms of software does not work or because the requirements are wrong in the first place. Probably both - my intention is to go look at see what happens.
The current way that software is developed it seems cheaper to develop the software and mend it on the fly – my question is where do you think the failures are most likely to occur? I think it has to be when we define what is design and where exactly it is happening.
11:06 on 3 June 2010