Competitive Engineering: A Handbook For Systems Engineering, Requirements Engineering, and Software Engineering Using PlanguageCompetitive 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.
|
What people are saying - Write a review
We haven't found any reviews in the usual places.
Contents
1 | |
Why? | 35 |
What systems do | 81 |
How Good? | 109 |
How to Quantify | 137 |
Costs of Solutions | 165 |
How to Solve the Requirements Problem | 185 |
How to know how well you specified | 221 |
How to understand strategies | 261 |
How to Manage Project Benefits and Costs | 291 |
Planguage Concept Glossary | 321 |
Further Reading | 445 |
Indices | 449 |
Other editions - View all
Competitive Engineering: A Handbook for Systems Engineering, Requirements ... Tom Gilb No preview available - 2005 |
Common terms and phrases
architecture benchmark Budget Chapter checker complex components Condition Constraint Cost Ratio delivered delivery design constraints design ideas design specification Design to Cost detail documents Edwards Deming elementary Entry Conditions Eritrea evaluate Evo plan Evo step Evolutionary Project Management example Exit Conditions feedback Function Requirement Gilb Gist Glossary Hewlett-Packard identify IE table Impact Estimation implementation Keyed Icon major defects Marketing ments Meter Note parameter PDSA Percentage Impact performance and resource performance attributes performance requirements performance to cost Planguage practice priority process improvement Product qualifier conditions Quality Requirement quantified Rationale Related Concepts relevant remaining major requirement specification resource attributes Resource Requirement Resource Saving risk rules scalar attribute scalar requirement Scale Impact scale of measure scale qualifier Software Software Engineering Source Specification Quality Control SQC process stakeholders standards Survival Synonyms systems engineering systems engineering process term Tom Gilb Transcription Education Type User Version Workload Capacity
Popular passages
Page xiii - I often say that when you can measure what you are speaking about and express it in numbers, you know something about it; but when you cannot measure it, when you cannot express it in numbers, your knowledge is of a meager and unsatisfactory kind...
Page xiii - IN physical science a first essential step in the direction of learning any subject, is to find principles of numerical reckoning, and methods for practicably measuring, some quality connected with it.