In this contribution we consider various sorts of vague and imprecise pieces of (requirements) specification information as different view points provided by different stakeholders. Usually there is an obvious “non convergence” in the stakeholders’ views and it is important to address the various sources of ambiguity and inconsistency between such view points. We advocate addressing not only “traditional” inconsistency to drive development forward but include other forms of imprecision like ambiguity and vagueness. The aim is to provide a path from a decentralized viewpoint-oriented style to a document-oriented style of software requirements specification. We use parts of the airport security case study to show aspects of our approach.