Here is a list of related doctypes to document system environments.

A process is a description of the steps to take to create the intended result. Agile teams usually work closely together and therefore have little need to document how they are doing things. In addition to that, agile teams usually seek to automate repetitive tasks and have their process descriptions in form of scripts.

But if the need arises, that the team decides to document how specific things should be done, the process document type is useful. It may also be the first attempt to describe a process before it is scripted. Some processes may not be scriptable, because the mainly describe the interaction between roles in the team.

A component describes a piece of implementation from its conceptional and implementation view. Components are part of the systems. Artifacts on the other hand may be created or passed to third parties who are not interested in the functional aspects of the component, but treat the artifact as an input to a process. Artifact documents describe these artifacts from that view.