Tom Gilb

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Jdblaine (talk | contribs) at 21:22, 1 November 2016 (Typographical error, it's software metrics, plural not singular. The title of Gilb's book is "Software Metrics" <ref>Google Books</ref>). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Tom Gilb (born 1940) is an American systems engineer, consultant, and author, known for the development of software metrics, software inspection, and evolutionary processes.

Biography

Tom Gilb was born in 1940 in Pasadena, California, United States. He emigrated to the United Kingdom in 1956 and to Norway in 1958. He took his first job with IBM in 1958 and became a freelance consultant in 1960.

He is currently[when?] a consultant, teacher and author, in partnership with his son Kai Gilb.[1] He mainly helps multinational clients improve their organizations and methods by using "evolutionary systems delivery" (Evo). He has "guest lectured at universities all over UK, Europe, China, India, USA, Korea – and has been a keynote speaker at dozens of technical conferences internationally".[2]

He is a member of INCOSE and is active in the Norwegian chapter, NORSEC, which presented him with an award in 2003.[citation needed] He lectures at INCOSE local chapters on his worldwide travels and at INCOSE conferences.

In 2012 he was made an Honorary Fellow of the British Computer Society.[3]

Publications

Gilb has written nine books and several articles. A selection includes:

  • Software Inspection (book)|Software Inspection, 1993. ISBN 0-201-63181-4.
  • Principles of Software Engineering Management, 1988. ISBN 0-201-19246-2 (19th printing).
  • Software Metrics (Winthrop computer systems series), 1977.
  • Competitive Engineering: A Handbook for Systems & Software Engineering Management using Planguage, 2005. ISBN 0-7506-6507-6. (Planguage is a formal, natural language modelling notation invented by Gilb that adds rigour to the requirement documentation.)

References

External links