Back to [[conference:committee:2014-proposals]]\\
\\
**Title**:Requirements Engineering\\
**Proposer**: [[2014:Tom Gilb]]\\
**Type**: pre-conference tutorial\\
**Duration**: 360 mins\\
**Description**: \\
• Requirements Engineering: The use of a quantified 
Planning Language to articulate all quality, and other 
performance variable, requirements - as a basis for 
Architecture Engineering and Quantified Agile Project 
Management (Evo)\\
\\
1. Overview of a semi formal Planning language (Planguage) 
for articulation of variable requirements and system 
objectives. In particular performance and quality objectives.\\
2. Components of expressing a quality requirement:\\
a. Core: Tag, Scale, Past, Tolerable, Goal\\
i.Advanced supplements to the core\\
b. Background: non core info about the requirement, such 
as: Sponsor, Owner, Dependencies, Assumptions, 
Issues, Risks, Proposed Designs, and many more\\
3. Examples of constructing a specification\\
4. How to articulate and tailor a Scale of Measure (for any 
quality or critical variable requirement)\\
5. Basic Quantified quality control of requirements: the Agile 
Spec QC method. The use of Rules to measure against. The 
use of Entry Exit level standards.\\
\\
\\
Location: Oslo, Norway

JJ: Tom says this Tutorial can be condensed (with loss of detail and time to discuss and absorb, but with gain of seeing the connection between requirements and design, into a half day tutorial, immediately followed by his other preconference submission, Architecture Engineering, also as a half-day.\\
\\