Hi,
I would appreciate if this call for participation could be forwarded to the
CPHC list. Many thanks in advance,
Sebastian Uchitel
==========================
A BCS RESG event:
Tom Gilb presents 'Planguage': a planning language for requirements and more.
=========================================================
September 17, 2003. 14.00 - 17.00
Room 418, Huxley Building, Imperial College London
Attendance to the tutorial is free of cost for RESG members.
Registration costs for non-members are the same as becoming a RESG member
(BCS/IEE member: £10, Non-BCS/IEEE member £20, Full time students: free)
Registration via e-mail is required. Please email Sebastian Uchitel
([log in to unmask]) if you wish to attend.
For more details please visit www.resg.co.uk
Please find below the tutorial abstract, outline, and a Tob Gilb bio.
===========================================================
Abstract:
-------------
Requirement(s) Engineering is arguably the most critical single discipline
in systems and software engineering. Bad requirements are cited as a main
cause of large systems engineering project failures (P. Morris, The
Management of Projects, Telford, London 1994). Too little investment in
requirements is proven as a cause for software projects and systems
engineering projects (NASA, IT survey). I would argue that the theory and
teaching of requirements today is in bad shape. There are several signs of
this. Most so-called requirements are actually design for unstated
requirements! Most requirements are a nice sounding set of words with no
testable or quantified structure and very little information about the
requirements and its relation to all other requirements, designs, and
plans. This tutorial will open up a radically new approach to requirements
that will rectify many of these problems. It is based on the ideas in
Planguage a specifically invented and evolved language for requirements
specification. Fundamentals are reexamined (what is a function
requirement?). All qualitative requirements are quantified richly. Ten to
30 parameters are used to describe a single reusable requirement fully and
appropriately for its task. Requirements are related directly and
individually to stakeholders. Requirements are looked at in the wider
systems engineering context of design, testing, project management, and
engineering-work quality-control.
Outline:
-----------
1. Analysis of dangerous common requirements practices.
2. Quantitative measurement of how good a requirement specification is.
3. Basic Rules (standards) for requirement specification
4. Requirement categories, maps and concept definition.
5. Examples of advanced requirements specifications (real cases)
6. Defined processes for requirement specification
7. Templates for requirement specification.
8. Exploitation of requirement specification by other disciplines.
9. Requirement Policy examples
10. Fundamental Principles of Requirement specification.
Bio:
-------
Tom Gilb born 1940, in Pasadena California, emigrated to London in 1956 and
to Norway in 1958, took his first job with IBM in 1958 and became a
freelance consultant in 1960. He is the author is 9 books and has at least
4 more drafted and contracted for publication. Current printings include
Software Inspection (1993) and Principles of Software Engineering
Management (1988, now in 15th printing). His next book Competitive
Engineering: A Handbook for Systems & Software Engineering Management using
Planguage will be published in 2003 by Addison Wesley. Much of his current
work is available on his website, www.Gilb.com. He is currently a
consultant, teacher and author in partnership with his son. He mainly
serves multinational clients in improving their organizations and methods.
Current clients include BAE Systems, Sun Microsystems, CitiGroup, Philips
Medical Systems, Nokia, HP, Intel, Microsoft, Canon. Email [log in to unmask]
Tom is a semi active participant at RESG meetings when he is in the UK.
|
