Discussion Topic 1

The Issue | Related Issues

The Issue

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.

Related Issues

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.

Correctness

What do we mean by correctness of a specification? Can you ever be completely confident that your client has captured all the relevant issues?

Inexorable Formality

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?

Abstraction

Justify the use of the word "abstract" in the statement of the issue. Are there scenarios in which "concrete" specifications are better?

Set Theory

Set Theory? Is there any other way? Discuss a possible alternative.

Document History

This page maintained by John Hurst. Copyright Monash University Copyright Policy	385 accesses since 24 Jul 2008
Generated at 20090705:2039 from an XML file modified on 20080924:1222 Maintainer use only; not generally accessible: Local ServerWork ServerCSSE Server

711 accesses since 24 Jul 2008, HTML cache rendered at 20120202:0749