Website additions and updating September 2012
Register and Login to see details of PSL/PSA (your information will not be given to any third party)
As soon as the first version of PSL/PSA-lite has been released, work will continue to make available once again, the full capability of PSL/PSA® as most people will have known it. There may be some variation and work is underway to investigate the reasoning behind the inclusion of some of the original relations.
ATTRIBUTE, CONDITION, ELEMENT, ENTITY, EVENT, GROUP, INPUT, INTERFACE, MEMO, OUTPUT, PROCESS, PROCESSOR, RELATION, REQUIREMENT, RESOURCE, ,SET, SUBTYPE, SYSTEM-PARAMETER, UNIT.
PSL/PSA relations (some have been combined into subject to make this list):
access-right, adds, asserts, associated, attributes, becoming-false, becoming-true, cardinality, causes, changes, classification, coding-structure, collection, composite, connectivity, consists, consumes, creates, derives, destroys, element-values, employs, equivalent-to, false-interrupts, false-termination, false-triggers, function-of, generates, happens, identifies, inception-causes, in-response-to, interrupts, keywords, left-part, maintains, makes-false, makes-true, measures, memo, modifies, ordered-by, partial-order, performs, receives, references, removes, responsible-interface, responsible-problem-definer, right-part, security, source, subparts, subsets, subsetting-criterion, syspar-range, syspar-value, terminates, termination-causes, trace-key, triggers, true-interrupts, true-termination, true-triggers, updates, utilizes.
Following on from a re-issue of PSL/PSA the next version is likely to be a variant that is more suitable for the modelling of systems generally. Some of the PSL/PSA objects are really more suited to modeling required information processing systems. However, PSL/PSA has been used successfully to model systems, and not only information systems. This requires little modification to the definition of PSL, by the addition of a small number of objects and relations. This becomes evident if a PSL model is viewed as a semantic network of objects joined by relations - putting on one side for a moment, the names of the specific objects, it should be clear that in many cases such a semantic network can be isomorphic to a semantice network for a system and not only an information system. It is only that the names of the objects and relations in those semantic networks need to be adjusted to give clearer contextual meaning.