A competence map or competency map defines a tree or network of connected competences that are in turn operationalized in terms of learning objectives.
Maps are how skills and competencies or competency definitions can be aggregated to form more comprehensive skills and competencies, or decomposed into component skills or competencies. Taxonomies are simple maps in the form of trees, according to the IMS Reusable Definition of Competency or Educational Objective - Best Practice and Implementation Guide [1]
Competence maps allow defining curriculum content in terms of interrelated competencies rather than in terms of fragmented or disassociated knowledge, skills and attitudes. (Stoof et al.2007:348).
Competency data are also essential to automatize training. “Competitive performance in today's organization requires a good handle on how to acquire, recognize and use competencies within the organizations. Automated competency tracking and management in the context of performance support, training and adaptive online learning requires a systematic way to define and track competencies for individuals and teams. However, the competency data may come from a variety of sources and in many different formats.” (Learning Technology: The Big Picture by C. Ostyn (2005), retrieved May 2016.
See also:
Schools can define competence maps in several ways:
Skill gap analysis, e.g. through various means, e.g. learning analytics or positioning tests allow for better counseling or organization of catch-up modules, etc.
Organisation can use competence maps in the following way:
The following figure by Claude Ostyn, shows a model of the Ecosystem of competence management. “This diagram is an attempt to show how learning management, training management and performance support systems can be aligned with business goals as part of an "ecosystem of competencies".” (2005)
Competence maps can be defined in non-formal of formal ways. Formal standards do have the advantage that they could integrate with learning infrastructures such as LMSs or LCMS. Claude Ostyn, in a [ working paper] defined sample use case for competency technical standards.
Schneckenberg's (2010:986) [2] definition of eCompetence (i.e. the bundle that is required from teachers to use educational technology) is defined as action competence, i.e. “relates the ability for adequate action to complex electronic contexts (Phelps, Hase & Ellis, 2005). [3]”. He then cites and agrees with Van de Blij (2002) [4] who defines “action competence as ‘...the ability to act within a given context in a responsible and adequate way, while integrating complex knowledge, skills and attitudes’. The dispositional components of knowledge, skills and attitudes (KSA) are at the core of the action competence concept.”.
Knowledge, skills and attitudes alone cannot really be observed and in addition (even if exist) do not guarantee action. The latter depends on context, resources, motivation, etc. Someone is more likely to use a competence if the context requires action and the environment encourages its use. For example, a teacher is more likely to use technology if the pedagogical challenge requires it and if the institution values investment in education and encourages the use of educational technology.
Stoof et al (2007:349) acknowledge that competence can be defined in manners that suit specific situations. They however point out six important dimensions found in an analysis of 16 competence maps and that designers should think about when creating competence maps:
Winterton et al. (2005) [5] distinguish between four main kinds of competence as shown in the table below. The cognitive, functional and social competences correspond to the french savoir (knowledge), savoir-faire (know-how), and savoir-être (identity) and also to the KSA (knowledge, skills, attitudes model).
occupational | personal | |
---|---|---|
conceptual | Cognitive competence (knowledge) | Meta-competence (facilitating learning) |
operational | Functional competence (skills) | Social competence (attitudes and behaviours) |
The authors also show, that various national cultures, while distinguishing knowledge from know-how (skills) and some sort of social competence, do define competence in different ways, the German approach distinguishing Fachkompetenz (domain knowledge and skills), more general Sachkompetenz (domain knowledge), Methodenkompetenz (methods), Sozialkompetenz (social competence), and Personalkompetenz (personal competence)
Many institutions, in particular those define learning standards sometimes define broad categories of competences or learning outcomes. Often a distinction is made between "transversal skills" and domain-specific ones, although generic skills (such a communication, information, of evaluation skills) do seem to be partly or strongly context dependent.
An example of basic stills [6] that would be required from ICT workers is cited in Winterton, 2005:48-49) [5] and includes three categories:
Many of the listed skills are higher-level competences and some are metacognitive.
According to Stoof et al. (2007:348)
Competence maps typically consist of three parts:
The most important element for instructional designs are the competence descriptions.
Stoof et al (2007:352) identify 4 phases:
Stoof et al. (2006, 2007) argue that four aids seem to be particularly useful:
COMET is a loose acronym for Competency Modeling Toolkit, a web-based tool developed by Angela Stoof. (Daniel K. Schneider does not know whether it is used in production).
Stoof et al. (2006) studied wether a combination of a construction kit, phenomenarium, and information bank could help designers, i.e. improve the process quality of making a competence map.
“In a factorial design, eight conditions with all possible combinations of construction kits (present or absent), phenomenaria (present or absent) and information banks (full or condensed) were compared. (p. 204).”. Results indicated that availability of a construction kit enhanced percieved support and control however at the cost of taking more time. The phenomeniarium both improved perceived support and control, even in the absence of the construction kit. Finally, the information bank did not have any effect on process quality.
Competences can be described with formal languages.
These can:
“The Reusable Definition of Competency or Educational Objective (RDCEO) specification provides a means to create common understandings of competencies that appear as part of a learning or career plan, as learning pre-requisites, or as learning outcomes. The information model in this specification can be used to exchange these definitions between learning systems, human resource systems, learning content, competency or skills repositories, and other relevant systems. RDCEO provides unique references to descriptions of competencies or objectives for inclusion in other information models” (IMS Reusable Definition of Competency or Educational Objective Specification, retr. May 2016).
The RDECO Conceptual Model includes three types of data (IMS 2002: section 2.1) [1]
IMS RDCEO is the basis of IEEE 1484.20.1 IEEE Standard for Learning Technology - Data Model for Reusable Competency Definitions (commercial access) [7]
IEEE definitions of terms
Competency: Any aspect of competence, such as knowledge, skill, attitude, ability, or learning objective.
“In this Standard, the term “competency” is to be interpreted in the broadest sense to include learning objectives (those things that are sought) as well as competencies (those things that are achieved). The term “competency” is also used to include all classes of things that someone, or potentially something, can be competent in, although some communities of practice use the term with nuance, for example, limiting its use to skill and excluding knowledge or understanding.” (IEEE 2007: 3)[7]
The synopsis of the formal data model is defined as follows (page 5). It includes five elements, an identifier, a title, a description, a definition and some metadata.
Synopsis
reusable_competency_definition :
record
(
identifier :
long_identifier_type,
// Mandatory
// Occurs 1 time
title :
bag of langstring_type(1000),
// Mandatory
// Occurs 1 time
// SPM: 20 instances of langstring_type in the bag
// The parameter value is the SPM for the number of of characters in the string element of the langstring_type
description :
bag of langstring_type(4000),
// Optional
// Occurs 0 or 1 times
// SPM: 20 instances of langstring_type in the bag
// The parameter value is the SPM for the number of of characters in the string element of the langstring_type
definition :
definition_type,
// Optional
// Occurs 0 or more times
// SPM: 10 instances of definition in a reusable_competency_definition record
metadata :
metadata_type,
// Optional
// Occurs 0 or 1 times
)
The title is a mandatory single text label for the RCD. The label is a human-readable name for the RCD.
The description is optional and contains a human readable description of a competency.
The definition includes a structured, more formal description of the competency. It includes two subelements.
Examples
Bibliography
Cited with footnotes