Muutke küpsiste eelistusi

Getting Design Right: A Systems Approach [Kõva köide]

4.80/5 (8 hinnangut Goodreads-ist)
(Director, Systems Engineering Program and Professor, School of Operations Research and Information Engineering, Cornell UNiversity, New York, USA)
  • Formaat: Hardback, 392 pages, kõrgus x laius: 254x178 mm, kaal: 884 g, 154 Tables, black and white; 91 Illustrations, black and white
  • Ilmumisaeg: 22-Sep-2009
  • Kirjastus: CRC Press Inc
  • ISBN-10: 1439811156
  • ISBN-13: 9781439811153
Teised raamatud teemal:
  • Kõva köide
  • Hind: 75,59 €*
  • * hind on lõplik, st. muud allahindlused enam ei rakendu
  • Tavahind: 106,79 €
  • Säästad 29%
  • Raamatu kohalejõudmiseks kirjastusest kulub orienteeruvalt 2-4 nädalat
  • Kogus:
  • Lisa ostukorvi
  • Tasuta tarne
  • Tellimisaeg 2-4 nädalat
  • Lisa soovinimekirja
  • Raamatukogudele
Getting Design Right: A Systems ApproachSuurem pilt
  • Formaat: Hardback, 392 pages, kõrgus x laius: 254x178 mm, kaal: 884 g, 154 Tables, black and white; 91 Illustrations, black and white
  • Ilmumisaeg: 22-Sep-2009
  • Kirjastus: CRC Press Inc
  • ISBN-10: 1439811156
  • ISBN-13: 9781439811153
Teised raamatud teemal:
Teised raamatud sellest sooduspakkumisest: Taylor & Francis teadusraamatud International Student Editions hindadega
Püsilink: https://www.kriso.ee/db/9781439811153.html
Märksõnad:
This textbook integrates elements of design and systems engineering to provide a basis for understanding the fundamental principles and best practices on those subjects. The book's format initially defines a problem, determines technical requirements, and identifies customer value requirements. The book also covers design space, design choice optimization, and development of the architecture, including behavior, control, and structure. After design validation, the author provides an accessible treatment of resource-constrained scheduling as a computer puzzle. Author Jackson (School of Operations Research and Industrial Engineering, Cornell U.) also supplements chapters with discussion-provoking examples from industry. Annotation ©2009 Book News, Inc., Portland, OR (booknews.com)

Filling a new need in engineering education, Getting Design Right: A Systems Approach integrates aspects from both design and systems engineering to provide a solid understanding of the fundamental principles and best practices in these areas. Through examples, it encourages students to create an initial product design and project plan.

Classroom-tested and industry-reviewed, the text focuses on the steps of a basic design cycle. It first defines the problem, establishes technical requirements, and identifies the customer value proposition. The text then explores the design space, optimizes design choices, and develops the architecture, including behavior, control, and structure. After validating the design, the author presents an accessible treatment of resource-constrained scheduling as a computer puzzle. The final chapter covers the level-by-level decomposition of systems. In addition, the appendices offer useful design challenges for a bathroom-cleaning robot, a home health-care monitoring system, a night-vision system for automobiles, and an Internet-based meal delivery system.

Using a design approach based on simple text-based tools and spreadsheet software, this book presents a formal process for discovering requirements and tackling design problems. It will help mature audiences in professional settings as well as students with limited design and project experience.

List of Figures xvii
List of Tables xxi
1 Getting Design Right 1
What Do We Mean by "Design"?
1
Why "Getting Design Right"?
2
What Can Go Wrong?
2
What Is There to Learn?
4
Why a Systems Approach?
4
Design or Engineering?
5
For Whom Is This Text Designed?
6
What Is the Design Process?
6
Learn by Example
7
Learn by Doing
8
Is It Worth the Effort?
8
Why Use a Tabular Approach?
8
The Getting Design Right Web Site
10
Required Spreadsheet Skills
10
To the Instructor: Where This Text Fits
10
Discussion
12
References
12
2 Define the Problem 13
Introduction
13
Define the Project
14
Select the Project
14
Name the Problem
14
Sketch the Concept
17
Annotate the Product Sketch
19
Define and Tailor the Process
19
Identify the Owner, the Customer, and the User
20
Other Categories of Individuals Affected by the System
21
Write a Mission Statement
23
Define the Context
25
Define the System Boundary
25
Document the Context of the System
26
Context Diagrams
26
Context Matrices
27
Study the Current Context
28
Naturalist, Anthropologist, or Observer
28
Apprentice, Questioner, or Interpreter
29
Partner or Suggester
29
Pitfall of Contextual Inquiry
29
Collect Customer Comments
30
Summarize Project (Product) Objectives
31
Technique: Sticky Notes (Large Group Affinity Process)
31
The Affinity Process Using MS Excel
34
Results of the Affinity Process
34
Define Functional Requirements
35
Collect Use Cases
38
Prioritize Use Cases
40
Describe Use Case Behaviors
41
Summarize Functional Requirements from Use Cases
43
Repeat for Secondary Use Cases
47
Finalize Requirements
50
Summary
51
Discussion
51
Exercises
55
References
56
3 Measure the Need and Set Targets 59
Introduction
59
Measure the Need
59
Determine Measures of Effectiveness
62
The Goal—Question—Metric Method Applied to the Toy Catapult
63
Identify the Goals of the Measurement
63
Refine the Goals with Questions
64
Specify the Metrics
65
Develop Data Collection Methods
67
Repeat for Secondary Goals
72
Weight the Product Objectives
73
Illustration of the Analytic Hierarchy Process Using the Toy Catapult
75
Benchmark Competition on Measures of Effectiveness
79
Graphical Representation of Benchmarking Data
82
Translate to Technical Requirements
84
The House of Quality
85
Identify Engineering Characteristics
87
Map Engineering Characteristics to Customer Attributes
89
Document Engineering Interrelationships
91
Identify Units of Measure and Benchmark Competitors
92
Determine Target Technical Performance Measures
93
Collect and Rationalize System-Level Requirements
94
Identify the Customer Value Proposition
97
Guidelines for Writing a Customer Value Proposition
97
Summary
98
Discussions
99
Exercises
99
References
100
4 Explore the Design Space 103
Introduction
103
Discover Concepts
106
Clarify the Problem and Decompose the Functions
106
Brainstorm and Research
107
Organize Concept Fragments
111
Prune and Expand
112
Explore Concepts
114
Combine Concept Fragments
114
Generate Integrated Concepts
115
Identify Subsystems
122
Summary
127
Discussions
128
Exercises
128
References
129
5 Optimize Design Choices 131
Introduction
131
Select Concepts
133
Identify Alternatives
133
Identify Attributes
133
Screen the Alternatives
134
Rate Alternatives
137
Weight the Attributes
138
Score and Select Alternatives
138
Optimize Parameters
140
Define the Product Family
144
Summary
146
Appendix: The Physics of a Catapult Design (Advanced)
146
Discussions
149
Exercises
149
References
151
6 Develop the Architecture 153
Introduction
153
System Architecture and a Language for Systems
155
Design the Behavior
156
Review Use Cases, Context, and Functional Requirements
156
Map Behaviors to Subsystems
160
Identify Messages, Triggers, and Interfaces
164
Identify System States
164
Set Targets for Behavior
169
Extract Functional Requirements
169
Trace-Derived Requirements to Originating Requirements
178
The Centrality of the Operational Description Template
182
Design the Flow and Control
184
Identify Functional Relationships
184
Summarize State Changes
186
Design the Structure
191
Identify Interfaces and Finalize Subsystems
192
Document Links
192
Identify Emergent Interactions
194
Sketch a Design Concept
197
Create a Rough-Cut Bill of Materials
198
Create a Rough-Cut Reliability Estimate (Advanced Topic)
201
Allocate Target Technical Performance Measures to Subsystems
206
Allocation of Target Cost to Subsystems
206
Allocation of Target Reliability to Subsystems (Advanced Topic)
207
Dive and Surface in TPM Allocation
209
Summary
209
Discussions
211
Exercises
211
References
212
7 Validate the Design 213
Introduction
213
Verify Requirements
217
Conduct Design Reviews
217
Examples of Valid and Invalid Requirements
220
Develop the Test Plan
220
Identify Behavioral Test Sequences
221
Develop Behavioral Test Methodology
228
Repeat for Nonbehavioral Tests
230
Map Test Activities to System Requirements (VCRM)
235
Manage Risks
239
Conduct Failure Modes and Effects Analysis
240
Select Functions
240
Identify Failure Modes
241
Assess Potential Impact of Failure
241
Brainstorm Possible Causes
242
Suggest Corrective Actions
243
Rate the Severity of Impact
245
Rate the Likelihood of Causal Occurrence
245
Assess the Risk
252
Prioritize the Action
252
Summary
253
Discussion
253
Exercises
253
References
254
8 Execute the Design 255
Introduction
255
Schedule the Project and Track Progress
257
Develop the Task List (Work Breakdown Structure)
258
Estimate Durations
260
Track Percent Complete
262
Identify Task Inputs, Outputs, and Deliverables
264
Establish Task Precedence Relationships
268
Schedule the Project
271
Compute an Earliest Start Schedule (Advanced Topic)
275
Display a Gantt Chart
276
Adjust the Schedule for Team Availability
278
Conduct Management Reviews
286
Summary
288
Discussions
288
Exercises
288
References
289
9 Iterate the Design Process 291
Introduction
291
Iterate until Feasible
291
Backtracking Strategies
293
Iterate with Improvement
294
Iterate by Level
299
Level-by-Level Decomposition: The Vee Diagram
299
Detail Functions into Behaviors
300
Allocate Nonbehavioral Requirements: Linked Houses of Quality
301
Maintain Hierarchies and Traceabilities
302
Dive and Surface: A Systems View
303
Summary
310
What Is Next?
312
Discussions
312
References
312
Appendix A: Case Studies 313
Case Study: The Harley-Davidson Motor Company
313
Company Background
313
The Motorcycle Marketplace
313
Steps to Learning Customer Wishes
314
Encourage Employees to Become Active Motorcyclists
314
Attend Rallies on Company Time
314
Pay Close Attention to the Aftermarket
314
Demonstrate Products and Debrief Customers
314
Assimilate and Document
314
Market Strategy Result
315
Case Study: Formula SAE Racing Competition
316
Context and Background
316
The Cornell Formula SAE Record
316
Define the Problem
317
Mission Statement
318
Rule Analysis
318
Optimization
318
Benchmarking
318
Competitive Intelligence
318
Brainstorming
318
Corporate Memory
318
Examples of Derived Requirements
319
Requirements Traceability
319
Architecture
320
Management
321
Resources
321
Planning
321
Case Study Summary
321
References
322
Appendix B: Product and Service Development Challenges 323
Product Development Challenge: A Bathroom-Cleaning Robot
323
Preface
323
Product Concept and Market Review
323
Company Profile/Industry Background.
323
Market Opportunity
326
Market Conditions
326
Competitive Analysis
326
Customer Profile
327
Market Strategy
327
Marker Size
327
Sales Projections
328
Product Development Challenge: A Home-Health Monitoring and Trauma Alert System
328
Preface
328
Summary
328
Product Concept and Marker Review
329
Industry Background
329
Company Profile
329
Market Opportunity
330
Market Conditions
331
Competitive Analysis
331
Patient Profile
333
Market Strategy
333
Sales Projections
333
Product Development Challenge: A Night Vision System for Automobiles
333
Preface
333
Product Concept and Market Review
334
Industry Background and Company Profile
334
Market Opportunity
334
Market Conditions
335
Competitive Analysis
335
Customer Profile
336
Market Strategy
336
Market Size
337
Sales Projections
337
Service-Development Challenge: Internet-Based Meal Order and Delivery System
337
Preface
337
Product Concept and Market Review
337
Industry Background
337
Company Profile
338
Market Opportunity
338
Market Conditions
339
Competitive Analysis
339
Customer Profile
340
Market Strategy
341
Projections
341
References
342
Appendix C: Use Case Behaviors for Toy Catapult 343
Index 355
Peter L. Jackson is director of the Systems Engineering Program and professor in the School of Operations Research and Information Engineering at Cornell University.