Process

<accesscontrol>members of projects</accesscontrol> tyjak:Prosessiolion rakenne

Process

<section begin=glossary />In general (according to the PSSP ontology), a process is a change of substance in time. It is one of the universal objects. In the open assessment context, the information processes related to the doing of an assessment are described as processes. In contrast, the processes that occur in the nature are described as variables. Methods are typical processes in open assessment.

<section end=glossary />

Template: process description (a guidebook information object)

Summary

The summary of a process is a very short overview of the process, and may contain all types of information that are considered relevant for this specific process (max words: 250?)

Name

The name of the process should be unique (there should not be two objects (processes, products or product descriptions) with identical names). The name should be chosen so that it is descriptive, unambiguous and not easily confused with other processes, products or product descriptions. (max words: 20?)

Purpose

(This is the same as Scope in the general object attribute list.) The general purpose of every process is to manipulate information in aim to produce a particular information product. The process-specific purpose describes the intended product of this particular process. This should contain all relevant information needed to distinguish the process from other processes. (max words: 400?)

Structure of the process

(This is the same as the Result (of the process description) in the general object attribute list.) The result section has three sub-attributes. (max words: 3000?)

Input format

The input data, variable or parameter types, their syntax, and other relevant information is described here.

Procedure

The actual process – how it works and how to do – is described here. It consists of e.g. the mathematical formula to calculate the result. The procedure uses algebra or other explicit methods if possible.

Management

A complex process may require that also the management process of the procedure is described. The procedure may for example be a mathematical algorithm. The management process is a computer software that runs the algorithm, so that when you have the software, the management is a trivial task. If you do not have the management process - well, good luck to you and your calculator. So, actually models and software are procedures that have the management process packed into the same neat package. An other example of a management process is a guidance by the U.S.EPA about how to plan and organise for stakeholder meetings. The actual procedure here is to obtain information and feedback from the stakeholders.

Output format

shortly describes the format of the product of the process, which should fulfil the purpose as described in the scope. It furthermore links – if applicable – to the product object.

Rationale

(This is the same as the Definition (of the process description) in the general object attribute list.) This attribute answers to the following questions: What is known about a good process for this purpose? How do you know that the procedure described is good? (max words: 2000)

See also

See also links to pages (both internal guidebook pages and external) which relate to the process subject. All subjects that could be relevant for readers of this page can be listed here. (max links: 20?)

References

All references, as used in the texts above. (max references: 30?)

You can copy and paste the template below to your page. Put the name of the process as the name of your page.

<accesscontrol>members of projects</accesscontrol> {{method}} '''Summary''' ==Purpose== ==Structure of the process== ===Input format=== ===Procedure=== ====Management==== ===Output format=== ==Rationale== ==See also== ==References== <references/>