@www.csse.monash.edu.au |
| Assessment | Contacts | Lectures | Resources | Timetables | Tutorials | Unit Outline |
| Last modified: 20080723:165134/initial version for 2008 | FIT3013 AJH-2009-24 |
Posting Your Response | The Issue | Related Issues
Go to the Moodle Forum Page to enter your postings
In thinking about the "inexorable" formality required in order to be completely confident about the correctness of an abstract specification, discuss whether Set Theory is the most appropriate way to go.
You may want to bring any or all of these topics into your discussion - they are not mandatory, but are here to prompt some of your thinking. Feel free to explore other (related) topics.
What do we mean by correctness of a specification? Can you ever be completely confident that your client has captured all the relevant issues?
Does formality have to be inexorable? What happens if it is not? Those of you who think of themselves as computer scientists, what does science have to say about formality? Those of you who lean towards roles as software engineers, what does engineering have to say about inexorability?
Justify the use of the word "abstract" in the statement of the issue. Are there scenarios in which "concrete" specifications are better?
Set Theory? Is there any other way? Discuss a possible alternative.
| 20080723:165134 | 7.0.0 | ajh | initial version for 2008 |
| This page maintained by John Hurst. Copyright Monash University Copyright Policy |
| ||
Generated at 20090706:1537 from an XML file modified on 20090515:0936 | |||