Difference between revisions of "Systems Engineering and Project Management"

From SEBoK
Jump to navigation Jump to search
Line 9: Line 9:
 
*[[Relationships between Systems Engineering and Project Management]]   
 
*[[Relationships between Systems Engineering and Project Management]]   
 
*[[The Influence of Project Structure and Governance on Systems Engineering and Project Management Relationships]]
 
*[[The Influence of Project Structure and Governance on Systems Engineering and Project Management Relationships]]
−
 
−
==The Nature of Project Management==
 
−
Project managers and systems engineers are both concerned with management issues such as planning, measuring and controlling, leading, directing, and managing risk.  In the case of project managers, the project attributes to be managed include project plans, estimates, schedule, budget, project structure, staffing, resources, infrastructure and risk factors.  Product attributes managed by systems engineers include items such as requirements allocation and flow-down, system architecture, structure of and interactions among technical teams, [[Systems Engineering and Specialty Engineering|specialty engineering]], [[integration (glossary)]], [[System Verification|verification]] and [[System Validation|validation]].  The exact allocation of the [[Acronyms|SE]] and [[Acronyms|PM]] duties depend on many factors such as customer and stakeholder interactions, organizational structure of the parent organization, and relationships with affiliate contractors and subcontractors.  See the article on [[The Influence of Project Structure and Governance on Systems Engineering and Project Management Relationships]] in this KA.
 
−
 
−
The activities of project management include the following (Fairley 2009; Forsberg et al 2005):
 
−
*Planning and Estimating
 
−
*Measuring and Controlling
 
−
*Leading and Directing
 
−
*Managing Risk
 
  
 
==References==  
 
==References==  

Revision as of 12:56, 30 August 2012

The goal of project management is to plan and coordinate the work activities needed to deliver a satisfactory product, service, or enterprise endeavor within the constraints of schedule, budget, resources, infrastructure, and available staffing and technology. The purpose of this knowledge area (KA) is to acquaint systems engineers with the elements of project management and to explain the relationships between systems engineering (SE) and project management (PM).

To download a PDF of all of Part 6 (including this knowledge area), please click here.

Topics

Each part of the SEBoK is divided into knowledge areas (KAs), which are groupings of information with a related theme. The KAs in turn are divided into topics. This KA contains the following topics:

References

Works Cited

Boehm, B., C. Abts., A.W. Brown, S. Chulani, B.K. Clark, E. Horowitz, R. Madachy, D. Reifer, and B. Steece. 2000. Software Cost Estimation with COCOMO II. Upper Saddle River, NJ, USA: Prentice Hall.

Fairley, R.E. 2009. Managing and Leading Software Projects. Hoboken, NJ, USA: John Wiley & Sons.

Forsberg, K., H. Mooz, and H. Cotterman. 2005. Visualizing Project Management. Hoboken, NJ, USA: John Wiley and Sons.

INCOSE. 2012. Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities, version 3.2.2. San Diego, CA, USA: International Council on Systems Engineering (INCOSE), INCOSE-TP-2003-002-03.2.2.

ISO/IEC/IEEE. 2009. Systems and Software Engineering - Life Cycle Processes - Project Management. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electronical Commission (IEC)/Institute of Electrical and Electronics Engineers (IEEE), ISO/IEC/IEEE 16326:2009(E).

NASA. 2007. Systems Engineering Handbook." Washington, DC,USA: National Aeronautics and Space Administration.

Valerdi, R. 2008.The Constructive Systems Engineering Cost Model (COSYSMO): Quantifying the Costs of Systems Engineering Effort. Saarbrucken, Germany: VDM Verlag.

Primary References

Fairley, R.E. 2009. Managing and Leading Software Projects. Hoboken, NJ, USA: John Wiley & Sons.

Forsberg, K., H. Mooz, and H. Cotterman. 2005. Visualizing Project Management. 3rd ed. New York, NY, USA: John Wiley & Sons.

PMI. 2008. A Guide to the Project Management Body of Knowledge, 4th ed. Newtown Square, PA, USA: Project Management Institute (PMI).

Additional References

Blanchard, B. 2008. System Engineering Management. Hoboken, NJ, USA: John Wiley & Sons.

Kerzner, Harold. 2003. Project Management: A Systems Approach to Planning, Scheduling, and Controlling. 8th Ed. Hoboken, NJ, USA: John Wiley & Sons.

Martin, J. 1997. Systems Engineering Guidebook: A Process for Developing Systems and Products. London, UK: Taylor and Francis Group CRC-Press, LLC.

< Previous Article | Parent Article | Next Article >
SEBoK v. 1.9.1 released 30 September 2018

SEBoK Discussion

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

Retrieved from "https://sandbox.sebokwiki.org/index.php?title=Systems_Engineering_and_Project_Management&oldid=41708"