Competitive Engineering A Handbook For Systems Engineering Requirements Engineering and Software Engineering Using Planguage 1st Edition by Tom Gilb 0750665076 9780750665070

Competitive Engineering A Handbook For Systems Engineering Requirements Engineering and Software Engineering Using Planguage 1st Edition by Tom Gilb – Ebook PDF Instant Download/Delivery: 0750665076, 9780750665070

Full download Competitive Engineering A Handbook For Systems Engineering Requirements Engineering and Software Engineering Using Planguage 1st Edition after payment

Product details:

ISBN 10: 0750665076

ISBN 13: 9780750665070

Author: Tom Gilb

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

Table of contents:

1. Planguage Basics and Process Control: The Purpose of Planguage
1.1 Introduction: Why We Need a Different ‘Systems Engineering’ Approach
Learning through Rapid Feedback
Dynamic Adaptability
Capturing the Requirements
Focus on Results
Interdisciplinary Communication
Leadership and Motivation
Receptiveness to Organizational Change
Continuous Process Improvement
Practical Strategies for Systems Engineering

1.2 Practical Example: Twelve Tough Questions
1.3 Language Core: Planguage Basics and Process Control
Planguage Specification Language
A Set of Defined Concepts
A Set of Defined Parameters and Grammar
A Set of Icons
Planguage Process Descriptions
Requirement Specification (RS)
Design Engineering (DE)
Specification Quality Control (SQC)
Impact Estimation (IE)
Evolutionary Project Management (EVO, also known as Evo)
Standards
Rules
Process Descriptions
Entry Conditions
Procedure
Exit Conditions

1.4 Rules: Generic Rules for Technical and Management Specification
1.5 Process Description: Generic Project
Entry Conditions
Procedure
Exit Conditions
Generic Entry and Exit Process and Conditions
Process: Generic Entry or Generic Exit
Procedure

1.6 Principles: Generic Project
1.7 Additional Ideas
Continuous Process Improvement

1.8 Further Example/Case Study: Continuous Process Improvement at Raytheon
Background
Aim
Financing the Improvements
Measuring the Effects
Calculating Savings

1.9 Diagrams/Icons
Some Basic Planguage Icons
Document or Specification
Plan-Do-Study-Act Process Cycle

1.10 Summary: Planguage Basics and Process Control

2. Introduction to Requirements: Why?
2.1 Introduction to Requirements Specification
Definition of Requirements
Key Issues for Requirements
Identifying the critical stakeholders
Separating Ends and Means
Identifying the key requirements
Quantifying success and failure
Understanding the past and the future – benchmarks and state-of-the-art
Considering the timescales for delivery of requirements
Avoiding the ‘ambiguity trap’
Handling complex requirements
Allowing requirements to evolve

2.2 Practical Example: What is ‘Flexibility Improvement’?
Analyzing a requirement
Decomposition of Requirements
Scalar Requirements

2.3 Language Core: System Attributes and Requirement Specification Types
System Attributes
System
Attribute
Function
Performance
Resource
Design
Requirement Types
Vision
Basic Requirement Types
Function Requirement: what a system has to ‘do.’
Performance Requirement
Quality Requirement
Resource Saving Requirement
Workload Capacity Requirement
Resource Requirement
Design Constraint
Condition Constraint

2.4 Rules: Requirement Specification
2.5 Process Description: Requirement Specification
Process: Requirement Specification
Entry Conditions
Procedure
Exit Conditions

2.6 Principles: Requirement Specification
2.7 Additional Ideas
Using Qualifiers to Specify Conditions
Qualifier Definition
Qualifiers and System Space/Scope
The Difference between Qualifier Conditions and Condition Constraints
Qualifiers and Evo Steps
Additional Ideas Concerning Constraints
Adherence to Constraints
Constraint Viewpoints

2.8 Further Example/Case Study: A Proposal to the Board for $60 Million
2.9 Diagrams/Icons: Requirement Specification
2.10 Summary: Requirement Specification

3. Functions: What systems ‘do’
3.1 Introduction: Function and Function Requirement Specification
Separation of Functions from Design Ideas
Function Requirements

3.2 Practical Example: Function Analysis
Stakeholders
Functions

3.3 Language Core: Function and Function Requirement Specification
Referencing Functions
Specifying an Arbitrary Set of Functions
Inheritance of Higher Level Requirements
Function Specification
Function Description
Functional Relationships
Sub-functions
Supra-functions
Sibling functions
Defining Supra-functions (as a set of functions)
Referencing Supra-functions for a Function
Defining Sibling Functions
Attributes of a Function
Qualifiers

3.4 Rules: Function and Function Requirement Specification
Functionality
Detail
Not Degrees
Not Design
Function Priority
Testable
Test

3.5 Process Description: Function Requirement Specification
Process: Function Requirements
Entry Conditions
Procedure
Exit Conditions

3.6 Principles: Function and Function Requirement Specifications
3.7 Additional Ideas: Function and Function Requirement Specification
Mission
Elementary and complex concepts
Measuring Functionality
Additional Examples of Function Specification

3.8 Further Example/Case Study: Function Specification for an Airborne Command and Control System
3.9 Diagrams/Icons: Function and Function Requirement Specification
3.10 Summary: Function and Function Requirement Specification

4. Performance: How Good?
4.1 Introduction
Performance: Quality, Resource Savings and Workload Capacity
Quality
Resource Savings
Workload Capacity

4.2 Practical Example: Performance Requirements
Step 1
Step 2
Step 3

4.3 Language Core: Scalar Attributes
Ambition
Scale
Meter
Benchmarks
Targets
Goal
Budget
Stretch
Wish
Constraints
Fail
Survival
Conditions

4.4 Rules: Scalar Requirements
Completeness
Explode
Scale
Meter
Benchmark
Requirement
Goal or Budget
Stretch
Wish
Fail
Survival

4.5 Process Description: Performance Requirements
Process: Performance Requirements
Entry Conditions
Procedure
Exit Conditions

4.6 Principles: Performance Requirements
4.7 Additional Ideas: Performance Requirements
Handling Complex Performance Requirements
Limit the Amount of Detail
Setting Scalar Levels
Implicit Assumptions Supporting a Scalar Parameter Level

4.8 Further Example/Case Study: Performance Specification for a Water Supply
4.9 Diagrams/Icons: Scalar Attribute Requirements
4.10 Summary: Performance Requirements

5. Scales of Measure: How to Quantify
5.1 Introduction
Finding and Developing Scales of Measure and Meters
Reference Library for Scales of Measure
Reference Library for Meters
Managing ‘What’ You Measure

5.2 Practical Example: Scale Definition
Level of Specification Detail

5.3 Language Core: Scale Definition
Specifying Scales
The Central Role of a Scale within Scalar Attribute Definition
Specifying Scales using Qualifiers
Embedded Qualifiers within a Scale
Additional Qualifiers

5.4 Rules: Scale Definition
Standard
Notify Owner
Scale Definition
Elementary Attribute
Differentiate
Uncertainty
Scalar Priority

5.5 Process Description: Scale Definition
Process: Scale Definition
Entry Conditions
Procedure
Exit Conditions

5.6 Principles: Scale Definition
5.7 Additional Ideas: Generic Hierarchies for Scalar Attributes
Hierarchy of Performance
Performance
Quality
Availability
Reliability
Maintainability
Integrity
Adaptability
Flexibility
Upgradeability
Usability
Entry Level Experience
Training Requirement
Handling Ability
Likeability
Demonstrability
Resource Savings
Financial Saving
Time Saving
Effort Saving
Equipment Saving
Workload Capacity
Throughput
Response Time
Storage Capacity

5.8 Further Example/Case Study: Scale Definition
5.9 Diagrams/Icons: Scale Definition
5.10 Summary: Scales of Measure

6. Resources, Budgets and Costs: Costs of Solutions
6.1 Introduction
Relationships amongst Resources, Budgets and Costs
Stakeholder Requirements and Resources
The Relationship between Costs and Performance Delivery
Look at the Use of Resources across the Entire System Lifetime
Numeric Performance Levels Enable Us to Understand the Associated Costs Better
The Cost of Perfection – Beware Infinite Cost Increases
Specify Costs Down to a More Detailed Level – Not Just Total Costs!
Accurate Estimation of Costs in Advance is Unlikely for Complex Systems
Use Design to Cost and Evolutionary Project Management (Evo)

6.2 Practical Example: Resources, Budgets and Costs
Resource Requirement Specifications: Allocation of Resources

6.3 Language Core: Resources, Budgets and Costs
6.4 Rules: Resource Requirement Specification
6.5 Process Description: Resource Requirement Specification
Process: Resource Requirement Specification
Entry Conditions
Procedure
Exit Conditions

6.6 Principles: Resource Requirements
6.7 Additional Ideas
Using Impact Estimation and Evolutionary Processes to Balance Requirements

6.8 Real Example: Resource Target and Resource Constraint Specification
6.9 Diagrams/Icons: Resource Requirement Specification
Resource Requirement Icons
Resource Requirement Specification Template

6.10 Summary: Resource Requirement Specification

7. Design Ideas and Design Engineering: How to Solve the ‘Requirements Problem’
7.1 Introduction
To Design and to Engineer
Requirement Specification, Design Engineering and Evo are all Iterative Processes
Requirements Dictate and Constrain the Design, but Detailed Requirement Specification can Wait
Any Design Idea can be Considered
Design Ideas can be Identified during Requirement Specification
Potential Design Ideas
Design Constraints
The Need for Alternative Design Ideas
Choosing the Best from the Alternatives
Choosing the Best Combined Set from all the Alternatives
Reducing Risk by Use of Alternative Design
Design Optimization
Cost Minimization
Design to Cost
Design to Performance Targets within Cost
Design for Risk
Brief Recap of Planguage Methods and the Design Engineering Process
Requirement Specification
Impact Estimation (IE)
Evolutionary Project Management

7.2 Practical Example: Beginning the Design Engineering Process
7.3 Language Core: Design Idea Specification
7.4 Rules: Design Specification
Design Separation
Detail
Explode
Dependencies
Impacts
Side Effects
Background Information
IE table
Constraints
Rejected Designs

7.5 Process Description: The Design Engineering Process
Process: Design Engineering Process
Entry Conditions
Procedure
Analyze the Requirements
Establish the Stakeholder Value on Delivery of each Requirement
Sequence the Delivery Order of the Requirements
Establish Scope of Design Interest
Make a List of Requirements within the Scope defined
Find and Specify Design Ideas
Exploit any Earlier Notes of Design Ideas
Establish the Design Constraints
Brainstorm Design Ideas
Draft Design Ideas
Collect Specification Detail (to support later Impact Estimation)
Consider Design Implementation
Consider System Capacity and Growth
Evaluate Design Ideas
Filter for Violation of any Constraint
Estimate all Impacts
Consider Side Effects
Consider Safety Margins
Select Design Ideas and Produce Evo Plan
Initial Sequencing of Design Ideas
Ensure adequate Safety Margins to address Risks
Consider Design Ideas with regard to the Risks
Consider Optimization
Re-define Design Definitions
Consider Pilot and/or Trial
Exit Conditions

7.6 Principles: The Design Engineering Process
7.7 Additional Ideas
Priority Determination
What is wrong with the Subjective Weighting Approach for Determining Priority?
The Role of Resource in Determining Priority
Planguage Information Supports Priority Determination
Priority Strategy
Dynamic Priority Evaluation

7.8 Further Example/Case Study: Design Specifications Masquerading as Requirements
7.9 Diagrams/Icons: The Design Engineering Process
7.10 Summary: The Design Engineering Process

8. Specification Quality Control: How to Know How Well You Specified
8.1 Introduction: Specification Quality Control
Improving Process
Saving Time
Increasing Productivity
Industrial Usage

8.2 Practical Example: Specification Quality Control
8.3 Language Core: Specification Quality Control
Basic Definitions (see also Glossary terms)
Specification Quality Control (SQC)
Defect Detection Process
Defect Prevention Process
Issue
Defect
Major defect
Page
Checking Rate
Optimum Checking Rate
Remaining Major Defects
Checklist
Rule
Main Specification
Source Documents
Kin Documents

8.4 Standards: Specification Quality Control
Guidelines for assessing functioning of overall SQC
Economic
SQC Champion
Team Leaders
Statistics
Meetings
Checkers
Checking Rate
Condition
Standards
Upstream Pollution
Forms
SQC Process Roles and Responsibilities
Team Leader
Checker
Writer: Also Known as Author
Editor
Scribe
Others

8.5 Process Description: Specification Quality Control
Process: Specification Quality Control
Entry Conditions
SQC Sub-Processes
Entry
Planning
SQC Strategy
Kickoff
Checking
Specification Meeting
Checkers’ Report
Issue Logging
Double Checking
Process Meeting
Edit
Edit Audit
SQC Statistics
Exit
Exit Conditions
A Simplified SQC Process

8.6 Principles: Specification Quality Control
8.7 Additional Ideas: Specification Quality Control
Economics of using SQC
Effectiveness of SQC
Determining Effectiveness and Estimating Remaining Defects
SQC and Rules
Extending from SQC into Specification Review

8.8 Further Example/Case Study: A Stitch in Time Saves Nine
Use of SQC on many different types of document
The Organization Must be Supportive and SQC Needs a Champion

8.9 Diagrams/Icons: Specification Quality Control
8.10 Summary: Specification Quality Control
Finding Defects
Understanding Document Quality
Continuous Process Improvement

9. Impact Estimation: How to Understand Strategies
9.1 Introduction to Impact Estimation
9.2 A Simple Practical Example of Impact Estimation
9.3 Language Core: Impact Estimation

9.4 Rules/Forms/Standards: Impact Estimation
Table Format
Requirement
Qualifiers
Design Idea
Scale Impact
Percentage Impact
Uncertainty
Evidence
Credibility
Completeness
Calculations
Credibility-Adjusted Calculations

9.5 Process Description/Standards: Impact Estimation
Process: Impact Estimation
Entry Conditions
Procedure
Exit Conditions

9.6 Principles: Impact Estimation
9.7 Additional Ideas: Impact Estimation
Understanding Mathematical Inaccuracy
Level of Detail
Coping with Interactions amongst Design Ideas
Considering Side Effects
Dealing with Alternatives
Dealing with Dependencies
Priority Management within IE
Can We Always Use the Stated Requirements to Determine Priority?
Managing Risk: Building in Safety Margins
Highlighting System Failure and System Survival Levels

9.8 Further Example/Case Study: IE Table for US Army Personnel System Long Term Planning
9.9 Diagrams/Icons: Impact Estimation
Presentation of IE Tables
Software Tools Supporting IE

9.10 Summary

10. Evolutionary Project Management: How to Manage Project Benefits and Costs
10.1 Introduction to Evolutionary Project Management
Practical Experience with Evolutionary Project Management
Underlying Principles of Evolutionary Project Management

10.2 Practical Example: Evolutionary Project Management
The Naval Radar System

10.3 Language Core: Evolutionary Step Specification
Step Content
Step Name
Step Dependency
Step Sequencing
Specification using Planguage

10.4 Rules: Evolutionary Project Management
Tags
Detail
Cost
Time
Priority
Next
Impact
Learn
Completeness

10.5 Process Description: Evolutionary Project Management
Process: Strategic Management Cycle (‘The Head’)
Entry Conditions: Entry.SM
Procedure: Procedure.SM
Exit Conditions: Exit.SM
Process: Delivery Cycle (Part of ‘The Body’)
Entry Conditions: Entry.DC [Step n]
Procedure: Procedure.DC [Step n]
Exit Conditions: Exit.DC [Step n]

10.6 Principles: Evolutionary Project Management
10.7 Additional Ideas: Evolutionary Project Management
Backroom/Frontroom
Using IE Tables for Evo Plans
Using Templates for Specifying Evo Steps

10.8 Further Example/Case Study: The German Telecommunications Company
10.9 Diagrams/Icons: Evolutionary Project Management
10.10 Summary: Evolutionary Project Management

Planguage Concept Glossary
Glossary Introduction
Purpose of the Glossary
Development of this Glossary
Development of Concepts
The Glossary as a Reader-Extendible Tool
About the Glossary Concepts
Glossary
Further Reading
Indices
Concept Index

People also search:

tom gilb competitive engineering

competitive engineering gilb

a competitive inc

competitive engineering

gilb competitive engineering

Tags: Tom Gilb, Competitive, Engineering, Systems, Requirements