ISO IEC IEEE 24774 pdf free download

ISO IEC IEEE 24774 pdf free download.Systems and software engineering一 Life cycle management一 Specification for process description.
Process outcomes are measurable, tangible, technical or business results that are achieved by a process. For example, the results are used by other processes. Outcomes are observable and assessable. Outcomes are distinguished from outputs and are not stated as the production of a document, record, or other in formation item.
An outcome shall be phrased as a declarative sentence using a verb in the present tense. For example, if the preceding sentence is phrased as an outcome, the preceding sentence states, “Outcomes are phrased as declarative sentences using verbs in the present tense.”
Outcomes shall be expressed in terms of a positive, observable objective, e.g. the provision of a service, a significant change of state, the successful maintenance of a desired state (e.g. safety), or the meeting of specified objectives (such as requirements, goals).
An outcome shall express a single result. Hence, the use of the word “and” or “and/or” to conjoin clauses shall be avoided; such constructions are better expressed as multiple outcomes.
Outcomes of generic processes shall be written in a manner that is meaningful for any scope of applicability, e.g. for organizations of any relevant domain or size.
As a test of completeness, the set of outcomes shall be sufficient to achieve the stated purpose of the process.
As a test of relevancy, each outcome shall be phrased so that it is necessary to the achievement of the purpose of the process.
Outcomes shall avoid requiring any specific method, technique or tool.
Outcomes shall avoid requiring any specific process measures or management methods.
Outcomes shall avoid presuming any particular sequence of execution; and the process user shall not be expected to presume any sequence.
Outcome statements should be no longer than two lines of text, about 20 words.
A process should have from three to seven outcomes, but may have only one or two outcomes.
Outcomes should be differentiated from benefits, which are positive achievements from the execution of a process, often spread broadly across the business and not necessarily related to the technical or business intent of executing a process. Benefits are not usually assessable, or at least not assessable using process assessment approaches. A benefit may provide the motivation to execute a process, but it may not be the primary reason to do so. Benefits may be described in an informative Note to the purpose statement.
The list of outcomes associated with a process should be prefaced by the text, “As a result of successful implementation of this process…”
There is no need for a one-to-one correspondence between outcomes and activities; in particular, it is not necessary to specify an activity for every outcome of a process or an outcome for every activity. The execution of the activities, considered as a group, shall produce the set of outcomes, considered as a group.
Outcomes should be meaningful and understandable when considered individually. They may be based on terminology and concepts that are further explained by other material included in the process description.
ISO IEC IEEE 24774  pdf download.