Difference between revisions of "Body of Knowledge (glossary)"
Kguillemette (talk | contribs) m |
Kguillemette (talk | contribs) m (→Source) |
||
| Line 6: | Line 6: | ||
===Source=== | ===Source=== | ||
| − | (1) Abran, A. and J.W. Moore (exec. eds); P. Bourque and R. Dupuis (eds.). 2004. Guide to the Software Engineering Body of Knowledge (SWEBOK). Piscataway, NJ, USA: The Institute of Electrical and Electronic Engineers, Inc. (IEEE). Available at: http://www.computer.org/portal/web/swebok. | + | (1) Abran, A. and J.W. Moore (exec. eds); P. Bourque and R. Dupuis (eds.). 2004. [[Guide to the Software Engineering Body of Knowledge (SWEBOK)|Guide to the Software Engineering Body of Knowledge (SWEBOK Guide)]]. Piscataway, NJ, USA: The Institute of Electrical and Electronic Engineers, Inc. (IEEE). Available at: http://www.computer.org/portal/web/swebok. |
(2) PMI. 2013. ''[[A Guide to the Project Management Body of Knowledge|A Guide to the Project Management Body of Knowledge (PMBOK® Guide)]]''. 5th ed. Newtown Square, PA, USA: Project Management Institute (PMI). | (2) PMI. 2013. ''[[A Guide to the Project Management Body of Knowledge|A Guide to the Project Management Body of Knowledge (PMBOK® Guide)]]''. 5th ed. Newtown Square, PA, USA: Project Management Institute (PMI). | ||
Revision as of 19:59, 22 May 2014
(1) 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. (Abran and Moore 2004)
(2) Identifies that subset of the project management body of knowledge generally recognized as good practice. “Generally recognized” means the knowledge and practices described are applicable to most projects most of the time, and there is consensus about their value and usefulness. “Good practice” means there is general agreement that the application of these skills, tools, and techniques can enhance the chances of success over a wide range of projects...The PMBOK® Guide also provides and promotes a common vocabulary within the project management profession…The Project Management Institute views this standard as a foundational project management reference for its professional development programs and certifications. (PMI 2013)
(3) Document explicitly intended to capture the knowledge for entry into the practice of [an] engineering [discipline] at the professional level. (ASCE 2008)
Source
(1) Abran, A. and J.W. Moore (exec. eds); P. Bourque and R. Dupuis (eds.). 2004. Guide to the Software Engineering Body of Knowledge (SWEBOK Guide). Piscataway, NJ, USA: The Institute of Electrical and Electronic Engineers, Inc. (IEEE). Available at: http://www.computer.org/portal/web/swebok.
(2) PMI. 2013. A Guide to the Project Management Body of Knowledge (PMBOK® Guide). 5th ed. Newtown Square, PA, USA: Project Management Institute (PMI).
(3) ASCE. 2008. Civil Engineering Body of Knowledge for the 21st Century: Preparing the Civil Engineer for the Future, 2nd ed. Reston, VA, USA: American Society of Civil Engineers.
Discussion
None.
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