Difference between revisions of "Related Disciplines"
Line 16: | Line 16: | ||
None. | None. | ||
===Primary References=== | ===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. | ||
+ | |||
===Additional References=== | ===Additional References=== | ||
No additional references have been identified for version 0.5. Please provide any recommendations on additional references in your review. | No additional references have been identified for version 0.5. Please provide any recommendations on additional references in your review. |
Revision as of 13:43, 2 September 2011
Note to public reviewers: The Part 6 knowledge areas are less mature than other KAs in SEBoK v0.5. Answers to the following questions will be helpful, in addition to your review comments concerning content, references, and glossary terms:
1. Are there other knowledge areas that should be added, in addition to Systems Engineering and Software Engineering; Systems Engineering and Project Management; Systems Engineering and Procurement/Acquisition; and Specialty Disciplines?
2. Are there missing specialty disciplines that should be added?
Knowledge Areas
- Systems Engineering and Software Engineering
- Systems Engineering and Project Management
- Systems Engineering and Procurement/Acquisition
- Specialty Disciplines
References
Citations
None.
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.
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:06, 22 August 2011 (UTC) (on behalf of Dick Fairley)