Name: Concept System
Based on: System (Abstract)
Abstract System: This system has been identified as an abstract system that cannot be implemented directly. The abstract system establishes a shared pattern of characteristics that any system can use to describe its unique characteristics when referenced in the 'based on' list above. These references are described using a generalization association in UML.
Concept Systems are used in Terminology and Ontology Work.
Terminology and Ontology Work Standards.
The scope of this system is being explored in conjunction with Ontology and Symbol Systems.
A Concept System provides a way to identify the concepts and "concept relation"s that underpin the terminology for a domain of knowledge. Each concept is then defined with name and definition to establish a unit of knowledge.
The terminology can then be used in various types of documents and conversations within an organization.
The terminology work behind the Concept System ensures:
-
No duplicates with data validation
-
Coherent concept definitions and use
-
The underlying corpus is aligned to the vocabulary
-
All domains can use the same approach to define their terminology
Systemic Measurable Variables
Terms in use in an organization
Terminology issues reported and resolved
Systemic Quality Properties
Coherence across the domain
Understanding and meaning across the domain
Ease of Use of concepts
Concepts embedded in training and other terminology resources and these are being used.
System Quantity Properties
Number of Concepts
Systemic Capabilities or Functions
To convey the meaning and build a common context of meaning for an organization.
To establish a knowledge base that can be improved through usage..
System States
The various defined states that the system-of-interest can be in.
- Architectural states: Generally defined in the enabling system
- Concept System and Domain Identified
- Concept System Scope Identified.
- Transformational States Generally defined in an enabling or adaptive system associated with the control system.
- Concepts identified
- Concept Relationships identified
- Concept Model prepared
- Terms and definitions prepared.
- Operational States: These are typically initialising, Reference input change, stable, shutting down.
- Terminology is embedded in terminology resources and used.
- Terminology is improved based upon usage..
Identify the key stakeholders and their concerns for this system. Each stakeholder is identified and their concerns and interests are identified. The list below is an example. Each system will have a specific set of stakeholders and concerns.
- Standards Writers: Are concepts identified and clearly defined?
- System Architect: Is the domain of knowledge clear and bounded?
- Ontology Engineers Can the concepts be placed in a formal ontology? or are they already in a formal ontology?
- Change Agents Can we use the concepts with our stakeholders?
- Process Developers What terminology already exists and what are terminology gaps for a new or updated process?
- People who are part of the system Will the stakeholders in the domain recognize the concepts?
The environment and the potential impacts on the system-of-interest.
-
Other Top Level Ontologies
-
Other Conceptual Models in other Domains.
The Concept System is expected to be established, maintained and used within organizations carrying out terminology work.
Terminology work to Establish and maintain Concept Systems is embedded in an organization as a capability. See the following organization and capability systems:
The diagram below highlights the key areas of a terminology work capability in an organization:
Terminology work capabilities are used to:
-
develop standards
-
develop processes
-
work with languages and translations
-
work with IT to create machine readable / translatable language elements.
The following System Breakdown Structure shows the concepts and their relations for the Concept System. The concepts in the Concept Model show the definition number in ISO 1087:2019.
Additional Key Concept System Key Concept Term Types
Configuration / Scenario:
Describes any configuration / scenario attributes for a specific system-of-interest. This may not be appropriate for all system descriptions (e.g. patterns or abstract systems).
There are various ways to present the concept system. The System Description approach uses UML as the Modelling Language. Other modelling languages can be used. Each approach may have tradeoffs / tool support, training and learning support, etc.
Mathematical Methods Used:
Set Theory and Category Theory may help with terminology mapping
Cyclical (Repeating / Regular) Processes
The regular / repeating processes are:
Trigger: Use of a term is problematic Process: Record an issue and evaluate and identify actions to be prioritized
Trigger: New terms found with similar concepts Process: Consider harmonizing concepts and terms
Trigger: New concepts found within the domain Process: Record an issue and evaluate and identify actions to be prioritized.
Development Life Cycle Processes
The development life cycle for a Concept System is the following:
Identify the Domain and Scope for the Concept System
Identify the source data for the concept system.
Identify the Concepts.
Identify the Concept Relations
Identify the designations (Terms, Symbols, etc)
Identify the Definitions
Check the terminology on the list according to the criteria
Consider harmonizing concepts and / or Terminology.
Integrate Terminology into Terminology Resources
These steps should appear in a terminology work process underlying a terminology work capability.
The following references support this type of system-of-interest.
Click here to provide feedback on this topic