Subject: Modeling: Archetypes vs. Stock & Flow

Posted by Sharon Villines on 12/28/2009
In Reply To:Modeling: Archetypes vs. Stock & Flow Posted by Gene Bellinger on 12/27/2009

Message:

I haven't been following this thread closely so apologies if this has been covered. This information science definition of "archetype" makes little sense to me (lots of information, no communication) but may help this conversation along.

> Archetype (information science)
>
> From Wikipedia, the free encyclopedia
>
> In the field of informatics, an archetype is a formal re-usable model
> of a domain concept. Traditionally, the term archetype is used in
> psychology to mean an idealized model of a person, personality or
> behaviour (see Archetype). The usage of the term in informatics is
> derived from this traditional meaning, but applied to domain modelling
> instead.
> An archetype is defined by the OpenEHR Foundation (for health
> informatics) as follows:[1]
>
> An archetype is a computable expression of a domain content model in
> the form of structured constraint statements, based on some reference
> model. openEHR archetypes are based on the openEHR reference model.
> Archetypes are all expressed in the same formalism.
> In general, they are defined for wide re-use, however, they can be
> specialized to include local particularities. They can accommodate any
> number of natural languages and terminologies.
>
> The use of archetypes in health informatics was first documented by
> Thomas Beale, who stated the concept was coined by Derek Renouf.
> According to Beale, Renouf applied archetypes to configuring Smalltalk
> systems.[2]

Sharon