Systems Engineering Management
The systems engineering management (sem) knowledge area contains information associated with managing the resources and assets allocated to perform systems engineering, often in the context of a project or a service, but sometimes in the context of a less well-defined activity. SEM is distinguished from general project management by the focus of the former on the technical or engineering aspects of a project. It also includes exploratory research and development (R&D) activities at the enterprise level in commercial or government operations.
To download a PDF of all of Part 3 (including this knowledge area), please click here.
The topics contained within this knowledge area include:
- Assessment and Control
- Risk Management
- Decision Management
- Configuration Management
- Information Management
- Quality Management
Implementing systems engineering requires the coordination of technical and managerial endeavors. Success with the technical aspects is not possible in the absence of the managerial aspects. Management provides the planning, organizational structure, collaborative environment, and program controls to ensure that stakeholder needs are met.
The Venn diagram below provides context for the material in the SEM knowledge area. It indicates that some functions are managed more or less exclusively within the systems engineering (se) function, while others are managed in collaboration with the management of systems implementation and with overall project and systems management.
With respect to collaborative management specifics, there is no one-size-fits-all way to define the details of where various SEM functions are performed. An in-company SE organization will not run its own accounting system, but will rely on the corporate management organization for this aspect of SEM. A company performing only SE will include the accounting functions as part of its SEM.
In all cases, the managers of the SE function must be actively involved in the management of all the activities within the SE system boundary, including working out what collaborative arrangements best fit their situation. They must also remain aware of management events in their environment outside the system boundary that may affect their ability to perform.
Part 6 of the SEBoK includes relevant knowledge areas for this collaboration, including Systems Engineering and Software Engineering, Systems Engineering and Project Management, Systems Engineering and Industrial Engineering, Systems Engineering and Procurement/Acquisition, and Systems Engineering and Specialty Engineering.
This article relies heavily on limited resources. Reviewers are asked to provide additional resources in their reviews.
Blanchard, B. S. 2004. Systems Engineering Management. 3rd ed. New York, NY, USA: John Wiley & Sons Inc.
Sage, A. P, and W. Rouse. 2009. Handbook of Systems Engineering and Management. 2nd Ed. Hoboken, NJ, USA: John Wiley and Sons.
No additional references have been identified for version 0.75. Please provide any recommendations or references in your review.
Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.
If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.blog comments powered by Disqus