MIS Peer Review Issue #5

[whitere123]

Hello @vajihehm ,

This issue is regarding section 11 (ContoursADT) of your MIS document.

• You say that z : R and than proceed to say that it is a sequence. If this is a finite sequence you might be able to get away with saying that it is a vector in R^a where a is the number of elements in the sequence. (you do something similar with s: FuncT. )
• I do not think that it is proper MIS convention to put actual code into this document. You did this for slice(x,flip). I thought the purpose of this document was to explain everything mathematically. I could be wrong. @smiths, should we have code in our MIS?

[smiths]

@whitere123 you are correct that ideally code is not part of the specification for a module. The goal is to provide a state based specification - a specification that says what should happen, but not the steps for its calculation. However, there are cases where this kind of specification is difficult to write, or more confusing than it has to be. In those cases we can use a procedural specification. It is still a specification, just a different form.