Differences

This shows you the differences between two versions of the page.

--- 2014:requirements_engineering [2013/11/14 19:26] – jonjagger
+++ 2014:requirements_engineering [2016/06/11 14:05] (current) – external edit 127.0.0.1
@@ Line 6: / Line 6: @@
 **Duration**: 360 mins\\
 **Description**: \\
-We will teach the following practical tools:\\
+• 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)\\
 \\
-. The discipline of estimating the impact of any type of ‘design
+. Overview of a semi formal Planning language (Planguage)
-idea’ on any quantified system requirement level (as defined
+for articulation of variable requirements and system
-by a Scale of measure, and a Goal or Tolerable level of
+objectives. In particular performance and quality objectives.\\
-requirement)\\
+. 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\\
+. Examples of constructing a specification\\
+. How to articulate and tailor a Scale of Measure (for any
+quality or critical variable requirement)\\
+. 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.\\
 \\
-. The corresponding discipline of estimating the design costs
-in several dimensions such as capital expenditure, calendar
-time, and human resources\\
 \\
-. The use of the Impact Estimation Table discipline, for
+Location: Oslo, Norway
-articulating the quality of estimates: ± uncertainty, % of Goal
-or Budget, Source, Evidence, Credibilty, Safety Factor\\
+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.\\
 \\
-. Process and Specification standards: Procedures, Rules,
-Templates, Principles, for Architecture Engineering. Derived
-from the Competitive Engineering book (digital copy supplied
-free).\\
-\\
-. Case studies of use of the Architecture Engineering method\\
-\\
-. Application of Dynamic Design Prioritization\\
-\\
-. Project Management consequences of this basis for articulating the Architecture.\\
-\\
-\\
-\\