## Are your Requirements complete?

No Analyst will ever can tell if the requirements are complete, however at least completeness can be approached by systematic analysis. The idea goes roughly like this:

Say you should tell all the Integers between 0 and 11, how would you approach that?
Bad way: “6, 3, 2, 1, 8, 6, 5 – so, that’s it or did I miss one?”
Good way: “1, 2, 3, 4, 5, 6, 7, 8, 9, 10 – bingo!” – for example.

Obviously the point is, to obtain an understanding the structure of the domain. Else it is just collecting facts. Finding appropriate systematics, I’d see mainly in the responsibility of the analyst.
Bad way: “Tell me all the integers between 0 and 11.”
Good way: “What’s the next integer after 0?” etc – for example.

To me this is already a basic application of modeling and its benefits.

## About modelpractice

Modeling Theory and Abstraction Awareness in strive for scientific rigour and relevance to information systems engineering.
This entry was posted in Epistemology, Software_Engineering and tagged , , , , , , , , , , , . Bookmark the permalink.

### 3 Responses to Are your Requirements complete?

1. henry says:

slightly more complex example: http://xkcd.com/899/ đŸ˜‰

2. I like this simple example pretty much.
It shows perfect assorting can help to complete requirements.
But it is too inutitive, pretending to find a helpful assorting is very easy.
A look at one less famous order of the numbers between 0 and 11 shows what i mean:
8, 5, 4, 9, 1, 7, … whats next? … not easy? why?
Cause we are not used to the alphabetical order. So itis less intuitiv and less helpful.
So i like the alphabetical assorting example also pretty much.
It shows to choose some helpful assorting is sometimes no trivial problem.

• cool example! In the end it does the job as well, and I like it too, since it shows how many surprisingly different views on a problem there may exist.

thx!
|=