Cover

Table of Contents

Cover

Title page

Copyright page

ABOUT THE AUTHOR

PREFACE

PART I: OVERVIEW

1 SYSTEMS, PROJECTS, AND MANAGEMENT

1.1 INTRODUCTION

1.2 SYSTEMS AND PROJECTS

1.3 PROBLEMS IN MANAGING ENGINEERING PROJECTS

1.4 THE SYSTEMS APPROACH

1.5 THE PROJECT ORGANIZATION

1.6 ORGANIZATIONAL ENVIRONMENTS AND FACTORS

1.7 LARGE-SCALE ORGANIZATION AND MANAGEMENT ISSUES

QUESTIONS/EXERCISES

2 OVERVIEW OF ESSENTIALS

2.1 INTRODUCTION

2.2 PROJECT MANAGEMENT ESSENTIALS

2.3 SYSTEMS ENGINEERING PROCESS AND MANAGEMENT ESSENTIALS

2.4 HISTORICAL OVERVIEW OF ACQUISITION NOTIONS

2.5 SELECTED STANDARDS

QUESTIONS/EXERCISES

PART II: PROJECT MANAGEMENT

3 THE PROJECT PLAN

3.1 INTRODUCTION

3.2 NEEDS, GOALS, OBJECTIVES, AND REQUIREMENTS

3.3 TASK STATEMENTS, STATEMENT OF WORK (SOW), AND WORK BREAKDOWN STRUCTURE (WBS)

3.4 TECHNICAL APPROACH

3.5 SCHEDULE

3.6 ORGANIZATION, STAFFING, AND TASK RESPONSIBILITY MATRIX (TRM)

3.7 BUDGET

3.8 RISK ANALYSIS

3.9 THE PROPOSAL

3.10 SEMP AND SEP

QUESTIONS/EXERCISES

4 SCHEDULE, COST, AND SITUATION ANALYSIS

4.1 INTRODUCTION

4.2 SCHEDULE ANALYSIS AND MONITORING

4.3 COST ANALYSIS AND MONITORING

4.4 SITUATION ANALYSIS (SA)

QUESTIONS/EXERCISES

5 THE PROJECT MANAGER AND LEADERSHIP

5.1 INTRODUCTION

5.2 PROJECT MANAGER ATTRIBUTES

5.3 SELF-EVALUATION

5.4 INTERACTIONS WITH YOUR SUPERVISOR

5.5 CUSTOMER INTERACTION

5.6 LEADERSHIP

QUESTIONS/EXERCISES

6 TEAM BUILDING AND TEAM INTERACTIONS

6.1 INTRODUCTION

6.2 COMMUNICATIONS

6.3 BUILDING THE PROJECT TEAM

6.4 TEAM BUSTERS

6.5 CONFLICT MANAGEMENT

6.6 MEETINGS

6.7 PRESENTATIONS

6.8 PROPOSALS

6.9 A NOTE ON MOTIVATION AND INCENTIVES

6.10 ANOTHER TEAM-RELATED PERSPECTIVE

6.11 GROUP PROCESSES

QUESTIONS/EXERCISES

PART III: SYSTEMS ENGINEERING AND MANAGEMENT

7 THE THIRTY ELEMENTS OF SYSTEMS ENGINEERING

7.1 OVERVIEW OF THE SYSTEMS APPROACH AND ENGINEERING PROCESS

7.2 TWO SYSTEMS ENGINEERING PERSPECTIVES

7.3 THE THIRTY ELEMENTS OF SYSTEMS ENGINEERING

7.4 THE IMPORTANCE OF DOMAIN KNOWLEDGE IN SYSTEMS ENGINEERING

QUESTIONS/EXERCISES

8 REQUIREMENTS ANALYSIS AND ALLOCATION

8.1 INTRODUCTION

8.2 DEPARTMENT OF DEFENSE (DOD) PERSPECTIVES

8.3 A NATIONAL AERONAUTICS AND SPACE ADMINISTRATION (NASA) PERSPECTIVE

8.4 THE ORGANIZATION OF REQUIREMENTS STATEMENTS

8.5 SPECIFIC REQUIREMENTS STATEMENTS

8.6 ESSENTIAL STEPS OF REQUIREMENTS ANALYSIS

8.7 DERIVED AND ALLOCATED REQUIREMENTS

8.8 OTHER REQUIREMENTS ISSUES

QUESTIONS/EXERCISES

9 SYSTEMS ARCHITECTING: PRINCIPLES

9.1 INTRODUCTION

9.2 A VIEW OF SYSTEMS ARCHITECTING

9.3 A NATIONAL AERONAUTICS AND SPACE ADMINISTRATION (NASA) PERSPECTIVE

9.4 ARCHITECTURE DESCRIPTIONS

9.5 ESSENTIAL STEPS OF SYSTEM ARCHITECTING

9.6 THE 95% SOLUTION

9.7 TRADE-OFFS AND SENSITIVITY ANALYSES

9.8 MODELING AND SIMULATION

9.9 OTHER ARCHITECTURES AND TOOLS

9.10 SUMMARY

QUESTIONS/EXERCISES

10 SOFTWARE ENGINEERING

10.1 INTRODUCTION

10.2 STANDARDS

SOFTWARE MANAGEMENT STRATEGIES

10.4 CAPABILITY MATURITY

10.5 METRICS

10.6 THE SYSTEMS ENGINEER AND SOFTWARE ENGINEERING

10.7 SUMMARY

QUESTIONS/EXERCISES

11 SELECTED QUANTITATIVE RELATIONSHIPS

11.1 INTRODUCTION

11.2 BASIC PROBABILITY RELATIONSHIPS

11.3 THE BINOMIAL DISTRIBUTION

11.4 THE POISSON DISTRIBUTION

11.5 THE NORMAL (GAUSSIAN) DISTRIBUTION

11.6 THE UNIFORM DISTRIBUTION

11.7 THE EXPONENTIAL DISTRIBUTION

11.8 THE RAYLEIGH DISTRIBUTION

11.9 ERROR ANALYSES

11.10 RADAR SIGNAL DETECTION

11.11 SYSTEM RELIABILITY

11.12 SOFTWARE RELIABILITY

11.13 AVAILABILITY

11.14 A LEAST SQUARES FIT

11.15 SUMMARY

QUESTIONS/EXERCISES

PART IV: TRENDS, PERSPECTIVES, AND INTEGRATIVE MANAGEMENT

12 SYSTEMS/SOFTWARE ENGINEERING AND PROJECT MANAGEMENT TRENDS

12.1 INTRODUCTION

12.2 SYSTEMS ENGINEERING TRENDS

12.3 SOFTWARE ENGINEERING TRENDS

12.4 PROJECT MANAGEMENT TRENDS

QUESTIONS EXERCISES

13 SELECTED NEW PERSPECTIVES

13.1 INTRODUCTION

13.2 ROLE OF INCOSE

13.3 ACQUISITION OF SYSTEMS

13.4 PROBLEMS IN SYSTEMS AND SOFTWARE

13.5 INTEGRATION OF SYSTEMS

QUESTIONS/EXERCISES

14 INTEGRATIVE MANAGEMENT

14.1 INTRODUCTION

14.2 MANAGERS AS INTEGRATORS

14.3 TEAMS AS INTEGRATORS

14.4 PLANS AS INTEGRATORS

14.5 THE SYSTEMS APPROACH AS INTEGRATOR

14.6 METHODS AND STANDARDS AS INTEGRATORS

14.7 INFORMATION SYSTEMS AS INTEGRATORS

14.8 ENTERPRISES AS INTEGRATORS

14.9 THINKING OUTSIDE THE BOX

14.10 SUMMARY

QUESTIONS/EXERCISES

APPENDIX: SYSTEMS ARCHITECTING—CASES

A.1 INTRODUCTION

A.2 A LOGISTICS SUPPORT SYSTEM (CASE 1)

A.3 A SOFTWARE DEFECTS ASSESSMENT SYSTEM (CASE 2)

A.4 A SYSTEMS ENGINEERING ENVIRONMENT (CASE 3)

A.5 AN ANEMOMETRY SYSTEM (CASE 4)

A.6 SUMMARY

Index

Title page

This book is printed on acid-free paper.copyrightpage001

Copyright © 2008 by John Wiley & Sons, Inc. All rights reserved.

Published by John Wiley & Sons, Inc., Hoboken, New Jersey.

Published simultaneously in Canada. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning, or otherwise, except as permitted under Section 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600, or on the web at www.copyright.com. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030, (201) 748-6011, fax (201) 748-6008, or online at www.wiley.com/go/permissions.

Limit of Liability/Disclaimer of Warranty: While the publisher and the author have used their best efforts in preparing this book, they make no representations or warranties with respect to the accuracy or completeness of the contents of this book and specifically disclaim any implied warranties of merchantability or fitness for a particular purpose. No warranty may be created or extended by sales representatives or written sales materials. The advice and strategies contained herein may not be suitable for your situation. You should consult with a professional where appropriate. Neither the publisher nor the author shall be liable for any loss of profit or any other commercial damages, including but not limited to special, incidental, consequential, or other damages.

For general information about our other products and services, please contact our Customer Care Department within the United States at (800) 762-2974, outside the United States at (317) 572-3993 or fax (317) 572-4002.

Wiley also publishes its books in a variety of electronic formats. Some content that appears in print may not be available in electronic books. For more information about Wiley products, visit our web site at www.wiley.com.

Library of Congress Cataloging-in-Publication Data:

Eisner, Howard, 1935–

Essentials of project and systems engineering management / Howard Eisner. – 3rd ed.

p. cm.

Includes bibliographical references and index.

ISBN 978-0-470-12933-3 (cloth)

ISBN: 978-1-118-27644-0 (epdf)

ISBN: 978-1-118-27634-1 (epub)

ISBN: 978-1-118-27646-4 (mobi)

1. Systems engineering–Management. 2. Project management. I. Title.

TA168.E38 2008

658.406–dc22

2007050287

ABOUT THE AUTHOR

Since 1989, Howard Eisner has served as Distinguished Research Professor and Professor in the Engineering Management and Systems Engineering Department at The George Washington University in Washington, DC. For the prior thirty years, he held various technical and management positions in industry, including president of two systems and software engineering companies (Intercon Systems Corporation and the Atlantic Research Services Company). He also served as a board member of three high-tech companies. He is a Life Fellow of the Institute of Electrical and Electronics Engineers (IEEE) and a Fellow of the International Council on Systems Engineering (INCOSE) and a member of several engineering honor societies. Dr. Eisner has written two books on systems engineering and related topics. He has also written a book on personal and corporate reengineering and one on ways of thinking about and managing large complex systems. He holds a BEE from the City College of New York, an MS from Columbia University, and a Doctor of Science from The George Washington University.

PREFACE

This book has two primary objectives: (1) to define and describe the essentials of project and systems engineering management, and (2) to show the relationship and interconnection between project management and systems engineering.

The subject of project management is well-trodden territory and is explored at considerable length in numerous books. Systems engineering, though, is not as well known, as measured perhaps by the literature that describes and supports it. However, this literature has clearly been on the upswing as the need for systems engineering has been increasing and expanding. Like project management, systems engineering deals with a variety of methods for designing and building a system that are largely independent of the domain itself. Slowly, but noticeably, systems engineering is finding its way into a greater number of college curricula and taking its place alongside the more traditional engineering disciplines, such as electrical engineering, mechanical engineering, chemical engineering, and the like.

More often than not, systems engineering is carried out in the real world in the context of a project. In a typical scenario, a company might set up a project whose basic purpose is to design and build some type of system. Thus, there is almost always a strong connection between project management and systems engineering, whether it is formally recognized or not. Many students have asked about this sometimes murky connection during my courses in systems engineering. They want to know more about how systems engineering fits into the structure of a project and its various management-oriented tasks and activities. These questions, directly and indirectly, have led to this book. Indeed, this may be the first book that attempts to bring these two important subjects together.

This third edition provides new and expanded materials, including these subject areas:

As compared with the second edition, this edition adds a chapter (a new chapter 13) so that it has a total of 14 chapters and an appendix. This makes it suitable for a 15-week course in project and systems engineering management. At the same time, Systems Engineers and Project Managers in an industrial environment, or with a government agency, will find the essentials of what they need to know under one cover.

I am pleased to dedicate this book at both a professional and a personal level. With respect to the former, I dedicate it to my graduate students and colleagues in the engineering management and systems engineering department in the School of Engineering and Applied Science, The George Washington University. At a personal level, I dedicate the book to my wife, June Linowitz, whose patience, support, and love helped make it possible.

HOWARD EISNER

Bethesda, Maryland