TABLE OF CONTENTS This glossary contains the master definitions of the fundamental Planguage concepts. Its central purpose is to define concepts not words. I view this concept glossary as a central contribution of this book, standing in its own right.
"What's in a name? That which we call a rose, by any other name would smell as sweet."
Shakespeare, Romeo and Juliet, Act 2
"Every word or concept, clear as it may seem to be, has only a limited range of applicability."
Werner Heisenberg [1]
With the Heisenberg quotation in mind, this glossary will try to give the interpretation Planguage intends, when the glossary terms are used in this book. (If the text and the glossary do not seem to agree, I suggest you trust the glossary primarily as a correct interpretation. [2])
Further explanation of the glossary-defined concepts is found in the main text (via the index). An updated and extended Planguage Glossary is also to be found on the website http://www.Gilb.com and at http://www.books.elsevier.com. Space limitations within the book meant that not all the glossary could be included.
I have not tried to define all possible concepts for a systems engineering discipline. I have merely concentrated on defining those that I have found useful in my work.
Some other concepts have been included because the glossary has been developed in connection with drafting future books in this Planguage series. (The intended titles are Requirements Engineering, Priority Management
