Semantic Web Ontology for Requirements Engineering (SWORE) Jens Lehmann Kim Lauenroth Philipp Heim Sebastian Tramp Steffen Lohmann Thomas Riechert http://creativecommons.org/licenses/by/3.0/ 2007-03-12 2007-03-13 2007-10-24 2008-01-22 2008-02-29 2008-07-08 2009-01-15 2009-03-04 2009-07-09 2010-01-09 2010-06-28 2011-10-28 2011-11-02 2018-10-28 Semantic Web Ontology for Requirements Engineering (SWORE) version 2.01 - Customizations for documentation version 2.0 (the generic one) - 2011-11-02 - Thomas and Steffen: - subclasses of ReferencePoint removed - alignment to DOAP vocabulary - cardinalities on requirements class edited - CC license added - descriptions revised and edited version 1.9 - 2011-10-28 - Steffen Lohmann - changeLog: - MUTO instead of TAGS as tagging ontology - consistent German and Englisch labels - additional requirements relations - imports removed - further alignments: - req:Document to foaf:Document - sioc:User (deprecated) to sioc:UserAccount - DC to DCTERMS - used additional DCTERMS properties (dcterms:created, dcterms:modified, dcterms:references) - added global requirement properties (re:status, req:priority, req:quality) - equivalentClass instead of subproperty alignments (to avoid "ontology hijacking") - skos:Concept no longer subclass of req:referencePoint version 1.05 - for requirements management we added a general class ApplicationDecision version 1.04 - as a result of practical experiences the Abstract classes like AbstractRequirement, AbstractReferencePoint, AbstractSource are not necessary anymore; we renamed them version 1.03 - alignement to tag und dc improved; version 1.01 - Alignment to SIOC, FOAF and SKOS added version 1.00 - Thomas Riechert, Steffen Lohmann, Kim Lauenroth, Philipp Heim - starting the next generation of SWORE on 8th of July 2008 in Duisburg version 0.8 - Sebastian Dietzold - skos, tags and dc alignment (title now functional) version 0.7 - Sebastian Dietzold - labels completed and namespace correction version 0.6 - name space changed to ns.softwiki.de/req version 0.5 - refined by Thomas according to ESWC Poster submission version 0.4 - refined by Jens on the way home from Essen version 0.3 - refined by Jens during discussion with Kim and Steffen on 13 March 2007 in Essen version 0.2 - refined by Thomas and Jens in the evening of 12 March 2007 in Essen version 0.1 - simple initial version by Thomas and Jens before meeting in Essen http://ns.softwiki.de/req/2/img/sworeV2.png conficts steht im Konflikt zu beinhaltet contains Contributor trägt bei Indicates the req:Stakeholder that creates the resource of a req:Requirements. Creator hat erstellt depends on hängt ab von detailliert details angereichert durch enriched by entails hat zur Folge gehört zu Projekt has Project erklärt ungültig invalidates detailed by detailliert durch invalid for ungültig für is part of ist Teil von redundant to redundant zu benötigt requires similar to ähnlich wie Indicates the req:Stakeholder that made the latest contribution on a req:Requirements. Last Contributor hat zuletzt beigetragen Letzter Autor last author Deprecated - use lastContributor instead. references referenziert is related to steht in Beziehung zu benötigt requires has source hat Quelle Describes the priority of a req:Requirement. hat Priorität priority Describes the quality of a req:Requirement. hat Qualität quality Defines the state of a req:Requirement. hat Status status This class represents Documents that are source of a Requirement. Such documents may be standards, a law, manuals, screenshots etc.. req:Document is aligned to foaf:Document. Document Dokument Enrichments are any concepts that added value to an Requirement. This class is aligned to sioc:Item so mainly enrichments are sioc:Poll or sioc:Comment on a Requirement. n additional alignment is defined to MUTO vocabulary to support personal tagging. Anreicherung Enrichment This class represents references to existing systems, if they are sources for requirements. The URI of instances of this class can be the URL of an existing Web-Application. Bestehendes System Existing System Glossary terms are very important to understand the domain of a further project. They are derived from general tags extended by a description of the meaning of the tag. Glossarbegriff Glossary Term Stakeholder can define one rating about the priority for each requirement. Gewichtung Priority Rating The class req:Project describes general projects. It is aligned to doap:Project that is intended to describe open-source projects. Project Projekt Stakeholder can define one rating about the quality for each requirement. Quality Rating Qualitätsbewertung A reference point is a resource that is related to the req:Requirement. The resources range from domain specific topics, represented by skos:Concept, Tags (tags:Tag), req:GlossaryTerms. The class req:ReferencePoint is also very important to document the traces, e.g. from requirement to source code. Reference Point Referenzpunkt The concept of this class is a Requirement that is related to nearly any kind of project. Between instances of the class req:Requirement relations can be defined using the sub-properties of req:relation (e.g. req:contains, req:invalidates, req:dependsOn, etc.). Requirements are derived from Sources (req:Source) or its subclasses req:Document and req:Stakeholder. Stakholders can contribute (req:contributor) information to the Requirement and enchrich (req:enrichedBy) it by commenting, voting or personal tagging. Requirements are referenced by a domain specific topic (skos:Concept), using Tags (tags:Tag) or as usual in the requirements engineering domain by using Glossary Terms (req:GlossaryTerm). Anforderung Requirement The class req:Source represents the req:source of a requirement. There are two major subclasses of req:Source : req:Stakeholder and req:Document. Anforderungsquelle Source of the Requirement This class represents involved Stakeholders. Usually it will be not directly used as it is aligned to foaf:Agent and its subclasses foaf:Person, foaf:Group etc.. Stakeholder Stakeholder Rule: Every Author only votes at most one requirement. Abstimmung Vote