Competitive Engineering documents Tom Gilb's unique, ground-breaking approach to communicating management objectives and systems engineering requirements, clearly and unambiguously. Competitive Engineering is a revelation for anyone involved in management and risk control. Already used by thousands of project managers and systems engineers around the world, this is a handbook for initiating, controlling and delivering complex projects on time and within budget. The Competitive Engineering methodology provides a practical set of tools and techniques that enable readers to effectively design, manage and deliver results in any complex organization - in engineering, industry, systems engineering, software, IT, the service sector and beyond. Elegant, comprehensive and accessible, the Competitive Engineering methodology provides a practical set of tools and techniques that enable readers to effectively design, manage and deliver results in any complex organization - in engineering, industry, systems engineering, software, IT, the service sector and beyond.
- Provides detailed, practical and innovative coverage of key subjects including requirements specification, design evaluation, specification quality control and evolutionary project management
- Offers a complete, proven and meaningful 'end-to-end' process for specifying, evaluating, managing and delivering high quality solutions
- Tom Gilb's clients include HP, Intel, CitiGroup, IBM, Nokia and the US Department of Defense
Inhaltsverzeichnis
1;Front cover;1 2;Title page;4 3;Copyright page;5 4;Table of contents;6 5;Foreword;8 6;Endorsements;10 7;Preface;13 7.1;Background to writing Competitive Engineering;13 7.2;Major influences on Planguage;13 7.3;How to use this book;14 7.4;Some book conventions;14 8;Acknowledgements;16 8.1;Further acknowledgements;17 9;Introduction;18 9.1;What is in Competitive Engineering?;18 9.2;How was Competitive Engineering developed?;19 9.3;What is special about Planguage?;19 9.4;How to use Competitive Engineering;20 9.5;Structure of Competitive Engineering;21 9.6;Format of Competitive Engineering;21 9.7;A friendly warning;22 10;1 Planguage Basics and Process Control: The Purpose of Planguage;24 10.1;1.1 Introduction: Why We Need a Different Systems Engineering Approach;26 10.1.1;Learning through Rapid Feedback;26 10.1.2;Dynamic Adaptability;26 10.1.3;Capturing the Requirements;27 10.1.4;Focus on Results;27 10.1.5;Interdisciplinary Communication;28 10.1.6;Leadership and Motivation;28 10.1.7;Receptiveness to Organizational Change;28 10.1.8;Continuous Process Improvement;28 10.1.9;Practical Strategies for Systems Engineering;29 10.2;1.2 Practical Example: Twelve Tough Questions;30 10.3;1.3 Language Core: Planguage Basics and Process Control;32 10.3.1;Planguage Specification Language;32 10.3.1.1;A Set of Defined Concepts;32 10.3.1.2;A Set of Defined Parameters and Grammar;32 10.3.1.3;A Set of Icons;32 10.3.2;Planguage Process Descriptions;32 10.3.2.1;Requirement Specification (RS);33 10.3.2.2;Design Engineering (DE);33 10.3.2.3;Specification Quality Control (SQC);33 10.3.2.4;Impact Estimation (IE);33 10.3.2.5;Evolutionary Project Management (EVO, also known as Evo);33 10.3.3;Standards;33 10.3.4;Rules;35 10.3.5;Process Descriptions;35 10.3.5.1;Entry Conditions;35 10.3.5.2;Procedure;36 10.3.5.3;Exit Conditions;36 10.4;1.4 Rules: Generic Rules for Technical and Management Specification;39 10.5;1.5 Process Description: Generic Project;42 10.5.1;Entry Conditions;43 10.5.2;Procedure;43 1
0.5.3;Exit Conditions;44 10.5.4;Generic Entry and Exit Process and Conditions;44 10.5.4.1;Process: Generic Entry or Generic Exit;44 10.5.4.2;Procedure;44 10.6;1.6 Principles: Generic Project;46 10.7;1.7 Additional Ideas;48 10.7.1;Continuous Process Improvement;48 10.8;1.8 Further Example/Case Study: Continuous Process Improvement at Raytheon;51 10.8.1;Background;51 10.8.2;Aim;51 10.8.3;Financing the Improvements;51 10.8.4;Measuring the Effects;52 10.8.5;Calculating Savings;52 10.9;1.9 Diagrams/Icons;53 10.9.1;Some Basic Planguage Icons;54 10.9.1.1;Document or Specification;54 10.9.1.2;Plan-Do-Study-Act Process Cycle;54 10.10;1.10 Summary: Planguage Basics and Process Control;56 11;2 Introduction to Requirements: Why?;58 11.1;2.1 Introduction to Requirements Specification;60 11.1.1;Definition of Requirements;60 11.1.2;Key Issues for Requirements;61 11.1.2.1;Identifying the critical stakeholders;61 11.1.2.2;Separating Ends and Means;62 11.1.2.3;Identifying the key requirements;62 11.1.2.4;Quantifying success and failure;62 11.1.3;Understanding the past and the future benchmarks and state-of-the-art;63 11.1.4;Considering the timescales for delivery of requirements;64 11.1.5;Avoiding the ambiguity trap;64 11.1.6;Handling complex requirements;65 11.1.7;Allowing requirements to evolve;65 11.2;2.2 Practical Example: What is Flexibility Improvement?;66 11.2.1;Analyzing a requirement;66 11.2.2;Decomposition of Requirements;68 11.2.3;Scalar Requirements;69 11.3;2.3 Language Core: Sytem Attributes and Requirement Specification Types;70 11.3.1;System Attributes;70 11.3.1.1;System;70 11.3.1.2;Attribute;70 11.3.1.3;Function;71 11.3.1.4;Performance;72 11.3.1.5;Resource;73 11.3.1.6;Design;74 11.3.2;Requirement Types;74 11.3.2.1;Vision;75 11.3.2.2;Basic Requirement Types;76 11.3.2.2.1;Function Requirement: what a system has to do.';77 11.3.2.2.2;Performance Requirement;77 11.3.2.2.2.1;Quality Requirement;78 11.3.2.2.2.2;Resource Saving Requirement;79 11.3.2.2.2.3;Workload Capacity R
equirement;79 11.3.2.2.3;Resource Requirement;80 11.3.2.2.4;Design Constraint;80 11.3.2.2.5;Condition Constraint;80 11.4;2.4 Rules: Requirement Specification;84 11.5;2.5 Process Description: Requirement Specification;85 11.5.1;Process: Requirement Specification;85 11.5.1.1;Entry Conditions;86 11.5.1.2;Procedure;86 11.5.1.3;Exit Conditions;87 11.6;2.6 Principles: Requirement Specification;87 11.7;2.7 Additional Ideas;88 11.7.1;Using Qualifiers to Specify Conditions;88 11.7.1.1;Qualifier Definition;89 11.7.1.2;Qualifiers and System Space/Scope;91 11.7.1.3;The Difference between Qualifier Conditions and Condition Constraints;91 11.7.1.4;Qualifiers and Evo Steps;91 11.7.2;Additional Ideas Concerning Constraints;92 11.7.2.1;Adherence to Constraints;92 11.7.2.2;Constraint Viewpoints;93 11.8;2.8 Further Example/Case Study: A Proposal to the Board for $60 Million;94 11.9;2.9 Diagrams/Icons: Requirement Specification;98 11.10;2.10 Summary: Requirement Specification;101 12;3 Functions: What systems do;104 12.1;3.1 Introduction: Function and Function Requirement Specification;106 12.1.1;Separation of Functions from Design Ideas;106 12.1.2;Function Requirements;108 12.2;3.2 Practical Example: Function Analysis;110 12.2.1;Stakeholders;110 12.2.2;Functions;111 12.3;3.3 Language Core: Function and Function Requirement Specification;112 12.3.1;Referencing Functions;113 12.3.2;Specifying an Arbitrary Set of Functions;113 12.3.3;Inheritance of Higher Level Requirements;113 12.3.4;Function Specification;114 12.3.4.1;Function Description;114 12.3.4.2;Functional Relationships;115 12.3.4.2.1;Sub-functions;115 12.3.4.2.2;Supra-functions;115 12.3.4.2.3;Sibling functions;115 12.3.4.3;Defining Supra-functions (as a set of functions);115 12.3.4.4;Referencing Supra-functions for a Function;115 12.3.4.5;Defining Sibling Functions;116 12.3.4.5.1;Attributes of a Function;116 12.3.4.5.2;Qualifiers;117 12.4;3.4 Rules: Function and Function Requirement Specification;117 12.4.1;Functionality;117 12.4
.2;Detail;117 12.4.3;Not Degrees;118 12.4.4;Not Design;118 12.4.5;Function Priority;119 12.4.6;Testable;119 12.4.7;Test;119 12.5;3.5 Process Description: Function Requirement Specification;120 12.5.1;Process: Function Requirements;120 12.5.1.1;Entry Conditions;120 12.5.1.2;Procedure;120 12.5.1.3;Exit Conditions;121 12.6;3.6 Principles: Function and Function Requirement Specifications;122 12.7;3.7 Additional Ideas: Function and Function Requirement Specification;123 12.7.1;Mission;123 12.7.2;Elementary and complex concepts;123 12.7.3;Measuring Functionality;124 12.7.4;Additional Examples of Function Specification;124 12.8;3.8 Further Example/Case Study: Function Specification for an Airborne Command and Control System;125 12.9;3.9 Diagrams/Icons: Function and Function Requirement Specification;128 12.10;3.10 Summary: Function and Function Requirement Specification;130 13;4 Performance: How Good?;132 13.1;4.1 Introduction;134 13.1.1;Performance: Quality, Resource Savings and Workload Capacity;134 13.1.1.1;Quality;135 13.1.1.2;Resource Savings;135 13.1.1.3;Workload Capacity;135 13.2;4.2 Practical Example: Performance Requirements;136 13.2.1;Step 1;137 13.2.2;Step 2;137 13.2.3;Step 3;137 13.3;4.3 Language Core: Scalar Attributes;139 13.3.1;Ambition;140 13.3.2;Scale;140 13.3.3;Meter;140 13.3.4;Benchmarks;140 13.3.5;Targets;141 13.3.5.1;Goal;141 13.3.5.2;Budget;141 13.3.5.3;Stretch;141 13.3.5.4;Wish;141 13.3.6;Constraints;141 13.3.6.1;Fail;142 13.3.6.2;Survival;142 13.3.7;Conditions;142 13.4;4.4 Rules: Scalar Requirements;145 13.4.1;Completeness;146 13.4.2;Explode;146 13.4.3;Scale;146 13.4.4;Meter;146 13.4.5;Benchmark;146 13.4.6;Requirement;146 13.4.7;Goal or Budget;146 13.4.8;Stretch;146 13.4.9;Wish;146 13.4.10;Fail;147 13.4.11;Survival;147 13.5;4.5 Process Description: Performance Requirements;147 13.5.1;Process: Performance Requirements;147 13.5.1.1;Entry Conditions;148 13.5.1.2;Procedure;148 13.5.1.3;Exit Conditions;149 13.6;4.6 Principles: Performance Requirements;14
9 13.7;4.7 Additional Ideas: Performance Requirements;150 13.7.1;Handling Complex Performance Requirements;150 13.7.2;Limit the Amount of Detail;151 13.7.3;Setting Scalar Levels;151 13.7.3.1;Implicit Assumptions Supporting a Scalar Parameter Level;151 13.8;4.8 Further Example/Case Study: Performance Specification for a Water Supply;154 13.9;4.9 Diagrams/Icons: Scalar Attribute Requirements;156 13.10;4.10 Summary: Performance Requirements;159 14;5 Scales of Measure: How to Quantify;160 14.1;5.1 Introduction;162 14.1.1;Finding and Developing Scales of Measure and Meters;162 14.1.2;Reference Library for Scales of Measure;162 14.1.3;Reference Library for Meters;163 14.1.4;Managing What You Measure;163 14.2;5.2 Practical Example: Scale Definition;164 14.2.1;Level of Specification Detail;167 14.3;5.3 Language Core: Scale Definition;168 14.3.1;Specifying Scales;168 14.3.1.1;The Central Role of a Scale within Scalar Attribute Definition;168 14.3.1.2;Specifying Scales using Qualifiers;169 14.3.1.2.1;Embedded Qualifiers within a Scale;169 14.3.1.2.2;Additional Qualifiers;169 14.4;5.4 Rules: Scale Definition;170 14.4.1;Standard;170 14.4.2;Notify Owner;171 14.4.3;Scale Definition;171 14.4.4;Elementary Attribute;171 14.4.5;Differentiate;171 14.4.6;Uncertainty;171 14.4.7;Scalar Priority;171 14.5;5.5 Process Description: Scale Definition;172 14.5.1;Process: Scale Definition;172 14.5.1.1;Entry Conditions;172 14.5.1.2;Procedure;173 14.5.1.3;Exit Conditions;174 14.6;5.6 Principles: Scale Definition;174 14.7;5.7 Additional Ideas: Generic Hierarchies for Scalar Attributes;176 14.7.1;Hierarchy of Performance;176 14.7.1.1;Performance;176 14.7.1.1.1;Quality;176 14.7.1.1.1.1;Availability;176 14.7.1.1.1.1.1;Reliability;177 14.7.1.1.1.1.2;Maintainability;178 14.7.1.1.1.1.3;Integrity;178 14.7.1.1.1.2;Adaptability;178 14.7.1.1.1.2.1;Flexibility;180 14.7.1.1.1.2.2;Upgradeability;180 14.7.1.1.1.3;Usability;181 14.7.1.1.1.3.1;Entry Level Experience;181 14.7.1.1.1.3.2;Training Requirement;181 14.7
.1.1.1.3.3;Handling Ability;181 14.7.1.1.1.3.4;Likeability;182 14.7.1.1.1.3.5;Demonstrability;182 14.7.1.1.2;Resource Savings;183 14.7.1.1.2.1;Financial Saving;183 14.7.1.1.2.2;Time Saving;183 14.7.1.1.2.3;Effort Saving;184 14.7.1.1.2.4;Equipment Saving;184 14.7.1.1.3;Workload Capacity;184 14.7.1.1.3.1;Throughput;184 14.7.1.1.3.2;Response Time;184 14.7.1.1.3.3;Storage Capacity;184 14.8;5.8 Further Example/Case Study: Scale Definition;184 14.9;5.9 Diagrams/Icons: Scale Definition;186 14.10;5.10 Summary: Scales of Measure;186 15;6 Resources, Budgets and Costs: Costs of Solutions;188 15.1;6.1 Introduction;190 15.1.1;Relationships amongst Resources, Budgets and Costs;190 15.1.2;Stakeholder Requirements and Resources;190 15.1.3;The Relationship between Costs and Performance Delivery;191 15.1.4;Look at the Use of Resources across the Entire System Lifetime;192 15.1.5;Numeric Performance Levels Enable Us to Understand the Associated Costs Better;192 15.1.6;The Cost of Perfection Beware Infinite Cost Increases;192 15.1.7;Specify Costs Down to a More Detailed Level Not Just Total Costs!;193 15.1.8;Accurate Estimation of Costs in Advance is Unlikely for Complex Systems;193 15.1.9;Use Design to Cost and Evolutionary Project Management (Evo);194 15.2;6.2 Practical Example: Resources, Budgets and Costs;195 15.2.1;Resource Requirement Specifications: Allocation of Resources;195 15.3;6.3 Language Core: Resources, Budgets and Costs;197 15.4;6.4 Rules: Resource Requirement Specification;197 15.5;6.5 Process Description: Resource Requirement Specification;198 15.5.1;Process: Resource Requirement Specification;198 15.5.1.1;Entry Conditions;198 15.5.1.2;Procedure;198 15.5.1.3;Exit Conditions;199 15.6;6.6 Principles: Resource Requirements;199 15.7;6.7 Additional Ideas;200 15.7.1;Using Impact Estimation and Evolutionary Processes to Balance Requirements;200 15.8;6.8 Real Example: Resource Target and Resource Constraint Specification;202 15.9;6.9 Diagrams/Icons: Resource Requirement Speci
fication;204 15.9.1;Resource Requirement Icons;204 15.9.2;Resource Requirement Specification Template;204 15.10;6.10 Summary: Resource Requirement Specification;204 16;7 Design Ideas and Design Engineering: How to Solve the Requirements Problem;208 16.1;7.1 Introduction;210 16.1.1;To Design and to Engineer;210 16.1.2;Requirement Specification, Design Engineering and Evo are all Iterative Processes;210 16.1.3;Requirements Dictate and Constrain the Design, but Detailed Requirement Specification can Wait;211 16.1.4;Any Design Idea can be Considered;212 16.1.5;Design Ideas can be Identified during Requirement Specification;213 16.1.5.1;Potential Design Ideas;213 16.1.5.2;Design Constraints;214 16.1.6;The Need for Alternative Design Ideas;214 16.1.6.1;Choosing the Best from the Alternatives;214 16.1.6.2;Choosing the Best Combined Set from all the Alternatives;214 16.1.6.3;Reducing Risk by Use of Alternative Design;215 16.1.7;Design Optimization;215 16.1.7.1;Cost Minimization;215 16.1.7.2;Design to Cost;215 16.1.7.3;Design to Performance Targets within Cost;216 16.1.7.4;Design for Risk;216 16.1.8;Brief Recap of Planguage Methods and the Design Engineering Process;216 16.1.8.1;Requirement Specification;216 16.1.8.2;Impact Estimation (IE);216 16.1.8.3;Evolutionary Project Management;217 16.2;7.2 Practical Example: Beginning the Design Engineering Process;217 16.3;7.3 Language Core: Design Idea Specification;220 16.4;7.4 Rules: Design Specification;223 16.4.1;Design Separation;223 16.4.2;Detail;223 16.4.3;Explode;223 16.4.4;Dependencies;223 16.4.5;Impacts;223 16.4.6;Side Effects;224 16.4.7;Background Information;224 16.4.8;IE table;224 16.4.9;Constraints;225 16.4.10;Rejected Designs;225 16.5;7.5 Process Description: The Design Engineering Process;225 16.5.1;Process: Design Engineering Process;225 16.5.1.1;Entry Conditions;226 16.5.1.2;Procedure;226 16.5.1.2.1;Analyze the Requirements;226 16.5.1.2.1.1;Establish the Stakeholder Value on Delivery of each Requirement;227 16.5.1.
2.1.2;Sequence the Delivery Order of the Requirements;227 16.5.1.2.1.3;Establish Scope of Design Interest;227 16.5.1.2.1.4;Make a List of Requirements within the Scope defined;227 16.5.1.2.2;Find and Specify Design Ideas;228 16.5.1.2.2.1;Exploit any Earlier Notes of Design Ideas;228 16.5.1.2.2.2;Establish the Design Constraints;228 16.5.1.2.2.3;Brainstorm Design Ideas;228 16.5.1.2.2.4;Draft Design Ideas;229 16.5.1.2.2.5;Collect Specification Detail (to support later Impact Estimation);229 16.5.1.2.2.6;Consider Design Implementation;229 16.5.1.2.2.7;Consider System Capacity and Growth;229 16.5.1.2.3;Evaluate Design Ideas;229 16.5.1.2.3.1;Filter for Violation of any Constraint;229 16.5.1.2.3.2;Estimate all Impacts;230 16.5.1.2.3.3;Consider Side Effects;230 16.5.1.2.3.4;Consider Safety Margins;230 16.5.1.2.4;Select Design Ideas and Produce Evo Plan;230 16.5.1.2.4.1;Initial Sequencing of Design Ideas;230 16.5.1.2.4.2;Ensure adequate Safety Margins to address Risks;231 16.5.1.2.4.3;Consider Design Ideas with regard to the Risks;231 16.5.1.2.4.4;Consider Optimization;232 16.5.1.2.4.5;Re-define Design Definitions;232 16.5.1.2.4.6;Consider Pilot and/or Trial;232 16.5.1.3;Exit Conditions;232 16.6;7.6 Principles: The Design Engineering Process;233 16.7;7.7 Additional Ideas;234 16.7.1;Priority Determination;234 16.7.1.1;What is wrong with the Subjective Weighting Approach for Determining Priority?;235 16.7.1.2;The Role of Resource in Determining Priority;236 16.7.1.3;Planguage Information Supports Priority Determination;236 16.7.1.4;Priority Strategy;237 16.7.1.5;Dynamic Priority Evaluation;237 16.8;7.8 Further Example/Case Study: Design Specifications Masquerading as Requirements;237 16.9;7.9 Diagrams/Icons: The Design Engineering Process;239 16.10;7.10 Summary: The Design Engineering Process;241 17;8 Specification Quality Control: How to know how well you specified;244 17.1;8.1 Introduction: Specification Quality Control;246 17.1.1;Improving Process;246 17.1.2;Saving Time;24
7 17.1.3;Increasing Productivity;247 17.1.4;Industrial Usage;247 17.2;8.2 Practical Example: Specification Quality Control;248 17.3;8.3 Language Core: Specification Quality Control;251 17.3.1;Basic Definitions (see also Glossary terms);251 17.3.1.1;Specification Quality Control (SQC);251 17.3.1.2;Defect Detection Process;251 17.3.1.3;Defect Prevention Process;251 17.3.1.4;Issue;251 17.3.1.5;Defect;252 17.3.1.6;Major defect;252 17.3.1.7;Page;252 17.3.1.8;Checking Rate;252 17.3.1.9;Optimum Checking Rate;252 17.3.1.10;Remaining Major Defects;253 17.3.1.11;Checklist;253 17.3.1.12;Rule;253 17.3.1.13;Main Specification;253 17.3.1.14;Source Documents;253 17.3.1.15;Kin Documents;254 17.4;8.4 Standards: Specification Quality Control;254 17.4.1;Guidelines for assessing functioning of overall SQC;254 17.4.1.1;Economic;254 17.4.1.2;SQC Champion;254 17.4.1.3;Team Leaders;254 17.4.1.4;Statistics;254 17.4.1.5;Meetings;254 17.4.1.6;Checkers;255 17.4.1.7;Checking Rate;255 17.4.1.8;Condition;255 17.4.1.9;Standards;255 17.4.1.10;Upstream Pollution;255 17.4.2;Forms;255 17.4.3;SQC Process Roles and Responsibilities;260 17.4.3.1;Team Leader;260 17.4.3.2;Checker;260 17.4.3.3;Writer: Also Known as Author;261 17.4.3.4;Editor;261 17.4.3.5;Scribe;261 17.4.3.6;Others;261 17.5;8.5 Process Description: Specification Quality Control;262 17.5.1;Process: Specification Quality Control;262 17.5.1.1;Entry Conditions;262 17.5.1.2;SQC Sub-Processes;262 17.5.1.2.1;Entry;262 17.5.1.2.2;Planning;262 17.5.1.2.3;SQC Strategy;262 17.5.1.2.4;Kickoff;263 17.5.1.2.5;Checking;263 17.5.1.2.6;Specification Meeting;263 17.5.1.2.6.1;Checkers Report;263 17.5.1.2.6.2;Issue Logging;263 17.5.1.2.6.3;Double Checking;263 17.5.1.2.7;Process Meeting;264 17.5.1.2.8;Edit;264 17.5.1.2.9;Edit Audit;264 17.5.1.2.10;SQC Statistics;264 17.5.1.2.11;Exit;264 17.5.1.2.12;Exit Conditions;265 17.5.1.2.13;A Simplified SQC Process;265 17.6;8.6 Principles: Specification Quality Control;269 17.7;8.7 Additional Ideas: Specification Quality C
ontrol;269 17.7.1;Economics of using SQC;269 17.7.2;Effectiveness of SQC;270 17.7.3;Determining Effectiveness and Estimating Remaining Defects;270 17.7.4;SQC and Rules;272 17.7.5;Extending from SQC into Specification Review;272 17.8;8.8 Further Example/Case Study: A Stitch in Time Saves Nine;273 17.8.1;Use of SQC on many different types of document;274 17.8.2;The Organization Must be Supportive and SQC Needs a Champion;275 17.9;8.9 Diagrams/Icons: Specification Quality Control;275 17.10;8.10 Summary: Specification Quality Control;280 17.10.1;Finding Defects;281 17.10.2;Understanding Document Quality;281 17.10.3;Continuous Process Improvement;282 18;9 Impact Estimation: How to understand strategies;284 18.1;9.1 Introduction to Impact Estimation;286 18.2;9.2 A Simple Practical Example of Impact Estimation;288 18.3;9.3 Language Core: Impact Estimation;291 18.4;9.4 Rules/Forms/Standards: Impact Estimation;294 18.4.1;Table Format;294 18.4.2;Requirement;294 18.4.3;Qualifiers;294 18.4.4;Design Idea;295 18.4.5;Scale Impact;295 18.4.6;Percentage Impact;295 18.4.7;Uncertainty;295 18.4.8;Evidence;295 18.4.9;Credibility;296 18.4.10;Completeness;296 18.4.11;Calculations;296 18.4.12;Credibility-Adjusted Calculations;299 18.5;9.5 Process Description/Standards: Impact Estimation;299 18.5.1;Process: Impact Estimation;299 18.5.1.1;Entry Conditions;299 18.5.1.2;Procedure;299 18.5.1.3;Exit Conditions;301 18.6;9.6 Principles: Impact Estimation;301 18.7;9.7 Additional Ideas: Impact Estimation;303 18.7.1;Understanding Mathematical Inaccuracy;303 18.7.2;Level of Detail;303 18.7.3;Coping with Interactions amongst Design Ideas;303 18.7.3.1;Considering Side Effects;303 18.7.3.2;Dealing with Alternatives;303 18.7.3.3;Dealing with Dependencies;303 18.7.4;Priority Management within IE;304 18.7.4.1;Can We Always Use the Stated Requirements to Determine Priority?;304 18.7.5;Managing Risk: Building in Safety Margins;306 18.7.6;Highlighting System Failure and System Survival Levels;306 18.8;9.8 Furt
her Example/Case Study: IE Table for US Army Personnel System Long Term Planning;306 18.9;9.9 Diagrams/Icons: Impact Estimation;308 18.9.1;Presentation of IE Tables;308 18.9.2;Software Tools Supporting IE;309 18.10;9.10 Summary;312 19;10 Evolutionary Project Management: How to Manage Project Benefits and Costs;314 19.1;10.1 Introduction to Evolutionary Project Management;316 19.1.1;Practical Experience with Evolutionary Project Management;316 19.1.2;Underlying Principles of Evolutionary Project Management;317 19.2;10.2 Practical Example: Evolutionary Project Management;319 19.2.1;The Naval Radar System;319 19.3;10.3 Language Core: Evolutionary Step Specification;321 19.3.1;Step Content;321 19.3.2;Step Name;322 19.3.3;Step Dependency;322 19.3.4;Step Sequencing;322 19.3.5;Specification using Planguage;323 19.4;10.4 Rules: Evolutionary Project Management;325 19.4.1;Tags;325 19.4.2;Detail;325 19.4.3;Cost;325 19.4.4;Time;325 19.4.5;Priority;325 19.4.6;Next;326 19.4.7;Impact;326 19.4.8;Learn;326 19.4.9;Completeness;326 19.5;10.5 Process Description: Evolutionary Project Management;327 19.5.1;Process: Strategic Management Cycle (The Head);327 19.5.1.1;Entry Conditions: Entry.SM;327 19.5.1.2;Procedure: Procedure.SM;327 19.5.1.3;Exit Conditions: Exit.SM;328 19.5.2;Process: Delivery Cycle (Part of The Body);329 19.5.2.1;Entry Conditions: Entry.DC [Step n];329 19.5.2.2;Procedure: Procedure.DC [Step n];330 19.5.2.3;Exit Conditions: Exit.DC [Step n];331 19.6;10.6 Principles: Evolutionary Project Management;333 19.7;10.7 Additional Ideas: Evolutionary Project Management;334 19.7.1;Backroom/Frontroom;334 19.7.2;Using IE Tables for Evo Plans;334 19.7.3;Using Templates for Specifying Evo Steps;336 19.8;10.8 Further Example/Case Study: The German Telecommunications Company;337 19.9;10.9 Diagrams/Icons: Evolutionary Project Management;339 19.10;10.10 Summary: Evolutionary Project Management;341 20;Planguage Concept Glossary;344 20.1;Glossary Introduction;344 20.1.1;Purpose of the Glos
sary;344 20.1.2;Development of this Glossary;344 20.1.3;Development of Concepts;345 20.1.4;The Glossary as a Reader-Extendible Tool;345 20.1.5;About the Glossary Concepts;346 20.2;Glossary;347 21;Further Reading;468 22;Indices;472 22.1;Concept Index;472 22.2;Author Index;484 22.3;Subject Index;488