Difference between revisions of "Systems Engineering and Software Engineering"
Wikiexpert (talk | contribs) m (Removed protection from "Systems Engineering and Software Engineering") |
|||
| Line 1: | Line 1: | ||
| − | Software is usually prominent in modern systems architectures and is often the | + | Software is usually prominent in modern systems architectures and is often the primary means for integrating complex system components. Software engineering and systems engineering are not merely related disciplines; they are intimately intertwined (see [[Systems Engineering and Other Disciplines]]). |
The [[Acronyms|SEBoK]] explicitly recognizes and embraces the intertwining between systems engineering and software engineering, and defines the relationship between the SEBoK and the [http://www.swebok.org Guide to The Software Engineering Body of Knowledge] (SWEBOK), which is published by the IEEE (Abran et al. 2004). | The [[Acronyms|SEBoK]] explicitly recognizes and embraces the intertwining between systems engineering and software engineering, and defines the relationship between the SEBoK and the [http://www.swebok.org Guide to The Software Engineering Body of Knowledge] (SWEBOK), which is published by the IEEE (Abran et al. 2004). | ||
Revision as of 18:21, 21 May 2012
Software is usually prominent in modern systems architectures and is often the primary means for integrating complex system components. Software engineering and systems engineering are not merely related disciplines; they are intimately intertwined (see Systems Engineering and Other Disciplines).
The SEBoK explicitly recognizes and embraces the intertwining between systems engineering and software engineering, and defines the relationship between the SEBoK and the Guide to The Software Engineering Body of Knowledge (SWEBOK), which is published by the IEEE (Abran et al. 2004).
This knowledge area describes the nature of software, provides an overview of the 2004 SWEBOK Guide, describes the concepts that are shared by systems engineers and software engineers, and indicates the similarities and difference in how software engineers and systems engineers apply these concepts and use common terminology.
To download a PDF of all of Part 6 (including this knowledge area), please click here.
Topics
The Systems Engineering and Software Engineering knowledge area contains the following topics:
- The Nature of Software
- An Overview of the SWEBOK Guide
- Ten Things a Systems Engineer Needs to Know about Software Engineering
- Ten Things a Systems Engineer Needs to Know about Managing a Software Team
References
Works Cited
Abran, A. and J.W. Moore (exec. eds); P. Borque and R. Dupuis (eds.). 2004. SWEBOK: Guide to the Software Engineering Body of Knowledge. Piscataway, NJ, USA: The Institute of Electrical and Electronic Engineers, Inc. (IEEE). Available at: http://www.computer.org/portal/web/swebok
Brooks, F. 1995. The Mythical Man-Month, Anniversary Edition. Boston, MA, USA: Addison Weslley Longman Inc.
Fairley, R.E. 2009. Managing and Leading Software Projects. Hoboken, NJ, USA: John Wiley and Sons.
Primary References
Abran, A. and J.W. Moore (exec. eds); P. Borque and R. Dupuis (eds.). 2004. SWEBOK: Guide to the Software Engineering Body of Knowledge. Piscataway, NJ, USA: The Institute of Electrical and Electronic Engineers, Inc. (IEEE). Available at: http://www.computer.org/portal/web/swebok
Brooks, F. 1995. The Mythical Man-Month, Anniversary Edition. Boston, MA, USA: Addison Wesley Longman Inc.
Fairley, R.E. 2009. Managing and Leading Software Projects. Hoboken, NJ, USA: John Wiley and Sons.
Additional References
Pressman, Roger. 2009. Software Engineering: A Practitioner's Approach. 7th Ed. New York, NY, USA: McGraw Hill.
Sommerville, Ian. 2010. Software Engineering. 9th Ed. Boston, MA, USA: Addison Wesley.