Error: Twitter did not respond. Please wait a few minutes and refresh this page.
Tag Archives: IEEE 830
We’ll see that the concept of ambiguity of (requirements in software engineering) models comprises structural as well as material aspects, on all model levels (top to bottom). Continue reading
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
IEEE 830 provides eight quite abstract characteristics for good requirements, like correctness, completeness, traceablity etc. Continue reading