Practical 'how to quantify and clarify' any type of quality for requirements, design, and project management.
Watch the video
Non-quantified (‘Highly User-friendly') and roughly specified (‘Good quality’) quality requirement specification, is not a serious approach to quality in IT Systems. All interesting qualities need to be designed (architected) into your system. The basis for that is quantification of each concurrent quality requirement.
Most people, and most popular methods, do not know how to do this at all. They seem to believe that if they throw some popular standards or products at the system, that they will achieve the qualities they failed to clarify and specify. This is irresponsible but pervasive.
We will focus primarily on the construction of a Quality Scale of Measure. This is one component of Tom's ‘Planguage' (for modelling IT Systems).
- How to derive a Quality Scale of Measure from a rough ‘Ambition Level’ (or even a User Story)
- Building a Scale with [Qualifiers] to model complex systems, and enable decomposition, for Agile delivery of high-priority conditions (who, where, what, when).
- Specification of Levels of Quality (Status, Wish, Goal, Tolerable, and a few more), with conditions and deadlines.
- A Five-minute hint at a future lecture subject: How to exploit this Quality Requirement to enable Quality Design evaluation, Impact Estimation.
Free pdf books for participants: The core booklet is Quanteer.
QUANTeer: The Art of quantifying your value ideas
148 Pages, 2020, Major edit 2021
Feel free to start reading, before the lecture.
About the speakers
Tom was born in California 1940, lived in the UK 1956-58, Norway 1958 to present. He joined IBM 1958. Consulted for a very wide variety of organisations, and managed to influence some of them in interesting and well documented ways.
Tom is an Honorary Fellow of BCS. See Gilb.com for more details.
He has held many courses at BCS for many years.
Tom is the author of many books and hundreds of papers on these and related subjects. His book ‘Competitive Engineering’ is a substantial definition of requirements ideas. His ideas on requirements are the acknowledged basis for CMMI level 4 (quantification, as initially developed at IBM from 1980). Tom 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.
There are very many organisations and individuals who use some or all of Gilb methods. IBM and HP were two early corporate adopters. Over the recent years, 20,000 engineers at Intel have adopted the Planguage requirements methods. Ericsson, Nokia, and A Major Multinational Finance Group use parts of their methods extensively. Many smaller companies also use the methods.
Our events are for adults aged 16 years and over.
BCS is a membership organisation. If you enjoy this event, please consider joining BCS. You’ll be very welcome. You’ll receive access to many exclusive career development tools, an introduction to a thriving professional community and also help us make IT good for society. Join BCS today.