The Black box-White box distinction

This short text is written with the aim to clear some confusions and to make all people more aware and proactive in the use case driven development. But the black-box-White-box thinking is also useful for structuring information and knowledge which often has to be worked into layers to be comprehensible and possible to use from different views and by different stakeholders.

Often, even experienced modelers have problems with the distinction between what should be modeled at a certain level versus what is known. When the black box restriction is not followed, it results in messy Use Case descriptions that are difficult to manage in a requirements changing environment. 

---

English pdf version