RequirementsOntology
In the development of the basic version the following partners participated:
Dirk Fritsch, Jens Lehmann, Kim Lauenroth, Steffen Lohmann, Thomas Riechert
The figure visualises the core of the RE ontology, which we developed in ac-
cordance with [2,3,4,5]. Central to our approach are the classes Stakeholder and
Abstract Requirement as well as the properties details and defines. Abstract re-
quirements have the subclasses Goal, Scenario, and Requirement, each of which
are defined by stakeholders and can be detailed by other abstract requirements.
This enables the specification of abstract requirements at different levels of gran-
ularity. We emphasise the collaborative aspects of requirements engineering by
integrating discussions amongst the stakeholders and voting (with the criteria of
agreement and importance) in the model. In the RE process this documentation
is often relevant for future decisions.
[1] Soren Auer, Klaus-Peter Fähnrich, and Thomas Riechert.
SoftWiki – Agiles Requirements-Engineering fur Softwareprojekte mit einer großen Anzahl verteilter
Stakeholder. In GeNeMe’ 06 – Gemeinschaft in neuen Medien, 2006.
[2] Peter Haumer, Klaus Pohl, and Klaus Weidenhaupt. Requirements elicitation and
validation with real world scenes. IEEE Transactions on Software Engineering,
24(12):1036–1054, December 1998.
[3] Klaus Pohl. Process-centered requirements engineering. Research Studies Press,
Advanced Software Development, 1996.
[4] Klaus Pohl: 
Requirements Engineering. Grundlagen, Prinzipien, Techniken. Dpunkt Verlag,2007.5. Axel van Lamsweerde.
[5] Goal-oriented requirements engineering: A guided tour. In
Fifth IEEE International Symposium on Requirements Engineering (RE’01), pages
249–263. IEEE Computer Society Press, August 2001
