Software Engineering Classifications: Difference between revisions
imported>Stéphane Richard No edit summary |
imported>Meg Taylor No edit summary |
||
| (5 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{TOC | {{subpages}} | ||
Software engineering | {{TOC|right}} | ||
Software engineering, over the last five decades, has grown into a vast body of knowledge. Certain organizations have made attempts at classifying all this knowledge by breaking down the knowledge into categories and sub categories in order to make each section of knowledge more manageable. The body of software engineering knowledge became such that a means of classifying this vast knowledge became abundantly clear and warranted. | |||
In essence, there are three better known efforts, efforts that seem to be accepted throughout the software engineering domain. What follows is an explanation of these three groups of classification as well as links there were more details can be obtained. | |||
== The Software Engineering 2004 (SE2004) Classification == | == The Software Engineering 2004 (SE2004) Classification == | ||
The '''Software Engineering 2004 Classification (SE2004)''' is a classification created by the IEEE Computer Society and the Association for Computing Machinery (ACM) that presents what the software engineer courses should cover. These are not necessarily followed by all teaching institutions as institutions are at liberty to include different aspects of software engineering subjects to their curriculum. The SE2004 effort is there to give universities the complete list of subject matter that is considered as good knowledge to have for a software engineering undergraduate program. Depending on the program schedule institutions may or may not include all that is specified in the SE2004 but are very likely to have subjects that are in the SE2004 classification. | The '''Software Engineering 2004 Classification (SE2004)''' is a classification created by the IEEE Computer Society and the Association for Computing Machinery (ACM) that presents what the software engineer courses should cover. These are not necessarily followed by all teaching institutions as institutions are at liberty to include different aspects of software engineering subjects to their curriculum. The SE2004 effort is there to give universities the complete list of subject matter that is considered as good knowledge to have for a software engineering undergraduate program. Depending on the program schedule institutions may or may not include all that is specified in the SE2004 but are very likely to have subjects that are in the SE2004 classification. | ||
===External links:=== | |||
*[http://sites.computer.org/ccse/ The Software Engineering 2004 website] | |||
* [http://sites.computer.org/ccse/ The Software Engineering 2004 | *[http://www.informatik.uni-trier.de/~ley/db/conf/iastedSE/se2004.html Software Engineering 2004 - Informatik] | ||
* [http:// | |||
== Software Engineering Body of Knowledge (SWEBOK) Classification == | |||
The '''SWEBOK Classification System''' was created again by the IEEE Computer Society with the collaborate of many organizations. It is an effort to give a structure, a taxonomy if you will, the everything that is the body of Software Engineering knowledge. The main purpose is to help organize and recognize software engineering as a engineering field in itself. It's worth noting that everything that makes it into the SWEBOK hierarchy is the result of a acceptance effort (a vote if you will) and as such some software engineering philosophies and practices may not make it in this reference. | The '''SWEBOK Classification System''' was created again by the IEEE Computer Society with the collaborate of many organizations. It is an effort to give a structure, a taxonomy if you will, the everything that is the body of Software Engineering knowledge. The main purpose is to help organize and recognize software engineering as a engineering field in itself. It's worth noting that everything that makes it into the SWEBOK hierarchy is the result of a acceptance effort (a vote if you will) and as such some software engineering philosophies and practices may not make it in this reference. | ||
===External links:=== | |||
*[http://www.swebok.org/ The S.W.E.B.O.K. website] | |||
* [http://www.swebok.org/ The S.W.E.B.O.K. | *[http://www.inf.ed.ac.uk/teaching/courses/seoc/2006_2007/resources/SWEBOK_Guide_2004.pdf Guide to the Software Engineering Body of Knowledge (2004)] | ||
* [http:// | |||
== The A.C.M. Classification System == | == The A.C.M. Classification System == | ||
The '''ACM Classification System''' is probably the oldest of the classification system and was created by the Association for Computing Machinery. This hierarchy attempts to classify everything about computers not just software engineering (which you can find in the D. section of the main hierarchy). | |||
===External links:=== | |||
*[http://www.acm.org/class/1998 The A.C.M. Computing Classification System website] | |||
*[http://www.jucs.org/jucs_info/acm_categories A.C.M. Computing Classification System] | |||
* [http://www.acm.org/class/1998 The A.C.M. Computing Classification System | |||
* [http:// | |||
{{reflist}} | |||
Latest revision as of 19:17, 25 October 2013
Software engineering, over the last five decades, has grown into a vast body of knowledge. Certain organizations have made attempts at classifying all this knowledge by breaking down the knowledge into categories and sub categories in order to make each section of knowledge more manageable. The body of software engineering knowledge became such that a means of classifying this vast knowledge became abundantly clear and warranted.
In essence, there are three better known efforts, efforts that seem to be accepted throughout the software engineering domain. What follows is an explanation of these three groups of classification as well as links there were more details can be obtained.
The Software Engineering 2004 (SE2004) Classification
The Software Engineering 2004 Classification (SE2004) is a classification created by the IEEE Computer Society and the Association for Computing Machinery (ACM) that presents what the software engineer courses should cover. These are not necessarily followed by all teaching institutions as institutions are at liberty to include different aspects of software engineering subjects to their curriculum. The SE2004 effort is there to give universities the complete list of subject matter that is considered as good knowledge to have for a software engineering undergraduate program. Depending on the program schedule institutions may or may not include all that is specified in the SE2004 but are very likely to have subjects that are in the SE2004 classification.
External links:
Software Engineering Body of Knowledge (SWEBOK) Classification
The SWEBOK Classification System was created again by the IEEE Computer Society with the collaborate of many organizations. It is an effort to give a structure, a taxonomy if you will, the everything that is the body of Software Engineering knowledge. The main purpose is to help organize and recognize software engineering as a engineering field in itself. It's worth noting that everything that makes it into the SWEBOK hierarchy is the result of a acceptance effort (a vote if you will) and as such some software engineering philosophies and practices may not make it in this reference.
External links:
The A.C.M. Classification System
The ACM Classification System is probably the oldest of the classification system and was created by the Association for Computing Machinery. This hierarchy attempts to classify everything about computers not just software engineering (which you can find in the D. section of the main hierarchy).