Tutorial H06: The Requirements DrivenManagement Approach to Systems Engineering.

Description:

The RDM method is a freely available set of concepts for managing systems engineering.There are four major components.

  1. ‘Requirements specification’ based on a well-defined specification language called ‘Planguage’, which emphasizes quantified and testable control over all critical quality parameters, and the specification of customer ‘end needs’, not ‘means’.
  2. The ‘design process’ (finding the means to meet the ends) is based on visibly quantified satisfaction of all stated quality and cost requirements, and is monitored by an Impact Estimation table which uses objective data, and documents uncertainty and risk.
  3. Document Quality Control (DQC) based on the Software Inspection Process. DQC is a rigorous process, controlled by feedback and optimization, for detecting and correcting defects, for process improvement, for all critical engineering plans and specifications. This DQC process has been proven superior to all conventional checking, reviewing methods in Aircraft Industry, in software and Electronics applications for dealing with Major defects early.
  4. All these processes integrated with a project management process based on the Evolutionary Delivery paradigm ("Evo"), which operates with step deliveries at 2% to 10% of total budget for early delivery and feedback and correction. This is probably the most powerful known (DoD and Civil) project management method for systems engineering projects.

Intended Audience:

Project Managers, Methods Consultants and Teachers

Class Size: Limited to 50 participants.

Instructor:

Tom Gilb was born in Pasadena in 1940, emigrated to London 1956, and toNorway 1958, where he joined IBM for 5 years, and where he resides when not travelling.

He has mainly worked within the software engineering community, but since 1983 withCorporate Top Management problems, and 1988 with large scale systems engineering. He is anindependent teacher, consultant and writer. He has published eight books, including theearly coining of the term "Software Metrics" (1976) which is the basis for SEICMM Level 4. He wrote "Principles of Software Engineering Management" (1988, nowin 13th printing), and "Software Inspection" (1993). Both titles are reallysystems engineering books in software disguise. His pro bono systems engineeringactivities include several weeks a year for US DoD and Norwegian DoD, and environmental(EPA) and Third-World Aid charities or organizations.

Additional Information:

The instructor has indicated he will also provide:

Proposed Course Outline: