SpecIF Domain Classes
Domain classes are generated from the SpecIF Ontology. Here, the classes of release 1.1 are listed.
Domain 01: Base Definitions
Data types of domain 01: Base Definitions
| title | id | revision | type | description |
|---|---|---|---|---|
| Boolean | DT-Boolean | 1.1 | xs:boolean | The Boolean data type. |
| Byte | DT-Byte | 1.1 | xs:integer | A byte is an integer value between 0 and 255. |
| Integer | DT-Integer | 1.1 | xs:integer | A numerical integer value from -32768 to 32767. |
| Real | DT-Real | 1.1 | xs:double | A floating point number (double). |
| Real with 2 Decimals | DT-Decimal2 | 1.1 | xs:double | A floating point number (double) with two fraction digits. |
| Date or Timestamp | DT-DateTime | 1.1 | xs:dateTime | Date or timestamp in ISO-format |
| String[256] | DT-ShortString | 1.1 | xs:string | String with max. length 256 |
| Plain or formatted Text | DT-Text | 1.1 | xs:string | An account of the resource (source: http://dublincore.org/documents/dcmi-terms/). Descriptive text represented in plain or rich text using XHTML. SHOULD include only content that is valid and suitable inside an XHTML <div> element (source: http://open-services.net/). |
| URL | DT-URL | 1.1 | xs:string | A uniform resource locator. |
| DT-EmailAddress | 1.1 | xs:string | Data type to represent an e-mail address. | |
| SpecIF:LifeCycleStatus | DT-LifeCycleStatus | 1.1 | xs:string | Enumerated values for status
|
| SpecIF:Priority | DT-Priority | 1.1 | xs:string | Enumerated values for priority
|
| SpecIF:Discipline | DT-Discipline | 1.1 | xs:string | Enumerated values for engineering discipline
|
Property classes of domain 01: Base Definitions
| title | id | revision | dataType | description |
|---|---|---|---|---|
| dcterms:identifier | PC-VisibleId | 1.1 | String[256] | A unique reference to the resource within a given context. (source: DCMI) An identifier for a resource. This identifier may be unique with a scope that is defined by the RM provider. Assigned by the service provider when a resource is created. Not intended for end-user display. (source: OSLC) |
| dcterms:title | PC-Name | 1.1 | String[256] | A name given to the resource. (source: DCMI) Title (reference: Dublin Core) of the resource represented as rich text in XHTML content. SHOULD include only content that is valid inside an XHTML <span> element. (source: OSLC) |
| dcterms:description | PC-Description | 1.1 | Plain or formatted Text | An account of the resource. (source: DCMI) Descriptive text (reference: Dublin Core) about resource represented as rich text in XHTML content. SHOULD include only content that is valid and suitable inside an XHTML <div> element. (source: OSLC) |
| SpecIF:Origin | PC-Origin | 1.1 | String[256] | The origin (source, reference) of an information or requirement. |
| SpecIF:Diagram | PC-Diagram | 1.1 | Plain or formatted Text | A partial graphical representation (diagram) of a model. |
| SpecIF:Notation | PC-Notation | 1.1 | String[256] | The notation used by a model diagram, e.g. 'BPMN:2.0', 'OMG:SysML:1.3:Activity Diagram' or 'FMC:Block Diagram'. |
| SpecIF:LifeCycleStatus | PC-LifeCycleStatus | 1.1 | SpecIF:LifeCycleStatus | The 'status', e.g. lifecycle state, of the resource. |
| SpecIF:Priority | PC-Priority | 1.1 | SpecIF:Priority | The 'priority' of the resource. |
| SpecIF:Discipline | PC-Discipline | 1.1 | SpecIF:Discipline | The engineering discipline (system, electronics, mechanics, software, safety). |
| SpecIF:Responsible | PC-Responsible | 1.1 | String[256] | The 'person' being responsible for the resource. |
| SpecIF:DueDate | PC-DueDate | 1.1 | Date or Timestamp | A 'due date' for the resource. |
| UML:Stereotype | PC-Stereotype | 1.1 | String[256] | A stereotype gives an element an additional/different meaning. |
| SpecIF:Abbreviation | PC-Abbreviation | 1.1 | String[256] | An abbreviation for the resource or statement. |
| dcterms:type | PC-Type | 1.1 | String[256] | The element type resp. the metamodel element (e.g. OMG:UML:2.5.1:Class) |
| SpecIF:Alias | PC-Alias | 1.1 | String[256] | An alias name for the resource. |
| rdf:value | PC-Value | 1.1 | Plain or formatted Text | A value of different meaning, depending on the element type (attribute default value, a taggedValue value etc.). |
Resource classes of domain 01: Base Definitions
| title | id | revision | description |
|---|---|---|---|
| SpecIF:Heading | RC-Folder | 1.1 | Folders with title and text for chapters or descriptive paragraphs. Property classes:
|
| SpecIF:Paragraph | RC-Paragraph | 1.1 | Information with text for descriptive paragraphs. Property classes:
|
| SpecIF:Hierarchy | RC-Hierarchy | 1.1 | Root node of a hierarchically organized specification (outline). Property classes:
|
| SpecIF:Comment | RC-Comment | 1.1 | Comment referring to a model element ('resource' or 'statement' in general). Property classes:
|
Statement classes of domain 01: Base Definitions
| title | id | revision | description |
|---|---|---|---|
| rdf:type | SC-Classifier | 1.1 | States that the relation subject is an instance of the relation object. |
| SpecIF:refersTo | SC-refersTo | 1.1 | A resource 'refers to' any other resource. Property classes:
|
Domain 02: Requirements Engineering
Data types of domain 02: Requirements Engineering
| title | id | revision | type | description |
|---|---|---|---|---|
| IREB:RequirementType | DT-RequirementType | 1.1 | xs:string | Enumerated values for the requirement type according to IREB.
|
| Perspective | DT-Perspective | 1.1 | xs:string | Enumerated values for the perspective (of a requirement)
|
Property classes of domain 02: Requirements Engineering
| title | id | revision | dataType | description |
|---|---|---|---|---|
| IREB:RequirementType | PC-RequirementType | 1.1 | IREB:RequirementType | Enumerated value for the requirement type according to IREB. |
| SpecIF:Perspective | PC-Perspective | 1.1 | Perspective | Enumerated values for the perspective (of a requirement). |
Resource classes of domain 02: Requirements Engineering
| title | id | revision | description |
|---|---|---|---|
| IREB:Requirement | RC-Requirement | 1.1 | A 'requirement' is a singular documented physical and functional need that a particular design, product or process must be able to perform. Property classes:
|
| SpecIF:Feature | RC-Feature | 1.1 | A 'feature' is an intentional distinguishing characteristic of a system, often a unique selling proposition. Property classes:
|
Statement classes of domain 02: Requirements Engineering
| title | id | revision | description |
|---|---|---|---|
| SpecIF:dependsOn | SC-dependsOn | 1.1 | Statement: Requirement/feature depends on requirement/feature. |
| SpecIF:duplicates | SC-duplicates | 1.1 | The subject requirement duplicates the object requirement. |
| SpecIF:contradicts | SC-contradicts | 1.1 | The subject requirement contradicts the object requirement. |
| IREB:refines | SC-refines | 1.1 | The subject requirement refines the object requirement. |
Domain 03: Model Integration
Data types of domain 03: Model Integration
| title | id | revision | type | description |
|---|---|---|---|---|
| SpecIF:VisibilityKind | DT-VisibilityKind | 1.1 | xs:string | Enumerated values for visibility.
|
Property classes of domain 03: Model Integration
| title | id | revision | dataType | description |
|---|---|---|---|---|
| SpecIF:Visibility | PC-Visibility | 1.1 | SpecIF:VisibilityKind | The visibility of a resource (e.g. public, private, protected,...) as known from object orientation. |
| SpecIF:ImplementationLanguage | PC-ImplementationLanguage | 1.1 | String[256] | The name of an used implementation language (e.g. C, C++, C#, Java, ADA, OCL, ALF etc.). |
Resource classes of domain 03: Model Integration
| title | id | revision | description |
|---|---|---|---|
| UML:Package | RC-Package | 1.1 | A 'package' is used to bring structure into a model. Packages can contain further packages and/or (model-)elements. It corresponds to a package in UML/SysML or a folder in a file system. Property classes:
|
| SpecIF:View | RC-View | 1.1 | A 'view' is a graphical model view with a specific communication purpose, e.g. a business process or system composition. Property classes:
|
| FMC:Actor | RC-Actor | 1.1 | An 'actor' is a fundamental model element type representing an active entity, be it an activity, a process step, a function, a system component or a role. Property classes:
|
| FMC:State | RC-State | 1.1 | A 'state' is a fundamental model element type representing a passive entity, be it a value, a condition, an information storage or even a physical shape. Property classes:
|
| FMC:Event | RC-Event | 1.1 | An 'event' is a fundamental model element type representing a time reference, a change in condition/value or more generally a synchronization primitive. Property classes:
|
| SpecIF:Collection | RC-Collection | 1.1 | A 'collection' is a logic (often conceptual) group of resources linked with a SpecIF:contains statement. It corresponds to a 'group' in BPMN diagrams or a 'boundary' in UML diagrams. Property classes:
|
| SpecIF:SourceCode | RC-SourceCode | 1.1 | Source code assigned to a model element (e.g. an activity or operation). Typically used for model-based code generation to provide some code snippets inside the model. Property classes:
|
Statement classes of domain 03: Model Integration
| title | id | revision | description |
|---|---|---|---|
| SpecIF:shows | SC-shows | 1.1 | Statement: Plan resp. diagram shows model element. |
| SpecIF:contains | SC-contains | 1.1 | Statement: Model element contains model element. |
| SpecIF:serves | SC-serves | 1.1 | Statement: An actor serves an actor. |
| SpecIF:stores | SC-stores | 1.1 | Statement: Actor (role, function) writes and reads state (information). |
| SpecIF:writes | SC-writes | 1.1 | Statement: Actor (role, function) writes state (information). |
| SpecIF:reads | SC-reads | 1.1 | Statement: Actor (role, function) reads state (information). |
| SpecIF:influences | SC-influences | 1.1 | Statement: A state (information) influences a state (information). |
| SpecIF:precedes | SC-precedes | 1.1 | An FMC:Actor 'precedes' an FMC:Actor or an FMC:Actor 'precedes' an FMC:Event or an FMC:Event 'precedes' an FMC:Actor. The rdf:type property specifies if it is a simple precedes, a SpecIF:signals or a SpecIF:triggers. Property classes:
|
| oslc_rm:satisfies | SC-satisfies | 1.1 | Statement: Model element satisfies requirement. |
| SpecIF:allocates | SC-allocates | 1.1 | Statement: Model element is allocated to model element. The semantics are equal to allocation in SysML or deployment relation in UML. |
| SpecIF:implements | SC-implements | 1.1 | A FMC:Actor or FMC:State 'implements' a SpecIF:Feature. |
| SpecIF:isAssociatedWith | SC-isAssociatedWith | 1.1 | The subject is associated with the object. Property classes:
|
| SpecIF:isSpecializationOf | SC-isSpecializationOf | 1.0 | A term is a specialization of another, such as 'Passenger Car' and 'Vehicle'. |