Tag Archives: Consistent

Reflections on Abstractions: Correctness and Completeness

An earlier post on quality properties of models is compared to basic concepts of mathematical logic, in strive for rigour. What does a formal system of mathematical logic has in common with a modelling situation as in requirements analysis? It depends … Continue reading

Posted in Mathematics, Reflections on Abstractions | Tagged , , , , , , , , , , , , , , , , , , , , , , | Leave a comment

Models: Correct, Complete, Consistent, Unambiguous

How do you judge how ‘good’ or ‘bad’ a model is? I mean models like we use them in software requirements specification or business analysis. On this, one can find criteria in literature like BABOK, Wikipedia, IEEE, research papers, or textbooks. However, for some reason these criteria sets are quite different in each case. I’ve tried to get the things a little straighter, starting with the ‘big four’ quality characteristics of software requirements specifications … Continue reading

Posted in Mathematics, Requirements | Tagged , , , , , , , , , , , , , , , , , , , , , | 1 Comment

Making use of IEEE 830 for Requirements Engineering

IEEE 830 provides eight quite abstract characteristics for good requirements, like correctness, completeness, traceablity etc. Continue reading

Posted in Software_Engineering | Tagged , , , , , , , , , , , , , , | Leave a comment