Atnaujinkite slapukų nuostatas

El. knyga: Systems Engineering: Fifty Lessons Learned [Taylor & Francis e-book]

(Professor Emeritus, The George Washington University)
  • Formatas: 120 pages, 5 Tables, black and white; 5 Line drawings, black and white; 5 Illustrations, black and white
  • Serija: CRC Press Focus Shortform Book Program
  • Išleidimo metai: 14-Jul-2020
  • Leidėjas: CRC Press
  • ISBN-13: 9781003002505
  • Taylor & Francis e-book
  • Kaina: 84,93 €*
  • * this price gives unlimited concurrent access for unlimited time
  • Standartinė kaina: 121,33 €
  • Sutaupote 30%
  • Formatas: 120 pages, 5 Tables, black and white; 5 Line drawings, black and white; 5 Illustrations, black and white
  • Serija: CRC Press Focus Shortform Book Program
  • Išleidimo metai: 14-Jul-2020
  • Leidėjas: CRC Press
  • ISBN-13: 9781003002505
"This Focus book provides a "looking back" at author's 50-year run and the lessons he learned and would like to share with other engineers, so they can use these lessons in their day-to-day work in systems engineering and related fields. The book is written from a systems engineering perspective. It offers 50 lessons learned while the author worked for a variety of different companies, which can be used across many other engineering fields"--

The author has spent approximately 50 years in the field of systems engineering. This Focus book provides a "looking back" at his 50-year run and the lessons he learned and would like to share with other engineers, so they can use these lessons in their day-to-day work in systems engineering and related fields.

The book is written from a systems engineering perspective. It offers 50 lessons learned working for a variety of different companies, which can be used across many other engineering fields.

The book will be of interested to students and engineers across many fields, as well as students and engineers working in business and management fields.

Preface xiii
About the Author xv
Other Books by the Author xvii
1 Technical
1(20)
1 When and Where Possible, Go Back to Fundamentals (*)
1(2)
Case One
1(1)
Case Two
2(1)
Case Three
2(1)
2 Seriously Explore Alternatives, Even If Time Is Short
3(2)
References and Recommended Reading
5(1)
3 Embrace Prototyping as Well as Modeling and Simulation (M & S)
5(2)
References and Recommended Reading
7(1)
4 Cost-Effectiveness Is Still the Preferred Approach
7(3)
Typical MOEs for Communication Systems
8(1)
Selected MOEs for Transportation Systems
8(1)
Limited MOEs for Air Defense Systems
9(1)
Weighting Factors
9(1)
References and Recommended Reading
9(1)
5 Do Not Attempt to Integrate All Stovepipes
10(2)
Reference and Recommended Reading
11(1)
6 A Bit at a Time or All at Once
12(1)
References and Recommended Reading
13(1)
7 Growth by Acquisition
13(3)
8 The Contract
16(1)
9 Less Paper Please
17(4)
References and Recommended Reading
19(2)
2 Management
21(18)
10 Definitely Measure, but Do Not Over-Measure
21(3)
Software Measurement
21(1)
Overall Project Measurement
22(1)
Significant Parameters
22(1)
COCOMO I and COCOMO II
23(1)
References and Recommended Reading
23(1)
11 Under Promise and Over Deliver
24(1)
Reference and Recommended Reading
25(1)
12 Try to Improve Overall Systems Engineering Practices
25(2)
References and Recommended Reading
27(1)
13 Negotiate
27(2)
References and Recommended Reading
28(1)
14 Understanding the Enterprise
29(1)
Monthly Measurements
29(1)
The Balanced Scorecard
30(1)
References and Recommended Reading
30(1)
15 The Systems Approach
30(3)
Systems Thinking
31(1)
References and Recommended Reading
32(1)
16 Industry/Government Interaction
33(1)
Universities
33(1)
INCOSE Certification
34(1)
17 Tradeoffs
34(3)
Risk
35(1)
Detection and False Alarm Probabilities
35(2)
18 Resilience
37(2)
References and Recommended Reading
38(1)
3 Idea Based
39(28)
19 They Were Right: KISS, Simplify, and Reduce Complexity
39(2)
References and Recommended Reading
41(1)
20 Seek a Balanced System Solution; Do Not Try to Optimize or Achieve Perfection (*)
41(4)
Other References to Balance
42(2)
Stakeholders
44(1)
References and Recommended Reading
44(1)
21 Understand the Power, Importance, and Challenge of Functional Decomposition
45(2)
References and Recommended Reading
47(1)
22 Break the Problem into Pieces Using the Reductionist Approach Whenever Possible, and Then Apply Lateral Thinking
47(3)
References and Recommended Reading
49(1)
23 Develop and Try a New Way of Architecting
50(2)
The DoD Procedure for Developing Architecture
50(1)
Products for Views
51(1)
An Alternative Approach
51(1)
References and Recommended Reading
52(1)
24 Plato and Proust
52(2)
Reference and Recommended Reading
54(1)
25 Try to Master New Tools and Use Them as Needed
54(2)
References and Recommended Reading
56(1)
26 Real EAM
56(3)
References and Recommended Reading
58(1)
27 Ways of Thinking
59(4)
Visualization
59(1)
Lateral Thinking
59(1)
Hybrid Thinking
60(1)
Six Thinking Hats
60(1)
Special Point-of-View Thinking
61(1)
References and Recommended Reading
62(1)
28 New Ideas to Be Explored
63(4)
General Systems Theory
63(1)
Rapid Computer-Aided Systems of Systems
63(1)
New Method of Systems Architecting
64(1)
National Aviation System (NAS) Model
64(1)
Systems Engineering and Software Engineering
64(1)
Emergent Properties of Systems
64(1)
Affordability
64(1)
Design to Cost
64(1)
References and Recommended Reading
65(2)
4 People Oriented
67(24)
29 Building a Highly Productive Systems Engineering Team
67(2)
The Team Leader
67(1)
Project Management and Leadership
68(1)
References and Recommended Reading
68(1)
30 Listen to Your Elders
69(2)
References and Recommended Reading
71(1)
31 Leadership
71(2)
Practical Visionary
72(1)
Inclusive Communicator
72(1)
Positive Doer
72(1)
Renewing Facilitator
72(1)
Principled Integrator
72(1)
Reference and Recommended Reading
73(1)
32 New Boss
73(1)
Reference and Recommended Reading
74(1)
33 Team Busters
74(2)
34 Meetings
76(3)
A Systems Engineering Meeting
78(1)
References and Recommended Reading
78(1)
35 Myers-Briggs
79(2)
Reference and Recommended Reading
80(1)
36 Becoming a Hi-Tech Manager
81(2)
Skills Required
81(1)
Specific Steps
82(1)
Reference and Recommended Reading
82(1)
37 Dealing with Your Customer
83(2)
Going to Lunch with Your Customer
83(1)
Issuance of a New Task Order
83(1)
Quick Response Capability
84(1)
A Truthful Interchange
84(1)
The Re-Competition
84(1)
38 Integration
85(1)
Reference and Recommended Reading
86(1)
39 Hall, Goode, and Machol
86(2)
A D. Hall
86(1)
Goode and Machol
87(1)
Machol's View
87(1)
References and Recommended Reading
88(1)
40 Man vs. Machine
88(3)
5 Miscellany
91(20)
41 Redundancy is Important and May Be Critical in Certain Systems
91(2)
Reference and Recommended Reading
93(1)
42 Rechtin's Heuristics Are Brilliant and Need to Be Studied and Followed
93(2)
References and Recommended Reading
94(1)
43 Mistakes
95(2)
A Footnote to the IBM - Microsoft Story
96(1)
References and Recommended Reading
96(1)
44 Cost Estimating
97(1)
References and Recommended Reading
98(1)
45 Generalize
98(1)
46 Risk Analysis and Mitigation
99(2)
Take Your Pick of Serial and Parallel Configurations
100(1)
References and Recommended Reading
101(1)
47 Change, Options Open, and Iteration
101(3)
Rechtin's Options Open
102(1)
Configuration Control and Management
102(1)
Iteration
103(1)
TBDs
103(1)
References and Recommended Reading
104(1)
48 DOTSS
104(1)
References and Recommended Reading
105(1)
49 Obversity
105(1)
50 Vaillant, Turned into Lessons Considered
106(5)
Grit
107(1)
Intelligence
107(1)
Listening
107(1)
Focus
107(1)
Integrity
107(1)
Community Involvement
108(1)
Problem Solver
108(1)
Respect
108(1)
Curiosity
108(1)
Sense of Humor
108(1)
Resilient
108(1)
Growth-Oriented
109(1)
References and Recommended Reading
109(2)
6 Top Ten Lessons
111(6)
1 Stovepipes
111(1)
2 Modeling and Simulation
111(1)
3 Architecting
112(1)
4 Amid a Wash of Paper
113(1)
5 Industry Initiatives and Government Support
113(1)
6 The Elders in Systems Engineering
114(1)
7 Functional Decomposition
114(1)
8 Team Building
115(1)
9 Risk Analysis and Mitigation
115(1)
10 The Systems Approach and Systems Thinking
116(1)
References and Recommended Reading
116(1)
Index 117
Howard Eisner spent 30 years in industry and 24 years in academia. In the former, he was a working engineer, manager, executive (at ORI, Inc. and the Atlantic Research Corporation) and president of two high-tech companies (Intercon Systems and the Atlantic Research Services Company). In academia he was a professor of engineering management and a distinguished research professor in the Engineering School at The George Washington University (GWU). At GWU he taught courses in systems engineering, technical enterprises, project management, modulation and noise and information theory.



He has written nine books that relate to engineering, systems, and management. He has also given lectures, tutorials and colloquia to professional societies (such as INCOSE International Council on Systems Engineering), government agencies (such as the DoD, NASA and the DOT) and other groups (such as the Osher Lifelong Learning Institute (OLLI)).

In 1994 he was given the outstanding achievement award from the GWU Engineering Alumni.

Dr. Eisner is a Life Fellow of the IEEE (Institute of Electrical and Electronics Engineers) and a fellow of INCOSE and the New York Academy of Sciences. He is a member of Tau Beta Pi, Eta Kappa Nu, Sigma Xi and Omega Rho, various research/honor societies. He received a Bachelors degree (BEE) from the City College of New York (1957), a Master of Science degree in Electrical Engineering from Columbia University (1958), and a Doctor of Science degree from The George Washington University (1966).

Since 2013, he has served as professor emeritus of engineering management and distinguished research professor at The George Washington University. As such, he has continued to explore advanced topics in engineering, systems, and management.