Discovering requirements
Speaker: Ian Alexander
Date 14 October 2008
Time
This seminar is now fully booked.
Location
The Savoy Tup, The Strand, London, WC2R 0BA
Introduction
Ian Alexander an Independent Consultant, Specialising in Requirements will review his soon to be published book "Discovering Requirements", being published by John Wiley in March 2009.
The book is organised into three parts: discovering requirement elements; contexts for discovery and discovering priorities.
Outline
- Requirements work is simple but not easy: it is a craft which requires skill. Fortunately, that can be learnt.
- Requirements are discovered by appropriate inquiry techniques. They are not sitting about waiting to be “captured”. The many different situations demand a set of different techniques.
- When requirements are undefined, a project knows neither what it needs to do, nor how big a problem it faces. A “soft systems” process that can handle undefined problems is required, at least at first.
- Requirements are more than a list of statements of what a system must do. A better approach is to define a network of related elements, including such things as definitions, goals, scenarios, rationale, and measurements.
- Requirements work involves a discovery cycle: discover with stakeholders; document; validate with stakeholders.
- The book is organised into three parts: discovering requirement elements; contexts for discovery; and discovering priorities.
Programme
Arrive at 6pm, hear Ian's talk and then enjoy further discussion and questions with other attendees over a light buffet supper. The pub will operate a cash bar as normal.
Organiser
The Systems Engineering Technical Professional Network

