User Tools

Site Tools


2014:architecture_engineering

Differences

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

Link to this comparison view

Next revision
Previous revision
2014:architecture_engineering [2013/11/14 19:28] – created jonjagger2014:architecture_engineering [2016/06/11 14:05] (current) – external edit 127.0.0.1
Line 8: Line 8:
 The use of a quantified Planning Language to articulate all quality and other  The use of a quantified Planning Language to articulate all quality and other 
 performance variable attributes of all designs, architecture  performance variable attributes of all designs, architecture 
-ideas, and strategies– as a basis for Architecture Decisions +ideas, and strategies as a basis for Architecture Decisions 
 and Quantified Agile Project Management (Evo)\\ and Quantified Agile Project Management (Evo)\\
 \\ \\
 We will teach the following practical tools:\\ We will teach the following practical tools:\\
 \\ \\
-1. The discipline of estimating the impact of any type of design  +1. The discipline of estimating the impact of any type of 'design  
-idea’ on any quantified system requirement level (as defined +ideaon any quantified system requirement level (as defined 
 by a Scale of measure, and a Goal or Tolerable level of  by a Scale of measure, and a Goal or Tolerable level of 
 requirement)\\ requirement)\\
Line 23: Line 23:
 \\ \\
 3. The use of the Impact Estimation Table discipline, for  3. The use of the Impact Estimation Table discipline, for 
-articulating the quality of estimates: ± uncertainty, % of Goal +articulating the quality of estimates: +- uncertainty, % of Goal 
 or Budget, Source, Evidence, Credibilty, Safety Factor\\ or Budget, Source, Evidence, Credibilty, Safety Factor\\
 \\ \\
2014/architecture_engineering.1384457336.txt.gz · Last modified: 2016/06/11 14:05 (external edit)