*************************************************************************
_An Audience With David Parnas_
Wednesday 25 May 2005
Imperial College London
http://www.resg.org.uk/
A chance to hear one of the big names in software engineering.
David Parnas is an early pioneer of software engineering who developed
the concept of modular design, the foundation of object-oriented systems
today. His double dictum of high cohesion within modules and loose
coupling between modules is part of the bedrock on which encapsulation
as a design technique is built.
10.00 - 13.00 Tutorial (coffee at 9:30 and 11:30am)
13.00 - 15.00 Lunch (not provided, but there are plenty of
places to eat locally)
15.00 - 16.00 (plus discussion time) Distinguished Speaker Lecture
_Tutorial Abstract_
"Preparing Requirements Documents using the Four (Five) Variable Model"
Unless you have a complete and precise description of a product's
requirements, it is very unlikely that those requirements will be
satisfied. An incomplete or inconsistent requirements document can
actually mislead developers and introduce errors. A collection of
statements in English, or some other natural language, cannot be checked
for completeness and will not be precise. Even if you translate an
informal requirements statement into a mathematical language, and show
that the result is complete and unambiguous; the original may still be
faulty.
This talk describes a sound procedure for documenting requirements - one
that lets you know when your document is complete and consistent. The
resulting documents can be reviewed by potential users and specialists
and serve as input to tools that generate prototypes and monitors.
_Distinguished Speaker Lecture Abstract_
"Document Driven Disciplined Development of Software"
It is no accident that the branches of Engineering are called
"disciplines". Every properly educated Engineer has learned that the
design of quality products requires discipline and adherence to standard
procedures. Engineers understand that they must produce a specified set
of documents and perform a variety of analysis whose results must be
included in the documents. Engineers who do these things are less likely
to produce a defective product. In many jurisdictions, engineers who
fail to follow the standard discipline may be considered to have been
legally negligent. Software development should not be different but it is.
Document standards can help to support and enforce the appropriate
discipline. We describe a set of documents that contain the information
required for disciplined development. A developer who completes these
documents properly will have performed the analysis necessary to assure
that the product will be of high quality. This talk does not describe a
"process". Discipline does not require that these documents be completed
in any particular order - only that they are all eventually completed
properly.
*************************************************************************
The morning tutorial and afternoon lecture will be treated as separate
events.
Morning tutorial registration -
Student registration : £50.00
RESG member registration : £75.00
Non-RESG member registration : £100.00
Afternoon lecture registration -
free
*************************************************************************
NB If the formatting below is corrupted, the form can be downloaded from
http://www.resg.org.uk/parnasreg.txt
_REGISTRATION FORM_
Please return completed registration forms to -
William Heaven,
PhD. Dept of Computing,
180 Queen's Gate,
Imperial College London
SW7 2AZ
[log in to unmask]
Please attach duplicate registration forms if more than one delegate is
attending.
I would like to attend the morning tutorial / the afternoon lecture
(free) / both (please indicate).
I enclose a cheque for £ ___________ for the morning tutorial.
Please make cheques payable to "BCS Requirements Engineering Specialist
Group".
Dr/Mr/Ms ____ First name ______________ Surname __________________
Organisation _____________________________________________________
Address __________________________________________________________
___________________________________________ Post code ____________
Tel __________________
Fax __________________
Please send an invoice: yes/no.
Invoice address if different to above:
Organisation ______________________________________________________
Address ___________________________________________________________
___________________________________________ Post code _____________
Date _________________
--
William Heaven <http://www.doc.ic.ac.uk/~wjh00>
RESG Publicity Officer <http://www.resg.org.uk>
|
