Difference between revisions of "Systems Engineering and Software Engineering"
| Line 78: | Line 78: | ||
===Additional References=== | ===Additional References=== | ||
| − | + | No additional references have been identified for version 0.5. Please provide any recommendations on additional references in your review. | |
| − | |||
| − | |||
---- | ---- | ||
====Article Discussion==== | ====Article Discussion==== | ||
Revision as of 13:26, 2 September 2011
Software is usually prominent in modern systems architectures and is often the glue for integrating complex system components. Software engineering and systems engineering are not merely related disciplines; they are intimately intertwined; see Intertwined Disciplines and the SEBoK.
The SEBoK explicitly recognizes and embraces the intertwining between SE and SwE, which includes defining 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). [external link: http://www.swebok.org]
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 those concepts and use common terminology in similar and different ways.
Topics
The Systems Engineering and Software Engineering knowledge area contains the following topics:
- The Nature of Software
- An Overview of the SWEBOK Guide
- Software Engineering and Systems Engineering: Similarities and Differences
An Overview of the SWEBOK Guide
The Preface to the 2004 version of the Guide to the Software Engineering Body of Knowledge states external link: http://www.swebok.org]:
The purpose of the Guide to the Software Engineering Body of Knowledge is to provide a consensually validated characterization of the bounds of the software engineering discipline and to provide a topical access to the Body of Knowledge supporting that discipline.
Version 3 of the SWEBOK Guide is being developed and will be completed in late 2011 or early 2012. Version 3 of the SWEBOK Guide contains 15 knowledge areas:
- Software Requirements
- Software Design
- Software Construction
- Software Testing
- Software Engineering Methods
- Software Maintenance
- Software Configuration Management
- Software Quality
- Software Engineering Process
- Software Engineering Management
- Software Professional Practice
- Software Economics
- Computing Foundations
- Mathematical Foundations
- Engineering Foundations
The description of each knowledge area includes an introduction, a descriptive breakdown of topics and sub-topics, recommended references, references for further reading, and a list of standards most relevant to the knowledge area.
The following table indicates the correspondences between SWEBOK knowledge areas and SEBoK knowledge areas. The similarities and differences are described below [{Systems Engineering and Software Engineering: Similarities and Differences}].
Table 1. Correspondences between SWEBOK and SEBoK Knowledge Areas
NOTE: Table 1 To be completed
The SWEBOK Guide also contains a chapter on related disciplines, which include:
- Computer Engineering
- Business Management
- Project Management
- Quality Management
- Systems Engineering
The related disciplines are those that share a boundary, and often a common intersection, with software engineering. The SWEBOK Guide does not characterize the knowledge of the related disciplines but rather indicates how those disciplines interact with the software engineering discipline.
References
Citations
Brooks, Fred. 1995. The Mythical Man-Month, Anniversary Edition. Boston, Massachusetts: Addison Weslley Longman Inc.
Fairley, Richard E. 2009. Managing and Leading Software Projects. Hoboken, New Jersey: John Wiley and Sons.
Abran et al. 2004. Guide to the Software Engineering Body of Knowledge (SWEBOK. Piscataway, New Jersey: The Institute of Electrical and Electronic Engineers, Inc.
Primary References
Abran et al. 2004. SWEBOK: Guide to the Software Engineering Body of Knowledge. Piscataway, New Jersey: The Institute of Electrical and Electronic Engineers, Inc.
Brooks, Fred. 1995. The Mythical Man-Month, Anniversary Edition. Boston, Massachusetts: Addison Weslley Longman Inc.
Fairley, Richard E. 2009. Managing and Leading Software Projects. Hoboken, New Jersey: John Wiley and Sons.
Additional References
No additional references have been identified for version 0.5. Please provide any recommendations on additional references in your review.
Article Discussion
Signatures
--Bkcase 19:07, 22 August 2011 (UTC) (on behalf of Dick Fairley)