| |
| |
| Foreword | |
| |
| |
| Preface | |
| |
| |
| Acknowledgments | |
| |
| |
| |
| Engineering Design | |
| |
| |
| |
| Where and when do engineers design? | |
| |
| |
| |
| A vocabulary primer for engineering design | |
| |
| |
| |
| More on design and engineering design | |
| |
| |
| |
| On the evolution of design and engineering design | |
| |
| |
| |
| Managing engineering design | |
| |
| |
| |
| Notes | |
| |
| |
| |
| Exercises | |
| |
| |
| |
| The Design Process | |
| |
| |
| |
| The design process as a process of questioning | |
| |
| |
| |
| Describing and prescribing the design process | |
| |
| |
| |
| Strategies, methods, and means in the design process | |
| |
| |
| |
| Getting started on managing the design process | |
| |
| |
| |
| Case study and illustrative examples | |
| |
| |
| |
| Notes | |
| |
| |
| |
| Exercises | |
| |
| |
| |
| Defining the Client's Design Problem | |
| |
| |
| |
| Identifying and representing the client's objectives | |
| |
| |
| |
| On measuring things | |
| |
| |
| |
| Setting priorities: Rank ordering the client's objectives | |
| |
| |
| |
| Demonstrating success: Measuring the achievement of objectives | |
| |
| |
| |
| Constraints: Setting limits on what the client can have | |
| |
| |
| |
| Designing an arm support for a CP-afflicted student | |
| |
| |
| |
| Notes | |
| |
| |
| |
| Exercises | |
| |
| |
| |
| Functions and Requirements | |
| |
| |
| |
| Identifying functions | |
| |
| |
| |
| Design requirements: Specifying functions, behavior and attributes | |
| |
| |
| |
| Functions for the Danbury arm support | |
| |
| |
| |
| Managing the requirements stage | |
| |
| |
| |
| Notes | |
| |
| |
| |
| Exercises | |
| |
| |
| |
| Generating and Evaluating Design Alternatives | |
| |
| |
| |
| Using a morphological chart to generate a design space | |
| |
| |
| |
| Expanding and pruning the design space | |
| |
| |
| |
| Applying metrics to objectives: Selecting the preferred design | |
| |
| |
| |
| Generating and evaluating designs for the Danbury arm support | |
| |
| |
| |
| Managing the generation and selection of design alternatives | |
| |
| |
| |
| Notes | |
| |
| |
| |
| Exercises | |
| |
| |
| |
| Design Modeling, Analysis and Optimization | |
| |
| |
| |
| Some mathematical habits of thought for design modeling | |
| |
| |
| |
| Design modeling of a ladder rung | |
| |
| |
| |
| Preliminary and detailed design of a ladder rung | |
| |
| |
| |
| Notes | |
| |
| |
| |
| Exercises | |
| |
| |
| |
| Communicating the Design Outcome (I): Building Models and Prototypes | |
| |
| |
| |
| Prototypes, models, and proofs of concept | |
| |
| |
| |
| Building models and prototypes | |
| |
| |
| |
| Selecting a fastener | |
| |
| |
| |
| Notes | |
| |
| |
| |
| Exercises | |
| |
| |
| |
| Communicating the Design Outcome (II): Engineering Drawings | |
| |
| |
| |
| Engineering design drawings speak to many audiences | |
| |
| |
| |
| Geometric dimensioning and tolerancing | |
| |
| |
| |
| Notes | |
| |
| |
| |
| Exercises | |
| |
| |
| |
| Communicating the Design Outcome (III): Oral and Written Reports | |
| |
| |
| |
| General guidelines for technical communication | |
| |
| |
| |
| Oral presentations: Telling a crowd what's been done | |
| |
| |
| |
| The project report: Writing for the client, not for history | |
| |
| |
| |
| Final report elements for the Danbury arm support project | |
| |
| |
| |
| Managing the project endgame | |
| |
| |
| |
| Notes | |
| |
| |
| |
| Exercises | |
| |
| |
| |
| Leading and Managing the Design Process | |
| |
| |
| |
| Getting started: Organizing the design process | |
| |
| |
| |
| Managing design activities | |
| |
| |
| |
| An overview of project management tools | |
| |
| |
| |
| The team charter: What exactly have we gotten ourselves into? | |
| |
| |
| |
| Work breakdown structures: What must be done to finish the job | |
| |
| |
| |
| Linear responsibility charts: Keeping track of who's doing what | |
| |
| |
| |
| Schedules and other time management tools: Keeping track of time | |
| |
| |
| |
| Budgets: Follow the money | |
| |
| |
| |
| Tools for monitoring and controlling: Measuring our progress | |
| |
| |
| |
| Managing the Danbury arm support project | |
| |
| |
| |
| Notes | |
| |
| |
| |
| Exercises | |
| |
| |
| |
| Designing for . . | |
| |
| |
| |
| Designing for manufacture and assembly: Can we make this design? | |
| |
| |
| |
| Designing for cost: Can we afford this design? | |
| |
| |
| |
| Designing for reliability: How long will this design work? | |
| |
| |
| |
| Designing for sustainability: What about the environment? | |
| |
| |
| |
| Designing for quality: Building a House of Quality | |
| |
| |
| |
| Notes | |
| |
| |
| |
| Exercises | |
| |
| |
| |
| Ethics in Design | |
| |
| |
| |
| Ethics: Understanding obligations | |
| |
| |
| |
| Codes of Ethics: What are our professional obligations? | |
| |
| |
| |
| Obligations may start with the client . . . | |
| |
| |
| |
| . . . but what about the public and the profession? | |
| |
| |
| |
| Engineering ethics and the welfare of the public | |
| |
| |
| |
| Ethics: Always a Part of engineering practice | |
| |
| |
| |
| Notes | |
| |
| |
| |
| Exercises | |
| |
| |
| References and Bibliography | |
| |
| |
| Index | |