Are there any systematic guidelines for that?
Is there any difference among the three terms?
Have you checked ISO standards? I would think that the ISO standards must have something on this.
To add to above answer, most of ISO and IEEE standards are now interlinked
Software Engineering Vocabulary
https://standards.ieee.org/findstds/standard/24765-2010.html
For example Software Architecture, this is the standards related link from IEEE
https://standards.ieee.org/findstds/standard/42010-2011.html
Benchmark is a standardized problem or test that serves as a basis for evaluation or comparison (e.g. computer system performance).
Taxonomy (or classification) is orderly presentation of some artifacts or properties in this case as related to software or hardware.
We use taxonomy to classify (present in an orderly manner) the objects of our interest
We use benchmark to compare (or evaluate) the objects of our interest
Andrew's provided you with clear definitions. Benchmarks depend on the area and they require that you have a term of comparison, and this can be a significant difficulty, requiring to gather data from several projects/organizations and eventually during several years. See for example: http://www.qsm.com/resources/qsm-database
About classifications, any classification is done based on some set of characteristics. Usually, this set is limited. I did propose a distinct approach here:
Also, I like to distinguish among classifications, but that is another issue.
Conference Paper Towards an Internal Numerical Taxonomy of Software Process A...
A taxonomy already exists, The Guide to the Software Engineering Body of Knowledge (SWEBOK Guide), available for free from the IEEE Computer Society.
Which are the characteristics of themes of the software engineering that you want to classify?
Emigdio, that's another question and the answer can be found inside the SWEBOK (see the answer above by James Moore). I only add that there is also a non free printed book about SWEBOK at amazon.
- Badges
- Science topic