Required Domain Knowledge in Model UI Fragment Properties@0.0.3
Contents
- Audit Properties
- Content Markup Properties
- Context-of-Use Properties
- Cultural Environment
- Organization Environment
- Physical Environment
- Regulatory Environment
- Technical Environment
- User
- BasicCognitiveProperties
- Knowledge
- Required Arbitrary Knowledge
- Required Content Entity Assembly Knowledge
- Required Content Entity Configuration Knowledge
- Required Content Entity Knwoledge
- Required Content Entity Operating Mode Knowledge
- Required Domain Knowledge
- Required Location Knowledge
- Required Process Knowledge
- Required Product Knowledge
- Required Task Type Knowledge
- Personality Traits
- Skills
- Knowledge
- BasicPhysicalProperties
- Design process documentation
- Handicaps and Deficiencies Supported
- 3D Vision Limitation
- Attentiveness Limitation
- Colour Vision Limitation
- Directional Hearing Limitation
- Far Distance Vision Limitation
- Generic Limitation
- Hearing Limitation
- Orthography Limitation
- Short Distance Vision Limitation
- Short Term Memory Limitation
- Speech Recognition Limitation
- Tactile Insensitivity Limitation
- Temperature Insensitivity Limitation
- Vision Limitation
- User Equipment
- BasicCognitiveProperties
- Design Properties
- Property Types
- Audit Property Types
- Content Markup Types
- Context-of-Use-PropertyTypes
- Cultural Environment Property Types
- Organization Environment Property Types
- Physical Environment Property Types
- Regulatory Environment Property Types
- CategorizedDescriptionType
- DataCollectionActivationTypeType
- DataCollectionDeclarationType
- DataProcessingDeclarationType
- DataStorageLocationDeclarationType
- DataTransferPolicyDeclarationType
- PredefinedRegulatedDesignAspectType
- PredefinedRegulationLevelType
- RegulatedDesignAspectType
- RegulationLevelType
- RegulatoryDomainType
- TermsOfServiceDeclarationType
- Technical Environment Property Types
- EntityStateType
- EnvironmentalEquipmentType
- Platform Requirement Property Types
- DevicePropertyRequirementType
- DeviceRequirementListType
- DeviceRequirementType
- DeviceTypePropertyRequirementType
- DeviceTypeRefType
- DimensionAccuracyType
- MeasurementDimensionRefType
- PlatformPropertyRequirementListType
- PlatformPropertyRequirementType
- PlatformRefListType
- PropertyRequirementType
- SensorRequirementListType
- SensorRequirementType
- SensorTypeRefType
- Software Requirement Property Types
- ValueStatementType
- User Property Types
- Design Property Types
- ActivationCategoryType
- ActivationType
- AdaptationType
- AnimatedRepresentationType
- AugmentationTypeType
- ContentEntityAssemblyTypeType
- DialogTypeRefType
- DialogTypeType
- GraphicAbstractionLevelType
- GraphicDimensionType
- ImmersionModeType
- InteractionBlockingTypeType
- LayoutMechanicsCategoryType
- LayoutMechanicsType
- LayoutRefType
- NavigationDirectionTypeType
- NavigationElementType
- PerspectiveTypeType
- PredefinedDialogTypeType
- PredefinedUIDesignPatternType
- PredefinedViewOrderCriteriaType
- PredefinedViewTypeType
- ProportionateScaleType
- QualitativeScaleType
- RegistrationReferenceListType
- RegistrationReferenceType
- RegistrationTypeType
- ScaleType
- SemanticAbstractionLevelType
- UICustomizationType
- UIDesignPatternRefType
- UIDesignPatternType
- ViewOrderCriteriaRefType
- ViewOrderCriteriaType
- ViewTypeRefType
- ViewTypeType
- Section Reference Types
- Technical Property Types
- Tool Property Types
- Use-Case Property Types
- Technical Properties
- Use Case Properties
FragmentProperty: Required Domain KnowledgeStatus: EXPERIMENTAL
Documentation
Denotes required domain concepts. For example, in process industries, a plant operator should know about the process, the types of devices that are needed to control the process, and the required procedures that are to be performed by ui users. The abstract term 'domain concepts', thus, refers to well known domain-related type definitions that even may be standardized within the respective domain and to individual (e.g. devices) that are derived from these types and may be uinique in composition and behaviour. Since ui fragments are intended to be linked to their respective content entity (the type of which may be a domain concept), the content of ui fragments themselfes can be seen as domain concepts. That is due to the fact that ui fragments usually use a domain specific ui syntax to represent their corresponding entity.
Typed Element: → 'KnowledgeReferenceType'
Instanciatable Types 1
Base Type: STRUCTURED
Abstract: No
Cardinality: 0..1
From Model: UI Fragment Properties
Documentation: <NONE>
- entity : → 'GenericReferenceType' [1..∞]
- quality : → 'KnowledgeLevelType' [0..1]